Overview

NComputing PMC is an endpoint management system designed and developed to remotely manage NComputing access devices including LEAF OS devices (PCs/Laptops), RX420(RDP), RX-RDP+, RX-RDP and RX-300 thin clients.  

Requirements

1. A compatible virtual machine hypervisor (e.g., Windows with Hyper-V enabled, VMware)
   
2. Administrative access to your virtual hypervisor
   
3. PMC virtual appliance ZIP file downloaded from the NComputing Management Portal
   
4. Network knowledge sufficient to configure VM network bridging or external switches
   

Step-by-Step: Deploying PMC on Hyper-V

1. Download the PMC Appliance. 
   In the Management Portal homepage, go to My PMC Installations > Software Downloads     
   Show me the process

   1. Visit www.ncomputing.com and sign in using your credentials.
   2. Click the Management Portal tab to enter the homepage.
      
      
   3. Click on My PMC Installations.
      
      
   4. On the left-hand panel, select Software Downloads.
      
      
   5. Download the Hyper-V PMC Virtual Appliance (VHD) ZIP package.
      

   
   
   

   
   
2. Extract the ZIP folder and Import the Virtual Machine. 
   Do this by using the Import menu of your Virtual Machine Hypervisor.  
   Show me the process for Hyper-V

   1. Extract the downloaded .zip file to a known location.
   

   

   
   

   2. Open the Hyper-V Manager.
   

   3. In the Actions menu, select Import Virtual Machine.
   

   

   4. Browse to the extracted folder and select the Virtual Machines directory.
   

         

   5. Choose the PMC virtual machine and click Next.
   

         

   6. Select Register the virtual machine in place (Refer to this Microsoft article guidance: 🔗Export and import virtual machines).
         

   7. Complete the import wizard.
         

   
   
3. Configure Virtual Networking for your Virtual Machine. 
   

   
   Ensuring Network Connectivity Between PMC and Physical Devices
   

   To allow the PMC Virtual Appliance to discover and communicate with your physical NComputing thin clients, the virtual machine must be configured to connect to the same local network (LAN) as the physical devices. If you’re familiar with your organization's network configuration policies and virtual network setup, proceed accordingly and skip to the next section. Otherwise, follow the general guidance below.
   

   Bridged Networking – General Virtualization Platforms

   In most virtualization platforms (e.g., VMware Workstation, VMware ESXi, VirtualBox), this is typically achieved by setting the PMC VM’s network adapter to use “Bridged” mode.
   

   

   This configuration bridges the virtual network interface card (vNIC) of the VM directly to the host machine’s physical network adapter (NIC), allowing the virtual machine to act as if it were another physical device on the same network. 

   Bridged Networking – Hyper-V (Microsoft Windows)

   Hyper-V handles network bridging differently. Instead of selecting a "bridged" option per VM, you must first create a Virtual Switch that connects your VM to the physical network.

   1. In the right-hand pane, under your host machine’s name, click Virtual Switch Manager.
      
      
   2. Select External, then click Create Virtual Switch.
      
   3. Choose your host machine's physical NIC that connects to your LAN and save the settings.
   4. Next, select your PMC VM, then click Settings.
      
   5. Under Network Adapter, choose the New Virtual Switch you just created.
      
   6. Leave the VLAN ID setting at default unless your network uses VLAN tagging.
      

   Note: Without this Virtual Switch setup in Hyper-V, your PMC VM will remain isolated and unable to discover or manage devices on the network.

   
   
   

   
   

   Tip: Once bridged, the PMC VM will receive an IP address from the same DHCP server as your physical devices (we strongly recommend to use a reserved, Static IP) thus, enabling an a fixed, direct communication channel.

4. Start the PMC Virtual Appliance.
   In the case of Hyper-V, in the VM list, right-click the PMC VM and select Start. In the console view to monitor the initialization process.
   Wait for the VM to boot, self configure. When it is ready, you will see the 'homepage', which shows the PMC configuration menu (text-based interface).
   
   
   

Initial PMC Configuration

1. Set Up Networking
   
1. From the PMC startup menu, select option 1 - Configure Networking and follow the menus until completion.
   We recommend assigning a static IP address. This ensures reliable access for both administrators and managed devices. If using DHCP, consider creating a DHCP reservation on your router or DHCP server to maintain a consistent IP.
2. Once you save your configurations, PMC will display its assigned IP address and URL for you to use.
   
   
   
2. Access the PMC Web Interface
   
1. Open a browser and enter the provided PMC URL.
   
2. Login using your NComputing Management Portal credentials (this links PMC with your licenses and registered devices under your account).
   
3. Complete activation by following the on-screen prompts.
   
   

Choosing Subnet Tagging Behavior

Before completing the setup, you will be prompted to choose how PMC should assign devices to groups using Subnet Tags. This choice defines how devices will be automatically grouped and cannot be changed later without redeploying PMC

1. Use Network Addressing when assigning devices with a Subnet Tag value
   Recommended for deployments in corporate environments where network topology (subnets) aligns with organizational structure.
1. Devices are grouped using a combination of their actual network subnet and the Subnet Tag value set on the device.
   
2. Enables more granular grouping and automatic organization across different office locations.
   
3. Ideal for internal networks where devices are on known subnets managed by IT.
   
2. Only use device Subnet Tag value when assigning devices to groups
   Recommended for distributed or remote work scenarios where devices are connecting over external or home networks.
1. Ignores network subnet and groups devices exclusively by their Subnet Tag value.
   
2. Prevents the system from creating unnecessary subnet-based groupings due to unpredictable public IP ranges (common with remote workers).
   
3. Ideal for remote deployments, BYOD scenarios, or when network subnet info is unreliable or too diverse.
   

• Default Username: pmcadmin

• Default Password: pmcadmin


⚠️ Security Note: Please change the default password immediately. However, be advised that NComputing support cannot recover lost credentials. 

Once you login you should be able to see the homepage of your PMC End Point Manager Dashboard

Conclusion

Your PMC appliance is now deployed and configured. You can begin managing your compatible NComputing thin clients via the web interface and leverage advanced tools such as firmware updates, configuration profiles, and zero-touch onboarding.

For further help, contact NComputing Technical Support.