Hyper-V регистрация существующей ВМ

The first step to make this machine known to Hyper-V is to create a Symbolic link to the <GUID>.xml configuration files, in the following folder:

“%systemdrive%\programdata\Microsoft\Windows\Hyper-V\Virtual Machines”

We use the mklink command built into cmd.exe

C:\>mklink “%systemdrive%\programdata\Microsoft\Windows\Hyper-V\Virtual Machines\2F855D88-F990-47BA-95D6-0029BCD8C059.xml” “V:\manualrecover\Virtual Machines\2F855D88-F990-47BA-95D6-0029BCD8C059.xml

The VM Name should now already appear in Hyper-V Manager. When using Windows Server 2008 R2, you might need to restart the vmms service to make the VMs visible at this point.

We need to add the Service SID to this Symbolic link so that Hyper-V is allowed to access it

C:\>icacls “%systemdrive%\programdata\Microsoft\Windows\Hyper-V\Virtual Machines\2F855D88-F990-47BA-95D6-0029BCD8C059.xml” /grant “NT VIRTUAL MACHINE\2F855D88-F990-47BA-95D6-0029BCD8C059“:(F) /L

Note the /L parameter to indicate we work on a symbolic link

=========================================================================

We also need to give the Service SID access to all files of our VM

C:\>icacls v:\manualrecover\ /T /grant “NT VIRTUAL MACHINE\2F855D88-F990-47BA-95D6-0029BCD8C059“:(F)

Note for simplicity we give Full Control, whereas the default is more granular

 

Подробно:

https://blogs.msdn.microsoft.com/robertvi/2008/12/19/howto-manually-add-a-vm-configuration-to-hyper-v/

Uninstall SQL Server SSMS 2016 from Windows 7 / Server 2008 R2

  1. Download the SSMS uninstall powershell script

  2. Download the Get-RemoteProgram Powershell script and make sure to place it in the same directory as the Powershell uninstall script above.

  3. Open an admin session of Powershell

  4. In powershell, run the command "Get-ExecutionPolicy". This command will display the current ExecutionPolicy of your machine. You will need to change this value if it is not "Unrestricted".

     
  5. In powershell, run the command "Set-ExecutionPolicy -ExecutionPolicy Unrestricted". This will launch a popup asking you to confirm changing the ExecutionPolicy. Confirm the change.

  6. Navigate to the folder with the SSMS uninstall Powershell script and run ".\UninstallSsms.ps1". This will launch a popup asking you to confirm launching the script. Click run. The script will now uninstall SSMS and all its dependencies.

     
  7. To revert the ExecutionPolicy back to its original state, run the command "Set-ExecutionPolicy -ExecutionPolicy [previous policy value]`". This will launch a popup asking you confirm changing the ExecutionPolicy. Confirm the change.