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

-->

Phase 3 :- Installation of Windows Exchange server standard 2007 SP1 & Move Mailbox, Installtion/Transfer of Commercial Certificate

A/ Install Exchange Pre-requisites and IIS

Install IIS Role from Go to Start > “Server Manager àFutures Roleà Install IIS role and Please make sure you install IIS 6.0 management compatibility, IIS6 Metabase Compatibility, Digest Authentication, Dynamic content compression à Restart the server.

Install Exchange Server Prerequisite

à Windows ServerPowerShell Management Tool

à.NET Framework 2 OR 3.5 (**Install this first .net 1.1
sp1, .net 2)

à MMC

àExchangeBPA,

àExchange2007-KB970162-x64-EN

And all the updates from AWD “BBN-Migration Utility” folder on AWD nas\pub

B/ Prepare Current Exchange Server 2003 Std environment to install and Transfer Mailbox to Exchange server 2007 Std.

Step 1:

Raise the Microsoft Exchange Server Operational Level From Mixed Level to Native Mode

On the Old Exchange server Open Exchange Server manager à R/C on “First Organisation (Exchange)” à Properties à Change the Operational Level From Mixed Level to Native Mode

Export (*.p12b) certificate from Old Exchange server with full certificate path and private key.

Step 2: Prepare Current Exchange server 2003 to transfer all records and schemas to new Exchange server 2007:-

Prepare AD and Domain Schema For Installing Exchange Server 2007 / 2010.

Run this command by pointing CMD to Exchange Server CD

1 / Setup.com /PrepareLegacyExchangePermissions

2/ Setup.com /PrepareSchema

3/ Setup.com /PrepareAD

4/ Setup.com /PrepareDomain

5/ Setup.com /PrepareAllDomains

c/ Install Exchange server 2007 SP1 Std.

Copy All Files and Folders from Exchange Server CD to the Local Hard Drive.

àR/C on Setup.exeà Compatibility TAB à Select “Run this program in Compatibility mode for Windows server 2008”)

(If you are installing Exchange Server 2010 run the Setup.exe Directly Without running compatibility Mode)

àR/C on EXCHANGESERVER.exe àCompatibility TAB à Select “Run this program in Compatibility mode for any Windows Previous Version.”

Ø Once Exchange Server is installed successfully check the Mail Box, Distribution list (Mailboxes Should be available in Legacy Mode)

Ø Check Recipients Connector to send and Receive Email’s.

d/ Change Mailbox size limit In Order to Start Moving Mail box from old to new server

àMEMC(Microsoft Exchange Management Console) àOrganisation Configurationà HUB Transport à Global Settings à Transport Settings à Properties and Change the Mailbox Size limit for Send and Receive.

Transfer Mailbox from old exchange server store to new exchange server store.

àMEMC(Microsoft Exchange Management Console) àRecipient Configuration à Mail Box à select the Mailbox you want to transfer to new store.

(Please do 4 Mailbox transfer at a time this task can take up to 18 to 23hrs)

e/ Install Commercial Certificate

Install Old server commercial certificate (*.p12b)

Ø On the new server

Start à mmc à Add snap in à Select Certificates à Select service for this computer à Select for this computer à ok.

Expand Certificates à Click on Intermediate Certificate à R/C Import à Select (*.p12b) certificate à Follow the wizard steps and finish the process.

Open IIS Management console à select IIS (Server Name)à on right pane click on “Server Certificates” à on the extreme right pane select Import à Select (*.p12b) certificate à Follow the wizard steps and finish the process.

f/ Change Client Access URL in order to take affect Commercial Certificate

Run the following command on Exchange server Mgt Console.

The following commands are for the single Exchange Server 2007 scenario

#holding the MBX, CA, HT roles

#Check the SCP details (Autodiscover Uri):

Get-ClientAccessServer | FL

#Set the new URI for SCP

Get-ClientAccessServer | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://mail.kbc.com.au/Autodiscover/Autodiscover.xml

#Check the Web Services URL:

