ITschoolGuy
Instructor
Hello -
I have been tasked with installing a new 64-bit Windows Server 2008 file server in a small, single server network. The existing server is running 32-bit Server 2003 and is configured as a DC. It is showing signs of an imminent failure so it needs to be replaced ASAP.
While I have a good general understanding of what's involved, I'm pretty weak on the specifics. Nevertheless, it has to be done and there is no one else in the company to do it. I'm hoping one of the experts here can assist me with a bit of troubleshooting or, at least, guidance as to how best to complete this task.
Here is what I've done so far: I setup the new Server 2008 box on the LAN and assigned static IPs to both its Ethernet interfaces (only one of which is going to be used - I disabled the other). On the existing Server 2003 machine, I made sure the domain functional level was bumped up to the 2003 level (as opposed to Windows 2000 native). Then, using the adprep32 tool from the Server 2008 DVD, I did the forestprep and domainprep. Then I went to the new Server 2008 machine and added it to the domain, making sure DNS and DHCP services were installed and enabled. I ran dcpromo on the 2008 box to make it a DC. Then, using the AD Schema snap-in in MMC, I tried to set the new server as the domain controller (this initially failed but, then, it seemed to work). Then I transferred the FSMO roles to the new server...which didn't work either initially but, after waiting a while and trying again, it seemed to. I also checked in the Sites and Services console to make sure the new server was shown as a GC. Finally, I grabbed the DHCP scope from the old server and copied it to the new one.
I ran into some snags along the way - for example, I had to manually configure the interface binding before my DCHP would work. Also, the DNS forward lookup zone didn't come over to the new server right away - it took a while.
Anyway, as of right now, everything functions normally as long as the old 2003 server is up and running. If I take it offline (either by shutting down or disconnecting it from the LAN) I run into trouble - client PCs can't logon and the various management consoles on the new server (DNS, AD Users & Computers, AD Sites & Services, etc.) won't work because they indicate that the domain can't be found.
I went into DNS and placed checkmarks in the boxes for "allow zone transfers" but that didn't seem to do any good. I also tried forcing replication from the NTDS Settings in the AD Sites & Services console - also to no avail.
HEEEEELLLLPPPPPP!!! Sorry for "yelling" in all caps but I am pulling my hair out!
Does anyone have any idea what I might have missed?
Any assistance would be greatly appreciated.
Thanks.
Chris
I have been tasked with installing a new 64-bit Windows Server 2008 file server in a small, single server network. The existing server is running 32-bit Server 2003 and is configured as a DC. It is showing signs of an imminent failure so it needs to be replaced ASAP.
While I have a good general understanding of what's involved, I'm pretty weak on the specifics. Nevertheless, it has to be done and there is no one else in the company to do it. I'm hoping one of the experts here can assist me with a bit of troubleshooting or, at least, guidance as to how best to complete this task.
Here is what I've done so far: I setup the new Server 2008 box on the LAN and assigned static IPs to both its Ethernet interfaces (only one of which is going to be used - I disabled the other). On the existing Server 2003 machine, I made sure the domain functional level was bumped up to the 2003 level (as opposed to Windows 2000 native). Then, using the adprep32 tool from the Server 2008 DVD, I did the forestprep and domainprep. Then I went to the new Server 2008 machine and added it to the domain, making sure DNS and DHCP services were installed and enabled. I ran dcpromo on the 2008 box to make it a DC. Then, using the AD Schema snap-in in MMC, I tried to set the new server as the domain controller (this initially failed but, then, it seemed to work). Then I transferred the FSMO roles to the new server...which didn't work either initially but, after waiting a while and trying again, it seemed to. I also checked in the Sites and Services console to make sure the new server was shown as a GC. Finally, I grabbed the DHCP scope from the old server and copied it to the new one.
I ran into some snags along the way - for example, I had to manually configure the interface binding before my DCHP would work. Also, the DNS forward lookup zone didn't come over to the new server right away - it took a while.
Anyway, as of right now, everything functions normally as long as the old 2003 server is up and running. If I take it offline (either by shutting down or disconnecting it from the LAN) I run into trouble - client PCs can't logon and the various management consoles on the new server (DNS, AD Users & Computers, AD Sites & Services, etc.) won't work because they indicate that the domain can't be found.
I went into DNS and placed checkmarks in the boxes for "allow zone transfers" but that didn't seem to do any good. I also tried forcing replication from the NTDS Settings in the AD Sites & Services console - also to no avail.
HEEEEELLLLPPPPPP!!! Sorry for "yelling" in all caps but I am pulling my hair out!
Does anyone have any idea what I might have missed?
Any assistance would be greatly appreciated.
Thanks.
Chris