Perform PMC Endpoint Manager "In-Place" Upgrade in Azure Cloud (related to Microsoft Defender for Cloud)

Perform PMC Endpoint Manager "In-Place" Upgrade in Azure Cloud (related to Microsoft Defender for Cloud)

Important Notice

This article applies only to PMC versions earlier than 4.2.1.

Starting with PMC version 4.2.1, the platform has migrated to a Debian 12–based OS, which resolves the compatibility issues previously seen with Microsoft Defender for Cloud when running in Azure.

We strongly encourage all customers to upgrade to PMC 4.2.1 or newer to benefit from:

  • Full compatibility with Microsoft Defender for Cloud

  • Improved security and performance with Debian 12

  • Ongoing feature and maintenance support

If you must continue using an earlier PMC version (Debian 11–based), please follow the guidance below to perform an in-place upgrade on Azure Cloud while minimizing service interruption.

1. Background

Earlier PMC versions (3.x, 4.0.x, and 4.1.x) were built on Debian 11 and could encounter issues when Microsoft Defender for Cloud was enabled on the Azure subscription hosting the PMC VM. These issues stemmed from the Defender extension installing incompatible Linux agents (such as MDE.Linux and OmsAgentForLinux), which could cause excessive log generation and resource usage.

Starting with PMC 4.2.1, these limitations are eliminated. This KB remains relevant only for users running earlier versions who cannot immediately migrate.

2. Pre-Upgrade Preparation

Before beginning the in-place upgrade process, complete the following steps:

  1. Back up PMC data

    • Log in to PMC as an administrator.

    • Navigate to System Settings → Backup & Restore.

    • Download a full configuration backup, including device and license data.

  2. Confirm current version

    • Run cat /etc/os-release to verify that your current OS is Debian 11 (bullseye).

    • Run pmc --version to verify PMC version (should be earlier than 4.2.1).

  3. Check Microsoft Defender for Cloud status


3. Performing the In-Place Upgrade

Note: This procedure applies only to Debian 11–based PMC appliances (versions 3.x to 4.1.x). Do not apply these steps to PMC 4.2.1 or later.

  1. Access PMC via SSH

    • Use an SSH client to connect to your PMC Azure VM as the ncomputing user (or admin user).

  2. Update repositories

    sudo apt update && sudo apt upgrade -y

  3. Download the latest PMC package for your series

    • Obtain the appropriate upgrade package from NComputing Support or the PMC Downloads portal.

    • Upload the package to /home/ncomputing/ on the PMC VM.

  4. Install the upgrade

    sudo dpkg -i pmc_<version>.deb
sudo systemctl restart pmc

  5. Verify PMC services

    sudo systemctl status pmc

  6. Confirm PMC web console access

    • Open a browser and log in to PMC using its Azure public IP or assigned DNS name.

    • Verify that the version has been updated successfully.

4. Post-Upgrade Steps

  1. Re-enable Defender for Cloud (if previously disabled)

    • After completing the upgrade and validating stability, you may re-enable Defender for Cloud if needed.

    • Monitor the system for at least 24 hours to ensure logs and resource usage remain normal.

  2. Consider migrating to PMC 4.2.1+

    • Once operational stability is confirmed, plan your migration to PMC 4.2.1 or newer to fully benefit from Debian 12 and native Defender compatibility.

5. Migration to PMC 4.2.1 or Newer

For customers ready to upgrade to the latest version:

  • PMC 4.2.1 introduces a Debian 12–based architecture that eliminates the Defender for Cloud conflict entirely.

  • Deployment can be done directly from the
    Azure Marketplace

  • You can restore your previous PMC backup to retain all device and policy settings after deployment.

For detailed migration steps, refer to the official upgrade guide or contact NComputing Support for assistance.

6. Summary

PMC VersionOS Base      Microsoft Defender CompatibilityAction Recommended
3.x – 4.1.x   Debian 11      Compatibility issues possible          Follow this KB for in-place upgrade or policy workarounds
4.2.1 +   Debian 12      Fully compatible          Upgrade recommended; this KB not applicable




    • Related Articles

    • [Release Notes] PMC Endpoint Manager

      NComputing PMC Endpoint Manager Version 4.2.1 Release Notes PRODUCT RELEASE NOTES: NCOMPUTING PMC ENDPOINT MANAGER, VERSIONS 4.2.1 Product: NComputing PMC Endpoint Manager Version: 4.2.1 Supported virtualization environments: VMware ESXi 6.7.0, ...

    • Tips for Deploying PMC Endpoint Manager on Azure Cloud (related to Microsoft Defender for Cloud)

      Important Notice If you are using PMC Endpoint Manager version 4.2.1 or newer, this article does not apply to your deployment. Starting with version 4.2.1, PMC has migrated to a Debian 12-based OS and the previously described compatibility issue with ...

    • PMC Version 4, Start Guide

      Overview This document based on the release notes of PMC 4.1.1. It covers everything you need to know, in-depth, regarding installation and deployment of PMC. It is always recommended that you use the current release notes of every PMC version that ...

    • Updating PMC Virtual Appliance – Process and Best Practices

      Overview This article provides a step-by-step guide for updating the PMC Virtual Appliance. Whether your PMC is hosted on-premises or in a cloud environment like Azure, following these instructions will ensure a smooth and secure update process. PMC ...

    • Can I install PMC Endpoint Manager on Azure Cloud?

      Yes. Starting with PMC Endpoint Manager version 2.7.0, the PMC Linux virtual appliance can be installed and deployed on Microsoft Azure Cloud. Please refer to the PMC Endpoint Manager (2.7.0) Azure Installation guide here for detailed instructions.