mountainss Cloud and Datacenter Management Blog

Microsoft SystemCenter blogsite about virtualization on-premises and Cloud

Add Microsoft Library Server in SCVMM2012 Services

Leave a comment


This topic is about adding an other library server in the SCVMM2012 admin console and use deploying services.

Checklist: Library Preparation for Deploying Services

Task Description
1 Update the InstallSAV.cmd script in the Application Frameworks resources that are added to the VMM default library share during setup.

ImportantImportant
If you are using a highly available VMM 2012 management server, you must first add the Application Frameworks resources to the VMM library. For more information, see How to Share Application Resources When Using a Highly Available VMM Server.
2 Add your application files to the library.
3 Download a Microsoft Windows Server 2008 R2 Evaluation VHD to a library share, and install the needed updates.

The following procedure explains how to update the InstallSAV.cmd script, which is distributed with VMM 2012, to fix the installation order for Microsoft Web Deploy and the Server App-V agent.

noteNote
This procedure is only needed if the Web Deployment Tool is installed with Server App-V -(that is, when the \w parameter is used with the InstalSAV.cmd).

To update the InstallSAV.cmd script

  1. Locate the InstallSAV.cmd script in Windows Explorer.

    The file is stored in the ApplicationFrameworks folder, which is added to the default library share when a stand-alone VMM 2012 management server is installed. The default share name is MSSCVMMLibrary. The default physical location for the share is the following local path:

    C:\ProgramData\Virtual Machine Manager Library Files\ApplicationFrameworks

    noteNote
    The ProgramData folder is hidden by default. To display the ProgramData folder, in Windows Explorer, on the Tools menu, click Folder options. Then, on the View tab, click Show hidden files, folders, and drives.

    In the Application Frameworks resources, x64 and x86 versions of the Server App-V resources are stored in separate folders. For US English installations of VMM 2012, the folders have the following names, where “en-US” identifies the language of the VMM 2012 installation:

    SAV_x64_en-US_4.7.11.11.1127.cr

    SAV_x86_en-US_4.7.11.11.1127.cr

    Update both copies of the script.

  2. Open InstallSAV.cmd in Notepad or another editor.
  3. In the script, move installation of Web Deploy ahead of installation of the SAV agent by modifying the following .cmd section:

    Description Code
    Current code
    echo Installing SAV agent...
    start /wait agentsetup.exe /q "LOG_LEVEL=voicewarmupx!"
    if errorlevel 1 (
    echo "SAV agent installation failed. See log(s) at %%temp%% for more details."
    goto EOF
    )
    echo SAV agent installed.
    
    if defined _InstallWebDeploy (
    echo Installing WebDeploy...
    start /wait %windir%\system32\msiexec.exe /qn /i webdeploy.msi /l %temp%\WebDeploy.log
    if errorlevel 1 (
    echo "WebDeploy installation failed. See log at %%temp%%\WebDeploy.log for more details."
    goto EOF
    )
    echo WebDeploy installed.
    )
    Replacement code
    if defined _InstallWebDeploy (
    echo Installing WebDeploy...
    start /wait %windir%\system32\msiexec.exe /qn /i webdeploy.msi /l %temp%\WebDeploy.log
    if errorlevel 1 (
    echo "WebDeploy installation failed. See log at %%temp%%\WebDeploy.log for more details."
    goto EOF
    )
    echo WebDeploy installed.
    )
    
    echo Installing SAV agent...
    start /wait agentsetup.exe /q "LOG_LEVEL=voicewarmupx!"
    if errorlevel 1 (
    echo "SAV agent installation failed. See log(s) at %%temp%% for more details."
    goto EOF
    )
    echo SAV agent installed.
  4. Repeat the previous step to update the other version (x86 or x84) of SAVInstall.cmd.

Next, add the application packages that you will use during service deployment to the library. Maintain a folder that holds all releases of the application, and add a subfolder for each application release.

In the example scenario, the application folder is created in the default library share, which makes the application files available to administrators. You can add the application files to any library share. If the application will be deployed to a private cloud, see How to Configure the Library to Support Application Deployment in a Private Cloud in VMM 2012 for guidance on how to make the application files available to self-service users.

While you are configuring library paths, you will create a folder to store the XML files for exported virtual machine templates and service templates.

Enter here the right credentials

Advertisements

Author: James van den Berg

I'm Microsoft Architect and ICT Specialist and Microsoft MVP System Center Cloud and Datacenter Management

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s