Imports selected Windows features, and operating system settings from a migration store, and applies them to the local computer.
Windows Server · Risk: High · Documentation Verified
Last verified: 2026-10-26
Microsoft Microsoft.Windows.ServerManager.Migration reference: Imports selected Windows features, and operating system settings from a migration store, and applies them to the local computer. The syntax and selected example below are adapted from the pinned Windows Server 2025 reference. Module availability, target configuration and delegated permissions determine whether it can run in your environment. Documentation and parameter text: Microsoft, CC BY 4.0; formatting adapted by Cmdlet World. No execution testing is claimed.
Use an account with the target resource permissions documented for Import-SmigServerSetting. Modifying administrative cmdlets may require elevation or delegated administration. This catalog does not assert that ordinary users can execute the command.
Supported environments
Windows / Microsoft.Windows.ServerManager.Migration · Windows Server 2025 documentation; feature/module prerequisites apply
Parameters
-Confirm
Prompts you for confirmation before running the cmdlet.
-Feature
Specifies the Windows feature objects that you want to import from the migration store. 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 migration store to the destination server, and pass the resulting list to the Import-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. This cmdlet also installs Windows features and their dependencies, if the features you are migrating have not been installed. Some Windows features might require that the destination computer be restarted to complete installation. After restarting the computer, you must run the cmdlet again with the *Force* parameter to complete the import operation.
-FeatureId
Specifies the IDs of the Windows features that you want to import from the migration store. 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, which can be migrated from the migration store to the destination server. Separate multiple feature IDs by using commas. Standard PowerShell wildcard characters are supported. This cmdlet also installs Windows features and their dependencies, if the features you are migrating have not been installed. Some Windows features might require that the destination computer be restarted to complete installation. After restarting the computer, you must run the cmdlet again with the *Force* parameter to complete the import operation.
-Force
Specifies that imported settings overwrite existing Windows feature settings on the destination computer. If this parameter is not used, by default, existing Windows feature settings on the destination computer are preserved.
-Group
Imports the local groups and their memberships from the migration store. If a group already exists on the destination server, it is not overwritten. Group memberships from the source server are added to existing groups on the destination server, and the existing group memberships on the destination server are preserved.
-IPConfig
Imports the source server's basic IP configuration settings. The following are acceptable values for this parameter: - NIC: network interface card (NIC) IP configuration settings such as connection-specific suffix, IPv4 settings and Disable IPv6 Component registry key. IP configuration can only be imported for a NIC if it is enabled and connected to the network. You must restart your computer for disabling IPv6 components to take effect. - Global: Windows IP configuration settings for the local computer. - All: both NIC and Global settings.
-Password (required)
Specifies the password, as a secure string, to decrypt the migration store. 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 specify a password after entering your command.
-Path (required)
Specifies the path to the migration store from which you want to import Windows features and operating system settings. The path must be a well-formed 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. Because the *Path* parameter is required, if it is not added to your command, you are prompted to specify a path after entering your command.
-SourcePhysicalAddress
Specifies, in double quotations, the physical addresses of the source network interface cards (NICs) from which to import IP settings. To specify multiple source physical addresses, use commas to separate each address. The number of source physical addresses must be the same as the number of destination physical addresses specified in the *TargetPhysicalAddress* parameter. Wildcard characters are not supported. This parameter is required when migrating NIC or all IP configurations.
-TargetPhysicalAddress
Specifies, in double quotations, the physical addresses of the destination network interface cards (NICs) to which you want to apply IP settings. If you specify multiple destination physical addresses, use commas to separate each address. The number of destination physical addresses must be the same as the number of source physical addresses specified in the *SourcePhysicalAddress* parameter. Wildcard characters are not supported. This parameter is required when migrating NIC or all IP configurations.
-User
Specify the type of local user accounts to import from the migration store. The following are acceptable values for this parameter: - Enabled: import only enabled local users - Disabled: import only disabled local users - All: import both enabled and disabled local users 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.
-WhatIf
Shows what would happen if the cmdlet runs. The cmdlet is not run.
Prerequisites
Windows with the Microsoft.Windows.ServerManager.Migration module and the Windows feature or management tools that provide it. Confirm target connectivity and version compatibility using the linked Microsoft reference.
Security considerations
This cmdlet changes system state. Review every target and parameter in the official reference, test outside production, and prepare an appropriate backup or rollback. Do not execute the example automatically.
Examples
Example 1: Import a DHCP server
Import-SmigServerSetting -Feature "DHCP" -User All -Group -Path "c:\temp\store" -Verbose
This sample command imports the Dynamic Host Configuration Protocol (DHCP) server, and all other Windows features required by this technology. The command also import local user accounts, local groups, and group memberships to the location c:\temp\store that is specified in the *Path* parameter. Entering the password to decrypt 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. Source: Microsoft, CC BY 4.0; transcript prompt/output removed. This example was not executed.