I know what you are saying but didn't want to go too deep into the whole process. Was just posting a possible solution. As to infrastructure Thats going to be my next exam which I'm not looking forward to.
The clue was in the post - moving HDD. The disk numbering will be screwed, hence making boot.ini invalid. Wouldn't be the ntldr/ntdetect files missing, as it boots in one machine.
Obviously, shouldn't move disks like that, as all the wrong drivers, and if done properly (unlikely given the circumstances we know) the chipset drivers will cause a boot failure later in the boot sequence, once the kernel mode driver loads.
Infratsructure is pretty easy if you understand TCP/IP and assocaited technologies, esp DNS (which is dead easy, esp with Microsoft's half baked implementation). Just the AD part to worry about. IIRC, FSMOs aren't part of it, but GCs are, as is replication/ntfrs/sites and service/rdns. Not sure if WINs is in the 2003 one - it was in 2000 one. DHCP/DNS/Kerberos/PKI etc are all standard Internet stuff, and should be easy for anyone working in the industry.
Good luck with exam
