Installing and Configuring Systems Center Virtual Machine Manager 2008 in Software

Maker QR Code in Software Installing and Configuring Systems Center Virtual Machine Manager 2008

2 In the VMM Roles and Computer Names area, specify the VMM roles and functions that you want to evaluate and enter the names of the computers you want to scan by doing one of the following: To scan the local computer for all VMM roles, do not change the default settings To scan the local computer for only some VMM roles, clear the check box for each VMM role for which you do not want to scan the local computer

NOTE When you scan the local computer, the VMMCA uses the credentials that you logged on with, which must be those of a local administrator You cannot provide different credentials for scanning the local computer When you scan the local VMM server and the VMM database is installed on a remote SQL Server instance, the name of the remote computer is prepopulated and it is also scanned The credentials for scanning a remote VMM database computer must be those of a member of the sysadmin server role on that computer and usually are the same account that you used to install VMM Unless you specify different credentials, the VMMCA uses the credentials that you logged on with To specify different credentials, click Credentials, and then in the Remote Database Administrator Credentials dialog box, enter the appropriate credentials You cannot change the computer name for the VMM server or the VMM database server You can clear the VMM Server check box to exclude it and the VMM database server from the scan To scan a remote computer for either the VMM Administrator Console or VMM Self-Service Portal role, enter the name of the remote computer and, if necessary, provide different credentials in the Credentials area You can scan different computers for the VMM Administrator Console role and the VMM Self-Service Portal role at the same time

NOTE When you scan a remote computer, the VMMCA uses the credentials that you logged on with, unless you specify different credentials in the Credentials area The credentials for a remote computer must be those of a domain account that is a local administrator on the remote computer To scan the configuration of one or more computers that either are serving or might serve a specific VMM function, do the following: a Select the Other Computers check box, and then, in the Other Computers list, click a VMM function b Type the name of a computer that you want to scan, and then click Add Repeat this step until all the computers that you want to scan are included in the list

NOTE You can scan computers for only one VMM function at a time, but you can scan multiple computers for the same VMM function Before you can scan a computer for the VMware VirtualCenter server function, you must first add a VMware VirtualCenter server to VMM 3 After you have specified all VMM roles or functions, and associated computer names, click Scan NOTE If you are scanning remote computers, the VMMCA must authenticate the credentials on all remote computers before it can begin scanning This might take several minutes Once the installation is complete, you can start the Configuration Analyzer from Start | All Programs | Virtual Machine Manager Configuration Analyzer | Configuration Analyzer

5:

You cannot change the VMM server name because VMMCA needs to be run on the server that will be the eventual SCVMM server You can, however, change the server names for systems that could possibly run the VMM Administrator Console and or the VMM Self-Service Portal

Installation is a pretty straightforward affair But before you install SCVMM, keep these issues in mind: Install the latest Microsoft Quick Fix Engineering (QFE) updates for Hyper-V and clustering through Windows Server Update Services Make sure that your shared storage solution is compliant with both Windows Server 2008 and Hyper-V clustering Some solutions may be Windows Server 2008 compliant but not support Hyper-V clustering You can check this by confirming with your storage vendor to find out whether updates to existing firmware and drivers are necessary Use the Node and Disk Majority option for the cluster witness model (this is also called the quorum in previous Windows Server versions) in most single-site cluster deployments Check with your storage vendor for the optimal selection Use Server Core deployments as often as possible for host servers and VMs Not only do they provide administrative benefits, but VMs using Server Core installations can also fail over much more quickly than VMs using similarly configured full installations with a GUI Additionally, because Server Core installations require less memory and fewer hard disk resources than full installations, the same host space can support additional VMs For hard disks, provision one or more discrete logical units (LUNs) to each VM to enable individualized VM failover Also, use highly available mount points for implementing more than 21 drive letters (LUNs) within a cluster, and use fixed virtual hard disks for optimal flexibility and best performance For scalable solutions, add a single dedicated Gigabit Ethernet NIC port for every four VMs, depending on individual VM network I/O requirements These guest network NIC ports are in addition to the other required ports recommended for Hyper-V parent partition accessibility, cluster heartbeats, and iSCSI connectivity (if required)

Once all prerequisites are configured for the scenario that you ve chosen, insert the Systems Center Virtual Machine Manager 2008 disk into your SCVMM server