Proactive service alerts in Full Configuration. A flag icon is now available in the upper-right corner of Home, and a Troubleshoot tab appears for each zone that has issues. Currently, this feature gives you proactive warnings and alerts to make sure that your Local Host Cache and zones are configured correctly so that when an outage happens Local Host Cache works and your users are not impacted.
The Connector Appliance now provides functionality to connect a resource location to forests that do not contain Citrix Virtual Apps and Desktops resources.
A new "Notifications" tab is in development for administrators to set their preferences to receive notifications via email. This tab will also include the ability to add non-administrator users or listservs to receive these same notifications.
Support for SAML group-based administration within Citrix Cloud
The limit on the number of rows that you can export using the Export to CSV format feature on the Self-service pages is now increased from 10K rows to 100K rows.
Previously, you could schedule image updates by waiting for the MCS machine's next reboot, or by triggering an immediate reboot to all VMs in the catalog. With this feature, you can now create a reboot schedule for a desired catalog or VM(s) to occur once on a desired date and time in an effort to facilitate scheduled MCS image updates.
In VMware virtualization environments, when creating a machine catalog, you can now set a desired folder ID for the catalog. You can also change the folder ID after you create the catalog. When the folder ID changes, only the new VMs will be created inside the new folder. Existing VMs remain in the old folder.
The Cloud Connector installation can now use the system default browser.
You can now create a catalog that supports AWS EC2 hibernation. The hibernation process stores the in-memory state of the instance, along with its private and elastic IP addresses, allowing it to pick up exactly where it left off.
Using this feature, you can now change the network setting for an existing Provisioning Scheme so that the new VMs are created on the new subnetwork.