Re: Enumerating all active computer accounts in a domain

From: Gerry Hickman (gerry666uk_at_yahoo.co.uk)
Date: 02/14/05


Date: Mon, 14 Feb 2005 22:13:07 +0000

Hi Sascha,

I _was_ talking about NT4 computers, that's why I suggested using the
WinNT provider with ADSI. I don't have NT4 right here in front of me so
can't test it, but if you get stuck, let me know.

Your NT4 boxes should have an ADSI client, if they don't, try to put one
on. You'll soon find out when you try to instantiate the object whether
or not the client is installed.

You can also test the WinNT provider on any workstation that has theh
client NT4, Win2k, XP. This is a good place to test things before you
hit your domain controllers for real.

Sascha wrote:
> Gerry Hickman wrote:
>
>> Hi,
>>
>> Have you had a look at using the WinNT provider with ADSI?
>>
>> It's important to understand the differece between "network discovery"
>> and simply getting "all computer accounts in a domain". Computer
>> accounts are specifically computers that are joined to the domain, but
>> anyone could have a laptop connected in the WORKGROUP workgroup if
>> they know the IP block and this laptop would NOT be included.
>>
>> Sascha wrote:
>>
>>> Hello,
>>>
>>> can anybody provide some wsh-code on the following problem:
>>>
>>> I want to get a collection of all the active computeraccounts in a
>>> NT4-Domain. So the result program should list all computers which
>>> normally get listed when using the following commandline:
>>> net view /domain:DOMAIN. So essentially all computers visible in the
>>> Netbios-Browselist for the NT4-Domain.
>>>
>>> If it's possible, I want to avoid using the net-command-tool and
>>> wonder if there is a "WMI" or a "WINNT:/" - Way to do it and get a
>>> collection of Objects.
>>>
>>> Any ideas? Thanks.
>>
>>
>>
>>
>
> Hello Gerry,
>
> thank you for the suggestion of the WINNT-Provider. But so far I did not
> find a solution to get the list of domain-member computers. Using ADSI
> is a possibility to get the computers using LDAP Queries. But I am
> talking about an NT4-Domain...
> Imagine that you open Network Neighborhood and doubleclick on a
> NT-domain. There you get the collection of computers, which are
> available in the domain and also turned on (at least most of them ;-).
> I am simply looking for a script that gives me exact this collection.
> But it seems that it's not possible that easy.
>
> Any further ideas?
>
> Regards,
>
> Sascha
>

-- 
Gerry Hickman (London UK)


Relevant Pages

  • Re: Unable to authenticate to untrusted domain NTLM v2 related issue
    ... computers via a local user account. ... I am having a problem getting XP SP1 clients using NTLM v2 (AD domain ... to authenticate (NT4 SP6 domain B) user credentials. ... afterwards) - but not to any of the member servers which are a mixture ...
    (microsoft.public.win2000.security)
  • Re: Flat domain to start off?
    ... site can operate independantly if one of the WAN connections were to go ... Moving computers is quite simple if you do need to do that in the future. ... control the DCs that your client computers authenticate against to ... But I suspect since you are using a single NT4 domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: Flat domain to start off?
    ... site can operate independantly if one of the WAN connections were to go down. ... Moving computers is quite simple if you do need to do that in the future. ... control the DCs that your client computers authenticate against to prevent ... But I suspect since you are using a single NT4 domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: Retrieving DC list
    ... I don't have NT4 DC's in my domain, but there is a quick way to check. ... Using something like ADSI Edit ... In "Configuration Container", ... >> Microsoft MVP Scripting and ADSI ...
    (microsoft.public.scripting.vbscript)
  • Re: Remote WMI scripting problems
    ... Microsoft MVP Scripting and ADSI ... Hilltop Lab - http://www.rlmueller.net ... You cannot connect to computers running XP Home. ...
    (microsoft.public.windows.server.scripting)