3. Publishing Applications to Users
Configuring Microsoft Windows Application Servers for Printing
Configuring Printing for Microsoft RDP 5.0 or Later
Configuring the Printers Available in Windows Terminal Services Sessions
Configuring Other Microsoft Windows Application Servers for Printing
Configuring UNIX and Linux Platform Application Servers for Printing
How to Install an SGD Printer Queue on a UNIX or Linux Platform Application Server
The SGD Printer Queue Installation Script
Printing With the SGD lp and lpr Scripts
Configuring an SGD Server for Printing
Checking the Ghostscript Installation on the SGD Host
Using the gstest Script to Test a Ghostscript Installation
Configuring the SGD Host to Accept Remote Print Requests
Configuring SGD Print Job Conversion
Printer Type Configuration Files
The tta_print_converter Script
Configuring Printing to Microsoft Windows Client Devices
The Printer Types Configuration File
Printing From a UNIX or Linux Platform Application Server
Configuring Printing to UNIX, Linux, and Mac OS X Platform Client Devices
Setting a Time Limit for Print Jobs
Users Cannot Print From Applications Displayed Through SGD
Troubleshooting Other Printing Problems
Troubleshooting Printer Preferences and Settings
Current Client Printer Preferences Are Ignored
Changes to Printer Preferences Are Not Remembered
Printer Preferences Are Corrupted
Printer Preferences Are Lost When a User Changes Printers
Local Printer Settings Are Not Set in the Remote Windows Application Session
Printer Settings Are Ignored When Using PDF Printing
Print Jobs Can Be Queued When SGD Printing is Disabled
Fonts Do Not Print Correctly With PDF Printing
TrueType Fonts and Windows Applications
Changing Printer Names in Windows Application Sessions
Changing the Names of the SGD PDF Printers
Users See a Printer Called '_Default' in a Windows Application Session?
Setting Up Client Drive Mapping
Configuring UNIX and Linux Platform Application Servers for CDM
Configuring an NFS Share for CDM
Configuring a Shared Directory on the Application Server
Configuring How Client Drives Are Displayed on UNIX Platforms
Starting CDM Processes on the Application Server
Configuring Microsoft Windows Application Servers for CDM
How to Enable SGD Client Drive Mapping Services
Running UNIX Platform CDM With Another SMB Service
How to Run UNIX Platform CDM and Another SMB Service on the Same Host
Configuring the Client Drives Available to Users
Configuring the Drives Available to UNIX, Linux, and Mac OS X Platform Client Devices
An Example of Configuring Drive Availability for Users
Troubleshooting Client Drive Mapping
Removable Drives Attached During a User Session are Not Detected Automatically
Invalid Password Errors on Microsoft Windows Application Servers
More Client Drives Are Mapped Than Expected
The Recycle Bin Does Not Work As Expected
Mapped Drives Have Unusual Names
CDM Limitations for Shared Users
Disabling CDM for a Client Device
Enabling CDM Logging for the SGD Array
CDM Diagnostics for Microsoft Windows Application Servers
CDM Diagnostics for UNIX or Linux Platform Application Servers
SGD Client Logging for Client Devices
Configuring Microsoft Windows Application Servers for Audio
Configuring UNIX and Linux Platform Application Servers for Audio
Configuring X Applications for Audio
How to Enable the SGD Windows Audio Service
How to Enable the SGD UNIX Audio Service
Configuring Client Devices for Audio
Troubleshooting Audio in Applications
Enabling UNIX Audio Debug Logging
Controlling Copy and Paste in Applications
Configuring Global Copy and Paste Settings for the SGD Array
Configuring Copy and Paste for Specific Users
Configuring Copy and Paste for Specific Applications
An Example of Using Clipboard Security Levels
Tips on Configuring Copy and Paste
Copy and Paste Troubleshooting
Using Smart Cards With Windows Applications
Setting Up Access to Smart Cards
Configuring the Microsoft Windows Application Server for Smart Cards
Application Server Authentication Dialog Settings
How to Enable Smart Cards in SGD
Configuring Smart Card Readers on Client Devices
Microsoft Windows Client Devices
Linux Platform and Solaris OS Client Devices
How to Log In to a Microsoft Windows Application Server With a Smart Card
Setting Up Access to Serial Ports
Configuring the Microsoft Windows Application Server
Enabling Serial Port Access in SGD
7. SGD Servers, Arrays, and Load Balancing
B. Secure Global Desktop Server Settings
This section describes how to set up access to serial ports for Windows applications displayed through SGD.
This section includes the following topics:
Setting up access to serial ports involves the following configuration steps:
Enable COM port mapping on the application server.
Enable access to serial ports for SGD users.
Configure the client device for serial port access.
You can only access serial ports if COM port mapping is enabled on
the Windows Terminal Server. See Configuring Microsoft Windows Terminal Services for Use With SGD for details of the Windows platforms that
support COM port mapping.
Access to serial ports is enabled for all users by default. If serial port access is disabled, you can enable access to serial ports for all users, or for specific users.
When a user starts a Windows application, SGD checks the user profile for the user and then any parent object further up the organizational hierarchy to see whether access to serial ports is enabled or disabled. If all the objects checked are configured to use the parent’s setting, then the global setting is used.
Firewalls between SGD servers can interfere with the connections required for serial ports,
seeFirewalls Between SGD Servers.
The Serial Port mapping check box is enabled by default.
To enable access to serial ports, select the Enabled check box. To disable access to serial ports, deselect the Enabled check box.
If you configure an organization or organizational unit object, this affects all the users in that organization or organizational unit.
Note - The changes made only take effect for new user sessions.
To determine the serial ports that are mapped in the Windows Terminal Services session, you might have to configure the client device.
On UNIX and Linux client platforms, users must have read and write access to any serial device that is mapped. SGD uses the first match of the following:
The serial ports listed in the SUN_MAP_SERIALPORTS environment variable.
Each serial port in the list is separated with a semi-colon and has the format serial device=com-port-name. For example:
/dev/ttyS0=COM1;/dev/ttyS4=COM8
The =com-port-name part is optional, but if it is omitted the serial port is mapped to COMx in the Windows application session, where x is the position of the serial port in the list.
The serial ports listed in the user’s client profile.
The <serialports> entry in the <localsettings> section of the user’s client profile lists the serial ports to be mapped. See Client Profile Settings.
The <serialports> entry has to be added manually.
The serial ports are listed in the same format as above.
![]() | Caution - If a user has not edited their client profile, any manual changes made to the profile.xml file are lost when the user next logs in. |
The serial port listed in the SUN_DEV_SERIAL environment variable.
This is a single serial device, for example /dev/ttyS2. This is always mapped to COM1 in the Windows application session.
On Microsoft Windows client platforms, SGD uses the first match of the following:
The serial ports listed in the user’s client profile.
The <serialports> entry in the <localsettings> section of the user’s client profile lists the serial ports to be mapped. See Client Profile Settings.
The <serialports> entry has to be added manually.
Each serial port in the list is separated with a semi-colon and has the format serial device=com-port-name.
COM1=COM5;COM2=COM8
The =com-port-name part is optional, but if it is omitted the serial port is mapped to COMx in the Windows application session where x is the position of the serial port in the list.
![]() | Caution - If a user has not edited their client profile, any manual changes made to the profile.xml file are lost when the user next logs in. |
Any available COM1 to COM9 ports.
The SGD Client attempts to open ports COM1 to COM9. If a COM port is found, it is mapped to the same COM port number in the Windows application session.