windows users

[Jim]

Hi

I would like to get all the windows users defined in the current domain.
What is the code for this?

ch Jim

[Sahil Malik]

Using WMI - "Select * from Win32_UserAccount" and then look for "FullName"
or "Name" where "Domain" matches.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hi

I would like to get all the windows users defined in the current domain.
What is the code for this?

ch Jim

[Jim]

against which database do i have to run this?

ch Jim
"Sahil Malik" <co*****************@nospam.com> schreef in bericht
news:uB**************@TK2MSFTNGP15.phx.gbl...

Using WMI - "Select * from Win32_UserAccount" and then look for "FullName"
or "Name" where "Domain" matches.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hi

I would like to get all the windows users defined in the current domain.
What is the code for this?

ch Jim

[Willy Denoyette [MVP]]

You should not use WMI for this, use the System.Directory namespace classes
DirectoryEntry and DirectorySearcher, these are wrappers arround ADSI.
If your domain is AD based (W2K and higer) use the LDAP ADSI provider for
downlevel domains (NT4) you have to use WinNT as provider.
Check following link for samples:

http://msdn.microsoft.com/library/de...e_examples.asp

Willy.
"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

against which database do i have to run this?

ch Jim
"Sahil Malik" <co*****************@nospam.com> schreef in bericht
news:uB**************@TK2MSFTNGP15.phx.gbl...

Using WMI - "Select * from Win32_UserAccount" and then look for
"FullName" or "Name" where "Domain" matches.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hi

I would like to get all the windows users defined in the current domain.
What is the code for this?

ch Jim

[Bob Powell [MVP]]

Please set your system clock correctly.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hi

I would like to get all the windows users defined in the current domain.
What is the code for this?

ch Jim

[Jim]

what is the problem with it? it displays the correct time over here

Jim
"Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> wrote in message
news:Ok**************@TK2MSFTNGP12.phx.gbl...

Please set your system clock correctly.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...

Hi

I would like to get all the windows users defined in the current domain.
What is the code for this?

ch Jim

[Jim]

thanks!

ch Jim
"Willy Denoyette [MVP]" <wi*************@pandora.be> wrote in message
news:Ot**************@TK2MSFTNGP14.phx.gbl...

You should not use WMI for this, use the System.Directory namespace classes DirectoryEntry and DirectorySearcher, these are wrappers arround ADSI.
If your domain is AD based (W2K and higer) use the LDAP ADSI provider for
downlevel domains (NT4) you have to use WinNT as provider.
Check following link for samples:

http://msdn.microsoft.com/library/de...e_examples.asp
Willy.
"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

against which database do i have to run this?

ch Jim
"Sahil Malik" <co*****************@nospam.com> schreef in bericht
news:uB**************@TK2MSFTNGP15.phx.gbl...

Using WMI - "Select * from Win32_UserAccount" and then look for
"FullName" or "Name" where "Domain" matches.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

I would like to get all the windows users defined in the current domain. What is the code for this?

ch Jim

[Cor Ligthert]

Jim,

It can be as well that your localization setting of your computer is wrong.

Cor

[Sahil Malik]

Isn't WMI an alternative? Why shouldn't it be used?

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik

"Willy Denoyette [MVP]" <wi*************@pandora.be> wrote in message
news:Ot**************@TK2MSFTNGP14.phx.gbl...

You should not use WMI for this, use the System.Directory namespace classes DirectoryEntry and DirectorySearcher, these are wrappers arround ADSI.
If your domain is AD based (W2K and higer) use the LDAP ADSI provider for
downlevel domains (NT4) you have to use WinNT as provider.
Check following link for samples:

http://msdn.microsoft.com/library/de...e_examples.asp
Willy.
"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@TK2MSFTNGP12.phx.gbl...

against which database do i have to run this?

ch Jim
"Sahil Malik" <co*****************@nospam.com> schreef in bericht
news:uB**************@TK2MSFTNGP15.phx.gbl...

Using WMI - "Select * from Win32_UserAccount" and then look for
"FullName" or "Name" where "Domain" matches.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
"Jim" <pe*********@hotmail.com> wrote in message
news:%2****************@tk2msftngp13.phx.gbl...
Hi

I would like to get all the windows users defined in the current domain. What is the code for this?

ch Jim

[Willy Denoyette [MVP]]

"Sahil Malik" <co*****************@nospam.com> wrote in message
news:uk**************@TK2MSFTNGP12.phx.gbl...

Isn't WMI an alternative? Why shouldn't it be used?

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik

Following are a number of reasons not to use WMI for this:
1. Speed. WMI wasn't designed for domain account management tasks,
especially for larger domains it tends to be real slow, Win32_UserAccount is
particularly known to affect performance negatively. LDAP based DS where
specially designed to execute such queries real fast.
2. Security. Most domain admins turn off WMI services on DC's, or are
granting access to domain admin only.
3. WMI doesn't have a notion of an AD domain hierarchy and as such is not as
feature rich as AD based DS.
4. Using WMI you have to know the DC to connect to, so it fails if the DC is
not reachable, AD DS automatically finds an alternate DC in the domain if a
connection to the logon DC fails.
5. WMI fails to enumerate other domains in the forest (see 3).

One can say it's an alternative for very small NT4 domains, but as it
doesn't offers any advantage over using the ADSI based "WinNT" provider
interfaces encapsulated by System.DirectoryServices, I would say stick with
DS even for small NT4 domains.

Willy.

[Sahil Malik]

Thanks Willy, these newsgroups are ultra-awesome.

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik

"Willy Denoyette [MVP]" <wi*************@pandora.be> wrote in message
news:#s**************@TK2MSFTNGP15.phx.gbl...

"Sahil Malik" <co*****************@nospam.com> wrote in message
news:uk**************@TK2MSFTNGP12.phx.gbl...

Isn't WMI an alternative? Why shouldn't it be used?

- Sahil Malik
http://dotnetjunkies.com/weblog/sahilmalik
Following are a number of reasons not to use WMI for this:
1. Speed. WMI wasn't designed for domain account management tasks,
especially for larger domains it tends to be real slow, Win32_UserAccount

is particularly known to affect performance negatively. LDAP based DS where
specially designed to execute such queries real fast.
2. Security. Most domain admins turn off WMI services on DC's, or are
granting access to domain admin only.
3. WMI doesn't have a notion of an AD domain hierarchy and as such is not as feature rich as AD based DS.
4. Using WMI you have to know the DC to connect to, so it fails if the DC is not reachable, AD DS automatically finds an alternate DC in the domain if a connection to the logon DC fails.
5. WMI fails to enumerate other domains in the forest (see 3).

One can say it's an alternative for very small NT4 domains, but as it
doesn't offers any advantage over using the ADSI based "WinNT" provider
interfaces encapsulated by System.DirectoryServices, I would say stick with DS even for small NT4 domains.

Willy.