Office of Education Technology (OET) Microsoft Hyper-V Standards

Size: px

Start display at page:

Download "Office of Education Technology (OET) Microsoft Hyper-V Standards"

Alexander Pearson
8 years ago
Views:

1 Office of Education Technology (OET) s Version 1.0 Reference # - 12/3/08

2 Document Owner: Approver(s): Date Created: Date Approved: Summary: This document contains various standards for the implementation of Microsoft Windows Server 2008 Hyper-V within OET. Purpose and Scope: This standard applies the Hyper-V technology as implemented by Data Center Services. Reason for Implementing: Naming & configuration standards will reduce support complexity and effort and save time. I. Virtualization Host Naming This naming standard applies to the Windows 2008 servers that are serving as virtualization (Hyper-V) hosts. It does NOT apply to the virtual machines themselves or to the guest Operating Systems. This standard is based on the existing standard 0019 OET Managed Server Naming Standards. : EDOETHVHROLE_IDENTIFIER ROLE_IDENTIFIER Is P, Q, T, or R followed by a digit (per the OET Managed Server Naming Standard) EDOETHVHT1 EDOETHVHP1 II. Virtualization Host Network Connections Naming This naming standard applies to network connections defined on the Virtualization host and visible on the Network Connections and Network and Sharing Center screens in Server ZONE_CONNECTION_TYPE_COUNTER ZONE should be VENDOR for the Vendor zone, KETSSS for the KETS Shared Services zone, and KDE for the KDE zone CONNECTION_TYPE is MGMT for a management connection and VM for a virtual machine guest connection Version /3/08 Page 2

3 COUNTER is a number used to distinguish between multiple network connections that are of the same type KDE_MGMT_1 KETSSS_VM_1 Note: See also the Network Connection configuration standard elsewhere in this document. III. Virtual Machines Naming This naming standard applies to Virtual Machines that are (or will be) active systems, as opposed to model/template VMs. GUEST_SERVER_NAME GUEST_SERVER_NAME is the name of the guest OS (just the first part, not the FQDN). KDEDATAN1 IV. Virtual Network Switch Naming This naming standard applies to Virtual Network Switches. TYPE_[ZONE]_COUNTER_SWITCH TYPE is EXT for an External network, INT for an Internal network, PRIV for a Private network ZONE should be VENDOR for the Vendor zone, KETSSS for the KETS Shared Services zone, and KDE for the KDE zone IF this is an External network. For Internal and Private networks, other possible values will be determined over time. COUNTER is a number used to distinguish between multiple switches that are of the same Type and Zone this will happen when a host server has multiple NICs and more than one is connected to the same Zone. EXT_KETSSS_1_SWITCH EXT_KETSSS_2_SWITCH INT_DISTDMZCOPY_1_SWITCH Version /3/08 Page 3

4 V. Model/Template Virtual Machine Naming This naming standard applies to virtual machines that are created as models or templates from which to create actual guest VMs. VENDOR_PRODUCT[_EDITION]_VERSION_ServicePackOrOtherVersionDetail[_Distin guishingdetail]_sysprepstatus_template VENDOR is the software producer PRODUCT is the product name, abbreviated only if absolutely necessary EDITION is optional and is only used when the product comes in different editions (such as Home, Professional, etc) VERSION is the primary version as widely identified by the vendor ServicePackOrOtherVersionDetail is detailed version information, such as service pack, Beta, etc. DistinguishingDetail is optional and includes any other information that makes this particular template unique, such as additional software installed, an unusual network configuration, etc. SysPrepStatus is WithSysprep if SysPrep has been done and NoSysPrep if SysPrep has not been done. Microsoft_Windows_Server_Std_2008_RC1_NoSysPrep_TEMPLATE Microsoft_Windows_Pro_XP_SP2_wOutlook_SysPrep_TEMPLATE Microsoft_Windows_Business_Vista_RTM_ForWebAppTesting SysPrep_TEMPLATE VI. Virtual Hard Disk File Naming This naming standard applies to fixed and dynamic Virtual Hard Disk files. Differencing disks will need to follow a different, not-yet-defined standard. VIRTUAL_MACHINE_NAME_[DistinguishingDetail]_COUNTER.vhd VIRTUAL_MACHINE_NAME is the name of the Virtual Machine or Virtual Machine Template with which this disk is associated DistinguishingDetail is optional and used to explain the purpose of the specific VHD, especially useful if there are a large number of VHDs for a particular Virtual Machine COUNTER is a number used to distinguish between multiple VHDs related to the same Virtual Machine or Template. KDEDATAN1_1.vhd KDESQLDBRD1_Backups_1.vhd Version /3/08 Page 4

