Installing the SMS-Agent on Windows

You need to install the Agent on the Windows source server that you want to migrate. During the installation, you need to enter the AK/SK pair of your target account. After the Agent is started, it automatically reports source server information to SMS. The information is used for migration only. For more information, see What Information Does SMS Collect About Source Servers?

There are two options for Windows:

• GUI-based Windows Agent (Python 3): Windows Server 2012, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows 10, and Windows 8.1
• CLI-based Windows Agent (Python 2): Windows Server 2008 and Windows 7
  Caution

  You must log in to the Windows source server as user Administrator.

• You have obtained the AK/SK pair for your target account
  • If you use an IAM user for migration, see How Do I Obtain an AK/SK Pair for an IAM User?
  • If you use an account for migration, see How Do I Obtain an AK/SK Pair for an Account?.
• You have obtained the administrator permissions for the source server.
• You have confirmed that the source server OS is included in Supported Windows OSs.
• There is no antivirus software on the source server. Antivirus software may prevent the Agent from starting up.

  If the message "Failed to start I/O monitoring" is displayed when you start the Agent, rectify the fault by following the operations provided in How Do I Fix Error "Failed to start the I/O monitoring module" When I Start the Agent?

1. Log in to the management console.
2. Click Service List. Choose Migration > Server Migration Service.
3. In the navigation pane on the left, choose Agents.
4. Select the Windows card, locate the Agent that matches the source server OS, and click the icon next to Agent.
   • GUI-based Windows Agent (Python 3): Windows Server 2012, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows 10, and Windows 8.1
   • CLI-based Windows Agent (Python 2): Windows Server 2008 and Windows 7

5. Read and agree to the service agreement, and click Yes to download the Agent installation file.
6. Click SHA256 File in the pane of the downloaded Agent to verify the integrity of the Agent installation file. For details, see How Do I Verify the Integrity of the Agent Installation File?

1. Transmit the SMS-Agent-Py3.exe file to the source server.
2. Log in to the source server as user Administrator and double-click the SMS-Agent-Py3.exe file.
3. Click Install and wait for the installation to complete.
4. Click Finish. The SMS-Agent GUI is displayed.
5. Enter the AK/SK pair of the account and the SMS domain name in the region you are migrating to. You can obtain the SMS domain name on the Agents page of the SMS console.
6. If the EPS service has been enabled for your account, after you entered the AK/SK pair, the Agent will list all enterprise projects your account is allowed to access. You can select the enterprise project you would like to migrate the source server to. This enables you to isolate permissions, resources, and finance during the migration.
7. Click start.
8. Carefully review the Privacy Statement and click Yes if you want to continue.

   When message Upload success. Waiting for the SMS instruction is displayed, the SMS-Agent has started up and started reporting source server information to SMS.

1. Transmit the SMS-Agent-Py2.exe file to the source server.
2. Log in to the source server as user Administrator and double-click the SMS-Agent-Py2.exe file.
3. Click Install and wait for the installation to complete.
4. Click Finish. The SMS-Agent CLI is displayed.
   Note

   To manually start the Agent when needed, double-click agent-start.exe in the installation directory C:\SMS-Agent-Py2.

5. When prompted, enter the AK/SK pair of the cloud account and the SMS domain name in the region you are migrating to. You can obtain the SMS domain name on the Agents page of the SMS console.

   If the EPS service has been enabled for your account, after you entered the AK/SK pair, the Agent will list all enterprise projects your account is allowed to access. You can select the enterprise project you would like to migrate the source server to. This enables you to isolate permissions, resources, and finance during the migration.

   After the authentication succeeds, the SMS-Agent starts to report source server information to SMS, and the window is closed. You can go to the Servers page on the SMS console to view the record of the source server.

• How Do I Resolve Error "AK/SK authentication failed. Ensure that the system time is consistent with the standard time and the AK and SK are correct" When I Start the Agent?
• Why Wasn't My Source Server Added to the SMS Console After I Configured the Agent?