Features covered by the Unified User Experience
This overview provides a summary of the supported features for administration and also which information is transferred via the Enterprise Service Bus (ESB). Please see the help for more details.
Covered version 23.0 with ESB 2.9
- ESB = Information is transferred via Enterprise Service Bus
- Connector = Information is transferred via Empirum Connector
- Data Provider = Information via Empirun Data Provider or Silverback/Intune Data Provider
- EWC = Requires a installed Empirum Web Console and configured access
- API = Requires direct API access to the core system
|Dashboard with charts for SUEM
|Empirum, Silverback and EDP related data. Includes service management incident information and announcements.
|Dashboard with charts for UEM
|Empirum, Silverback related data
Co-Managed devices which are managed by Empirum and Silverback/Intune. Classic = Empirum only and Modern = Silverback or Intune only.
The state gets detected by the Empirum ID and/or Silverback ID/Intune ID of devices.
|Data from Empirum Connector and/or ESB is available. Co-Managed devices also gets updates from Silverback (ESB/Data Provider). Intune devices are imported via the Intune data provider.
|Endpoint Device View
|Shows a list of all managed computers and allows to drill in a preview. Also the "Editing" is possible which displays all details and allows changing several values. The data is shared with Asset Management.
|Data from Empirum Connector/ Data Provider and/or ESB is available. Modern and Co-Managed devices also get updates from Silverback (ESB/Data Provider) and Intune data provider.
Shows various management relevant information
Data from Empirum Connector or ESB is available
Silverback (Data Provider and ESB)
Intune data provider
Patch Management (ESB)
|Add / Delete Computer
Uses Empirum API
Add and Delete in the UEM/SUEM App will also perform the activity in Empirum. But the same actions via Asset Management are not affected computers in Empirum
|Actions on managed computers
Actions allow to manage one or more selected computers.
ESB and API.
Empirum API needs to be configured in the UEM Settings. Silverback API is configured in the Silverback Data Provider.
Empirum Web Console installed and configured in UEM settings for Show Log.
Intune actions are performed via API and require the correct App privileges for the used service connection.
Shows a list of UEM Objects assignable in UUX from Empirum and Silverback. All are provided via ESB from Empirum and Silverback.
Empirum Software Classes are not (yet) provided.
|Empirum, Silverback via ESB
|Actions on UEM Objects
Actions allow the upload and removal of various UEM Objects.
Add Package: Uploads UEM Objects. Uploaded objects are downloaded by the core systems (Empirum and Silverback) and registered.
Delete: Deletes the object. The user can choose to only remove from UUX or also send the delete request to the core system (Empirum).
|Communication via ESB remote actions.
Shows the state and details of deployments. Empirum information is based on installation state from log and Silverback on assignment state to Tags.
|Empirum, Silverback via ESB
Management of Assignments. Assignments are used for deployments and assigning computers to Tags.
Provides features like pe-building and later activation, automated rollout plans, Empirum distribution options.
Assignments are created in Empirum in a dedicated Assignment Group called "UEM Console". Existing Empirum assignments in other groups are not considered.
Assignments are created, updated and deleted via API. Empirum API needs to be configured in the UEM Settings. Silverback API is configured in the Silverback Data Provider.
The installation status used for calculation of the progress is sent via ESB.
|Settings for connection information of the Empirum API and Empirum Web Console (EWC). Only available for self hosted customers. (EWC)
|Empirum API and EWC
- Proceed with Service Bus Installation and Configuration: Enterprise Service Bus