1E 23.11 (SaaS)

1E lets you investigate your network using questions and actions, which are collectively known as Instructions.

You can load Instructions into 1E, either individually or with a DEXPack, which is essentially a zip file containing one or more Instructions. 1E comes with a range of pre-framed questions and actions in the form of DEXPacks, providing extensive out-of-the-box capabilities that can be extended as new and updated DEXPacks are made available.

1E permissions for the Instructions are handled using Instruction sets. You create Instruction sets, then define roles that specify particular permissions on those sets, and then assign the roles to users. Each Instruction is only allowed to reside in one Instruction Set, which associates it with a role and thereby the users that have that role and can run the Instruction. The roles have associated Management groups that determine the devices that users with the role have access.

When Instructions are loaded into 1E they are placed in the default Unassigned Instruction Set, so you must move them into previously created Instruction sets before they can be run.

For more information on uploading product packs into 1E and managing Instruction sets, please refer to Instruction sets page.

Connectors are used to connect to other 1E and third party systems and populate repositories. When more than one connector to different data sources is used, the information from those different data sources is de-duplicated and normalized into a single cohesive view that is then stored in a repository. In this way, you can use the data from different sources to augment each other and build a better picture of "what's out there?".

For example, you can sync inventory data from Configuration Manager into an inventory repository, which will fetch information about your Windows devices. You could then augment that with inventory data synced from 1E which could include information about non-Windows devices where the client has been installed.

Repositories are used by applications to process and store information. For example, the Patch Insights application uses both an inventory and a BI repository to process the information needed to report on how successful patching is in your enterprise. Normally a connector is used to connect a data source to an appropriate repository.

Device Tags are generally associated with Endpoint Troubleshooting and can be used when setting coverage to target Instructions to particular devices, but they can also be used to define Management Groups optionally used by all applications.

Device Tags must be defined by a Full Administrator before they can be used to tag devices or used to set the coverage of Instructions.

This is done from the Settings→Configuration→Custom properties→ Device Tags page, which can be viewed by users with the Full Administrator role.

Using Software Tags allows you to create custom labels and associate them with the software titles you have deployed in your estate.

You can do this from the Settings→Configuration→Custom properties→Software Tags page, which can be viewed by users with the Full Administrator role.

Using Software Tags allows you to create custom labels and associate them with the software titles you have deployed in your estate. An administrator with either the Full Administrator or Group Administrator role can set Software Tags in their environment, they can also create Management Groups based on the tag name and value. For details about configuring 1E users, Roles, and Management Groups refer to the Permissions Menu pages.

In short, you can work with Software tags by:

If an administrator adds or modifies Software Tags or associations, they will have to run the Management Group evaluation report again to see the updated devices reflected in Inventory.

Schedules can be created to execute specific operations on repositories in 1E so that they are kept up to date with their data sources and processing. These operations include:

Repository schedules are different from Instruction schedules that can be set in Endpoint Troubleshooting.

There are pages in the Settings application for each of these. They are described in the following table:

Information on your 1E license is available, as well as the ability to, reactivate it following an update.

You can view information on the 1E system information for the Consumer, Coordinator, Background channel, Core and Switch.

The monitoring pages let you view how 1E is performing its tasks. Four key log pages are provided:

1E users or groups can be added from AD. They can be assigned roles that determine what aspects of 1E they can access. Custom roles can be created that let you associate particular permissions on particular Instruction sets for particular management groups.

Management groups use inventory-based rules to define groups of particular devices, they are implemented in SLA and then made available to 1E applications and other consumers. After a management group is defined, each time the inventory is updated the device membership of the groups is re-evaluated by applying the management group's rules to the new inventory.

Custom roles can be created that tie particular Instruction sets to particular management groups. This means you can not only set the permissions for users to access the Instructions in specific Instructions sets, but you can also determine which devices they can target using those Instructions.

Once defined, management groups can then be used to set the coverage for Instructions in Endpoint Troubleshooting and also which devices can be targeted by particular users. Management groups are also used by the Patch Insights and Endpoint Automation applications to determine which devices are being targeted.

You determine the capabilities of Endpoint Troubleshooting by uploading Instructions from product packs into 1E. DEXPacks are either provided with the release or downloaded from the 1E Exchange. Once the Instructions have been uploaded into 1E you then need to put them into Instruction sets. The Instruction sets can then be associated with custom roles to determine the permissions applied to the Instructions. The custom roles are then applied to users to determine which Instructions each user has access to.