Share via


about_VMM_2012_Library

Updated: January 15, 2013

Applies To: System Center 2012 - Virtual Machine Manager, System Center 2012 SP1 - Virtual Machine Manager

about_VMM_2012_Library

TOPIC
    about_VMM_2012_Library

SHORT DESCRIPTION
    Provides an overview of new library features in Virtual Machine Manager 
    (VMM) for System Center 2012 and the VMM command-line interface.

LONG DESCRIPTION
    With the VMM command shell, you can configure and manage library servers 
    and library resources (for example, virtual hard disks, templates, and 
    profiles) as well as configure and manage update baselines.

  Library Servers

      By default, the VMM management server is also a library server. However,
      you can add more library servers, as well as update and remove existing 
      library servers, by using the following cmdlets in the VMM command shell:

      - Add-SCLibraryServer
      - Get-SCLibraryServer
      - Set-SCLibraryServer
      - Remove-SCLibraryServer

      After you have added your library servers, you can use the VMM library 
      as a central location to store the following resources:

      - Templates. As with previous versions of VMM, you can store virtual
        machine templates in the library. With VMM for System Center 2012,
        you can also store Service Templates and Service Deployment 
        Configurations in the VMM library.

      - Profiles. You can store the following types of profiles in the VMM 
        library:

          - Application Profiles. An application profile provides instructions
            for installing Microsoft Server App-V, Microsoft Web Deploy, and 
            Microsoft SQL Server data-tier applications (DACs), and for running
            scripts when deploying a virtual machine as part of a service. For 
            more information, type: "Get-Help New-SCApplicationProfile".

          - Capability Profiles. Capability profiles define which resources
            (for example, number of processors or maximum memory) are available
            to a virtual machine that is deployed to a private cloud. For more 
            information, type: "Get-Help New-SCCapabilityProfile".

          - Guest OS Profiles. A guest operating system profile contains common
            operating system settings (for example, computer name, domain name,
            product key, and time zone), that you can apply to a virtual 
            machine template. For more information, type: "Get-Help 
            New-SCGuestOSProfile."

          - Hardware Profiles. Hardware profiles contain hardware
            specifications (for example, memory, network adapters, and DVD 
            drive) that you can apply to a new virtual machine or to a virtual
            machine template. For more information, type: "Get-Help 
            New-SCHardwareProfile".

          - Host Profiles. Host profiles contain the hardware and operating
            system configuration settings used to convert a bare-metal computer
            to a Hyper-V host. For more information, type: 
            "Get-Help New-SCVMHostProfile".

          - SQL Server Profiles. A SQL Server profile provides instructions for
            customizing a SQL Server instance for a SQL Server DAC when 
            deploying a virtual machine as part of a service. For more 
            information, type: "Get-Help New-SCSQLProfile".

      - 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. New
        in VMM for System Center 2012, you can store application packages that
        are 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.
 
      - Custom resources. 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. For example, you may want to store a custom installation 
        package as a custom resource. To add a custom resource to the library,
        create a folder with a .CR extension, place content in the folder, and
        then use the VMM console to drop the folder on a VMM library share. VMM
        discovers and imports the folder into the library as a custom resource.
        After you have added custom resources to the library, you can manage
        them by using the Get-SCCustomResource, Set-SCCustomResource, and
        Remove-SCCustomResource cmdlets.

  Library Shares

      VMM only indexes files stored on designated library shares. When you add 
      a library share, the resources on the share are immediately indexed in
      VMM. Thereafter, the files on the library share will be indexed during 
      each periodic library refresh, which is, by default, once each hour. For 
      more information, type: "Get-Help Add-SCLibraryShare".

  Update Catalog and Baselines

      VMM for System Center 2012, adds the capability to add an update 
      server. After you have added a Windows Server Update Services (WSUS)
      server as an update server to your VMM environment, you can create an
      update baseline and view the updates that are available on the WSUS 
      server. For more information, type: "Get-Help Add-SCUpdateServer" and 
      "Get-Help New-sCBaseline".

  Managing Scripts stored in the Library

      Administrators can view, edit, and run scripts that are stored in the VMM
      library by using the Get-SCScript cmdlet. To remove a script from the 
      library, use the Remove-SCScript cmdlet.

SEE ALSO
    about_VMM_2012
    about_VMM_2012_Cmdlet_and_Parameter_Name_Mapping
    about_VMM_2012_Cmdlet_Backward_Compatibility
    Add-SCLibraryServer
    Get-SCLibraryServer
    Set-SCLibraryServer
    Remove-SCLibraryServer
    New-SCApplicationProfile
    New-SCGuestOSProfile
    New-SCVMHostProfile
    New-SCSQLProfile
    Get-SCCustomResource
    Set-SCCustomResource
    Remove-SCCustomResource
    Add-SCLibraryShare
    Add-SCUpdateServer
    New-sCBaseline
    Get-SCScript
    Remove-SCScript