• Deploying Lync Jump Start (01): Features and Architecture of Microsoft Lync Server 2010
• Deploying Lync Jump Start (02a): Deploying Microsoft Lync Server 2010 | Part 1
• Deploying Lync Jump Start (02b): Deploying Microsoft Lync Server 2010 | Part 2
• Deploying Lync Jump Start (03): Configuring Users and Rights for Microsoft Lync Server 2010
• Deploying Lync Jump Start (04a): External User Access Microsoft Lync Server 2010 | Part 1
• Deploying Lync Jump Start (04b): External User Access Microsoft Lync Server 2010 | Part 2
• Deploying Lync Jump Start (05a): Configuring Basic Enterprise Voice Functionality Microsoft Lync Server 2010 | Part 1
• Deploying Lync Jump Start (05b): Configuring Basic Enterprise Voice Functionality Microsoft Lync Server 2010 | Part 2
• Deploying Lync Jump Start (6a): Extending Enterprise Voice Functionality Microsoft Lync Server 2010 | Part 1
• Deploying Lync Jump Start (6b): Microsoft Exchange Server 2010 SP1/Unified Messaging Integration | Part 2
• Deploying Lync Jump Start (7a): Implementing Response Groups in Microsoft Lync Server 2010
• Deploying Lync Jump Start (7b): Real-world IVR Scenarios with Microsoft Lync Server 2010
• Deploying Lync Jump Start (8): Conferencing with Microsoft Lync Server 2010
• Deploying Lync Jump Start (9): Monitoring Microsoft Lync Server 2010
• Deploying Lync Jump Start (10): Compliance and Archiving with Microsoft Lync Server 2010
• Deploying Lync Jump Start (11): High Availability and Disaster Recovery in Microsoft Lync Server 2010
• Deploying Lync Jump Start (12): Call Admission Control with Microsoft Lync Server 2010
• Deploying Lync Jump Start (13): Deploying and Configuring Enhanced 9-1-1 with Microsoft Lync Server 2010

I have used these VMs with the VMware Tools from the TechPreview.

As soon as I try to install and configure the Active Director Domain Services, the VM needs to reboot. Once it has rebooted, it goes in a blank screen, and there is nothing I can do. Workstation thinks the VM is running, but there is no response via the GUI in the VM, no response to ping traffic to the VM or RDP.

Solution:
Downgrade from Workstation TP2012 hardware to Workstation 8 hardware and to select Windows 2008 R2 as the guest OS

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.

Start the DPM Management Shell

PS> get-dpmdisk –dpmservername WARD-DPM01

Name Status NtDiskIdty Total Capaci Unallocated Space Type
—- —— ——– ———— ———— —-
VMware Vir… Healthy 1 150 GB 28 GB Basic #0
VMware Vir… Healthy 2 250 GB 100 GB Basic #1

Read the disk order in to a variable ($disk)

PS > $disk = Get-DPMDisk -DPMServername ward-dpm01

Now you can use the script MigrateDatasourceDataFromDPM.ps1. First find the disk number of the source disk, these numbers are not displayed when you use the get-dpmdisk command. Do not get fooled by the NTdiskID, you do not need those. You just need to count the disks listed starting with 0 (see red numbers in example). Now find the number for the destination disk using the same trick.
In the example below we like to migrate the data from disk 2 to disk 1

PS > ./MigrateDatasourceDataFromDPM.ps1 -DPMServerName ward-dpm01 -Source $disk[2] -Destination $disk[1]

More options and examples can be found on Technet

Check them out:

Cookbook: Installing a Virtual LoadMaster (VLM)

Cookbook: High Availability: From a Single to a HA System

Cookbook: Finetuning the LoadMaster in 10 simple steps

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:

• KB2617514 Include updated version of Portuguese-Brazil speller.
• KB2696649 Exchange 2007sp3/2010 OWA CSRF via Cookie Tossing.
• KB2696628 Read Receipt is still duplicated when connecting IMAP.

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.

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:

