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 the 1E products that combine to support particular features.
|
Products |
Features that depend on 1E Platform |
|---|---|
|
AppClarity |
AppClarity is a consumer application of the 1E Platform and requires a full 1E infrastructure. |
|
Application Migration |
Application Migration is a consumer application of the 1E Platform and requires a full 1E infrastructure. |
|
Endpoint Automation |
Endpoint Automation is a consumer application of the 1E Platform and requires a full 1E infrastructure. |
|
NightWatchman |
Console live status of NightWatchman clients is an optional feature of NightWatchman and requires a full 1E infrastructure. NightWatchman is not a 1E Platform application and requires its own server(s). |
|
Content Distribution |
Content Distribution is a consumer application of the 1E Platform and requires a full 1E infrastructure. It includes the Content Distribution feature that replaces the legacy ActiveEfficiency Server and its features. |
|
Patch Insights |
Patch Insights is a consumer application of the 1E Platform and requires a full 1E infrastructure. It also requires 1E SLA Platform Business Intelligence to be installed and a SQL Server Analysis Server (SSAS) instance. |
|
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 |
Experience Analytics is a consumer application of the 1E Platform and requires a full 1E infrastructure. |
|
Endpoint Troubleshooting |
Endpoint Troubleshooting is a consumer application of the 1E Platform and requires a full 1E infrastructure. |
In addition to the consumer applications listed above, 1E Setup is also used to install the Inventory Insights and Settings applications.
Supported versions of 1E companion products that 1E Platform features depend on.
|
Products |
Features that 1E Platform depends on |
|---|---|
|
1E Client |
1E requires the 1E Client to be installed on all client computers. Client features:
# not supported on non-Windows, ## partially supported on non-Windows Platform clients can optionally use the Content Distribution client module of 1E Client to more efficiently download content. |
|
Content Distribution |
Clients can optionally use Content Distribution (1E Client with Content Distribution client features enabled) to provide more efficient downloading of content. |
Connectors
You have to decide which connectors you want to use to populate inventory repositories. Connectors are used to connect to other 1E and third-party systems, retrieve their data, and populate repositories. Refer to About connectors.
Patch Insights needs to get meta-data for patches. Ensure you add a connector for whichever one of the following sources that you use to approve patches:
-
Configuration Manager (SCCM) if it is configured to manage WSUS
-
Windows Server Update Services (WSUS)
If you are using Configuration Manager then you must add a System Center Configuration Manager connector.
If you are using WSUS then you must add a Windows Server Update Services connector.
Patch Insights also requires a 1E connector.
The table below shows the supported versions of software used by out-of-box connectors.
|
Connector |
Product |
Prerequisites and configuration information |
|---|---|---|
|
BigFix |
BigFix |
|
|
Intune |
Intune |
|
|
Microsoft Office 365 |
Azure |
|
|
OpenLM |
OpenLM Server version 21.12 |
|
|
Oracle LMS |
Oracle LMS |
|
|
ServiceNow |
|
|
|
System Center Configuration Manager (SCCM) |
|
|
|
1E |
1E |
|
|
vCenter |
VMware PowerCLI 11.1.0 |
VMware PowerCLI 11.1.0 must be installed on the 1E Master server (where the SLA Integrate Services Agent service is hosted) before you can configure and use the vCenter connector. Earlier or later versions of PowerCLI are not supported and may cause errors. VMware PowerCLI is freeware and was previously known as vSphere PowerCLI. VMware PowerCLI supports multiple versions of VMware vCenter Server. Refer to the VMware compatibility matrix. |
|
WSUS (Windows Server Update Services) |
WSUS |
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.
Integrated DEX Packs:
-
Include policies and/or instructions
-
Are uploaded using the 1E product pack deployment tool as described in Uploading Integrated Product Packs
-
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 will detect if the Content Distribution client module of the 1E Client is enabled, or if Content Distribution is running on the device. Content Distribution then automatically downloads content from 1E Background Channel servers, and any other HTTP/S content source that the client may use.
1E use of Content Distribution works irrespective of whether Content Distribution is integrated with Configuration Manager or using advanced Content Distribution features that use Content Distribution.
Configuration Manager is not a prerequisite for 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 Content Distribution for it to integrate with 1E. Refer Introducing Content Distribution 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 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 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.