Configuring the VMM Library
Updated: May 13, 2016
Applies To: System Center 2012 SP1 - Virtual Machine Manager, System Center 2012 R2 Virtual Machine Manager, System Center 2012 - Virtual Machine Manager
The procedures in this section describe how to perform basic configuration of the library in Virtual Machine Manager (VMM). The VMM library is a catalog of resources that provides access to file-based resources such as virtual hard disks, virtual floppy disks, ISO images, scripts, driver files and application packages that are stored on library servers, and to non file-based resources such as virtual machine and service templates and profiles that reside in the VMM database.
The VMM library can store the following types of resources:
File-based resources. File-based resources include virtual hard disks, virtual floppy disks, ISO images, scripts, driver files and application packages. To be used in VMM, a file must be added to the library. Application packages are a type of resource that is used for service creation. These application packages include SQL Server data-tier applications, Web Deploy packages, and Server App-V packages. You can also store driver files that are used during the deployment of an operating system when you use VMM to convert a bare-metal computer to a managed Hyper-V host.
You can also add custom resources to the library. Custom resources enable you to store resources in the library that would otherwise not be indexed and show up as available resources by the library server. If a user creates a folder with a .CR extension, and then saves the contents to a library share, the folder contents will be available to all users who can access the share. VMM will discover and import the folder into the library as a custom resource. Examples of what you may want to store as a custom resource are pre- and post-execution scripts that you want to use for service deployment, or a custom installation package.
A library server can discover only those files that are associated with a version of an operating system that is equal or earlier than the version of the operating system that the library server is running. For example, a library server that is running Windows Server 2008 R2 will not discover .vhdx files because they are associated with Windows Server 2012. The following table lists the file types that are automatically indexed and added as physical library resources during library refreshes in VMM.
Library Resource File Name Extension Virtual hard disks .vhd (Hyper-V and Citrix XenServer), .vhdx (Hyper-V), .vmdk (VMware) ISO image files .iso PowerShell scripts .ps1 SQL Server scripts .sql Web Deploy (MSDeploy) packages Note: These appear in the library as the “Web Application Package” type. .zip SQL Server data-tier applications (DACs) .dacpac Server App-V packages Note: These appear in the library as the “Virtual Application Package” type. .osd Driver files .inf Important: If you add driver files, we strongly recommend that you create a separate folder for each driver package, and that you do not mix resources in the driver folders. If you include other library resources such as .iso images, .vhd files or scripts with an .inf file name extension in the same folder, the library will not discover those resources. Also, realize that when you delete an .inf driver package from the library, VMM deletes the entire folder where the driver .inf file resides. For more information, see How to Add Driver Files to the VMM Library. Answer files .inf, .xml Custom resources Folders with .CR extension Virtual floppy disks .vfd (Hyper-V), .flp (VMware)
Virtual hard disks, ISO images, and virtual floppy disks that are attached to a stored virtual machine, and the configuration files for stored virtual machines, are indexed in VMM but are not displayed as physical resources. The virtual machine configuration files are created by the virtualization software but are not used by VMM. VMM stores a stored virtual machine’s configuration in the VMM database. Virtual machine configuration files include .vmc, .xml, and .vmx (VMware) files.
Templates and profiles. Templates and profiles are used to standardize the creation of virtual machines and services. These configurations are stored in the VMM database but are not represented by physical configuration files. There are several new types of templates and profiles in VMM, most of which are used for service creation. There are also host profiles (or in System Center 2012 R2, physical computer profiles), used for deploying a Hyper-V host from a bare-metal computer. In addition, there are capability profiles, used to specify the capabilities of virtual machines on each type of supported hypervisor when virtual machines are deployed to a private cloud.
The VMM library recognizes the .vmtx extension for VMware templates. If you import a VMware template, the template appears under Templates, in the VM Templates node.
Equivalent objects. Equivalent objects are a user-defined grouping of library resources that are considered equivalent. For example, you may mark a Windows Server 2008 R2-based virtual disk that is located on a library share in Seattle and a Windows Server 2008 R2-based virtual disk that is located on a library share in New York as equivalent. In a template or profile, when you point to a specific virtual disk on a specific library share, VMM can substitute any equivalent object during virtual machine or service creation. By using equivalent objects, you can author templates or profiles that do not depend on particular physical resources. Therefore, you can service resources without affecting the availability of the template or profile.
For virtual machine and service deployment, VMM supports only the use of virtual disks, .iso images and custom resources as equivalent objects.
The VMM placement process determines which resource should be used when a resource that has equivalent objects is defined in a profile or template. Placement considers several factors, such as the association between library servers and host groups to help determine which resource to use. This helps to improve performance and optimize network bandwidth usage. Therefore, we recommend that you use resources that have equivalent objects when you create profiles such as application and host profiles, and when you create virtual machine and service templates.
The resources that you mark as equivalent can be files that are replicated by a replication technology or files that you manually copy to each location.
Cloud libraries. Private cloud libraries consist of read-only library shares that are assigned to a private cloud and a Stored Virtual Machines and Services node where self-service users who have appropriate permissions can store virtual machines and services. An administrator or a delegated administrator whose management scope includes the library servers can add resources to the read-only library shares that they want to make available to users of the private cloud.
During private cloud creation, VMM adds a private cloud library to the Cloud Libraries node, with a name that matches the private cloud name. If the administrator specifies read-only library shares and a path to store virtual machines, the library shares and the Stored Virtual Machines and Services nodes appear under the private cloud library. For information about how to create a private cloud, see Creating a Private Cloud in VMM Overview.
Self-service user content. This node enables self-service users to upload their own resources such as authored templates, virtual disks, ISO image files, application files, scripts and other building blocks to the VMM library. They can use these resources when they author templates. Because this node enables self-service users to write to a common file path that other members of their user role have access to, self-service users with appropriate permissions can share resources with other users in the same or a different self-service user role.
To share with users in a different self-service user role, the target self-service user role must have appropriate permissions. For information about how to configure permissions for a self-service user role, see How to Create a Self-Service User Role in VMM.
Stored virtual machines and services. Users can choose to store virtual machines that are not in use to the Stored Virtual Machines and Services node. This node is available when you expand Library Servers, and then expand the library server.
Be aware that when a self-service user stores a virtual machine or service to the library, the resource is stored in the Stored Virtual Machines and Services node in the private cloud library.
Orphaned resources. When you remove a library share from VMM management, and there are templates that reference resources that were located on the library share, a representation of the library resource appears in the Orphaned Resources node. You can click an orphaned resource to view the templates that reference the orphaned resource. You can then modify the template to reference an existing resource in the VMM library.
Update catalog and baselines. If you manage updates through VMM for the VMM management server and other computers that are under VMM management, Windows Server Update Services (WSUS) update baselines are stored in the VMM library. Updates are covered in more detail in Managing Fabric Updates in VMM.
Operating System Requirements
For information about the supported operating systems for the library server role, see the following topics:
For System Center 2012 – Virtual Machine Manager or for System Center 2012 SP1 see System Requirements: VMM Library Server in System Center 2012 and in System Center 2012 SP1.
For System Center 2012 R2 Virtual Machine Manager see: Preparing your environment for System Center 2012 R2 Virtual Machine Manager.
To make the library server highly available, you can create highly available file shares on a clustered file server that meets the operating system requirements that are outlined in the ‘Operating System Requirements’ section above. For more information, see Create a Shared Folder in a Clustered File Server.
Do not create highly available file shares for the VMM library on the same cluster as a highly available VMM management server installation. VMM does not support this configuration.
Example Scenario Overview
The example scenarios in this section assume that you have a VMM management server installed and a library share configured as part of VMM installation. The scenarios also use a server in a second site that you add as a library server. To demonstrate the concept of equivalent objects, it is best to use multiple library servers and library shares. The following table summarizes the example names that are used in this section.
The example resource names and configuration are used to help demonstrate the concepts. You can adapt them to your test environment.
|VMM management server||VMMServer01.contoso.com|
|Library share in Seattle (added during VMM management server installation)||VMMServer01\SEALibrary|
|Library server and share in New York||NYLibrary01\NYLibrary|
In This Section
Use the following procedures to perform basic configuration of the VMM library.
|How to Add a VMM Library Server or VMM Library Share||Describes how to add a new library server or library share.|
|How to Associate a VMM Library Server with a Host Group||Describes how to associate a library server with a host group. This association helps VMM to determine which resource to use when there is a set of equivalent objects.|
|How to Add File-Based Resources to the VMM Library||Describes how to add file-based resources to the library.|
|How to Create or Modify Equivalent Objects in the VMM Library||Describes how to mark file-based objects as equivalent.|
|How to View and Remove Orphaned Resources in VMM||Describes how to view orphaned resources, and how to resolve any issues with templates that reference the orphaned resource so that you can remove the orphaned resource.|