Numecent CloudPaging + Citrix DaaS Integration Guide

book

Article ID: CTX695729

calendar_today

Updated On:

Description

Overview 

Numecent’s Cloudpaging is an advanced application virtualization and containerization platform that allows Windows applications to be packaged into secure, lightweight Cloudpaging containers. These containers are dynamically provisioned and updated on end user desktops without requiring full installation, significantly reducing image management complexity.

Cloudpaging applications can be: 

  • Packaged using Cloudpaging Studio or Cloudpaging AI
  • Virtualized via the Cloudpaging Player
  • Managed at scale through Cloudpager, Numecent’s cloud-native enterprise application delivery control plane 

 

Citrix App Packages node enables administrators to discover cloud-hosted application packages via an external source URL and deliver them to Citrix Delivery Groups for seamless access through Citrix Workspace or virtual desktops. 

 

This guide walks through the complete workflow of delivering Cloudpaging containers through Citrix DaaS, including the packaging of Cloudpaging applications (to be taken care of independent of the Citrix Configuration) and hosting containers in Cloudpager (also to be taken care of independent of the Citrix configuration):

  1. Configure Cloudpager components
  2. Configuring a Cloudpager Console URL as a Citrix Discovery Source
  3. Running Citrix App Package Discovery
  4. Assigning Cloudpaging apps to Delivery Groups
  5. Launching Cloudpaging apps via Citrix Workspace

 

Prerequisites 

  • Citrix Requirements 

    • Active Citrix DaaS subscription
    • Citrix VDA 2511 or later
    • A configured Citrix Delivery Group
    • Citrix App packages component on the VDA
    • Endpoint or VDA must have access to Cloudpaging Player (if required for your container type)

    Numecent Requirements 

    • Cloudpaging Studio (for packaging apps) or Cloudpaging AI
    • Cloudpager tenant
    • Ability to upload Cloudpaging containers (.stp files) into Cloudpager

     

    Refer to Numecent’s official documentation for details on packaging applications, installing the Cloudpager client, and setting up appropriate permissions.  

 

1. Configure Cloudpage Components

How to generate Cloudpager API PowerShell key and App Launcher key

Generate Cloudpager API subscription key 

  • Log onto your Cloudpager Admin portal 
  • Go to Settings > API Keys 
  • Click on Add under PowerShell Subscription Keys  

image.png

  • Select an expiration date and time, select role Application Admin then click Add New Key 

image.png

 

 

  • Now you can view or copy your key 

image.png

  

Generate App Launcher Key 

  • Log onto your Cloudpager Admin portal
  • Go to Settings > API Keys
  • Click on Add under App Launcher Keys 

image.png

  • Select an expiration date and time, then click on Add New Key 


image.png

  • Now you can view or copy your key

image.png 

Configure Discovery VDA

Download and Install the Cloudpager PowerShell module 

  • Log into your Cloudpager admin portal
  • Navigate to the Downloads section and download the Cloudpager PowerShell Module
  • Extract Cloudpager folder and copy to C:\Program Files\WindowsPowerShell\Modules
  • Set the execution policy to remote signed: Set-ExecutionPolicy RemoteSigned

 

2. Configure a Cloudpager Console URL as a Discovery Source in Citrix App Packages

Inside the Citrix Manage DaaS Console: 

  1. Navigate to ManageApp Packages
  2. Click Create Discovery Profile


image.png
 

  1. Configure the Discovery Profile:
  • Enter aProfile Name:g., Cloudpager Console Discovery 
  • SelectLocation Type: Numecent Cloudpager 
  • Enter the Cloudpager Console (Admin Portal) URL: e.g., https://<tenant>.cloudpager.net
  • Enter the PowerShell Subscription Key (reference the steps above) 
  • Enter the App Launcher Key (Reference the steps above) 

Citrix now knows where to discover Cloudpaging containers hosted in Cloudpager. 

