Updated on: 25 November, 2019

VMware Pulse IoT Center | Version 2.0.1 | On-Premise GA Release


What's in the Release Notes

The release notes cover the following topics:

About VMware Pulse IoT Center

VMware Pulse IoT Center is a secure, enterprise-grade, edge infrastructure and IoT device management solution that provides visibility and control over all IoT use cases. It helps companies to onboard, configure, monitor, manage and secure IoT devices and infrastructure. The solution enables IT and Operational Technology (OT) to simplify device management and operationalize IoT use cases quickly by reducing the complexity of managing all the heterogeneous edge and IoT systems in one place.

VMware Pulse IoT Center Version 2.0 includes the following new features and capabilities by their feature category:


  • Onboard certified gateways and connected devices securely to the Service Offering through a low-touch enrollment process
  • Configure gateways, connectivity to gateways, and application/containers on gateways
  • Setup of device properties and metrics through device template
  • Define metrics collection frequency and batch size

Monitor and Troubleshoot IoT Infrastructure

  • Set up alert definition and notification through email or REST API
  • Monitor device health and detect abnormalities
  • Troubleshoot through system log and audit log 
  • Act by sending supported commands to devices 

Manage IoT Infrastructure

  • Enable policy driven over-the-air software lifecycle management 
  • Manage the software and security patch update approval process
  • View alerts, metrics trends, and granular status of software update execution on the dashboard
  • Visualize the representation of the parent-child topology 
  • Manage certified heterogeneous devices and gateways with different hardware, operating systems, and communication protocols


  • Role-based user access according to organizations and use cases.

What's New in this Release

Release 2.0.1 - Released October 18, 2019

VMware Pulse IoT Center Server Version 2.0.1-14836451​ |  VMware Pulse IoTC Agent Version 2.0.1-14825020​​

Onboarding and Device Management

  • You can now enroll a device to a specific domain of an organization.
  • A new SDK API getDevicesData is introduced to get details of all the gateway devices and their connected devices.
  • You can now register multiple devices through the Package Management CLI tool.
  • You can now register devices using the Basic Enrollment Provider type. This provides more flexibility to pre-register your devices.
  • You can now view the list of files uploaded by the device on the VMware Pulse IoT Center console. This could be useful to manage the log files you upload from devices.
  • You can now run commands across multiple devices. 

OTA Campaign

  • You can now update the VMware Pulse IoTC Agent using OTA Campaign to assist the update process. For more information, see the Update the VMware Pulse IoTC Agent section of the VMware Pulse IoT Center User Guide.
  • You can now monitor the status of a campaign from the Campaign Details screen of the VMware Pulse IoT Center console.

Alerts and Notifications

  • Repeated notification instances to notify the user of any required action - When creating a notification definition, you can now configure its repetition interval and the repetition count.
  • You can set alerts on devices across multiple device templates. This eliminates the effort to set alerts on one device template at a time.
  • You can now use the advanced search query result to select those devices that you want to monitor and create alerts on.

Identity and Access Management

  • You can now use the same user name to log in across multiple organizations. In the VMware Pulse IoT Center login screen, select the domain name of the organization from the drop-down menu and log in.
  • The default password expiration duration is 90 days. This duration is reset when you update, change, or reset your password.
  • As a System Administrator or an Organization Administrator, you will now receive an email notification about your domain name, which is the same as your organization name, during an upgrade. 

Gateways Certified for Use

The VMware Compatibility Guide lists the Gateways and Edge Systems that are certified for use with VMware Pulse IoT Center:

Before You Begin

