Suspender solicitudes de movimiento

Puede usar el cmdlet Suspend-MoveRequest para suspender una solicitud de movimiento en cualquier momento posterior a la creación de dicha solicitud pero antes de que llegue al estado de CompletionInProgress, Completing o Completed. También puede suspender de forma automática una solicitud de movimiento con el cmdlet New-MoveRequest con el parámetro SuspendWhenReadyToComplete.

  Usar el Shell para suspender una solicitud de movimiento

Deberá tener asignados permisos antes de poder llevar a cabo este procedimiento. Para ver qué permisos necesita, consulte el contenido "Movimientos de buzones de correo" en el tema Permisos de buzones.

Ee364735.note(es-es,EXCHG.140).gifNota:

No puede usar la EMC para suspender una solicitud de movimiento.

En este ejemplo, se suspende una solicitud de movimiento para el buzón de correo de Antonio Bermejo y se incluye el comentario de suspensión "Movimiento suspendido por solicitud del usuario. No reanudar hasta el domingo".

Suspend-MoveRequest -Identity 'Tony@humongousinsurance.com' -SuspendComment "Move suspended per user request. Do not resume until Sunday."

En este ejemplo, se suspenden todas las solicitudes de movimiento que tienen la base de datos de destino DB02 y se incluye el comentario de suspensión "Pendiente de aprobación final".

Get-MoveRequest -TargetDatabase DB02 | Suspend-MoveRequest -SuspendComment "Pending final approval."

Para obtener información detallada acerca de la sintaxis y los parámetros, consulte Suspend-MoveRequest y Get-MoveRequest.

  Usar el Shell para suspender automáticamente una solicitud de movimiento

Deberá tener asignados permisos antes de poder llevar a cabo este procedimiento. Para ver qué permisos necesita, consulte el contenido "Movimientos de buzones de correo" en el tema Permisos de buzones.

En este ejemplo, se suspende de forma automática una solicitud de movimiento cuando la solicitud alcanza el estado ReadyToComplete.

New-MoveRequest -Identity Ayla@alpineskihouse.com -TargetDatabase DB05 -SuspendWhenReadyToComplete

Quitar o borrar solicitudes de movimiento

Puede quitar o desactivar solicitudes de movimiento.

Dd351276.note(es-es,EXCHG.140).gifNota:

Para ver todas las solicitudes de desplazamiento en un entorno de varios dominios en la consola de administración de Exchange, se debe modificar el ámbito de destinatario para ver el bosque completo. Para obtener más información, consulte Cambiar el ámbito de destinatario.

  Requisitos previos

Antes de que lleve a cabo los procedimientos que se detallan en este tema, es importante que entienda la diferencia entre quitar y borrar una solicitud de movimiento.

  • Quitar una solicitud de movimiento   Cuando crea una solicitud de movimiento, la puede quitar en cualquier momento antes de que alcance el estado CompletionInProgress, Completing, Completed with Error o Completed. Cuando se quita una solicitud de movimiento que está en progreso, la replicación de buzones se detiene y la réplica se elimina de la base de datos de destino. Si quita una solicitud de movimiento y más tarde decide mover el buzón, deberá comenzar el proceso de solicitud de movimiento desde el principio.
  • Borrar una solicitud de movimiento   Cuando una solicitud de movimiento alcanza el estado Completed o Completed with Error, debe borrarla para eliminar el marcador InTransit del buzón. No podrá mover el buzón de nuevo hasta que haya borrado la solicitud de movimiento anterior. Para obtener más información acerca del estado Completed with Error, consulte Solución de problemas de los movimientos de buzón.

  Usar la EMC para quitar una solicitud de movimiento

Deberá tener asignados permisos antes de poder llevar a cabo este procedimiento. Para ver qué permisos necesita, consulte el Entrada "Movimientos de buzones" en el tema Permisos de buzones.

  1. En el árbol de la consola, vaya a Configuración de destinatarios > Solicitud de movimiento.
  2. En el panel de resultados, seleccione un destinatario con un Estado de solicitud de movimiento distinto a Completion in Progress (Finalización en progreso) o Completed (Completado).

    Dd351276.note(es-es,EXCHG.140).gifNota:

    Puede seleccionar varios destinatarios en el panel de resultados.

  3. En el panel de acciones, haga clic en Quitar solicitud de movimiento.
  4. Aparece una advertencia para que confirme si desea quitar la solicitud de movimiento. Haga clic en .

  Usar la EMC para borrar una solicitud de movimiento

