Windows Server - moving to windows server 2008 r2 from 2003 r2

Asked By Aussie Rules
20-Nov-09 05:19 AM
Hi,

Currently we have a windows 2003 r2 server which is our domain controller.

We want to move to Win Server 2008 R2, and this will be on a new machine.

Is it possible to introduce the windows 2008R2 machine into the current
domain, and configure it as a backup domain contoller, the promote it, which
would de-mote the 2003 R2, so that we can then just turn off the 2003 R2
server, and all the domain users and other stuff would be the same in the
new 2008 domain, as the old 2003 domain ???

Thanks
SQL Server
(1)
Exchange Server 2007
(1)
PDCEmulator
(1)
Database
(1)
Exchnage
(1)
Domainhierarchie
(1)
Manualpeerlist
(1)
Syncfromflags
(1)
  Meinolf Weber [MVP-DS] replied to Aussie Rules
20-Nov-09 08:35 AM
Hello Aussie,

Yes, you can do it that way. See here for some details:

!!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!

- Do you use any kind of Exchange in the 2003 domain? If yes, which one?

- On the old server open DNS management console and check that you are running
Active directory integrated zone (easier for replication, if you have more
then one DNS server)

- run replmon from the run line or repadmin /showrepl(only if more then one
DC exist), dcdiag and netdiag from the command prompt on the old machine
to check for errors, if you have some post the complete output from the command
here or solve them first. For this tools you have to install the support\tools\suptools.msi
from the 2003 installation disk.

- run adprep /forestprep and adprep /domainprep and adprep /rodcprep from
the 2008 installation disk against the 2003 schema master(forestprep) / infrastructure
master(domainprep/rodcprep), with an account that is member of the Schema/Enterprise/Domain
admins, to upgrade the schema to the new version (44) or 2008 R2 (47)

- you can check the schema version with "schupgr" or "dsquery * cn=schema,cn=configuration,dc=domainname,dc=local
-scope base -attr objectVersion" without the quotes in a command prompt

- Install the new machine as a member server in your existing domain

- configure a fixed ip and set the preferred DNS server to the old DNS server
only, think about disabling IPv6 if you are not using it, some known problems
exist with it. Follow (http://blogs.dirteam.com/blogs/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-2008.aspx)
to disable it

- run dcpromo and follow the wizard to add the 2008 server to an existing
domain, make it also Global catalog and DNS server.

- for DNS give the server time for replication, at least 15 minutes. Because
you use Active directory integrated zones it will automatically replicate
the zones to the new server. Open DNS management console to check that they
appear

- if the new machine is domain controller and DNS server run again replmon,
dcdiag and netdiag (copy the netdiag from the 2003 to 2008, will work) on
both domain controllers

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801
applies also for 2008), FSMO should always be on the newest OS DC

- after transfer of the PDCEmulator role, configure the NEW PDCEmulator to
an external timesource and reconfigure the old PDCEmulator to use the domainhierarchie
now. Therefore run on the NEW "w32tm /config /manualpeerlist:PEERS /syncfromflags:manual
/reliable:yes /update" where PEERS will be filled with the ip address or
server(time.windows.com) and on the OLD one run "w32tm /config /syncfromflags:domhier
/reliable:no /update" and stop/start the time service on the old one. All
commands run in an elevated command prompt without the quotes.

- you can see in the event viewer (Directory service) that the roles are
transferred, also give it some time

- reconfigure the DNS configuration on your NIC of the 2008 server, preferred
DNS itself, secondary the old one

- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server

- if needed export and import of DHCP database for 2008 choose "netshell
dhcp backup" and "netshell dhcp restore" command (http://technet.microsoft.com/en-us/library/cc772372.aspx)



Demoting the old DC (keep in mind that you should always have at least 2
DC/DNS/GC per domain)

- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC

- to be sure that everything runs fine, disconnect the old DC from the network
and check with clients and servers the connectivity, logon and also with
one client a restart to see that everything is ok

- then run dcpromo to demote the old DC, if it works fine the machine will
move from the DC's OU to the computers container, where you can delete it
by hand. Can be that you got an error during demoting at the beginning, then
uncheck the Global catalog on that DC and try again

- check the DNS management console, that all entries from the machine are
disappeared or delete them by hand if the machine is off the network for ever

- also you have to start AD sites and services and delete the old servername
under the site, this will not be done during demotion

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
  Aussie Rules replied to Meinolf Weber [MVP-DS]
24-Nov-09 04:24 PM
Hi Thanks for your response.

No there is no exchange 2003 in my domain, its just a domain we use for our
development work, so most of the data is either in visual source safe or on
a network attached device. The OS itself has only got SQL Server, which on
the new machine 08 we will install sql server 2008 and move our sql 05 db
accross before shutting down the old 03 server.

There currently is just one DC in the domain, so should be straight forward
based on your great comments below.

Watch this space,if I have any issues I will be posting them!!!

Again, thanks!!
  Naresh Reddy replied to Meinolf Weber [MVP-DS]
27-Nov-09 12:31 AM
Hello Meinolf Weber.

Even my Scenarion is same as Aussie, But we use Exchange Server 2007 in our
environment. Will the above process affect Exchnage Server 2007 ( Which is on
another computer).

Do i need to perform any additional steps.

Please advice..

Waiting for your reply.

Regards,
Naresh
Create New Account
help
Backup: 2003 Server, Exchange, SQL, Oracle RAC Windows Server Hi! I'm looking for backup solution which allows to backup and restore windows 2003 server, MS SQL (whole database and one table), Exchange (whole exchange database and specific email) and Oracle RAC (with RMAN). The application I'm looking for
SQL Server 2000 and Exchange Server 2003 on the same cluster Windows Server Hello! Can anybody tell me if Microsoft supports mixing SQL Server 2000 and Exchange Server 2003 on the same cluster? Does anybody know if there are any published guidelines
How to diagnose? Windows Server We're running SBS2003 with Exchange, SQL Server and ISA Server. I cannot make it in to the office for a couple days. I am trying I can connect to the VPN just fine and access files that are on the server. SQL Server is accessible as well. Exchange is not working. We are receiving no emails. We can
SBS Server solution Windows Server I have an SBS 2003 Premium server. It is approximately 3 years old. There are under 20 users accessing the server. The server is running ISA server, exchange server and SQL server. The SQL application performance is ok The exchange performance is ok. The
SQL Server on SBS Windows Server http: / / www.microsoft.com / technet / prodtechnol / sql / 2000 / maintain / sp3sec04.mspx and http: / / technet.microsoft.com / en-us / library / ms143719.aspx says NEVER install SQL Server on a Domain Controller. . . . So SQL server should be run on a member server in SBS environment?? This is not a problem