Create a Workspace – A trusted advisor often creates the workspace first. A workspace is the secure area where OneIQ IT Environment (ITE) data is shared and analyzed with others, with controls for visibility and privacy.

Create an IT Environment (ITE) – The IT professional who owns the environment sets up the ITE. This is where Pulse stores collected data, which can include multiple platforms such as VMware, Nutanix, Hyper-V, AWS, Azure, GCP, Kubernetes, Windows, and Linux.

Connect the ITE to the Workspace – The IT professional links the ITE to the pre-created workspace, allowing the collected data to be securely shared with the trusted advisor and made visible in the OneIQ Portal. (It's also possible to create the ITE first, then share it later via a workspace).

Deploy the Pulse connector – The IT professional downloads and installs OneIQ Pulse (a Windows executable) on a Windows Server 2016 or newer. Using the setup wizard, they connect Pulse to their platforms (e.g. vCenter, Prism Central). Pulse begins collecting configuration, performance, and network data, which is stored in the OneIQ ITE.

Confirm that OneIQ Pulse is deployed correctly on the specified Windows Server 2016 or newer.

Use the Test Connection feature within OneIQ Pulse to verify connectivity. If the test fails, review and update the settings as needed.

Ensure that outbound traffic to the OneIQ Central data warehouse (hosted on Microsoft Azure) is allowed, particularly over HTTPS (port 443).

If using a proxy, configure OneIQ Pulse to route traffic through the correct proxy settings.

https://help.oneiq.com/en/articles/9360552-oneiq-pulse-with-a-proxy

Verify that the credentials used for connecting to target systems have sufficient permissions. OneIQ Pulse requires read-only access for data collection and should not need admin privileges.

Check that credentials are up-to-date and correctly entered in the OneIQ Pulse configuration.

Make sure that you are using the latest version of OneIQ Pulse. Updates often include security patches and connectivity improvements.

Download the latest version from the OneIQ Portal and redeploy if necessary.

OneIQ Pulse requires valid SSL/TLS certificates for secure communication. If you encounter errors related to certificates, ensure that they are correctly installed and trusted.

Manually trust certificates if necessary, especially when connecting to private infrastructure.

https://help.oneiq.com/en/articles/8409546-troubleshooting-the-m_safecertcontext-is-in-invalid-handle-error

Access OneIQ Pulse logs for any error messages or warnings that might indicate connection issues.

Look for specific error codes or messages that can guide further troubleshooting or highlight specific connection failures.

Ensure that data being transmitted from OneIQ Pulse is encrypted as per OneIQ's standards (asymmetric encryption and HTTPS) to avoid issues related to data handling policies within your organization.

Restart the OneIQ Pulse service to refresh the connection.

Reboot the server hosting OneIQ Pulse if persistent connection problems occur.

If the above steps do not resolve the issue, contact OneIQ support directly via the OneIQ Portal's support icon. Provide detailed information about your setup and any error messages encountered to expedite the resolution process.