Install Worker on a Windows Image
Use the Workload Manager installer executable cliqr_installer.exe to create Workload Manager-enabled Windows images on different clouds and regions.
The Windows worker installer is compatible with these releases of Windows Server:
- Windown 2008
- Windows 2012
- Windows 2016
- vCenter Installation Nuances
You must first install VMware tools on the VM.
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.
To install the worker on a Windows image, follow this procedure:
Download the artifacts.zip file from software.cisco.com and unzip it to obtain the installer package (cliqr_installer.exe).
You should only run the cliqr_installer.exe package once on a clean image. Do not attempt to run the installer twice on the same image.
Launch a base Windows image from the Cloud Provider Console. The following image is an example for OpenStack.
Workload Manager requires PowerShell 4.0 or above on Windows 2012 R2 or Windows 2016. Verify that you are running the correct version of PowerShell:
Verify that the
C:\PROGRA~1path is resolvable to
Otherwise, you must create the corresponding link:
Download CloudCenter Tools as directed by CloudCenter Support.
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, azurerm, google, openstack, vmware)
Run the Installer. You may optionally 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
Recently, AWS has changed its metadata script execution behavior, and custom images will not work out-of-box
To execute the scripts while launching the image, the following extra step is required if configuring a Windows 2016 application VM image on AWS.
Before creating this image run the following scripts PowerShell.
The following extra steps are required if configuring Windows 2012 R2 or Windows 2016 application VM image in AzureRM.Windows 2012 R2 worker image in Azure
Open Server Manager and start/open the Add Roles and Features Wizard.
Click Next at the Before you begin pane.
Select Role-based or feature-based installation on the Installation type pane and click Next .
Select the Select a server from the server pool option in the Server Selection pane.
In the Server Roles pane, select Web Server (IIS), and add all roles under Application Development.
Click Next to proceed to the Features pane.
In the Internet Information Services pane, expand Web Management Tools, and select IIS Management Console.
- Select Add Features and select:
.NET Framework 3.5 Features, add .NET Framework 3.5
.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 Suite 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.
After installing the agent, verify the following post-installation information.
If this information remains unverified, be aware that the agent may not be successfully installed.
Ensure that the CliQr Startup Service starts up using the Automatic (Delayed Start) type – if not, set it to Automatic(Delayed Start)
Capture an image of the Worker VM.
After creating the image, use the Image ID to map the corresponding Workload Manager logical image to this physical image (Workload Manager UI > Admin > Images > Manage Cloud Mapping > Add/Edit Mapping). See Images Page for additional context).
- No labels