Exchange 2003

Migration From Exchange 2003 to Exchange 2010 on Windows Server 2008 R2

Prerequisites:

  • Existing Exchange 2007 Servers must have SP2 installed.
  • Existing Exchange 2003 Servers must have SP2 installed.
  • Exchange Organization is set to Native Mode.
  • At least one Global Catalog in each AD site must be Server 2003 with SP2.
  • Active Directory Forest Functionality must be at least Windows Server 2003.
  • Exchange 2010 cannot be installed on a RODC.
  • Verify the existing Exchange 2003 Server does not have a SMTP Smart Host configured.
  • Verify network with Exchange Pre-Deployment Analyzer.
  • Possible Got Ya’s: Exchange 2010 requires client encryption and Outlook 2003 slow to delete email messages.

Required Software:

  • From PowerShell on the server where Exchange will be installed.
  • Set-ExecutionPolicy RemoteSigned – This will allow PowerShell scripts created on the server to be run on the server.
  • Import-Module servermanager
  • Save the command below to a .PS1 file extension. (Command below needs to be on a single line)
  • add-WindowsFeature Net-Framework,RSAT-ADDS,Web-Server,WEB-ISAPI-Ext,Web-Metabase,Web-Lgcy-Mgmt-Console,Web-Basic-Auth,Web-Digest-Auth,Web-Windows-Auth,Web-Dyn-Compression,NET-HTTP-Activation,RPC-over-HTTP-Proxy -Restart
  • Change to the directory of the PowerShell script you just created.
  • Enter .\SriptName.ps1
  • After the Reboot, configure Net.TCP port sharing service.  Enter – Set-Service NetTcpPortSharing -StartupType Automatic

(continue reading…)


Active Sync Setup on Single Exchange 2003 Server with OWA SSL Enabled

http://support.microsoft.com/kb/817379

 

Disable the forms-based authentication for the Exchange virtual directory

To create a secondary virtual directory for Exchange that is based on steps 1 through 7 of the following procedure, make sure that forms-based authentication is disabled for the Exchange virtual directory before you make the copy. Before you follow these steps, disable forms-based authentication in Exchange System Manager. Then restart Internet Information Services (IIS). To do this, follow these steps:

  1. Open Exchange Manager.
  2. Expand Administrative Groups, expand the first administrative group, and then expand Servers.
  3. Expand the server container for the Exchange Server 2003 server that you will be configuring, expand Protocols, and then expand HTTP.
  4. Under the HTTP container, right-click the Exchange Virtual Server container, and then click Properties.
  5. Click the Settings tab, clear the Enable Forms Based Authentication check box, and then click OK.
  6. Close Exchange Manager.
  7. Click Start, click Run, type IISRESET/NOFORCE, and then press ENTER to restart Internet Information Services (IIS).

Create a secondary virtual directory for Exchange server

You must use Internet IIS Manager to create this virtual directory for Exchange ActiveSync and Outlook Mobile Access to work. If you are using Windows Server 2003, follow these steps:

  1. Start Internet Information Services (IIS) Manager.
  2. Locate the Exchange virtual directory. The default location is as follows:

    Web Sites\Default Web Site\Exchange

  3. Right-click the Exchange virtual directory, click All Tasks, and then click Save Configuration to a File.
  4. In the File name box, type a name. For example, type ExchangeVDir. Click OK.
  5. Right-click the root of this Web site. Typically, this is Default Web Site. Click New, and then click Virtual Directory (from file).
  6. In the Import Configuration dialog box, click Browse, locate the file that you created in step 4, click Open, and then click Read File.
  7. Under Select a configuration to import , click Exchange, and then click OK.
    A dialog box will appear that states that the "virtual directory already exists."
  8. Select the Create a new virtual directory option. In the Alias box, type a name for the new virtual directory that you want Exchange ActiveSync and Outlook Mobile Access to use. For example, type exchange-oma. Click OK.
  9. Right-click the new virtual directory. In this example, click exchange-oma. Click Properties.
  10. Click the Directory Security tab.
  11. Under Authentication and access control, click Edit.
  12. Make sure that only the following authentication methods are enabled, and then click OK:
    • Integrated Windows authentication
    • Basic authentication
  13. On the Directory Security tab, under IP address and domain name restrictions, click Edit.
  14. Click the option for Denied access, click Add, click Single computer and type the IP address of the server that you are configuring, and then click OK twice.
  15. Under Secure communications, click Edit. Make sure that Require secure channel (SSL) is not enabled, and then click OK.
  16. Click OK, and then close the IIS Manager.
  17. Click Start, click Run, type regedit, and then click OK.
  18. Locate the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MasSync\Parameters

  19. Right-click Parameters, click to New, and then click String Value.
  20. Type ExchangeVDir, and then press ENTER. Right-click ExchangeVDir, and then click Modify.
    NoteExchangeVDir is case-sensitive. If you do not type ExchangeVDir exactly as it appears in this article, ActiveSync does not find the key when it locates the exchange-oma folder.
  21. In the Value data box, type the name of the new virtual directory that you created in step 8. For example, type /exchange-oma. Click OK.
  22. Quit Registry Editor.
  23. Restart the IIS Admin service. To do this, follow these steps:
    1. Click Start, click Run, type services.msc, and then click OK.
    2. In the list of services, right-click IIS Admin service, and then click Restart.
  24. If you want to reuse Forms-based Authentication on the Exchange server, follow these steps to re-enable Forms-based Authentication on the /Exchange virtual directory in Exchange System Manager.
    1. Open Exchange Manager.
    2. Expand Administrative Groups, expand the first administrative group, and then expand Servers.
    3. Expand the server container for the Exchange Server 2003 server that you will be configuring, expand Protocols, and then expand HTTP.
    4. Under the HTTP container, right-click the Exchange Virtual Server container, and then click Properties.
    5. Click the Settings tab, click to select the Enable Forms Based Authentication check box, and then click OK.
    6. Close Exchange Manager.
    7. Click Start, click Run, type IISRESET/NOFORCE, and then press ENTER to restart Internet Information Services (IIS).

