Skip to content

Fix 36 instances of broken fwlink to Microsoft.Windows.ServerManager.Migration #4016

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Export-SmigServerSetting [-FeatureId <String[]>] [-Feature <Feature[]>] [-User <
The **Export-SmigServerSetting** cmdlet 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 [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Get-SmigServerFeature -Path <String> -Password <SecureString> [<CommonParameters
The **Get-SmigServerFeature** cmdlet gets the set of all Windows Server features that can be migrated from the local server or from a migration store.
If a migration store is specified in the *Path* parameter, this cmdlet returns only the features in the migration store that can be installed on the local server.

For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ You can also use this cmdlet to install Windows features and their dependencies,
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 *Force* parameter to complete the import operation.

For online Help about the Windows Server Migration Tools cmdlets, see [http://go.microsoft.com/fwlink/?LinkId=246313](https://go.microsoft.com/fwlink/?LinkId=246313).
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ File access rights are maintained during the migration; the same set of users is
Because files are sent by using an encrypted connection, a password must be provided to decrypt migrated files on both the source and destination servers.
Transporting encrypted files (EFS) and junction points is not supported.

For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ File access rights are maintained during the migration; the same set of users is
Because files are sent by using an encrypted connection, a password must be provided to decrypt migrated files on both the source and destination servers.
Transporting encrypted files (EFS) and junction points is not supported.

For online Help about the [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Export-SmigServerSetting [-FeatureId <String[]>] [-Feature <Feature[]>] [-User <
The **Export-SmigServerSetting** cmdlet 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 [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Get-SmigServerFeature -Path <String> -Password <SecureString> [<CommonParameters
The **Get-SmigServerFeature** cmdlet gets the set of all Windows Server features that can be migrated from the local server or from a migration store.
If a migration store is specified in the *Path* parameter, this cmdlet returns only the features in the migration store that can be installed on the local server.

For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ You can also use this cmdlet to install Windows features and their dependencies,
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 *Force* parameter to complete the import operation.

For online Help about the Windows Server Migration Tools cmdlets, see [http://go.microsoft.com/fwlink/?LinkId=246313](https://go.microsoft.com/fwlink/?LinkId=246313).
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ File access rights are maintained during the migration; the same set of users is
Because files are sent by using an encrypted connection, a password must be provided to decrypt migrated files on both the source and destination servers.
Transporting encrypted files (EFS) and junction points is not supported.

For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ File access rights are maintained during the migration; the same set of users is
Because files are sent by using an encrypted connection, a password must be provided to decrypt migrated files on both the source and destination servers.
Transporting encrypted files (EFS) and junction points is not supported.

For online Help about the [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Export-SmigServerSetting [-FeatureId <String[]>] [-Feature <Feature[]>] [-User <
The **Export-SmigServerSetting** cmdlet 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 [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Get-SmigServerFeature -Path <String> -Password <SecureString> [<CommonParameters
The **Get-SmigServerFeature** cmdlet gets the set of all Windows Server features that can be migrated from the local server or from a migration store.
If a migration store is specified in the *Path* parameter, this cmdlet returns only the features in the migration store that can be installed on the local server.

For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ You can also use this cmdlet to install Windows features and their dependencies,
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 *Force* parameter to complete the import operation.

For online Help about the Windows Server Migration Tools cmdlets, see [http://go.microsoft.com/fwlink/?LinkId=246313](https://go.microsoft.com/fwlink/?LinkId=246313).
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ File access rights are maintained during the migration; the same set of users is
Because files are sent by using an encrypted connection, a password must be provided to decrypt migrated files on both the source and destination servers.
Transporting encrypted files (EFS) and junction points is not supported.

For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ File access rights are maintained during the migration; the same set of users is
Because files are sent by using an encrypted connection, a password must be provided to decrypt migrated files on both the source and destination servers.
Transporting encrypted files (EFS) and junction points is not supported.

For online Help about the [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Export-SmigServerSetting [-FeatureId <String[]>] [-Feature <Feature[]>] [-User <
The **Export-SmigServerSetting** cmdlet 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 [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Get-SmigServerFeature -Path <String> -Password <SecureString> [<CommonParameters
The **Get-SmigServerFeature** cmdlet gets the set of all Windows Server features that can be migrated from the local server or from a migration store.
If a migration store is specified in the *Path* parameter, this cmdlet returns only the features in the migration store that can be installed on the local server.

For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ You can also use this cmdlet to install Windows features and their dependencies,
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 *Force* parameter to complete the import operation.

For online Help about the Windows Server Migration Tools cmdlets, see [http://go.microsoft.com/fwlink/?LinkId=246313](https://go.microsoft.com/fwlink/?LinkId=246313).
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ File access rights are maintained during the migration; the same set of users is
Because files are sent by using an encrypted connection, a password must be provided to decrypt migrated files on both the source and destination servers.
Transporting encrypted files (EFS) and junction points is not supported.

For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the Windows Server Migration Tools cmdlets, see [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ File access rights are maintained during the migration; the same set of users is
Because files are sent by using an encrypted connection, a password must be provided to decrypt migrated files on both the source and destination servers.
Transporting encrypted files (EFS) and junction points is not supported.

For online Help about the [Server Migration Cmdlets in Windows PowerShell](https://go.microsoft.com/fwlink/?LinkId=246313) at http://go.microsoft.com/fwlink/?LinkId=246313.
For online Help about the [Server Migration Cmdlets in Windows PowerShell](/powershell/module/microsoft.windows.servermanager.migration).

## EXAMPLES

Expand Down