June 10, 2013.ppt

* * * * * * * * * * * * * * * * * * * * * * * Hyper-V Configuration in Synchronizer Console 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. Virtual Appliance Configuration Virtual appliance configuration is defined for the primary Synchronizer server in the Virtual Appliance tab. This tab is not available for native installations Synchronizer installed directly on the Hyper-V host server . The UNC paths are used by Hyper-V to access VHD and ISO files managed by Synchronizer. UNC paths are mostly for display purposes. It is very rare that they would ever need to be changed. If you think you need to change these paths, please contact XenClient Enterprise support for guidance. Hyper-V Virtual Network Synchronizer Hyper-V configuration includes a virtual network name. Hyper-V VMs created by Synchronizer are configured to connect to the named virtual network. The virtual network must match an entry in the Hyper-V virtual network manager. Virtual Appliance Activation This action creates and configures the Synchronizer shared folder so Hyper-V can access VHD files managed by Synchronizer. Initial virtual appliance activation should be done automatically when Synchronizer is installed in virtual appliance mode. Do not reactivate the virtual appliance if any Hyper-V VMs are using VHD files in the Synchronizer shared folder! Reactivation deletes and recreates the folder share, which will disconnect the VHD file from the Hyper-V VM. This may result in the Hyper-V V