Microsoft maakt niet alleen hele mooie software, we hebben ook een team met top-consultants dat implementaties van die software bij klanten doet. Een belangrijke reden hiervoor is dat we op die manier Best Practices kunnen verzamelen en publiceren over hoe je het beste onze software kunt deployen. Zo zijn we ook tot onderstaande lijst gekomen voor Exchange 2010. Let wel: het is een lijst met tips & tricks, er kunnen geen rechten aan ontleend worden!
1.
In a multi-domain forest with
Exchange objects in multiple domains, make sure domainprep has been run with E2010
SP1 or later to ensure that individual SP1 or SP2 server installs in that
domain work (i.e. all domains prepped with RTM need to be updated by running SP1
or SP2 domainprep. The root domain is auto-updated when prepareschema and
preparead are run. Any domains prepped by using RTM need to be re-prepped with
SP1 or SP2).
You can check by looking at the objectVersion property on the Microsoft
Exchange System Objects (MESO) container under DC=<domain name> using
ADSIEdit. This objectVersion property contains the version of domain
preparation. The version for Exchange 2010 RTM is 12640. The version for
Exchange 2010 SP1 and SP2 is 13040.
2.
If a Hub Transport server role
installs but the Edgesync service will not start after the install (you will
also see 1045 events for example in the Application log for MSExchange
Edgesync), then please check through ADSIEdit if the AD site object in which
the hub transport server was installed has a child container called
CN=EdgeSyncService. (Alternatively run Get-EdgeSyncServiceConfig. The site should NOT be listed in the output). Most probably the AD
container is missing (cf. below screenshot):
It can be (re-)created by running: New-EdgeSyncServiceConfig –site
<AD site name with Exchange 2010 HT server(s) in it>. Cf. below
screenshot:
The
Edgesync service should start now. It is set to Started and Automatic by
default and needs to be running even though Edgesync may not be utilized within
the environment. You need to be an Organization Administrator to run
New-EdgeSyncServiceConfig.
3.
Do not forget to create a
routing group connector when deploying 2010 in a new site if that site also has
2003 deployed. That will make sure email is routed directly from local 2003 to
local 2010, preferably with multiple 2003 and 2010 source and target bridgehead
servers listed (if available).
4.
Installing SP2 on a CAS server
requires that the “IIS6
WMI Compatibility” component is installed. This will be installed by default
when doing new server installs using SP2 and will be installed when running the SP2 upgrade from the command line using: Setup
/m:upgrade /installwindowscomponents.
However, when installing SP2 using the
GUI, make sure you installed the IIS6 WMI Compatibility component manually through Server Manager before
starting setup or it will fail (cf. below screenshot):
5.
Internet Explorer 9 installs
and EMC not closing. There was a bug where on a computer that has Windows
Internet Explorer 9 installed, you start the Exchange Management Console (EMC).
After you make a change and then try to close the EMC window, the window does
not close. Additionally, you receive the following message: You must close all
dialog boxes before you can close Exchange Management Console. However, you
cannot find any open dialog boxes for the Exchange Management Console.
In order to fix this you need to install http://support.microsoft.com/kb/2618444
(this one hotfix replaces two earlier hotfixes that were released to fix this
issue).