Deberá tener asignados permisos antes de poder llevar a cabo este procedimiento. Para ver qué permisos necesita, consulte el Entrada "Movimientos de buzones" en el tema Permisos de buzones.

  1. En el árbol de la consola, vaya a Configuración de destinatarios > Solicitud de movimiento.
  2. En el panel de resultados, seleccione un destinatario con un Estado de solicitud de movimiento de Completed (Completado) o Completed with Error (Completado con error).

    Dd351276.note(es-es,EXCHG.140).gifNota:

    Puede seleccionar varios destinatarios en el panel de resultados.

  3. En el panel de acciones, haga clic en Desactivar solicitud de movimiento.
  4. Aparece una advertencia para que confirme si desea desactivar la solicitud de movimiento. Haga clic en .

  Usar el Shell para quitar o desactivar una solicitud de movimiento

Deberá tener asignados permisos antes de poder llevar a cabo este procedimiento. Para ver qué permisos necesita, consulte el Entrada "Movimientos de buzones" en el tema Permisos de buzones.

En este ejemplo, se quita la solicitud de movimiento del buzón de Vanessa García.

Remove-MoveRequest -Identity 'Ayla@humongousinsurance.com'

En este ejemplo se quita la solicitud de movimiento de todos los buzones con el estado Completed.

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

Para obtener más información acerca de la sintaxis y los parámetros, consulte Remove-MoveRequest y Get-MoveRequest.

Prepare Mailboxes for Cross-Forest Moves Using Sample Code

Microsoft Exchange Server 2010 supports an online mailbox move using the New-MoveRequest cmdlet to move a mailbox from a source Exchange forest to a target Exchange forest. To run New-MoveRequest, a mail user must exist in the target Exchange forest with a minimum set of Active Directory attributes.

With the sample code described in this topic, you can create the required mail user in the target Exchange forest by customizing your Microsoft Identity Lifecycle Manager 2007 deployment. You can download the sample code from the Prepare for Online Mailbox Move download page.

  Prerequisites

To run this sample code, you need ILM 2007 FP1 SP1. See KB 97779 1 (ILM 2007 FP1 SP1) to download the feature pack. You also need the following:

  • A source forest running Exchange 2003, Exchange 2007 or Exchange 2010, where the mailbox currently resides
  • A target forest with Exchange 2010 installed, where the mailbox will be moved to

  Contents of Sample Code

