Export (0) Print
Expand All
This topic has not yet been rated - Rate this topic

Export-SmigServerSetting

Windows Server 2012 R2 and Windows 8.1

Updated: November 20, 2013

Applies To: Windows 8.1, Windows PowerShell 4.0, Windows Server 2012 R2

Export-SmigServerSetting

Exports selected Windows features and operating system settings from the local computer, and stores them in a migration store.

Syntax

Parameter Set: Default
Export-SmigServerSetting [[-Feature] <Feature[]> ] [[-FeatureId] <String[]> ] [[-User] <String> ] [[-Group]] [[-IPConfig]] [-Path] <String> -Password <SecureString> [ <CommonParameters>]




Detailed Description

Exports selected Windows features and operating system settings from the local computer, and stores them in a migration store specified in the -Path parameter. Use the Import-SmigServerSetting cmdlet to import Windows features and operating system settings to the destination computer from the migration store populated by the Export-SmigServerSetting command.

For online Help about the Windows Server Migration Tools cmdlets, see http://go.microsoft.com/fwlink/?LinkId=246313.

Parameters

-Feature<Feature[]>

Specifies the Windows features to be exported from the source computer. Not all Windows features can be migrated by using migration cmdlets. You can use the Get-SmigServerFeature cmdlet to retrieve a list of Windows features that can be migrated from the local server, and pass the resulting list to the Export-SmigServerSetting cmdlet, either by piping the results to the cmdlet, or by storing the results in a variable and then using the variable to represent the results in your command.


Aliases

F

Required?

false

Position?

1

Default Value

none

Accept Pipeline Input?

True (ByValue)

Accept Wildcard Characters?

false

-FeatureId<String[]>

Specifies the IDs of the Windows features to be exported from the source computer. Not all Windows features are supported for migration. You can use the Get-SmigServerFeature cmdlet to retrieve a list of Windows features, along with their feature IDs, that can be migrated from the local server. Separate multiple feature IDs by using commas. Standard PowerShell wildcard characters are supported.


Aliases

ID

Required?

false

Position?

2

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Group

Exports the source server's local groups.


Aliases

none

Required?

false

Position?

6

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-IPConfig

Exports the source server's basic IP configuration settings, including network interface card (NIC) settings such as connection-specific suffix, IPv4 settings, registry key to disable IPv6 components, and global Windows IP configuration settings. IP configuration for a NIC can only be exported if the NIC is enabled and connected to the network. See IP Configuration Migration Guide for more information.


Aliases

none

Required?

false

Position?

7

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Password<SecureString>

Specifies the migration store encryption password as a secure string. The secure string can be obtained by entering the command Read-Host -AsSecureString or Convertto-Securestring. Because the Password parameter is required, if it is not added to your command, you are prompted to create a password after entering your command. The password length must be a minimum of 6 characters and a maximum of 260 characters.


Aliases

none

Required?

true

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Path<String>

Specifies the path to store the exported migration data. The specified migration store location must be empty. The path must be a valid local or Universal Naming Convention (UNC) path; if it is a share on a remote computer, the share must be notated as a drive letter on the local computer. The path length cannot be longer than 246 characters. Wildcard characters are not supported.


Aliases

none

Required?

true

Position?

8

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-User<String>

Specifies the type of user accounts to export to the migration store. The following are acceptable values for this parameter:
     - Enabled
     - Disabled
     - All

User passwords are not migrated. Users must create a password the first time they log on to the server. Only the "User Name" and "Account is Disabled" properties are migrated.


Aliases

none

Required?

false

Position?

4

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

  • Microsoft.Windows.ServerManager.Migration.MigrationResult

Notes

  • The Windows Server Migration Tools deployment log file is located in %windir%\Logs\SmigDeploy.log. Other Windows Server Migration Tools log files are created at the following locations:
         - %windir%\Logs\ServerMigration.log
         - On Windows Server 2008 and later versions: %localappdata%\SvrMig\Log
         - On Windows Server 2003: %userprofile%\Local Settings\Application Data\SvrMig\Log

    If the log files cannot be created at these locations, ServerMigration.log and SmigDeploy.log will be created at %temp%, and other logs will be created at %windir%\System32.

    The maximum size of all log files (in MB) is stored in the following registry key. When the log file grows larger than the size specified in the registry key, the log file is deleted. Logging begins again in a new log file that uses the same file name and path. The default maximum log size is 200 MB.
         - Key: HKLM\Software\Microsoft\ServerMigration
         - Value: MaxLogSize (REG_DWORD)
         - Data: Whole numbers between 1 and 1000 (represents log size, in MB)

Examples

EXAMPLE 1

This sample command exports the Dynamic Host Configuration Protocol (DHCP) Server and all other Windows features that are required by DHCP Server. The command also exports local user accounts, local groups, and group memberships to the location c:\temp\store that is specified in the -Path parameter.

Creating a password to encrypt the migration store is required. Because a password is not provided in this sample command, after you enter the command, the user is prompted to enter a password for encrypting the migrated data. Password characters are displayed as asterisks (*).When the password is entered, the value is passed to the command as a SecureString.

By using the -Verbose parameter, the command also displays detailed information about the migration operation.


PS C:\> Export-SmigServerSetting -Feature "DHCP" -User All -Group -Path "c:\temp\store" -Verbose

EXAMPLE 2

This sample command exports basic IP configuration settings, and stores the data in the migration store specified by the -Path parameter as c:\temp\store. The sample command also instructs the migration utilities to display the text string "Create a Password:" to prompt the user to create a password for encrypting the migration store. Password characters are displayed as asterisks (*). When the new password has been entered, the value is stored by the Export-SmigServerSetting as a SecureString.

By using the -Verbose parameter, the command also displays detailed information about the migration operation.


PS C:\> Export-SmigServerSetting -IPConfig -Path c:\temp\store -Password (Read-Host "Create a Password:" -AsSecureString) -Verbose

EXAMPLE 3

This sample command exports a set of Windows features that have already been specified by using the Get-SmigServerFeature cmdlet. In the sample, the migration utilities are instructed to use a variable, $c, to represent the features specified by using the Get-SmigServerFeature cmdlet.

The first command retrieves Windows feature objects specified by using the Get-SmigServerFeature cmdlet, and saves them in the $c variable. The second command exports the Windows features represented by the $c variable, and stores the data in the location that is specified in the -Path parameter, c:\temp\store.

Creating a password to encrypt the migration store is required. Because a password is not provided in this sample command, after entering the command, the user is prompted to enter a password for encrypting the migrated data. Password characters are displayed as asterisks (*).When the password is entered, the value is passed to the command as a SecureString.

By using the -Verbose parameter, the command also displays detailed information about the migration operation.


PS C:\> $c = Get-SmigServerFeature
PS C:\> Export-SmigServerSetting -Feature $c -Path c:\temp\store -Verbose

EXAMPLE 4

In this example, the first command instructs the migration utilities to convert the store encryption password, represented by "password," to a secure string, and store it in the variable $pass. The second command exports all local user accounts, sets the value of the variable $pass as the password to encrypt the migration store, and stores the migration data in the location c:\temp\store.

By using the -Verbose parameter, the command also displays detailed information about the migration operation.


PS C:\> $pass = convertto-securestring -string "password" -asplaintext -force
PS C:\> Export-SmigServerSetting -User All -Password $pass -Path "c:\store" -Verbose

Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft. All rights reserved.