This is a known issue that we will potentially address in an upcoming QFE. For now, there is a workaround that is detailed in this blog post. Alex from our team wrote the PowerShell script that resolves this issue.

How to tell if you have switch port leaks:

1. You are managing Hyper-V using VMM
2. Calling the following cmdlet from PowerShell take more than 3 minutes to return: get-vmhost "<host computer name FQDN>" | refresh-vmhost???
3. executing the following queries locally on the Hyper-V host from an elevated command prompt return more than a couple of hundred different objects. Running the same query command from wbemtest.exe connecting to root\virtualization as "select * from Msvm_hostedaccesspoint" for example will give you an instant count.
   1. ??winrm enum wmi/root/virtualization/Msvm_hostedaccesspoint
   2. ??winrm enum wmi/root/virtualization/Msvm_resourceallocationsettingdata
   3. ??winrm enum wmi/root/virtualization/Msvm_networkelementsettingdata
   4. winrm enum wmi/root/virtualization/Msvm_bindsto
   ?

How to fix the switch port leaks:

1. Run the attached powershell script locally on the Hyper-V host from an elevated powershell window. This command will return back data on the unused networking elements in Hyper-V that were potentially leaked by VMM
   1. DeleteUnusedHyper-VNetworkingComponents.ps1 <hostname FQDN> no
2. If you are satisfied with the objects that will potentially be deleted, run the same cmdlet with the "yes" switch.
   1. DeleteUnusedHyper-VNetworkingComponents.ps1 <hostname FQDN> yes
3. Run refresh-vmhost again in VMM a couple of times to observe the increase in speed
4. Create a scheduled task to execute this script against your Hyper-V hosts every couple of weeks.

DeleteUnusedHyper-VNetworkingComponents.ps1

In order for VMM to take advantage of this new OS support in Hyper-V (and as long as you are using the supported version of Hyper-V for SUSE 11), you need to execute a Database script to update VMM.

To make the process simple, follow the exact same steps as this blog post from me. https://blogs.technet.com/b/m2/archive/2010/04/16/getting-the-os-name-for-windows-2000-to-show-up-properly-in-the-vmm-administrator-console.aspx However, instead of the DB scripts outlined in this blog post, run the two ones i mention below

<< 

INSERT INTO tbl_IL_OS

(OSId, Name, Description, Edition, ProductType, Version, Architecture, OSFlags, VMWareGuestId) VALUES ('dd8570f2-00db-449f-aa97-9c189279eeb3', 'Suse Linux Enterprise Server 11 (64 bit)', 'Suse Linux Enterprise Server (64 bit)', NULL, NULL, NULL, 'amd64', 0x14, 'suse64Guest')

INSERT INTO tbl_IL_OS

(OSId, Name, Description, Edition, ProductType, Version, Architecture, OSFlags, VMWareGuestId) VALUES ('7a6b5e40-c2ae-4709-b789-1ed711817094', 'Suse Linux Enterprise Server 11 (32 bit)', 'Suse Linux Enterprise Server (32 bit)', NULL, NULL, NULL, 'x86' , 0x15, 'suseGuest')

>> 

???

hi everyone, the experts conference (TEC) kicks off in 3 weeks in vegas.

I will be speaking there on VMM and MS virtualization technologies. The first ever TEC for Virtualization & Cloud will be keynoted by Edwin Yuen, Director for Virtualization Strategy in the Server and Cloud Platform team at Microsoft. Join Edwin and other coworkers from the Microsoft technology leadership teams representing Active Directory, FIM, Exchange, SharePoint, PowerShell, and Virtualization & Cloud at the Red Rock Resort in Las Vegas, April 17-20, 2011!  For more information, please visit: www.theexpertsconference.com 

Please follow all the steps in this guide to successfully deploy Pet Shop. If you encounter any issues, post to the VMM forums and our team will help you fix them. 

Setting Up the Fabric

Hosts

Add Hosts/Clusters, create the necessary host groups that will provide the compute resources for the Pet Shop Application.

Networking

• Create Logical Network
  • Create Logical Network Definition
    • Attach it to a host group
• Associate Host Network Adapters with Logical Networks
  • In the host properties, go to networking tab and find the Network Adapter for which the Virtual Network is created.
  • Then in Hardware tab for host properties, go to the Network Adapter and mark the checkbox to set the logical network connectivity.

Library resources

