Settings features

The Settings application lets you configure the 1E system and application settings. For more information refer to the Using Settings section of this documentation.

Instructions, DEX Packs, Instruction sets, and permissions

1E enables you to investigate your network using questions and actions, collectively known as Instructions. You can load Instructions into 1E either individually or with a DEX Pack, which is essentially a zip file containing one or more Instructions. 1E offers a variety of pre-framed questions and actions in the form of DEX Packs, providing extensive out-of-the-box capabilities that can be expanded with new and updated DEX Packs.

Permissions for Instructions in 1E are managed through Instruction sets. You create Instruction sets, define roles that specify particular permissions for those sets, and assign the roles to users. Each Instruction can only reside in one Instruction set, associating it with a role and thereby the users who have that role and can execute the Instruction. The roles have associated Management groups that determine the devices accessible to users with the role. When Instructions are loaded into 1E, they are placed in the default Unassigned Instruction set. You must move them into previously created Instruction sets before they can be executed. Refer to Instructions.

Connectors

Connectors are used to integrate with other 1E and third-party systems to populate repositories. When multiple connectors to different data sources are employed, the information from these sources is de-duplicated and normalized into a single cohesive view, which is then stored in a repository. This allows you to use data from various sources to complement each other and build a more comprehensive picture of "what's out there."

For example, you can sync inventory data from Configuration Manager into an inventory repository to gather information about your Windows devices. You can then enhance this with inventory data synced from 1E, which may include details about non-Windows devices where the client has been installed. Refer to Connectors page.

Repositories

Repositories are used by applications to process and store information. For example, the Patch Insights application utilizes both an inventory repository and a BI repository to process the information needed to report on the success of patching in your enterprise. Typically, a connector is used to link a data source to the appropriate repository.

Repositories are also useful for segregating different types of data. For instance, you could have one inventory repository for Configuration Manager inventory data and another for BigFix data. Alternatively, you can have connectors from different inventory sources pushing data into a single repository. Any Management Groups you create will span all the repositories you have.

For more information on managing repositories, refer to:

• Repositories page - 1E Server

Device Tags

Device Tags are primarily associated with Endpoint Troubleshooting and can be used to target specific devices when setting coverage for Instructions. Additionally, they can be used to define Management Groups, which can be optionally utilized by all applications. Device Tags must be defined by a Full Administrator before they can be used to tag devices or set the coverage of Instructions. This is done from the Settings > Configuration > Custom properties > Device Tags page, accessible to users with the Full Administrator role. Refer to Custom properties and Tagging client devices

Software Tags

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 pages.

In short, you can work with Software tags by:

1. Creating your Software Tag.

2. Associating the new tag with a software title.

3. Creating a Management Group based on the Software Tag name and Tag value rules. This step can be run anytime before evaluation.

4. Evaluating the new Management Group by running a Basic Inventory Consolidation.

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

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 syncing data sources to repositories using connectors and processing the BI data cube. Repository schedules are different from Instruction schedules that can be set in Endpoint Troubleshooting. Refer to Schedules page.

Consumers, Applications, Components, and Providers

The Settings application includes pages for each of these, as detailed in the following table:

Configuration objects	Description
Consumers	These can access 1E using the 1E Consumer API. To enhance the security of the 1E system, only consumers that have been registered on Settings > Configuration > Consumers will be allowed to access 1E.
Applications	Features of 1E that is hosted in the 1E portal. Applications are generally Consumers as they need to interact with 1E using the 1E API. These are available on the Switch App menu.
Components	These form part of SLA and cannot be changed or altered by a user. These can be viewed using the Settings > Configuration > Components page.
Providers	These are components that can be configured to provide a particular operation in SLA. These can be viewed and configured using the Settings > Configuration > Provider configuration page.

Refer to:

• Consumers

• Components page

• Provider configuration page

Information pages

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. Refer to License information and System information page.

Monitoring log files

The monitoring pages let you view how 1E Platform is performing its tasks.

Page	Description
Process log	Whenever you execute a sync or process a repository the steps are displayed here. This page is updated in real-time and shows the status of each step as it happens.
Sync log	The results of performing a sync are displayed here.
Infrastructure log	Information on the 1E infrastructure is displayed here, such as license status and instruction workflow.
Audit information log	This page displays information on the Instructions that have been run in Endpoint Troubleshooting. This includes the instruction text and the user that requested it.

Refer to the Monitoring menu.

Defining users and roles

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.

Refer to:

• Users and Groups

• Roles page

• Configuring Access Rights tutorial

Management groups

Management groups utilize inventory-based rules to define specific device groups. These groups are implemented in SLA and made available to 1E applications and other consumers. Once a management group is defined, the device membership is re-evaluated each time the inventory is updated by applying the group's rules to the new inventory. Custom roles can be created to link specific instruction sets to particular management groups. This allows you to set user permissions for accessing instructions within specific sets and also determine which devices they can target using those instructions.

Once defined, management groups can be used to set the coverage for instructions in Endpoint Troubleshooting and determine which devices can be targeted by specific users. Additionally, management groups are utilized by the Patch Insights and Endpoint Automation applications to identify which devices are being targeted. Refer to Management Groups and Management Groups tutorial.

Uploading Instructions into 1E and creating Instruction sets

You determine the capabilities of Endpoint Troubleshooting by uploading Instructions from product packs into 1E. DEX Pack s 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. Refer to Instructions