When installing the Cloudmersive Management Agent, you can perform the below diagnostics to confirm if it is working as expected:

• Navigate to the Cloudmersive Management Portal and click on Private Cloud then select the relevant node. Click on Check Health. Click on the Refresh button on the resulting page to see if health check information appears. If it does not, even after waiting a few tens of seconds, then there is an issue to further diagnose.
• Ensure outbound connectivity from your server to all Cloudmersive endpoints, particularly the Management and Notification endpoints - see here - as these are required.
• Open the Windows Services manager and scroll down to Cloudmersive Management Agent. If the Status does not show Running try selecting it and click Start. If it now transitions to Running then repeat step 1 above. If it does not start, ensure that there is no group policy or security software present that could be preventing it from starting up. If you do not see the Cloudmersive Management Agent listed at all it either means that you did not install the Cloudmersive Management Agent, and so should proceed with install, or the install did not succeed. If it is the latter case, share the output of the install command with Cloudmersive Support for further analysis. The most likely cause could be security software or group policy that blocks the installation of new Windows Services.
• If none of the above address the issue, send the log files at C:\CloudmersiveManagementAgent\*.log to Cloudmersive Support via a support case for further analysis and assistance.

Additional Notes

• Please note that Cloudmersive Management Agent is not available for Kubernetes and Azure App Service-based deployments because in those deployments, management is performed via the Kubernetes/App Service platform.