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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Rebooting 2003 Server with AD

Status
Not open for further replies.

cmeshore

Technical User
Feb 17, 2004
6
US
Question,

new to 2003 Server and AD

I have a 2003 server running AD as the Primary domain controller. We have had a request from one of our departemtns to reboot the 2003 Server to clear up a problem with a service running on the server.

Question: Can the Server be rebooted with my users on the system and it still allow them to work with no problems? I know that users will not be able to login while it is reboots but other than that is they any reason I should not reboot the server?

This server is the PDC, DNS Server, and DHCP

Thanks in advance for any help on this question
 
While it is rebooting, your users will not be able to authenticate at all. That means they won't be able to access shared resources that require AD authentication. If you have a single domain controller, it most likely holds your DNS and DHCP. The bigger problem here would be the DNS. I would wait until after hours to reboot. Have your tried stopping and starting the service that is causing the problem?
 
No such thing as a PDC in Windows Server 2003.

You should have at least two domain controllers, each configured as a global catalog

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
If you reboot the server during production hours and it's the only DNS server, you're users will have issues resolving addresses. Probably won't be a huge deal for LAN resolution, as each client should have a DNS cache. No authentication will take place. No addresses will be released to workstations.

Like 58sniper said, you should have at least 2 DC's for redundancy and situations like this. Have you thought about what you would do if your DC were to cease functioning? There's a good chance you'll be dusting off your resume and looking through help wanted ads. [neutral]

With that being said, wait til after hours. Then, plan to deploy another DC in the near future.

I hope you find this post helpful,

Jonathan Almquist
Minneapolis, MN
 
you should have at least 2 DC's for redundancy and situations like this. Have you thought about what you would do if your DC were to cease functioning? There's a good chance you'll be dusting off your resume and looking through help wanted ads.

I would go as far as saying if your company doesn't want to invest in a second DC, I'd be dusting off the resume and looking though help wanted ads.

Pat Richard, MCSE MCSA:Messaging CNA
Microsoft Exchange MVP
Want to know how email works? Read for yourself -
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top