To create the Pet Shop Application in VMM, you need to first download the library building blocks for Pet Shop.

• Go to https://Connect.Microsoft.Com
• Sign In using your Live ID
• Click on 'Browse the full Product Directory'
• Choose to Join the VMM 2012 Beta
  • Product: System Center in the Datacenter and Cloud
  • Program: SCVMM 2012 Public Beta
• Once you visit the SC VMM 2012 Beta page, click on Downloads
• Download the "PetShop Sample Resources"
  • This resource package contains the VHDs, Scripts and Applications necessary to create the Pet Shop application as a Service in VMM
• Once you extract the contents of the self-extractor, copy all the contents of the top level PetShop folder to the library share you want to use
• Refresh the library share that contains the Pet Shop resources you just copied

In case of Highly Available VMM setup, the application frameworks for installing Server App-V and Web Deploy clients are not added to the library and will need to be copied manually from VMM 2012 installation directory to the library share, for instructions on how to configure the library resources for Highly Available VMM setup, please refer to https://go.microsoft.com/fwlink/?LinkId=213988

Set Web Application Package Encryption Password

• Set the encryption password for the web app package petshop-ws08-v1.zip
  • Password: 123

Credential Management

In Pet Shop Service template, Run As Profiles are needed for

• SQL Server service accounts needed in configuring SQL Instance install in the SQL profile
• DAC instance installation in the Application Profile for the SQL tier
  • 1. Create a run as account for SQL Server Administrator: SQLAdminRAA

User: sa

Password: Passw0rd

Category: Profile Account

• 2. Create a run as profile SQLAdminRAP for the SQLAdminRAA
  • o Add SQLAdminRAA for the host group scope
  • o For deploying to cloud, add the RAA for the cloud scope as well
• 3. Create run as profile NTSystemRAP
  • o Add the built in "NT Authority\System" RAA for the host group scope
  • o For deploying to cloud, add the RAA for the cloud scope as well

Setting up the Cloud

• This section is needed only if you want to deploy the service to cloud, skip if your deployment is targeted to host groups.
• Create Cloud
  • o Set the cloud name and host group
  • o Set a Read Only library path to the share where the Pet shop resources (VHDs/Application Packages/Scripts) are located
  • o Add the Hyper-V capability profile
  • o If the run as profiles were scoped to a particular host group when created, then set the RAA/RAP association for RAA/RAP from the cloud properties.

Setting up the Self Service User Role

• This section is needed only if you want to deploy to cloud as Self Service User, skip if you want to deploy as a Full Admin.
• Create a Self Service user role
  • o Profile: Self Service User
  • o Members: <domain accounts designated for the role, i.e. Contoso\ServiceUser , etc.)
  • o Scope: select the cloud
  • o RunAsProfiles: add SQLAdminRAP & NTSystemRAP
  • o Actions: select all

After creating the user role, connect the Admin console using the desired user role.

Service Creation and Deployment

Pet shop service will be deployed from a service template that defines the profiles for hardware, guest OS, applications, and SQL.

Step 1. Create a New Service Template

• 1. Library workspace -> Home tab, click Create Service Template ribbon action.

• 2. Enter a name for the new Service Template, click OK.
• 3. The Virtual Machine Manager 2012 Service Template Designer opens.

Step 2. Create Virtual Machine Templates For the 3 Tiers of Pet Shop

The Virtual Machine template will contain information about the VHD used for this tier, along with hardware, operating system and application configuration.

Hardware Configuration identifies settings as memory, CPU, network adapter configuration, and cloud capability profiles in case deployments are made to the cloud.

Operating System Configuration identifies Operating system type, Computer Name, product key,  domain join info, operating system roles and features.

Application Configurations will contain the application packages, along with configuration scripts for each tier.

Scripts will be used to install application clients as Server App-V agent and Web Deploy agent, these scripts will be configured as Pre-Install scripts on the Application Profile level so that they execute before deploying any application in the application profile.

Scripts used to configure specific applications, should be configured as Pre-Install or Post-Install on the Application Deployment level.

For Pet Shop service template, we will create 3 Virtual Machine templates, one for each tier.

To create a VM template, click Create VM template button from the service template designer.

Create a Virtual Machine Template for the Web Tier

