Move Mailbox Wizard

Moving from Exchange 2000 to Exchange 2003

Kieran McCorry , in Microsoft Exchange Server 2003, Deployment and Migration SP1 and SP2, 2006

Status Reports and Move Mailbox Reports

The Motility Mailbox Wizard volition display data well-nigh pending moves, moves currently in progress, failed moves, and completed moves. Timing data with regard to schedule information and elapsed times for moves is also displayed. Whenever a mailbox motility session is completed, Motion Mailbox Sorcerer volition produce a detailed study of the motility. This report can exist analyzed offline or incorporated into other reporting or administrative systems. These reports are divers in eXtensible Markup Linguistic communication (XML), and then the rendering of the data can be manipulated by utilize of a custom XML style sheet.

Read full chapter

URL:

https://www.sciencedirect.com/scientific discipline/article/pii/B9781555583491500110

Moving from Substitution 2000 to Commutation 2003

Kieran McCorry , in Microsoft® Commutation Server 2003 Deployment and Migration, 2004

8.iv.ii.5 Status reports and Move Mailbox reports

The Move Mailbox Wizard volition display information about pending moves, moves currently in progress, failed moves, and completed moves. Timing data with regard to schedule data and elapsed times for moves is besides displayed. Whenever a Movement Mailbox session is completed, Move Mailbox Sorcerer will produce a detailed written report of the move. This report can be analyzed offline or incorporated into other reporting or administrative systems. These reports are defined in extensible markup language (XML), so the rendering of the information can be manipulated by use of a custom XML style sail.

Read full chapter

URL:

https://www.sciencedirect.com/scientific discipline/commodity/pii/B9781555583163500105

The Basics of Managing Substitution 2007

Tony Redmond , in Microsoft Commutation Server 2007 with SP1, 2008

iii.5.1 Moving mailboxes

Because yous can't upgrade an Exchange 2003 mailbox server to be an Exchange 2007 mailbox server, the just way that you can transfer existing mailboxes to Substitution 2007 is to use the Motility Mailbox feature. Y'all tin can move mailboxes from Substitution 2000 (SP3 or later), Substitution 2003 (SP1 or later), or Substitution 2007 servers to Commutation 2003 (SP3 or afterward), Substitution 2003 (SP1 or later), or Exchange 2007 servers. You can also move mailboxes between different Exchange organizations, providing that the necessary trusts exist between the 2 forests. In nearly cases, you'll be moving to Commutation 2007, but it's nice to know that y'all can use the feature to motion mailboxes between older servers if necessary. To move a mailbox to an Exchange 2007 server, your account needs to hold administrative permissions for the target server and you'll plain need authoritative permission to access the source mailbox. Autonomously from migrations, common reasons to move mailboxes include rebalancing across databases on a server or across servers within the organization, or to move mailboxes off a server that is beingness decommissioned for some reason such as a datacenter consolidation.

You tin can utilise two approaches to motility mailboxes in Exchange 2007: the traditional magician-based method available through EMC or past using the Motion-Mailbox beat out command (see Chapter 4 for details). Considering they are based on the same code base of operations, both methods get the job done, but you tin specify additional parameters to exert more control using the Move-Mailbox command. In most cases, you won't demand the additional degree of control to motility a few mailboxes effectually on an advertisement-hoc ground, simply the extra parameters become more important every bit you lot dive into the possibilities that scripting offers to automate moves for hundreds of mailboxes during the migration to Exchange 2007.

Microsoft made many improvements such every bit support for multiple threads to the Movement Mailbox sorcerer in Commutation 2003. Exchange 2007 adds pre-validation checking to ensure that any obvious errors that could stop a successful mailbox move are detected before the motion commences. The checks include:

▪

Verify that the user account exists and that they accept a valid mailbox.

▪

Check that the user performing the motility has sufficient permissions to perform the motion. This check is done by connecting to both source and target server.

▪

Bank check the mailbox quota limit on the target database to ensure that the mailbox does non exceed the quota.

▪

Stop attempts to motility system mailboxes.

▪

Check that the target database is mounted and available to accept the incoming mailbox.

The Move Mailbox wizard always performs these checks before information technology attempts to motility a mailbox. If you use the Move-Mailbox shell command, y'all tin specify the –ValidateOnly parameter to force Exchange to make the checks.

Figure 3-28 illustrates the first two screens of the Commutation 2007 Move Mailbox wizard.

Figure 3-28. The Exchange 2007 Motion Mailbox sorcerer
▪

The commencement choice to brand is what are the target server and database. As long as a network link is available, you can move a mailbox. My own mailbox was transferred from a server in Dublin, Ireland to a server in Houston, Texas during HP's migration to Exchange 2007 but conspicuously, the closer the two servers are in terms of network connectivity and bandwidth, the faster that the move can progress.

▪

