Omnissa Workspace ONE

nav.hidden, nav ul [x-cloak], nav ul li ul { display: block !important; } This website requires Javascript for some parts to function properly. Your experience may vary.

Cookie Settings

This site uses cookies that need consent.

Functional First party cookies are needed for the website to function. These can't be turned off.

Products / Omnissa Workspace ONE

Omnissa Workspace ONE

Omnissa Workspace ONE UEM (formerly VMware Workspace ONE UEM) is a unified endpoint management solution that enables organisations to manage and secure a wide range of devices—including mobile, desktop, rugged, and IoT—from a single platform. It offers centralised device lifecycle management, policy enforcement, application deployment, and endpoint security. Designed for modern, distributed workforces, Workspace ONE UEM supports multiple operating systems and integrates with identity and access management tools to ensure secure, seamless user experiences.

The CI Synchronizer Workspace ONE connector allows organisations to synchronisation both corporate and BYOD information into your CMDB to underpin ITSM and ITAM processes in the destination system.

Setup of the connector is straight forwards allowing you rapidly integrate Workspace ONE with your CMDB.

Corporate and BYOD

Effortlessly extract a range of end user compute resource types, encompassing both corporate and Bring Your Own Device (BYOD) categories. Further, the synchronisation process can be customised to your specific needs and preferences.

Software Inventory

Efficiently retrieve Installed Software data and seamlessly generate corresponding Software Package records in the Configuration Management Database (CMDB). CI Synchronizer automates this process, ensuring an up-to-date and comprehensive software inventory.

Relationships

Roadmap Connectors

Meraki

SentinelOne

Tanium

Frequently Asked Questions

CI Synchronizer Professional Edition provides a streamlined, out-of-the-box solution for businesses looking for efficient, hassle-free CMDB synchronisation without the need for extensive customisation.

CI Synchronizer Enterprise Edition offers advanced customisation and high-volume data handling capabilities, perfect for organisations with complex synchronisation needs and custom configuration requirements.

Compare CI Synchronizer editions

Many! Check out each source connector page for details of the supported assets and other records.

Yes. CI Synchronizer can detect which source records have changed since the previous synchronisation job and only sync the newly changed source data.

Throughput is affected by factors outside of the control of CI Synchronizer, however we see a typical throughput of between 200,000 and 400,000 records per hour (and even higher rates are possible).

Yes. CI Synchronizer has a highly customisable rules engine. Amendment of some Standard (simple) default Data Sync Rules can be performed via the CI Sync Web User Interface and supported with Knowledge Base articles. Amendment of Advanced Data Sync Rules or creation of Custom Data Sync Rules requires an “Extended Implementation and Ongoing Support Plan” available at an additional cost to your CI Sync Subscription Plan.

Visit the Support page for details on amending the Default CI Sync Data Sync Rules relative to the support plan (including no plan) offered by Syncfish.

Yes. Please fill and submit the Book a Demo form to set up a time to meet with one of the Syncfish team.

No. Each customer is provisioned with a dedicated CI Synchronizer instance.

Ultimately the customer decides, however Syncfish recommends hosting each customer instance physically close to the location of their ServiceNow instance (for best performance). It can be hosted in most/all Azure Regions globally (it is still hosted/managed/maintained by Syncfish, but the customer decides which geography it is physically located in).

No. The source asset data (read from the relevant source system by one of the CI Synchronizer connectors) is transited through your dedicated CI Synchronizer instance then deleted after it’s been processed into ServiceNow.