Autoconnect rule conflict

Loading

RickTalbot asked a question.

June 26, 2017 at 7:00 AM

Autoconnect rule conflict

When there is a conflict with autoconnect rules, which rule takes precedent?

I have an organizational structure that is location based - so Toronto, New York, etc.

But we I want to have 1 single TestDev organizational node for all test/dev machines, identified by naming convention.

This is causing a conflict as the computers could be grouped in both New York and TestDev.

Is there a way to specify which rule takes precedent, so that we can ensure that the TestDev rule overrides the others?

Software & License Management

Community Manager (Flexera Software)
9 years ago
Hi Rick, I believe which ever rule was created first takes precedence.
Expand Post
- RickTalbot
  9 years ago
  Hi Marc, I added the autoconnect rule, and it appears that all computers are following the new rule, which was added last. I'd be interested if you're able to reproduce this on your side. Thanks!
  Expand Post
  - Portal User
    9 years ago
    I was also under the impression it started at the top item of the list for priority. We use the PC naming as the first rule with the IP range as the second and it seems to get most lined up in the right organization.
    Expand Post

Related Product Forums

→ Flexera One

→ FlexNet Manager

→ Snow License Manager

Need help finding an answer?

Ask a Question →

Loading

Autoconnect rule conflict