AnsweredAssumed Answered

How to create a huge number of auto connect rules?

Question asked by svenbauersfeld on Nov 8, 2017
Latest reply on Nov 13, 2017 by svenbauersfeld

Like • Show 0 Likes0
Comment • 4

Hi All,

We do have a pretty complex organization structure with several level:

Root
Legal entity
Division
Business Unit
Department
Team

Based on LDAP data users will be assigned to teams automatically.

(Client) Computers will be assigned based on their primary user via auto connect rules which allows a very detailed tracking of license consumption.

As we have hundreds of teams and auto connect rules cannot be inherited we are facing the challenge of creating a huge number of auto connect rules. It is more or less impossible to do this manually via SMACC.

Does anybody have experience with creating auto connect rules automatically (e.g. via SQL scripts)?

Your support is greatly appreciated.

Thanks,

Sven

No one else has this question

Outcomes

jonas.nilsson

Nov 9, 2017 4:54 AM

I don't think there is a silver bullet to your problem. As the number and complexity of Auto Connect Rules increases, the value you get out of it decreases. I would suggest one or two other alternatives:

1: Create multiple site ids - that is multiple agent configurations. You will still have a large number of Auto Connect Rules, but you move the complexity and responsibility away from SMACC to the workstation management Group.

2: Ignore Auto Connect Rules altogether and instead manage organizational owner by importing/updating computers.

Or manage ownership outside of Snow in Excel. You unfortunately loose the automation aspect.

1 person found this helpful

Actions

mark.lillywhite

Nov 12, 2017 4:00 AM

Hi Sven,

Can you ask your snow presales / Consulting team in Germany about this? I know there is a services led (ie not free of charge) solution to tackle the levels of complexity you are talking about in the ou structure.

I would just ask that you check the complexity is necessary - in snow typically the OU structure is there to support licensing and often custom fields are used to tag assets with certain values (eg service owner, asset function etc) to drive other reports and groupings

Actions

Oliver.Berger

@ mark.lillywhite on Nov 13, 2017 10:03 AM

Hi Sven,

as Mark mentioned, we have some experience here. Adding this as a one-shot for all Organisations and setting the computer rule "according to primary User" is not that complex.

Adding a procedure to the data update job, to add new Rules to new Organizations regularly would be a little more tricky.

So get in contact to your partner manager, to get this on track.

Cheers

1 person found this helpful

Actions

svenbauersfeld @ Oliver.Berger on Nov 13, 2017 2:27 PM

Hi All & Oliver,

Many thanks for your suggestions, I really appreciate the quick responses!

As proposed by Oliver I'll reach out to the German team.

Thanks

Sven

Actions

4 Replies

jonas.nilsson Nov 9, 2017 4:54 AM
Mark Correct
Correct Answer
I don't think there is a silver bullet to your problem. As the number and complexity of Auto Connect Rules increases, the value you get out of it decreases. I would suggest one or two other alternatives:

1: Create multiple site ids - that is multiple agent configurations. You will still have a large number of Auto Connect Rules, but you move the complexity and responsibility away from SMACC to the workstation management Group.
2: Ignore Auto Connect Rules altogether and instead manage organizational owner by importing/updating computers.

Or manage ownership outside of Snow in Excel. You unfortunately loose the automation aspect.
1 person found this helpful
Like • Show 2 Likes2
Actions
mark.lillywhite Nov 12, 2017 4:00 AM
Mark Correct
Correct Answer
Hi Sven,

Can you ask your snow presales / Consulting team in Germany about this? I know there is a services led (ie not free of charge) solution to tackle the levels of complexity you are talking about in the ou structure.

I would just ask that you check the complexity is necessary - in snow typically the OU structure is there to support licensing and often custom fields are used to tag assets with certain values (eg service owner, asset function etc) to drive other reports and groupings
Like • Show 0 Likes0
Actions
- Oliver.Berger @ mark.lillywhite on Nov 13, 2017 10:03 AM
  Mark Correct
  Correct Answer
  Hi Sven,
  
  as Mark mentioned, we have some experience here. Adding this as a one-shot for all Organisations and setting the computer rule "according to primary User" is not that complex.
  Adding a procedure to the data update job, to add new Rules to new Organizations regularly would be a little more tricky.
  So get in contact to your partner manager, to get this on track.
  
  Cheers
  1 person found this helpful
  Like • Show 1 Like1
  Actions
  - svenbauersfeld @ Oliver.Berger on Nov 13, 2017 2:27 PM
    Mark Correct
    Correct Answer
    Hi All & Oliver,
    Many thanks for your suggestions, I really appreciate the quick responses!
    As proposed by Oliver I'll reach out to the German team.
    
    Thanks
    Sven
    Like • Show 0 Likes0
    Actions

How to create a huge number of auto connect rules?

Outcomes

Related Content

Recommended Content

Incoming Links