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-6606: No prefix option needed in copynested group

Authentication Service ,  

8 April,16 at 12:08 PM

Problem:

Is there a way to avoid inserting a prefix when using the copynested group utility (CopyGroupNested.exe) so that the group name can be identical to the one in the Trusted AD Forest? Currently if the prefix is left blank the script fails to run. 

Cause: 

The copynested group utility was originally intended to be used with a prefix so it will produce an error if the prefix switch is left blank. 

Resolution:

Starting in version 5.3.0 (Server Suite 2016) the prefix switch can now be left empty. 


Note:
You must add "" to specify no prefix
This must be ran using CMD and not powershell

Example:
copygroupnested.exe source.domain source_group target.domain "" 

 


 

Related Articles

 articleKB-6041: How to show current license type in use by adclient 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-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-6038: How to specify the license type to use when joining the server to AD using adjoin? articleKB-3925: How to add Centrify parameter to a group policy articleKB-6050: How to configure a group for automatic Kerberos Credentials for infinite renewal? articleKB-6044: How to configure users for automatic Kerberos Credentials for infinite renewal even after users have logged out?