Loading
search-img

Autoconnect Rules

Skip Feed

  1. LaurenMcEleney asked a question.

    July 2, 2019 at 7:00 AM
    Getting autoconnect site rules to show in SLM

    Hello! 

    I've created lots of autoconnect rules in the SMACC to match computers to IP addresses so I can then report better on which sites have what devices that day. 

    I have added in lots of rules and they are showing on the preview as no conflicts but it's not assigning the computers to them in SLM.

    Do I need to add something into the agent config? If so, what? 

    Any help would be appreciated! I did look at other questions that were similar on here but I was unclear as to my answer! 

    Thank you 

    Expand Post
    • 3 answers
    • 142 views

    • Portal User

      If the autoconnect rules work they should show up and align to whatever you setup. Are you using IP to put them into specific Organization name, location?  How is your Organization setup in relation to the rules? 

  2. 1 of 14

    • Mike Rossouw (Flexera Software)

      Hi Marco, The rule (Rule Type: Computer/Mobile Device) and (Rule Identifier: According to Primary User) combination is generally used when User-based rules are predefined and most often in covering development/test environments. Given how dynamic these can be, it saves you a bunch of time chasing down development or test computers that as you know can be built, destroyed and rebuilt any number of times in a single day depending on the environment they're used. That is of course if your organisation tracks development computers.   For example: If Joe Bloggs is a developer (one of ten developers and works in the London office) and uses 10 computers for his development environments, it is easier and makes more sense (if your developers use standard naming for users names) to create a user rule for the developer user rather than create 10 or more computer rules that are out of date the minute you create them.   Then, to automatically link the London development computers to the London office you can create the computer rule with the identifier of 'According to Primary User' In these circumstances use of a common username format is advisable as well, for example, 'Dev_username' using 'Dev_% in the User rule would then allow you to have multiple developers in the London office and only need to create one rule. I hope this makes sense Mike
      Expand Post

  3. alexander_bu asked a question.

    September 21, 2018 at 7:00 AM
    Define Auto Connect Rule via SQL
    Hi all, Does anyone have experience whether one could define Auto Connect Rules via SQL directly rather than via SMACC? Let's say I have created a very basic rule, stating that all computers that have %WKS% as their name will be connected with a specific OU. The SQL statement then looks like this: ComputerID IN (SELECT c.ComputerID FROM tblComputer c WHERE c.CID = @CID AND c.HostName LIKE '%WKS%') Plus, the full dataset for the rule is fairly easily structured. So theroretically I should be able to create a rule directly in SQL. Why would I want to do that? Well, the Auto Connect Rules I can set in SMACC have a single major flaw: I can only set LIKE-conditions. Let's stick with the example above. My computer names are structured like             [SITE]-[NAME]-[NUMBER]. While all the clients carry 'WKS' as [NAME], there is no such standard scheme for servers. For distribution of license costs I want my clients to be assigned to OUs based on their primary user. All the other computers shall be assigned to my "standard" Prod OU. The next logical step would be to create a rule like this: ComputerID IN (SELECT c.ComputerID FROM tblComputer c WHERE c.CID = @CID AND c.HostName NOT LIKE '%WKS%') I tried exactly this, but it doesn't work properly, and I don't know why. As a result both WKS-machines as well as non-WKS-machines are connected to my Prod OU. So the allocation is inconsistent. I wonder: Are their any interdependencies between the rule in SMACC and the SQL statement if they do not match contentwise (at least on the surface). And what exactly is the  CID parameter? I don't quite get it. If anyone has a hint on that, please let me know. Plus, ‌ - fyi Best,   Alex
    Expand Post
    • 2 answers
    • 197 views

    • Oliver Berger (Flexera Software)

      Hi  ?, well works for me. CID is the customerID. In Enterprise Editions, it's always 1, in Service Provider Editions it can vary. Make sure, - "Disable Auto Editing" is off, - you never ever use the SMACC again for touching rules or organisations - it will change and apply them when clicking okay, including reseting the unsupported "not like". - if you want to test your rule, you can use the "exec orgautocunnectrulesapply Procedure" afterwards. And if you want to move the Computers using SQL, why don't you update tblcomputerinfo.orgchecksum inside a Custom Stored Procedure, attached to the Data Update Job directly? Cheers Oliver.
      Expand Post

  4. SamuelBaughan asked a question.

    June 1, 2018 at 7:00 AM
    Unlinked auto-connect rule definitions
    Dear Community, Recently I was tidying up our auto-connect rules in our SMACC and I found that we have a few dozens of Rule Definitions that are not linked to any Rule. I think they might be remains of Rules that we deleted in the past as we created and updated our Organization structure in the SMACC. The rules are in the table tblOrgAutoConnectRule and their definitions are in tblOrgAutoConnectRuleDefinitions. The 2 tables are linked through the RuleID field. So if I run this query: SELECT * FROM tblOrgAutoConnectRuleDefinitions r LEFT OUTER JOIN tblOrgAutoConnectRule rd ON r.RuleID = rd.RuleID WHERE rd.RuleID IS I should find nothing because each rule definition should have a rule associated to it. But the query brings up over 30 rules. Is there a reason why they are left behind? Can I delete those rules? Thanks for your advice.
    Expand Post
    • 2 answers
    • 138 views

    • Community Manager (Flexera Software)

      Hi Samuel, thank you for raising this! I would not recommend to make any changes on a database level, unless you fully know all dependencies. This is something, that can be covered by either our Snow Support or by Professional Services in your region. I would suggest you to open a ticket via the  Support Portal  and to contact your account manager, if you would like this to be investigated properly. Please let me know, if you need any assistance. /marcel
      Expand Post

  5. 1 of 15

    • Portal User

      There are several strings going on with this being asked, somewhat answered and which always leads to more questions.  But the short answer to your question is, you add a wildcard for a range, in your example it would look like this: 192.168.%. the will grad the whole subnet range.  I would like to see subnet range as an option and have ask SNOW via a feature request ticket for it. So we'll see.  Hope this helps. 

  6. Portal User

    March 6, 2018 at 8:00 AM

    How do you use autoconnect rules?

     

    For those using autoconnect rules in order to get devices into an Organization structure, how are you using these rules? In other words, what have you found are the best ones? Device Name, IP, ? 

    And for the future are there any missing you wish were added? IP Subnet, connector rules (assigned based on SIC connector used)?

    This is just a discussion to get the creative juices flowing. 

    Thank you for any input. 

    Expand Post
    • 10 comments
    • 132 views
    1 of 10

    • Portal User

      Any ideas about an autoconnection rule by operative system?

  7. Portal User asked a question.

    March 2, 2018 at 8:00 AM
    More autoconnect rules?

    Here is another question regarding autoconnect rules, specifically IP address. I have started going through the list of devices that do not fall into an Organization because of incorrect PC name, etc. That is our main autoconnect rule, device naming, so I have started adding the IP to the autoconnect rules for specific sites to pick up those stragglers that are not named correctly.  

    My question is related to the IP address the client is showing. For example I added this IP as an autoconnect rule for a specific site, 10.1.101.%. A lot have multiple IP's (must be because of multiple network adapters), show they show up like this in the reports, 0.0.0.0,0.0.0.0,0.0.0.0,169.254.157.205,0.0.0.0,10.1.100.187. This is one I want to show up in that site based on 10.1.101.%, but it appears it may only look at the first IP and move on? In this case the real IP is 5th in the string. 

    Any way around this? Or do I have another issue as to why this is not working? 

    BTW: Autoconnect rule with this IP address works for other machines with single IP for this wildcard. 

    thank  you. 

    Expand Post
    • 2 answers
    • 135 views

    • Oliver Berger (Flexera Software)

      Hi Mark, yes, that's how it currently works. The workaround is to use also a '%' at the beginning. It is just tsql searching a string. Of course, due to the limitations of the mask, you could not separate between i.e.192.%.%.% and 182.% .%.% if you can only enter %82.%.%%. and %10.%.%.% could also be 210 or 110. As usual: Feature Requests welcome. Hope that helps. Best Oliver

  8. NGA10 asked a question.

    December 12, 2017 at 8:00 AM
    Auto Connect Rules - According to primary user
    Hi folks, Most of our sites have one business unit per site, so we are able to assign an endpoint to a business unit based on the computer name which starts with a site code. However we have a small number of sites where there are multiple business units on that site which we wish to account for separately. We have looked at computer names, IP ranges etc. as ways of filtering the business units but it does not produce the desired level of accuracy. We are therefore looking to assign a computer endpoint to a business unit based on their primary (most frequent) user. I have assigned users to the business unit using auto connect rules on a per-user basis. I have also selected within that business unit an auto connect rule as below. The documentation which I can find on auto connect rules does not explain the behaviour of this rule. My hope was that, for this business unit, it would assign computers to the business unit based on users who belong to that business unit being the primary/most frequent user. However that has not happened. Is there anyone on the forum who has done this? Thanks and regards, Nick.
    Expand Post
    • 3 answers
    • 139 views
    1 of 3

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
10 Posts

Related Topics

    +1.800.374.4353
    CONTACT SALES SUPPORT HUB FLEXERA REVENERA
    © 2026 Flexera. All rights reserved.
    Privacy policy Terms and conditions Revenera Community Help
    Loading
    Autoconnect Rules | Flexera