Migrates one or more user accounts from Office Communications Server 2007 or Office Communications Server 2007 R2 to Microsoft Communications Server 2010.
Syntax
add-attachmentfilterentry -Name <String> -Type <ContentType | FileName> [-Confirm [<SwitchParameter>]] [-DomainController <Fqdn>] [-WhatIf [<SwitchParameter>]] |
Parameters
| Parameter | Required | Type | Description |
|---|---|---|---|
|
Identity |
Required |
Indicates the Identity of the user account to be migrated. User Identities can be specified using one of four formats: 1) The user's SIP address; 2) the user's Universal Principal Name; 3) the user's domain name and logon name, in the form domain\logon (for example, litwareinc\kenmyer); and, 4) the user's Active Directory Domain Services display name (for example, Ken Myer). Note that the SAMAccountName cannot be used as an identity because it is not necessarily unique in a forest. You can use the asterisk (*) wildcard character when using the Display Name as the user Identity. For example, the Identity "* Smith" would return all the users with the last name Smith. |
|
|
Target |
Required |
String |
Fully qualified domain name of the registrar pool where the user account should be homed. For example: -Target atl-mcs-001.litwareinc.com. |
|
Force |
Optional |
Switch Parameter |
If present, suppresses all errors and warnings (except fatal errors) when migrating a user account. |
|
ExcludeVoicePolicy |
Optional |
Switch Parameter |
When present, any voice policies assigned to the user account are not retained when the account is migrated. |
|
ExcludeConferencingPolicy |
Optional |
Switch Parameter |
When present, any conferencing policies assigned to the user account are not retained when the account is migrated. |
|
ExcludeDialPlan |
Optional |
Switch Parameter |
When present, any dial plans assigned to the user account are not retained when the account is migrated. |
|
ExcludeArchivingPolicy |
Optional |
Switch Parameter |
When present, any archiving policies assigned to the user account are not retained when the account is migrated. |
|
ExcludeExternalAccessPolicy |
Optional |
Switch Parameter |
When present, any external access policies assigned to the user account are not retained when the account is migrated. |
|
ExcludePresencePolicy |
Optional |
Switch Parameter |
When present, any presence policies assigned to the user account are not retained when the account is migrated. |
|
ProxyPool |
Optional |
String |
Full qualified domain name of an Access Edge proxy pool used in your organization. |
|
DomainController |
Optional |
String |
Fully qualified domain name of a domain controller in your domain. |
|
PassThru |
Optional |
Switch Parameter |
Returns a user object for each user account being migrated. By default, this cmdlet does not generate any output. |
|
WhatIf |
Optional |
Switch Parameter |
Describes what would happen if you executed the command without actually executing the command. |
|
Confirm |
Optional |
Switch Parameter |
Prompts you for confirmation before executing the command. |
Detailed Description
Many organizations that install Microsoft Communications Server 2010 are also running a previous version of the software (either Office Communications 2007 or Office Communications Server 2007 R2). Fortunately, this does not present a problem: you can run both the latest version of the software and a previous version of the software simultaneously, then – over time – begin to migrate your configuration settings, your policies, and, finally, your user accounts to Communications Server 2010.
The Move-CsLegacyUser cmdlet not only enables you to migrate users to Communications Server 2010, but it gives you considerable control over the migration process. For example, in its simplest form you can give Move-CsLegacyUser the identity of the user to be migrated and the fully qualified domain name of the Communications Server 2010 Registrar pool where that user account will be homed; in turn, Move-CsLegacyUser will move the user account, and will maintain any existing policies and settings that have been applied to that account. For example, suppose the Ken Myer’s 2007 R2 was assigned a dial plan. By default, when you migrate that user account the dial plan will be migrated as well: Move-CsLegacyUser will automatically assign Ken Myer the Communications Server 2010-equivalent of the dial plan he was assigned in 2007 R2.
Of course, this command will only succeed if you migrated dial plans and there actually is a Communications Server 2010-equivalent of the dial plan ken Myer was assigned in 2007 R2. It might be that, with the upgrade to Communications Server 2010, you decided not to migrate dial plans but to create all-new dial plans instead. In that case, you can call Move-CsLegacyUser along with the –ExcludeDialPlan parameter. When you use this parameter, dial plans are not migrated along with the user account: ken Myer’s user account will be moved to Communications Server 2010, but he will not be assigned a dial plan. (This will be true even if you did migrate dial plans.) Other parameters allow you to exclude voice policies, conferencing policies, archiving policies, external access policies, and/or presence policies when migrating user accounts.
Before you can run Merge-CsLegacyUser you must first install WMI Backcompat; this application is installed by running the OCSWMIBC.msi. After installing WMI Backcompat Merge-CsLegacyUser can then be called in order to move one or more user accounts from Office Communications Server 2007 or 2007 R2 to Communications Server 2010..
Return Types
Move-CsLegacyUser does not return any values or objects. Instead, the cmdlet moves instances of the Microsoft.Rtc.Management.ADConnect.Schema.ADUser object.
Examples
-------------------------- Example 1 ------------------------
 Copy Code |
|
|---|---|
Move-CsLegacyUser -Identity "Pilar Ackerman" -Target "atl-mcs-001.litwareinc.com" |
|
In the preceding example, Move-CsLegacyUser is used to migrate a single account (the user account with the Identity Pilar Ackerman) to the Registrar pool atl-mcs-001.litwareinc. Because no additional parameters are included, any policies or settings previously assigned to this account will be migrated as well. That means that if any legacy policies (such as a dial plan) were assigned to Pilar Ackerman she will be assigned their Communications Server 2010-equivalent.
-------------------------- Example 2 ------------------------
| Copy Code |
|
|---|---|
Get-CsUser -OU "ou=Finance,dc=litwareinc,dc=com" | Move-CsLegacyUser -Target "atl=mcs-001.litwareinc.com" |
|
In example 2, all the user accounts in the Finance OU are migrated to the Registrar pool atl-mcs-001.litwareinc.com. To carry out this task, the command first uses Get-CsUser and the –OU parameter to retrieve a collection of all the user accounts in the Finance OU. After the data has been retrieved, the information is piped to Move-CsLegacyUser, which proceeds to migrate each account to Communications Server 2010. In addition, the cmdlet assigns each user the 2010 policies equivalent to the policies previously assigned to those users.
-------------------------- Example 3 ------------------------
| Copy Code |
|
|---|---|
Move-CsLegacyUser -Identity "Pilar Ackerman" -Target "atl-mcs-001.litwareinc.com" -ExcludeDialPlan |
|
The command shown in Example 3 migrates Pilar Ackerman’s user account to Communications Server 2010, but does not migrate any dial plans previously assigned to her account. After the account is migrated, Pilar will not have an assigned dial plan.