Citrix Cloud Updates

The App Layering management console is being redesigned and modernized to no longer require Silverlight or Internet Explorer, to support modern browsers and plugins, and more.

The blade style is now applied to the final two nodes: Machine Catalogs and Policies. The new wizards appear in blade views with wider viewports, enabling more content to display. The workflows for configuring your settings remain the same.

Using Full Configuration, you can now change the size of MCS-provisioned VMs in Azure environments. The feature applies to both persistent VMs and non-persistent VMs.

In Full Configuration, when you create a catalog, a Hybrid Azure Active Directory joined identity type, is now available in Machine Identities. With that identity type, you can use MCS to create hybrid Azure Active Directory joined machines. Those machines are owned by an organization and signed into with an Active Directory Domain Services account that belongs to that organization.

You can now create configuration partitions within a single Citrix DaaS instance. You achieve that by creating tenant scopes in Administrators > Scopes and associating related configuration objects, such as machine catalogs and delivery groups, with those tenants. As a result, administrators with access to a tenant can manage only objects that are associated with the tenant. This feature is useful, for example, if your organization has independent divisions or separate IT management teams. Also, the Full Configuration interface lets you filter tenant customers by name. By default, the interface displays information about all tenants.

CSPs have a new permission to control which administrators can view the customer dashboard. This permission only allows you to show or hide the customer dashboard for custom access administrators. Only full access administrators can add new customers.

Citrix Cloud introduces REST APIs to create and consume reports that help you manage licensing in Citrix Cloud. 

The VDA upgrade feature allows Citrix DaaS administrators to automate upgrades to the latest version of the VDA (CR or LTSR) depending on the type of machine catalog.

Previously, you could use only VMs as machine profiles. You can now use ARM template specs as machine profiles as well when creating Azure machine catalogs. This feature lets you take advantage of Azure ARM template features such as versioning. To ensure that the selected spec is configured correctly and contains required configurations, we perform validation on it. If the validation fails, you are prompted to select a different machine profile.

In Full Configuration, when creating hosting connections, you're required to select a zone before selecting a connection type. The Connection type drop-down list displays hypervisors and cloud services available with the zone. (Previously, to ensure the Connection type list shows a required hypervisor or cloud service, you had to install its plug-in in every zone. With this new configuration sequence, you can now install the plug-in only in the required zone.)