Migrating to Windows Server 2008
(Page 1 of 4 )
Migrating a server operating system is somewhat trickier than installing an update or patch to run-of-the-mill software. This article is the second part of our multi-part series focusing on the migration to Windows Server 2008. The first part covered the preliminary basics and glanced at the business factors and other considerations that it implied. This part will focus on performing the actual migration.
Per the previous article, we are assuming the following: we already have a primary domain controller that manages all of the FSMO roles, and even has other server roles like DHCP and DNS. This server is running Windows Server 2000/2003 and we want to upgrade it to Windows Server 2008. We want the new server to take over its server roles.
We can do this by installing the new server running Windows Server 2008 individually and transfer each of the roles one by one, configure the services, and promoting the server into the position of primary domain controller, while simultaneously demoting the already-existing Windows Server 2000/2003 to the status of backup domain controller (BDC/RODC). This is a wise choice, because we will still have our old server that can act as a back up.
But we can also upgrade the old server running Windows Server 2000/2003 to the new operating system. This means that the old server is going to be technically replaced by the new Windows Server 2008. In this case, the IP address and host name remain the same. And the old server must be demoted and removed from the domain.
In the first segment we covered the necessary considerations regarding the staging process and discussed the virtual lab (virtualization). Along with these recommendations, the first route is highly advised. Why? Because if the migration fails, then you can promote the old server once again, re-transfer the FSMO roles, and it's going to be lock and loaded-up and running just like it was before. This is much safer.
Now let's cover the actual technical aspects of how to accomplish the entire migration.
Next: Migration Steps: AD, DNS >>
More BrainDump Articles
More By Barzan "Tony" Antal