Product integration requirements

An overview of how 1E connects to third-party systems, and how it integrates with its companion 1E products. More detailed information about how to configure 1E is provided in Using Settings.

1E companion products

The following tables show products that combine to support particular features.

For details of the 1E Product Life Cycle refer to 1E Product Lifecycle.

Products and features that depend on 1E Platform	Companion products
Endpoint Automation	A consumer application of 1E Platform.
NightWatchman	Console live status of NightWatchman clients is an optional feature of NightWatchman and requires 1E Platform. NightWatchman is not a platform application and requires its own server(s).
Content Distribution	A consumer application of 1E Platform.
Patch Insights	A consumer application of 1E Platform.
Shopping	Shopping uses 1E Platform and 1E Client for its client-side order notifications, and to allow end-users to shop for 1E instructions. Shopping is not a 1E Platform application, and requires its own server(s).
Experience Analytics	A consumer application of 1E Platform.
Endpoint Automation	A consumer application of 1E Platform.

Companion products that 1E Platform features depend on.

Products and features that 1E Platform depends on	Companion products
1E Client	1E requires the 1E Client. Features: Real-time response to instructions, which supports the retrieval of information using questions, and running actions Tags (freeform and device/coverage) Criticality and Location 1E Client UI to support the Real-Time Control Center, Announcements, Surveys, and Sentiment features of the Experience Analytics application # Inventory, including process usage, to support: Tachyon Activity Record (TAR) feature. Inventory and other consumer applications. Performance metrics features to support the Experience Analytics application # Policy feature to support consumer applications: Endpoint Automation ##, Experience Analytics #, and Content Distribution # Modules to support: The Patch Insights application. # Command and script execution. Content distribution. Device criticality. Manipulation of files and processes. Manipulation of registry and WMI. # Security. # Software uninstallation. User sessions, including Primary User. # not supported on non-Windows. ## partially supported on non-Windows. Clients can optionally use the Content Distribution client module of 1E Client to more efficiently download content.
Content Distribution	Clients can optionally use Nomad (1E Client with Content Distribution client features enabled) to provide more efficient downloading of content.

DEX Packs and Security Roles

Classic DEX Packs:

• Include instructions

• Are uploaded using either of the following methods:

  • 1E product pack deployment tool as described in 1E Product Pack Deployment Tool (PPDT)

  • Upload button on the Settings - Instructions sets page, as described in Instructions.

• Once the instructions are uploaded you must organize them manually into Instruction Sets, although the Tool will use the name of the zip file as the basis for the Instruction set name.

• Instruction Sets are the basis for assigning custom roles that determine who can do what with the instructions in each Set. Refer to Custom Role.

Integrated DEX Packs:

• Include policies and/or instructions.

• Are uploaded using the 1E product pack deployment tool as described in Configuring Endpoint Automation.

• If the pack contains instructions, each one is automatically uploaded into an Instruction Set using the folder name as the basis for the Instruction set name.

• Policies are uploaded into Endpoint Automation.

The Integrated Product Packs provided by 1E include ready-made Policies, and any instructions included in the packs are intended to augment the policies, but can be used independently.

You may want to create AD security groups to use custom roles to control access to:

• Instructions Sets - you should think about groups of people who will need to view, question, action, and approve instructions

• Policies - you must decide who needs access to Endpoint Automation - in this version, you cannot grant access to individual Policies.

Content Distribution integration

Content Distribution integration is available on Windows PC devices and is enabled by default NomadContentDownloadEnabled=true, and can be disabled during or after installation of the 1E Client.

With the integration feature enabled, 1E Platform will detect if the Content Distribution client module of the 1E Client is enabled, or if Content Distribution v6.0.100 or later version is running on the device. Content Distribution then automatically downloads content from the 1E Background Channel, and any other HTTP/S content source that the client may use. 1E Platform use of Microsoft content distribution works irrespective of whether Content Distribution is integrated with Configuration Manager, or using advanced features.

Configuration Manager is not a prerequisite for Microsoft content distribution integration with 1E, but you will need to consider the following:

Configuration Manager present

You do not need to make any configuration changes to Microsoft content distribution for it to integrate with 1E Platform. Refer to Content Distribution features for guidance on designing and deploying Content Distribution.

Configuration Manager not present

You can deploy Content Distribution to Windows devices where the Configuration Manager client is not present. You will need to enable the following bits in relevant installer properties:

• CompatibilityFlags bit 1 - enable long hashes

• SpecialNetShare bit 13 - enable HTTP(S)

These are enabled by default in the Content Distribution client module of the 1E Client.

Configuration Manager integration

1E Platform is able to integrate into the Configuration Manager console to provide a right-click context menu that can be invoked from Configuration Manager computer collections. 1E Platform can then use the members of the computer collections as the coverage for any instruction selected from the menu. The Configuration Manager extensions are part of the 1E PowerShell Toolkit. Refer to Preparing ConfigMgr extensions for 1E Endpoint Troubleshooting.