Hello,
one of our customers has decided to create a new OU in Active Directory without telling us.
They've placed several users into this new AD and are now complaining that their LDAP login into Portal is no longer working.
We are only searching a single OU which is on the same level as the newly-created OU - our config entry is as follows:
<ServerObject>LDAP://C-CAP-DC-02.corpad.corp.edinburgh.gov.uk/OU=User Accounts,OU=Corp Accounts,DC=corpad,DC=corp,DC=edinburgh,DC=gov,DC=uk</ServerObject>
Can somebody recommend the best solution to this problem?
The possible options I can see are:
- search the whole AD domain (which would be inefficient)
- create a separate TPS folder and web application with the new AD OU in the config file (a bit of work and a new URL to deploy)
- ask the customer to move the OU under the existing (searched) OU (not sure of the implications or their willingness to do so)
Any help would be greatly apprecviated,
thanks,
Keiron.