• 1. Click Create VM Template on the Service Template Designer.
• 2. In the select source page, use Existing VHD: Windows Server 2008 R2 Enterprise Evaluation.VHD
• 3. VM Template Identity: Enter the VM template name: ex. Web Tier VM Template
• 4. Configure Hardware as follows:
  • a. Select the disk, verify the check box for "Contains the operating system for the virtual machine" is marked.
  • b. Connect the Network Adapter of the hardware profile to the logical network created during fabric setup
  • c. For deploying to cloud, set the Capability Profile to Hyper V in the Compatibility of the hardware properties.

• 5. Configure the Operating System as follows:
  • a. Computer Name: MyWebVM##
    • i. Computer name should be short and unique to avoid conflicts in DNS.
    • ii. Patterns as ## will be automatically replaced by 01, 02, ...etc before deployment.
  • b. Admin Password: Passw0rd
  • c. Product key: 489J6-VHDMP-X63PK-3K798-CPX3Y
  • d. Operating System: 64-bit edition of windows server 2008 R2 Enterprise
  • e. Roles:
    • i. Application Development
    • ii. Basic Authentication
    • iii. Management Tools
    • iv. Web Server (IIS)
  • f. Features:
    • i. .NET Framework
    • ii. Background Intelligent Transfer Service (BITS)
    • iii. Message Queuing
  • g. Domain join:
    • i. Domain Name: provide the FQDN (ex. Contoso.com)
    • ii. Domain User: should be in (domain\user) format (ex. Contoso\User1)

• 6. Configure Applications: The application profile for the web tier will contain:
  • 1. Pre-install application profile script to install the Web Deploy client
  • 2. The web deploy application package
  • 3. Post-install application deployment script to configure the web deploy application

•  
  • Operating System: 64-bit edition of windows server 2008 R2
  • Add a Pre-Install Application Profile Script:

Click on Scripts option group, then from the toolbar, click Add ->Script.

•  
  •  
    • o Script command type: Pre-Install
    • o Executable: cmd.exe
    • o Parameters: /q /c InstallWebDeploy.cmd
    • o Script Package: WebDeploy_x64_en-US_1.1.0600.cr (1.1.0600)
    • o Timeout: 300
    • o Advanced options:
    • § Provide a standard output/error file paths for logging purposes

•  
  • Add Web Deploy Application:
    • o Application Package: petshop-ws08-v1.zip
    • o Provide values for application settings as follows:

• Add a Post-Install Application Deployment Script

Click on the Web Application, then from the toolbar click Add -> Application Script

• o Script Command type: Post-Install
• o Executable: cmd.exe
• o Parameters: /q /c configure-webtier.cmd
• o Script package: petshop.wt.cr
• o Timeout: 300
• o Advanced options:
  • § Provide a standard output/error file paths for logging purposes

7. Click Next in the Configure Applications page to commit the changes made in the previous step.

             8. Go to the Summary page, and click Create.

Create a Virtual Machine Template for the Middle Tier

• 1. Click Create VM Template on the Service Template Designer.
• 2. In the select source page, use Existing VHD: Windows Server 2008 R2 Enterprise Evaluation.VHD
• 3. VM Template Identity: Enter the VM template name: ex. Middle Tier VM Template
• 4. Configure Hardware as follows:
  • a. Select the disk, verify the check box for "Contains the operating system for the virtual machine" is marked.
  • b. Connect the Network Adapter of the hardware profile to the logical network created during fabric setup
  • c. For deploying to cloud, set the Capability Profile in the Compatibility of the hardware properties.

• 5. Configure the Operating System as follows:
  • a. Computer Name: MyMidVM##
  • b. Admin Password: Passw0rd
  • c. Product key: 489J6-VHDMP-X63PK-3K798-CPX3Y
  • d. Operating System: 64-bit edition of windows server 2008 R2 Enterprise
  • e. Roles:
    • i. Application Development
    • ii. Basic Authentication
    • iii. Management Tools
    • iv. Web Server (IIS)
  • f. Features:
    • i. .NET Framework
    • ii. Background Intelligent Transfer Service (BITS)
    • iii. Message Queuing
  • g. Domain join:
    • i. Domain Name: provide the FQDN (ex. Contoso.com)
    • ii. Domain User: should be in (domain\user) format (ex. Contoso\User1)

• 6. Configure Applications: The application profile for the middle tier will contain
  • 1. Pre-install application profile script to install Server App-V client
  • 2. The Server App-V application package for the middle tier
  • 3. Pre-install application deployment script to configure the Server App-V application

