PMC Device Management:

            PMC Device Management provides simple device management for RX300 & RX-RDP thin clients.

            Manage your installation over local and wide-area networks, behind firewalls and NAT-routers. PMC is available as part of AMP for vSpace Pro 11 and Verde 8.2. Alternatively, PMC perpetual license (per thin client device) can be purchased separately. 

            Key features for PMC Device Management include:

                   Easy-to-use web-based user interface

                   Device profiles provisioning and configuration pushing to individual or grouped devices

                   Device firmware updates scheduling

                   Remote firmware updates for managed devices

                   Deployed as a virtual appliance compatible with industry-standard hypervisors

                   Dashboard with auto-refreshing summary info

                   Detailed event logging with filtering capability

            Below please the setup instructions for the PMC Device Management software:

            (1)    Hypervisor upload

                   PMC will be delivered as a ready to use virtual appliance, which must be uploaded to a supported hypervisor machine

                   Supported virtual machine environments: 

            -       VMware ESXi 6.0.0

            -       Citrix XenServer 7.1.0

            -       Microsoft Hyper-V (Windows Server 2012 R2)

            (2)    Network setup – interface

            ·         After uploading the PMC virtual appliance to a hypervisor care must be taken to ensure that the virtual Ethernet interface is connected to a virtual network which is bridged with the hypervisor host’s physical network interface or connected to necessary VLAN

            ·         This network interface must be accessible by the managed devices

            o   Connecting the PMC virtual appliance to hypervisor’s NAT-network or host-only network will prevent the managed devices from connecting to PMC




            (3)    Static IP configuration
            • After being uploaded to a hypervisor and started for the first time the PMC virtual appliance will obtain an IP address from a DHCP server.
            • NComputing strongly recommends assigning a static IP address (or at least to create a DHCP reservation) for the PMC appliance. This is to ensure that PMC will always appear in the network with the same IP address. Please pay attention to PMC activation information though!
            • PMC virtual appliance automatically starts a TUI (text-based user interface) on its virtual console (which is accessible through hypervisor’s administration interface). TUI allows the configuration of PMC virtual appliance’s network interfaces.



            (4)    Web-based GUI access:
            • PMC’s web-based user interface can be accessed from any modern web browser through the ‘https://<PMC_address>/pmc’ URL, where <PMC_address> must be replaced with the proper address of the PMC virtual appliance, as shown in the TUI.
            • The PMC component delivering the web-based user interface is preconfigured with a self-signed SSL certificate. An exception for the PMC URL should be created in the web browser used for accessing PMC’s web-based interface.

            ·         The built-in PMC user account with administrative privileges is ‘pmcadmin’. The password is ‘pmcadmin’ too

            (5)    Activation and licensing

            ·         PMC virtual appliance must be activated before it will be used for managing any devices. The activation page will appear when the web-based user interface will be opened for the first time.



                   PMC is available as part of AMP for vSpace Pro 11 and VERDE VDI 8.2

                   Alternatively, PMC perpetual license (per thin client device) can be purchased separately

             

            (6)    Direct activation from NComputing Management Portal

                   For direct activation the PMC virtual appliance must be able to resolve through DNS the fully-qualified domain name of the NComputing Management Portal

                   This becomes impossible after changing the appliance’s IP address to a static one, as currently the static IP configuration does not include DNS configuration

                   Two workarounds are possible for this issue:

            Workaround 1:

            -       The IP configuration can be reverted to DHCP. DHCP reservation should exist to ensure that PMC will always get the same IP address

            -       This will allow successful direct activation, assuming that DHCP provides valid DNS configuration

            Workaround 2:
            DNS configuration can be added to PMC appliance manually to resolve the issue, as following:

                   Connect with an SSH client (e.g. PuTTY) to the IP address of the PMC appliance or use the hypervisor’s administration interface to logon as the 'root' user with 'pmcadmin' password

                   Use the following command to determine the name of the Ethernet interface:

            nmcli con

                   Invoke the following command to add the IP addresses of DNS servers to PMC appliance:

                                    nmcli con mod IFACE ipv4.dns "DNS1_IP DNS2_IP"

            Replace IFACE with the Ethernet interface name and DNS1_IP and DNS2_IP with the IP address of the first and second DNS server. For example, for eth0 interface, when 192.168.200.1 is the IP  address of the first DNS server and 192.168.200.2 the address of the second, the command should be:

                                    nmcli con mod eth0 ipv4.dns "192.168.200.1 192.168.200.2"

                   Invoke the following command to apply the changes:

                                    nmcli con down eth0 ; nmcli con up eth0

                   After this change the PMC virtual appliance configured with a static IP address will be able to resolve the host names using DNS and the direct activation with the Management Portal will succeed

             

            (7)    PMC Licensing

            • Number of allocated PMC licenses depends on how PMC was activated:
              • Activation through vSpace Pro 11: PMC is a benefit of AMP (Annual Maintenance Program) for vSpace Pro 11 and will be granted a number of licenses matching the number of active vSpace Pro AMP subscriptions
              • Activation through VERDE VDI 8.2 server: PMC will be granted a number of licenses matching the number of purchased VERDE VDI licenses
              • Direct activation on NComputing Management Portal: PMC will be granted a number of licenses matching the number of purchased PMC licenses redeemed in the ‘My PMC Installations > My Licenses’ section of the NComputing Management Portal account used for PMC activation
            • 5 complimentary device licenses are always available for test or evaluation purposes

            (8)    PMC Dashboard

            Dashboard contains automatically updating summary information




            (9)    Connecting managed devices
            • The devices to become manageable must obtain the address of the PMC appliance (the URL of the PMC Management Server) to connect to.
            • The address/URL can be specified manually in the Management section of RX300 and RX-RDP Setup GUI as the ‘Use following PMC address’ parameter.


             

            (10)     DHCP-based PMC server auto-detection

            • To automate the PMC server discovery the DHCP option 207 can be used.
            • This DHCP option should provide a string value containing the URL in form of ‘https://<PMC_address>’, where <PMC_address> must be replaced with the proper IP address of the PMC virtual appliance.
            (11)     Device – PMC Communication

            ·         HTTPS protocol will be used by the devices for communication with PMC.

            ·         TCP 443 port must be opened on all firewalls located between the managed devices and the PMC appliance.

            ·         The managed devices repeatedly (every 30 seconds) send to PMC small portions of information – so called heartbeats.

            ·         Heartbeats allow PMC to keep track of devices which are online and also give the devices the information about PMC availability.

            o   Each heartbeat is just around 300 bytes sent and 500 bytes received.

            o   1000 devices will generate: 1000 heartbeats * 300 bytes * 8 bits / 30 seconds = …. 80 kbps incoming (and 133 kbps outgoing).

            o   This is less traffic than one single UXP session (even without multimedia) generates in average.

            ·         In responses to heartbeats PMC sends to devices
            requests to execute management actions.

            o   Because of this approach the devices may react with some delay (up to 30 seconds) to management actions performed in PMC.

            (12)



            (13)  Device Configuration
            ·         Configuration is possible for selected device

            o   Configuration editor shows the edited settings on top of actual configuration reported by the device

            ·         Device profiles help do configure the devices en masse

            o   Configuration editor shows the edited settings on top of the default configuration for the device family, mode, and configuration version

            ·         Configuration editor uses appropriate schema (settings definition) for the edited device family, model, and configuration version

            ·         PMC is ready to manage not yet existing devices or firmware versions, as the schema files are up loadable

             

            (14)     Configuration editor

            ·         Device configuration editor can be used to modify device parameters and push settings remotely to devices via PMC Device Management.







            Updated: 24 Oct 2018 07:24 AM
            Helpful?  
            Help us to make this article better
            0 0