no longer applies, and SCVMM lists only its minimum and recommended values
regardless of the number of managed hosts. You can certainly exceed these
maximums if you find that memory is low (though that should be unlikely), but I
don’t recommend that you go below the minimum supported for the startup unless
perhaps you have a small lab environment with only a couple of hosts and you are
short on memory.
You must specify an account to be used to run the SCVMM service during the
installation of SCVMM. During installation, you are given the option either to specify
a domain account or to use Local System. Don’t use Local System; although it may
seem like the easy option, it limits some capabilities of SCVMM (such as using shared
ISO images with Hyper-V virtual machines) and can make troubleshooting difficult
because all of the logs will show Local System instead of an account dedicated to
SCVMM. On the flip side, don’t use your domain Administrator account, which has
too much power and would have the same problem troubleshooting because you
would just see Administrator everywhere. Create a dedicated domain user account just
for SCVMM that meets your organization’s naming convention, such as svcSCVMM or
VMMService. Make that account a local administrator on the SCVMM server by
adding the account to the local Administrators group. You can do this with the
following command, or you can use the Server Manager tool to navigate to
Configuration ➢ Local Users And Groups ➢ Groups and add the account to the
Administrators group.
C:\ >net localgroup Administrators /add savilltech\svcSCVMM
The command completed successfully.
Do not use a generic domain service account for different applications. This can cause
unexpected results and once again makes troubleshooting hard. Use a separate
account for each of your services—one for SCVMM, one for System Center Operations
Manager (in fact, you need more than one for Operations Manager), another for
System Center Configuration Manager, and so on. What do I mean by unexpected
results? When SCVMM manages a host, it adds its management account to the local
Administrators group of that host—in my case, svcSCVMM. If that host is removed
from SCVMM management, that account is removed from the local Administrators
group of that host. Now imagine you use a shared service account between SCVMM
and another application that also needs its service account to be part of the local
Administrators group. When you remove the host from SCVMM management, that
shared service account is removed from the local Administrators group on that host,
so you just broke that other application.
If you have multiple SCVMM servers in a high-availability configuration, the same
domain account is used on all servers. It’s a requirement to use a domain account in a
SCVMM high-availability scenario or if you have a disjointed namespace in your
domain. For information on disjointed namespaces, see
[http://support.microsoft.com/kb/909264. Ideally, this is not something you have in](http://support.microsoft.com/kb/909264. Ideally, this is not something you have in)
your environment because it can be a huge pain for many applications.