ADC Admin Guide PDF
ADC Admin Guide PDF
Contents
Citrix Active Directory Connector ................................................................................. 1
Managing Users ............................................................................................................ 2
Provisioning ................................................................................................................... 2
Alternate Provisioning Solution ..................................................................................... 2
Install the Citrix Active Directory Connector ............................................................... 3
Update the Citrix Active Directory Connector ............................................................. 4
Uninstall the Citrix Active Directory Connector .......................................................... 5
Citrix Active Directory Connector requirements ......................................................... 6
Citrix Accounts Requirements ....................................................................................... 6
Active Directory Requirements ...................................................................................... 6
System Requirements ................................................................................................... 6
Firewall Settings ........................................................................................................ 6
Attributes used to access the Active Directory .......................................................... 7
Acquire a consumerKey for the ADC............................................................................ 8
Launch the Active Directory Connector ....................................................................... 9
Launching the ADC ....................................................................................................... 9
Connect Active Directory and Citrix Accounts .......................................................... 10
Assign Active Directory groups .................................................................................. 11
Edit or delete a group assignment ........................................................................... 12
Manage ADC provisioning options ............................................................................. 13
Modify ADC provisioning options ................................................................................ 13
Modifying email Accounts for Testing ...................................................................... 13
Provision Users............................................................................................................. 14
Start the ADC .............................................................................................................. 16
1. Match valid Active Directory Users ......................................................................... 16
2. Provision all matched and new Active Directory users ........................................... 18
3. Review and modify Citrix-only users ....................................................................... 19
Run the ADC .................................................................................................................. 20
Run the ADC ............................................................................................................... 20
Adding users ............................................................................................................... 21
Deleting users ............................................................................................................. 21
ii
Implementation of the Citrix Active Directory Connector consists of installing the ADC, connecting the
ADC to specific Active Directory groups, and running the ADC. This queries the Active Directory groups
and your corporate Citrix account. All identified users are displayed in a User page.
Managing Users
Most customers have an existing Citrix account with a set of current users. The ADC User page provides
a procedure administrators can follow to manage the different user groups in a manner appropriate to
their organization. The procedure addresses and clears the simplest (and usually the largest number of)
cases first, resulting in a refined list of user cases that need additional attention. The process to provision
for the first time, or for newly added Active Directory groups, is:
Start the ADC - This queries the linked Active Directory groups and your Citrix account and displays
all the users in the ADC Users page. You can now work with your users in three basic steps.
1. Recognize existing Citrix account holders to avoid reprovisioning. To do this, use Automatic
matching to link Active Directory users to existing Citrix accounts where the emails are identical. Then
manually match accounts where the same user has different credentials for the two accounts.
(Alternately, you can delete the Citrix account and reprovision the user under their Active Directory
credentials.)
2. Provision all new Active Directory users. This clears the Active Directory queue (unmatched AD
users) of all but users with incorrect Active Directory data. Fix the data and these users will be
provisioned automatically the next time you start the ADC.
3. Finally, review and correct as needed users with Citrix accounts and no Active Directory
account. These may be Unix or Mac users, contractors, or other special cases. Create equivalent
Active Directory accounts if you want to ensure all Citrix account management can be done by
managing your Active Directory groups.
Provisioning
Users provisioned through the ADC receive an enrollment email. The email directs them to login, where
they will change their password, and then have access to a Citrix account. They can login on their
Windows desktop, through a browser, or on a mobile device. They can also access their accounts
through extensions for applications such as Outlook, Salesforce and Google Calendar.
For small changes of one to several users, the provisioning or deprovisioning can occur in a matter of
minutes. If you are provisioning hundreds or thousands of users, a general rule of thumb for a average
system is 1000 provisioning requests per hour.
Any changes to users in the provisioned Active Directory groups or users is reflected in the ADC and
passed to the Citrix Admin Portal. Provisioning is fully automated and your users have full access to Citrix
SaaS business tools.
Under normal operations, the ADC polls the Active Directory at the interval you set (see Managing Users
after Implementation).
2. Run the Citrix Active Directory Connector Setup.exe file. The InstallShield Wizard will guide you
through the installation. Click Next on each screen to continue.
3. Click Install > Finish to exit the wizard and complete the installation.
4. Click the new desktop shortcut
1. To verify your current installed version, open the Operations tab and check the version number.
3. Once the Active Directory Connector Administration application has been uninstalled, click Finish to
exit the installer.
An Active Directory Service account. The account must have read access and the password
should not expire.
An Active Directory forest with Windows Server 2003 functionality.
System Requirements
Operating System: Windows Server 2008 R2 (not necessarily a domain controller)
Software: Microsoft .NET Framework 4.5 update (included in the ADC installer if needed).
Memory: 2GB RAM or greater recommended
Available disk space: Minimum 200MB (depending on log level and storage period)
Display: Minimum 1024 x 768
Internet connection:The ADC connects to developer.citrixonline.com via the Internet
Firewall Settings
Firewall settings should be configured as follows:
Use Case
<source server>
<target server>:<port>
pi.citrixonline.com:443
Active Directory Domain Controller:389 (LDAP)
Active Directory Domain Controller:636 (LDAPS)
Active Directory Domain Controller:3268 (LDAP)
Active Directory Domain Controller:3269 (LDAPS)
SMTP server : 25
SMTP server : 465
Group
User
X
X
X
X
X
X
X
mail
name
X
userAccountControl
aAMAccountName
sn
givenName
accountExpires
X
X
X
X
X
You can access the MyApps page at any time from the Home page (developer.citrixonline.com): click
Building with access to a key.
3. All new developer accounts are Test accounts by default and lack adequate permissions to manage
users and provisioning. Set your developer account to Production status by emailing [email protected] and requesting that your account be changed to Production for the Active
Directory Connector.
Include the following information:
consumerKey
Application Name: AD Connector
App Product: GoToMeeting
Application URL: your companys home page
Number of anticipated provisioned accounts
10
4. In the Create Assignment dialog, choose the Citrix product to provision (GoToMeeting,
GoToWebinar, GoToTraining or OpenVoice). GoToWebinar and GoToTraining accounts automatically
include access to GoToMeeting. Only one product can be selected for each assignment; to provision
group members with multiple products, create additional assignments for the same group.
5. Click OK. Your new group assignment appears under Active Directory groups with assigned
products.
6. Click Apply changes when finished.
11
12
13
Provision Users
Provisioning users in the Citrix Active Directory Connector (ADC) for the first time, or when you add
groups of users, allows for review of the user accounts before you provision. This procedure gives you
the opportunity to review your users, fix any errors, and provision only when you're ready. After this,
provisioning is automatic, assuming the Active Directory data values are valid. Also make sure you have
Production status for your developer account before proceeding.
For a detailed overview of this process, see Managing Users in the ADC Overview.
The process to provision for the first time, or for newly added Active Directory groups, is:
Start the ADC - This queries the linked Active Directory groups and your Citrix account and displays
all the users in the ADC Users page. You can now work with your users in three basic steps.
1. Recognize existing Citrix account holders to avoid reprovisioning. To do this, use Automatic
matching to link Active Directory users to existing Citrix accounts where the emails are identical. Then
manually match accounts where the same user has different credentials for the two accounts.
(Alternately, you can delete the Citrix account and reprovision the user under their Active Directory
credentials.)
2. Provision all new Active Directory users. This clears the Active Directory queue (unmatched AD
users) of all but users with incorrect Active Directory data. Fix the data and these users will be
provisioned automatically the next time you start the ADC.
3. Finally, review and correct as needed users with Citrix accounts and no Active Directory
account. These may be Unix or Mac users, contractors, or other special cases. Create equivalent
Active Directory accounts if you want to ensure all Citrix account management can be done by
managing your Active Directory groups.
14
Users provisioned through the ADC receive an enrollment email. They login to change their password,
and they then have access to a Citrix account. They can login on their Windows desktop, through a
browser, or on a mobile device. They can also access their accounts through extensions for applications
such as Outlook, SalesForce and Google Calendar.
For small changes of one to several users, the provisioning or deprovisioning can occur in a matter of
minutes. If you are provisioning hundreds or thousands of users, a general rule of thumb for a average
system is 1000 provisioning requests per hour.
Any changes to users in the provisioned Active Directory groups or users is reflected in the ADC and
passed to the Citrix Admin Portal. Provisioning is fully automated and your users have full access to Citrix
SaaS business tools.
15
Once the queries run, all linked Active Directory users new to the ADC display in the Unmatched Active
Directory users pane on the Users tab. All existing Citrix users on your corporate account display in the
Unmatched Citrix users pane on the Users tab.
16
Review the two unmatched panes. Look for Active Directory users who match users with Citrix accounts,
but who were not identified during automatic matching. These users have different email addresses for
the two accounts.
You have two choices for how to manage these users. You can require identical email credentials (steps
3 & 4) or match the two accounts (step 5).
3. To force identical emails, delete the Citrix account. Right-click the user from the Unmatched Citrix
users list, and select Delete User. This removes the user and any product provisioning for the user
from the ADC and the Citrix product portals.
4. Click Apply changes. You'll see a Provisioning successful message, and the status(es) will no
longer say Pending. If you deactivate edit mode before applying changes, any unsaved changes will
be lost.
Or match the two accounts:
17
5. To match two accounts, select each pair of matching accounts - one in Unmatched AD users and
one in Unmatched Citrix users - and click Match Selected.
Unmatching accounts
6. If for any reason you decide to unmatch a matched user, select the desired user(s) in the Matched
users table and click Revoke selected user matchings. The entries return to the Unmatched Active
Directory users and Unmatched Citrix users tables.
7. Click Apply changes.
You will be alerted that you are in Edit mode. Click Deactivate edit mode to begin provisioning.
IMPORTANT: Provisioning may take time. Assume approximately 1 hour per 1000 users.
When the provisioning step is completed, all valid Active Directory users - new Citrix users and those
with a pre-existing Citrix account - are all in the Matched users pane.
If you have unmatched users remaining in either pane, continue on to the next section. However, if you
do have users in the Unmatched AD users pane at this point, these should now be only users with invalid
Active Directory data.
10. Correct the errors in the Active Directory. For a list of the data values the ADC queries, see
ADC Requirements.
11. After a few minutes, the users will refresh in the Unmatched AD users pane. You can provision
them, or match them with Citrix accounts.
All users should be cleared from the Unmatched AD users pane at this point.
18
19
3. Set the Active Directory polling time(in seconds). The default polling time is set to 15 seconds
full range is 0 to 30,000 seconds. Alerts (see Manage ADC Provisioning) occur based on events
between polls. Set polling periods and event thresholds accordingly. Assume roughly one event every
half second or 500 milliseconds.
20
Adding users
Adding a new user consists of including them in the proper Active Directory group(s).
1. Add users to the appropriate Active Directory group or groups for Citrix provisioning.
2. Optional: In the ADC, verify that the new user appears in the User page of the ADC, typically in the
Unmatched AD users pane.The users will be automatically provisioned with the Citrix SaaS products
defined for their groups.
Deleting users
Removing a user consists of removing them from your Active Directory and then making sure they are
automatically removed in the ADC.
1. Delete the user in Active Directory. They are automatically deleted from the provisioning groups in
Active Directory.
2. The user is also automatically deleted in the Citrix Active Directory Connector. It is a good idea to
verify that the deleted user is removed. If not, the user may be unmatched to an Active Directory
group. In that case:
3. Select the Users tab in ADC.
4. Click Activate edit mode and wait until you see Edit mode: Active in the bottom-right corner.
7. Click Deactivate edit mode and wait until you see Edit mode: Inactive.
21
22
23
SMTP(S) server (to send status information) -- SMTP service account (user/password) for
sending emails (only if it's necessary for your SMTP server)
SSL certificate -- May be required to connect to the SMTP server and Domain Controller securely
(optional)
24
6. Fill out the From, To, Subject, Text, Attachment and SMTP server fields and click Next.
7. Click Finish to save your new task.
Specify when the notification email is sent using the Windows Task
Scheduler
1. Open the Windows Task Scheduler (Start > All Programs > Administrative Tools > Task
Scheduler).
2. In the left navigation, select Task Scheduler Library > Event Viewer Tasks.
3. Right-click the new task created in the prior set of steps and select Properties.
4. On the General tab, click Run with highest privileges check box.
5. On the Triggers tab, select On an event and click Edit. Enable the Delay task for check box and
enter 2 minutes and click OK. If you do not add a delay, new events that arrive will trigger additional
actions before the actual action is completed.
6. On the Actions tab, review the actions that will occur when your task starts. The following actions
are required; you can add, edit or delete as needed. Click OK when finished.
Stop task (disable_task.bat) schtasks /Change /TN "Event Viewer
Tasks\ADCSLog_Error" /DISABLE
Get error (error_status.bat) del %temp%\error_status.txt wevtutil qe ADCSLog
/q:"*[System[Provider[@Name='AD Conn'] and (Level=2) and
TimeCreated[timediff(@SystemTime) <= 120000]]]" /f:text /rd:true >
C:\temp\error_status.txt
Enable task (enable_task.bat) schtasks /Change /TN "Event Viewer
Tasks\ADCSLog_Error" /ENABLE
25
The following events represent examples of error messages and what they mean if they're reported in the
Active Directory Connector service.
Event[0]: Log Name: ADCSLog Source: AD Conn Event[3]: Log Name: ADCSLog Source: AD Conn
Date: 2013-02-28T16:11:59.000 Event ID: 0 Date: 2013-02-28T16:11:58.000 Event ID: 0
Task: N/A Level: Error Opcode: Info
Task: N/A Level: Error Opcode: Info
Keyword: Classic User: N/A User Name: N/A Keyword: Classic User: N/A User Name: N/A
Computer: de-pc-devComputer: de-pc-dev018.ad.corp.expertcity.com Description:
018.ad.corp.expertcity.com Description:
2013-02-28 16:11:59,502 [WorkOrderThread] 2013-02-28 16:11:58,257 [WorkOrderThread]
ERROR - Writing OSD data: Organizer
ERROR - Writing OSD data: Server response
[email protected] was not created exception: {StatusCode": "409",
"StatusCodeAsString": "Conflict",
"Response": "The remote server returned an
error: (409) Conflict."}
Event[1]: Log Name: ADCSLog Source: AD Conn Event[4]: Log Name: ADCSLog Source: AD Conn
Date: 2013-02-28T16:11:59.000 Event ID: 0 Date: 2013-02-28T16:11:56.000 Event ID: 0
Task: N/A Level: Error Opcode: Info
Task: N/A Level: Error Opcode: Info
Keyword: Classic User: N/A User Name: N/A Keyword: Classic User: N/A User Name: N/A
Computer: de-pc-devComputer: de-pc-dev018.ad.corp.expertcity.com Description:
018.ad.corp.expertcity.com Description:
2013-02-28 16:11:59,499 [WorkOrderThread] 2013-02-28 16:11:56,966 [WorkOrderThread]
ERROR - Writing OSD data: Server response ERROR - Writing OSD data: Organizer
exception: {"StatusCode": "409",
[email protected] was not
"StatusCodeAsString": "Conflict",
created
"Response": "The remote server returned an
error: (409) Conflict."}
Log Name: ADCSLog Source: AD Conn Date:
Event[5]: Log Name: ADCSLog Source: AD Conn
2013-02-28T16:11:58.000 Event ID: 0 Task: Date: 2013-02-28T16:11:56.000 Event ID: 0
N/A Level: Error Opcode: Info Keyword:
Task: N/A Level: Error Opcode: Info
Classic User: N/A User Name: N/A Computer: Keyword: Classic User: N/A User Name: N/A
de-pc-dev-018.ad.corp.expertcity.com
Computer: de-pc-devDescription: 2013-02-28 16:11:58,260
018.ad.corp.expertcity.com Description:
[WorkOrderThread] ERROR - Writing OSD data: 2013-02-28 16:11:56,963 [WorkOrderThread]
Organizer [email protected] was ERROR - Writing OSD data: Server response
exception: {"StatusCode": "409",
not created
"StatusCodeAsString": "Conflict",
"Response": "The remote server
26
SMTP(S) server (to send status information) -- SMTP service account (user/password) for
sending emails (only if it's necessary for your SMTP server)
SSL certificate -- May be required to connect to the SMTP server and Domain Controller securely
(optional)
27
5. On the Actions tab, review the actions that will occur when your task starts. The following action is
required; you can add, edit or delete as needed. Click OK when finished.
Filter event log and write file (daily_status.bat) del
%temp%\daily_status.txt wevtutil qe ADCSLog /q:"*[System[Provider[@Name='AD
Conn'] and TimeCreated[timediff(@SystemTime) <= 86400000]]]" /f:text
/rd:true > C:\temp\daily_status.txt
28