Microsoft Server OS
--
Questions
--
Followers
Top Experts
AD inventarisation tool
Hi!
Would by thankfull for tips about tools for Actove Directory inventarisation.
We have a domain containing mainly Server 2000 and 2003. About 800 servers. The domain would be demolished as new domain has been set up and migration of users and mailing system was performed. Now we are at stage where we will have to take a closer look at what we've got left in old domain and what dependencies are still existing there.
We need a good tool (the cheaper the better) that can give us a picture of:
1.Trust topology
2. WINS
3. DNS
4. What is installed on the servers (server rolles, systems, services)
Would by thankfull for tips about tools for Actove Directory inventarisation.
We have a domain containing mainly Server 2000 and 2003. About 800 servers. The domain would be demolished as new domain has been set up and migration of users and mailing system was performed. Now we are at stage where we will have to take a closer look at what we've got left in old domain and what dependencies are still existing there.
We need a good tool (the cheaper the better) that can give us a picture of:
1.Trust topology
2. WINS
3. DNS
4. What is installed on the servers (server rolles, systems, services)
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Would you consider investigating a bit of scripting to perform the inventory rather than a pre-built tool?
Chris
Chris-Dent,
yes we can consider that too.
yes we can consider that too.
Then I would grab PowerShell from here:
http://www.microsoft.com/windowsserver2003/technologies/management/powershell/default.mspx
And the Quest add-in from here:
http://www.quest.com/powershell/activeroles-server.aspx
Both are free, the second will simplify many things.
Single domain? Or Forest?
Chris
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
we have forest.
I will take a look at PowerShell. Not shure we can manage PowerShell good enough but it worth trying.
I will take a look at PowerShell. Not shure we can manage PowerShell good enough but it worth trying.
I had intended to help you along in that respect :)
I have much of 3 already. 1 is moderately easy depending on how far you would extend that. 4 is time-consuming, but not especially hard. And 2 is part of 4 because there's no real hierarchy in WINS to bother about, it's either there or not.
Chris
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Chris-Dent:
Thank you so much, Chris! Your help appreciated. We continue to look at available options. We'll see what the project manager thinks about PowerShell solution. :) You've given us a new way to think anyway.
Thank you so much, Chris! Your help appreciated. We continue to look at available options. We'll see what the project manager thinks about PowerShell solution. :) You've given us a new way to think anyway.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Hi Chris! Thanx for youe help!
Microsoft Server OS
--
Questions
--
Followers
Top Experts
The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.