• KB2696913 You cannot log on to Outlook Web App when a proxy is set up in an Exchange Server 2010 environment
• KB2688667 High CPU in W3WP when processing recurrence items who fall on DST cutover
• KB2592398 PR_INTERNET_MESSAGE_ID is the same on messages resent by Outlook
• KB2630808 EwsAllowMacOutlook Setting Not Honored
• KB2661277 Android/Iphones stuck with 451 during Cross forest proxy in datacenter
• KB2678414 Contact name doesn’t display company if name fields are left blank

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.

In contains numerous bug fixes as well as support for SCCM 2007 and SCCM 2012.

Improvements for All MDT Technologies

The MDT improvements that affect all MDT technologies, which are discussed in a subsequent section, are as follows:

• Support for upgrading from previous versions of MDT
• Integration with security and compliance templates generated by Microsoft Security Compliance Manager (SCM) version 2.0
• Run Windows PowerShell™ scripts within an MDT task sequence
• Create partitions to support best practice recommendations for deployment of BitLocker® Drive Encryption
• Automatically configure participation in the Windows Customer Experience Improvement Program (CEIP) and Windows Error Reporting (WER)
• Guidance that describes how to use Microsoft SQL Server® 2008 R2 with Service Pack 1 (SP1) for all database needs within MDT

Improvements for LTI Deployments

MDT includes the following improvements for LTI deployments:

• Support for Windows 8 Consumer Preview and Windows Server 8 Beta. Note: The deployment of Windows Server 8 Beta roles and features using the Install Roles and Features task sequence action is not supported.
• Support for the Windows Assessment and Deployment Kit (Windows ADK). Note: Currently, the Windows ADK is only supported for deploying Windows 8 Consumer Preview or Windows 7 in lab environments, not in production environments.

Windows ADK requires the Microsoft .NET Framework version 4.0. If not already installed, the Windows ADK installation installs the Microsoft .NET Framework version 4.0. For more information, see Introduction to the Windows Assessment and Deployment Kit.

• Monitoring of LTI deployment process. MDT includes the new LTI monitoring feature that allows you to perform centralized monitoring of LTI deployments in the Monitoring node in the Deployment Workbench.
• Deployment of Windows Recovery Environment (Windows RE). Windows RE helps users troubleshoot and recover from startup-related problems on their computers.
• Deployment of Microsoft Diagnostics and Recovery Toolkit (DaRT).
• Deployment to computers that use the Unified Extensible Firmware Interface (UEFI).
• Deployment to computers that require the new globally unique identifier (GUID) Partition Table (GPT) format.
• Deployment to virtual hard disks (VHDs) for native boot.
• Support for Windows Thin PC.
• Support for Windows Embedded POSReady 7.
• Add local administrator accounts.
• Deployment Wizard user experience improvements.

Improvements for Configuration Manager Deployments

MDT includes the following improvements for MDT deployments with Configuration Manager 2012 or Configuration Manager 2007 R3:

• Support for System Center 2012 Configuration Manager. MDT includes support for System Center 2012 Configuration Manager for ZTI and UDI deployments
• Support for new application model in Configuration Manager 2012.
• Support for the user device affinity feature in Configuration Manager 2012.
• Support for prestart command files.
• Support for automatically starting a specific task sequence.
• UDI Wizard user experience improvements.
• The UDI Wizard has been completely revised to improve user experience.
• UDI Wizard Designer user experience improvements.
• The UDI Wizard Designer UI has been improved to make configuring the UDI Wizard even easier than previous versions.
• Support for enabling BitLocker in UDI.
• Support for MDT Replace Computer deployment scenario.
• Localization of UDI Wizard.
• Guidance for customizing UDI.
• Upgrade tasks sequences created in Configuration Manager 2007 to Configuration Manager 2012.
• Guidance for Configuration Manager 2007 R3.

