Introduction

A Unit either exists in the global part of a Configuration Management Point, or inside a business unit.

If it is located inside a business unit, it will be limited to those packages and MDM profiles which are members of that same business unit.

If it exists in the global part of a Configuration Management Point, it may be linked to packages and MDM profiles, regardless of which business units they have been assigned to.

Regarding group membership, a unit inside a business unit may be linked to both local groups inside that business unit and global groups.

There are advantages to both types of membership.

Using local groups will help keep the overview of units in the organization for that specific business unit, without the distraction of units outside.
Global groups might be the better option in situations, where you would otherwise have very similar groups inside several of your business units. An example of such a situation could be a requirement, that all computers with a specific operating system, must install a certain set of packages across the entire organization. Instead of creating multiple local groups with the same configuration, a single global dynamic group targeting those computers based on OS would accomplish the task. You would only have to link the required packages to this one group and make sure they are available to the business units.

Usually, a combination of local and global groups will be advisable, but with careful thoughts on when to use what in order to both accomplish optimal overview and reduce configuration and maintenance.

If you want to...	You can...
Learn more about linking units to business units	Link unit to Business Unit
Learn more about units in Configuration Management	Working with Users
Learn more about groups and business units	Groups and Business Units

Browser not supported