Loading
  • Hi,

     

    I'd say you have two options that both require some scripting.

    1. Get the information from AD using a powershell script for example and write this into a csv file that will be imported into SLM. Performing an user import allows to create non-existing OUs.
    2. Add a custom procedure to DUJ and update the OU for all users there.

     

    In one of our customer environments we were able use a csv that is generated by another system anyway. We just copied this file into the configured import folder every night.

    Downturn of both versions is that OUs not longer used will remain in the system. Our customer occasionally deletes the entire organisation in SMACC as it will be rebuild with the next import anyway.

     

    Kind regards, Axel

    Expand Post
  • Hi Axel, thanks for quick answer! Could be a entry for the "ideas board": the "possibilty to assign the user to a SNOW Org level based on AD OUs. ;-) kr mathias

Loading
Has anybody experience with customizing the "users auto connect rules"?