Users are not able to get Google PlayStore Apps. Tested different Google Play Accounts with different AndroidDeviceIDs. These accounts work well at on-premise XenMobile installations but not in Citrix Cloud. Error Message:
“Error, Application search Failed.”
Currently, CSPs are not able to provide hybrid storage to their tenant accounts, i.e. cloud and on-premise StorageZones on the same account. Rather, the CSP can provide exclusively on-premise or cloud storage to each of their tenants.
Multi-Tenant StorageZone: This is a single storage repository, managed by the CSP, which can be shared by an unlimited amount of CSP Content Collaboration tenants. This type of StorageZone is classified as an on premise StorageZone it can be linked to the partner’s cloud blob.
Normal or Standard StorageZone: This is a storage repository, managed by the CSP, which is dedicated to one Content Collaboration account. This type of StorageZone is classified as an on premise StorageZone it can be linked to the partner’s cloud blob.
Cloud StorageZone: This is a storage repository managed by Citrix, and not the CSP. This offering for CSPs provides an unlimited of storage to each Content Collaboration tenant.
1. Log-in to citrix.cloud.com with partner MyCitrix credentials. Within the main dashboard, select the “Resell” button under the Content Collaboration badge. If the button appears as “Manage” the partner can skip to step #4.
2. Create or Link a Content Collaboration Partner Account: Fill out the necessary fields in order to create a new Content Collaboration partner account or link an existing Content Collaboration partner account. If the partner has an existing Content Collaboration partner account but it doesn’t appear for automatic linking, please contact Citrix Support.
3. Optional – Set up a Multi-Tenant StorageZone: If the CSP decides to provide a Multi-Tenant StorageZone then the CSP needs to ensure the following:
The Multi-Tenant StorageZone needs to be registered and live on the partner’s Content Collaboration account before the CSP creates a Content Collaboration tenant account.
To check that the partner has successfully installed and registered a Multi-Tenant StorageZone to their partner Content Collaboration account, they can check by logging into their partner account from the Content Collaboration web app and navigate to “Admin Settings” >> “StorageZones.” Here, the Multi-Tenant StorageZone should be located under “Partner-Managed” tab.
If their StorageZone is under the “Customer-Managed” tab then they accidentally installed and registered a standard StorageZone (not Multi-Tenant enabled). In order to change their standard StorageZone to a Multi-Tenant StorageZone the partner will have to “Delete this Zone” within the Content Collaboration web app, remove the StorageZone from their designated server, and re-create the StorageZone and run the Multi-Tenant command prompt.
4.Create a Content Collaboration Tenant Account: From the partner’s Citrix Cloud customer dashboard, select “Invite or Add.” If the partner would like to add a new Citrix customer they will be prompted to fill out information about their new tenant’s Citrix Cloud account. If the partner would like to invite an existing Citrix Cloud customer to their customer dashboard, they can send them a link. Once that customer receives that link and accepts the terms and conditions of becoming a tenant of the CSP. The partner can then add services to their tenants through the customer dashboard by selecting the three dots by the tenant’s company name, then selecting “Add Service” >> “Content Collaboration.”
The partner will select the primary StorageZone that the Content Collaboration tenant will consume. If they select a Multi-Tenant StorageZone, they are required to specify the existing StorageZone (live, and registered on their Content Collaboration partner account).
Master Admin user information must be specified, and will be added to the tenant’s account, along with a partner admin user.
All tenant accounts receive 1,000 available licenses. The CSP payment model is based on the total number of used licenses, and not on total number of all licenses.
A partner admin user is always provisioned on the CSP’s Content Collaboration tenant account. This allows the partner to manage the customer’s account, such as configure account settings, manage employee users, run reports, etc. This partner admin is added to the Super User group within their tenant’s account, giving this user complete access to all files and folders. If the partner does not want access to the customer’s Content Collaboration data, they will need to remove the partner admin user from the Super User group. Once the partner admin is removed from the Super User group then that user will only receive access to files that are specifically shared by other employee users.
If the CSP has managed Content Collaboration tenants prior to establishing their Citrix Cloud partner account, then their existing tenants will not appear on their Citrix Cloud customer dashboard. Instead, these tenants will only appear on the partner’s Content Collaboration account under “Admin Settings” >> “Advanced Preferences” >> “Tenant Management.” If “Tenant Management” is not an option, then this particular partner user will need to enable the “Manage Tenants” user permission. There is currently not a way to import or show these existing tenants in the CSP’s Citrix Cloud customer dashboard.If the CSP creates a tenant from within Citrix Cloud, then that tenant will appear in their Citrix Cloud tenant dashboard.
If the CSP has created some tenants via the online form and some via Citrix Cloud, then the partner can easily see all tenants from within the partner’s Content Collaboration account (first bullet).
For Multi-Tenant StorageZones:
Each tenant onboarded to a partner’s Multi-Tenant StorageZone receives their own root-level folder within the StorageZone. The name of the root-level folder is the tenant’s unique Content Collaboration account ID (starts with an “a”).
For CSP reporting (i.e. payment model):
CSPs are required to report on the amount of used licenses by their Content Collaboration tenants to their preferred Citrix distributor. For directions on capturing the accurate number of licenses for monthly reporting:
Hotfix package name: BrokerSvcWX64_7_15_2001.zip
For: XenApp and XenDesktop 7.15 Long Term Service Release (LTSR) Cumulative Update 2 (CU2) for Citrix Broker Service (7.15.2000.243)
Replaces: None
Date: October, 2018
Languages supported: English (US), Japanese (JA), Simplified Chinese (SC)
Readme version: 1.00
Readme Revision History
| Version | Date | Change Description |
| 1.01 | October, 2018 | Fixed the power state issue for the previous build |
| 1.00 | August, 2018 | Initial release |
Important: This hotfix can only be applied to a XenApp and XenDesktop 7.15 LTSR CU2 Desktop Delivery Controller.
Caution: The Broker Service hotfix (Broker_Service_x64.msi) included in this update also modifies the Broker DbSchema of the Site data store.* These modifications are permanent and irreversible. Should you decide, for any reason, to uninstall this update at a later time, these modifications do not revert automatically. As a result and as a matter of precaution, Citrix recommends strongly that you back up your Site data store as described below before installing this update. Doing so allows you to manually restore your Site data store to the backed up version. Even so, any changes you make to your Site data store between backing up and restoring it are lost. For information about backing up and restoring data stores, see Knowledge Center article CTX135207.
For an automatic database upgrade, the Studio user needs permissions to update the SQL Server database schema (for example, the db_securityadmin or db_owner database role). If the Studio user does not have those permissions, initiating a manual database upgrade will generate scripts. The Studio user runs some of the scipts from Studio; the database administrator runs other scripts using a tool such as SQL Server Management Studio. If the SQL scripts are run manually, they should be run using either the SQLCMD utility or SQL Management Studio in SQLCMD mode. Inaccurate errors can result otherwise.
After the upgrade to this release, a prompt might appear for the License Server compatibility check in Desktop Studio that makes sure that your License server is the required version. If you are using the License server released with XenDesktop 7.15 or from a more recent version, you do not need to upgrade the License server. Click Continue to proceed with the DBschema upgrade.
If the Download link is not available on this page and you wish to obtain this limited distribution release, visit our support site at http://www.citrix.com/support and open a support case using your Citrix account credentials, or contact your reseller at http://www.citrix.com/partners/locator.
Testing of this release was targeted only at the affected functionality, and regression and stress testing were minimal. Introduce this release to a test environment for evaluation before deploying it to a production environment.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CITRIX AND ITS SUPPLIERS MAKE AND YOU RECEIVE NO WARRANTIES OR CONDITIONS, EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, AND CITRIX AND ITS SUPPLIERS SPECIFICALLY DISCLAIM WITH RESPECT TO THE HOTFIX ANY CONDITIONS OF QUALITY, AVAILABILITY, RELIABILITY, SECURITY, LACK OF VIRUSES, BUGS OR ERRORS, OR SUPPORT AND ANY IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, ANY WARRANTY OF TITLE, QUIET ENJOYMENT, QUIET POSSESSION, MERCHANTABILITY, NONINFRINGEMENT, OR FITNESS FOR A PARTICULAR PURPOSE. TO THE EXTENT PERMITTED BY APPLICABLE LAW, NEITHER CITRIX, NOR ITS SUPPLIERS SHALL BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL, MULTIPLE, PUNITIVE OR OTHER DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF DATA, LOSS OF INCOME, LOSS OF OPPORTUNITY, LOST PROFITS, COSTS OF RECOVERY OR ANY OTHER DAMAGES), HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, AND WHETHER OR NOT FOR BREACH OF CONTRACT, NEGLIGENCE OR OTHERWISE, AND WHETHER OR NOT CITRIX, ITS SUPPLIERS, OR LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
You import changes from the principal broker to the Local Host Cache (LHC) database and remove a user or machine from the Active Directory without removing it from Citrix Studio. As a result, errors might occur and the LHC isn’t updated.
[From BrokerSvcWX64_7_15_2001][#LC9054]]
No hotfixes were replaced by this release.
| Component | Hotfix Name | Version | MSI Name |
|
Citrix Broker Service |
BrokerSvcWX64_7_15_2001 |
7.15.2001.2 |
Broker_Service_x64.msi |
Notes:
Important Notes: This release is packaged as a .zip file containing the replacement .msi files for the Broker components of XenApp and XenDesktop 7.15 LTSR CU2 Controller. For more information about deploying msi files, see Microsoft article 884016 or visit the Microsoft Web Site and search on keyword msiexec.
Caution: The Broker Service hotfix (Broker_Service_x64.msi) included in this update also modifies the Broker DbSchema of the Site data store.* These modifications are permanent and irreversible. Should you decide, for any reason, to uninstall this update at a later time, these modifications do not revert automatically. As a result and as a matter of precaution, Citrix recommends strongly that you back up your Site data store as described below before installing this update. Doing so allows you to manually restore your Site data store to the backed up version. Even so, any changes you make to your Site data store between backing up and restoring it are lost. For information about backing up and restoring data stores, see Knowledge Center article CTX135207.
For an automatic database upgrade, the Studio user needs permissions to update the SQL Server database schema (for example, the db_securityadmin or db_owner database role). If the Studio user does not have those permissions, initiating a manual database upgrade will generate scripts. The Studio user runs some of the scipts from Studio; the database administrator runs other scripts using a tool such as SQL Server Management Studio. If the SQL scripts are run manually, they should be run using either the SQLCMD utility or SQL Management Studio in SQLCMD mode. Inaccurate errors can result otherwise.
Caution: Downgrades, also known as rollbacks, from individual component update in this release are not supported and might leave your systems in an unstable state. The component update in this release do not patch the existing installations of the components – each fully replaces the original component with a new installation. As a result, uninstalling a component update removes the entire component from the Controller. If the need arises to revert to an earlier version of the product, you must uninstall each component update of this release and then reinstall the earlier versions of each component. Reverting to an earlier version of a component might result in the loss of settings you configure while this upgrade is installed.
To install the component updates in the release successfully, servers must not have registry modification restrictions in place.
For information about installing XenDesktop/XenApp 7.x Controller updates, see Knowledge Center article CTX201988.
To install the component updates in this release:
To uninstall this hotfix and revert to an earlier level of the component and the data store:
Microsoft releases regular builds of the next version of Windows 10 through their Insider Preview Program. Citrix does not support Insider Preview builds as stated on CTX224843 – Windows 10 Compatibility with Citrix XenDesktop.
This article is intended to capture known issues with Windows 10 Redstone 5 (RS5) that have been identified so far through Citrix internal testing and customer reports for the benefit of customers who are conducting early testing in preparation for when the Semi-Annual Channel release of RS5 becomes available.
Note:
The following are the known issues:
Problem Cause
Full-screen sessions hide the PIN prompt window. The Windows Security and UAC prompt are updated from Winform to XAML. This causes the PIN prompt window to lose focus and stay in the background.
Solution
This is a known issue with Citrix Receiver (https://docs.citrix.com/en-us/receiver/windows/current-release/about/known-issues.html).
Problem Cause
Monochrome custom cursors created via CreateCursor() in a non-DPI aware application do not scale correctly with Windows 10 v1703 and later versions. Custom cursors created via CreateInconIndirect() in a non-DPI aware application do not scale correctly in all versions of Windows 10.
Solution
Issue Description
The mouse cursor is distorted or may disappear at times when a published application or VDA is launched in full screen on multi-monitor setup with high DPI/Resolution.
[RFWIN-7040]
Problem Cause
Monochrome custom cursors created via CreateCursor() can be distorted on multi-monitor setups with mixed DPI in Windows 10.
Solution
Problem Cause
During the upgrade,the key CtxBackupShell is getting removed under [HKLM -> SOFTWARE -> Microsoft -> Windows NT -> CurrentVersion -> Winlogon] . As a result, an error message “1: Read failed HKLMSOFTWAREMicrosoftWindows NTCurrentVersionWinlogonCtxBackupShell=(32bit on 32bit)” is displayed.
Solution
This issue is resolved with Redstone 5 build 17763 and newer.
Issue Description
Pin prompt for Smart card authentication is not available to login into VDA session. User is prompted for “Username” and “Password” instead of Smart card PIN to login into VDA session.
[HDX-13195]
Problem Cause
Microsoft has changed the way Smart Card Service (SCardSvr) works in Windows 10 v1803 and later versions. The service will run only if a Smart Card reader is connected. As ICA sessions redirect the Smart Card, it finds the service not to be running and fails.
Solution
Microsoft has provided a mechanism to enable to enable Smart Card Service (SCardSvr) by adding a registry key. To add the registry key, follow below steps on the VDA:
Caution! Refer to the Disclaimer at the end of this article before making changes to Registry
Issue Description
Print command from inside an ICA session of Windows 10 RS5 client fails to print using mapped Citrix UPS configured XPS Printer.
[HDX-13664]
Problem Cause
XPS Viewer is not available on Windows 10 v1803 and later versions by default. It is available as a Feature on Demand.
Solution
To install XPS Viewer, follow the below steps:
Note:
Issue Description
Some maximized applications in Local App Access(LAA) enabled desktop sessions cannot be minimized using the minimize button. (Example application: Notepad, CMD)
[LC8813]
Problem Cause
The issue is due to an incorrect function call getting triggered for LAA enabled desktops.
Solution
This issue is resolved in Citrix XenDesktop 7.18 and CU2 for XenDesktop 7.15.
Issue 8
Issue Description
Citrix Workspace Environment Management (WEM) Agent fails to work when Windows 10 is upgraded to Redstone 5.
[TPV-1184]
Problem Cause
The ‘Norskale’ key under [HKLM -> System -> CurrentControlSet -> Control] is removed during the upgrade to Redstone 5.
Solution
This issue is resolved with Redstone 5 build 17763 and newer.
Issue 9
Issue Description
Upgrade from Windows 10 v1803 to Redstone 5 fails if Citrix User Profile Manager (UPM) is installed.
[TPV-1431]
Problem Cause
The upgrade fails with an error message “error during MIGRATE_DATA operation”.
Solution
The Microsoft KB4343909 resolves this issue. Install KB4343909 OR its replacement prior to upgrade of Windows 10 RS5.
Issue 10
Issue Description
Citrix User Profile Manager (UPM) stops working after Windows 10 is upgraded to Redstone 5.
[TPV-1307]
Problem Cause
The upgrade process is removing some of the registry entries related to UPM.
Solution
Citrix is working with Microsoft to resolve this issue.
Workaround 1:
As a workaround, users are advised to reinstall UPM after upgrading to Redstone 5.
Workaround 2:
Add the registry keys manually that were removed during upgrade.
Caution!
Part A – Setting permissions to Administrator group.
Part C – Restore permissions to TrustedInstaller
Issue 11
Issue Description
Client Drives are not getting mapped within a Redstone 5 Build 17666 VDA.
[LCM-4255]
Solution
This issue is not seen with Redstone 5 build 17682.
Issue Description
Unable to open Internet Explorer, unable to install 3rd party browsers like Chrome after installing Citrix VDA on Redstone 5 Build 17666
[LCM-4254]
Solution
This issue is not seen with Redstone 5 build 17682.
Issue Description
UPS Printers are not getting mapped within a Redstone 5 Build 17661 VDA.
[LCM-4253]
Solution
This issue is not seen with Redstone 5 build 17682.
Issue Description
Upgrade to Redstone 5 build 17713 on x86 platform fails with error message “Modern Setup Host has stopped working”.
[TPV-1695]
Solution
This issue is not seen with Redstone 5 17723 build and newer.
Issue Description
Upgrade to Redstone 5 build 17744 fails and rolls back.
[TPV-1785]
Problem Cause
The upgrade process fails with error message “The installation failed in the SECOND_BOOT phase with an error during BOOT operation”.
Solution
This issue is not seen with builds 17754 and later.
Issue Description
WinSCard ‘AccessStartedEvent’ is not signalled when the Smart Card Service is running, with no Smart Card reader present. This may break explicit Smart Card authentication within an ICA Session.
Problem Cause
When the Microsoft Smart Card Service is running, calling the SCardListReaders API should return the SCARD_E_NO_READERS_AVAILABLE error.
Solution
This issue is fixed with builds 17754 and newer builds.
Issue Description
Smart Card is not detected during launch of Redstone 5 17751 VDA.
[TPV-1826]
Problem Cause
A message “Connect the Smart Card” is displayed though the Smart Card is connected to the end point.
Solution
This issue is fixed with builds 17754 and newer builds.
Issue Description
Mouse pointer is not visible within a RS5 HDX 3D pro session. All operations inside the session are to be performed by keyboard using shortcuts.
[LCM-4951]
Solution
Citrix is working with Microsoft to resolve this issue.
Issue Description
After HDX 3D Pro VDA is upgraded from Windows 10 v1803 to RS5, the policy “Use hardware encoding for video codec” is not in effect and Hardware Encoding is disabled. The Registry information related to BitMap Provider is also not as expected post upgrade.
[LCM-4955, LCM-4956]
Solution
Citrix is working with Microsoft to resolve this issue.
Workaround:
C:Program FilesCitrixICAServiceNvFBCEnable.exe -enable
C:Program FilesCitrixICAServiceNvFBCEnable.exe -checkstatus
Note – If status is still shown as disabled, then Nvidia driver may need to be reinstalled. After reinstalling the driver, try to enable FBC again.
On Controllers, select Start > Citrix > Citrix Scout
Scout lists the Controllers and VDAs it discovers. Beginning with XenApp and XenDesktop 7.16, Scout allows to add/remove machines manually, such as StoreFront Servers and Provisioning Services Servers.
On the Scout opening page, click Collect.
Select the machines you want to collect diagnostics from.
When machine verification completes, click Continue.
Review the list of machines, and click Start Collecting.
After collection completes, click Continue.
Next step:
On the Scout opening page, click Trace & Reproduce.
Select the machines you want to start tracing from.
When machine verification completes, click Continue.
Review the list of machines and click Start Tracing.
When done reproducing the issue, click Continue.
Indicate if you were able to reproduce the issue, and click Start Collecting.
When collection completes, click Continue.
Next step:
Follow the steps on “How do I collect diagnostics?” or “How do I collect traces while reproducing issues and collect diagnostics?”
Select Upload the diagnostics collection to Citrix.
Select Citrix Credentials, and click Continue.
Enter your Citrix username and password.
Optionally check Store and skip this step in the future.
Click Continue.
Adjust upload name, and optionally enter a case number and description.
Click Start Upload.
Click Done to return to main UI.
Follow the steps on “How do I collect diagnostics?” or “How do I collect traces while reproducing issues and collect diagnostics?”
Select Upload the diagnostics collection to Citrix.
Select Citrix Cloud Credentials, and click Continue.
Click Generate token at Citrix Cloud (this will open a browser window).
Sign in to Citrix Cloud.
Click Copy.
Return to Scout UI and paste token.
Optionally check Store and skip this step in the future.
Click Continue.
Adjust upload name, and optionally enter a case number and description.
Click Start Upload.
Click Done to return to main UI.
Follow the steps on “How do I collect diagnostics?” or “How do I collect traces while reproducing issues and collect diagnostics?”
Select Save the diagnostics collection on your local machine, and click Continue.
Select the directory, enter the File name, and click Save.
Click Done to return to main UI.
Follow the steps on “How do I upload diagnostics to Citrix using Citrix Credentials” or “How do I upload diagnostics to Citrix using Citrix Cloud Credentials?”
On the last step, click View Analysis.
You will be taken to Citrix web site so you can review the Health Check Summary.
On the Scout opening page, click Schedule.
Select the machines you want to review the configured schedules.
When machine verification completes, review the schedule status.
Click Back to return to main UI.
Follow the steps 1, 2 and 3 on “How do I review periodic diagnostic collection schedule?”
Click Continue.
Review the list of machines that schedules will be adjusted and click Continue.
Select the Frequency: Weekly, Day of the week and Time.
Click Continue.
When configuring weekly schedules, you will be asked for credentials (refer to previous “How do I” related to Credentials for instructions).
When credentials are provided, click Continue.
Review Schedule to confirm it has been set weekly, and click Done to return to main UI.
Follow the steps 1, 2 and 3 on “How do I review periodic diagnostic collection schedule?”
Click Continue.
Review the list of machines that schedules will be adjusted and click Continue.
Select the Frequency: Daily and Time.
Click Continue.
When configuring daily schedules, you will be asked for credentials (refer to previous “How do I” related to Credentials for instructions).
When credentials are provided, click Continue.
Review Schedule to confirm it has been set daily, and click Done to return to main UI.
Follow the steps 1, 2 and 3 on “How do I review periodic diagnostic collection schedule?”
Click Continue.
Review the list of machines that schedules will be adjusted and click Continue.
Select the Frequency: Off.
Click Continue.
Review Schedule to confirm it has been set to off, and click Done to return to main UI.
If you need to use a proxy to authenticate or upload files to Citrix, a Configure proxy link will be displayed on Scout status bar.
Click on Configure Proxy.
Select your Proxy Settings.
Click Done to return to steps you are following on previous “How do I…”
If you have selected the option “Store token and skip this step in the future”, you no longer need to enter credentials to send diagnostics to Citrix.
If you want to clear the previously saved token:
Follow the steps on “How do I upload diagnostics to Citrix using Citrix Credentials?” until you reach the Upload details screen.
On the status bar, click Change / Reauthorize.
Select Citrix Credentials, and click Continue.
Enter your Citrix username and password.
Be sure to uncheckStore and skip this step in the future.
Click Continue.
When you see the Upload details screen, you can close Scout.
Next time you run Scout, credentials will always be requested.
Click on the “?” icon to visit https://docs.citrix.com/scout.
For the case where every Linux endpoint connecting to a particular store has Linux Workspace App installed, refer to Solution – 1
If there is a mixed environment of Linux endpoints connecting to a particular store, i.e some endpoints have Citrix Workspace App installed and some do not have Citrix Workspace app installed then please refer to Solution- 2
In DDC, launch Citrix Studio > Click Stores under Citrix StoreFront in the left pane > Manage Receiver for WebSites (in Right panel) > configure > Deploy Citrix Receiver – give the deployment option as Install locally.
Always open ICA files: After the above mentioned configuration, Firefox will ask the Users to download the ICA file when clicked on the desktop/app enumeration for the first time. Click the “Open with” option and select “Do this automatically for files like this from now on”.
From now on whenever we click a desktop or app it launches automatically with wfica, which effectively means that when the user subsequently clicks on any virtual app icon or virtual desktop icon, it will just simply launch that virtual app or virtual desktop and none of the behaviors described in the symptoms section above will be experienced by the end-user.
In the scenario where some Linux endpoints have Workspace app for Linux installed and some don’t – follow the below steps. This will allow the users launching their desktop/app either using Receiver for HTML5 or Workspace app/Receiver for Linux.
In DDC, launch Citrix Studio > Click Stores under Citrix StoreFront in the left pane > Manage Receiver for WebSites (in Right panel) > configure > Deploy Citrix Receiver – give the deployment option as “Use Receiver for HTML5 if local receiver is unavailable”
Open the file “web.config” in the path – C:inetpubwwwrootCitrixStoreWeb
Add “Linux” to protocolHandler element as shown below:
When you access storefront from Firefox, on the first page select “Detect Receiver”
For those users that have Receiver installed Select “Already Installed” and go ahead with the next steps.
For those users who do not have Workspace App or Receiver for Linux installed and wants to go ahead with HTML5 receiver select “Use light version”
If the user has selected “Already Installed”: Follow “Always open ICA files” as mentioned above. From now on whenever we click on a desktop/app enumeration, it launches automatically with wfica, thus enabling a smooth seamless user-experience with launch of virtual applications and desktops.
Note: Citrix Cloud Studiocan perform all these actions automatically when using the Create new… option while adding a new Hosting Connection. Account privilege level in Azure must be Owner (not Contributor) to perform the actions listed in Step 1 and Step 4. If your Azure account role is Contributor, you might see the error “Invalid Azure Credentials” in Citrix Cloud Studio when choosing the Use Existing… option or no error but a window prompting for credentials again when using the Create New option. Only follow the steps below once you’ve confirmed the current role level for your Azure account.
Login to your Azure Tenant
Select the Azure Active Directory blade
Select App Registrations
Select “+ New application registration”
Enter:
Name
Application Type: “Web app / API”
Sign-on URL: “https://citrix.cloud.com”
Select Create
Select the App Registration from Step 4 to open its Settings
Select Required Permissions under API Access
In the Required permissions Tab Select “Windows Azure Active Directory”
Check the box “Read all users’ basic profiles”
Select Save
In the Required permissions Tab Select “+ Add”
Choose “Select an API”
Select Windows Azure Service Management API
Select “Select”
In the Enable Access tab Select “Access Azure Service Management as organization users”
Select “Select”
Select “Done”
From the Settings tab of the App registration; select “Keys”
Enter a name for this secret in “Key Description”
Select a Duration from the drop down
Select Save
Copy the value of the Key (this is the secret, similar to a password you will only see once)
Select the Properties
Copy the Application ID of the App registration (this is similar to the username)
The Key and Application ID are pieces of information required to create the Host connection to Azure from Citrix Cloud.
Now that the App registration account has been created and access has been granted to the Azure API it needs to be granted permissions to resources within your Azure account.
Citrix recommends that Citrix Cloud specific subscriptions be created. This reduces the risk of worker provisioning or life cycle actions from interfering with or impacting other production systems.
The following instructions utilize the built-in Azure RBAC Roles. The instructions select the most restrictive built-in Role for a particular resource, this allows Citrix Cloud to do what it needs to for worker machine provisioning and lifecycle actions.
At this point, there is a decision of how much control a customer will grant to the Citrix Cloud App registration for machine provisioning.
Citrix Managed – In this model, Citrix Cloud is in full control of Resource Group(s) during the machine provisioning process. As Resource Groups are required, Citrix Cloud will simply add more as necessary to support the additional catalogs being provisioned. This streamlines the management experience by handling these details. This also makes the Citrix administrator the sole arbiter of how many virtual machines can be deployed.
Customer Managed – In this model, an Azure Admin or Co-Admin pre-creates Resource Groups that worker machines will be provisioned in to. Citrix Cloud cannot create additional Resource Groups as necessary, this will need to be performed by an Azure Subscription Admin or Co-Admin. This will require good communication between the Citrix Administrator and Azure Administrator as the number of Citrix workers in Azure is increased.
Note: The Customer Managed option is currently supported in the Citrix Cloud and in XenApp and XenDesktop 7.16 or later via the Studio GUI.
The primary difference between the two is the level of control that the application service principal has to the Azure Subscription and resources. These two models are detailed below.
The following outlines the permission settings required for the resource that is being secured with the built-in Azure RBAC role that provides the minimum settings necessary for the model.
Most of the settings will be the same for both models, except the settings on the Subscription where Citrix workers will be provisioned and the Resource Groups within it.
For more information about assigning permissions see: https://docs.microsoft.com/en-us/azure/active-directory/role-based-access-control-configure
For more information about built-in Azure RBAC roles see: https://docs.microsoft.com/en-us/azure/active-directory/role-based-access-built-in-roles
The Subscription where Citrix workers (XenApp and/or XenDesktop will be provisioned) will reside.
| Management Model | Citrix Managed | Customer Managed |
| Azure RBAC Role | Contributor | None Azure Admin / Co-Admin must create Resource Groups manually |
To grant the App Registration Contributor permission to a Subscription:
The Resource Groups within the Subscription where Citrix workers will be provisioned.
| Management Model | Citrix Managed | Customer Managed |
| Azure RBAC Role | Contributor Inherited from Subscription |
Virtual Machine Contributor Storage Account Contributor |
To grant the App Registration Contributor permission to a Resource Group
Citrix Managed – Do nothing, the permissions will be inherited.
Customer Managed – Complete the following:
The Azure Virtual Network that Citrix worker machines will be joined to.
| Management Model | Citrix Managed | Customer Managed |
| Azure RBAC Role | Contributor Inherited from Subscription |
Virtual Machine Contributor |
Complete this for both scenarios.
The Resource Group within the Subscription where Citrix worker master images are maintained. Citrix and / or Desktop administrators should have full access, but the App registration does not need to modify the image.
| Management Model | Citrix Managed | Customer Managed |
| Azure RBAC Role | Contributor Inherited from Subscription |
Virtual Machine Contributor |
Complete this for both scenarios.
Citrix Documentation – Citrix Cloud Connector
If you have worked through the process of manually creating an App registration in Azure and properly assigning the permissions, this new App registration now needs to be added to Citrix Cloud as a Resource Location for capacity.
Within the Citrix Cloud management portal / Citrix Studio;
Select Hosting
Select “Add Connection and Resources”
Select “Create a new Connection”
Select the Azure hosting environment
Select Next
Select “Use existing”
Copy and paste;
Azure Subscription ID (where Citrix workers will be provisioned by Citrix Cloud)
Active Directory ID (the Directory ID of the Azure Active Directory in which the App registration was defined)
Application ID (of the App registration)
Application secret (the Key)
Enter a “Connection name”
Select Next
Select the Azure Region where Citrix workers will be provisioned
Select Next
Enter a Citrix Cloud name for this Azure Subscription and Region
Select the Azure Virtual Network that Citrix Worker machines will be joined to
Select the Azure Virtual Network Subnet that Citrix Worker machines will retrieve IP addresses from
Select Next
Select Finish
To use copy and paste in Citrix Cloud Studio:
Select the Half Circle connection menu in the top center of the browser
Select the Clipboard
Copy your Azure Subscription ID to the Clipboard
Either; right click and paste or use CTRL + v to paste the clipboard contents to the remote clipboard
Select the X to close the Session clipboard
Select the field to paste the data to
Either; right click and paste or use CTRL + v to paste the clipboard contents to the field
In order to enable FAS together with the Citrix Cloud, the following Citrix components must be built outside of the XenApp and XenDesktop Service (note that not all are offered today in Citrix Cloud, but are included below for completeness):
The above components may be built in a public cloud or in an on-premises datacenter. The FAS and StoreFront servers should be configured according to product documentation just as they would for a fully customer-owned solution to support FAS authentication, including such items as applying Group Policy settings and configuring Microsoft Certificate Authority servers.
This article describes how Custom Workflows can be integrated with third party applications using Post to Web Services action. It is assumed that reader is aware of HTTP, Web service , POST, and Custom Workflows web composer application.
To post data to webservices hosted on-premises, use Citrix Cloud Connector. Otherwise, you can jump to Configuring Post-to-Web-Service in Custom Workflows
Get-Service Citrix* | Stop-Service -force
2. Remove the connection strings value manually via registry on all DDCs in the site:
Connection String in XenApp / XenDesktop 7.6
HKEY_LOCAL_MACHINESOFTWARECitrixDesktopServerDataStoreConnectionsController
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesADIdentitySchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesAnalyticsDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesConfigLoggingSiteSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesConfigurationSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesDASDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesDesktopUpdateManagerSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesEnvTestServiceSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesHostingUnitServiceSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesMonitorDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesStorefrontSchemaDataStoreConnections
Connection String in XenApp / XenDesktop 7.15
HKEY_LOCAL_MACHINESOFTWARECitrixDesktopServerDataStoreConnectionsController
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesADIdentitySchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesAnalyticsDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesAppLibrarySchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesConfigLoggingSiteSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesConfigurationSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesDASDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesDesktopUpdateManagerSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesEnvTestServiceSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesHostingUnitServiceSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesMonitorDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesOrchestrationSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesStorefrontSchemaDataStoreConnections
HKEY_LOCAL_MACHINESOFTWARECitrixXDservicesTrustSchemaDataStoreConnections
Delete the value for the ConnectionString Registry Key:
3. Restart the Citrix Services. Open elevated PowerShell and run:
Get-Service Citrix* | Start-Service
4. Open Studio. You will see the option to create a new site. Follow the wizard to create a new database for your site.
5. Once completed, add any additional DDC(s) as needed.