Hank,
It can be. I have used it before in a test lab in a WIN2000 SP4 environment
( there we go again with the SP4!!!! ). However, with some of the tools
there is a limited functionality issue. I have not yet run the new ds tools
in a WIN2003 AD environment so I can not really tell you what tools have
what limited functionality. A possible way around this ( or, at least to
minimize the 'limited functionality' issue ) is to update the Schema in your
WIN2000 AD. You do this by running adprep. Several people have done this
in a WIN2000 AD environment without issue. However, if you are running
Exchange 2000 then you might want to look into the 'mangled attributes'
issue and take the corrective action ( all detailed in the MSKB article ).
How did I do this? - I simply took the five ds* files, extracted them and
then placed each .exe in the \winnt folder ( or was that the \winnt\system32
folder - do not think that it matters! ). Each location is in the default
path so just go to a command prompt and enter ds******.
One thing that you can do if you do not want to mess with all of this is use
ldifde. I have to say that I am still a big fan of ldifde. However, I must
add that the new ds* tools are really the way to go. I have just started
playing with them and they are really neat.
Anyway, if you wanted to use ldifde ( which is native to WIN2000 ) you would
simply enter the following at a command prompt:
c:\>ldifde -f computersplevel.ldf -s yourdc.yourdomain.com -t 389 -d
"DC=yourdomain,DC=com" -p subtree -r
"(&(objectCategory=computers)(objectClass=user))" -l
"DN,sAMAccountName,operatingSystem,operatingSystemVersion,operatingSystemSer
vicePack"
Naturally, you could also run csvde and then import that into a nice Excel
Spreadsheet....your choice.
HTH,
Cary
Hank Arnold said:
Jerold,
You keep referring to tips that use DSQUERY. From the web pages, it seems to
indicate that this is a Server 2003 program. Can it be used on earlier
versions (say 2000 server)? If so, how do we get it?