Open “Microsoft.Exchange.Sample.OneWayGALSync.sln” to view the sample code in Visio Studio 2008. The sample code includes the following:

  • “Microsoft.MetadirectoryServicesEx.dll” is the binary file that is shipped with ILM 2007 FP1 SP1 under “\Program Files\Microsoft Identity Integration Server\Bin\Assemblies”. It is referenced by the sample code.
  • “OneWaySync.xml” is referenced by the sample code.
  • ILMServerConfig folder contains the ILM configuration files for the source MA, target MA, and the MV.
  • “Microsoft.Exchange.Sample.OneWayGALSync.MARules.dll” and “Microsoft.Exchange.Sample.OneWayGALSync.MVRules.dll” (built from the sample code) are under “\obj\Debug”

  Installation

  1. Copy “OneWaySync.xml”, “Microsoft.Exchange.Sample.OneWayGALSync.MARules.dll” and “Microsoft.Exchange.Sample.OneWayGALSync.MVRules.dll” to the ILM Extensions folder “\Program Files\Microsoft Identity Integration Server\Extensions” on the ILM Server.
  2. On the ILM Server, edit the file “OneWayGALSync.xml” you just copied to the ILM Extensions folder in step 1 to specify the distinguishedName (DN) of the TargetOU container in the target Exchange forest that you want to create the synchronized mail users to. You can use LDP.exe or ADSIEdit.exe to browse, copy, paste if you don’t know what it is.

    Ee861124.note(es-es,EXCHG.140).gifNota:

    If you are using this sample together with ILM Galsync2007, then this container should be excluded from the list of containers managed by Galsync2007.

  3. On the ILM Server in ILM Identity Manager Console, go to File > Import Server Configuration to import the ILM server configuration from the folder ILMServerConfig. This action will import two Active Directory MAs along with Metaverse schema and provisioning rule.

    Ee861124.note(es-es,EXCHG.140).gifNota:

    During the import you will need to provide the forest name and credentials and match the partitions of the imported ADMA to the partition name in your configuration for both the source and target ADMAs.

    Aprovisionamiento de Exchange 2010 del agente de administración

  4. For ADMA to support the Exchange 2010 target forest, on the Configure Extensions screen, select Provision for Exchange 2010 and provide the remote Windows PowerShell URI (of an Exchange 2010 CAS server).

    Ee861124.note(es-es,EXCHG.140).gifNota:

    The credential that you supplied to connect to the Exchange 2010 target forest must have the appropriate level of RBAC permission to call the UpdateRecipient cmdlet.

  5. On the ILM Server, in ILM Identity Manager on the Management Agents tab, open the Properties for the Source Forest Management Agent. Select the Configure Directory Partitions wizard page, and then click Containers to select the container that will contain the mailboxes you will be moving to the target forest. Clear the selections for all other containers, that is, scope the MA to only manage this one container. Similarly, for the target forest MA, select the container to which MEUs will be provisioned, that is, the TargetOU specified in step 2.

    Ee861124.note(es-es,EXCHG.140).gifNota:

    If you’re using this sample together with ILM Galsync2007, both these containers should be excluded from the list of containers managed by Galsync2007.

  6. Perform an initial Full Import (stage only) on the Target MAs so ILM can discover the TargetOU specified in step 2.

  Sync Cycle

The following steps describe how to create the required mail user in the target Exchange forest so that New-MoveRequest can be run to perform an online mailbox move.

  1. In the source forest, use EMC to create mailbox users in, or ADUC to move existing mailbox users to, the container selected in #4.
  2. Perform Delta Import and Delta Sync run on the Source MA to discover the mailboxes added to the source container, and provision mail users to the Target MA.
  3. Perform Export run on the Target MA to export the mail users provisioned by #7 to the target AD.
  4. Perform Delta Import on the Target MA to confirm the changes exported in #8.
  5. In the target forest use the New-MoveRequest cmdlet to move mailboxes from the source forest.

Prepare Mailboxes for Cross-Forest Moves Using the PrepareMoveRequest.ps1 script in the Shell

In Exchange 2010, moving a mailbox has been separated into two distinct parts:

  • Preparing the Active Directory object
  • Data migration

This sample Windows Powershell script supports the first part by synchronizing mailbox users from an Exchange 2003, Exchange 2007 and Exchange 2010 source forest to Exchange 2010 target forests as mail enabled users. This is accomplished by synchronizing Active Directory attributes in the online help and by calling the Update-Recipient cmdlet to turn the target objects into mail enabled users.

You can download the sample Windows Powershell script from the Prepare for Onli n e Mailbox Move download page. For more information about using and writing scripts, see Scripting con el Shell de administración de Exchange.

  Prerequisites

To run this sample script, you need the following:

  • a source forest running Exchange 2003, Exchange 2007 or Exchange 2010, where the mailbox currently resides
  • a target forest with Exchange 2010 installed, where the mailbox will be moved to

  Using the PrepareMoveRequest.psi script

The script should be run from Exchange Management Shell on an Exchange 2010 server role in the target Exchange 2010 forest. The script copies the mailbox attributes from the source forest.

The following command runs the prepareMoveRequest.ps1 script:

prepareMoveRequest.ps1 -Identity JohnSmith@Fabrikan.com -RemoteDomainController DC001.Fabrikam.com -RemoteForestCredential DouglassB@Fabrikam.com -ForestTrust $true

The following table lists the parameter set for the script.

Parameter

Required

Description

Identity

Required

The Identity parameter specifies the identify of the mailbox in the source forest. Identity can be any of the following:

  • Cn
  • Alias
  • ProxyAddress
  • objectGuid
  • displayname

