Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-4752: ZPA is no longer provisioning AD users into Zone after some or all existing zone users were removed

Authentication Service ,  

20 August,19 at 03:51 PM

Applies to:

All versions of Centrify Zone Provisioning agent.

Problem:

ZPA is no longer provisioning AD users into zone.

Background:

Previous to issue, some or all zone profiles were deleted from the zone in question.

ZPA log shows the following:

[2014-09-10 16:54:17.743 -0400]Centrify.Provisioning.Agent.exe[4848,6]
Warning: ProvisioningWorker.LogEvent: Failure:
[2014-09-10 16:54:17.743 -0400] Centrify.Provisioning.Agent.exe[4848,6]
Warning: ProvisioningWorker.LogEvent: testlab.net/Zone1
[2014-09-10 16:54:17.743 -0400] Centrify.Provisioning.Agent.exe[4848,6]
Warning: ProvisioningWorker.LogEvent: - Failed to provision user
aduser1@testlab.net. Error: The UNIX name is already in use.


Resolution:

This issue stems from leftover Service Connection Point (SCP) artifacts in AD from the previous
provisioned users for this zone.

Steps to resolve as authorized administrator:

1. Launch Centrify Access Manager 

2. Right click the zone in question and select properties

3. Take note of the Location listed on the General tab

4. As a precaution please open "authentication" then right click Users and select Export to take a backup of the
existing users and their Unix Profiles.

5. Start Active Directory users and Computers (ADUC)

6. Drill down to the location from step #3

7. Expand the zone container and open the "users" Container

8. The conflicting Service Connection Points should be removed from this container to allow ZPA to be able
to provision them again.

 

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.

Related Articles

 articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-6041: How to show current license type in use by adclient articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-6056: How to report the group policy settings that are in effect for the local computer? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0) articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? article[HOWTO] Setup the Zone Provisioning Agent articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out?