Configuring AD Sync Settings in Pure Access

1. Log into your Pure Access tenant.
2. Create User Groups which will be populated with user profiles from AD.
3. Navigate to Settings > Active Directory
4. Set sync times under General Configuration.
5. Map AD fields to Pure Access fields under User Field Mapping (you may need to refresh the fields for them to appear).
6. Map AD groups to Pure Access user groups under User Group Field Mapping (you may need to refresh the groups for them to appear).
7. Once everything is set up properly, click FULL SYNC.
   • Please note that this may take some time to complete if this is the first time syncing. If there doesn’t appear to be activity after 10 minutes, refresh the page and try to sync again.
   • If the above did not work, restart the Isonas AD Connect Windows service and try again.

*Still need help? Please send the adpod.log file (located in the same directory that AD Connect is installed) and a description of your issue to our support team for review.

FAQ

1. Changing Group Names in Active Directory
   1. Q – If the group names are updated in Active Directory, will the sync pick up these name changes, and will mapping the new names be needed in Pure Access Cloud?
   2. A – The AD Group names are synced and stored to Pure Access Cloud (PAC) based upon their GUID, which is a unique non-changing identifier in Active Directory. If the AD Group name is updated in Active Directory, this name change will automatically update within PAC. Remapping will not be required as the names will flow and update directly without extra intervention.
2. Changing Users’ Names in Active Directory
   1. Q – If user names are updated in Active Directory, will the sync pick up these name changes, and will mapping the new names be needed in Pure Access Cloud?
   2. A – The AD user names are synced and stored to Pure Access Cloud (PAC) based upon their GUID, which is a unique non-changing identifier in Active Directory. If a user’s name is updated in Active Directory, this name change will automatically update within PAC. Remapping will not be required as the names will flow and update directly without extra intervention.