Hyper-v installation steps for management through DCOM :

1. Open the Registry Editor (Regedit.exe) and under the HKEY_CLASSES_ROOT key use the Find method to locate a key with the name WbemScripting.SWbemLocator.

2.You will find it at other levels, but it should be located at the level directly below the HKEY_CLASSES_ROOT. After you locate the key, expand the folder for the key name and you should see a subkey named CLSID. Click that folder to see the values within that key. The key should be: {76a64158-cb41-11d1-8b02-00600806d9b6} . Make a note of this value or copy it to Notepad. Include the brackets.

3.Navigate under the HKEY_CLASSES_ROOT\CLSID key and find the subkey with this GUID number. After you highlight the HKEY_CLASSES_ROOT\CLSID key you can use the Find function in Registry Editor (under the Edit menu) and paste the GUID into the Find dialog box. Make sure that you have found the proper interface by inspecting the InprocServer32 subkey below this key, which points to the location of your COM DLL file. If there is a TypeLib key, check this GUID value

While under the GUID's InprocServer32 subkey, make sure that a ThreadingModel value exists and that it is set to either Both or Free to make sure the marshaling understands 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.

NOTE: Maybe you need to add privileges to this key in order to change the ThreadingModel value

Highlight the GUID number/subkey under the HKEY_CLASSES_ROOT\CLSID key. Righ click on the key and right-click button "Permissions". Click "Advanced", Next click on the Owner tab 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, I would suggest just picking Administrators [Abiquo:6].

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: I think it should be: {76a64158-cb41-11d1-8b02-00600806d9b6}. Include brackets

Add a new subkey under the HKEY_CLASSES_ROOT\AppID and set it's name to the same class identifier or GUID number with the brackets as inserted in the preceding step. NOTE: Maybe you 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 it's process space.

WinRM service configuration

This service is used to call remote methods in object that can't be properly managed through DCOM.

1. By default, no WinRM listener is configured. Even if the WinRM service is running, WS-Management protocol messages that request data cannot be received or sent [Abiquo:3].

Use the Winrm command to locate listeners and the addresses by typing the following command at a command prompt:

 winrm e winrm/config/listener  

If no listener is configured, type:

 winrm QuickConfig  

To check the state of configuration settings, type winrm get winrm/config.

2. Allow unencrypted traffic and basic auth:

Allow unencrypted messages:

winrm set winrm/config/service @{AllowUnencrypted="true"} 

Allow use of basic authentication:

winrm set winrm/config/service/auth @{Basic="true"} 

3. Execute the next command to inspect the listening port:

winrm get winrm/config/Service/DefaultPorts  

Note the HTTP port since it will be used in the virtual factory configuration section

4.[Abiquo:optional] If you want to test this configuration steps from a winrm client:

Set the hosts that are allowed (the client IP, yours will be different) :

winrm set winrm/config/client @{TrustedHosts="IP"} 

To Ping WS-Man on a remote machine [Abiquo:5]:

 winrm id -auth:none -remote:\<some machine\>  

Networking installation:

Furthermore, the MAC interval allocation should be [Abiquo:2]:

MinimumMacAddress = 00-15-5d-00-00-00
MaximumMacAddress = 00-15-5d-FF-FF-FF

VLAN Configuration

To allow Abiquo to manage VLANs in this HyperV server, we need to add a new network attached to the service network interface.
The network name should be: SERVICE_NETWORK.

iScsi service installation:

The first thing you need to do is enable iSCSI service and set it to start automatically

 sc config msiscsi start= auto  

output:

 ChangeServiceConfig SUCCESS  

 net start msiscsi 

output:

 The Microsoft iSCSI Initiator Service service is starting.
The Microsoft iSCSI Initiator Service service was started successfully.  

San Policy

Open a command line and run the following commands:

diskpart
san policy=OfflineAll
exit

Local Repository Creation

A directory to store the vhd must be created in the hyper-v machine. For example:

c:\localRepository\

This directory path shall be configured in the virtual factory configuration parameter localRepositoryPath.

VirtualFactory configuration

VirtualFactory configuration is located in the Abiquo Server Host:

Abiquo 1.5

/opt/abiquo-server/config/virtualfactory.xml

Abiquo 1.6

/opt/abiquo/config/virtualfactory.xml

user: the administrator user
password: the administrator password
localRepositoryPath: the physical machine path where the vhd files will be copied from the repository.

wsmanPort, the winRM port configured in the section 3 of WinRM service configuration in this document

destinationRepositoryPath: is the SMB repository path, for example:  \\192.168.1.45\opt\vm_repository

VirtualSystemMonitor configuration

VirtualSystemMonitor configuration is located in the Abiquo Server Host:

Abiquo 1.5

/opt/abiquo-server/config/vsm.xml

Abiquo 1.6

/opt/abiquo/config/vsm.xml

user: the administrator user
password: the administrator password
pollInterval: The polling interval in milliseconds. The VSM for Hyper-V checks periodically the hypervisor state. This parameter configures the check interval.

References:

[Abiquo:1] [http://support.microsoft.com/kb/198891/en-us

[Abiquo:2] http://www.virtualizationadmin.com/articles-tutorials/microsoft-hyper-v-articles/networking/mac-address-pool-duplication-hyper-v.html

[Abiquo:3] http://msdn.microsoft.com/en-us/library/aa384372%28VS.85%29.aspx

[Abiquo:4] http://www.windowsitpro.com/article/john-savills-windows-faqs/q-how-can-i-use-the-command-line-to-configure-iscsi-connections-.aspx

[Abiquo:5] http://blogs.technet.com/otto/archive/2007/02/09/sample-vista-ws-man-winrm-commands.aspx

[Abiquo:6] http://helpdeskgeek.com/windows-7/windows-7-how-to-delete-files-protected-by-trustedinstaller/