Business Units target specific groups of devices that share an attribute such as location, device type, or connectivity. They use Rollout Processes to manage notifications and approvals and manage deployment. Each Business Unit can have its own unique settings and policies that apply to its member devices. These settings include rollouts, interaction settings, and more.
In addition, children of Business Units inherit settings from parent Business Units to reduce the administrative burden of managing settings across multiple units. OneSite Patch includes a Parent Business Unit for All Clients and Child Business Units that address most device grouping scenarios.
Related business units, including Child Business Units or Lab Business Units, provide another level of detail that administrators can use to further customize a patching environment.
Important
When adding Business Units to a Patching Strategy, make sure that the Patch Deployment Bot for that Strategy specifies the same Business Units.
In addition to identifying the devices to include in a Business Unit, you can also identify many aspects of patching for endpoints, such as rollout processes, maintenance windows, approvals, and more.
Business Unit objects use a parent-child hierarchy. A parent Business Unit may have multiple child Business Units, but a child Business Unit may have only one parent. The folder structure used in OneSite Patch shows the parent as the top-level folder and the child units as sub folders of a parent. This structure gives you the freedom to create patching hierarchies that match any endpoint landscape.
Tip
Child Business Units may only contain devices that the Parent Business Unit also manages. For example, if a Parent Business Unit has devices A, B, C, and D, and the Child Business Unit has devices C, D, E, and F, the resulting devices in the Child Business Unit include C and D only.
There is no functional difference between parent and child Business Units. The purpose of the parent/child hierarchy is to allow a child Business Unit to inherit settings from a Parent, which can simplify the creation of Business Units with both distinct and common requirements. An up-arrow with a blue background preceding a setting or process shows an inherited setting.
The hierarchical nature of Business Units allows a child Business Unit to inherit settings from its parent. An up-arrow with a blue background preceding a setting or process shows an inherited setting.
OneSite Patch accommodates an unlimited number of parent or top-level Business Units. Create many different Business Unit hierarchies based on details that model requirements and processes in your environment.
In OneSite Patch inheritance defaults to Enabled.
Important
The colors shown here are default color settings. If you change the Admin Portal theme settings to use different colors, your arrows and backgrounds might be different.
A white up-arrow with a blue background preceding a setting or process shows an inherited setting. Enabling inheritance disables the Browse button for the setting because you may not make any changes.
A black up-arrow with a white background preceding a setting or shows a disinherited setting. Disabling Inheritance enables the Browse button for the setting, which allows you to change the settings.
You can arrange the Business Unit view in hierarchies that meet the needs of your environment. Parent Business units pass attributes to child Business Units – sub-folders – so it is important to maintain those relationships where they exist.
In addition, when a device is part of multiple Business Units, the device inherits the settings of the highest priority Business Unit. This occurs even when the patch information comes from a Business Unit with different settings than the highest priority Business Unit.
In the Business Unit hierarchy shown in the OneSite Patch dashboard, the Business Unit at the top of the list has the lowest priority. When changing the priority of a Business Unit in the hierarchy, consider the following items:
-
Priority – Do the settings and desired state of the new priority Business Unit match your expectations for the moved Business Unit?
-
Membership – Are the devices in the moved Business Unit compatible with the new priority Business Unit?
-
Inheritance – Are the inheritance settings for the moved Business Unit still accurate in this new location?
-
Deployment Waves – Is the Business Unit you are moving, or any of its ancestors included in a Wave Entry that includes descendants? If so, are those deployments still necessary?
Further, is the new parent, or any ancestors, included in a Wave Entry that includes descendants? If yes, do you want the new BU included in those deployments?
-
Follow the steps to create a Business Unit, and then drag and drop a parent Business Unit to a new location.
-
Select OK at the prompt to verify your intended move. The new hierarchy structure shows the parent Business Unit and all child Business Units moved to the new location.
Adaptiva provides default settings for the included templates. Except for the Business Unit templates provided for Root, you can copy the default templates and save them with new details, or you can create a new Business Unit. Related Business Units, including Child Business Units or Lab Business Units, provide another level of detail that administrators can use to further customize a patching environment.
Related Business Units, including Child Business Units or Lab Business Units, provide another level of detail that administrators can use to further customize a patching environment.
Caution
When modifying an existing Business Unit template to create a new configuration, be sure to verify that the Maintenance Window settings and the User Input Settings include the details you require for your Business Unit. Failure to provide these settings can result in installation failures.
Except for Business Units provided for Root, you can copy the default templates and save them with new details, or you can create a new Business Unit.
-
Mouse over or select Business Units in the left pane of the Patch Dashboard, and then select Business Units.
-
Select the right arrow to the left of any folder to expand the list of available templates.
-
Select the ellipses ... next to the object you want to open, and then select Save As.
-
Save the template with a new title:
-
Select Save. When you have finished modifying your new template, you can drag and drop it onto the folder you created (see Patch Object Management).
For Business Units with dynamic membership that may change over time, evaluation schedules determine when to check the membership of a Business Unit. Dynamic membership can occur based on Location or Sensor scopes where a device moves between locations or Sensor results change over time.
The Evaluation Schedules added here trigger Group Membership evaluations for this Business Unit to regularly check for group membership changes.
-
From an open Business Unit, review the selected schedules (if any).
-
If you choose to use the existing schedules, skip to Configure Business Unit Scopes.
-
Otherwise, click + Browse, and then continue with the next step.
-
-
Select Save on the upper-left corner of the dialog to save your progress:
Business Unit Scopes define the rules used to find and include devices in a named Business Unit. Adaptiva supports using one or more scopes to create a Business Unit.
Tip
If the scope type (Locations, and so on) has a number in parenthesis after the name, the template you copied included one or more of the identified scopes. Select the scope type to view the setting. You can either keep the included scope or click the ellipsis (…) after the scope name in the table to edit (if allowed) or delete it.
-
Scroll down to Business Unit Scopes in an open Business Unit.
-
Select the Scope you want to use for this Business Unit.
Use this option to define the Business Unit based on the location of devices. For example, you might want this Business Unit to include all devices in an office located in Chicago.
-
Select Locations from Business Unit Scopes, and then click + Browse.
-
Select one or more Location Names from the Add Locations table to assign them to the Business Unit. For information about managing available Location settings see the Adaptiva OneSite Platform Installation User Guide.
-
Select OK on the lower-left corner of the dialog. This returns you to the Business Unit template and populates a table with the selected Locations.
Design your own SQL queries to define the scope of devices to include in this Business Unit.
-
Select SQL Queries from Business Unit Scopes, and then click + Add Query. This opens the Add Query dialog.
-
Enter a Name for the Query, and then add a detailed Description. The Type field defaults to Client ID, meaning that the software returns a list of Client IDs regardless of what the query might request.
-
Write your SQL query in the Query text box.
Important
Adaptiva recommends testing your sample query using SQL Server Management Studio.
-
Select Add Query at the bottom left of the dialog. This returns you to the Business Unit template and populates a table with the new SQL query.
Choose one or more individual devices as members of this Business Unit.
Important
Device scoping is sensitive to the Client ID. If an administrator reinstalls a client, the client receives a fresh ID and the Business Unit no longer scopes the new client.
-
Select Devices from Business Unit Scopes, and then click + Browse.
-
Use Search to define one or more search details you want to use to locate specific client devices.
-
Enter your search term, and then click Search.
-
Select one or more devices to add to this Business Unit, and then click OK on the lower-left corner of the dialog.
Sensors mark device inventory using technology settings such as Java, PowerShell, WMI, and so on. Adaptiva includes choices for common sensor settings, or you can create your own.
Tip
Selecting a Sensor from this location assumes you have already created the Sensor type you want to use, or that you intend to use one of the default sensors.
To include devices in this Business Unit based on sensor settings, complete the following steps:
-
Select Sensors from Business Unit Scopes, and then click + Add Sensor Group Scope.
-
Enter a Name and a detailed Description of the Sensor Group in the Sensor Group Scope dialog.
-
Select Browse to choose a Sensor.
-
Select the ellipsis (…) next to Sensors, and then select Expand All to view the list of available Sensor settings.
-
Select an item to use in your Sensor Group, and then click Add Sensor. This returns you to the Sensor Group Scope dialog. To add a Filter Condition, see Patch Filter Conditions
-
Select OK to return to the Business Unit template or change Base Scope settings.
Use Base Scope settings to add or exclude devices in a Business Unit based groups, CM collections, or other business units. Using Operators and Conditions, you can extend Business Unit membership and group multiple devices together.
-
Select Base Scope from Business Unit Scopes.
-
Select the ellipsis (…) to the right of Select Operator, and then select Add Group.
-
Select the container type you want to use.
-
Select a CM collection, Business Unit, or Group to add to the Base Scope.
-
Select OK on the lower-left corner of the dialog. The entry under Business Unit Scopes shows the AND operator and the item you chose.
After setting the initial Base Scope, use this procedure to add additional Groups or Business Units to include in the Base Scope. You can add or exclude other Groups or Business Units or change Operators to customize your Base Scope depending on your needs.
-
In the Business Unit Scopes section of an object template, click Base Scope.
-
Select the ellipsis (…) to the right of Select Operator (or any existing Operator), and then select Add Operator.
-
Select the Operator you want to include (AND, OR, NOT). This populates the workspace with the operator you chose.
-
Select the ellipsis (…) next to the operator, and then select Add Group. This opens the Add Group dialog.
-
Select one item from either Groups, ConfigMgr Collections , or Business Units, and then click Add Group on the lower-left corner of the dialog.
-
Repeat steps 1 through 5 to continue modifying the Base Scope to meet your needs.
Select the ellipsis (…) to the right of an Operator or a Group, and then select Remove.
-
Removing the top-level Operator removes everything beneath it.
-
Removing a nested Operator also removes the associated Group or Business Unit.
-
Removing a Group or Business Unit removes only that Group or Business Unit.
Adding Approval Chains to a Business Unit is an advanced feature. The Approval Chains fields allow advanced users to specify details for use in customized Patching Strategies, Deployment Chains, or Business Units when necessary to achieve different results.
-
In an open Business Unit template, click Approval Chains. This opens the Approval Chains workspace.
-
Business Units inherit these settings from a parent by default. For more information about inheritance, see Parent and Child Business Units
-
Disable inheritance to enable and assign a different Approval Chain to a setting.
-
-
Select Browse next to the type of Approval chain you want to add (Product Owner, Patch Management, Security, and so on).
-
Select an Approval Chain from the Approval Chains table. This example uses an All Admins Approval Chain.
-
Select on the bottom left to return to the Approval Chains workspace.
-
Repeat Steps 2 through 4 for each of the groups listed in the Approval Chains workspace:
-
Skip any groups that do not apply to your situation.
-
When each group from which you need an approval contains an approval chain, continue with the next step.
-
-
Select Save at the upper left to save your progress:
Customer Extension Data is an advanced feature of Adaptiva. The Customer Extension Data fields allow advanced users to specify different key/value pairs for use in customized Patching Strategies, Deployment Chains, or Business Units when necessary to achieve different results.
Customer Extension Data fields relate directly to fields in a customized template. If you do not have customized templates with key/value pairs you can modify, you do not need to configure or use this feature.
If you want to create customized templates that use key/value pairs for some settings, contact Adaptiva Customer Support.
Notification Chain settings exist in the object templates for Patching Strategies, Deployment Channels, and Business Units.
-
Expand the Notifications box in an open object template to show the available configuration options.
-
Select Browse next to Notification Chain. This opens the Notifications Chain dialog.
-
Select
Notification Chains, and then select Show All to see the available templates.
-
Select a Notification Chain from the table. To edit or create Notification Chains, see .
-
Continue editing the Notification settings or click on the bottom left corner to return to the template.
The Content Prestaging feature deploys content to devices ahead of the scheduled deployment, either pushing content to a location or allowing a client to pull content. Prestaging content makes the content available on the device locally when the deployment time arrives. This reduces the deployment time and minimizes the chances of missing service windows or having devices going offline before a content download finishes.
To configure these settings, see Content Prestaging Settings.
After saving the Business Unit, click Show Members to display the members of the Business Unit and verify that you have populated the Business Unit as you intend.
Important
Selecting causes evaluation of the group membership rules to occur off schedule.
Designate Lab Business Units to use for testing purposes prior to production deployment.
-
Make sure that the devices you want to use in the lab have the Adaptiva Client installed and are associated with .
-
Follow the steps to Create a Business Unit. When defining the Business Unit Scopes, use Add Devices to identify the devices in your lab or test environment and include them in the Lab Business Unit.
-
Define any other characteristics appropriate to your Lab Business Unit.
Comments
0 comments
Article is closed for comments.