I'm installing a second server on the network that will be running SQL 2000. Since there are only two servers, I want to set it up as a domain server so the global catalog is backed up to this server from the primary server, along with the AD. When I was done congfiguring the second domain server, somehow I connected the two with regards to the AD because I could not access the AD info on my primary server unless the secondary server was online. Also, they now share the same Admin account. I'm demoting the SQL server and will try again, but what did I do wrong?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
What did I do wrong?
- Thread starter alexs0628
- Start date
Are you sure you did something wrong? They should both have the same admin account "Domain Admin". DC's do not have Local Admin accounts. You will probably find that your AD MMC is pointed at the other DC, or they have not completely replicated yet.
- Thread starter
- #3
But why couldn't I access the AD information on my primary DC if the second domain controller is not running? That means I can't work on it and work on the other server at the same time. The second server is not ready to be active yet and I don't want to lose administrative functions on the primary DC while the second DC is being tested. The second DC will be configured for SQL 2000, which hasn't been installed yet. A contractor is doing that work since I don't know anything about SQL. Should SQL 2000 be installed first before promoting the server from a member to a domain server?
- Status
Similar threads
- Locked
- Question
- Locked
- Question
