XenMobile 10 Cluster installation Here is the task that would be completed in order to implement a XenMobile 10 Cluster. For this example, running on my lab, I am using XenServer 6.5 SP1 as hypervisor and SQL 2014 installed on a Windows 2012 R2 as DB server. After the virtual appliance has been imported, power it on. Logon with default username which is admin. You will be prompted to change the password during the initial configuration. Enter the following network information for the virtual appliance: IP Address Subnet Mask Gateway Primary DNS Secondary DNS (optional) Confirm the settings to continue
17
Embed
XenMobile 10 Cluster installation - WordPress.com · XenMobile 10 Cluster installation Here is the task that would be completed in order to implement a XenMobile 10 Cluster. For this
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
XenMobile 10 Cluster installation
Here is the task that would be completed in order to implement a XenMobile 10 Cluster.
For this example, running on my lab, I am using XenServer 6.5 SP1 as hypervisor and SQL 2014 installed on a
Windows 2012 R2 as DB server.
After the virtual appliance has been imported, power it on.
Logon with default username which is admin.
You will be prompted to change the password during the initial configuration.
Enter the following network information for the virtual appliance:
IP Address
Subnet Mask
Gateway
Primary DNS
Secondary DNS (optional)
Confirm the settings to continue
Type Y and press Enter
Here I will chose N and press Enter
For the Database connection, remote is required in order to complete the cluster installation.
I am using a remote SQL Server on my lab so, enter mi and press Enter.
Enter the following information to connect to the remote SQL Server:
SSL Use
Server
Port
Username
Password
Database Name
Type Y and press Enter to commit settings
Note: XenMobile 10 has to create the database so the credentials to connect to remote SQL Server need
dbcreator role according to the product documentation (but also sysadmin role to avoid error messages)