RemoteDomainController

Required

The RemoteDomainController parameter specifies the domain controller of the source forest where the mailbox resides.

RemoteForestCredential

Required

The Crenditial parameter specifies the administrator with permissions to copy data from the Active Directory of the source forest.

LocalForestDomainController

Optional

The DomainController parameter specifies the domain controller of the target forest where the mail enabled user will be created.

LocalForestCredential

Optional

The LocalForestCrendiatial parameter specifies the administrator with permissions to write data to the Active Directory of the target forest.

TargetOU

Optional

The TargetOU parameter specifies where the target mail enabled user will be created.

LinkedMailUser

Optional

The LinkedMailUser parameter accepts a $true or $false value. This parameter is set to $false by default. If set to $true, this setting creates a linked target mail enabled user with the source mailbox user.

MailboxDeliveryDomain

Optional

The MailboxDeliveryDomain parameter specifies an authoritative domain of the target forest so that the script can pick the correct source mailbox user’s proxyAddresses as the target mail enabled user’s targetAddress.

By default, the primary SMTP address of the source mailbox user is set as the targetAddress of the target mail enabled user.

UseLocalObject

Optional

If the script detects an object in the local forest that conflicts with the to be created mail enabled user, you can use the UseLocalObject parameter to convert the existing local object to the required target mail enable user.

Ee861103.note(es-es,EXCHG.140).gifNota:

Make sure that you use two separate credentials for the local forest, and the remote forest when calling this script.

  Examples

  EXAMPLE 1

This example provisions a single mail enabled user.

prepareMoveRequest.ps1 -Identity RobertJames@Contoso.com -RemoteDomainController DC001.Fabrikam.com -RemoteForestCredential DouglassB@Fabrikam.com -ForestTrust $true -LinkedMailUser $true

  EXAMPLE 2

The script supports pipelining if you supply the list of identities as shown below:

"IanB@Contoso.com", "JoeSm@Contoso.com" | prepareMoveRequest.ps1 -Identity RobertJames@Contoso.com -RemoteDomainController DC001.Fabrikam.com -RemoteForestCredential DouglassB@Fabrikam.com -ForestTrust $true

  EXAMPLE 3

You can generate a CSV file containing a list of mailbox identities from the source forest, which allows you to pipe the content of this file into the script to bulk create the target mail enabled users.

For example, the content of the CSV file can be:

Identity:

Ian@contoso.com

John@contoso.com

Rachel@contoso.com

This example calls a CSV file to bulk create the target mail enabled users.

Import-Csv Test.csv | prepareMoveRequest.ps1 -Identity RobertJames@Contoso.com -RemoteDomainController DC001.Fabrikam.com -RemoteForestCredential DouglassB@Fabrikam.com -ForestTrust $true

  Duplicate Target Mail Enabled Object

When the script attempts to create a target mail enabled user from the source mailbox user, and it detects a duplicate local mail enabled object, it uses the following logic:

  • If source mailbox user’s masterAccountSid equals any target object’s objectSid or masterAccountSid
    • If the target object is not mail enabled, return error since the script doesn’t support converting a non mail enabled object to a mail enabled user.
    • If the target object is mail enabled, the target object is a duplicate.
  • Or if an address in the source mailbox user’s proxyAddresses (smtp/x500 only) equals an address in a target object’s proxyAddresses (smtp/x500 only), then the target object is a duplicate.

The script will prompt the user about the duplicate objects.

If the target mail enabled object is a mail enabled user or contact, which is most likely create by a cross-forest (Identity Lifecycle Management 2007 Service Pack 1 based) GALSync deployment, then the user can rerun the script with ‘-UseLocalObject’ parameter to use the target mail enabled object for mailbox migration.

  Mail Enabled User

If the target object is a mail enabled user, the script copies the following attributes from the source mailbox user to the target mail enabled user:

  • msExchMailboxGUID
  • msExchArchiveGUID
  • msExchArchiveName

If LinkedMailUser parameter is set, the script copies the source objectSid/masterAccountSid.

  Mail Enabled Contact