• Operating System: 64-bit edition of windows server 2008 R2
• Add a Pre-Install Application Profile Script:

Click on Scripts option group, then from the toolbar, click Add -> Script.

•  
  • o Script command type: Pre-Install
  • o Executable: cmd.exe
  • o Parameters: /q /c InstallSAV.cmd
  • o Script Package: SAV_x64_en-US_4.7.11.1127.cr (4.7.11.1127)
  • o Timeout: 300
  • o Advanced options:
    • § Provide a standard output/error file paths for logging purposes
• Add Virtual Application:
  • o Application Package: Petshop-Midtier64
  • o Provide values for application settings as follows:

• Pre-Install Application Deployment Script

Click on the Virtual Application then from the toolbar click Add -> Application Script

• o Script command type: Pre-Install
• o Executable: cmd.exe
• o Parameters: /q /c configure-midtier.cmd
• o Script package: petshop.mt.cr
• o Timeout: 300
• o Advanced options:
  • § Provide a standard output/error file paths for logging purposes

• 7. Click Next in the Configure Applications page to commit the changes made in the previous steps.
• 8. Go to the Summary page, and click Create.

Create a Virtual Machine Template for the SQL Tier

• 1. Click Create VM Template on the Service Template Designer.
• 2. In the select source page, use Existing VHD: SQL Server 2008 R2 Evaluation (SQLPROFILE) on Windows Server 2008 R2.VHD
• 3. VM Template Identity: Enter the VM template name: ex. SQL Tier VM Template
• 4. Configure Hardware as follows:
  • a. Select the disk, verify the check box for "Contains the operating system for the virtual machine" is marked.
  • b. Connect the Network Adapter of the hardware profile to the logical network created during fabric setup
  • c. For deploying to cloud, set the Capability Profile in the Compatibility of the hardware properties.

• 5. Configure the Operating System as follows:
  • a. Computer Name: MySQLVM##
  • b. Admin Password: Passw0rd
  • c. Product key: 489J6-VHDMP-X63PK-3K798-CPX3Y
  • d. Operating System: 64-bit edition of windows server 2008 R2 Enterprise
  • e. Domain join:
    • i. Domain Name: provide the FQDN (ex. Contoso.com)
    • ii. Domain User: should be in (domain\user) format (ex. Contoso\User1)

• 6. Configure Applications: The application profile for the SQL Tier will contain:
  • 1. Four DACPAC application packages for the database definitions
  • 2. Post-install application profile script to configure the data tier by creating the sql login for the databases and populating the data in the SQL tables.

• Operating System: 64-bit edition of windows server 2008 R2
• DAC Application Deployment for Pet shop Database:
  • o Application package: mspetshop4.dacpac
  • o Authentication: SQL Server Authentication
  • o Deployment Run As Profile: SQLAdminRAP

•  
  • DAC Application Deployment for Pet shop Orders Database:
    • o Application package: mspetshop4orders.dacpac
    • o Authentication: SQL Server Authentication
    • o Deployment Run As Profile: SQLAdminRAP

• DAC Application Deployment for Pet shop Profile Database:
  • o Application package: mspetshop4profile.dacpac
  • o Authentication: SQL Server Authentication
  • o Deployment Run As Profile: SQLAdminRAP

 

• DAC Application Deployment for Pet shop Services Database:
  • o Application package: mspetshop4services.dacpac
  • o Authentication: SQL Server Authentication
  • o Deployment Run As Profile: SQLAdminRAP

• Post-Install Application Profile Script
• Click on Scripts option group, then from the toolbar, click Add ->Script.
  • o Script command type: Post-Install
  • o Executable: cmd.exe
  • o Parameters: /q /c configure-datatier.cmd @sqlAdmin@ @sqlAdminPassword@
  • o Script package: petshop.sql.cr
  • o Timeout: 300
  • o Advanced options:
    • § Provide a standard output/error file paths for logging purposes
• 7. SQL Server Configuration

The SQL Profile will specialize the sysprep SQL Server Image. The sysprep SQL image is included in the SQL Profile VHD: SQL Server 2008 R2 Evaluation (SQLPROFILE) on Windows Server 2008 R2.VHD

• Create new SQL Server Deployment
• SQL Server Deployment:
  • o Instance name: MSSQLSERVER
  • o Instance id: SYSPREPSQL
