Home Asset Management

Organizational Unit Change

Aybars_KutluturkAybars_Kutluturk Member IT Monkey ✭

Some of our Incident Resolvers and Service Request Analysts's organizational unit was changed yesterday on Active Directory. They can't enter, resolve, complete any of the records right now.

Answers

  • Geoff_RossGeoff_Ross Cireson Consultant O.G.

    Hi Aybars,

    You'll need to rerun your AD Connectors, (check the user's are still in scope of these because they can and should be targeted at specific OUs).

    If you are using the Cireson Portal, you will also need to restart the CacheBuilder service and recycle the App Pool.

    Geoff

  • Aybars_KutluturkAybars_Kutluturk Member IT Monkey ✭

    Hi Geoff,

    After my question I moved one of operator to old OU and rerun the AD Connector, restart the cachebuilder without recycling the App Pool. Now he can do everything like befor but another operator who is in new OU still can't do anything. Do you have any idea for this issue?

  • Justin_WorkmanJustin_Workman Cireson Support Super IT Monkey ✭✭✭✭✭

    @Aybars_Kutluturk - Sometimes running the AD connector after an OU move still doesn't update the CI's distinguishedName. You can manually update the distinguishedName property on the CI based on what distinguishedName is listed in AD(or try a "full sync" of the AD connector). Once that's done, a restart of the cachebuilder should fix the people in the new OU.

Sign In or Register to comment.