3. Publishing Applications to Users
Configuring Microsoft Windows Application Servers for Printing
Configuring UNIX and Linux Platform Application Servers for Printing
Configuring an SGD Server for Printing
Configuring Printing to Microsoft Windows Client Devices
Configuring Printing to UNIX, Linux, and Mac OS X Platform Client Devices
Users Cannot Print From Applications Displayed Through SGD
Troubleshooting Other Printing Problems
Setting Up Client Drive Mapping
Configuring UNIX and Linux Platform Application Servers for CDM
Configuring an NFS Share for CDM
Starting CDM Processes on the Application Server
Configuring Microsoft Windows Application Servers for CDM
Running UNIX Platform CDM With Another SMB Service
Configuring the Client Drives Available to Users
Troubleshooting Client Drive Mapping
Configuring Microsoft Windows Application Servers for Audio
Configuring UNIX and Linux Platform Application Servers for Audio
Configuring X Applications for Audio
Configuring Client Devices for Audio
Troubleshooting Audio in Applications
Controlling Copy and Paste in 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
Configuring Smart Card Readers on 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
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.
In the Administration Console, go to the Global Settings -> Client Device tab and select the Serial Port Mapping check box.
The Serial Port mapping check box is enabled by default.
In the Administration Console, go to the Client Device tab for an organization, an organizational unit, or a user profile object.
Select the Override Parent’s Settings or Override Global Settings check box.
Set the Serial Port Mapping attribute.
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.