The sorcerer tin can go along processing and motility the mailbox even if it encounters some corrupt messages in the mailbox. You can decide how many corrupt messages the magician should skip. In Substitution 2003, the magician had a hard-coded limit of 100, but Substitution 2007 allows you to specify much higher figures (the highest that I accept gone is i,000). Clearly, if you meet a mailbox that has many corrupt messages, it is a sign that the underlying mailbox shop is probably suffering from some sort of corruption that deserves your attending. Note that if the sorcerer skips any decadent messages, it generates a written report to show you what those messages are.

▪

You can schedule moves to occur at a particular time. The System Bellboy tracks and performs scheduled jobs at the requesting time, allowing you to ensure that mailboxes move when users are asleep!

▪

Yous tin can move multiple mailboxes concurrently by selecting multiple mailboxes and and so taking the "Move Mailbox" selection. Of course, you can achieve further acceleration by using multiple workstations to move mailboxes. The Move Mailbox wizard uses upwardly to 4 threads per session to move mailbox content (yous can increase the number of threads if you move mailboxes with the Move-Mailbox command).

Effigy 3-29 shows how to set a schedule through the sorcerer and how EMC reports details of a multi-mailbox move equally it progresses.

Effigy 3-29. Setting a schedule and a multiple mailbox motion

Depending on system load, moving large mailboxes (>100MB) will accept between 5 and 10 minutes to perform if the two servers share the same LAN, up to approximately 500MB an hour. Moving a mailbox is a binary functioning—it either works or not. If a failure occurs somewhere along the process, you have to showtime again. Annotation that you lot demand Exchange ambassador permission for the administrative group for both the source and target server to be able to perform the move. Ever make sure that you ask the mailbox owner to log off before commencing the move, and ensure that enough disk space is bachelor to accommodate all the transaction logs that the move operation generates. Each transferred message is a transaction for both the source and target databases, and then the disks that hold the transaction logs on both servers will handle a substantial I/O load during the transfer. To offset this issue, you can consider enabling circular logging for the storage groups that host these databases during the motion process. 1 small thing that occasionally trips people up is the fact that when you move mailboxes, the contents of the deleted items enshroud remain behind in the source database. Therefore, a user is not able to call back a deleted detail later on their mailbox is moved.

If users run Outlook 2003/2007 and have a cached Commutation mode mailbox, it is possible for them to continue working in a disconnected country while Exchange moves their mailbox. Substitution volition not deliver new letters to the mailbox and queues them on the source server while the move gain. When it has moved the mailbox, Commutation releases the messages and delivers them from the queue. Exchange notifies Outlook when the moved mailbox is ready to use, and Outlook then switches across (transparently) to access the new server and so transmits any letters that the user sent during the mailbox move. While it is possible to move Outlook 2003/2007 users who do non work in cached Commutation way while they are online, it is definitely something that tempts fate and invites bug. Therefore, it is always a good idea to have users disconnect earlier the move starts and have them set their connection status to "Work Offline." In addition, if a user attempts to log on during a mailbox move (every bit opposed to go on working during the motility), the Store detects the connection endeavour and logs issue 9660, identifying the user name and distinguished name. The Store also flags an fault to tell the user that a mailbox motion is nether way. Finally, you should ask users to look for twenty minutes after their mailbox is moved to a new server before attempting to connect. This pace allows any cached credentials to expire and forces Outlook to refresh its data about the user'south mailbox and so discover that the mailbox is now on a new server. iv

After Exchange has moved the mailboxes, it is best to leave a period of at least fifteen minutes earlier you attempt to access them on the new server. This is because the Shop procedure caches data near mailboxes so that it does not have to go back to Active Directory each time a user requests to access their mailbox. If a mailbox is not accessed in fifteen minutes, the Store removes the information from its cache. When you lot move mailboxes, Active Directory replication may create a slight time-lag before information technology reflects the truthful location of the mailbox across all domain controllers, which may so pb to a situation where a user attempts to log on to their mailbox but cannot considering Active Directory is nevertheless pointing to the old location. The Store caches the incorrect login data and will refer to this data if the user makes another attempt to access their mailbox. The net consequence is confusion and frustration, so it is best to wait for replication to occur before you lot attempt to admission a moved mailbox.

After a mailbox move, Substitution redirects Outlook Web Access connections to the new server the next fourth dimension that a user attempts to log on to their mailbox, but y'all have to update settings manually for IMAP4 and POP3 clients. In some cases, administrators report that newly moved mailboxes use larger quotas (in other words, the aforementioned number of messages occupy more than infinite) when hosted by Substitution 2007 than on a legacy server. This is anecdotal evidence that is not reported consistently from implementation to implementation and is probably highly dependent on the type and format of items stored in a mailbox. In any case, information technology is a good idea to check mailbox quotas before and after the motility to ensure that users can keep working.

