Movement Mailbox Wizard

Moving from Exchange 2000 to Commutation 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 will display information almost pending moves, moves currently in progress, failed moves, and completed moves. Timing information with regard to schedule information and elapsed times for moves is besides displayed. Whenever a mailbox movement session is completed, Move Mailbox Magician volition produce a detailed report of the movement. This report can be analyzed offline or incorporated into other reporting or administrative systems. These reports are defined in eXtensible Markup Language (XML), and so the rendering of the data can exist manipulated by apply of a custom XML mode sheet.

Read full chapter

URL:

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

Moving from Commutation 2000 to Substitution 2003

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

eight.four.2.v Status reports and Motility Mailbox reports

The Motility Mailbox Wizard volition display information about awaiting moves, moves currently in progress, failed moves, and completed moves. Timing information with regard to schedule information and elapsed times for moves is too displayed. Whenever a Move Mailbox session is completed, Motion Mailbox Magician volition produce a detailed report of the move. This report can be analyzed offline or incorporated into other reporting or authoritative systems. These reports are defined in extensible markup linguistic communication (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/science/article/pii/B9781555583163500105

The Basics of Managing Exchange 2007

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

three.5.i Moving mailboxes

Because y'all tin't upgrade an Exchange 2003 mailbox server to exist an Exchange 2007 mailbox server, the only way that you tin can transfer existing mailboxes to Exchange 2007 is to use the Motility Mailbox feature. You can move mailboxes from Exchange 2000 (SP3 or later), Substitution 2003 (SP1 or afterward), or Commutation 2007 servers to Exchange 2003 (SP3 or after), Commutation 2003 (SP1 or afterward), or Commutation 2007 servers. You tin too move mailboxes between unlike Commutation organizations, providing that the necessary trusts exist between the two forests. In most cases, you'll be moving to Exchange 2007, only it's nice to know that y'all can use the feature to move mailboxes betwixt older servers if necessary. To move a mailbox to an Exchange 2007 server, your business relationship needs to hold administrative permissions for the target server and you'll plainly need authoritative permission to access the source mailbox. Apart from migrations, mutual reasons to move mailboxes include rebalancing beyond 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.

Y'all can utilize ii approaches to move mailboxes in Exchange 2007: the traditional sorcerer-based method bachelor through EMC or by using the Move-Mailbox shell command (see Chapter 4 for details). Because they are based on the same lawmaking base, both methods get the job done, just yous can specify additional parameters to exert more command using the Motility-Mailbox command. In most cases, you won't need the additional degree of control to movement a few mailboxes around on an ad-hoc basis, but 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 Substitution 2007.

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

▪

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

▪

Bank check that the user performing the move has sufficient permissions to perform the move. This check is washed by connecting to both source and target server.

▪

Check the mailbox quota limit on the target database to ensure that the mailbox does not exceed the quota.

▪

Finish attempts to movement organization mailboxes.

▪

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

The Move Mailbox wizard always performs these checks before it attempts to motion a mailbox. If you use the Move-Mailbox shell command, you lot can specify the –ValidateOnly parameter to strength Exchange to make the checks.

Figure 3-28 illustrates the first 2 screens of the Exchange 2007 Move Mailbox wizard.

Figure iii-28. The Exchange 2007 Movement Mailbox sorcerer
▪

The first choice to make is what are the target server and database. Equally long every bit a network link is available, you tin move a mailbox. My ain mailbox was transferred from a server in Dublin, Ireland to a server in Houston, Texas during HP's migration to Commutation 2007 only clearly, the closer the two servers are in terms of network connectivity and bandwidth, the faster that the move can progress.

▪

The magician can keep processing and move the mailbox even if it encounters some decadent letters in the mailbox. You can decide how many decadent letters the magician should skip. In Substitution 2003, the magician had a hard-coded limit of 100, but Exchange 2007 allows you to specify much higher figures (the highest that I have gone is 1,000). Clearly, if you lot meet a mailbox that has many decadent messages, it is a sign that the underlying mailbox store is probably suffering from some sort of abuse that deserves your attention. Annotation that if the wizard skips any decadent messages, it generates a report to show y'all what those messages are.

▪

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

▪

Y'all can move multiple mailboxes concurrently by selecting multiple mailboxes and then taking the "Move Mailbox" option. Of grade, you tin achieve further acceleration by using multiple workstations to move mailboxes. The Motion Mailbox wizard uses up to four threads per session to move mailbox content (yous can increment the number of threads if you lot move mailboxes with the Motility-Mailbox command).

Figure three-29 shows how to set a schedule through the wizard and how EMC reports details of a multi-mailbox move equally it progresses.

Figure 3-29. Setting a schedule and a multiple mailbox motility

Depending on organization load, moving large mailboxes (>100MB) volition take between 5 and x minutes to perform if the 2 servers share the same LAN, up to approximately 500MB an hr. Moving a mailbox is a binary functioning—it either works or not. If a failure occurs somewhere along the process, you have to kickoff once more. Note that you lot demand Exchange administrator permission for the administrative group for both the source and target server to be able to perform the move. Ever make sure that you enquire the mailbox owner to log off before commencing the move, and ensure that plenty disk space is available to accommodate all the transaction logs that the move operation generates. Each transferred message is a transaction for both the source and target databases, so the disks that hold the transaction logs on both servers volition 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 procedure. One small thing that occasionally trips people up is the fact that when you movement mailboxes, the contents of the deleted items cache remain behind in the source database. Therefore, a user is not able to think a deleted item later their mailbox is moved.

If users run Outlook 2003/2007 and have a cached Substitution mode mailbox, information technology is possible for them to continue working in a disconnected land while Substitution moves their mailbox. Commutation volition not evangelize new letters to the mailbox and queues them on the source server while the move proceeds. 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 employ, and Outlook then switches across (transparently) to access the new server and so transmits whatever messages that the user sent during the mailbox move. While it is possible to move Outlook 2003/2007 users who do non piece of work in cached Exchange mode while they are online, it is definitely something that tempts fate and invites problems. Therefore, information technology is always a good idea to have users disconnect earlier the move starts and have them fix their connection status to "Work Offline." In addition, if a user attempts to log on during a mailbox movement (as opposed to continue working during the motility), the Store detects the connection endeavour and logs event 9660, identifying the user name and distinguished name. The Store also flags an error to tell the user that a mailbox movement is nether fashion. Finally, you should ask users to await for 20 minutes afterward their mailbox is moved to a new server earlier attempting to connect. This step allows any cached credentials to elapse and forces Outlook to refresh its data about the user's mailbox and so discover that the mailbox is now on a new server. 4

After Exchange has moved the mailboxes, information technology is best to leave a period of at least fifteen minutes before you endeavor to access them on the new server. This is because the Store process caches information about 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 15 minutes, the Store removes the information from its cache. When yous motion mailboxes, Active Directory replication may create a slight time-lag before information technology reflects the true location of the mailbox across all domain controllers, which may then lead to a state of affairs where a user attempts to log on to their mailbox merely cannot because Active Directory is all the same pointing to the old location. The Shop caches the incorrect login data and volition refer to this information if the user makes another attempt to access their mailbox. The net outcome is confusion and frustration, then information technology is best to wait for replication to occur before you try to admission a moved mailbox.

After a mailbox motility, Exchange redirects Outlook Spider web Access connections to the new server the next fourth dimension that a user attempts to log on to their mailbox, but you have to update settings manually for IMAP4 and POP3 clients. In some cases, administrators report that newly moved mailboxes employ larger quotas (in other words, the aforementioned number of messages occupy more space) when hosted past Exchange 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 whatsoever instance, information technology is a good idea to bank check mailbox quotas before and later the movement to ensure that users can keep working.

Microsoft plans to give the Motility Mailbox function the ability to import and export data from and to PSTs in Substitution 2007 SP1. This is a useful functionality upgrade, just exist sure that you use Unicode-format PSTs if you lot program to utilise this feature.

Read full chapter

URL:

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

Transitioning from Exchange 2000 or 2003 to Commutation 2007

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

Moving Legacy Mailboxes to Exchange 2007

Moving legacy mailboxes to an Exchange 207 Mailbox server is a straightforward process and can be done using either the Motion Mailbox Magician in the EMC or the Move-Mailbox CMDlet in the EMS.

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

If y'all want to motion the mailboxes using the EMS, do so using the Motion-Mailbox CMDlet. Using the Motility-Mailbox CMDlet gives you a ready of advanced options, among which the virtually interesting i is the option of specifying the number of mailboxes to be moved at a fourth dimension (the Move Mailbox Sorcerer is express to four).

Read full chapter

URL:

https://www.sciencedirect.com/science/commodity/pii/B9781597491372500137

Managing Recipients in Exchange 2007

In The Best Damn Commutation, SQL and IIS Book Menstruation, 2007

Moving a Mailbox

We can also move a mailbox to some other server, storage group, and mailbox database; we do this by clicking the Motion Mailbox link in the Activeness pane, bringing up the Movement Mailbox Wizard Introduction page, shown in Effigy 3.11. Here nosotros specify the server, storage group, and mailbox database the respective mailbox should exist moved to. When you lot take washed so, click Next.

Figure three.eleven. The Movement Mailbox Wizard Introduction Folio

On the Move Options page, nosotros tin specify how the mailboxes that comprise corrupted messages should exist managed. We can configure the Movement Mailbox Wizard to skip any mailboxes containing one or more corrupted messages or simply let information technology skip corrupted letters (Figure iii.12). If we select the latter, we have even more than granular control and can specify the maximum number of messages to skip before the mailbox move should be cancelled. In this example, nosotros choose Skip the mailbox and click Next.

Figure 3.12. Move Mailbox Magician Options

Nosotros're now taken to the Move Schedule page shown in Figure 3.thirteen, where we can specify when the mailbox movement should occur besides as the maximum length of time the motility should run earlier information technology should be cancelled. The idea behind the Movement Mailbox Schedule pick is to permit you to schedule the mailbox moves to occur during nonworking hours. In this example, we select Immediately and click Adjacent.

Figure iii.13. The Move Mailbox Magician Schedule Page

Side by side we are taken to the Move Mailbox page (encounter Effigy 3.14), where we tin can verify that the parameters for the mailbox motility are correct before the actual movement takes place. When you're set, click Move.

Figure 3.fourteen. The Move Mailbox Wizard Summary Page

Depending on the size of the mailbox, you lot will need to accept a little patience while the move takes place. The Motility Mailbox Wizard needs to first open the source mailbox and so create a destination mailbox on the target database. Just then does it commencement to motility the contents of the mailbox, completing its chore past finally deleting the source mailbox and closing its connection. When the mailbox has been moved successfully, you'll be taken to the Completion folio, where you can see the CMDlet also as the parameters used to move the mailbox (encounter Figure three.fifteen). Click Cease to go out the Move Mailbox Magician.

Figure 3.xv. The Move Mailbox Wizard Completion Page

Note

The Substitution 2007 Move Mailbox Wizard is the tool yous should employ for moving legacy mailboxes from Substitution 2000 or 2003 Server to an Exchange 2007 Mailbox Server.

To motion a mailbox using the European monetary system, y'all can use the Motion-Mailbox CMDlet. To go a listing of bachelor parameters for this CMDlet, type Get-Help Move-Mailbox in the Ems.

Read full affiliate

URL:

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

Moving from Exchange v.5 to Exchange 2003

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

vii.ix.1 The Substitution five.5 to Exchange 2003 upgrade approach

You cannot perform an in-identify upgrade from an Exchange five.five server to an Substitution 2003 server. Even if you endeavour to do and then, the Commutation 2003 Setup program volition instruct you that it cannot go on. This is different from the procedure that you could have used to upgrade an Substitution v.5 server to Exchange 2000, where an in-place upgrade was possible.

The alternative, and only recommended, method for migrating an Exchange v.five server to Exchange 2003 is to utilize the Motility Mailbox Wizard approach. Essentially, this arroyo involves installing an Exchange 2003 server into the aforementioned Substitution v.v site equally the Substitution v.5 server from which yous want to migrate mailboxes. You then movement all mailboxes from the Exchange five.5 server onto the Commutation 2003 server, ultimately decommissioning the Substitution five.v server when all mailboxes accept been moved off. One of the requirements that must be in place before whatsoever such Commutation 2003 servers can be installed into the Exchange 5.5 site is that an Active Directory Connector environment must already exist in place. This is the aforementioned approach that tin can besides be used for Exchange 5.five to Exchange 2000 migration.

Substitution 2000 servers can exist directly in-place upgraded to Exchange 2003, so if you actually must perform an in-place upgrade on an Commutation 5.5 server—perchance because you lot don't have enough actress or new hardware to employ the Movement Mailbox Magician approach—so y'all can perform an in-place upgrade from Substitution 5.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 affect of lack of service availability on users. However, in some cases it may be admittedly the only approach you tin can take. Recollect that after such a series of upgrades, it is of the utmost importance to take new backups of the Exchange databases. You should actually perform two backups in this scenario: one immediately subsequently the upgrade from Exchange five.5 to Exchange 2000 and another afterward the upgrade from Exchange 2000 to Exchange 2003.

Although upgrading from Exchange v.5 in place to Exchange 2000 and and so to Exchange 2003 is one of the most intuitive means past which to go Exchange 2003 deployed, it is as well the most complicated, time-consuming, and least appealing approach. This section covers what'south involved in upgrading an Exchange 5.5 server to Exchange 2000. Building on this, and covered later in this book, we'll discuss upgrading an Commutation 2000 server to Substitution 2003. Allow'south await at the process of getting to Commutation 2000 in the offset instance.

Read full chapter

URL:

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

Moving from Exchange five.v to Exchange 2003

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

8.11 Summary

If y'all are already familiar with Substitution five.5–to–Substitution 2000 migration, then there is very niggling that's new with Exchange 5.five–to–Exchange 2003 migration. The same principles and tools are used today equally yesterday. Furthermore, migrating from Exchange 5.v is straightforward, because it's simply a thing of creating an interoperability environment with the Active Directory Connector, and then using the Move Mailbox Wizard to move data: In that location'due south no real determination to be fabricated nearly upgrading or moving!

The possibility of discovering duplicate objects in your Agile Directory during or afterwards a migration to Exchange 2003 is a very real one. The Agile Directory Cleanup Magician provides an invaluable way to detect and merge these troublesome duplicates, while preserving aspect and access control data, besides every bit ensuring the integrity of groups and distribution lists.

Of course, the Active Directory Cleanup Magician is not all-powerful. It can't merge objects between forests. Nor can it merge enabled objects in dissimilar domains within the same wood (you must movement them into the same domain first). It can't merge ii objects that both have Substitution mailboxes associated with them: That'due south an entirely different problem! And it tin can't merge ii objects that are both post enabled: Which mail address would it choose? Although it reduces many migration headaches, it should not be used as an alibi for sloppy Exchange five.5 and Windows NT4 account data synergy or carefree migration practices. Take the time up front before any migration activity to clean upward 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 Magician finding a match. By selecting the right migration tools for the task and careful planning of your move to Exchange 2003, yous may go away with never having to apply the Active Directory Cleanup Wizard at all. Prevention is always better than cure.

Read full chapter

URL:

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

Managing Recipients in Exchange 2007

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

Solutions Fast Track

Managing Recipients Using the Exchange 2007 Management Panel

Management of recipients in Exchange Server 2007, too equally their Exchange-related backdrop, has been moved dorsum into the Exchange Direction Panel (EMC) in add-on to the Commutation Management Trounce (European monetary system), both of which are based on Windows PowerShell. This means that all direction of Exchange recipient objects should be modified from within the EMC or European monetary system, non using the ADUC snap-in.

Nosotros have 4 recipient type subnodes below the Recipient Configuration work middle. In club, nosotros accept a Mailbox, a Distribution Grouping, a Mail Contact, and a Disconnected Mailbox node.

Each blazon of recipient object has its own individual icon as well as recipient type clarification due to the fact that they now are explicit and not implicit, as was the instance in Exchange Server 2003. This is a squeamish addition because information technology makes it then 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.

Considering Commutation 2007 uses explicit mailbox recipient types, information technology'due south possible to create a search filter that lists all room mailboxes, for example, or possibly all legacy mailboxes, for that thing. List all resource mailboxes in the ADUC snap-in dorsum in Exchange 2000 or 2003 using a search filter was not a trivial process; information technology required you to use custom attributes considering in that location was no other mode to differentiate resource mailboxes from ordinary mailbox-enabled user accounts.

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

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

Dynamic distribution groups, which were known equally query-based distribution groups in Commutation 2003, provide the same type of functionality as ordinary distribution groups, but instead of manually adding members to the group's membership list, you tin apply a set of filters and conditions that you predefine when creating the group to derive its membership.

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

When you either disable or remove a mailbox, that mailbox will be marked for deletion but will not exist automatically deleted. Instead, information technology volition be kept in the respective mailbox database for the number of days specified on the mailbox database Properties page (nether the Limits tab), called "Keep deleted mailboxes for," more than commonly referred to as mailbox retentiveness. Like Substitution 2000 and 2003, Substitution 2007 will, by default, go along deleted mailboxes for 30 days before they are purged (permanently deleted).

Managing Recipients in a Coexistence Environment

During a transition from Commutation 2000/2003 to Exchange 2007, deploying Exchange 2007 server into your existing Substitution arrangement can have 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 menses of time.

Although y'all have the choice of managing Exchange 2007 mailbox and mail-enabled users using the ADUC snap-in, it isn't supported and will result in Exchange 2007 mailboxes that might not be fully functional. In improver, you lot should opt to utilize the Exchange 2007 tools for moving Exchange 2000/2003 user mailboxes.

The infamous Recipient Update Service (RUS), which most of united states of america know from Exchange 2000 and 2003, is no longer part of the Exchange 2007 production. RUS was responsible for stamping e-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 up. With Substitution 2007, the RUS (and thereby the asynchronous behavior used to provision objects) has been replaced past a new synchronous process, the EmailAddressPolicy CMDlet, used to stamp the e-mail accost onto objects immediately.

Granting Access and/or SendAs Permissions to a Mailbox

In some situations, i or more users might demand to be granted permissions to access another user'south mailbox. This could exist a more temporary access during vacations, motherhood leave, or other reasons, where one or more users need to take over the work of the user who will be absent. Information technology could also be a more permanent access, where a secretarial assistant needs to access her dominate'southward mailbox, for example. Another reason could be that all users in a particular department (such as a helpdesk) demand a shared mailbox.

Creating a Custom Recipient Management Console

Depending on the system, at times you might desire to create an Commutation 2007 Management Console that shows only the Recipient Configuration piece of work middle node. This is especially true in situations where you have a helpdesk that is used to having a customized ADUC console snap-in that provides the corresponding OUs holding the Exchange user objects they were to administrate.

You can create isolated Management Consoles for the Arrangement Configuration, Server Configuration, and Toolbox piece of work center nodes. You can do this by following the same steps simply opening a new console window past right-clicking the corresponding work centre node. If you accept both the Substitution 2007 Tools and the Windows AdminPak installed on a server or workstation, you can even create a single panel with access to both the ADUC snap-in and the Commutation 2007 Direction Panel.

Recipient Filtering in Exchange 2007

If you lot have already deployed and/or are planning to deploy Exchange 2007 in an organization consisting of several thousand recipients, you can apace lose the authoritative overview. This is where recipient filtering comes into the picture. Past creating a filter using either the EMC or the European monetary system, you will be able to observe the recipient or prepare of recipients yous're looking for in a thing of seconds.

Creating a recipient filter is washed past selecting the Recipient Configuration work center node or the particular recipient subnode.

Read full chapter

URL:

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

Interorganization Migrations

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

9.5.7 Interorganization mailbox migration

Providing interoperability past means of interorganization mail connections—which are straightforward to do for whatever surround—and directory synchronization just provides the get-go part of the interorganization migration. The adjacent challenge comes with actually moving mailbox contents from a server in a source Commutation 5.5 arrangement to the target Exchange 2000/2003 organization.

Microsoft provides the Move Mailbox Wizard for intraorganization moves, and the Commutation Server Migration Wizard and ExMerge tin also exist used. The latter tools work for interorganization moves, just they are both i-shot tools and provide no ongoing or gradual mailbox synchronization. This is another surface area where third-party migration tools ordinarily excel.

Much like the directory synchronization, mailbox synchronization is implemented using agents, three in this case: the Mailbox Source Agent (MSA), the Transmission Agent (TA), and the Post Target Agent (MTA). This is shown graphically in Figure nine-23.

Effigy 9-23. Agent Architecture for Mailbox Synchronization

The MSA resides on the source Exchange v.5 server, which monitors the synchronization status of mailboxes. You lot need one MSA per Commutation 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 then compressed in a unmarried file, known as the PRV file. The MSA and so transfers the aggregate PRV file to the TA, also installed on the Commutation 5.5 server, which transfers mailbox data to the target Exchange 2000/2003 server. If there are multiple target servers to receive data, so in that location volition be multiple PRV files. The TA will ship the advisable PRV file directly 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 information files (which is another advantage over the default Microsoft tools) so that the bodily 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 existence consolidated to centralized locations. (This trend is condign more widespread with the advent of Outlook 2003'due south cached working mode, which makes centralized, consolidated Exchange information centers with outlying remote clients all the more attractive and constructive.) You tin explicitly choose whether to utilise compression, and if y'all do, you tin choose the compression level. No compression incurs more network traffic but is faster; loftier compression incurs less network traffic but is slower.

Correct-clicking the Mailbox Synchronization particular in the Console and selecting Add Mailbox Synchronization Job will set upwardly all of the requisite agents on the source and target servers. Each Job identifies the single source Exchange v.5 server and the unmarried target Exchange 2000/2003 server. Although y'all are prompted to define the Storage Grouping and Mailbox Store on which the mailboxes are to be synchronized, you should select those 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 consolidation. A Collection is a group of mailboxes that will exist synchronized together. Each Collection retains its own settings and priority. You can ascertain when the migration for a item Collection will have place. A Synchronization Job can handle multiple Collections. A Collection will only begin processing if all higher-priority Collections take fully completed their processing.

When y'all run through the Mailbox Synchronization Job Wizard, you initially define whether yous want to use Collections at all and some full general settings effectually Collections (i.e., an initial first Collection, one Collection per target server mailbox store, or but distributing a fixed number of mailboxes into an arbitrary Collection name). This is shown in Figure 9-24.

Figure ix-24. Creating Mailbox Collections with the Mailbox Synchronization Job Wizard

Electing to apply Collections ways that you lot have much granularity in selecting which mailboxes will be moved at any given fourth dimension. With the Wizard y'all can add individual mailboxes to a given Collection or you tin select any number of Commutation 5.5 recipient containers equally the source, as shown in Figure 9-25. You can add additional Collections to a Chore at whatever time through the Console interface. With this interface you lot configure additional settings such as the Collection priority and commencement and end times. By default, the synchronization is fix to get-go immediately, simply you tin define exactly when you would like synchronization to start for each Collection. And by default, the synchronization process is active for about 4 weeks from the default start time. Once more, you can change this as required. You may also add mailboxes to a collection using an external file (e.thou., CSV formatted), which is useful if the Exchange migration is function of a wider migration projection in your environment and you must align your Commutation migration with other migration activities.

Figure 9-25. Adding Source Mailboxes to a Drove

All of this means that you need to carefully plan and schedule your unabridged migration and consolidation strategy, and in fact, schedule the whole process well in accelerate of any actual migration activity. With this approach you lot tin can gradually migrate users at the pace that suits you and imposes the to the lowest degree corporeality of load on the network and other terminate systems.

Getting the mailbox contents in sync between the source Commutation v.5 organization and the target Commutation 2000/2003 organizations is but one footstep in the mailbox migration procedure. The next stage is to decommission the Exchange 5.5 mailbox and take the Exchange 2000/2003 mailbox become the primary mailbox for the user. This process is known every bit mailbox switching.

Behind the scenes, the mailbox switching process is relatively trivial. Ii things happen. On the Substitution 5.5 server, the user's mailbox is modified so that an alternate recipient is defined for the mailbox. Any mail service 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 place. Thus any mail delivered to the redirection custom recipient is relayed to the Commutation 2000/2003 mailbox in the target organization. In the target organization the redirection on the Exchange 2000/2003 mailbox to the redirection contact is removed. Effigy 9-26 shows the alternate recipient modification to an Exchange five.v mailbox.

Figure ix-26. Exchange five. 5 Mailbox with Redirection Custom Recipient

Switching can be performed manually past selecting users already synchronized and associated with a particular Synchronization Task, right-clicking, and choosing the option to switch. Multiple mailboxes may be selected and switched at the aforementioned time. 3rd-political party migration tools can exist configured so that when mailboxes are switched, suitable messages are sent to user mailboxes informing them that they have been migrated.

Collections can as well exist configured then that fully synchronized user mailboxes are automatically switched. This is washed by setting the backdrop on the Collection. Some heavily used mailboxes may never get fully synchronized at a given point in fourth dimension and so long as mail service continues to be delivered into the source mailbox. For this reason, y'all tin can automatically have mailboxes switched even if they are slightly out of sync. Y'all specify the threshold (in KB) that you will tolerate, and immediately afterwards the mailbox is switched, whatsoever unsynchronized content is brought across to the target server.

Notation also that mailboxes can exist unswitched past but toggling the switched setting, so that users incurring issues with their new Substitution 2000/2003 mailbox can be just and quickly moved back to Exchange 5.5.

With an interorganization migration, users' MAPI profiles are invalidated when a user is moved to an Commutation server in a new organisation. Third-party migration tools usually 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 set by the mailbox switch procedure. Thus, the motility is relatively transparent to the end user.

Read full chapter

URL:

https://world wide web.sciencedirect.com/scientific discipline/commodity/pii/B9781555583163500117

Interorganizational Migrations

Kieran McCorry , in Microsoft Substitution 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 do in whatsoever environment—and directory synchronization only provides the get-go part of the interorganizational migration. The next challenge comes with actually moving mailbox contents from a server in a source Commutation v.five organization to the target Exchange 2000/2003 organization.

Microsoft provides the Move Mailbox Magician for intraorganizational moves; the Exchange Server Migration Wizard and ExMerge tin besides be used. The latter tools piece of work for interorganizational moves, merely they are both ane-shot tools and provide no ongoing or gradual mailbox synchronization. This is another area where tertiary-party migration tools ordinarily excel.

Much like directory synchronization, mailbox synchronization is implemented using agents, three in this instance: the Mailbox Source Amanuensis (MSA), the Transmission Agent (TA), and the Mail Target Agent (MTA). This is shown graphically in Figure 7.23.

Figure 7.23. Amanuensis architecture for mailbox synchronization.

The MSA resides on the source Exchange v.5 server, which monitors the synchronization status of mailboxes. You need i MSA per Exchange 5.v 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 so compressed in a single file, known as the PRV file. The MSA then transfers the aggregate PRV file to the Transmission Agent, too installed on the Substitution 5.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 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 procedure 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, since servers distributed over a broad area network are ofttimes beingness consolidated to centralized locations. (This trend is becoming more than widespread with the advent of Outlook 2003's cached working mode, which makes centralized, consolidated Exchange data centers with outlying remote clients all the more attractive and effective.) Yous can explicitly choose whether or non to use compression, and, if y'all do, you tin can choose the pinch level. No compression incurs more network traffic but is faster; high compression incurs less network traffic merely is slower.

Right-clicking the "Mailbox Synchronization" detail in the console and selecting "Add together Mailbox Synchronization Task" will set up all the requisite agents on the source and target servers. Each job identifies the single source Exchange five.v server and the unmarried 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, 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 power of mailbox synchronization and, indeed, consolidation. A drove is a group of mailboxes that volition be synchronized together. Each collection retains its own settings and priority. You can define when the migration for a detail collection will take identify. A synchronization job can handle multiple collections. A collection volition only begin processing if all higher-priority collections accept fully completed their processing.

When you run through the Mailbox Synchronization Job Wizard, you initially ascertain whether y'all want to use collections at all and some general settings around collections; that is, do you want to use an initial showtime collection or 1 collection per target server mailbox store, or are you lot merely distributing a fixed number of mailboxes into an capricious collection name. This is shown in Figure 7.24.

Figure 7.24. Creating mailbox collections with the Mailbox Synchronization Chore Magician.

Electing to use collections ways that y'all have much granularity in selecting which mailboxes will be moved at any given time. With the magician you tin add individual mailboxes to a given collection, or yous tin can select whatsoever number of Commutation 5.5 recipient containers as the source, as shown in Figure 7.25. Yous can add boosted collections to a chore at any time through the panel interface. With this interface, you configure additional settings such as the collection priority and beginning and end times. Past default, the synchronization is set to showtime immediately, but you tin can define exactly when you would like synchronization to start for each collection. And, past default, the synchronization process is active for about iv weeks from the default offset fourth dimension. Once more, yous tin can modify this as required. You may also add mailboxes to a collection using an external file (east.g., CSV formatted); this is useful if the Exchange migration is part of a wider migration project in your surround, and you must align your Exchange migration with other migration activities.

Figure 7.25. Adding source mailboxes to a drove.

All of this means that y'all demand to plan and schedule your entire migration and consolidation strategy carefully; in fact, yous schedule the whole process well in advance of any actual migration activity. With this approach, you can gradually migrate users at the footstep that suits you; it as well imposes the least amount of load on the network and other end systems.

Getting the mailbox contents in synch between the source Exchange five.5 system and the target Exchange 2000/2003 organizations is just i step in the mailbox migration process. The next stage is to decommission the Exchange v.5 mailbox and accept the Substitution 2000/2003 mailbox become the principal 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 5.5 server, the user's mailbox is modified and then that an alternate recipient is defined for the mailbox. Any post at present sent to that mailbox is redirected to the alternate recipient. The specified alternating recipient is actually the redirection custom recipient created when directory synchronization took place. Thus, any mail service delivered to the redirection custom recipient is relayed to the Commutation 2000/2003 mailbox in the target organization. In the target organisation, the redirection on the Substitution 2000/2003 mailbox to the redirection contact is of course removed. Figure 7.26 shows the alternate recipient modification to an Commutation 5.5 mailbox.

Effigy 7.26. Exchange v.5 mailbox with redirection custom recipient.

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

Collections can also be configured so that fully synchronized user mailboxes are automatically switched. This is done by setting the backdrop on the drove. Some heavily used mailboxes may never become fully synchronized at a given bespeak in time then long as post continues to be delivered into the source mailbox. For this reason, you tin 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, whatever unsynchronized content is brought across to the target server.

Notation too that mailboxes tin can be unswitched past simply toggling the switched setting so that users incurring issues with their new Commutation 2000/2003 mailbox tin can be just and quickly moved back to Commutation 5.5.

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

Read full chapter

URL:

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