Secure Signatures
Secure Signatures and Terminal Services
|
Nancy Administrator Posts: 765
12/29/2011
|
NancyAdministrator Posts: 765
PrintBoss Secured Signature Disks are designed to be read at a drive letter (or letters) specified in the command in the PrintBoss form. If PrintBoss can resolve the presence of the media at the appropriate drive letter, it then “unlocks” the file to enable it to be viewed and/or printed.
A common difficulty that signature users encounter is that if the user is logging in via a terminal server, their local disk drives may not be accessible as drive letters within the terminal server session. One solution to this issue is to map the user’s applicable local drive to a drive letter within the session, but if that proves unfeasible, there is an alternate option to attempt.
Within the dialog for the #Pic (or #SIG or #PCX) command in the PrintBoss form file, there is a text box labeled “Sig Disk Drive Letters” that specifies a list of letters for which the command will check the corresponding drives. A common entry would be something like “DEFGA,” which means that PrintBoss will check the local D:. E:, F:, G:, and A: drives for the presence of the signature disk. In the situation where such a direct drive mapping is not feasible, an alternate way to specify the local drive would be to use the \\tsclient\ modifier.
For example, if the user has a USB drive that appears as their E drive in their own Windows environment, but are logging into a terminal server session where that drive is not visible, you may consider using the following text in the Sig Disk Drive Letters box: \\tsclient\E
If a user’s drive could be one of multiple letters, you could have PB check for them by repeating that syntax but separating each instance with semicolons. For example: \\tsclient\E;\\tsclient\F
This will have PrintBoss attempt to check the local user’s E and F drives.
PLEASE NOTE: We have found that this solution will work for some, but may not work for all situations.
|
|
|
0
link
|