Microsoft plans to give the Move Mailbox function the ability to import and consign data from and to PSTs in Exchange 2007 SP1. This is a useful functionality upgrade, only be sure that yous use Unicode-format PSTs if you plan to use this characteristic.

Read full chapter

URL:

https://www.sciencedirect.com/science/article/pii/B9781555583552500064

Transitioning from Exchange 2000 or 2003 to Substitution 2007

Henrik Walther , in How to Crook at Configuring Commutation Server 2007, 2007

Moving Legacy Mailboxes to Exchange 2007

Moving legacy mailboxes to an Exchange 207 Mailbox server is a straightforward procedure and tin be done using either the Move Mailbox Sorcerer in the EMC or the Move-Mailbox CMDlet in the European monetary system.

If you will exist running in a coexistence environment for a period of time, it's important to understand that mailboxes stored on an Commutation 2007 server must non be managed using the Active Directory Users and Computers (ADUC) MMC snap-in but instead must be managed using the EMC or the EMS. However, Substitution 2003 mailboxes can still exist managed using ADUC.

If you want to motion the mailboxes using the EMS, do so using the Move-Mailbox CMDlet. Using the Motility-Mailbox CMDlet gives you a set of advanced options, among which the most interesting ane is the choice of specifying the number of mailboxes to be moved at a time (the Move Mailbox Wizard is express to four).

Read full affiliate

URL:

https://www.sciencedirect.com/scientific discipline/article/pii/B9781597491372500137

Managing Recipients in Exchange 2007

In The All-time Damn Exchange, SQL and IIS Book Period, 2007

Moving a Mailbox

We can too motility a mailbox to some other server, storage group, and mailbox database; we practice this by clicking the Motility Mailbox link in the Activity pane, bringing up the Move Mailbox Magician Introduction page, shown in Figure three.eleven. Here nosotros specify the server, storage grouping, and mailbox database the corresponding mailbox should exist moved to. When you have done so, click Next.

Effigy 3.11. The Move Mailbox Wizard Introduction Page

On the Move Options page, we tin specify how the mailboxes that comprise corrupted letters should be managed. Nosotros can configure the Move Mailbox Sorcerer to skip any mailboxes containing one or more than corrupted letters or simply let information technology skip corrupted messages (Figure 3.12). If we select the latter, we have fifty-fifty more granular control and can specify the maximum number of letters to skip earlier the mailbox move should exist cancelled. In this example, nosotros choose Skip the mailbox and click Adjacent.

Figure three.12. Move Mailbox Wizard Options

We're now taken to the Move Schedule page shown in Effigy 3.13, where we tin can specify when the mailbox move should occur as well as the maximum length of time the move should run before it should be cancelled. The idea backside the Move Mailbox Schedule selection is to allow you lot to schedule the mailbox moves to occur during nonworking hours. In this example, we select Immediately and click Next.

Figure three.13. The Motion Mailbox Sorcerer Schedule Page

Next we are taken to the Motion Mailbox page (come across Effigy 3.xiv), where we tin verify that the parameters for the mailbox motion are correct before the actual move takes place. When you're ready, click Motion.

Figure three.14. The Move Mailbox Wizard Summary Folio

Depending on the size of the mailbox, yous volition need to have a little patience while the movement takes place. The Motility Mailbox Sorcerer needs to commencement open the source mailbox and then create a destination mailbox on the target database. But then does information technology start to move the contents of the mailbox, completing its task by finally deleting the source mailbox and closing its connectedness. When the mailbox has been moved successfully, you lot'll be taken to the Completion page, where y'all can see the CMDlet as well as the parameters used to move the mailbox (see Figure iii.xv). Click Finish to leave the Movement Mailbox Wizard.

Figure 3.15. The Move Mailbox Magician Completion Page

Note

The Substitution 2007 Movement Mailbox Sorcerer is the tool you should use for moving legacy mailboxes from Exchange 2000 or 2003 Server to an Substitution 2007 Mailbox Server.

To move a mailbox using the European monetary system, yous can use the Move-Mailbox CMDlet. To get a list of available parameters for this CMDlet, blazon Get-Help Motility-Mailbox in the EMS.

Read full affiliate

URL:

https://www.sciencedirect.com/science/article/pii/B9781597492195000030

Moving from Exchange v.5 to Exchange 2003

Kieran McCorry , in Microsoft® Exchange Server 2003 Deployment and Migration, 2004

vii.9.one The Exchange 5.5 to Exchange 2003 upgrade approach

Yous cannot perform an in-place upgrade from an Exchange 5.five server to an Exchange 2003 server. Even if you attempt to practice and then, the Exchange 2003 Setup program will instruct y'all that it cannot proceed. This is different from the process that you could have used to upgrade an Exchange five.5 server to Commutation 2000, where an in-identify upgrade was possible.