If the target object is a mail enabled contact, the script will delete the existing contact and copy all of its attributes to a new mail enabled user. The script will also copy the following attributes from the source mailbox user:

  • msExchMailboxGUID
  • msExchArchiveGUID
  • msExchArchiveName
  • sAMAccountName
  • userAccountControl (set to 514 //equivalent to 0x202, ACCOUNTDISABLE | NORMAL_ACCOUNT)
  • userPrincipalName

If LinkedMailUser parameter is set, the script copies the source objectSid/masterAccountSid.

  Sync Back LegacyExchangeDN

When the Update-Recipient cmdlet is called to convert the target object into a mail enabled user, a new LegacyExchangeDN is generated for the target mail enabled user. The script will copy the LegacyExchangeDN of the target mail enabled user as a “x500” address to the proxyAddresses of the source mailbox user.

This ensures proper resolution of recipients when messages are sent between the source and target forests.

Prepare Mailboxes for Cross-Forest Move Requests

Exchange 2010 supports remote mailbox moves via the New-MoveRequest cmdlet. This topic describes the prerequisites for moving a mailbox from one Exchange forest to another Exchange 2010 forest.

Ee633491.note(es-es,EXCHG.140).gifNota:

Exchange 2010 doesn’t support moving an Exchange 2000 mailbox.

In order to run the New-MoveRequest cmdlet to move a mailbox from an Exchange 2003, Exchange 2007 and Exchange 2010 forest to another Exchange 2010 forest, the Exchange 2010 target forest must contain a valid mail enabled user with a specified set of Active Directory attributes.

Ee633491.note(es-es,EXCHG.140).gifNota:

If there is at least one Exchange 2010 Client Access server deployed in the forest, the forest is considered an Exchange 2010 forest.

For more information about remote mailbox moves and remote legacy moves, see Descripción de solicitudes de movimiento.

You can create the mail-enabled user with the required attributes in the target forest via a variety of Active Directory tools.

If you have deployed Identity Lifecycle Manager for cross-forest GAL synchronization, the recommended approach is to do this via ILM 2007 FP1 SP1. See KB 977791 (ILM 2007 FP1 SP1) to download the feature pack. We have created sample code that you can use to learn how to customize ILM to synchronize the source mailbox user and target mail user.

If you created the target mail user using an Active Directory tool other than ILM/MIIS, then you need to call the Update-Recipient <identity> cmdlet to run the Address List service to generate the LegacyExchangeDN for the target mail user. We have created a sample Powershell script that reads from and writes to Active Directory and calls the Update-Recipient cmdlet.

After creating the target mail user, you can then run New-MoveRequest to move the mailbox to the target Exchange 2010 forest.

For more information on remote move requests, see the following topics:

  What Do You Want To Do?

  • Learn about the list of Active Directory user attributes required for a mailbox move request
  • Use a Powershell script to configure Active Directory attributes
  • Use ILM sample code to configure Active Directory attributes

  List of Active Directory user attributes required for a mailbox move

In order to support online move mailbox, the mail user object in the target Exchange 2010 forest must have the following Active Directory attributes.

  Mandatory Attributes

The table below lists the minimum set of attributes that need to be configured in ILM on the target mail user for New-MoveRequest to function correctly.

Mail User’s attributes and required values

Mail User’s Active Directory attribute
Required value

displayName

Copy the corresponding attribute of the source mailbox or generate a new value

Mail

Directly copy the corresponding attribute of the source mailbox

mailNickname

Copy the corresponding attribute of the source mailbox or generate a new value.

msExchArchiveGUID and msExchArchiveName

Directly copy the corresponding attribute of the source mailbox. Attributes are only available if the source mailbox is E2010.

msExchMailboxGUID

Directly copy the corresponding attribute of the source mailbox.

msExchRecipientDisplayType

-2147483642 (decimal) //equivalent to 0x80000006 (hex)

msExchRecipientTypeDetails

128 (decimal) /0x80 (hex)

msExchUserCulture

Directly copy the corresponding attribute of the source mailbox.

msExchVersion

44220983382016 (decimal)

cn

Copy the corresponding attribute of the source mailbox or generate a new value.

proxyAddresses

Copy source mailbox’s proxyAddresses attribute. Additionally, copy source mailbox’s LegacyExchangeDN as an X500 address in the proxyAddresses attribute of the target mail user.

Ee633491.note(es-es,EXCHG.140).gifNota:

The proxyAddresses of the source mailbox user must contain a SMTP address that matches the authoritative domain of the target forest. This will allow New-MoveRequest to properly select the targetAddress of the source mail enabled user (converted from the source mailbox user after mailbox move request is complete) to ensure that mail routing is still functional.

sAMAccountName

Copy the corresponding attribute of the source mailbox or generate a new value.

Need to ensure that it is unique within the target forest domain that the target mail user belongs to.

targetAddress

Set to a SMTP address in the proxyAddresses attribute of the source mailbox.

This SMTP address must belong to the authoritative domain of the source forest.

userAccountControl

Constant: 514 //equivalent to 0x202, ACCOUNTDISABLE | NORMAL_ACCOUNT.

userPrincipalName

Copy the corresponding attribute of the source mailbox or generate a new value. Since the mail user is logon disabled, this userPrincipalName is not used.

  Optional Attributes

Configuring the following attributes are not mandatory for New-MoveRequest to function correctly, but synchronizing them provide a better end-to-end user experience after moving the mailbox. Since the GAL in the target forest will display this target mail user, you should set the following GAL related attributes.

GAL properties

Mail User’s Active Directory attributes
Description

c

Directly copy the corresponding attribute of the source mailbox

co

Directly copy the corresponding attribute of the source mailbox

countryCode

Directly copy the corresponding attribute of the source mailbox

company

Directly copy the corresponding attribute of the source mailbox

department

Directly copy the corresponding attribute of the source mailbox

facsimileTelephoneNumber

Directly copy the corresponding attribute of the source mailbox

givenName

Directly copy the corresponding attribute of the source mailbox

homePhone

Directly copy the corresponding attribute of the source mailbox

info

Directly copy the corresponding attribute of the source mailbox

initials

Directly copy the corresponding attribute of the source mailbox

l

Directly copy the corresponding attribute of the source mailbox

mobile

Directly copy the corresponding attribute of the source mailbox

msExchAssistantName

Directly copy the corresponding attribute of the source mailbox

msExchHideFromAddressLists

Directly copy the corresponding attribute of the source mailbox

otherHomePhone

Directly copy the corresponding attribute of the source mailbox

otherTelephone

Directly copy the corresponding attribute of the source mailbox

pager

Directly copy the corresponding attribute of the source mailbox

physicalDeliveryOfficeName

Directly copy the corresponding attribute of the source mailbox

postalCode

Directly copy the corresponding attribute of the source mailbox

sn

Directly copy the corresponding attribute of the source mailbox

st

Directly copy the corresponding attribute of the source mailbox

streetAddress

Directly copy the corresponding attribute of the source mailbox

telephoneAssistant

Directly copy the corresponding attribute of the source mailbox

telephoneNumber

Directly copy the corresponding attribute of the source mailbox

title

Directly copy the corresponding attribute of the source mailbox

  Linked Attributes

A linked attribute is an Active Directory attribute that references other Active Directory objects in the local forest. You can’t directly copy the linked attribute values from a mailbox in the source forest to a mail user in the target forest. You must find the Active Directory objects in the source forest that the source mailbox attribute refers to. You must find the corresponding Active Directory objects in the target forest for the above-mentioned Active Directory object in the source forest. And then, set the target mail user’s attribute to refer to the Active Directory objects in the target forest.

Linked attributes

Mail User’s Active Directory attributes
Description

altRecipient (and it’s backlinks)

Correspond to the source mailbox’s altRecipient attribute.

deliverAndRedirect

Directly copy the corresponding attribute of the source mailbox. This attribute is a boolean value that should be set along with altRecipient.

Manager (and it’s backlinks)

Correspond to the source mailbox’s manager attribute.

MemberOf (backlinks)

This is the back link of group member attribute.

publicDelegates (and it’s backlinks)

Correspond to the source mailbox’s publicDelegates attribute.

  Linked Mailbox

If you want to move a mailbox to an Exchange 2010 resource forest, the mailbox in the resource forest is a linked mailbox. In this scenario, you will need to create a linked mail user in the (target) resource forest. To create a linked mail user, you need to set the following attributes.

Linked mailbox attributes

Mail User’s Active Directory attributes
Description

msExchMasterAccountHistory

Directly copy the corresponding attribute of the source mailbox.

msExchMasterAccountSid

If the source mailbox has msExchMasterAccountSid, then copy it. Otherwise, copy the source mailbox’s objectSid.

msExchRecipientDisplayType

Constant:-1073741818 (decimal) //equivalent to *unsigned* 0xC0000006.

Ee633491.note(es-es,EXCHG.140).gifNota:

A linked mailbox can only be created if there is forest trust between the source forest and target forest.

If the source object is disabled and the msExchMasterAccountSid is set to self (resource mailbox, shared mailbox) do not stamp anything on the target user. RecipientDisplayType should be set to non ACL-able (second bit).

If the source object is disabled and the msExchMasterAccountSid is not set this is an invalid mailbox.

If the source object is enabled and the msExchMasterAccountSid is set, this is an invalid mailbox.

  Resource Mailbox

If you want to move a resource mailbox to an E2010 forest, you will need to set the following attributes in the table on the target mail user.

Resource mailbox attributes

Mail User’s Active Directory attributes
Description

msExchRecipientDisplayType

If source mailbox is a conference room:

Constant: -2147481850 (decimal) //equivalent to *unsigned* 0x80000706. If source mailbox is an equipment mailbox:

Constant: -2147481594 (decimal) //equivalent to *unsigned* 0x80000806.

msExchResourceCapacity

Directly copy the corresponding attribute of the source mailbox.

msExchResourceDisplay

Directly copy the corresponding attribute of the source mailbox.

msExchResourceMetaData

Directly copy the corresponding attribute of the source mailbox.

msExchResourceSearchProperties

Directly copy the corresponding attribute of the source mailbox.

  Additional Attributes

The Exchange 2007 Move-Mailbox cmdlet also copied the following attributes when moving a mailbox. You can optionally copy these attribute if needed:

Resource mailbox attributes

Mail User’s Active Directory attributes
Description

comment

Directly copy the corresponding attribute of the source mailbox.

deletedItemFlags

Directly copy the corresponding attribute of the source mailbox.

delivContLength

Directly copy the corresponding attribute of the source mailbox.

departmentNumber

Directly copy the corresponding attribute of the source mailbox.

description

Directly copy the corresponding attribute of the source mailbox.

division

Directly copy the corresponding attribute of the source mailbox.

employeeID

Directly copy the corresponding attribute of the source mailbox.

employeeNumber

Directly copy the corresponding attribute of the source mailbox.

employeeType

Directly copy the corresponding attribute of the source mailbox.

extensionAttribute1-15

Directly copy the corresponding attribute of the source mailbox.

homePostalAddress

Directly copy the corresponding attribute of the source mailbox.

internationalISDNNumber

Directly copy the corresponding attribute of the source mailbox.

ipPhone

Directly copy the corresponding attribute of the source mailbox.

language

Directly copy the corresponding attribute of the source mailbox.

lmPwdHistory

Directly copy the corresponding attribute of the source mailbox.

localeID

Directly copy the corresponding attribute of the source mailbox.

mAPIRecipient

Directly copy the corresponding attribute of the source mailbox.

middleName

Directly copy the corresponding attribute of the source mailbox.

msDS-PhoneticCompanyName

Directly copy the corresponding attribute of the source mailbox.

msDS-PhoneticDepartment

Directly copy the corresponding attribute of the source mailbox.

msDS-PhoneticDisplayName

Directly copy the corresponding attribute of the source mailbox.

msDS-PhoneticFirstName

Directly copy the corresponding attribute of the source mailbox.

msDS-PhoneticLastName

Directly copy the corresponding attribute of the source mailbox.

msExchBlockedSendersHash

Directly copy the corresponding attribute of the source mailbox.

msExchELCExpirySuspensionEnd

Directly copy the corresponding attribute of the source mailbox.

msExchELCExpirySuspensionStart

Directly copy the corresponding attribute of the source mailbox.

msExchELCMailboxFlags

Directly copy the corresponding attribute of the source mailbox.

msExchExternalOOFOptions

Directly copy the corresponding attribute of the source mailbox.

msExchMessageHygieneFlags

Directly copy the corresponding attribute of the source mailbox.

msExchMessageHygieneSCLDeleteThreshold

Directly copy the corresponding attribute of the source mailbox.

msExchMessageHygieneSCLJunkThreshold

Directly copy the corresponding attribute of the source mailbox.

msExchMessageHygieneSCLQuarantineThreshold

Directly copy the corresponding attribute of the source mailbox.

msExchMessageHygieneSCLRejectThreshold

Directly copy the corresponding attribute of the source mailbox.

msExchMDBRulesQuota

Directly copy the corresponding attribute of the source mailbox.

msExchPoliciesExcluded

Directly copy the corresponding attribute of the source mailbox.

msExchSafeRecipientsHash

Directly copy the corresponding attribute of the source mailbox.

msExchSafeSendersHash

Directly copy the corresponding attribute of the source mailbox.

msExchUMSpokenName

Directly copy the corresponding attribute of the source mailbox.

otherFacsimileTelephoneNumber

Directly copy the corresponding attribute of the source mailbox.

otherIpPhone

Directly copy the corresponding attribute of the source mailbox.

otherMobile

Directly copy the corresponding attribute of the source mailbox.

otherPager

Directly copy the corresponding attribute of the source mailbox.

preferredDeliveryMethod

Directly copy the corresponding attribute of the source mailbox.

personalPager

Directly copy the corresponding attribute of the source mailbox.

personalTitle

Directly copy the corresponding attribute of the source mailbox.

photo

Directly copy the corresponding attribute of the source mailbox.

pOPCharacterSet

Directly copy the corresponding attribute of the source mailbox.

pOPContentFormat

Directly copy the corresponding attribute of the source mailbox.

postalAddress

Directly copy the corresponding attribute of the source mailbox.

postOfficeBox

Directly copy the corresponding attribute of the source mailbox.

primaryInternationalISDNNumber

Directly copy the corresponding attribute of the source mailbox.

primaryTelexNumber

Directly copy the corresponding attribute of the source mailbox.

showInAdvancedViewOnly

Directly copy the corresponding attribute of the source mailbox.

street

Directly copy the corresponding attribute of the source mailbox.

terminalServer

Directly copy the corresponding attribute of the source mailbox.

textEncodedORAddress

Directly copy the corresponding attribute of the source mailbox.

thumbnailLogo

Directly copy the corresponding attribute of the source mailbox.

thumbnailPhoto

Directly copy the corresponding attribute of the source mailbox.

url

Directly copy the corresponding attribute of the source mailbox.

userCert

Directly copy the corresponding attribute of the source mailbox.

userCertificate

Directly copy the corresponding attribute of the source mailbox.

userSMIMECertificate

Directly copy the corresponding attribute of the source mailbox.

wWWHomePage

Directly copy the corresponding attribute of the source mailbox.

  Use a Sample Script Example to Configure Active Directory Attributes

You can download the sample remote Powershell script from the Prepare for Online M ailbox Move download page. For more information on using the sample script, see Prepare Mailboxes for Cross-Forest Moves Using the PrepareMoveRequest.ps1 script in the Shell.

  Use ILM Sample Code to Configure Active Directory Attributes

One prescriptive way to set the above mentioned Active Directory attributes is using ILM 2007 FP1 SP1. See KB 97 7 791 (ILM 2007 FP1 SP1) to download the feature pack.

Ee633491.note(es-es,EXCHG.140).gifNota:

ILM 2007 has been updated. You must select whether the local forest is Exchange 2007 or Exchange 2010.

For Exchange 2010, you need to provide the Remote Powershell connection URI. Enter the URI of an Exchange 2010 Client Access server to make sure the Remote Powershell connection is functioning. The Exchange 2010 RPS URI should be in the following format: http://CAS_Server_FQDN/Powershell.

Provision GalSync Management Agent for Exchange 2010

Aprovisionamiento de Exchange 2010 del agente de administración