Before you begin using VMware Pulse IoT Center, ensure that you meet the following requirements:


  • Create roles for various permissions that are suited to your organization. The following roles are created by default, and can be used as a reference:
    • Default Administrator
    • Monitoring Administrator
    • Campaign Administrator
    • Gateway Administrator
  • Ensure that the Gateways and Edge Systems are certified for use with VMware Pulse IoT Center.
  • Install the IoTC Agent package on your gateways: Perform the following steps:
    1. Log in to the VMware Pulse IoT Center UI.
    2. From the top right of the home page, click the settings icon and click Downloads.
    3. Download the IoTC Agent tarball Pulse Agent (x86_64)Pulse Agent (arm), or Pulse Agent (aarch64) to your local system.
    4. Copy the IoTC Agent tarball to the gateway file system by using SSH.
    5. Extract the IoTC Agent tarball on the gateway.
    6. Run install.sh.
  • Create a device template using VMware Pulse IoT Center to enroll gateways or thing devices.

Technical Configuration and Code Integration

  • Users with the Campaign Administrator or Package Administrator role can create campaign packages using the Package Management CLI tool.
  • The Package Management CLI tool is available for download from VMware Pulse IoT CenterDownloads section.
  • The Package Management CLI tool creates campaign packages in the VMware Pulse IoT Center recommended iotcp format.
  • Use the DefaultClient file as a binary or code to perform the following operations from the gateway. The DefaultClient file is available at: /opt/vmware/iotc-agent/bin:
    • Gateway and Thing Enrollment/Unenrollment
    • Custom Metrics Ingestion
    • Edit or Read Properties on the VMware Pulse IoT Center Server
    • Add Devices
  • Additionally, the VMware Pulse IoTC Agent has a DefaultClient daemon that collects device metrics such as CPU, Memory, and Disk Usage from the gateway and sends them to the VMware Pulse IoT Center server.
  • These metrics are called Default Metrics and are added automatically while creating the gateway templates.
  • While creating a gateway template, ensure that you do not remove or edit the CPU-Usage, Memory-Usage, and Disk-Usage metrics that are available in the template by default.


Known Issues

The following known issues will be fixed in the upcoming releases.
  • Log bundle download failure.

    Log bundle fails to download from the VMware Pulse IoT Center Administration console.

    Delete the following files:


    NOTE: Ensure that you delete the files only once per instance.

  • VMware Pulse IoTC Agent installation fails on gateways with selected OS combinations.

    This issue occurs because the previous version of VMware Pulse IoTC Agent (for  VMware Pulse IoT Center 2.0.0) runs as a root user whereas the latest version of VMware Pulse IoTC Agent (for VMware Pulse IoT Center 2.0.1) runs as an iotc user. If you are upgrading a VMware Pulse IoT Center 2.0.0 on-premise deployment, you must update the VMware Pulse IoT Center server instance with a newer version of the VMware Pulse IoTC Agent before starting the upgrade process. Gateways with the following operating systems are affected:

    • Photon OS 3
    • Ubuntu 16.04
    • Poky Linux (Yocto Project Reference Distro) 2.1.2

    To perform a fresh install of the VMware Pulse IoTC Agent:

    1. Remove the directories /opt and /opt/vmware by running the command: rm -rf /opt.
    2. Install the latest version of the VMware Pulse IoTC Agent.  For more information, see the Installing the VMware Pulse IoTC Agent section of the VMware Pulse IoT Center User Guide.

    To upgrade the VMware Pulse IoTC Agent on the above-mentioned gateways, see the VMware KB article https://kb.vmware.com/s/article/76368.

  • Memory usage issue on instances that manage a large number of devices.

    On VMware Pulse IoT Center instances that manage a large number of devices, it is observed that the memory usage of service processes stays consistently high over time. Due to this, long-running nodes could run out of memory and fail. This causes the instance to run at reduced capacity. You must restart the node to restore instance health.

    Workaround: Restart the processes of specific services where the RAM usage is high.

  • Repeated IoTCP package upload and delete operation fails.

    The file upload operation fails when you upload and delete an IoTCP package repeatedly.

    Modify the IoTCP package content such that the checksum or binary data of the package differs from the previously uploaded IoTCP package and upload.

check-circle-line exclamation-circle-line close-line
Scroll to top icon