Being able to quickly scale up and deploy Citrix quickly to your workforce has never been more important. And Cloud-based service is a strategic direction for Citrix, one that you cannot ignore if you are a Citrix client. So, what are the benefits of Citrix Cloud and what are the caveats?
George Spiers walks us through the pros and cons of migrating to Citrix Cloud.
• The Citrix Cloud architecture
• Architectural considerations when migrating to Citrix Cloud
• How to decide what stays on-prem and what is in the cloud
• Performance monitoring: How far do Citrix Director and Performance Analytics go
Virtual Apps and Desktops service
Citrix Gateway
Analytics
Citrix Secure Browser
Endpoint Management
ADM
WEM
=================
Talk about how components you previously deployed on-premises can now be hosted in Citrix Cloud
No database creation, no Site creation etc.
Talk about the upgrade process here. Latest release before on-premises editions are released. Canary approach.
Updates to services in Citrix Cloud such as a new release of the Virtual Apps and Desktops software, are released approximately every three weeks in a rolling fashion. Firstly Citrix internal sites receive the updates, and then updates will be pushed out gradually to customer environments. Delivering updates in this fashion reduces the risk of service impact and maximises availability for Citrix Cloud customers.
No longer do you have to perform monthly Windows patching to the servers hosting these services.
No longer do you have to upgrade the Virtual Apps and Desktops code.
Mention no requirement to manage SQL databases for WEM and Virtual Apps and Desktops.
No database creation, no Site creation etc.
Talk about the upgrade process here. Latest release before on-premises editions are released. Canary approach.
Updates to services in Citrix Cloud such as a new release of the Virtual Apps and Desktops software, are released approximately every three weeks in a rolling fashion. Firstly Citrix internal sites receive the updates, and then updates will be pushed out gradually to customer environments. Delivering updates in this fashion reduces the risk of service impact and maximises availability for Citrix Cloud customers.
No longer do you have to perform monthly Windows patching to the servers hosting these services.
No longer do you have to upgrade the Virtual Apps and Desktops code.
Mention no requirement to manage SQL databases for WEM and Virtual Apps and Desktops.
With a Virtual Apps and Desktops service deployment, talk about what the customer manages and what Citrix manage.
Talk about optional StoreFront and Gateway in exchange for Workspace and Gateway service.
Start from top then work down to Resource Locations. Talk about what a Resource Location is. How it becomes a Zone in VADS.
VDAs (can be hosted anywhere (Resource Locations)
That means Hypervisors, Storage, Network etc if on-premises.
Gateway (optional)
Storefront (optional)
Cloud Connectors (obviously)
Citrix Provisioning (if you use it)
Local Host Cache
Traffic flow
Security (credentials)
You would point StoreFront at your Cloud Connectors
Citrix Cloud as of March 2019 started to block TLS 1.0 and 1.1
If you have older receivers that need to continue using TLS 1.0 or 1.1, you will have to point those Receivers to a StoreFront
Local Host Cache only works with StoreFront. If you are an Epic customer, or run critical workloads, you will likely deploy StoreFront
You can still customise your StoreFront more than Citrix Workspace, and you can choose what URL you use, rather than a cloud.com URL.
Authentication methods
A number of authentication methods like RADIUS, SAML, Azure MFA etc can be used with your Gateway on-premises.
nFactor
You might use the Gateway for other services like VPN, or you might have multiple Gateways.
Traffic flow – with the Gateway on-premises, you can keep internal traffic from hair pining through Citrix Cloud
Talk about the Citrix Cloud Connector and how it connects your Resource Locations to Citrix Cloud
Talk about HTTPS/443 outbound only to Citrix Cloud. No requirement to open firewall rules inbound.
Pair of Connectors per RL.
How Cloud Connectors are managed and kept up to date by Citrix. You can now set the maintenance Window.
Can be installed on Server 2012 R2 and above – no server core support
Talk about HA and load balancing
Talk about different auth methods
Talk about different auth method
Talk about different auth method
Talk about different auth method
Talk about different auth method
Talk about different auth method
Talk about different auth method
Talk about different auth method
Talk about different auth method
Talk about what extra is required
On-premises License Server is required
You use the Provisioning Services Configuration Wizard, or the Licensing tab to select the Cloud radio button for licensing. Changes to licensing options requires the Stream service to be restarted
Talk about what extra is required
On-premises License Server is required
SDK to be installed, and an older one uninstalled
You use the Provisioning Services Configuration Wizard, or the Licensing tab to select the Cloud radio button for licensing. Changes to licensing options requires the Stream service to be restarted
Talk about HA and load balancing
Talk about HA and load balancing
If you click the Release Licenses button, Citrix Cloud gives you recommendations on what users and devices licenses can be released from, based on no activity in last 30 days.
Alternatively, you can select an individual licensed user, or licensed device, and release the license for that object.
Enabled with the flick of a switch
Allows external users to access their resources via Citrix Workspace
Changes the traffic flow
Internal user ICA traffic routes from Citrix Gateway service through Cloud Connector and then to VDA
To change that use Rendezvous protocol
Citrix Gateway service does not yet support EDT. Citrix plan for a Tech Preview later this year.
Changes the traffic flow so that the VDA connects directly to the Gateway service once the session is established. So user connection goes through Gateway service and to VDA, bypassing proxy connector.
Call our CAVD requirements (VDA version)
You have to use Workspace to access your resources, which also is true for being able to use the Gateway service.
Your VDAs must run the Virtual Apps and Desktops 7 1912 LTSR version.
The rendezvous protocol must be enabled via Citrix Policy (it is already enabled for all customers at a Citrix Cloud level).VDAs must be able to access https://*.nssvc.net including subdomains.
A DNS Reverse Lookup Zone with PTR records for the VDAs must be configured. A particular SSL Cipher Suite order must be configured, which is easily accomplished via Group Policy.
Changes the traffic flow so that the VDA connects directly to the Gateway service once the session is established. So user connection goes through Gateway service and to VDA, bypassing proxy connector.
Call our CAVD requirements (VDA version)
You have to use Workspace to access your resources, which also is true for being able to use the Gateway service.
Your VDAs must run the Virtual Apps and Desktops 7 1912 LTSR version.
The rendezvous protocol must be enabled via Citrix Policy (it is already enabled for all customers at a Citrix Cloud level).VDAs must be able to access https://*.nssvc.net including subdomains.
A DNS Reverse Lookup Zone with PTR records for the VDAs must be configured. A particular SSL Cipher Suite order must be configured, which is easily accomplished via Group Policy.
SSL Cipher Suite order, and default curve order
Two methods to verify Rendezvous is working
Currently in Technical Preview. Allows internal users to connect directly to VDAs they have direct connection to, bypassing Gateway service.
You have to define network locations, which are public Ips users will be connecting from
1. Create API Access client from Citrix Cloud portal
Run a bunch of commands to create your NLS Sites
Download the nls.psm1 PowerShell module from the Citrix Github repository
2. Import the nls.psm1 PowerShell Module
Create a $customer, $clientid and $clientsecret variables. The latter come frm the information saved when creating your Secure Client
4. Be sure to force PowerShell to use TLS 1.2
Connect to the Network Location Service using the three variables you created
Create a new NLS Site for each of your public networks.
In March 2020, Citrix announced that from the Virtual Apps and Desktops 7 2003 on-premises release onwards, hosting workloads (VDAs) in public clouds is an unsupported configuration. Customers have the following options:
To be able to host workloads in public clouds, you can leverage the Virtual Apps and Desktops service in Citrix Cloud.
Remain on version 1912 LTSR or the 7.15 version which included up to 5 years of mainstream support.
In March 2020, Citrix announced that from the Virtual Apps and Desktops 7 2003 on-premises release onwards, hosting workloads (VDAs) in public clouds is an unsupported configuration. Customers have the following options:
To be able to host workloads in public clouds, you can leverage the Virtual Apps and Desktops service in Citrix Cloud.
Remain on version 1912 LTSR or the 7.15 version which included up to 5 years of mainstream support.
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html
In short, Citrix’s “Service Commitment” is to maintain atleast 99.5% monthly uptime on Services. Monthly uptime is calculated by subtracting the minutes a service was in the state of “Unavailable” during a full month and calculating the percentage, known as the uptime percentage. The uptime percentage measurments exclude downtime that results from things such as regularly scheduled maintenance windows and customer failure to follow configuration guidelines and requirements for the service as documented by Citrix over on Citrix Docs. For more information on Citrix Cloud SLA, see: https://docs.citrix.com/en-us/citrix-cloud/overview/service-level-agreement.html