interworks.cloud Platform - Hyper-V Service Manager

Table of Contents

Document revision history5
About this guide 6
Introduction6
Document conventions6
Support and feedback7
CHAPTER 1 8
Overview of Cloud OSS Microsoft Hyper-V Service Manager 8
Introduction8Overview of Microsoft Hyper-V 2012 R28
Overview of Cloud OSS9
CHAPTER 2 10
Preparing for the installation 10
Introduction10
Deploying VMware vSphere Infrastructure10
Preparing the network11
Preparing the VM templates (Guest OS Master Images)11
CHAPTER 3 12
Installing Cloud OSS VMware vSphere Service Manager 12
Introduction12
Installing Cloud OSS VMware vSphere Service Managers12
CHAPTER 4 14
Configuring Cloud OSS Microsoft Hyper-V Service Manager 14
Introduction14
Configuring Microsoft Hyper-V module15
Configuring Network Settings17
Creating Virtual Server18
Creating Hosting Plan19
APPENDIX A 20
APPENDIX B 38
This page is intentionally left blank

Document revision history

There have been no changes to this document since its initial publication. For information about new features in this release, see the latest release notes at: *http://www.interworkscloud.com/release.en.aspx*

About this guide

Introduction

This guide provides instructions for installing and configuring interworks.cloud OSS Microsoft Hyper-V Service Manager 2.x. The following versions of Microsoft Hyper-V are currently supported in this release:

Microsoft Hyper-V 2012 R2

Note:

This guide is updated as new information becomes available. Before you begin, be sure to check the OSS documentation section at the interworks.cloud Platform support site, http://www.interworkscloud.com/downloads , to make sure you have the latest version of the guide. The publication date on the title page indicates the version; changes, if any, are recorded in the document revision history chapter of this guide.

Document conventions

Throughout this guide, specific fonts and styles are used to identify user input, computer code, and user interface elements. The following table lists conventions used in this guide.
Table 1. Document conventions

Convention	Usage
Bold text, Arial font	Used for information you type as well as path names, file names, menus, and command keys.
Italic text, Arial font	Used for column names, field names, window names.
Bold, italic text enclosed in angle brackets	Used for variables you replace with the appropriate information.
Normal text, Courier New	Used for system messages, screen text, and code examples.

Support and feedback

To receive support for the Cloud OSS platform use the following link:
*http://www.interworkscloud.com/downloads* to access product downloads and online help and documentation

CHAPTER 1

Overview of Cloud OSS Microsoft Hyper-V Service Manager

Introduction

This chapter provides an overview of interworks.cloud OSS platform and the Microsoft Hyper-V Service Manager.

Overview of Microsoft Hyper-V 2012 R2

Microsoft Hyper-V is the industry-leading virtualization platform for building cloud infrastructures. Realize cost savings and operational efficiencies by using the platform you know—with Hyper-V built into Windows Server. Take advantage of a unified set of integrated management tools for your physical, virtual, and cloud environments with a single console view. It enables IT to meet SLAs (service-level agreements) for the most demanding business critical applications, at the lowest TCO (total cost of ownership).
Microsoft Hyper-V Hypervisor Architecture provides a robust, production-proven, high-performance virtualization layer. It enables multiple virtual machines to share hardware resources with performance that can match (and in some cases exceed) native throughput.
VMware vSphere Virtual Symmetric Multiprocessing enables the use of ultra-powerful virtual machines that possess up to 64 virtual CPUs.
VMware vSphere Virtual Machine File System (VMFS) allows virtual machines to access shared storage devices (Fiber Channel, iSCSI, etc.) and is a key enabling technology for other vSphere components such as VMware vSphere Storage vMotion®.
VMware vSphere Storage APIs provide integration with supported third-party data protection, multi-pathing and disk array solutions.

Overview of Cloud OSS

The interworks.cloud OSS platform is a centralized software application that simplifies the day-to-day burden of activating, configuring and managing a service provider's unified communications and collaboration infrastructure. interworks.cloud OSS enables service providers to centrally create, control, and deliver hosted IP and application services. It addresses critical operational challenges for provisioning, monitoring, metering, self-management, authentication and further integration into other applications in the service provider's OSS/BSS systems.
interworks.cloud OSS has the following components:

