Tag Archive for: Migration

Best practices for doing an Exchange Dry Run using the Priasoft Migration Suite for Exchange

Priasoft Migration Suite for Exchange (PMSE)

What is a dry run?

The priasoft Migration Suite for Exchange allows you to do a ‘dry run’. An Exchange dry run is a testing process where the effects of a possible migration failure are intentionally mitigated. For example, an aerospace company may conduct a “dry run” test of a jet’s new pilot ejection seat while the jet is parked on the ground, rather than while it is in flight. In addition, a dry run allows you to understand how long your migration will take and what loads can be expected on both source and target Exchange systems. Read more

How to gain access to a user’s source mailbox post migration

Priasoft Migration Suite for Exchange (PMSE)

Post migration the source user’s mailbox is left in a “dormant state” so that if the need arises you can roll back the user. However, you may want to access the source mailboxes data without having to roll the source user back. This article will explain how to access a source mailbox post migration after migration using the Priasoft Migration Suite for Exchange.

Several properties are set on the source object post migration to place it in a “dormant state”. This is done to allow for roll back and to prevent unauthorized access to the source post migration. The main property that will block access to the source mailbox data post migration is the ProtocolSettings attribute on the users source AD object.

The ProtocolSettings attribute on the source user object in the Active Directory stores client access settings. This attribute is a multi-valued string property, where each string applies to a different protocol. MAPI access is restricted by adding the following string to the ProtocolSettings:

MAPI§<Bool1>§<Bool2>§§§§§§

The eight § separators define exactly nine fields. The meanings of the fields are as follows:

MAPISpecifies that this string contains settings that apply to the MAPI protocol
Bool10 to block all MAPI access; 1 to determine MAPI access based on Bool2.
Bool20 for “no effect”; 1 to deny access to non-cached mode Outlook clients
Remaining 6 fieldsCurrently not used

If there is no MAPI string in ProtocolSettings, all MAPI clients are allowed.

In order to gain access to the source mailbox post migration you will need to clear the MAPI§ setting in the ProtocolSettings attribute on the source mailbox.

Please note:

Changes to this setting do not take effect immediately and can up to two hours to take effect. This is because, as with others mailbox properties stored in the DS, ProtocolSettings are cached in the MIBCache (default TTL = 2hrs) and in DSAccess (default TTL = 15 min). These caches may delay the time it takes for a change in the ProtocolSettings to become effective.
In order to read more about the Information Store cache, please see the following article: http://support.microsoft.com/?id=179065

Issues to be considered while thinking about moving mailboxes to Exchange 2010 using the Microsoft native tools

Priasoft Migration Suite for Exchange (PMSE)

Below is a table of the issues to be considered while thinking about moving mailboxes using the Microsoft native tools in both the ‘upgrade’ and ‘deployment’ scenarios supported by Microsoft.

Note: If you’re using the Priasoft Migration Suite for Exchange this article does not apply to you.

Exchange 2003 To 2010

  • You need to use “move request” cmdlets in 2010 shell to move the mailboxes.
  • Move requests are performed by the Microsoft Exchange Mailbox Replication Service (MRS) that runs on all Client Access servers (CAS). Therefore, CAS servers are busy moving mailboxes and not servicing clients’ requests.
  • If you implement Exchange 2010 as an upgrade, some features of Exchange 2010 will not be available until the migration is completed and the organization in moved to a native mode state.
  • You must never try to manage a 2010 mailbox using a 2003 management tool or snap in
  • You can’t use 2003 System Manager.
  • You must be careful to use a split administration model while co-existing to not cause problems with migrated objects.
  • The mailbox move is offline, which means that the users can’t access the emails while it is moved.
  • No roll-back support – If something goes wrong you may need to go back to tape to restore the mailbox
  • No support for native tools – if they don’t work they don’t work.
  • No Outlook client profile automation for migrated mailboxes. No automatic enabling of RPC encryption for Outlook 2003 based clients. You will need to do them manually or you will need to disable RPC encryption on Exchange 2010 (not recommended)
  • No Public Folder migration tools
  • No distribution group migration tools
  • You can’t move mailboxes if running Exchange 2003 SP1 or earlier, you must update all servers to 2003 SP2+
  • You can’t perform message tracking configuration tasks between Exchange 2010 and Exchange 2003
  • You must use Exchange 2003 messaging tracking tools within your Exchange 2003 organization, and Exchange 2010 messaging tracking tools within your Exchange 2010
  • Side-by-side management for Exchange Server 2003 and Exchange 2010 management tools isn’t supported, because Exchange Server 2003 management tools can only be run on 32-bit machines
  • In order to do Cross-forest move requests must create mail-enabled users with the required attributes in the target forest or it won’t work
  • Depending on the scenario you just may be able to preserve mailbox folder delegates and send-on behalf of delegates
  • If upgrading, you must run the setup /PrepareLegacyExchangePermissions command so that the Exchange 2003 Recipient Update Service functions correctly
  • If upgrading, you are required to update the Active Directory schema for Exchange Server 2010
  • If upgrading, you must Upgrade Custom LDAP Filters to OPATH Filters

