Loading
Use AD OU for location with Autoconnect Rules

I am trying to find one way to get devices into the correct SNOW Organization using an auto-connect rule from AD OU=sitecode.

 

I have not done anything with AD and SNOW, is it possible? Each device is in an OU container for its sitecode location.

 

The devices are supposed to be named using that sitecode as the first 7 characters of the device name, but some are not and cannot rename for one reason or another.

 

Can SNOW see where to get the AD OU=sitecode that device is in for the autoconnect rule?


  • Hi Mark

     

    Have you already added the following tag to your snowagent.config?

     

    <Query>

       <Key recursive="true">HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine</Key>

       <Value>Distinguished-Name</Value>

      </Query>

     

    If yes, the OU assignments are scanned from the registry of each client. These can then be further processed via the autoconnect rules.

    I hope I have understood your requirement correctly so far :)

     

    BR

    Lars

    Expand Post
  • I looked sat my machine and do see the Distinguished name string in there. But how would I grab the part of that I need?

     

    Site name is not correct for my machine but the USRRK1 in the DN is.

     

    image

    Expand Post
    • You have to put the above string in your snowagent.config between

       

      <registry>

      <Query>

         <Key recursive="true">HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine</key>.

         <Value>Distinguished-Name</Value>

        </Query>

      </registry>

       

      Once you have that you can do all sorts of nonsense in the autoconnect rules section of the rules :)

       

      Example

       

      image 

       

      Expand Post
      • Awesome, I am going to try that. Thank you very much for the tip.

      • Another question on the Key string. I got it to work as a test on one Org. But as I am adding to other Orgs nothing is showing up in preview.

         

        Question is:

         

        Is the string for the Key - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine\

        (this one has the ending \)

         

        or

         

        HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\Machine

        (this one doesn't have the \)

         

        When I look at the one that works it truncates the string on the window and I am unable to see what I typed.

         

        Thanks,

         

        Expand Post
  • Now that companies are abandoning local AD forests and going to Azure, is there a method similar using AutoConnect rules for user locations?

  • In my humble opinion, autoconnect rules are pretty unflexible and hard to maintain.

     

    I prefer to use a powershell script to get a list of all computers including the OU information and write this into a csv file on a daily base. Then use the SLM Import Tool to import the information automatically.

    Haven't had the request to do this with Azure AD though, but should be not rocket science.

    Expand Post

Related  Product Forums


                     â†’ Flexera One



                      â†’ Snow Atlas



                      â†’ FlexNet Manager



                      â†’ Snow License Manager



                       â†’ App Broker


       Need help finding an answer?


        Ask a Question →


Loading
Use AD OU for location with Autoconnect Rules