The alternative, and just recommended, method for migrating an Exchange five.5 server to Exchange 2003 is to use the Move Mailbox Wizard arroyo. Essentially, this approach involves installing an Commutation 2003 server into the same Commutation 5.5 site as the Exchange 5.5 server from which you lot want to migrate mailboxes. You then move all mailboxes from the Exchange 5.5 server onto the Substitution 2003 server, ultimately decommissioning the Exchange 5.5 server when all mailboxes have been moved off. I of the requirements that must be in place earlier any such Substitution 2003 servers can be installed into the Commutation 5.5 site is that an Active Directory Connector environment must already be in identify. This is the aforementioned approach that can also be used for Exchange 5.5 to Substitution 2000 migration.

Substitution 2000 servers can exist directly in-place upgraded to Exchange 2003, and so if you really must perform an in-place upgrade on an Commutation 5.5 server—possibly because you don't have plenty extra or new hardware to use the Move Mailbox Wizard approach—then you tin perform an in-place upgrade from Commutation five.5 to Exchange 2000 followed by another in-identify upgrade from Exchange 2000 to Exchange 2003. This is not recommended, though, given the time required to perform such a series of operations and the impact of lack of service availability on users. However, in some cases it may be absolutely the only approach yous can take. Call back that afterwards such a series of upgrades, it is of the utmost importance to take new backups of the Exchange databases. You lot should really perform ii backups in this scenario: i immediately after the upgrade from Commutation 5.5 to Exchange 2000 and another subsequently the upgrade from Exchange 2000 to Exchange 2003.

Although upgrading from Exchange 5.five in place to Commutation 2000 and then to Substitution 2003 is i of the most intuitive ways by which to get Commutation 2003 deployed, it is also the about complicated, fourth dimension-consuming, and least appealing approach. This department covers what's involved in upgrading an Exchange 5.five server to Exchange 2000. Building on this, and covered afterwards in this volume, we'll discuss upgrading an Exchange 2000 server to Exchange 2003. Permit'southward expect at the process of getting to Exchange 2000 in the offset case.

Read full chapter

URL:

https://www.sciencedirect.com/science/article/pii/B9781555583163500099

Moving from Exchange 5.5 to Exchange 2003

Kieran McCorry , in Microsoft Exchange Server 2003, Deployment and Migration SP1 and SP2, 2006

eight.xi Summary

If you lot are already familiar with Exchange five.five–to–Exchange 2000 migration, then there is very fiddling that'southward new with Exchange v.five–to–Exchange 2003 migration. The same principles and tools are used today as yesterday. Furthermore, migrating from Exchange 5.5 is straightforward, because it's merely a thing of creating an interoperability environment with the Active Directory Connector, so using the Move Mailbox Wizard to motility information: There's no existent decision to be made about upgrading or moving!

The possibility of discovering duplicate objects in your Active Directory during or after a migration to Exchange 2003 is a very real ane. The Active Directory Cleanup Wizard provides an invaluable way to discover and merge these troublesome duplicates, while preserving attribute and admission command information, equally well every bit ensuring the integrity of groups and distribution lists.

Of course, the Active Directory Cleanup Wizard is not all-powerful. Information technology can't merge objects between forests. Nor tin it merge enabled objects in dissimilar domains within the same forest (you must motility them into the aforementioned domain start). It tin can't merge two objects that both have Substitution mailboxes associated with them: That's an entirely different problem! And information technology can't merge two objects that are both mail enabled: Which mail service address would it cull? Although it reduces many migration headaches, information technology should not be used as an alibi for sloppy Commutation five.5 and Windows NT4 account information synergy or carefree migration practices. Take the time upwardly forepart before whatever migration action to clean up your existing sources of data to reduce the likelihood of duplicates or, in the worst case, to increase the likelihood of the Active Directory Cleanup Wizard finding a lucifer. By selecting the correct migration tools for the job and careful planning of your move to Commutation 2003, you may get away with never having to utilize the Active Directory Cleanup Wizard at all. Prevention is e'er better than cure.

Read full chapter

URL:

https://world wide web.sciencedirect.com/science/article/pii/B9781555583491500109

Managing Recipients in Commutation 2007

Henrik Walther , in How to Cheat at Configuring Exchange Server 2007, 2007

Solutions Fast Track

Managing Recipients Using the Exchange 2007 Management Console

Direction of recipients in Exchange Server 2007, besides as their Exchange-related properties, has been moved back into the Exchange Management Panel (EMC) in addition to the Exchange Management Shell (Ems), both of which are based on Windows PowerShell. This means that all management of Exchange recipient objects should be modified from inside the EMC or Ems, not using the ADUC snap-in.

Nosotros have 4 recipient blazon subnodes beneath the Recipient Configuration work eye. In order, we have a Mailbox, a Distribution Group, a Mail Contact, and a Asunder Mailbox node.