Cloud OSS Provisioning Portal

Server that host the web-based control panels. Service providers can have multiple Provisioning Portal servers to balance loads and provisioning requests. Provisioning Portal servers or control panels provide easy access to tasks. These control panels enable service providers, resellers, organization administrators, and users to manage their accounts, resources, and other system settings. Provisioning Portal servers are typically placed in the Front End (internet facing) network.

Cloud OSS Orchestration Server

The Cloud OSS Orchestration Server coordinates the provisioning of services to customers. Service Providers can have multiple Orchestration servers to balance loads and provisioning requests. The Orchestration Server role comprises the business logic of Cloud OSS. Orchestration servers are typically placed in the Back End network.

Cloud OSS Service Managers

The Cloud OSS Service Manager can be seen as a provisioning helper server. Service Managers expose an extensive set of web services APIs that perform the actual provisioning actions as dictated by the Orchestration Servers. Service Managers are mainly installed on servers that host specific applications or services (e.g.: IIS, SQL Server), but they can also be installed on servers that have special management tools to manage and control other applications or services (e.g.: Exchange servers, Lync servers, etc.). Cloud OSS Service Managers are typically placed in the Back End network.

CHAPTER 2

Preparing for the installation

Introduction

This chapter explains how to prepare a hosting/cloud environment for the Cloud OSS VMware vSphere Service Manager installation.

Deploying VMware vSphere Infrastructure

This guide assumes that you have deployed and configured vSphere in high availability mode. The Service Manager can only interact with the vSphere infrastructure through vCenter Server, therefore vCenter Server must be installed and properly configured to manage the entire infrastructure. At the very least two servers running ESXi hypervisors are required in order to form a vSphere cluster.
The VMware vSphere Service Manager requires that the following configuration settings are applied:

A cluster of two or more ESXi Hosts is created and configured appropriately
A Datastore Cluster is configured with one or more datastores
A Datacenter object container is defined. The Cluster and Datastore Cluster must be linked under this Datacenter container
Network and storage configuration of each ESXi Host is set up correctly

Important:

The current release of Microsoft Hyper-V Service Manager supports only the Standard Virtual Internet. Make sure that Standard Virtual Internet is properly setup for the VM networks on each Hyper-V Host.

The vSphere administrator should also ensure that various other settings such as Time Configuration, DNS and Routing, Power Management, etc. are properly configured.

Note:

Further configuration of the hosts and cluster regarding settings such as HA, FT, Monitoring, EVC, DRS, SDRS, etc. is out of scope of this guide.

Preparing the Network

The current release of VMware vSphere Service Manager supports provisioning of VMs in standard VLAN based isolated networks. Each tenant (customer) is automatically assigned a VLAN and all VMs provisioned under that tenant belong to that specific VLAN. The Service Manager automatically configures the Standard vSwitch in each ESXi Host with the appropriate port group settings for each tenant VM.
The Network Administrator must prepare for and supply the following information:

A list of VLANs that will be made available to the VMs
Important:
Further configuration may be required depending on the existing network infrastructure. This may include routers, firewalls, physical switches or other networking devices.
A list of IP Addresses/Ranges (IP address, Network Subnet mask, Default Gateway) that will be assigned to VMs during provisioning
Primary and Secondary DNS server IP addresses that the provisioned VMs will use

Preparing the VM templates (Guest OS Master Images)

The Service Manager requires the use of templates created in vCenter Server, in order for VM provisioning to function correctly. The vSphere administrator should prepare the required VM templates along with relevant Guest OS customization specification files. Further instructions on how to create the necessary customization specification files and specific guest OS images can be found in Appendix A of this guide.

Important:

Take a note of the names of the VM templates and the names of the customization specification files that you create in vCenter Server. You will use these names in a special configuration file later on, during installation of the Cloud OSS VMware vSphere Service Manager.