5 Microsoft_Windows_Server_Std_2008_RC1_NoSysPrep_TEMPLATE_1.vhd Microsoft_Windows_Pro_XP_SP2_wOutlook_SysPrep_TEMPLATE_1.vhd Virtualization Host Drive Mapping VII. This standard covers the allocation of drive letters for different purposes on host systems. Note: this standard may change in a future project to better support clustering. C: Host OS system & boot drive (contains \windows, etc) D: Host system CD/DVD E: Any other host system local drive F: Cluster Quorum (if applicable) G: Reserved for standard mapping to \\kdedatan1\<division directory> H: Reserved for standard mapping to \\kdedatan1\<office directory> I: Reserved for standard mapping to \\kdedatan1\kde J: Available if needed sometimes used for mapping to kdedatan1 Division Directory K: Available if needed sometimes used for mapping to kdedatan1 Division Directory L: Reserved for standard mapping to \\kdedatan1\software M: Virtual Machine files root drive N: Unused O: Unused P: Unused Q: Unused R: Unused S: Reserved for standard mapping to \\kdedatan1\oet-software T: Unused U: Unused V: Unused W: Unused X: Reserved for Ad-hoc/custom needs Y: Reserved for Ad-hoc/custom needs Z: Reserved for Ad-hoc/custom needs Drives described as reserved for standard mapping do NOT need to be mapped to the respective network resources on a regular basis but should not be used for anything else. Reserved for AD-Hoc drives are generally intended for temporary use. Virtualization Host Directory Structure VIII. This standard covers the directory structure used on the M drive of virtual machine hosts. Only directories are listed, not files. Version /3/08 Page 5

6 M: VM_Name (contains all VM-specific files VHDs here) Snapshots (Snapshot config files and VM-specific subdirs) GUID (VM-specific snapshot state files) VM_GUID (VM-specific snapshot disk state files) Virtual Machines (VM config file and state files) VM_GUID (VM-specific state files) Note: To follow this standard, when creating a VM, it is important to override the default Virtual Machine directory and set it to M:\. This can and should be done whether the VM_NAME directory already exists or not. Note: the GUID directory within Snapshots has its own GUID-based name, distinct from any VM-specific GUIDs, and itself contains VM-specific files that have VM-GUID-based names. Example (with files): M: \KDESQLDBRD2_VM KDESQLDBRD2_VM_FI_1.vhd KDESQLDBRD2_VM_DY_1.vhd \Snapshots \94B DA2-BEEB-C49B14072D0A 6DC5B5F6-98C0-4E39-A7A4-D8AC2B4389A2.bin 6DC5B5F6-98C0-4E39-A7A4-D8AC2B4389A2.vsv \6DC5B5F6-98C0-4E39-A7A4-D8AC2B4389A2 KDESQLDBRD2_VM_Q1R679A-ASTF-934A-1A4DFG6GE3QXZ.avhd 94B DA2-BEEB-C49B14072D0A.XML \Virtual Machines 6DC5B5F6-98C0-4E39-A7A4-D8AC2B4389A2.xml \6DC5B5F6-98C0-4E39-A7A4-D8AC2B4389A2 6DC5B5F6-98C0-4E39-A7A4-D8AC2B4389A2.bin 6DC5B5F6-98C0-4E39-A7A4-D8AC2B4389A2.vsv IX. Network Connection Configuration This standard describes how host system network connections should be configured. One network connection should be used for host access and management only. The Microsoft Virtual Network Switch Protocol must be unchecked (disabled) for this network connection. The remaining network connections should be used for guest network access only. All clients, protocols, etc should be unchecked (disabled) for this connection except the Microsoft Virtual Network Switch Protocol. Do NOT attempt to use NIC teaming. Version /3/08 Page 6

7 Note: See also the Virtualization Host Network Connections naming standard elsewhere in this document. X. Virtual Machine Hard Disk Types This standard describes what types of hard disks should be used for virtual machines. For guests that require consistent performance and high reliability typically Production systems virtual machine disks should be configured as either fixed-size virtual disks or pass-through physical hard disks. For guests that do not require best available performance, virtual machine disks should be configured as dynamic virtual disks. Avoid the use of differencing virtual hard disks. Create only one logical (Guest OS) volume on each virtual disk. Acronyms/Abbreviations: VM Virtual Machine References: Quality Records Title Location Kept Duration Kept Disposal Method Version /3/08 Page 7

In addition to their professional experience, students who attend this training should have technical knowledge in the following areas.

In addition to their professional experience, students who attend this training should have technical knowledge in the following areas. 6422A - Implementing and Managing Windows Server 2008 Hyper-V Course Number: 6422A Course Length: 3 Days Course Overview This three-day instructor-led course teaches students how to implement and manage