Each type of recipient object has its own private icon as well as recipient blazon description due to the fact that they now are explicit and non implicit, as was the case in Exchange Server 2003. This is a nice improver because it makes it so much easier to differentiate the recipient types in Exchange 2007.

Although legacy mailboxes are exposed via the EMC, not all Exchange 2007-specific features apply to these types of mailboxes.

Because Commutation 2007 uses explicit mailbox recipient types, it's possible to create a search filter that lists all room mailboxes, for example, or perchance all legacy mailboxes, for that matter. Listing all resource mailboxes in the ADUC snap-in back in Substitution 2000 or 2003 using a search filter was not a piddling process; it required you to employ custom attributes because there was no other fashion to differentiate resource mailboxes from ordinary mailbox-enabled user accounts.

The Substitution 2007 Move Mailbox Wizard is the tool you should use to move legacy mailboxes from Substitution 2000 or 2003 Server to an Exchange 2007 Mailbox Server.

Equally is the case with Substitution 2000 and 2003, there are two types of Distribution Groups in Commutation 2007: mail-enabled distribution groups, which are used strictly for distributing messages, and mail-enabled security groups, which are used both to assign permissions to users too as to distribute messages. In addition, the query-based distribution group introduced in Exchange 2003 has also made its way into Exchange 2007, albeit with a new name and a few changes.

Dynamic distribution groups, which were known as query-based distribution groups in Exchange 2003, provide the aforementioned type of functionality as ordinary distribution groups, but instead of manually adding members to the group's membership list, you can utilise a ready of filters and conditions that you lot predefine when creating the grouping to derive its membership.

We manage mail contacts (postal service-enabled contacts) and mail users (mail-enabled users) nether the Mailbox Contact subnode beneath the Recipient Configuration work centre node.

When you either disable or remove a mailbox, that mailbox will exist marked for deletion but will not be automatically deleted. Instead, information technology volition be kept in the corresponding mailbox database for the number of days specified on the mailbox database Properties page (under the Limits tab), chosen "Keep deleted mailboxes for," more commonly referred to equally mailbox retentivity. Similar Exchange 2000 and 2003, Exchange 2007 volition, by default, proceed deleted mailboxes for 30 days before they are purged (permanently deleted).

Managing Recipients in a Coexistence Environment

During a transition from Exchange 2000/2003 to Exchange 2007, deploying Exchange 2007 server into your existing Commutation organisation can take a long time, depending on the size of your existing setup and organizational layout. This means that y'all might have to manage mail-enabled users from both the EMC and the ADUC MMC snap-in for a period of time.

Although yous have the selection of managing Exchange 2007 mailbox and mail service-enabled users using the ADUC snap-in, it isn't supported and volition outcome in Exchange 2007 mailboxes that might not exist fully functional. In addition, you should opt to employ the Substitution 2007 tools for moving Exchange 2000/2003 user mailboxes.

The infamous Recipient Update Service (RUS), which most of united states know from Exchange 2000 and 2003, is no longer part of the Commutation 2007 product. RUS was responsible for stamping electronic mail addresses, in add-on to address list membership along with a few other things, but didn't always piece of work as expected and was very hard to troubleshoot when it acted upwards. With Exchange 2007, the RUS (and thereby the asynchronous behavior used to provision objects) has been replaced by a new synchronous process, the EmailAddressPolicy CMDlet, used to stamp the e-mail address onto objects immediately.

Granting Access and/or SendAs Permissions to a Mailbox

In some situations, one or more users might need to be granted permissions to access another user'southward mailbox. This could be a more than temporary access during vacations, maternity get out, or other reasons, where i or more users demand to accept over the work of the user who will be absent. Information technology could besides be a more than permanent admission, where a secretary needs to access her boss's mailbox, for example. Some other reason could be that all users in a particular department (such every bit a helpdesk) need a shared mailbox.

Creating a Custom Recipient Management Panel

Depending on the organization, at times you might desire to create an Commutation 2007 Management Console that shows only the Recipient Configuration piece of work center node. This is peculiarly truthful in situations where you lot have a helpdesk that is used to having a customized ADUC console snap-in that provides the respective OUs holding the Exchange user objects they were to administer.

Yous can create isolated Management Consoles for the Organization Configuration, Server Configuration, and Toolbox work centre nodes. You lot tin can practice this by following the same steps but opening a new console window by right-clicking the corresponding piece of work center node. If y'all have both the Substitution 2007 Tools and the Windows AdminPak installed on a server or workstation, yous tin can even create a single console with admission to both the ADUC snap-in and the Exchange 2007 Direction Console.

Recipient Filtering in Exchange 2007

If you have already deployed and/or are planning to deploy Substitution 2007 in an arrangement consisting of several g recipients, you can quickly lose the authoritative overview. This is where recipient filtering comes into the moving-picture show. By creating a filter using either the EMC or the Ems, you will be able to discover the recipient or set of recipients you're looking for in a thing of seconds.

