You got your XenMobile 9 Setup and hum. Your device policies are complete, your apps are packaged, configured and used successfully, you have tuned your cluster and database. And, most importantly, has enrolled their user base .
Just when you thought you wanted to settle in a steady rhythm, here Citrix comes you will be prompted to XenMobile 10. Upgrade
And to boot, it's vanilla upgrade not your run -of-the-mill - it is a major upgrade to a new platform. Why should you do it? A good question, indeed!
a number of good reasons there are why the upgrade makes sense. Let a few a look
# 1 :. Unified devices and applications
To start with, you have not connected to two seemingly incompatible systems to do at the hip: you manage devices (Device Manager) and manage applications (App Controller). XenMobile 10 provides a unified platform devices and applications in a holistic and consistent way to manage. While the association is at all levels of the product, the visible manifestation is a single console - the XenMobile console -. To manage users, devices and applications
For example XenMobile 10 RBAC and Local User Support provides within the console for both devices and applications to manage. The console provides a flexible and consistent manner to list, filter and act on devices and applications. Dashboard widgets give a comprehensive overview of the operational status of the system. And you can avoid two places configuring things -. Eg certificates, directory services, packages, rolls, etc. We have a whopping 50% reduction in the steps recorded required to configure device policies in the new console
# 2: to obtain Simplified cluster management
at the level of infrastructure that you no longer have two sets of clusters with different scaling properties. This reduces the number of VMs decreases must maintain and freed some infrastructure on. You can in a unified and easy way to update and patch the cluster nodes. And you can easily maintainability info to capture for all nodes in a cluster
#. 3: Simplified High Availability and scaling
, you can achieve high availability and near linear scaling cured simply by replicating VM node in the cluster. There is a single database for the system to SQL Server is running. In this way you can use corporate standard practices for database management and use, including for example, a configuration Disaster Recovery
#. 4: Active Directory improvements
There are more under the hood. For example, Active Directory integration in XenMobile 10 is considerably improved to do On Demand Active Directory synchronization, make it robust and scalable when they are dealing with large Active Directory databases. A particularly important feature is the new and scalable manner, which are deeply nested treated groups in Active Directory
#. 5: New Google Cloud Support
Support for Android Google Cloud Messaging also increases the scalability installations with a large fleet Android
#. 6: Better User Experience
user will be delighted. XenMobile 10 a completely redesigned App Store support with social features such as ratings and reviews
There are many good and important reasons to XenMobile to move 10, but let's face it, you have questions: What are the risks? What can go wrong? If the user must log in again? These are all legitimate concerns
Rest assured:., When you upgrade, retained their policies and configurations and users remain logged on.
is, What you need to know that a large number of XenMobile customers with medium to large installations have XenMobile successfully updated 10. You are now ready to take advantage of additional features in the new flow platform. should also
Here are a few resources to get you started:
- XenMobile 10 product documentation
- XenMobile 10 upgrade tool
- configuration clustering for XenMobile 10 clusterings for XenMobile 10
- disaster Recovery Guide for XenMobile
0 Komentar