Install Worker on a Windows Image

This procedure may differ based on your cloud and your Windows version. This procedure provides a point of reference to install the WINDOWS_WORKER_OS_VERSION image.

Cloud Nuances

  •  vCD Installation Nuances
    1. Install CliQr Tools on the application VM.
    2. Stop the VM.
    3. Edit the settings for this VM and be sure to remove the NIC(s).
    4. Save the VM as a template into the vCD catalog of your choice.
  •  VMware Installation Nuances

    To use VMware VMs, you should have already installed VMware tools on the Linux machine.

Installation Process

To install CloudCenter Tools on a Windows image, follow this procedure:

  1. Contact CloudCenter Support to obtain the installer package (cliqr_installer.exe).

  2. Launch a base Windows image from the Cloud Provider Console. The following image is an example for OpenStack.

  3. Configure and save the User Account Control Level to Never Notify.
  4. CloudCenter requires Powershell 4.0. Verify that you are running this version of Powershell:
    PS C:\> $PSVersionTable.PSVersion

    Major Minor Build Revision 
    -----
     ----- ----- -------- 
    4
      0  -1  -1
  5. In the Powershell command line window, issue the command to bypass the Powershell ExecutionPolicy.
    Set-ExecutionPolicy -ExecutionPolicy Bypass
     

  6. Verify that the C:\PROGRA~1 path is resolvable to C:\Program Files.
    dir "C:\PROGRA~1"

    Otherwise, you must create the corresponding link:
    mklink /J "C:\PROGRA~1" "C:\Program Files"

  7. Download CloudCenter Tools as directed by CloudCenter Support.

  8. Go to the command prompt window and run the downloaded file:
    C:\<path to the file>\cliqr_installer.exe /CLOUDTYPE=openstack (or other cloud) /CLOUDREGION=default
    (The other cloud options are: amazon, azure, azurepack, google, openstack, opsource, softlayer, vcd, vmware, cisco)
  9. Run the Installer. You may add the IIS installation (depends on your deployment).

     Additional steps if using Windows 2016 Image on AWS
     Additional steps if using a Windows Azure Image
    • The following extra steps are required if configuring a Windows 2012 R2 application VM image in Azure.

       Windows 2012 R2 worker image in Azure
      1. Open Server Manager and start/open the Add Roles and Features Wizard.

      2. Click Next at the Before you begin pane.

      3. Select Role-based or feature-based installation on the Installation type pane and click Next .

      4. Select the Select a server from the server pool option in the Server Selection pane.

      5. In the Server Roles pane, select Web Server (IIS), and add all roles under Application Development.

      6. Click Next to proceed to the Features pane.

      7. In the Internet Information Services pane, expand Web Management Tools, and select IIS Management Console.

      8. Select Add Features and select:
        1. .NET Framework 3.5 Features, add .NET Framework 3.5
        2. .NET Framework 4.5 Features, add ASP.NET 4.5
    • Remove the installer.exe file.

    • Go to Control Panel > System and Security > System > Allow Remote Access. Uncheck the check box to Allow connections only from computers running Remote Desktop with Network Level Authentication. This action allows you to RDP into the VM from the CloudCenter UI.
    • In the file explorer go to C:\Windows\System32\Sysprep. Double click on sysprep. Make sure you choose the options displayed in the image below. Once sysprep is done, your RDP session will terminate

       

    • Go to the Azure Management UI and shutdown the application VM image.

  10. Create a snapshot of the image from your cloud console.
  11. After creating the snapshot, include the Image ID in the CloudCenter logical image (CCM UI > Admin > Images > Manage Cloud Mapping > Edit Mapping). See Cloud Mapping for Images for additional context).

    You have now mapped your Windows image to the cloud.

Post-Installation Verification

After installing the agent, verify the following information:

  • If the CliQr Startup Services are set to Automatic:

  • If the Jetty Service is up and running:

If this information remains unverified, be aware that the agent may not be successfully installed.


Back to: Worker (Conditional)

© 2017-2019 Cisco Systems, Inc. All rights reserved