Clone Exceptions does not work with 'Office' or 'physicalDeliveryOfficeName'. (NETIQKB43668)

fact
Directory and Resource Administrator 6.x

fact
Directory and Resource Administrator 7.x

symptom
CloneExceptions does not work with 'Office' or 'physicalDeliveryOfficeName'.

symptom

The 'Schema.mdb' file that is contained in the Software Development Kit (SDK) for Directory and Resource Administrator (DRA), lists the property name for the 'Office' to be 'physicalDeliveryOfficeName'.  Using this value with the CloneExceptions key in the registry does not keep the Office value from being copied from the source to the target user account.

cause
There are actually two properties that map to the Office field, physicalDeliveryOfficeName (AD property) and OfficeLocations (ADSI property).  When the UserCopy operation fetches the properties from the source user, it fetches both of these properties.

fix
The workaround is to add both physicalDeliveryOfficeName and OfficeLocations to the clone exceptions list.

note

Certain properties from the source/template user account can be configured to be ignored and not copied during a user clone operation.  See this article for more information:

NETIQKB3604 - "Can the properties cloned during any clone operations be customized?"

Formerly known as NETIQKB43668