CHAPTER 3

Installing Cloud OSS VMware vSphere Service Manager

Introduction

This chapter explains how to install the Cloud OSS VMware vSphere Service Manager.

Installing Cloud OSS VMware vSphere Service Managers

To integrate VMware vSphere into the Cloud OSS platform you will need to install the Cloud OSS Service Managers components on one or more mediation servers You can install Interworks.cloud OSS Service Manager on more than one servers and make use of hardware or software load balancing to distribute load and maintain high availability. This server may also be referred as Mediation Server. in your environment. Installation of the components is performed by the Interworks.cloud Platform Installer. For more information about installing the interworks.cloud Platform Installer and the Service Managers please consult the Interworks.cloud OSS Installation Guide.
The mediation server should have the following minimum system specifications:
Mediation Server System Requirements

Server Role	Network Zone	Processors	Memory	Storage	Notes
Mediation Server	Back Net	2 CPU Cores 2GHz	4GB	60GB	Windows 2008 R2 Std.

Login to every mediation server and install the Cloud OSS Service Managers components as described in the Cloud OSS Installation Guide. Keep in mind the following network port requirements, in order to maintain successful communication between the various Cloud OSS components and the vSphere infrastructure.
Network Access Rules

Source	Destination	Protocol	Src. Port	Dest. Port	Notes
Mediation Server	vCenter Server	TCP	Any	80,443,902,903 8080,8443,9090 9443
Mediation Server	vCenter Server	UDP	Any	902
OSS Orchestrator Server	Mediation Server	TCP	Any	9003

After installation has completed successfully, you will need to manually edit the configuration file templatesConfiguration.xml (you can use notepad or any other common text editor). This file is located at the root of the installation directory of the Cloud OSS Service Manager and contains the VM templates that the Service Manager will use to provision VMs. In this configuration file you define the names of the VM templates and the customization specification files you created earlier in vCenter Server (See previous section Preparing the VM templates). Fig. 3.1 shows an example of the contents of the configuration file.

Fig. 3.1
According to the example above, the administrator has configured one VM template named Windows Server 2008 R2 Standard and one VM template named CentOS 6.4 (64-Bit). There are also two customization specification files. One is configured for Windows based guest OS and is named OSS Windows Customization, and the other is configured for Linux based guest OS and is named OSS Linux Customization.
Appendix A of this guide contains step by step instructions on how to create both VM templates and customization specification files in vCenter Server to support VM provisioning in Cloud OSS.

Note:

The vSphere administrator may have configured any number of VM templates and/or customization specification files. Only the ones defined in the templatesConfiguration.xml file will be available in Cloud OSS during provisioning of new VMs.

CHAPTER 4

Configuring Cloud OSS Microsoft Hyper-V Service Manager

Introduction

This section provides information about configuring the Cloud OSS VMware vSphere Service Manager. It is assumed that you have installed the Cloud OSS Service Managers components on all servers that require it, as described in the previous sections and you have verified connectivity to the Service Managers web sites. Before configuring each component, it is necessary to add each server to the Cloud OSS servers' collection. This is done by signing in to the Cloud OSS Provisioning Portal, navigating to Configuration ► Servers (Fig. 4.1) and clicking on Add Server (Fig. 4.2) button.
Fig. 4.1 Fig. 4.2
You have to enter a server name (you may choose any name that is meaningful and/or descriptive of the server role) as well as the URL and server password that correspond to each Service Manager installation. For more information about administering and configuring Cloud OSS platform you may consult the Cloud OSS Administrator Guide.

Configuring Microsoft Hyper-V module

Sign in to Cloud OSS Provisioning Portal and navigate to Configuration ► Servers. Click on the server where the Cloud OSS Microsoft Hyper-V Service Manager was previously installed and perform the following actions:

Under the Services section click Add next to HyperV 2012 (Fig. 4.3)
Optionally, change the Service Name label if required
Select HyperV 2012 as Service Provider
Click on the Add Service button

Fig. 4.3
On the service settings page (Fig. 4.5) perform the following actions:

