donderdag 24 maart 2011 0:09
Kurt Roggen
SCVMM 2012 BETA: Installing a standalone VMM Management Server
This scenario is the installation of a standalone VMM Management Server, where both VMM Server and VMM Database (SQL Server only) live on the same box, actually a virtual machine in my case.
By placing the virtual machine in a Hyper-V cluster, you also achieve HA for VMM, but it will not provide any high availability at the application level (for both VMM and SQL). So you are not protected from VMM failures or SQL failures… There are many installation variations, but with VMM 2012 you are able to achieve complete high availability for VMM and it’s surrounding components (SQL, Library, Self-Service Portal).
VMM Setup is split up into several steps:
- Software and Hardware Pre-requisites check
- Database configuration
- Account configuration (Service Account and Distributed Key Management)
- Port configuration
- Library configuration (Default SCVMM Library Server and Share)
NOTE: If during the setup you encounter any problem, consult the log files that are located in the %SYSTEMDRIVE%\ProgramData\VMMLogs folder.
Using VMM Setup, you are able to do 3 things:
Install the VMM Management server Install the VMM Console (including VMM PowerShell cmdlets) Install the VMM Self-Service Portal
Both hardware and software prerequisites are checked.
For more information, see System Center TechCenter: SCVMM 2012 System Requirements and Supported Operating Systems
Make sure you meet the Software Prerequisites: Supported versions of
- OS: Windows Server2008 R2 (Full Installation) only
- WinRM 2.0, PowerShell 2.0
- .NET Framework 3.5 SP1
- WAIK 2.0 or above (for Windows 7)
- VMM Database: SQL 2008 SP2 or higher (NO SQL Express edition)
- VMM Self-Service Portal: IIS 7.5 components
WAIK (for Windows 7) no longer ships with VMM 2012 and need to be downloaded separately here.
Make sure you meet the Hardware Prerequisites:
- Memory: Minimum 2 GB
- Processor
- Disk space
Our installation scenario will have the VMM Database hosted on the SQL Server running locally on the same box as the VMM Server.
You require a full version of SQL Server 2008 SP2 or higher. SQL Server Express no longer ships with VMM 2012 and is no longer supported.
Service Account:
- If you plan to use shared ISO images with Hyper-V virtual machines, you must use a domain account.
- If you are installing a highly available VMM management server, you must use a domain account.
Distributed Key Management:
- If you are installing a highly available VMM management server, you must use distributed key management to store encryption keys in ADDS.
Assure that the specified VMM service account is member of the local group Administrators.
| Port Configuration: |
| VMM Server <> VMM Console, SSP: Uses by default port 8100 |
| BITS: Uses by default HTTPS port 443 |
| WinRM 2.0: Uses by default HTTP port 5985 |
Bare-metal Hyper-V Host deployments:
- VMM Server <> WDS: Uses port 8102
- VMM Server <> WinPE agents: Uses port 8101
- VMM Server <> WinPE TimeSync: Uses port 8103 |
Still required to create a default SCVMM library share. However, with VMM 2012 you are able to remove it once you have your “real“ library servers up and running.
Review of the installation summary
VMM 2012 Beta installation in progress.
Related reading:
Filed under: VMM2012