Note If the server is Microsoft Windows Small Business Server 2003 (SBS), the name of the Exchange OMA virtual directory must be exchange-oma.
The integrated setup of Microsoft Windows Small Business Server 2003 creates the exchange-oma virtual directory in IIS. Additionally, it points the ExchangeVDir registry key to /exchange-oma during the initial installation. Other SBS wizards, such as the Configure E-mail and Internet Connection Wizard (CEICW) also expect the virtual directory name in IIS to be exchange-oma.


Migration From Exchange 2000/2003 to Exchange 2007 on Windows Server 2003

Prerequisites:

  • Exchange Org must be set to “Native Mode” no pre-Exchange 2000 servers.
  • Exchange 2000 servers must be at Service Pack 3.
  • Exchange 2003 servers must be at Service Pack 2.
  • Active Directory Schema Master must be a Windows 2003 DC with Service Pack 1.
  • At least one Global Catalog in each site, where an Exchange 2007 Server will reside, must be Windows 2003 with Service Pack 1.
  • Active Directory Domain Functional Level must set to Windows Server 2000 or Windows Server 2003.
  • Verify the existing Exchange 2000/2003 Server does not have a SMTP Smart Host configured.
  • Run Exchange Best Practices Analyzer (ExBPA) to verify installation requirements.

Required Software:

  • MS .NET Framework 2.0 or 3.0
  • MMC 3.0
  • Windows PowerShell 1.0
    • Required Windows Components:
      • Mailbox Server
        • Enable network COM+ access
        • IIS Service
        • WWW Service
      • Client Access Server
        • WWW Service
        • RPC over HTTP
        • ASP .NET v2.0
      • Hub Transport Server
        • SMTP and NNTP must NOT be installed

(continue reading…)


Enable Auto IMF Updates

After you enable the Intelligent Message Filter in Exchange System Manager, to enable Intelligent Message Filter updates, you must create the ContentFilterState registry entry. To do this, follow these steps:

 

1.Click Start, click Run, type regedit, and then click OK.

2.Expand the following registry subkey:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange

3.In the left pane, click Exchange. Then, right-click in the right pane, point to New, and then click DWORD Value.

4.Type ContentFilterState, and then press ENTER to name the new registry entry.

5.Right-click ContentFilterState, and then click Modify.

6.In the Data value box, type 1, and then click OK.

7.Quit Registry Editor.

8.In the Services snap-in, restart the Simple Mail Transfer Protocol (SMTP) service.

 

By default, when the Intelligent Message Filter is installed together with Exchange Server 2003 SP2, a new folder that is named MSCFV2 is created. The Intelligent Message Filter engine and the .dat file are stored in the following location:

Drive_Letter:\Program Files\Exchsvr\Bin\MSCFV2


Increase The Default SP2 Database Size of 18GB

Open the registry on the Exchange 2003 server go to this key:

For Private Information Store – HKLM\System\CurrentControlSet\Services\MSExchangeIS\(Server Name)\Private-{GUID}

For Public Information Store – HDLM\System\CurrentControlSet\Services\MSExchangeIS\(Server Name)\Public-{GUID}

 

Under the database, create the following registry information:

Value Type: REG_DWORD

Value Name: Database Size Limit in GB

Enter a Decimal Value -  For the Standard Edition of Exchange, you can enter numbers between 1 and 75. For the Enterprise Edition, you can enter numbers between 1 and 8000.

 

Use Exchange System Manager and Dismount the Private or Public Store in order for the changes to be applied.


Exchange Server ESM Schema Removal

Use ADSI Edit to remove the old Exchange Server from the Active Directory Schema.

Go to Configuration Container – Config DC – Services – Microsoft Exchange – “Org Name” – Administrative Group – First Administrative Group – Servers – “Server Name”


  • Archives

  • Copyright © 1996-2010 My-Technet. All rights reserved.
    iDream theme by Templates Next | Powered by WordPress
    WordPress Appliance - Powered by TurnKey Linux