I did not directly deployed the above mentioned in production but rather in the Lab.
(I took an image of my exisiting Domain controllers and exchange 2003 servers from production and prepared a lab for the same on a different hardware using Symantec Live state recovery V 7.0 )
So, Here it goes....
How to Upgrade exisiting Windows server 2003 R2 Domain Controllers to Windows Server 2008 ?
My Set up has a Primary domain Controller and Addition Domain Controller, In place Upgrade of domain controllers is not recommended.
1) Install a fresh server with WS 2008
2) Make it as a Additional Domain Controller to the exisiting DC.
3) Prior Step (2), Upgrade the schema version of the existing DC by inserting Windows 2008 CD and running following commands from the command prompt.
i)Adprep /Forestprep ii)Adprep /domainprep iii)Adprep /gpprep
***Adprep tool can be located in Windows 2008 CD in Sources Directory.***
4)Now log on to newly installed windows server 2008, In server manager add the role of Active directory services, and let the wizard finish by clicking Next as it comes.
5) Run DCPROMO from the Run Command and follow the steps to finish.
6)Reboot your server and windows 2008 is a part of your Domain as Additional Domain Controller.
Transfering FSMO roles from exisiting DC (WS 2003R2 ) to ADC ( WS 2008 )
Five Roles need to be transferred which are as follows.
i)Schema Master
ii)Domain Naming Master
iii)RID
iv)PDC
v)Infrastructure
Transfer the Schema Master role
Transfer the Schema Master Role
Use the Active Directory Schema Master snap-in to transfer the schema master role. Before you can use this snap-in, you must register the Schmmgmt.dll file.
Register Schmmgmt.dll
1. Click Start, and then click Run.
2. Type regsvr32 schmmgmt.dll in the Open box, and then click OK.
3. Click OK when you receive the message that the operation succeeded.
Transfer the Schema Master Role
1. Click Start, click Run, type mmc in the Open box, and then click OK.
2. On the File, menu click Add/Remove Snap-in.
3. Click Add.
4. Click Active Directory Schema, click Add, click Close, and then click OK.
5. In the console tree, right-click Active Directory Schema, and then click Change Domain Controller.
6. Click Specify Name, type the name of the domain controller that will be the new role holder, and then click OK.
7. In the console tree, right-click Active Directory Schema, and then click Operations Master.
8. Click Change.
9. Click OK to confirm that you want to transfer the role, and then click Close.
Transfer the Domain Naming Master Role
1. Click Start, point to Administrative Tools, and then click Active Directory Domains and Trusts.
2. Right-click Active Directory Domains and Trusts, and then click Connect to Domain Controller.
NOTE: You must perform this step if you are not on the domain controller to which you want to transfer the role. You do not have to perform this step if you are already connected to the domain controller whose role you want to transfer.
3. Do one of the following: • In the Enter the name of another domain controller box, type the name of the domain controller that will be the new role holder, and then click OK.
-or-
• In the Or, select an available domain controller list, click the domain controller that will be the new role holder, and then click OK.
4. In the console tree, right-click Active Directory Domains and Trusts, and then click Operations Master.
5. Click Change.
6. Click OK to confirm that you want to transfer the role, and then click Close.
Transfer the RID Master, PDC Emulator, and Infrastructure Master Roles
1. Click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
2. Right-click Active Directory Users and Computers, and then click Connect to Domain Controller.
NOTE: You must perform this step if you are not on the domain controller to which you want to transfer the role. You do not have to perform this step if you are already connected to the domain controller whose role you want to transfer.
3. Do one of the following: • In the Enter the name of another domain controller box, type the name of the domain controller that will be the new role holder, and then click OK.
-or-
• In the Or, select an available domain controller list, click the domain controller that will be the new role holder, and then click OK.
4. In the console tree, right-click Active Directory Users and Computers, point to All Tasks, and then click Operations Master.
5. Click the appropriate tab for the role that you want to transfer (RID, PDC, or Infrastructure), and then click Change.
6. Click OK to confirm that you want to transfer the role, and then click Close.
Now Time to remove the Demote DC from domain, By default after a period of time all SRV records gets deleted from DNS or manually they need to be deleted.
Else, use NTDSUTIL and run metadata cleanup to remove the demoted DC from domain.
Installing Exchange 2007SP1 on Windows 2008 server.
Pre-requisites like Power shell is included by default on WS 2008 but not installed, DotNetFramework is installed by default.
Run the following command from the command line to install PowerShell
ServerMangerCmd -i PowerShell
Pre-requisites to run on WS 2008 prior Installing Exchange Roles ( In My scenario all roles are on single server )
If you are deploying a new Exchange organization, and you are preparing your Active Directory schema and domain(s) by using a computer running Windows Server 2008, you must first install the Active Directory Domain Services remote management tools on Windows Server 2008 prior to preparing the schema or a domain by using the following command:
ServerManagerCmd -i RSAT-ADDS
This command is a must prior installing any IIS web components for Server Roles
Note:You may need to restart the computer after installing the Active Directory Domain Services remote management tools. You will be notified at the end of the installation process if a system restart is required.
To install the Windows Server 2008 operating system prerequisites for a computer that will host the Hub Transport, Client Access, and Mailbox server roles
1.Open a Command Prompt window.
2.Install Windows PowerShell, which is included in Windows Server 2008 (but not installed by default) by running the following command:
ServerManagerCmd -i PowerShell ( Ignore if already you have run this command )
3.Install the necessary IIS prerequisites by running the following commands in the order in which they are listed:
ServerManagerCmd -i Web-Server
ServerManagerCmd -i Web-ISAPI-Ext
ServerManagerCmd -i Web-Metabase
ServerManagerCmd -i Web-Lgcy-Mgmt-Console
ServerManagerCmd -i Web-Basic-Auth
ServerManagerCmd -i Web-Digest-Auth
ServerManagerCmd -i Web-Windows-Auth
ServerManagerCmd -i Web-Dyn-Compression
4.If the server will support Outlook Anywhere clients, install the RPC over HTTP proxy feature by running the following command:
ServerManagerCmd -i RPC-over-HTTP-proxy
Insert Exchange 2007 CD (follow the images for rest of installation).
By default two RGC's are created during installation one in First Administrative group of Exchange 2007 SP1 and another in Exchange 2003, As per new concept of Exchange 2007 no more of routing group connectors in use, reason for the above mentioned RGC's is for sake of co-existance of Exchange 2007 with Exchange 2003.
I faced a problem in this case, My scenario as in production is we have a SMTP server in the DMZ, And already there exist a Routing Group Connector ( SMTP ), Along with this connector Installation of Exchange 2007SP1 created two default RGC's.All usermailboxes migration goes fine but any user exisiting in Legacy server cannot send an email to any migrated user in Exchange 2007 Database.
I read lot of forums,articles and blogs,but in vain, Finally one of the blogs has same scenario, suggestion was to delete the existing SMTP(For Legacy serer to communicate with SMTP)connector,and also the default RGC created by Exchange 2007 installation and recreate another SMTP RGC with smarthost as Exchange 2007 Server.Restart Information store and SMTP service to activate the connector.
Also, Public folder flow went susccesful after this attempt, which was always a major problem for me.
I will elaborate more in future on this topic...............