Under the VMM Management Server Connection Options enter the IP address of the SCVMM Server and the user name and password of either the Administrator user or a user with administrative privileges configured in SCVMM Server. Click on the check button next to the IP address text box. If the connection settings are correct the button image will change from red stop sign to a green check mark
Under the Clusters section select the desired cluster that the Service Manager will manage
Under the External Network section select the Standard Virtual Internet that will be used for VM external network communication
Click on the Update button. Upon successful operation the following message will be displayed:

Hyper-V Custom Service has been provisioned successfully

Fig. 4.4

Configuring Network Settings

VLAN Pool configuration

Sign in to Cloud OSS Provisioning Portal and navigate to Configuration ► Virtual LANs. Click on Add Virtual LAN button and enter a meaningful name in the Description field; then enter the range of available VLANs and finally click on the Add button to save your VLAN selection (Fig. 4.5).

Fig. 4.5

You can repeat this process if you wish to insert additional VLAN ranges.

IP Address Pool configuration
Sign in to Cloud OSS Provisioning Portal and navigate to Configuration ► IP Addresses. Click on the Add IP Address button and enter the following information (Fig. 4.6):

Select VM External Network in the Pool: drop down list
Select the server previously configured in the Server: drop down list (See section Configuring Microsoft Hyper-V module)
Enter an appropriate IP address range
Optionally, set the NAT Address that will apply to the selected IP Address range
Enter the Subnet mask and the Default Gateway
Select the appropriate Vlan from the drop down list

Fig. 4.6

You can repeat this process if you wish to insert additional IP Address ranges.

Creating Virtual Server

Sign in to Cloud OSS Provisioning Portal and navigate to Configuration ► Virtual Servers. Click on Add Virtual Server button and enter a meaningful name in the Server Name: field; then click on Add Server button to save the new Virtual Server.

Note:

It is strongly recommended to use Virtual Servers and not Servers to assign to Hosting Plans. This greatly increases scalability and helps you avoid potential problems when you want to add services or extra resources to existing customers.

Click on Add Services button and select Microsoft Hyper-V service on the server previously configured.
Click on the Update button.

Creating Hosting Plan

Sign in to Cloud OSS Provisioning Portal and navigate to Account Home ► Hosting Plans ► Create Hosting Plan. Enter a meaningful plan name and an optional description and select as target server the Virtual Server you created earlier from the drop-down list. Under the Quotas section select the HyperV 2012 service. Adjust the quotas and values of the service to meet your plan needs and click on the Save button to save the new Hosting Plan (Fig. 4.7).
Fig. 4.7
You are now ready to create a new customer and assign a new Hosting Space to the customer based on the Hosting Plan you just created.

APPENDIX A

Deploying Guest OS Master Images (VM Templates)

Introduction

This section provides information that can help you create Windows and Linux based guest OS templates that will be used by Cloud OSS during VM provisioning. Instructions provided herein will assist in creating customizations specification files for Windows and Linux operating systems as well as optimized images ready for provisioning. To follow these instructions you will need administrative access to SCVMM Server and Console as well as adequate ISO images or CD/DVD discs containing the operating systems for the guest OS.
CentOS 6.5 and Oracle Linux 6.5
Creating the Virtual Machine
The first thing we need to do in order to deploy the template is to create a Virtual Machine and install the CentOS 6.5 or Oracle Linux 6.5 Operating System.
You can download the CentOS 6.5 ISO image from here. This link contains a number of mirrors that have the CentOS images. For this guide we will be using the CentOS-6.5-x86_64-bin-DVD1.ISO (not all mirrors contain this ISO so you may need to check a couple of mirrors)
You can download the Oracle Linux 6.5 ISO image from here. You will need to register or sign-in with your existing Oracle account in order to download the ISO.
Once you have downloaded the ISO image you can are ready to create the Virtual Machine:

Open Hyper-V Manager in one of your Hyper-V cluster nodes or the System Center Virtual Machine Manager (SCVMM) management console and click on "Create Virtual Machine"
Create the Virtual Machine with a "Legacy Network Adapter" (see Figure 1.1 and Figure 1.2) and click "Next" after attaching the CentOS or Oracle installation ISO to the DVD drive