image.png
 

 

  1. Select a delivery group containing a VDA where the discovery will be processed.

 

  • The VD must have all the necessary prerequisites installed, including the Citrix AppPackaging VDA Component, Numecent’s Cloudpager PowerShell module, and the Cloudpaging Player. The VDA must be powered on and registered.

 

  1. Click Create Discovery Profile
  • A discovery will automatically start when the profile is created, and applications will start to appear in the Packages pane. 

3. Run App Package Discovery

After the source is added: 

  1. Navigate to App Packages → Package Discovery
  2. Select your Cloudpager Console URL source.
  3. Right-Click and select Check for Updates

 

Citrix pulls the Cloudpaging container metadata exposed by Cloudpager, listing: 

  • App name
  • Version
  • Container ID
  • Icon (if provided)
  • Delivery compatibility

 

All discovered Cloudpaging containers now appear in the App Packages tab. 

 

4. Assign Cloudpaging Containers to Delivery Groups

  1. Select a discovered Cloudpaging package.
  2. Click Assign to Delivery Groups
  3. Choose the appropriate Delivery Group(s).
  4. Complete the assignment.

 

The Citrix Delivery Group will now include a Cloudpaging-enabled application that users can launch from: 

  • Citrix Workspace app
  • Browser-based Workspace UI
  • VDI/Hosted shared desktops

 

 Note: VDAs in Delivery Groups must have Cloudpaging Player installed and appropriate access to Cloudpager service URLs

 

5. Launch Cloudpaging Applications via Citrix Workspace or Desktops

End-users see Cloudpaging applications like any other Citrix-provisioned app. 

Behind the scenes: 

  • Citrix handles entitlements and brokering
  • Cloudpager handles streaming and application lifecycle
  • Cloudpaging Player provides application virtualization (if required)

 

Launching the app triggers Cloudpager to deliver the Cloudpaging container to the user session, where it streams and activates instantly. 

 

Issue/Introduction

This guide provided an overview of how Numecent Cloudpaging integrates with Citrix DaaS using the Citrix App Packages workflow: 

  • Cloudpaging containers are packaged in Cloudpaging Studio 
  • Cloudpager hosts and exposes containers via Workpod URLs 
  • Citrix DaaS uses Workpod URLs as discovery endpoints 
  • Citrix discovers Cloudpaging containers automatically 
  • Applications are assigned to Delivery Groups 
  • End-users launch Cloudpaging applications via Workspace or desktops 

This workflow combines the dynamic, lightweight virtualization of Cloudpaging with the global application delivery and access control capabilities of Citrix DaaS, enabling a modern, simplified application management strategy. 

 

Additional Information

Troubleshooting

 

Issue

Suggested Action

Apps not discovered

Verify API keys and Cloudpager URL

Discovery fails

Check RBAC permissions

App not launching

Validate Delivery Group assignment

App missing in StoreFront

Refresh StoreFront or reassign package

 

Cloudpager Service URLs

Below is a list of the Cloudpager URL endpoints that need to be accessible to your clients for Cloudpager and its services to operate across your network. These DNS names may resolve to multiple IP addresses based on geolocation and to ensure high availability of our service.

 

URL

Port

Description

*.cloudpager.net

443

Cloudpager Server and API

*.numecentcloud.com

443

Cloudpaging CDN

ccdn-production-us-east-1-repo.s3-accelerate.amazonaws.com

443

Application Upload Service

ccdn-production-eu-central-1-repo.s3-accelerate.amazonaws.com

443

Application Upload Service (EU home region customers)

 

Remaining User Sessions left Active

When applications are virtualized, the Cloudpaging Player will spawn a CoreHelper.exe process that manages file associates for virtualized applications. When using Cloudpaging with Virtual Apps, this process will cause the Virtual Apps user session to remain active even when the user closes the Virtual Apps application.

 

To resolve this issue and allow the user's session to close/disconnect when the Virtual Apps application is closed the LogOffCheckSysModules registry value can be added (or modified if it is already used within the Virtual Apps environment).

 

More details are available in the Citrix knowledge base article: Graceful Logoff from a Published Application Renders the Session in Active State.

 

Registry Key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI

Value Name

LogoffCheckSysModules

Value Type

REG_SZ

Value Data

CoreHelper.exe