Get-WebServicesVirtualDirectory | FL

#Set the new URL for Web Services:

Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https:///EWS/Exchange.asmx -ExternalUrl https:///EWS/Exchange.asmx

#List Certificates in local store:

Get-ExchangeCertificate

Check and make sure you can see your Commercial Cetificate

#Asign an existing Certificate of Exchange Services:

Enable-ExchangeCertificate

Check the IPWS role attached to which Certificate and for taking role to your Commercial certificate run this command on the prompt:

Enable-ExchangeCertificate{Thumb Print of your Commercial certificate} Press Enter

When prompted please press “A” to yes to all role transfer from old to new Commercial certificate

Note / Troubleshooting : à Check the client computers of the domain for Outlook, it should pointing to new server. If not, please restart the client systems, that will do the change. It is good Idea to change/Move DNS, and DHCP services to new server. Also check the Exchange server to

MEMC(Microsoft Exchange Management Console) àOrganisation Configuration à Mailbox à on the right hand pane please select you server name à R/C Properties à System Settings and check à Active directory servers à Domain controller servers being used by Exchange server à should be your new server.

Also at the same place please check à Global Catalogue servers being used by Exchange server à should be your new server.

Please note that It will only take your new server as Active directory and Global catalogue server if your server has a Global catalogue server.

If your server is a Global Catalogue server and still having problem in this part (It is most probably It’s IPv6 problem that is not configured), Please go to command prompt and ping the server check

#ipconfig /all

Disable IPv6 on the server and restart the server and check it again.

1. Go to Network Connections folder (click on Start button, then right click on Network, select Properties, then click on “Manager Network Connections” on Tasks pane).
2. You should see various LAN, wireless, Bluetooth, high speed Internet, and other network connections available on the Vista computer with the network adapter description. Right click on the network connection that you want to disable the IPv6 interface and select “Properties”.

Click “Continue” on User Access Control permission request prompt.

3. Clear the check box next to the Internet Protocol version 6 (TCP/IPv6) component in the list under “This connection uses the following items” box.

-->

1. Click OK when done.
2. To re-enable IPv6, tick back the check box.

This method disables IPv6 on the particular LAN interface and connection. For other network adapter or connection, users have to repeat the steps to disable IPv6. Beside, disable IPv6 also does not disable IPv6 on tunnel interfaces or the IPv6 loopback interface.

It’s also possible to disable IPv6 and/or Teredo via Vista system registry. The registry settings also allow users to selectively disable components and configure behaviors for IPv6 in Windows Vista.

1. Open Registry editor (regedit).
2. Navigate to the following registry key branch:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
Services\tcpip6\Parameters\

3. Create the following registry value (DWORD type):

DisabledComponents

Note that the name must be exactly as shown, including capitalization. DisabledComponents is set to 0 by default.

4. The DisabledComponents registry value is a bit mask that controls the following series of flags, starting with the low order bit (Bit 0). To determine the value of DisabledComponents for a specific set of bits, the process is complicated, were hexadecimal value is calculated from binary number of the bits in correct position. For convenient, the following table lists some common configuration combinations and the corresponding DWORD value of DisabledComponents.

Configuration combination	DisabledComponents value
Disable all tunnel interfaces	0×1
Disable 6to4	0×2
Disable ISATAP	0×4
Disable Teredo	0×8
Disable Teredo and 6to4	0xA
Disable all LAN and PPP interfaces	0×10
Disable all LAN, PPP, and tunnel interfaces	0×11
Prefer IPv4 over IPv6	0×20
Disable IPv6 over all interfaces and prefer IPv4 to IPv6	0xFF

5. As seen from table above, to disable IPv6 support globally on all interface, set the value data for DisabledComponents to 000000FF, or simply FF. The registry entry will look like below:
6. 
   
   [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters]
   
   "DisabledComponents"=dword:000000ff
7. Restart the computer for changes to take effect.
8. To revert and enable IPv6, delete “DisabledComponents” registry key or set its registry value to 0.