• Configuration:
  • o Media source: C:\SQLEVAL
  • o SQL Admins: add a valid domain account
  • o Security Mode: SQLServerAuthentication
  • o SA Password RAP: SQLAdminRAP
  • o Enable named pipes: true
  • o Enable TCP: true
• Service accounts
  • o SQL server service: NTSystemRAP
  • o SQL server agent: NTSystemRAP
  • o Reporting services: NTSystemRAP
• 8. Go to the Summary page, and click Create.

Step 3: Add the Machine Tier Templates to the Service Template

• 1. Open the Service Template Designer if it's not already opened.
• 2. On the VM Templates tab, select the VM template for the Web Tier, Drag and drop it onto the service template designer canvas.
• 3. Repeat step 2 for the Middle and SQL Tier VM templates.
• 4. For customizing tier properties as deployment option, instance counts, ...etc. select a machine tier template in the canvas and view/change properties from the details pane.
• 5. In the Service Template Designer, click Save.

Step 4: Configure and Specialize the Service Instance

• From the service template designer, click on Configure Deployment.
  • o Set the name and destination for the new service instance.

• The Specialization UI will open.
  • o Check the generated VM/Computer names, and change them if needed
    • § It's a good practice to ping the VM computer name from the VMM server to make sure that the name you chose is not currently being used by another machine in the domain
  • o Provide Values for the service global settings as follows:
    • § petshopUser=mspetshop
    • § petshopPassword=pass@word1
    • § sqlAdmin=sa
    • § sqlAdminPassword=Passw0rd
    • § sqlComputerName=<your sql-tier computer name>
    • § lobComputerName = <your mid-tier computer name>

Step 5: Deploy the Service and Verify

• From the Specialization UI, Click on Deploy
• Verification
  • o After the deployment completes, open IE and connect to Pet Shop application.
  • o URL: Error! Hyperlink reference not valid.
  • o The website should open

Deploying-Pet-Shop-Service-in-VMM_2.docx

hi everyone, this is a troubleshooting blog post on how to fix and issue with VMM 2012 where the VMM service crashes with System.Runtime.InteropServices.COMException (0x8007200A): The specified directory service attribute or value does not exist.

Big thanks to Radhika from the VMM team for compiling this troubleshooting item.

Scenarios: This error could happen while adding a Host/Cluster or creating a new Virtual Machine.

Possible cause 1: This could happen if the VMM service account is running as a Local System account. Some AD configurations might not allow using Local System to read the AD tree. For example, if the Authenticated User Permissions are removed from the default Active Directory containers, including the Users, Configuration or System, and organizational units (OUs) where User and Computer objects are stored, we might not be able to query AD.

Workaround solution 1: Try changing the VMM service to run as a domain service account (not necessary domain admin, but any account with read rights to Active Directory).

Possible cause 2: This could also happen if VMM service account is running as regular domain account but that domain account does not have appropriate permissions to read the AD tree.

Solution 2: Try adding the read permission to the domain account used as the VMM service account for the whole AD hierarchy or change VMM service to run as a domain account with read permissions to AD tree.

Stack trace snippet from logs:

00000516             44.95616913       [4264] 10A8.0B40::03/15-19:28:42.150#04:WatsonExceptionReport.cs(756): Unhandled exception caught.           

00000517             44.95740128       [4264] 10A8.0B40::03/15-19:28:42.151#04:WatsonExceptionReport.cs(757): Unhandled exception.         

00000518             44.96680450       [4264] 10A8.0B40::03/15-19:28:42.158#04:WatsonExceptionReport.cs(757): System.Runtime.InteropServices.COMException (0x8007200A): The specified directory service attribute or value does not exist.    

00000519             44.96680450       [4264] 

00000520             44.96680450       [4264]    at System.DirectoryServices.DirectoryEntry.Bind(Boolean throwIfFail)  

00000521             44.96680450       [4264]    at System.DirectoryServices.DirectoryEntry.Bind()         

00000522             44.96680450       [4264]    at System.DirectoryServices.DirectoryEntry.get_SchemaEntry()              

00000523             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.ADStoreCtx.IsContainer(DirectoryEntry de)     

00000524             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.ADStoreCtx..ctor(DirectoryEntry ctxBase, Boolean ownCtxBase, String username, String password, ContextOptions options)   

00000525             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.PrincipalContext.CreateContextFromDirectoryEntry(DirectoryEntry entry)                

00000526             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.PrincipalContext.DoLDAPDirectoryInitNoContainer()   

