Hyper-V Manual Registry Configuration

This page describes how to manually configure the registry of a Hyper-V core machine to use with Abiquo.

Preparation
1. Install Hyper-V
2. Join a domain
3. Make the domain administrator a local administrator
Edit the registry as described below

Change key ownership where necessary
Set key values as described in Hyper-V page

Note that you can also perform step 2.a using other tools, for example, SetACL. This is described below in Hyper-V Manual Registry Configuration

Configure Hyper-V for DCOM Management

Configure Wbem Scripting to Run Remotely

Run regedit.exe (registry editor).

Click on Computer\HKEY_LOCAL MACHINE.

Open Find dialog

Edit->Find
Right-click menu -> Find

Search for a key with the name WbemScripting.SWbemLocator in the following location:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WbemScripting.SWbemLocator

Check the location in the box at the bottom of the Registry Editor Screen.

Repeat the search (F3) until you find this key in the right location.

Expand the WbemScripting.SWbemLocator folder.

Click the subkey named CLSID.

Open the "(Default)" value (use right-click -> Modify)

The value of the Data GUID should be:

{76A64158-CB41-11D1-8B02-00600806D9B6}

Make a note of the Value data or copy it to Notepad. Include the brackets.

Open the HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID key

From here, search for the saved GUID value

When you find the key, check it is:

\Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}

Change Owner of Wbem Scripting Key

Highlight the GUID number/subkey under the HKEY_CLASSES_ROOT\CLSID key. Right click on the key and right-click on "Permissions". Click "Advanced"

Next click on the Owner link and you'll now see that the current owner is TrustedInstaller. Now click on the Edit button and choose who you would like to change the owner to, either your account or the Administrators. If your account is an Administrator account, you can just pick Administrators.

Modify the Threading Model for Wbem Scripting

Click on the InprocServer32 subkey below this key

The InprocServer32 value for (Default) should point to the location of the COM DLL file, for example:

%SystemRoot%\system32\wbem\wbemdisp.dll

If there is a TypeLib subkey, check that the GUID value is not the same as the one from step 1. Otherwise, go back to where you copied the GUID and repeat the steps with the correct key if necessary. The following screenshot shows a correct value.

Also, under the GUID's InprocServer32 subkey, check that a ThreadingModel value exists. Modify (or create) it and set it to Both or Free.

This will ensure the marshaling works with the threading model of the COM object to enable execution of COM out of SQL Server process space. If there is not a ThreadingModel value or it is set to Apartment, COM object instantiation may not be consistent.

Key privileges

You may need to add privileges to this key in order to change the ThreadingModel value.

Configure AppID with Dllsurrogate

Select the key we have been working with:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{76a64158-cb41-11d1-8b02-00600806d9b6}

From the Edit menu, click New, and then select String Value. Under the Name column, type the following:

AppID

Press Enter and then insert the class identifier or GUID number. It should be in the format{76a64158-cb41-11d1-8b02-00600806d9b6} (include the brackets).

Add a new subkey under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID and set its name to the same class identifier or GUID number with the brackets as inserted in the preceding step.

Key privileges

You may need to add privileges to this key.

Highlight the GUID name. From the Edit menu, click New, and then select String Value. Under the Name column, type the following:

DllSurrogate

Leave the Data column blank for this value. Because the data column is blank, this informs DCOM to run the default executable file, Dllhost.exe and load the COM object within its process space.

Set Key Ownership Using Alternate Methods

As described in the manual process above, you should change key ownership before setting key values. You may wish to use another tool or method to change key ownership.

Add the Hyper-V to a Windows domain
Configure the CLSID key
1. Change the owner to the domain admin
2. Change the key values
Configure the AppID key
1. Create the key
2. Change the owner of the key
3. Change the key values

One method for changing ownership is to download SetACL.exe and use it to modify the keys.

#### Change ownership of CLSID key
SetACL.exe -on HKEY_CLASSES_ROOT\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}  -ot reg -rec yes -actn setowner -ownr n:example.com\\Administrator
SetACL.exe -on HKEY_CLASSES_ROOT\CLSID\{76A64158-CB41-11D1-8B02-00600806D9B6}  -ot reg -rec yes -actn ace -ace n:example.com\\Administrator;p:full

### Change ownership of AppID key
SetACL.exe -on HKEY_CLASSES_ROOT\AppID\{76A64158-CB41-11D1-8B02-00600806D9B6}  -ot reg -actn setowner -ownr n:example.com\\Administrator
SetACL.exe -on HKEY_CLASSES_ROOT\AppID\{76A64158-CB41-11D1-8B02-00600806D9B6}  -ot reg -actn ace -ace n:example.com\\Administrator;p:full