Exchange 2007 To 2010

  • You can use 2010 console or “move request” cmdlets in 2010 shell to move the mailboxes.
  • If you implement Exchange 2010 in mixed mode, some features of Exchange 2010 will not be available until the migration is completed and the organization in moved to a native mode state.
  • Move requests are performed by the Microsoft Exchange Mailbox Replication Service (MRS) that runs on all Client Access servers (CAS). Therefore, CAS servers are busy moving mailboxes and not servicing clients’ requests.
  • You can’t use “move-mailbox” cmdlet in 2007 shell.
  • No roll-back support – If something goes wrong you may need to go back to tape to restore the mailbox
  • No support for native tools – if they don’t work they don’t work.
  • The mailbox move is online, which means that the users can be online while the move happens.
  • You can’t move mailboxes from 2007 SP1 or earlier, the source should run 2007 SP2+
  • Exchange 2007 Mailbox databases can’t be managed from the EMC in Exchange 2010
  • No Public Folder migration tools
  • No distribution group migration tools
  • No Outlook client profile automation for migrated mailboxes. No automatic enabling of RPC encryption for Outlook 2003 based clients. You will need to do them manually or you will need to disable RPC encryption on Exchange 2010 (not recommended)
  • The EMC in Exchange 2010 can’t manage Exchange 2007 mobile devices
  • Exchange 2007 Mailbox databases can’t be managed from the EMC in Exchange 2010
  • You can’t use message tracking configuration tasks between Exchange 2010 and Exchange 2007
  • You must use Exchange 2007 messaging tracking tools within your Exchange 2007 servers, and Exchange 2010 messaging tracking tools within your Exchange 2010 servers.
  • Exchange 2010 and Exchange 2007 servers can only be viewed from their corresponding version of the EMC
  • In order to schedule Cross-forest move requests must create mail-enabled users with the required attributes in the target forest or it won’t work
  • If upgrading, you are required to update the Active Directory schema for Exchange Server 2010
  • Depending on the scenario you just may be able to preserve mailbox folder delegates and send-on behalf of delegates

Exchange 5.5 And 2000 To 2010

  • Not supported by Exchange 2010 native tools
  • If you want to move to Exchange 2010 using native tools from Exchange 5.5 you must first migrate to Exchange 2003/2007 then to Exchange 2010
  • If you want to move to Exchange 2010 using native tools from Exchange 2000 you must first migrate to Exchange 2003/2007 then to Exchange 2010

In short, it’s not as simple as tossing in a CD. Can it be done? Sure, would we want to do it? Nope.

We highly recommend you consider the resource forest model for Exchange 2010 to avoid trying to mix the old with the new. This model, in our opinion, allows the most flexibility during migration, allows you to build your Exchange organization to your needs, and provides benefits well into the future. It also helps to reduce risk. Something we all like!

This is not a complete list of issues nor should it be used as a roadmap to moving to Exchange 2010. We are providing this simply as a comparison and we do not take any responsibility whatsoever for the information contained. You are encouraged to do your own due diligence and research.

Exchange Adoption Patterns

Priasoft Migration Suite for Exchange (PMSE)

Despite the advantages of moving to Exchange Server 2010, will organizations using an old software product want to upgrade to a newly-released version? It all depends on the organization type. There are different organization types when it comes to adopting software:

  • Early adopters jump onto the software bandwagon as soon as the software is released. Needless to say, they are far and few between and will usually have a special relationship with the software manufacturer.
  • Common adopters wait for others to test the software release and find all of its potential bugs. This usually coincides with the release of the first service pack for the software product.
  • Conservatives will wait well after the software has been released, often after the release of multiple service packs, before they make their move.
  • Ultra-conservatives will wait until the very last minute before they move to the next version of the product and when they do, they won’t usually jump onto the very latest version of the product.

This cycle is repeated every time a new version of a product is released.

Regardless of which version your choose we have the tools and experience to move you from Exchange 5.5, 2000, 2003, 2007, and 2010 to Exchange 2000, 2003, 2007, 2010, and 2013…