Monday, 22 March 2010

Upgrade/Migration/Transtioning AD/Exchange 2003 Std to Ad/Exchange 2008 Ent. x64 Part II

Phase2 - Installation of New Server (AD, Exchange, Mail box Move)

Installation of new server and Transfer FSMO roles

A/ Install New Windows Server Enterprise 2008

B/ Make new Windows Server Enterprise 2008 a member server/Additional domain controller

Go to Start >Server manager >click on roles >click on Add roles > select AD domain services > will prompt you for .NET 3.5 installation > click on add requirements > click next and wait for installation to finish.

Roles>AD domain services >Run active directory installation wizard > click next >click “Existin
g forest” “Add a domain controller to an existing forest” > click next > check the domain name > make sure you have checked “my current logged on credential” > If it prompts for not able to install read-only domain controller in this domain click on YES to continue > continue with default and finish the installation.

(**Check the AD, DNS are there and all up to date)

C/ Make New Server a Global Catalogue for AD

To make New server a Global Catalouge à AD Sites and Servces à Default first Site name à Servers à Select the New server Expand à NTDS Settings à Properties Tick on Global Catlouge.

D/ Extend Active Directory Schema Version :-

To check current schema version

à Start à Run à regedit à

HKEY_Local_Machine\Systems\currentcontrolset\services\NTDS\Parameters

Click on “Schema Version” it should be 41 or 47.

E/ Transfer Fsmo role from Old server to new server :-

To demote Old server and transfer all roles to make new server as Primary Domain Controller and Global Catalogue.

First point all the Additional Domain controllers to the new Server for secondary DNS Server. To perform this steps please change the secondary IP Address in Network properties on all Additional domain controller.

Now perform/Run the following commands on the new server in order to transfer all FSMO role to new server.

è Start à Run à cmd Type

è #ntdsutil (press Enter you will see ntdsutil: as a command prompt)

è #ntdsutil: roles

è #fsmo maintenance:?

è #fsmo maintenance: connections

è #server connections:?

è #server connections: connect to domain domainname.local {check it should Bind and Connected to New Server}

è #server connections: connect to server {It should notify us by “Connected to server using locally logon credentials}

è #Quit

è #fsmo maintenance:?

è #fsmo maintenance: Transfer infrastructure master {When it’s prompted to to transfer the role to new server please click on “Yes”}

è #fsmo maintenance: Transfer naming master

è #fsmo maintenance: Transfer PDC

è #fsmo maintenance: Transfer RID master

è #fsmo maintenance: Transfer Schema master

Now new Windows Server 2008 DC is holding all master roles.

To check if new server is primary server type the following command:

#Net accounts

(Check whether server is Primary or backup, new server should be Primary now.)

Open support tools command prompt and check FSMO role.

Startà All programs àWindows support toolsàCommand prompt

# netdom query fsmo

Check all following 5 roles to make sure it is primary DC:

1 Infrastructure Master Role

2 Naming Master Role

3 PDC Master Role

4 RID

5 Schema master

All 5 Roles should be with New server

No comments:

ISM Cyber Security Terms

ISM Cyber Security Terms