XenClient Enterprise 5.0. Synchronizer and Hyper-V. June 10, 2013. Table of Contents. Synchronizer / Hyper-V Overview. Local v s. Remote Virtual Desktops. Client. Server. Remote Desktops with XenServer VM runs on a remote XenServer, booting from a VHD file.
XenClient Enterprise 5.0
Synchronizer and Hyper-V
June 10, 2013
Installing the OS, applying OS updates, installing applications, or other activities performed to configure the VM image.
These operations use Hyper-V.
Automated process that creates a new VM image version prepared for deployment to managed computers.
Mark a published VM image version “Current” or “Staged” so it can be downloaded by managed computers.
When a VM image version is deployed to a computer, Engine will download the VHD files from Synchronizer.
These operations do not use Hyper-V.
After VHD files are downloaded, Engine will install the VM image as a local VM.
The installed VM will run on Engine independently of Hyper-V or the Synchronizer.
In Synchronizer console, select the VM image then click “Start”.
Synchronizer uses the Hyper-V API to create and start a Hyper-V VM. Hyper-V Manager should show the VM running.
The console for the Hyper-V VM is available through the Synchronizer console. This only works in Microsoft Internet Explorer and requires an Active-X plugin to be installed.
Best practice is to shutdown the VM from within the VM console. Synchronizer will automatically detect the VM shutdown.
The VM can also be shutdown from the Synchronizer console.
After VM shutdown, Synchronizer will delete the Hyper-V VM definition (but not VHD files). The Hyper-V VM is created on every start and deleted after every shutdown.
In Synchronizer console, select the VM image then click Version/Publish.
Synchronizer will create and start a Hyper-V VM, but the VM console is not connected. The VM should be left alone to run the publish scripts.
When the publish process is complete, a new version of the VM image should appear which can be deployed to client computers.
Synchronizer is installed directly on the Hyper-V host. Hyper-V has direct access to Synchronizer VHD files. One computer is used for both Hyper-V and Synchronizer services.
Virtual Appliance Installation
Synchronizer is installed in a VM and connects to a native (non-virtualized) Windows Server for Hyper-V. Hyper-V has access to VHD files through a shared folder exported from the Synchronizer VM.
Native Windows Server
VM Working Storage
VM Working Storage
This is the local Administrators group on the Hyper-V appliance.
Computer account of the VM where the primary Synchronizer server is installed.
User account used to integrate Synchronizer with Hyper-V.
Create a very basic VM with no virtual disk or boot device, then start it.
The VM should go to “Running” state, although the VM console will display a boot failure.
If the VM fails to start, it indicates a Hyper-V problem that should be resolved.
Hyper-V configuration is defined for the primary server in the Hyper-V tab.
Synchronizer will connect to the Hyper-V API using this hostname. It must be a fully-qualified hostname, not an IP address.
Virtual network for Hyper-V VMs created by Synchronizer. See Hyper-V Virtual Networks for details.
Port used by Synchronizer to connect to the Hyper-V console service. The default port is almost always correct.
Synchronizer uses these credentials for Hyper-V manager connections. The domain short-name prefix is required. See Hyper-V Credentials for details.
Synchronizer Hyper-V configuration includes a virtual network name.
The virtual network must match an entry in the Hyper-V virtual network manager.
Hyper-V VMs created by Synchronizer are configured to connect to the named virtual network.
To activate or reactivate the virtual appliance, select the primary server in the Overview section, then click the Activate Appliance action.
The mstrash and mswheel Synchronizer servers are installed in these VMs.
This VM was created by Synchronizer mswheel when a Windows 7 VM was started within the mswheel console.
This VM was created by Synchronizer mstrash when a Windows 8 VM was started within the mstrash console.