The XenMobile virtual machine (VM) runs on Citrix XenServer, VMware ESXi, or Microsoft Hyper-V. You can use XenCenter or vSphere management consoles to install XenMobile. Before you start, see the System Requirements for XenMobile 10.1
and the XenMobile Pre-Installation Checklist
Note: Ensure that the hypervisor is configured with the correct time because XenMobile uses that time. Also, be sure that the XenMobile virtual machine is configured to synchronize guest time with the host in the Virtual Machine properties.
XenServer or VMware ESXi prerequisites: Before installing XenMobile on XenServer or VMware ESXi, you must do the following. For details, refer to your XenServer or VMware documentation.
- Install XenServer or VMware ESXi on a computer with adequate hardware resources.
- Install XenCenter or vSphere on a separate computer. The computer that hosts XenCenter or vSphere connects to the XenServer or VMware ESXi host through the network.
FIPs mode prerequisites: Before installing a XenMobile Server in FIPS mode, you need to complete prerequisites with SQL Server. For details, see Configuring FIPS with XenMobile.
Hyper-V prerequisites: Before installing XenMobile on Hyper-V, you must do the following. For details, refer to your Hyper-V documentation.
- Install Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 with Hyper-V enabled, role enabled, on a computer with adequate system resources. While installing the Hyper-V role, be sure to specify the network interface cards (NICs) on the server that Hyper-V will use to create the virtual networks. You can reserve some NICs for the host.
- If you install Windows Server 2008 R2 or Windows Server 2012, do the following:
- Delete the file Virtual Machines/<build-specific UUID>.xml
- Move the file Legacy/<build-specific UUID>.exp into Virtual Machines
These steps are necessary because there are two different versions of the Hyper-V manifest file representing the VM configuration (.exp and .xml). The Windows Server 2008 R2 and Windows Server 2012 releases support only .exp. For these releases, you must have only the .exp manifest file in place before installation.
Windows Server 2012 R2 does not require these extra steps.