In this post, I will explain with videos how to configure Lab Management 2013 with SCVMM 2012 R2 so we can create and manage SCVMM environments in Team Foundation Server 2013. For more information, visit the MSDN Configuring Lab Management for SCVMM Environments.
The following are the steps:
- Installing HV and verifying it is working properly
- Improving the reliability of WinRM
- Installing SCVMM 2012 R2 prerequisites
- Creating 2 folders: SCVMM Library and SCVMM VMs
- Installing SCVMM 2012 R2
- Adding Hyper-V Host to SCVMM 2012 R2
- Installing SCVMM Admin Console on TFS machine
- Configuring Lab Management for Team Foundation Server
- Installing and configuring Test Controller
- Verifying Lab Management and Test Controller configured successfully
- Note-1: Stopping and starting WinRM with SCVMM
- Note-2: Fix SPN that VMM requires were not correctly registered
1. Installing Hyper-V and verifying it is working properly
2. Improving the reliability of WinRM
See how to increase the maxtimeoutms for Windows Remote Management, which is required for Lab Management.
3. Installing SCVMM 2012 R2 prerequisites
See how to install System Center Virtual Machine Manager 2012 R2 prerequisites.
4. Creating 2 folders: SCVMM Library and SCVMM VMs
Creating one folder for the Library share that will hold templates and VMs and another folder for the deployed VMs.
5. Installing SCVMM 2012 R2
6. Adding Hyper-V Host to SCVMM 2012 R2
7. Installing SCVMM Admin Console on TFS machine
8. Configuring Lab Management for Team Foundation Server
9. Installing and configuring Test Controller
10. Verifying Lab Management and Test Controller configured successfully
11. Note-1: Stopping and starting WinRM with SCVMM
In case you want to stop and start Windows Remote Management with System Center Virtual Machine Manager installed, you will have to stop the System Center Virtual Machine Management Agent and start it manually.
12. Note-2: Fix SPN that VMM requires were not correctly registered
See the following video if you encounter the following error:
The Service Principal Names (SPNs) that VMM requires were not correctly registered when the VMM management server