Read more and download it from here 

Special thanks to Mikael Nystrom

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.
 

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.

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

Here are screenshots from the new packages in SoftPaq Download Manager and from the HP support website.


Special Thanks to: Deploymentresearch

Now when you first install MDT 2012 RC1, you might notice that the items aren’t sorted right away – you have to change something in the folder first. As soon as you do (e.g. add an item, rename an item), the items in that folder will be sorted.

Keeping the list of folders sorted is a much bigger challenge, so at this point they will still show up in the order that they were added.

• Installation and operation of VMware Workstation on Windows 8 and Windows Server 8
• Installation and operation of Windows 8 consumer preview and Windows Server 8 in a virtual machine
• Rendering and graphics correctness issues on all platforms and applications
• Linux 3D desktop experience, particularly when using the Ubuntu 12.04 LTS Beta
• Linux 3D application graphics correctness and performance
• Stability in real-world scenarios including suspend/resume and display and device support
• Nested Virtualization – running ESX and even trying Hyper-V* as a guest OS
• VNC connection performance and stability

Download

Get-Mailbox -Database MB1 | Enable-Mailbox -Archive  -ArchiveDatabase MB3

This is very when you want to create a lot of archive mailboxes in one time

get-mailbox | where {$_.UseDatabaseQuotaDefaults -eq $False}

To Set al mailbox to Mailbox Database Default:

get-mailbox | where {$_.UseDatabaseQuotaDefaults -eq $False} | set-mailbox -UseDatabaseQuotaDefaults $true

To download just click the picture

The first is to configure all the network adapters of all VM’s from the old to the new VLAN/Portgroup and the second is to do exactly the same but to shortly disconnect/reconnect the network adapters of the Virtual Machines to initiate a DHCP request for your VM’s.

First method:

Get-Cluster "Your Cluster" | Get-VM | Get-NetworkAdapter | Where { $_.NetworkName -eq "Old VLAN" } | Set-NetworkAdapter -NetworkName "New VLAN" –Confirm:$false

Second method:

Get-Cluster "Your Cluster" | Get-VM | Get-NetworkAdapter | Where { $_.NetworkName -eq "Old VLAN" } | Set-NetworkAdapter -NetworkName "New VLAN" -Connected:$false | Set-NetworkAdapter -Connected:$True –Confirm:$falsen

When you use the second method the vm’s must be powered on!!!!!

Special thanks to: Laurensdekoning

Download the MDT 2012 RC1 release now

New features and enhancements:

Support for Configuration Manager 2012 RC2: This update provides support for Configuration Manager 2012 RC2 releases. MDT 2012 fully leverages the capabilities provided by Configuration Manager 2012 for OS deployment. The latest version of MDT offers new User-Driven Installation components and extensibility for Configuration Manager 2007 and 2012. Users now also have the ability to migrate MDT 2012 task sequences from Configuration Manager 2007 to Configuration Manager 2012.

Customize deployment questions: For System Center Configuration Manager customers, MDT 2012 provides an improved, extensible wizard and designer for customizing deployment questions.

Ease Lite Touch installation: The Microsoft Diagnostics and Recovery Toolkit (DaRT) is now integrated with Lite Touch Installation, providing remote control and diagnostics. New monitoring capabilities are available to check on the status of currently running deployments. LTI now has an improved deployment wizard user experience. Enhanced partitioning support ensures that deployments work regardless of the current structure.

Secure Deployments: MDT 2012 offers integration with the Microsoft Security Compliance Manager (SCM) tool to ensure a secure Windows deployment from the start.

Reliability and flexibility: Existing MDT users will find more reliability and flexibility with the many small enhancements and bug fixes and a smooth and simple upgrade process.

Support for Windows 8: The RC1 release of MDT 2012 provides support for deploying Windows 8 Consumer Preview in a lab environment.

Key Benefits:

