Fourth in the series of moving the control plane to Citrix Cloud…. So you have moved your control plane and now you need some monitoring via the wonders of Director. You can do this… There are some things that you have to consider. First, historical data DOES NOT migrate as part of using the Automated Configuration Tool (ACT). I looked over the list of things that it did, and that was not one of the things listed as migrating. I did learn through a ticket that moving the historical data is not at this time supported, nor was there a tool to move said data. For those customers that heavily rely on the reporting data available, you will need to plan accordingly. This presents a difficulty that an on-prem version of Director would need to be maintained for a year (or whatever grooming schedule you have defined) to allow the data to be accessed while the new data was populating. This can cause issues with people needing to access BOTH locations in order to get accurate data. Also, default for Premium / Platinum customers is 90 days of historical data in Director. Advanced licensing provides 31 days. If you need more time than that, you will need to open a ticket with Citrix to get that time extended which can take 1 – 2 weeks. (More information on Citrix Director in Cloud can be found here: Director On Citrix Cloud )
Now if you have setup AD Connect to connect to Citrix Cloud with company credentials, you can publish Director with the accounts people already use to login with at their company. After moving, there is also a post that will come about how scopes are affected and you have to reassign your access groups used in your company to the new Monitor role that is created for EACH scope they need access.
To confirm that you have AD Connect configured, you can check the Identity And Access Management on the hamburger menu on your Citrix Cloud login.
It should show Azure Active Directory and next to https://citrix.cloud.com/go should be your company name selected when you connected AAD.
If this is showing as connected, you can publish Director to your helpdesk group.
These are the arguments for publishing Director with Microsoft Edge:
ApplicationName : Director
CommandLineArguments : https://xenapp.cloud.com/monitor
CommandLineExecutable : %ProgramFiles(x86)%\Microsoft\Edge\Application\msedge.exe
WorkingDirector : %ProgramFiles(x86)%\Microsoft\Edge\Application
Once you have published the app to your users, the directions below will allow them to connect with their AAD credentials.
Once the user clicks on the link, they will be presented with the Citrix Cloud login.
The user will need to click on “Sign in with my company credentials.”
The user will need to enter the company name assigned at the configuration of AAD Connect.
If you are using MFA with Office 365 or another provider, you will have needed to setup your MFA app / other methods of verification.
After completing login, user will be presented Director and be able to continue duties as assigned by roles.
Links to other articles in the series:
Part 1 of migration series Setting Up Cloud SDK And Authentication Profiles: Part 1
Part 2 of migration series Changing Custom PublishedName Property: Part 2
Part 3 of migration series Migrating Citrix Daily User Report: Part 3
Leave a Reply