Figure 5.9 Local management tools are not wanted on a Hyper-V server that should
be at the Server Core configuration level.
Actions after Installation of Hyper-V
Once the Hyper-V role is enabled on a server, several important steps and processes
need to be in place. Some obvious actions, such as actually creating virtual machines,
are covered later in this section and throughout the book. There are other items,
though, that you need to ensure are implemented or at least considered:
Add the server to SCVMM. This should be the first action before you create NIC
teams, configure Fibre Channel, create virtual switches, join clusters, or anything
else, because all of these items can be configured and managed through SCVMM in
a centralized fashion. Once the SCVMM agent is installed on the host and is being
managed by SCVMM, you should add to clusters, deploy logical switches, and so
on, to make the server ready to host workloads.
If you are not using SCVMM, you should create NIC teams and virtual switches
according to the guidelines discussed in Chapter 3. Remember to use a consistent
naming scheme for your switches to ensure that there is no network connectivity
interruption when you’re live-migrating virtual machines between hosts.
Add the server to a cluster or create a new cluster and add cluster disks to Cluster
Shared Volumes to enable simultaneous access to the storage across the cluster.
If you are running antivirus software on the Hyper-V hosts, ensure that you have
the proper exclusions configured, or problems can arise due to locking by the
malware solution. The key exclusions for files and processes, documented at
http://support .microsoft.com/kb/961804/en-us, are essentially blocking
everywhere virtual machines are stored and the vmms.exe and wmwp.exe processes.
Another option is not to run malware protection, but most security departments
would not be OK with this. If you consider that the Hyper-V server is running
Server Core, with no one ever logging on to the box or running other applications,