• Full use of the capabilities provided by System Center Configuration Manager 2012 for OS deployment.
• Improved Lite Touch user experience and functionality.
• A smooth and simple upgrade process for all existing MDT users.

New Features:

For System Center Configuration Manager customers:

• Support for Configuration Manager 2012 (while still supporting Configuration Manager 2007)
• New User-Driven Installation components for Configuration Manager 2007 and Configuration Manager 2012
  • Extensible wizard and designer, additional integration with Configuration Manager to deliver a more customized OS experience, support for more imaging scenarios, and an enhanced end-user deployment experience
• Ability to migrate MDT 2012 task sequences from Configuration Manager 2007 to Configuration Manager 2012

For Lite Touch Installation:

• Integration with the Microsoft Diagnostics and Recovery Toolkit (DaRT) for remote control and diagnostics
• New monitoring capabilities to see the progress of currently running deployments
• Support for deploying Windows to computers using UEFIAbility to deploy Windows 7 so that the computer will start from a new VHD file, "Deploy to VHD"
• Improved deployment wizard user experience

For all customers:

• Integration with configuration templates from the Security Compliance Manager Solution Accelerator, ensuring Windows is secure from the start
• A simple mechanism for running Windows PowerShell scripts during a deployment, with task sequence environment and logging integration
• Better partitioning support, creating the recommended partitioning structures on new computers and ensuring deployments work regardless of the current structure
• A smooth and simple upgrade process for all existing MDT users
• Many small enhancements and bug fixes

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

The SP2 RU1 package introduced a change to the user context cookie which is used in CAS-to-CAS proxying. An unfortunate side-effect is a temporary incompatibility between SP2 RU1 servers and servers running earlier versions of Exchange. The change is such that earlier versions of Exchange do not understand the newer cookie used by the SP2 RU1 server. As a result, proxying from SP2 RU1 to an earlier version of Exchange will fail with the following error:

Invalid user context cookie found in proxy response

The server might show exceptions in the event log, such as the following:

Event ID: 4999
Log Name: Application
Source: MSExchange Common
Task Category: General
Level: Error
Description: Watson report about to be sent for process id: 744, with parameters: E12, c-RTL-AMD64, 14.02.0283.003, OWA, M.E.Clients.Owa, M.E.C.O.C.ProxyUtilities.UpdateProxyUserContextIdFromResponse, M.E.C.O.Core.OwaAsyncOperationException, 413, 14.02.0283.003.

Not all customers are affected by this. But since we received a few questions about this, we wanted to let you know about the change. Many Exchange customers do not use proxying between Exchange 2010 and Exchange 2007 but rather use redirection, which is not affected by the change. However, if you are using CAS-to-CAS proxying, where an Exchange 2010 SP2 RU1 Client Access server is proxying to an earlier version of Exchange 2010 or Exchange 2007 Client Access server, then you are affected by the change.

If you are affected, it is important to note that this issue is temporary and will exist only until all of the CAS involved in the CAS-to-CAS proxy process are updated to Exchange 2010 SP2 RU1. Thus, if you are affected by this problem, simply deploy SP2 RU1 on the relevant Exchange 2010 servers and the issue no longer exists.

If you use CAS-to-CAS proxy between Exchange 2010 and Exchange 2007, we will have an interim update (IU) for Exchange 2007. Availability of the IU will be announced on this blog.

Server proxy version
Server being proxied to
Action to take

Exchange 2010 SP2 RU1 –> Any version of Exchange 2010 older than SP2 RU1
Apply Exchange 2010 SP2 RU1 to all servers involved in proxy process

Exchange 2010 SP2 –-> RU1 Exchange 2007
Hold off deployment of Exchange 2010 SP2 RU1 until you deploy the Exchange 2007 interim update (IU)

SOURCE: Exchange 2010 sp2 ru1 and cas to cas proxy incompatibility

It’s a long list with issues that are fixed in this rollup:

