Kemp released Exchange 2010 Templates witch makes configure a Kemp Loadmaster easier
Core services: MAPI, SMTP and Unified HTTP/HTTPS
Extended services: Per-service HTTP/HTTPS
Additional Services: POP, IMAP and SMTP
Ward 06-07-2012: Fixed Links
Exchange Team released the newest version of the Exchange 2010 language pack and that it is available for download here.
This language pack resolves three key issues some customers have experienced;
Note that Exchange 2010 Service Pack 2 included the full language pack, and if you are not experiencing the problems or have not installed any language packs post SP2 you do not need to apply this language
When you do a import or export request using the New-MailboxExportRequest or New-MailboxImportRequest CMDlet in Exchange 2010. It gave me an error.
Unable to open PST file ‘\\Server\Exports\Test.pst’. Error details: Access to the path ‘\\ExServer1\Imports\Test1.pst’ is denied.;
Microsoft.Exchange.MailboxReplicationService.RemotePermanentException: Access to the path ‘\\Server\Exports\Test.pst’ is denied.
The Mailbox Replication Server (MRS) is running as LocalSystem it can’t access a network share. By adding the Exchange Trusted Subsystem group to the share permissions you will give the LocalSystem account and therefore MRS access to the share.
Sometimes we want to minimize the time required to move all the current mailboxes available on Exchange 2003 / 2007 to Exchange 2010, and for configuring your Exchange 2010 to process high number of mailboxes move simultaneously, we need to change the default configuration, which described as follows:
1. Go to all Exchange 2010 CAS Servers, open the below file in notepad or any file editor:
X:\Program Files\Microsoft\Exchange Server\V1\Bin\MSExchangeMailboxReplication.exe.config
2. Change the below values:
MaxActiveMovesPerSourceMDB = “25″
MaxActiveMovesPerTargetMDB = “25″
MaxActiveMovesPerTargetServer = “25″
3. Save the file and restart the “Microsoft Exchange Replication” service.
The Exchange CXP team released Update Rollup 7 for Exchange Server 2007 SP3
This update contains a number of customer-reported and internally found issues since the release of SP3 RU6. See KB2655203: Description of Update Rollup 7 for Exchange Server 2007 Service Pack 3 for more details.
Note: Some of the following KB articles may not be available at the time of publishing this post.
The most important fixes:
Note that this fix will resolve the CAS to CAS OWA proxying incompatibility with Exchange 2010 SP2 RU1 as discussed here.
Support lifecycle statement: This is the final release under standard support for Exchange 2007, as the Exchange 2007 Mainstream Support has now ended. Extended Support for Exchange 2007 SP3 will end on 4/11/2017
Note for Forefront Protection for Exchange users:
Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.
The Exchange CXP team released Update Rollup 2 for Exchange Server 2010 SP2.
This update contains a number of customer-reported and internally found issues since the release of SP2 RU1. See KB2661854: Description of Update Rollup 2 for Exchange Server 2010 Service Pack 2 for more details.
Note: Some of the following KB articles may not be available at the time of publishing this post.
The most important fixes:
Note that this fix will not cause the CAS to CAS OWA proxying incompatibility with Exchange 2007 as discussed here. No additional updates are required on Exchange 2007 for proxying to work once Exchange 2010 SP2 RU2 is installed.
Note for Forefront Protection for Exchange users:
Before installing the update, disable ForeFront by using this command: fscutility /disable. After installing the update, re-enable ForeFront by running fscutility /enable.
Microsoft released November 2010 a great document: Publishing Exchange Server 2010 with Forefront Unified Access Gateway 2010 and Forefront Threat Management Gateway 2010.
One thing that I misted in that document: What is the best way to migrate PDA’s or Tablets from a legacy version of Exchange to Exchange 2010.
In most cases you wil use TMG als a firewall. Between the Internet and your internal Network.
Some weeks ago I did a Exchange 2010 migration en I don’t wanted a big bang scenario.
But I had the all the sort of phone’s that are on the marked today (Iphone, Android, Windows Phone 7.5 and some Windows Mobile phones and all so Ipad’s)
The First thing what is asked my self when design the new infrastructure.
Domain Joining Forefront TMG or Leaving in a Workgroup
In most organizations, the decision whether to domain join the server hosting Forefront TMG your production domain may be one of the most important parts of the deployment.
Forefront TMG deployments are more complex to discuss because Forefront TMG is considered a firewall and can protect the network edge. Domain joining Forefront TMG offers many advantages: it allows certificate based authentication to be used at Forefront TMG, using Kerberos Constrained Delegation to communicate to Exchange; it allows easy use of Active Directory groups and user objects in publishing rules to restrict access; and it provides other benefits. If your are not sure to domain join Forefront TMG, see Debunking the Myth that the ISA Firewall Should Not be a Domain Member.
I thinks that the best practice is to domain join TMG. Because is makes your live a lot easier.
First I created a Exchange 2010 group in the Active Directory.
Second you make the Exchange 2010 group available in TMG
Third you make four rules 2 for Exchange 2010 (OWA & ActiveSync) and 2 for your legacy server of servers (OWA & ActiveSync)
Fourth makes sure that the Exchange 2010 rules are above the legacy rules.
Fith: You change on the Exchange 2010 rules the all authenticated users to Exchange 2010. (After the migration you delete the legacy rules and change on the 2010 rules the Exchange 2010 back to all authenticated users).
Sixth: When you do a mailbox move you puth the user in de Exchange 2010 group.
Why you thing. When the user is in the Exchange 2010 group the PDA wil use the Exchange 2010 rule. When there user is not in the Exchange 2010 group the legacy rule will do the trick.
I migrated at this way about 300 users with random pda’s and tablets with no downtime at all 
Screenshot from the TMG rules.
At first you need to create a casarray on Exchange 2010 Server or Servers.
Configuring Client Access Array for Exchange 2010
If you want more info about Casarray and how it works read: Exploring Exchange 2010 RPC Client Access service & Demystifying the CAS Array Object – Part 1 & Demystifying the CAS Array Object – Part 2
Second: Configure Virtual Directories
Set Exchange 2010 Virtual Directories
Third: You set static RPC ports on your Client Access Server
Exchange 2010: Setting Static RPC ports when using a Kemp LoadMaster
Fourth: you register in DNS your casarray name and autodiscover name on a new “virtual” IP address.
Fifth: You configure the Kemp loadbalacers as descriptind in: LoadMaster Deployment Guide for MS Exchange 2010 with the new “virtual” IP address.
When you are done you have 6 Virtual Services 
When a hardware load balancer based CAS array has been properly configured, all servers in the array are represented by a single virtual IP (VIP) address and a fully qualified domain name (FQDN). When a client request comes in, it will be sent to an Exchange 2010 CAS server in the CAS array using DNS round robin distribution method.
With the following following powershell commands you set al the Exchange 2010 virtual directories
Set-ClientAccessServer -Identity ward-ex2010 -AutoDiscoverServiceInternalUri https://casarray.hyperv.local/Autodiscover/Autodiscover.xml
Set-WebServicesVirtualDirectory -Identity "ward-ex2010\EWS (Default Web Site)"-ExternalUrl "https://webmail.wardvissers.nl/ews/exchange.asmx" -InternalUrl "https://casarray.hyperv.local/ews/exchange.asmx"
Set-OABVirtualDirectory -Identity "ward-ex2010\oab (Default Web Site)" -InternalUrl http://casarray.hyperv.local/oab -ExternalUrl https://webmail.wardvissers.nl/oab
Enable-OutlookAnywhere -Server ward-ex2010 -ExternalHostname "webmail.wardvissers.nl" -ClientAuthenticationMethod "Basic" -SSLOffloading:$False
Set-ActiveSyncVirtualDirectory -Identity "ward-ex2010\Microsoft-Server-ActiveSync (Default Web Site)" -InternalURL https://casarray.hyperv.local/Microsoft-Server-Activesync -ExternalURL https://webmail.wardvissers.nl/Microsoft-Server-Activesync
Set-ECPVirtualDirectory –Identity "ward-ex2010\ecp (default web site)" -InternalURL https://casarray.hyperv.local/ECP -ExternalURL https://webmail.wardvissers.nl/ECP
Set-AutodiscoverVirtualDirectory "ward-ex2010\Autodiscover (Default Web Site)" -InternalUrl http:/casarray.hyperv.local -ExternalUrl https://autodiscover.nifv.nl
Today Microsoft released a fix (KB2677598) for a small cosmetic imperfection which shows up when using Outlook Web Access in Dutch, after installing Service Pack 2 on Exchange 2010.
Instead of showing up “Mail”, OWA displayed “Globale Adreslijst” (Global Addresslist) which might be confusing to end users.
To need to download the Microsoft Exchange Server 2010 SP2 Language Pack Bundle which released on 20 Feb 2012 and install on your Exchange 2010 SP2 Client Access Servers.
You can download the Microsoft Exchange Server 2010 SP2 Language Pack Bundle (219 MB) here.
Special thanks for Jetze for notice the update