Knowledge Base

Application server - Configuring RemoteApp

Problem

This article provides the steps to enable Application Server functionality in NiceLabel Control Center.

Prerequisites:

  • NiceLabel LMS Enterprise license.
  • Installed Microsoft RemoteApp with an active license on the Windows server. 

Some useful resources on the Microsoft web page:

Complete the steps described in the subsections below.

Solution

Publishing NiceLabel programs

On a computer with enabled RemoteApp role:

  1. Enable WebDAV Redirector features. This was you enable NiceLabel Designer to connect to the Document Storage (WebDAV) on the Control Center. 
  2. Install NiceLabel Designer. 
  3. Set the default directories to point to the Document Storage.
    In tc:\ProgramData\NiceLabel\NiceLabel <version> edit file product.config XML file.
    Update folder names in <Directories/> node.
  4. Activate NiceLabel Designer with the same LMS license key as used in the Control Center.
  5. Start Server Manager.
  6. In the left pane, click Remote Desktop Services.
  7. Click Collections, then on the right side, click TASKS drop-down and select Create Session Collection. Follow the wizard.
  8. Return to the Server Manager and open Publish RemoteApp Programs.
  9. If you do not see NiceLabel Designer and NiceLabel Print in the list, click Add... and browse to \\<remoteapp>\c$\Program Files\NiceLabel\NiceLabel 2017\bin.net.

    Replace the <remoteapp> with the Fully Qualified Domain Name (FQDN) for your RemoteApp server.

    Add NiceLabelDesigner.exe and NiceLabelPrint.exe RemoteApp programs from the bin.net folder: 

    Click Next.
  10. You should see the four selected programs listed in the window. Click Publish.
  11. All programs are now published. Click Close.
  12. All RemoteApp programs are visible in the Server Manager.
  13. Right-click each published program and select Edit properties.

    In the Parameters category, select the option Allow any command-line parameters for each program.
  14. Click OK.

Digitally signing your published applications

Each time you run NiceLabel Designer or NiceLabel Print with a file from your Document Storage, Control Center creates a .RDP file with instructions for the Remote Desktop Client. The .RDP file must be signed with the SSL certificate, or the users see warning messages about unknown publisher when executing the .RDP files.

To configure the digital signature:

  1. Addi certificate on RemoteApp deployment.
  2. Add a certificate for your computer account and allow Control Center to access it.
  3. Bind Control Center with the certificate.
Installing the certificate on the computer

To install the certificate on the computer and allow Control Center to use it, do the following:

  1. Open Console. Press Windows key + R, enter "mmc", then press Enter.
  2. In the Console, click File, then click Add/Remove Snap-in.
  3. In Add or Remove Snap-ins, under Available snap-ins, double-click Certificates.
  4. In Certificates snap-in, select Computer account. Click Next.
  5. Select Local computer, then click Finish.
  6. Click OK.
  7. Expand Certificates (Local Computer) > Personal > Certificates.
  8. Right-click Certificates, then select All Tasks > Import.
  9. Follow the wizard to import the certificate.
  10. Make sure the Certificates node is selected and certificates are listed in the right-hand pane. Select the certificate you created/imported previously.
  11. Right-click the certificate, select All Tasks, then Manage Private Keys.
  12. Click Add… and add the Application Pool user of the Control Center website. Enter the user name IIS AppPool\EPMAppPool.
    Click Locations and select the server name (top selection in the list).
    Click OK.
    Click Check Names to verify the entered user name.
    Click OK.
  13. Select the user and grant Read permission.
  14. Click OK.

    NOTE. If you see an error message Unable to save permission changes and Access is denied your user name doesn't have permissions to manage certificate access rights.
  15. Double click the certificate and go to Details tab.
    Scroll down to find the Thumbprint field.
    Select the certificate thumbprint and copy it to Clipboard.
Adding certificates to RemoteApp deployment

To add certificates for server authentication, single sign-on, and establishing secure connections, do the following:

  1. Start Server Manager.
  2. In the left pane, click Remote Desktop Services.
  3. Click Collections, then on the right-hand side, click TASKS drop-down and select Edit Deployment Properties.
  4. Click the Certificates category in the left-hand menu.
  5. Make sure you have a certificate issued by your Certification Authority (CA) in a file on a disk.
  6. Select the Role Service that is not in Trusted level yet (is not bound with a certificate). Click Select existing certificate...
  7. Select Choose a different certificate, then click Browse.
  8. Select a certificate from a file. Enable Allow the certificate to be added to the Trusted Root Certification Authorities certificate store on the destination computers option.
  9. Click OK.
  10. Click Apply to confirm the changes, then repeat steps 6-10 for all Role Services in the list. In the end, the level must be set to "trusted" and status to "OK".
Binding The Control Center With The Certificate

To configure Control Center to work with the RemoteApp server:

  1. Open your Control Center page and go to the Administration tab.
  2. Go to the Application Server section.
  3. Enable the Enable application server option.
  4. In the Application server URL, enter FQDN name of the RemoteApp server.
  5. In Signing certificate thumbprint, paste the thumbprint from the Clipboard (read the previous section in this chapter).
  6. Click Save changes.
Testing if .RDP file is signed with the certificate
  1. Open Control Center page.
  2. Go to the Document Storage.
  3. Select a label and click the Application Server button in the toolbar.
  4. Select Download Edit Label Shortcut. The .RDP file downloads.
  5. Open the .RDP file in a text editor.
  6. If the .RDP file is correctly signed, it contains additional entries signscope and signature.

Applying a custom remote desktop port number

If the Remote Desktop service runs on a non-default port, update the RDP template file that is used to generate .RDP file for the user.

  1. Navigate to the folder where Control Center is installed. By default, it is installed in:
    c:\Program Files\NiceLabel\NiceLabel Control Center\WEB
  2. Open the template.RDP file in a text editor.
  3. Search for the string:
    server port:i:3389
  4. Replace the default RDP port number 3389 with your custom port number.
  5. Save the file.

Print document   Email document

Feedback

Did this article help you? *