• 2465015 You cannot view or download an image on a Windows Mobile-based device that is synchronized with an Exchange Server 2010 mailbox
• 2492066 An automatic reply message is still sent after you clear the "Allow automatic replies" check box for a remote domain on an Exchange Server 2010 server
• 2492082 An Outlook 2003 user cannot view the free/busy information of a resource mailbox in a mixed Exchange Server 2010 and Exchange Server 2007 environment
• 2543850 A GAL related client-only message rule does not take effect in Outlook in an Exchange Server 2010 environment
• 2545231 Users in a source forest cannot view the free/busy information of mailboxes in a target forest in an Exchange Server 2010 environment
• 2549255 A meeting item displays incorrectly as multiple all-day events when you synchronize a mobile device on an Exchange Server 2010 mailbox
• 2549286 Inline contents disposition is removed when you send a "Content-Disposition: inline" email message in an Exchange Server 2010 environment
• 2556113 It takes a long time for a user to download an OAB in an Exchange Server 2010 organization
• 2557323 Problems when viewing an Exchange Server 2003 user’s free/busy information in a mixed Exchange Server 2003 and Exchange Server 2010 environment
• 2563245 A user who has a linked mailbox cannot use a new profile to access another linked mailbox in an Exchange Server 2010 environment
• 2579051 You cannot move certain mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server
• 2579982 You cannot view the message delivery report of a signed email message by using Outlook or OWA in an Exchange Server 2010 environment
• 2585649  The StartDagServerMaintenance.ps1 script fails in an Exchange Server 2010 environment
• 2588121 You cannot manage a mail-enabled public folder in a mixed Exchange Server 2003 and Exchange Server 2010 environment
• 2589982 The cmdlet extension agent cannot process multiple objects in a pipeline in an Exchange Server 2010 environment
• 2591572 "Junk e-mail validation error" error message when you manage the junk email rule for a user’s mailbox in an Exchange Server 2010 environment
• 2593011 Warning 2074 and Error 2153 are logged on DAG member servers in an Exchange Server 2010 environment
• 2598985 You cannot move a mailbox from a remote legacy Exchange forest to an Exchange Server 2010 forest
• 2599434 Public Folder Calendar folder is missing in the Public Folder Favorites list of an Exchange Server 2010 mailbox
• 2599663 The Exchange RPC Client Access service crashes when you send an email message in an Exchange Server 2010 environment
• 2600034 A user can still open an IRM-protected email message after you remove the user from the associated AD RMS rights policy template in an Exchange Server 2010 environment
• 2600289 A user in an exclusive scope cannot manage his mailbox in an Exchange Server 2010 environment
• 2600943 EMC takes a long time to return results when you manage full access permissions in an Exchange Server 2010 organization that has many users
• 2601483 "Can’t open this item" error message when you use Outlook 2003 in online mode in an Exchange Server 2010 environment
• 2604039 The MSExchangeMailboxAssistants.exe process crashes frequently after you move mailboxes that contain IRM-protect email messages to an Exchange Server 2010 SP1 mailbox server
• 2604713 ECP crashes when a RBAC role assignee tries to manage another user’s mailbox by using ECP in an Exchange Server 2010 environment
• 2614698  A display name that contains DBCS characters is corrupted in the "Sent Items" folder in an Exchange Server 2010 environment
• 2616124 Empty message body when replying to a saved message file in an Exchange Server 2010 SP1 environment
• 2616230 IMAP4 clients cannot log on to Exchange Server 2003 servers when the Exchange Server 2010 Client Access server is used to handle proxy requests
• 2616361 Multi-Mailbox Search fails if the MemberOfGroup property is used for the management scope in an Exchange Server 2010 environment
• 2616365 Event ID 4999 when the Store.exe process crashes on an Exchange Server 2010 mailbox server
• 2619237 Event ID 4999 when the Exchange Mailbox Assistants service crashes in Exchange 2010
• 2620361 An encrypted or digitally-signed message cannot be printed when S/MIME control is installed in OWA in an Exchange Server 2010 SP1 environment
• 2620441 Stop-DatabaseAvailabilityGroup or Start-DatabaseAvailabilityGroup cmdlet fails when run together with the DomainController parameter in an Exchange Server 2010 environment
• 2621266 An Exchange Server 2010 database store grows unexpectedly large
• 2621403 "None" recipient status in Outlook when a recipient responds to a meeting request in a short period of time in an Exchange Server 2010 environment
• 2628154 "The action couldn’t be completed. Please try again." error message when you use OWA to perform an AQS search that contains "Sent" or "Received" in an Exchange Server 2010 SP1 environment
• 2628622 The Microsoft Exchange Information Store service crashes in an Exchange Server 2010 environment
• 2628693 Multi-Mailbox Search fails if you specify multiple users in the "Message To or From Specific E-Mail Addresses" option in an Exchange Server 2010 environment
• 2629713 Incorrect number of items for each keyword when you search for multiple keywords in mailboxes in an Exchange Server 2010 environment
• 2629777  The Microsoft Exchange Replication service crashes on Exchange Server 2010 DAG members
• 2630708  A UM auto attendant times out and generates an invalid extension number error message in an Exchange Server 2010 environment
• 2630967A journal report is not sent to a journaling mailbox when you use journaling rules on distribution groups in an Exchange Server 2010 environment
• 2632206 Message items rescanned in the background in an Exchange Server 2010 environment
• 2633044 The Number of Items in Retry Table counter displays an incorrect value that causes SCOM alerts in an Exchange Server 2010 SP1 organization
• 2639150 The MSExchangeSyncAppPool application pool crashes in a mixed Exchange Server 2003 and Exchange Server 2010 environment
• 2640218 The hierarchy of a new public folder database does not replicate on an Exchange Server 2010 SP1 server
• 2641077 The hierarchy of a new public folder database does not replicate on an Exchange Server 2010 SP1 server
• 2642189 The RPC Client Access service may crash when you import a .pst file by using the New-MailboxImportRequest cmdlet in an Exchange Server 2010 environment
• 2643950 A seed operation might not succeed when the source mailbox database has many log files in a Microsoft Exchange Server 2010 DAG
• 2644047 Active Directory schema attributes are cleared after you disable a user’s mailbox in an Exchange Server 2010 environment
• 2644264 Disabling or removing a mailbox fails in an Exchange Server 2010 environment that has Office Communications Server 2007, Office Communications Server 2007 R2 or Lync Server 2010 deployed
• 2648682 An email message body is garbled when you save or send the email message in an Exchange Server 2010 environment
• 2649727 Client Access servers cannot serve other Mailbox servers when a Mailbox server encounters a problem in an Exchange Server 2010 environment
• 2649734 Mailbox replication latency may occur when users perform a Multi-Mailbox Search function against a DAG in an Exchange Server 2010 environment
• 2649735 Warning of undefined recipient type of a user after the linked mailbox is moved from an Exchange Server 2007 forest to an Exchange Server 2010 forest
• 2652849 The MailboxCountQuota policy is not enforced correctly in an Exchange Server 2010 hosting mode
• 2665115 Event ID 4999 is logged on an Exchange Server 2010 Client Access server (CAS)