Figure 1.1 – Removing Network Adapter Figure 2.2 – Adding Legacy Network Adapter

Start the Virtual Machine and connect to the console

Choose to "Install or upgrade an existing system"

Figure 3.3 – CentOS initial installation screen

Choose whether to test or not the install media and click "Next" in the screen that follows.

Figure 4.4 – Install media test dialogue box

Choose your preferred Language and Keyboard layout

Figure 5.5 – Preferred language Figure 6.6 – Preferred keyboard layout

Choose "Basic Storage Devices" and click on the "Yes, discard any data" button at the pop-up window.

Figure 7.7 – Installation devices Figure 8.8 – Storage Device Warning

Enter the FQDN (Fully Qualified Domain Name) you want to use for this Virtual Machine

Figure 9.9 – Virtual Machine Template FQDN

Click on the "Configure Network" button and Edit the "System eth0" network interface. Configure the IPv4 settings so that you can access the template at a later time.

Figure 10.9 – Network configuration Figure 11.10 – System etho network settings

Select the appropriate time zone and click "Next". In the next screen set a "Root" password.

Figure 12.11 – Time settings Figure 13.12 – Setting root password

In the next screen check "Use All Space" and click "Next". In the pop-up window click on "Write changes to disk".

Figure 14.13 – Partitioning Figure 15.14 – Write changes to disk

Choose installation type (Since this is going to be a server template, we choose the "Basic Server" option). Now the installation process will begin after we click "Next".

Figure 16.15 – Installation type Figure 17.16 – Starting installation process

When the installation process is over click on "Reboot".

Figure 18.17 Rebooting upon successful installation
Preparing the Virtual Machine for Template
After the Reboot process is completed successfully, shutdown the Virtual Machine by logging in as root with the password you chose during the installation and running the following command:

shutdown –h now

After the Virtual Machine is turned off, remove the "Legacy Network Adapter" and click "OK" after adding a "Standard Network Adapter".

Figure 19.18 Removing Legacy and adding a Standard Network Adapter

Turn the Virtual Machine on and login as root. By default CentOS and Oracle Linux do not enable the network adapter on startup. If you run the command "ifconfig" you will only find the loopback adapter listed.

Figure 20.19 Running ifconfig

Also by default the first adapter will be eth0. However, if we attempt to enable it by using the "ifconfig eth0 up" command we will receive the "no such device" error message as shown in the figure below:

Figure 21.20 Attempting to bring etho interface up
This is because eth0 is assigned to the legacy adapter we just removed. In order to fix this we need to clear the existing adapter rules, and update the configuration file for eth0.

First we are going to update the configuration file for eth0. To do this we run the following commands:

cd /etc/sysconfig/network-scripts/
nano ifcfg-eth0

We should receive a screen similar to the one below:

Figure 22.21 Updating config file for etho

From the config file remove the line that starts with HWADDR and set the value for BOOTPROTO=static. Hit Ctrl-X + Y + Enter to exit and save your changes

Now remove the network rules and reboot the Virtual Machine:
- rm /etc/udev/rules.d/70-persistent-net.rules –f
- shutdown –r now

After rebooting run the "ifconfig" command to verify network is set to eth0 and an IP address is configured.

Figure 23.22 Verifying eth0 proper state and configuration
You may also try to ping a public website in order to confirm Internet connectivity.
We can now continue with the required installation/configuration of the Virtual Machine in order to prepare it for template.

Hyper-V backup essentials have to be added in order for the Virtual Machine to support Live Backup. To do this run the following commands:

- curl –L –o backupessentials.tar.gz https://github.com/LIS/backupessentials/tarball/1.0
- tar –xvzf backupessentials.tar.gz
- cd LIS-backupessentials-f5f542e/hv/hv-rhel6.5/rpm/
- chmod +x install.sh
- ./install.sh
- Reboot