Creating a recipient filter is done by selecting the Recipient Configuration work centre node or the particular recipient subnode.

Read total chapter

URL:

https://world wide web.sciencedirect.com/science/commodity/pii/B978159749137250006X

Interorganization Migrations

Kieran McCorry , in Microsoft® Commutation Server 2003 Deployment and Migration, 2004

nine.5.7 Interorganization mailbox migration

Providing interoperability by ways of interorganization post connections—which are straightforward to do for any environment—and directory synchronization only provides the get-go function of the interorganization migration. The adjacent challenge comes with actually moving mailbox contents from a server in a source Exchange v.v organization to the target Substitution 2000/2003 organization.

Microsoft provides the Motility Mailbox Wizard for intraorganization moves, and the Exchange Server Migration Wizard and ExMerge can as well be used. The latter tools work for interorganization moves, but they are both i-shot tools and provide no ongoing or gradual mailbox synchronization. This is another area where tertiary-party migration tools usually excel.

Much like the directory synchronization, mailbox synchronization is implemented using agents, three in this example: the Mailbox Source Amanuensis (MSA), the Manual Amanuensis (TA), and the Mail service Target Amanuensis (MTA). This is shown graphically in Figure 9-23.

Effigy 9-23. Agent Architecture for Mailbox Synchronization

The MSA resides on the source Substitution 5.five server, which monitors the synchronization status of mailboxes. You lot need one MSA per Exchange 5.5 server. Each mailbox is queried for changes since the last synchronization, the changes are written to locally stored PST files for each mailbox and and so compressed in a single file, known as the PRV file. The MSA then transfers the aggregate PRV file to the TA, also installed on the Commutation v.5 server, which transfers mailbox information to the target Exchange 2000/2003 server. If in that location are multiple target servers to receive data, then there will exist multiple PRV files. The TA volition send the appropriate PRV file directly to the required target server. On the target server, the MTA accepts the data, decompresses information technology, and transfers it to the destination mailboxes.