00000527             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.PrincipalContext.DoDomainInit()          

00000528             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.PrincipalContext.Initialize()                

00000529             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.PrincipalContext.get_QueryCtx()          

00000530             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithTypeHelper(PrincipalContext context, Type principalType, Nullable`1 identityType, String identityValue, DateTime refDate)                

00000531             44.96680450       [4264]    at System.DirectoryServices.AccountManagement.Principal.FindByIdentityWithType(PrincipalContext context, Type principalType, IdentityType identityType, String identityValue)

00000532             44.96680450       [4264]    at AccountHelper.ResolvePrincipal(String principalName, String& domain)          

00000533             44.96680450       [4264]    at AccountHelper.IsADGroup(String user)          

00000534             44.96680450       [4264]    at Microsoft.VirtualManager.DB.DelegatedAdmin.UserRoleDBHelper.UpdateOwnerOfSharedObject(SqlContext ctx, Guid objectId, CarmineObjectType objectType, Guid roleId, UserOrGroup userOrGroup)      

https://blogs.technet.com/b/scvmm/archive/2011/03/24/system-center-virtual-machine-manager-2008-r2-sp1-available-now.aspx

https://blogs.technet.com/b/scvmm/archive/2011/03/22/system-center-virtual-machine-2012-beta-available-now.aspx

my co-worker Vishwa just posted a great article that includes tips on how to tune Virtual Machine Manager for VDI scenarios.

https://blogs.technet.com/b/vishwa/archive/2011/02/01/tuning-scvmm-for-vdi-deployments.aspx

https://blogs.technet.com/b/mkleef/archive/2011/01/19/scvmm-rds-connection-broker-plugin-released.aspx

You can find the connector MSI package and the related documentation here. https://go.microsoft.com/fwlink/?LinkID=195952

Just install on top of VMM 2008 R2 Administrator Console and you can take advantage of dynamic placement VDI scenarios through VMM.

i wanted to let you know I will be attending Tech-Ed Europe in Berlin from 8 - 12 of November. If any of you plan to attend, stop by the Virtual Machine Manager booth to chat.

cheers.

Use the following steps to resolve a name mismatch error when viewing the remote desktop connection of a VM on a Hyper-V host through VMM (using the Virtual Machine Viewer application). The VMM server in this case is running as a virtual machine.

When you execute the "Connect to virtual machine" action from the VMM Administrator Console, you will get the following error: "The remote computer could not be authenticated due to problems with its security certificate. It mabe be unsafe to proceed". In this case, the popup with the error will give you the Name mismatch parameters. For example:

Requested remote computer: 192.168.1.250

Name in the certificate from the remote computer: democomputer.redmond.contoso.corp.com

How to troubleshoot and fix this issue: 

• Use the Internal nic for all virtual machines including the Virtual Machine Management server
• Add the FQDN of the Hyper-V server to local hosts file on the VMM server (which is located in C:\Windows\System32\Drivers\etc\host. You'll need to change the folder options to view the extensions for known file types. An example entry looks like this. 192.168.1.250 democomputer.redmond.contoso.corp.com.
• When adding the host into Virtual Machine Manager, make sure you use the FQDN (democomputer.redmond.contoso.corp.com) and clear the option for host to be in a trusted domain (use the non-trusted domain authentication)
• Finish the rest of the steps to add the host.
• It will take a few minutes to populate all the virtual machines that are running on the Hyper-V host. Once populated, select a VM and connect to it. You'll get prompted with an error warning. Click on the View certificate button and install the certificate by choosing to manually decide where to place the certificate and click the browse button to install it to the trusted root certification authority. Close the dialog box.
• From your VMM server click start, run, and type MMC. From the menu bar select File, then select Add\Remove Snap-in. Select Certificates and then select Add for User. Repeat this process and Add Certificates for local computer.
• Next copy your democomputer.redmond.contoso.corp.com certificate from the user trusted root to the following three places. Right-click the certificate and select copy and then paste into:

  a. Certificates - Current User -> Personal -> Certificates

  b. Computer (Local Computer) -> Personal -> Certificates

  c. Computer (Local Computer) -> Trusted Root Certification Authorities

• Go back to VMM console and attempt to connect to the VM. You'll probably be prompted for your credentials. Enter your valid domain credentials, i.e. contoso\anotheradmin and select the option to remember my credentials.
• At this point you should now be able to connect to a virtual machine without any errors.