Download the rollup at HERE

By default Windows Server 2008 and 2008 R2 are configured with a dynamic RPC range of 49152-65535 for outbound connections. When the Exchange 2010 Client Access server role is installed on Windows Server 2008 or 2008 R2, the dynamic RPC port range is changed to 6005-59530 and the highest usable port number is set to 60554.

Exchange 2010 RPC Client Access Service

By default the RPC Client Access service on an Exchange 2010 Client Access server uses the TCP End Point Mapper port (TCP/135) and the dynamic RPC port range (6005-59530) for outgoing connections, every time an Outlook clients establish a connection to Exchange.

To set a static port for the RPC Client Access service on an Exchange 2010 Client Access server, you need to open the registry on the respective server and navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeRPC

Here, you need to create a new key named ParametersSystem, and under this key create a REG_DWORD named TCP/IP Port. The Value for the DWORD should be the port number you want to use.

Configuring static ports for the RPC Client Access service

RPC.reg
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeRPC\ParametersSystem]
"TCP/IP Port"=dword:0000e88c

Note

Microsoft recommends you set this to a unique value between 59531 and 60554 and use the same value on all CAS in any one AD site.

When you’ve configured the port, it’s required to restart the Microsoft Exchange RPC Client Access service in order for the changes to be applied.

