You missed a line sir: This server is the only server at this remote location and acts as a file server, DHCP server and domain controller.
Carl Webster Consultant and Citrix Technology Professional http://www.CarlWebster.com<http://www.carlwebster.com/> From: Andrew S. Baker [mailto:[email protected]] Sent: Tuesday, November 22, 2011 8:53 AM To: NT System Admin Issues Subject: Re: Bringing a Win2K3 server back online It's just a member server. You should have no issues with bringing it back online. Just be sure to rejoin the domain. -ASB: http://about.me/Andrew.S.Baker Sent from my Motorola Droid On Nov 22, 2011 9:32 AM, "Bob Hartung" <[email protected]<mailto:[email protected]>> wrote: We had a file server at a remote location suffer corruption from a software install gone bad. The server would appear to be booting normally, making it to the Windows 2003 splash screen with the progress indicator. Unfortunately, the screen would then go black and the system would reboot. The same thing would happen trying to boot in Safe Mode and Last Known Good Configuration. This server is the only server at this remote location and acts as a file server, DHCP server and domain controller. This server and PCs at this location are in their own subnet (172.17.x.x) but is a member of our single AD domain. The subnet at my location is 172.16.x.x. Since this location doesn't have an IT person on staff, it was decided they'd ship to server back to me so I could restore it from a tape backup. When I received the server, I decided I'd start by trying a Repair Install. It couldn't hurt since I was eventually planning on a restore from tape anyway. At this point, the server has been offline for about a week. The Repair Install actually seems to have worked. The system came up with its normal desktop background but then stopped before loading the desktop icons with a requirement to activate the operating system. I did that and the desktop came up. I have not hooked the server up to the network here yet. After all that, here's my question. Will I cause a lot of AD problems if I assign this server a 172.16.x.x IP address and bring it up and let it sync up with our domain? I want to make sure it's functioning properly. Also, I've never done a Repair Install before. Does a Repair Install change things to a system that need to be manually reconfigured? Any advice would be appreciated. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