The whole mailbox synchronization process uses compressed information files (which is another advantage over the default Microsoft tools) and then that the actual transmission on the wire is kept to a minimum. This is useful in many consolidation scenarios because servers distributed over the wide area network (WAN) are often being consolidated to centralized locations. (This trend is becoming more than widespread with the advent of Outlook 2003's buried working fashion, which makes centralized, consolidated Commutation information centers with outlying remote clients all the more bonny and effective.) Y'all can explicitly cull whether to use compression, and if yous do, you tin can cull the compression level. No compression incurs more network traffic only is faster; high compression incurs less network traffic merely is slower.

Right-clicking the Mailbox Synchronization particular in the Console and selecting Add Mailbox Synchronization Chore will gear up up all of the requisite agents on the source and target servers. Each Chore identifies the single source Exchange five.5 server and the single target Exchange 2000/2003 server. Although you are prompted to define the Storage Group and Mailbox Store on which the mailboxes are to be synchronized, y'all should select those Storage Groups and Mailbox Stores that correspond with those already identified during the Directory Synchronization phase.

The Collections feature exposes the existent power of mailbox synchronization and consolidation. A Drove is a grouping of mailboxes that will be synchronized together. Each Collection retains its own settings and priority. You can define when the migration for a item Collection will take place. A Synchronization Job tin handle multiple Collections. A Collection will only begin processing if all college-priority Collections have fully completed their processing.

When you run through the Mailbox Synchronization Task Wizard, y'all initially ascertain whether you lot want to use Collections at all and some general settings around Collections (i.e., an initial start Drove, one Collection per target server mailbox store, or simply distributing a stock-still number of mailboxes into an arbitrary Collection name). This is shown in Figure 9-24.

Figure nine-24. Creating Mailbox Collections with the Mailbox Synchronization Task Wizard

Electing to use Collections means that you have much granularity in selecting which mailboxes volition be moved at any given time. With the Wizard you lot tin add private mailboxes to a given Drove or you lot can select any number of Exchange 5.5 recipient containers as the source, every bit shown in Figure 9-25. You can add together additional Collections to a Job at any time through the Console interface. With this interface y'all configure additional settings such equally the Collection priority and start and end times. By default, the synchronization is set up to start immediately, just you can ascertain exactly when you lot would like synchronization to start for each Collection. And by default, the synchronization process is active for about four weeks from the default start time. Again, you can modify this as required. You may also add together mailboxes to a collection using an external file (e.grand., CSV formatted), which is useful if the Exchange migration is office of a wider migration projection in your environment and yous must align your Exchange migration with other migration activities.

Figure 9-25. Calculation Source Mailboxes to a Collection

All of this means that you need to carefully programme and schedule your entire migration and consolidation strategy, and in fact, schedule the whole process well in advance of any actual migration activity. With this approach yous can gradually migrate users at the pace that suits you and imposes the least amount of load on the network and other end systems.

Getting the mailbox contents in sync between the source Commutation v.5 organization and the target Exchange 2000/2003 organizations is just one footstep in the mailbox migration process. The next stage is to decommission the Exchange v.five mailbox and have the Exchange 2000/2003 mailbox become the primary mailbox for the user. This process is known as mailbox switching.

Backside the scenes, the mailbox switching process is relatively trivial. Two things happen. On the Substitution five.5 server, the user's mailbox is modified and so that an alternating recipient is defined for the mailbox. Whatsoever postal service now sent to that mailbox is redirected to the alternate recipient. The specified alternate recipient is really the redirection custom recipient created when directory synchronization took place. Thus any mail delivered to the redirection custom recipient is relayed to the Exchange 2000/2003 mailbox in the target system. In the target organization the redirection on the Exchange 2000/2003 mailbox to the redirection contact is removed. Figure 9-26 shows the alternate recipient modification to an Exchange 5.five mailbox.

Figure nine-26. Exchange 5. 5 Mailbox with Redirection Custom Recipient

Switching tin be performed manually by selecting users already synchronized and associated with a item Synchronization Task, right-clicking, and choosing the pick to switch. Multiple mailboxes may be selected and switched at the same time. Third-political party migration tools tin can be configured then that when mailboxes are switched, suitable messages are sent to user mailboxes informing them that they have been migrated.

Collections can also exist configured so that fully synchronized user mailboxes are automatically switched. This is done by setting the properties on the Collection. Some heavily used mailboxes may never go fully synchronized at a given point in time so long equally mail continues to be delivered into the source mailbox. For this reason, you can automatically accept mailboxes switched even if they are slightly out of sync. Y'all specify the threshold (in KB) that y'all volition tolerate, and immediately after the mailbox is switched, any unsynchronized content is brought beyond to the target server.

Note also that mailboxes tin exist unswitched by but toggling the switched setting, so that users incurring problems with their new Exchange 2000/2003 mailbox tin be simply and speedily moved dorsum to Exchange 5.5.

With an interorganization migration, users' MAPI profiles are invalidated when a user is moved to an Exchange server in a new organization. Third-political party migration tools commonly provide a Profile Updating Utility that is integrated with the mailbox switching process. The utility can be run from a logon script and recognizes a flag fix by the mailbox switch procedure. Thus, the move is relatively transparent to the end user.

Read total chapter

URL:

https://www.sciencedirect.com/science/article/pii/B9781555583163500117

Interorganizational Migrations

Kieran McCorry , in Microsoft Exchange Server 2003, Deployment and Migration SP1 and SP2, 2006

7.5.7 Interorganizational Mailbox Migration

Providing interoperability by means of interorganizational mail connections—which is straightforward to practise in any environment—and directory synchronization only provides the starting time part of the interorganizational migration. The next challenge comes with actually moving mailbox contents from a server in a source Exchange 5.5 organization to the target Substitution 2000/2003 organisation.

Microsoft provides the Move Mailbox Wizard for intraorganizational moves; the Exchange Server Migration Wizard and ExMerge can also be used. The latter tools work for interorganizational moves, but they are both one-shot tools and provide no ongoing or gradual mailbox synchronization. This is another expanse where tertiary-political party migration tools usually excel.

Much similar directory synchronization, mailbox synchronization is implemented using agents, 3 in this case: the Mailbox Source Agent (MSA), the Transmission Amanuensis (TA), and the Post Target Agent (MTA). This is shown graphically in Figure 7.23.

Figure vii.23. Amanuensis compages for mailbox synchronization.

The MSA resides on the source Exchange 5.5 server, which monitors the synchronization status of mailboxes. You need one MSA per Substitution 5.5 server. Each mailbox is queried for changes since the last synchronization; the changes are written to locally stored Personal Store (PST) files for each mailbox and and then compressed in a single file, known as the PRV file. The MSA and then transfers the amass PRV file to the Transmission Amanuensis, also installed on the Exchange five.five server, which transfers mailbox information to the target Exchange 2000/2003 server. If there are multiple target servers to receive data, then there volition be multiple PRV files. The TA will transport the appropriate PRV file straight to the required target server. On the target server, the MTA accepts the data, decompresses it, and transfers it to the destination mailboxes.

The whole mailbox synchronization process uses compressed data files (which is another advantage over the default Microsoft tools) so that the actual transmission on the wire is kept to a minimum. This is useful in many consolidation scenarios, since servers distributed over a wide expanse network are ofttimes existence consolidated to centralized locations. (This trend is condign more than widespread with the advent of Outlook 2003'southward cached working mode, which makes centralized, consolidated Commutation data centers with outlying remote clients all the more attractive and effective.) You lot can explicitly choose whether or not to apply compression, and, if you do, y'all tin can choose the compression level. No compression incurs more network traffic only is faster; loftier compression incurs less network traffic just is slower.

Right-clicking the "Mailbox Synchronization" detail in the console and selecting "Add Mailbox Synchronization Job" will set up up all the requisite agents on the source and target servers. Each task identifies the unmarried source Exchange 5.5 server and the single target Exchange 2000/2003 server. Although you are prompted to ascertain the storage group and mailbox store on which the mailboxes are to be synchronized, you should select the storage groups and mailbox stores that correspond with those already identified during the directory-synchronization phase.

The Collections feature exposes the real ability of mailbox synchronization and, indeed, consolidation. A drove is a group of mailboxes that volition be synchronized together. Each drove retains its own settings and priority. Yous can ascertain when the migration for a particular collection will take identify. A synchronization job tin can handle multiple collections. A collection will just begin processing if all higher-priority collections have fully completed their processing.

When you run through the Mailbox Synchronization Job Magician, you initially define whether you want to utilize collections at all and some general settings around collections; that is, practice you want to use an initial first collection or one collection per target server mailbox shop, or are you simply distributing a fixed number of mailboxes into an arbitrary collection proper noun. This is shown in Figure 7.24.

Effigy 7.24. Creating mailbox collections with the Mailbox Synchronization Chore Wizard.

Electing to use collections means that y'all take much granularity in selecting which mailboxes volition exist moved at any given time. With the wizard you lot can add together individual mailboxes to a given collection, or yous can select any number of Substitution v.5 recipient containers as the source, every bit shown in Figure 7.25. You lot can add together additional collections to a job at whatever time through the console interface. With this interface, you lot configure additional settings such equally the drove priority and outset and end times. Past default, the synchronization is set to start immediately, but you tin define exactly when you would like synchronization to commencement for each collection. And, past default, the synchronization procedure is agile for near four weeks from the default outset time. Once more, y'all can change this every bit required. You may also add together mailboxes to a collection using an external file (e.thou., CSV formatted); this is useful if the Exchange migration is function of a wider migration project in your environment, and you must marshal your Exchange migration with other migration activities.

Figure 7.25. Calculation source mailboxes to a collection.

All of this means that you need to plan and schedule your unabridged migration and consolidation strategy advisedly; in fact, you lot schedule the whole procedure well in accelerate of whatever bodily migration activity. With this approach, you can gradually migrate users at the pace that suits yous; it also imposes the least corporeality of load on the network and other cease systems.

Getting the mailbox contents in synch between the source Commutation 5.5 arrangement and the target Exchange 2000/2003 organizations is just one pace in the mailbox migration process. The adjacent stage is to decommission the Exchange 5.five mailbox and have the Exchange 2000/2003 mailbox go the primary mailbox for the user. This process is known as mailbox switching.

Behind the scenes, the mailbox-switching process is relatively trivial. Two things happen. On the Exchange v.5 server, the user'due south mailbox is modified so that an alternate recipient is defined for the mailbox. Any mail now sent to that mailbox is redirected to the alternate recipient. The specified alternate recipient is actually the redirection custom recipient created when directory synchronization took identify. Thus, any mail delivered to the redirection custom recipient is relayed to the Exchange 2000/2003 mailbox in the target arrangement. In the target organization, the redirection on the Substitution 2000/2003 mailbox to the redirection contact is of form removed. Figure 7.26 shows the alternate recipient modification to an Exchange 5.v mailbox.

Effigy 7.26. Exchange 5.5 mailbox with redirection custom recipient.

Switching tin can be performed manually by selecting users already synchronized and associated with a detail synchronization chore, right-clicking, and choosing the option to switch. Multiple mailboxes may exist selected and switched at the same time. Third-political party migration tools tin be configured so that when mailboxes are switched, suitable messages are sent to user mailboxes informing them that they have been migrated.

Collections can besides exist configured and then that fully synchronized user mailboxes are automatically switched. This is done past setting the properties on the drove. Some heavily used mailboxes may never become fully synchronized at a given point in time so long as mail service continues to exist delivered into the source mailbox. For this reason, you can automatically have mailboxes switched, even if they are slightly out of synch. You specify the threshold (in kilobytes) that you will tolerate, and immediately after the mailbox is switched, any unsynchronized content is brought across to the target server.

Note as well that mailboxes tin exist unswitched by simply toggling the switched setting so that users incurring issues with their new Commutation 2000/2003 mailbox can exist simply and rapidly moved back to Exchange 5.5.

With an interorganizational migration, a user's MAPI profiles are invalidated when that user is moved to an Substitution server in a new organization. Third-party migration tools usually provide a profile-updating utility that is integrated with the mailbox-switching procedure. The utility can be run from a logon script and recognizes a flag prepare by the mailbox-switching procedure. Thus, the move is relatively transparent to the end user.

Read total chapter

URL:

https://world wide web.sciencedirect.com/scientific discipline/article/pii/B9781555583491500092