Home > Exchange, Microsoft, Windows Server > Exchange 2007 SP1 (CAS, Hub, Mailbox roles and Tools) tips on Windows Server 2008

Exchange 2007 SP1 (CAS, Hub, Mailbox roles and Tools) tips on Windows Server 2008

Now then, I’m not going to describe here how to install or setup a Windows Server 2008 box with Exchange 2007 SP1. I presume that you already have Windows Server 2008 with Exchange 2007 SP1 running in your organization, maybe even multiple. I just want to go over few things you might need to double check, before saying that your Exchange 2007 SP1 box is ready for a public use. Specially if you are using multiple CAS, HUB, Mailbox servers in your organization and all of them are operating separately. Right, first thing you need to do is Disable IPv6 on your Windows Server 2008 box (as there is no fix for this yet). IPv6 loopback is not listening port 6004. Here’s how you can turn it off:

* Open the Network Connections window and select the network adapter that you are currently using and under properties unselect IPv6 protocol.
* Now open your hosts file which is located in %systemroot%\system32\drivers\etc\ folder:

Look for this line:

::1 localhost

and change it to this:

# ::1 localhost

Also add there your Exchange server HOSTNAME and FQDN. So the hosts file should look like this:

192.168.1.10 exch1.domain.local
192.168.1.10 EXCH1
127.0.0.1 localhost
# ::1 localhost

* The last thing you should do, is edit your registry and disable the IPv6 there. Go down to:

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters

and add a 32-bit D-WORD with the name DisabledComponents, and give it a value ff. It is possible you may need to reboot your server after this.

After this is done, confirm that you have Exchange 2007 SP1 installed with CAS, HUB, Mailbox roles plus the Tools. If you have not yet you might want to install RPC over HTTP. You can do this with the following command: ServerManagerCmd -i RPC-over-HTTP-proxy. If you got several Active Directory sites in your organization and you are not relying on Exchange 2007 to pick the closest Domain Controller, there is a way you can manually force them to use local site DC’s. Here What you need to do:

* Open your regedit on Exchange server and add under:

HKLM\SYSTEM\CurrentControlSet\Services\MSExchangeSA\Parameters\

new multi string value (REG_MULTI_SZ) called NSPI Target Server. Inside it write down your local site Domain Controller(s). Next thing you need to do is go down to your Domain Controller(s) and open up the registry go down to:

HKLM\SYSTEM\CurrentControlSet\Services\NTDS\Parameters\

and add the following new multi string value (REG_MULTI_SZ) called NSPI Interface protocol sequences. Inside it write this: ncacn_http:6004, after this is done reboot your Domain Controller(s) and Exchange server.

Now it is time to enable Outlook Anywhere: Enable-OutlookAnywhere -Server exch1.domain.local -DefaultAuthenticationMethod:Basic -SSLOffloading:$false

Next we are going to verify CAS services URLs. First lets verify which URLs we currently are using. Outlook 2007 has a built-in tool for that. It is called Test E-mail Autoconfiguration. We can access it by opening the Outlook 2007 client, holding down the Ctrl key and right-clicking on the Outlook icon located on the systray. In the tool uncheck Use Guessmart and Secure Guessmart Authentication and click on Test. Then we will receive all the current URLs set up for Outlook 2007 clients they are shown on 2 sections:

First is Exchange RPC (internal):

Availability Service: https://exch1.domain.local/EWS/Exchange.asmx
OOF URL: https://exch1.domain.local/EWS/Exchange.asmx
OAB URL: https://exch1.domain.local/OAB/2c00976e-35c9-4e1b-b5bf-5oc2d07de8es
UM URL: https://exch1.domain.local/UnifiedMessaging/Service.asmx

Second is Exchange HTTP (external). Now these URLs might be missing or wrong and these are the ones we will go over:

Availability Service: https://domain.com/EWS/Exchange.asmx
OOF URL: https://domain.com/EWS/Exchange.asmx
OAB URL: https://domain.com/OAB/2c00976e-35c9-4e1b-b5bf-5oc2d07de8es
UM URL: https://domain.com/UnifiedMessaging/Service.asmx

First lets check the autodiscover URL (internal). To see the current URL use the following command:

Get-ClientAccessServer EXCH1 | Select Name, *Internal* | fl

Now if the URL is not what you want it to be use this command to change it:

Set-ClientAccessServer –Identity EXCH1 –AutoDiscoverServiceInternalUri ”https://exch1.domain.local/Autodiscover/Autodiscover.xml”

Now the OAB internal URL:

Get-OABVirtualDirectory –server EXCH1 | Select Name, Identity, *Internal* | fl

Set the new OAB internal URL:

Set-OABVirtualDirectory -Identity “EXCH1\OAB (Default Web Site)” –InternalURL “https://exch1.domain.local/OAB”

And add the external URL as well:

Get-OABVirtualDirectory –server EXCH1 | Select Name, Identity, *External* | fl

Set-OABVirtualDirectory -Identity “EXCH1\OAB (Default Web Site)” –ExternalURL “https://domain.com/OAB”

Next lets go over the web services external URL (as Internal should be ok):

Get-WebServicesVirtualDirectory | Select Name, Identity, *url* | fl

And to add or change it:

Set-WebServicesVirtualDirectory –Identity EXCH1\EWS (Default Web Site)” –ExternalUrl: https://domain.com/EWS/Exchange.asmx

Just in case restart IIS7 (iisreset /noforce) and to confirm that the new URLs are working run the Test E-mail Autoconfiguration tool again.

Now publish your Exchange (if you haven’t already done this) by creating rules in your ISA 2006 SP1 server and you are good to go.

-Eric

Advertisements
  1. June 26, 2013 at 7:40 pm

    I really like your blog.. very nice colors & theme. Did you make this website yourself or did you hire
    someone to do it for you? Plz respond as I’m looking to construct my own blog and would like to know where u got this from. thanks a lot

    • July 8, 2013 at 9:34 pm

      no its running on wordpress, and im just using a skin.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: