I am walking through the installation of SCVMM 2008 R2 SP1 on a new server that I just setup in my demo environment. Hope this is helpful. First lets look at the system requirements. If you want to setup your environment with multiple servers or you want to do a custom install you can find the requirements here. I am doing my install on a virtual machine that is being hosted on a Lenovo W510 laptop using Boot2VHD technology. If you want to do the same, you might want to checkout a post I did on automatically creating BCDEdit data for a Boot2VHD System.
I am starting with a sysprep’d Windows Server 2008 R2 Server. I have allocated 2 processors and 512mb memory to the guest using dynamic memory. Once I get the system up and running, I will bump up the memory to be close to what I actually need but I will leave it dynamic.
I am going to be installing the Administrator console as well as the Self-Service portal on my machine. I need to install some prerequisite software before I can install SCVMM.
If you would like more detail on the installation of IIS see How To Install IIS 7 on Windows Server 2008 R2 SP1 For Use With SCVMM 2008 R2 SP1
We now have IIS and SQL Server 2008 R2 configured and the firewall ports open for SQL and for IIS.
Default VMM library server: VMM uses library servers and library shares to store file-based resources, such as ISO images and virtual hard disks that can be used to create virtual machines. The VMM library also makes available virtual machine templates, guest operating system profiles, and hardware profiles that reside in the VMM database. You can also store virtual machines in the library when they are not in use. When you install the VMM server, Setup also adds the computer as the default library server, and you have the option to either create a new default library share on the VMM server or use an existing share on the VMM server as a library share. After setup is complete, you can add other library shares to the default library server or other library servers on separate computers. Important: You cannot remove or relocate the default library server or its library share. Give careful consideration to the location of the default library share before installing the VMM server.
Time to put the media in and start the VMM installation
Make sure you are logged into the machine as a Domain account that is also a local Administrator
On the product media or network share, right-click setup.exe, and then click Run as administrator.
On the Setup menu, click VMM Server.
On the Microsoft Update page, indicate whether or not you want to use Microsoft Update. Note If you have previously chosen to use Microsoft Update on this computer, the Microsoft Update page does not appear.
On the Customer Experience Improvement Program (CEIP) page, click Yes to participate in, or No to opt out of, the CEIP. I am opting out.
On the Prerequisites Check page, review any alerts or warnings about hardware that does not meet the minimum or recommended requirements, or missing software prerequisites. You can continue the installation if you receive warnings, but you must resolve all alerts before you can proceed with the installation. For more information, see System Requirements: VMM Server. In my case all is well so I will just click Next.
On the Installation Location page, type an installation path for the program files or click Next to use the default path. In my case, I just changed the drive to E: to put the application on my data volume.
On the SQL Server Settings page, select the appropriate Microsoft SQL Server settings for your VMM database.
Important If you specify a remote SQL Server instance, there are additional configuration steps you must perform. For more information, see Configuring a Remote Instance of SQL Server for VMM (http://go.microsoft.com/fwlink/?LinkID=134060).
If you followed my instructions above you would simply put in the values from your installation of SQL Server 2008 R2.
Note
On the Library Share Settings page, select the option to either create a new default library share on the VMM server or use an existing share on the VMM server as a library share. The default library share created by VMM is named MSSCVMMLibrary and its folder is located at %SYSTEMDRIVE%\ProgramData\Virtual Machine Manager Library Files. As has been the case with all other location decisions, I have changed the path to point to my E drive. I also created a folder called VMM-Library and selected that folder.
Important After setup is complete, you can add other library shares to the default library server or other library servers on separate computers; however, you cannot remove or relocate the default library server or its library share. So give careful consideration to the location of the default library share before installing the VMM server.
On the Installation Settings page, in the Ports area, type the ports that you want to use for the VMM server connections, and, in the VMM service account area, do one of the following:
If you use a domain account for the VMM service account, it is strongly recommended that you create an account that is specifically designated to be used for this purpose. When a host is removed from the VMM server, the account that the VMM service is running under is removed from the local Administrators group of the host. If the same account is used for other purposes on the host, this can cause unexpected results. You also should not use the same account for the VMM service account that you use for configuring a remote SQL Server for the VMM database. For more information, see Hardening the VMM Server (http://go.microsoft.com/fwlink/?LinkID=145055).
Important If you plan to use shared ISO images with Hyper-V virtual machines, you must use a domain account for the VMM service account.
Important If you are using a disjointed namespace, you must use an account other than the Local System account. A disjointed namespace occurs when one or more computers have a primary Domain Name System (DNS) suffix does not match the DNS name of the Active Directory Domain Services (AD DS) domain of which the computers are members. For example, a member computer that uses a primary DNS suffix of corp.fabrikam.com in an AD domain named na.corp.fabrikam.com is using a disjointed namespace. For more information about a disjointed namespace, see Naming conventions in Active Directory for computers, domains, sites, and OUs (http://go.microsoft.com/fwlink/?LinkId=123886).
Important It is a best practice to not use the default port settings. The port settings that you assign during the VMM server installation cannot be changed without uninstalling and reinstalling VMM server. The ports that you assign during setup must identically match the port settings that you assign when installing the related VMM components that the VMM server communicates with. For more information, see VMM Ports and Protocols (http://go.microsoft.com/fwlink/?LinkID=128912). Consider this… All other web services IIS and SQL Reporting will default to port 80! I will take the default.
Note The value of the File transfers to agents on hosts and library servers port cannot exceed 32768.
On the Summary of Settings page, review the settings that you chose and if all is well, just click Install
On the Installation page, do one of the following:
Note When you install the VMM server, all accounts in the local Administrators security group are automatically added to the VMM Administrator user role. If you want to add or remove user accounts from the VMM Administrator user role, see Managing User Roles (http://go.microsoft.com/fwlink/?LinkID=125951).
Now that we have the server installed and running, we need to install a client so we can connect to it.
Resources that were helpful in putting this post together: http://technet.microsoft.com/en-us/library/cc793149.aspx
Important After you have finished installing the VMM components, there are additional tasks required to make VMM fully functional and optional configuration tasks depending on how you implement VMM in your environment. Case in point… check out Backing Up and Restoring the VMM Database
I will do a separate post on adding a Hyper-V Host to the VMM. I will also do a separate post on Integrating VMM with SCOM. And yet another to add the Self Service Portal in the days or weeks to come.
Awesome , keep up this good work : love the way you explain and the screen shots help alot .. Totally perfect ...please keep this up THANK YOU