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




Disk Cleanup Utility в Windows Server

1. Install "Desktop Experience" feature.

2. Copy files manually (not for Windows Server 2012 R2):

The location of the files you need to copy depend on your version of Windows:

Operating System


File Location

Windows Server 2008 R2


C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da \cleanmgr.exe

Windows Server 2008 R2


C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63 \cleanmgr.exe.mui

Windows Server 2008


C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.0.6001.18000_en-us_b9f50b71510436f2 \cleanmgr.exe.mui

Windows Server 2008


C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.0.6001.18000_none_c962d1e515e94269 \cleanmgr.exe.mui

Windows Server 2008


C:\Windows\winsxs\x86_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.0.6001.18000_en-us_5dd66fed98a6c5bc \cleanmgr.exe.mui

Windows Server 2008


C:\Windows\winsxs\x86_microsoft-windows-cleanmgr_31bf3856ad364e35_6.0.6001.18000_none_6d4436615d8bd133 \cleanmgr.exe

Windows Server 2012


C:\Windows\WinSxS\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.2.9200.16384_none_c60dddc5e750072a \cleanmgr.exe

Windows Server 2012




Once you’ve located the files move them to the following locations (Server 2012 non-R2 and earlier):

  1. Copy Cleanmgr.exe to %systemroot%\System32.
  2. Copy Cleanmgr.exe.mui to %systemroot%\System32\en-US.

You can now launch the Disk cleanup tool by running Cleanmgr.exe from the command prompt.



Event ID 10 is logged in the Application log after install Service Pack 1 for Windows 7 or Windows Server 2008 R2

В журнале Application появляются сообщения об ошибках вида "Event filter with query "SELECT * FROM __InstanceModificationEvent WITHIN 60 WHERE TargetInstance ISA "Win32_Processor" AND TargetInstance.LoadPercentage > 99" could not be reactivated in namespace "//./root/CIMV2" because of error 0x80041003. Events cannot be delivered through this filter until the problem is corrected."

Описание и решение - https://support.microsoft.com/en-us/kb/2545227.


Смена алгоритма подписи SSL-сертификатов в Windows Server Certificate Authority

Необходимо заменить используемый алгоритм (Hash Algorithm) SHA-1 на SHA-256 и перевыпустить корневой сертификат CA.

1. На сервере CA выполнить команду:
certutil -setreg ca\csp\CNGHashAlgorithm SHA256
2. Перезапустить сервис CA
3. Перевыпустить новый корневой сертификат CA (All Tasks - Renew CA Certificate)

В дальнейшем для выпуска сертификатов использовать шаблоны с минимальным уровнем CA (Minimum Supported CAs) не ниже "Windows Server 2008 Enterprise".