Install the key/value pair (KVP) infrastructure and the libvirt which is the API that HypervISOr's layer uses:
- yum install hypervkvpd
- yum install libvirt

Download the Hard disk extend scripts on your Workstation from here

Unrar the file and open the WinSCP or any other SCP client tool

Copy and overwrite the rc.local from the CloudWorks-Linux-ExtendScripts folder to the /etc/ director on the Linux Operating System

Grant executable permissions to the new rc.local file by using the following command:

- chmod +x /etc/rc.local

Copy the disk_extend_script1.sh and the disk_extend_script2.sh under the /etc/rc.d/init.d/ directory of the Linux Operating System and grant executable permissions to the scripts using the following commands:

- chmod +x /etc/rc.d/init.d/disk_extend_script1.sh
- chmod +x /etc/rc.d/init.d/disk_extend_script2.sh

Remove the wtmp reboot counter with the following command:

- rm –rf /var/log/wtmp

(Note: If you don't remove this log, there might be an issue with the Disk Extend feature)

Add the SCVMM Guest Agent. You can find the SCVMM Agent inside your SCVMM Server under the folder C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\agents\ . You have to find the scvmmguestagent.1.0.2.1014.x64.tar and the install.sh. Copy them on your Virtual Machine with the WinSCP client tool and install them by using the following commands:

- cd /the/directory/you/copy/the/agent/and/the/shell/script
- chmod +x install.sh
- ./install.sh scvmmguestagent.1.0.2.1014.x64.tar

The last step before creating the template is clearing network rules once more so that the new adapter from the Cloud OSS provisioning platform is added as eth0. To do this run the following command:

- rm /etc/udev/rules.d/70-persistent-net.rules –f

Shutdown the Virtual Machine by running the following command:

- shutdown –h now

Creating the Template

To create the template you will need to copy the Virtual Machine .vhdx file in the SCVMM "Library Share" folder

After the file copy is over refresh the "Library Share" folder so it can show it up on the SCVMM Console.

Figure 24.23 Refreshing the Library Share folder

Now you should be able to see the Virtual Hard Disk

Right click on the .vhdx file and navigate to Properties -> General -> Operating System. Choose "CentOS 6 (64 bit)" and "Microsoft Hyper-V" in the "Virtualization platform" drop down list.

You can now start the Template wizard by right clicking on the .vhdx file and clicking on "Create VM Template".

Figure 25.24 Refreshing the Library Share folder

In the "Identity" tab choose "VM Template name" and select "Generation 1" for Generation.

Figure 26.25 VM Template name and Generation

In the "Configure Hardware" tab select "Hyper-V" in "Cloud Capability Profiles". In "General" section choose minimum specs for the base image (you may specify 1CPU/1GB RAM and 10GB HD).

Figure 27.26 – Configuring Compatibility Figure 28.27 – Configuring Resources

In "Network Adapters" select "Connected to a VM network". In the "Advanced" section check "Make this virtual machine highly available" with your preferred priority.

Figure 29.28 – Configuring Network Adapters Figure 30.29 – Configuring High Availability

In the "Configure Operating System Settings" tab if the Operating System select the [Create new Linux operating system customization settings] on "Guest OS profile" and select "CentOS Linux 6 (64 bit)" in the dropdown menu (for Oracle Linux select "Oracle Linux 6 (64 bit)").

Figure 31.30 – Specify Operating system

At the "Application Configuration" and "SQL Server Configuration" click "Next".

View your "Summary" configuration settings and click "Create".

Windows Server 2008 R2, Windows Server 2012 and Windows Server 2012 R2
Creating the Virtual Machine
The first thing we need to do in order to deploy the template is to create a Virtual Machine and install the Windows 2008 R2, 2012 or 2012 R2 operating system. In our example we have used Windows 2008 R2

Open System Center Virtual Machine Manager (SCVMM) console and click on "Create Virtual Machine". Check "Create the new Virtual Machine with a blank Virtual hard Disk" and click "Next".

Figure 2.1 – Selecting Source

In the "Identity" section specify "Virtual machine name" and "Description". Leave the default "Generation 1" and click "Next".

Figure 2.2 – Identity

In the "Configure Hardware" section choose minimum specs for the base image (you may specify 1CPU/1GB RAM and 20GB HD). In the Virtual DVD Drive press "Existing ISO Image" and browse for the windows installation media. You will have to insert the installation ISO into your Library to be able to browse for it. In "Network Adapters" choose your VM Network or Virtual Switch. In the "Advanced" tab in the availability option choose "Make this virtual machine High Available" given that you are using a Host Cluster. Leave all other option to default and click "Next".

Figure 2.3 – Configure Hardware
In the "Select Destination" section check the "Place the virtual machine on a host" and click "Next" after selecting your Host Cluster in the "Destination" drop down menu.

Figure 2.4 – Select Destination

In the "Select Host" section choose a server or leave the default server and click next.

Figure 2.5 – Select Host

In the "Configuration Settings" section specify the virtual machine path. This is the storage path where the Virtual Machine will be created in. In case of a Host Cluster you should be using one of the high available cluster shared volumes you have. Leave all other settings to default and click "Next".

Figure 2.6 – Configuration Settings

In the "Select Networks" section leave the default settings and click "Next". Networking has been configured in the "Configure Hardware" section. You may also configure this after the Virtual Machine is created.

Figure 2.7 – Select Networks

In the "Add Properties" section leave the default settings and click "Next" after specifying the appropriate operating system.

Figure 2.8 – Add Properties

In the "Summary" section click "Create". After the create process is complete power on the Virtual Machine to start the Windows Installation.

During the installation specify required settings and click next for the process to start.

Figure 2.9 – Windows Server Installation Process

Following successful operating system installation, install "Virtual Guest Services" by connecting to the VM via Hyper-V Console and navigating to "Action" in toolbar and selecting "Insert Integration Services Setup Disk".

Figure 2.10 – Installing Virtual Guest Services

After inserting the virtual image go to My Computer / DVD Drive "Integration Services Setup" and double click on it. A window will appear with a message about the upgrade procedure. Click "OK" to upgrade and reboot after the installation process is completed.

Figure 2.11 – Installing Virtual Guest Services

Following the installation of integration services components continue setting up virtual machine based on your requirements. Install windows updates, enable remote desktop, configure windows firewall etc.
Install the "Cloudworks WebsitePanel Plugin". Download this from the following link: https://downloads.interworkscloud.net/downloads/cloudoss/CloudWorks-Windows-WebSitePanelConfig.rar Unzip the contents of the file in c:\program files.
Download and install .Net Framework 4
Open command prompt with the "Run as administrator" option
Navigate to the folder that you have unzipped the "Cloudworks WebsitePanel Plugin" and run the "install.bat" file.
After the installation is complete go to "Windows Services", search for "Website Panel Virtual Machine Configuration Service" and "start" the Service after changing startup type to "Automatic".

Creating the Template

In the SCVMM Console navigate to your base Virtual Machine. Right click and select "Create" -> "Clone".
Specify a name for this clone VM and click "Next"
In the "Configure Hardware" section click on the "Advanced" Tab and check the "Make this Virtual Machine High Available" option. Click "Next".
In the "Select destination check "Place the virtual machine on a Host" and choose your host cluster or standalone server. Click Next
Leave all other options to default and click "Create".
After the creation is over you will have a Clone of the base Virtual Machine you have configured. We need this because after creating a template the Virtual Machine is destroyed. We need to have a base virtual machine always available in order to apply changes, clone it and create new templates.
Right click on the new clone we have created, create VM Template and click yes at the warning
Insert the VM template name and click next
Go to the "Configure Operating System" options and choose the correct operating system in general settings. Enter the product key of the Operating System, Time zone and click next.
In the "Select Library Server" option choose your library server and click next
Select the path in the library server to store the template and click next
Click Create and wait for the operation to finish.

interworks.cloud S.A.interworks.cloud OSS Microsoft Hyper-V Service ManagerInstallation Guide

Browser not supported