How Do I Handle a Network Failure After Services Are Switched from a Windows BMS Booted from an EVS Disk to an HA BMS?

Scenarios

After services are switched from a Windows BMS booted from an EVS disk to an HA BMS, the HA BMS cannot connect to the network.

Procedure

1. Log in to the Windows BMS and create a reserved administrator account.

   Choose Control Panel > User Accounts > Change account type > Add to add an administrator account.

2. Click in the lower left corner, choose Windows PowerShell, and enter regedit.exe to open the registry.

   In the Registry Editor window, choose HKEY_LOCAL_MACHINE > SOFTWARE > Cloudbase Solutions > Cloudbase-Init and delete all folders from Cloudbase-Init.

   Figure 1 Deleting Cloudbase-Init folders
   
3. Manually delete bond information.

   a. Delete Team1.

   Run the Get-NetAdapter command to check whether Team1 is there.

   If there is a Team1, open Windows PowerShell as an administrator and run the following command to delete it:

   Remove-NetLbfoTeam -Name Team1

   b. Delete hidden network adapters.

   Choose Computer Management > Device Manager > View > Show hidden devices > Network adapters. Right-click the adapter (it should be displayed in gray) and choose Uninstall device. Uninstall other grayed out adapters, one by one, in the same way.

   Figure 2 Network adapters
   
4. Restart the Windows BMS.
5. Use the reserved administrator account to log in to the BMS. (The original administrator account becomes invalid after the BMS is restarted.)

   After network access is restored, change the password of the original administrator account. Then, delete the reserved account.