X
17 Rate this article:
No rating

INTERNAL: Licensing a remote display (Windows Terminal Server or Remote Desktop) session of IDL or ENVI

David Blackston
Topic:
Below is an explanation of licensing for remote display sessions of IDL (and ENVI) from a Windows terminal server machine (multi-user Windows system), like Windows 2003 Server. Also included is an explanation of licensing for a "Remote Desktop" session of IDL or ENVI from a *single-user* Windows operating system.Discussion:
Windows Terminal Server Remote Access
On a Windows terminal server type system, like Windows 2003 Server, to access a licensed remote session of IDL (or ENVI), it is necessary to license the installation with license-server-based licensing. That is the license source for the IDL session must be from a license that requires the license manager to run such as a floating network license or from a counted-server-based node-locked license. License files of this type can be identified by the presence of a SERVER line and FEATURESET line, as well as a license unit count in the INCREMENT lines (i.e., a non-zero number after the expiration data)

Unserved Node-locked Licenses
A regular un-served Windows node-locked license (which does not use the FLEXlm/FLEXnet license manager service and does not contain a SERVER line or a FEATURESET line, and the INCREMENT line shows a zero or "uncounted" after the expiration date) will not allow a licensed IDL or ENVI session over a remote connection from a Windows terminal server machine.

TS_OK
In fact, even an un-served license built with a "TS_OK" will not allow a licensed remote IDL or ENVI session from a Windows terminal server machine.

"Remote Desktop" (One-user Machine) Access
An unserved Windows node-locked license built with a TS_OK string will allow "Remote Desktop" (one user machine remote access) IDL or ENVI sessions only from a one-user Windows operating system (such as regular XP, Vista, or 2000). Note that if the machine is enabled for "Fast User Switching" then IDL and ENVI will identify the environment as a multi-user machine and so will require a server-based license instead.Solution:
[Edit this field in the IDL-based Tech Tip Editor, v62]