Exchange 2010 Address Book Service

To set a static RPC port for the Exchange Address Book Service, create a new REG_SZ registry key named “RpcTcpPort” under:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters

RPCAB.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchangeAB\Parameters]
"RpcTcpPort"="59533"

Microsoft recommends you set this to a unique value between 59531 and 60554 and use the same value on all Exchange 2010 Client Access servers in any one AD site.

When you’ve configured the port, it’s required to restart the Microsoft Exchange Address Book service in order for the changes to be applied.

Exchange 2010 Public Folder connections

By default public folder connections uses the TCP End Point Mapper (TCP/135) and the dynamic RPC port range (49152-65535) for outgoing connections, every time an Outlook client establish a connection to Exchange.

To set a static port for public folder connections, follow the same steps as those required for configuring static ports for the RPC CA service. Just bear in mind you need to perform them on the Exchange 2010 servers that stores public folder databases. This is because public folder connections from an Outlook client occur against the RPC Client Access service on the Mailbox server role.

Verifying the Statically Configured Ports are used

In order to verify that the static ports configured are used, the netstat.exe tool can be used:

Netstat -an -p tcp

Verifying the configured static ports are used on the Client Access and Mailbox servers
In my next blog post I will show how to config a Kemp Loadmaster.

Reference:
Link: Configure Static RPC Ports on an Exchange 2010 Client Access Server

Type add first: cd $exscripts and press enter.

Now you are in the Exchange Scripts folder.

Exchange Node 1: 
Process for running maintenance on exchange database servers
.\StartDagServerMaintenance.ps1 -ServerName <Dag Node 1>

Run maintenance on <Dag Node 1>

When you are finished on Node 1
.\StopDagServerMaintenance.ps1 -ServerName <Dag Node 1>

Exchange Node 2:
.\StartDagServerMaintenance.ps1 -ServerName <Dag Node 2>

run maintenance on <Dag Node 2>

When you are finished on Node 2
.\StopDagServerMaintenance.ps1 -ServerName <Dag Node 2>

When done performing maintenance on one or multiple servers (hopefully one at a time to maintain full database availability for end users!) you can end up with a sub-optimal active database layout, especially if you have a cross-site DAG. To resolve this you have to rebalance the databases based on the priorities set for them upon creation.
 
Rebalance databases across dag
.\RedistributeActiveDatabases.ps1 -DagName <Your DAG Name> -BalanceDbsByActivationPreference -ShowFinalDatabaseDistribution -Confirm:$false

If you get any errors you may have to re-index the search catalog for the passive database. Rather than hunting down which ones need to be fixed you can just fix them all with the custom script I wrote below (or for only the mail servers with issues). When finished running these commands then try to run the maintenance or rebalance scripts again.
 
Fix/Rebuild Search Catalogs
Get-MailboxDatabaseCopyStatus -Server <Dag Node 1> | where {$_.Status -like "Healthy"} | Update-MailboxDatabaseCopy –catalogonly

Get-MailboxDatabaseCopyStatus -Server <Dag Node 2> | where {$_.Status -like "Healthy"} | Update-MailboxDatabaseCopy -catalogonly