Scriptel Wiki - User contributions [en]

Using Citrix XenApp USB Forwarding

2018-05-31T17:50:28Z

William Powell: /* Configuring Citrix XenApp/XenDesktop Policy */

{{#ev:youtube|DidB8d1_LxQ}}

==Requirements==
*Citrix XenApp 7.6+ / XenDesktop 5.6+
*Citrix Receiver 4.2+
*VDA Running Windows Server 2012 R2 or Higher

==Configuring Citrix XenApp/XenDesktop Policy==
[https://support.citrix.com/article/CTX137939 https://support.citrix.com/article/CTX137939]
*Start Citrix Studio
*Go to "Policies" on the left-hand side.
*Either edit an existing policy, or create a new policy.
*Edit "Client USB device redirection", set it to "Allowed".
*Edit "Client USB device redirection rules", click "New" and type: "Allow: VID=18FB" (space and capitalization is important, no quotes).
**If you wish to also include the PID in your redirection rule, please view our list of [[ScripTouch USB IDs|USB IDs]].
*Click "Finish" and close Citrix Studio.

==Configuring Automatic Device Forwarding==
[https://support.citrix.com/article/CTX123015 https://support.citrix.com/article/CTX123015]

===Using Group Policy===
[https://www.citrix.com/downloads/citrix-receiver/windows/receiver-for-windows-latest.html Citrix Group Policy Extensions Download]
*Open the group policy editor for the policy controlling your Citrix Receiver client's.
*Go to Administrative Templates -> Citrix Components -> Citrix Receiver -> Remoting client devices -> Generic USB Remoting (if this is missing you need the Citrix Group Policy Extensions, see [https://docs.citrix.com/en-us/receiver/windows/4-3/ica-overview-receiver-config/ica-import-icaclient-template-v2.html here]).
*Open "New USB Devices", select "Enabled", click "OK".
*Open "Existing USB Devices", select "Enabled", click "OK".
*If you need to restrict which devices get automatically forwarded, open "USB Device Rules", add the required rules and hit "OK".
*Run "gpupdate /force" as an administrator on the client computer you're testing on to make sure you have the newest version of the policy.

===Using the Registry===
*Create a new key located at: HKLM\SOFTWARE\Citrix\ICA Client\GenericUSB\Devices\VID18FB PID0200 (replace PID0200 with the product id for the product you're looking to forward).
*Create a new DWORD value named "AutoRedirect" and set it to "1".

==Troubleshooting==

===Receiver Drivers===
*Citrix Receiver installs two drivers to support USB forwarding functionality
*In a command prompt run: driverquery
*A list of installed drivers should display and look like this:
[[File:Driverquery.png]]
*Verify that both ctxusbm and Ctxusbr are in the list
*If a driver is missing, attempt a reinstall of Citrix or contact support to attempt to resolve the missing driver issue

ScripTouch USB IDs

2018-05-31T17:43:14Z

William Powell:

Various different USB utilities will require the appropriate vendor and product ID's for ScripTouch Devices. Below is a table of all ScripTouch devices with their vendor and product ids.

{| class="wikitable"
! Model
! Firmware
! Vendor ID
! Product ID
|-
| [[ST1400]]
| All
| 18fb
| 0204
|-
| [[ST1401-STN]]
| >= 4.0.0
| 18fb
| 0246
|-
| [[ST1401-STN]]
| < 4.0.0
| 18fb
| 01c5
|-
| [[ST1475]]
| All
| 18fb
| 0206
|-
| [[ST1476-STN]]
| >= 4.0.0
| 18fb
| 0244
|-
| [[ST1476-STN]]
| < 4.0.0
| 18fb
| 01c9
|-
| [[ST1500]]
| All
| 18fb
| 0200
|-
| [[ST1500B]]
| All
| 18fb
| 0208
|-
| [[ST1501-STN]]
| >= 4.0.0
| 18fb
| 0240
|-
| [[ST1501-STN]]
| < 4.0.0
| 18fb
| 01c0
|-
| [[ST1501B-STN]]
| >= 4.0.0
| 18fb
| 0241
|-
| [[ST1525]]
| All
| 18fb
| 0202
|-
| [[ST1526-STN]]
| >= 4.0.0
| 18fb
| 0242
|-
| [[ST1526-STN]]
| < 4.0.0
| 18fb
| 01c1
|-
| [[ST1550]]
| All
| 18fb
| 0201
|-
| [[ST1551-STN]]
| >= 4.0.0
| 18fb
| 0243
|-
| [[ST1551-STN]]
| < 4.0.0
| 18fb
| 01c6
|-
| [[ST1570]]
| All
| 18fb
| 0207
|-
| [[ST1571-STN]]
| >= 4.0.0
| 18fb
| 0245
|-
| [[ST1571-STN]]
| < 4.0.0
| 18fb
| 01cb
|}

ScripTouch USB IDs

2018-05-31T17:40:43Z

William Powell:

Various different USB utilities will require the appropriate vendor and product ID's for ScripTouch Devices. Below is a table of all ScripTouch devices with their vendor and product ids.

{| class="wikitable"
! Model
! Firmware
! Vendor ID
! Product ID
|-
| [[ST1400]]
| All
| 18fb
| 0204
|-
| [[ST1401-STN]]
| All
| 18fb
| 01c5
|-
| [[ST1475]]
| All
| 18fb
| 0206
|-
| [[ST1476-STN]]
| >= 4.0.0
| 18fb
| 0244
|-
| [[ST1476-STN]]
| < 4.0.0
| 18fb
| 01c9
|-
| [[ST1500]]
| All
| 18fb
| 0200
|-
| [[ST1500B]]
| All
| 18fb
| 0208
|-
| [[ST1501-STN]]
| >= 4.0.0
| 18fb
| 0240
|-
| [[ST1501-STN]]
| < 4.0.0
| 18fb
| 01c0
|-
| [[ST1501B-STN]]
| >= 4.0.0
| 18fb
| 0241
|-
| [[ST1525]]
| All
| 18fb
| 0202
|-
| [[ST1526-STN]]
| >= 4.0.0
| 18fb
| 0242
|-
| [[ST1526-STN]]
| < 4.0.0
| 18fb
| 01c1
|-
| [[ST1550]]
| All
| 18fb
| 0201
|-
| [[ST1551-STN]]
| >= 4.0.0
| 18fb
| 0243
|-
| [[ST1551-STN]]
| < 4.0.0
| 18fb
| 01c6
|-
| [[ST1570]]
| All
| 18fb
| 0207
|-
| [[ST1571-STN]]
| >= 4.0.0
| 18fb
| 0245
|-
| [[ST1571-STN]]
| < 4.0.0
| 18fb
| 01cb
|}

Epic Registry Values

2018-04-30T14:26:52Z

William Powell:

This article covers the registry values that are available for use with ScripTouch for Epic Hyperspace. All keys unless otherwise stated require ScripTouch for Epic Hyperspace version 3.2.89 or greater to use.

All registry values discussed in this article will require you to either navigate to or create the following registry key:

*Windows 32-bit: HKLM\Software\Scriptel Corporation\Epic
*Windows 64-bit: HKLM\Software\WOW6432Node\Scriptel Corporation\Epic

=Screen Lock Values=

==ScreenLockPrevent==
* DWORD
* Default 'No' (0)
* Determines if the graffiti lock screen will be used or not.
* Value overrides PreventScreenLock if present.

==ScreenLockToggleBacklight==
* DWORD
* Default 'Yes' (1)
* Toggles the backlight between on and off when the screen lock is in use.

==ScreenLockMessage==
* REG_SZ
* Default "Please wait for signature prompt."
* Single line of text (~40-50 characters recommended limit) organization can use to customize lock screen message.

==Legacy Values==

===PreventScreenLock===
* DWORD
* Default 'No' (0)
* Requires version 3.2.47 or greater (Deprecated as of 3.2.87)
* Determines if the graffiti lock screen will be used or not.

=Signature Pad Display Values=

==EnableSigPadLine==
* DWORD
* Default 'No' (0)
* When enabled, draws a signature line on the screen.

==EnableSigPadButtons==
* DWORD
* Default 'Yes' (1)
* When enabled, draws navigation buttons on the screen.

Epic Registry Values

2018-04-30T13:48:13Z

William Powell: Created page with "This article covers the registry values that are available for use with ScripTouch for Epic Hyperspace. All keys unless otherwise stated require ScripTouch for Epic Hyperspace..."

This article covers the registry values that are available for use with ScripTouch for Epic Hyperspace. All keys unless otherwise stated require ScripTouch for Epic Hyperspace version 3.2.87 or greater to use.

All registry values discussed in this article will require you to either navigate to or create the following registry key:

*Windows 32-bit: HKLM\Software\Scriptel Corporation\Epic
*Windows 64-bit: HKLM\Software\WOW6432Node\Scriptel Corporation\Epic

=Screen Lock Values=

==ScreenLockPrevent==
* DWORD
* Default 'No' (0)
* Determines if the graffiti lock screen will be used or not.
* Value overrides PreventScreenLock if present.

==ScreenLockToggleBacklight==
* DWORD
* Default 'Yes' (1)
* Toggles the backlight between on and off when the screen lock is in use.

==ScreenLockMessage==
* REG_SZ
* Default "Please wait for signature prompt."
* Single line of text (~40-50 characters recommended limit) organization can use to customize lock screen message.

==Legacy Values==

===PreventScreenLock===
* DWORD
* Default 'No' (0)
* Requires version 3.2.47 or greater (Deprecated as of 3.2.87)
* Determines if the graffiti lock screen will be used or not.

=Signature Pad Display Values=

==EnableSigPadLine==
* DWORD
* Default 'No' (0)
* When enabled, draws a signature line on the screen.

==EnableSigPadButtons==
* DWORD
* Default 'Yes' (1)
* When enabled, draws navigation buttons on the screen.

Prevent Epic from Locking Signature Pad

2018-04-27T15:33:54Z

William Powell:

A graffiti block feature added in the ScripTouch for Epic plugin version 3.2.47 and higher automatically locks the signature pad after signing is complete. This is done to prevent user confusion about whether the pad is supposed to be signed yet or not. Since this change may break customer workflows there is a way to disable this new feature.

Navigate to or create the following registry key:
*Windows 32-bit: HKLM\Software\Scriptel Corporation\Epic
*Windows 64-bit: HKLM\Software\WOW6432Node\Scriptel Corporation\Epic

Once you're at the key, create a new DWORD value called PreventScreenLock and set the value to:
*0x01 - Screen lock is disabled, mirroring the old default behavior.
*0x00 - Screen lock is enabled, the new default that locks the pads.

[[File:Epicregedit.png]]

Troubleshooting ScripTouch for Epic

2017-07-25T18:48:19Z

William Powell:

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016/2017]
| ScriptelDevice.3
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2018 2018]
| ScriptelDevice.4
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 VMware Guide] to set up and troubleshoot Horizon View USB redirection issues.

VMware Horizon View 5.0+ supports USB redirection.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Beta Features==
===Annotation and Timestamp===
This feature has been added as of Version 3.1.66 (September 23rd, 2016). When activated, it will bake the annotation and timestamp into the signature.

To activate this feature, please do the following:
*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corporation\Epic'
**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corporation\Epic'
*Change the value 'useAnnotations' from '0' to '1'
To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.

Do note that this feature will NOT add annotations and timestamps to pre-existing signatures.

Citrix Ready

2017-06-20T17:56:30Z

William Powell:

The Citrix Ready® program makes it easy for customers to identify complementary products and solutions that can enhance Citrix environments. Customers can be confident that [[Scriptel]] signature pads have successfully passed a series of tests established by Citrix, and can be trusted to work effectively with Citrix XenApp and XenDesktop in order to deliver high-quality handwritten signatures to electronic documents, avoid error-prone and expensive print-sign-scan interactions with customers and vendors, and get that much closer to having a completely paperless operation.

The Citrix Ready program helps customers identify third-party solutions that are recommended to enhance virtualization, networking and cloud computing solutions from Citrix Systems, Inc. The Scriptel signature pads completed a rigorous verification process to ensure compatibility with Citrix XenApp and XenDesktop virtualization systems, providing confidence in joint solution compatibility.

{| class="wikitable"
!XenDesktop || EasyScript || ProScript
|-
|7.6+ || Yes || Yes
|-
|7.5 || Yes || Yes
|-
|7.1 || Yes || Yes
|-
|7.0 || Yes || Yes
|-
!XenApp || EasyScript || ProScript
|-
|7.6+ || Yes || Yes
|-
|7.5 || Yes ||Requires installation of [[ScripTouch Remote]]
|-
|7.1 || Yes ||Requires installation of [[ScripTouch Remote]]
|-
|7.0 || Yes ||Requires installation of [[ScripTouch Remote]]
|-
|6.5 || Yes ||Requires installation of [[ScripTouch Remote]]
|-
|6.0 || Yes ||Requires installation of [[ScripTouch Remote]]
|}

Using EasyScript with Citrix

2017-02-24T20:12:32Z

William Powell:

ScripTouch devices using the EasyScript protocol can be used with Citrix solutions (XenApp and XenDesktop) without the need for any USB redirection software. Depending on your environment there are some considerations that may need to be made in order for EasyScript to work reliably.

==Slowing Down Keyboard Output==
Some environments will require you to slow down the keyboard output speed of your ScripTouch device. This can be done by using the [[ScripTouch Toolbox]]:
*Open the ScripTouch Toolbox, go to the "Output" tab.
*Move the "Packets per Second" slider between 100-250 packets per second (exact value may depend on your environment).
*Optionally (if your application supports it) checking the "Stream output" and "Compress output" boxes should improve reliability and speed.

After adjusting the slider test the signature pad again using the [https://ny.scriptel.com/easyscript/ diagnostic utility]. This setting will persist even if the device is powered off or unplugged. You only need to do this once per ScripTouch device.

==Configure Citrix Receiver to Buffer Keyboard Output==
In cases, Citrix keyboard forwarding can limit the amount of packages sent over the connection, requiring ScripTouch devices to further slow down. Below is a solution to buffer the inputs into fewer, denser packets:
#In C:\Program Files (x86)\Citrix\ICA Client\appsrv.ini: Change KeyboardTimer property from 0 to 50.
#Do one of the following:
#*In C:\Users\<username>\AppData\Roaming\ICAClient\APPSRV.ini: Change KeyboardTimer property from 0 to 50.
#; OR
#*Delete Folder C:\Users\<username>\AppData\Roaming\ICAClient. On Receiver restart, this folder will be recreated with the changed property.

These changes will require restarting Citrix Receiver. To guarantee this happens, we recommend restarting the client PC.

Scriptel provides a PowerShell Script that configures these options [https://ny.scriptel.com/customer/easyscript-citrix.ps1 here].

Using EasyScript with Citrix

2017-02-24T20:08:23Z

William Powell: Created page with "ScripTouch devices using the EasyScript protocol can be used with Citrix solutions (XenApp and XenDesktop) without the need for any USB redirection software. Depending on your..."

EasyScript

2017-02-24T19:50:09Z

William Powell: /* Troubleshooting */

EasyScript was built from the ground up to enable a simple and convenient way to capture electronic signatures and magnetic card swipe data (on supported devices) from a wide variety of usages including web-based and traditional applications.

This interface excels at providing an extremely simple and portable integration that does not require any software or drivers to be installed to run your application.

====Simple Integration====
Traditionally communicating with attached peripherals from applications (particularly web applications) is problematic. Many web based solutions use Java applets or ActiveX controls that allow a web application to access an attached signature digitizer. This approach creates work for individuals maintaining this type of software because these plugins require constant security and compatibility updates. Failure to apply these updates can leave systems with these plugins installed insecure which potentially compromises the security of the network. On the other hand, applying these updates occasionally will break software requiring updates to the application to fix new incompatibilities.

The EasyScript interface mitigates this problem by communicating with the computer as if it were a keyboard. Nearly any application implemented on most platforms can communicate with keyboards without plugins. [[Scriptel]] provides API’s and documentation for capturing the keyboard data from a wide variety of different programming languages in order to simplify application development.

====Simple Portability====
A common issue with application development is the problem of how to deploy the application when it’s done and how to update it once it’s installed on the end user’s machine. Today’s application ecosystem includes many operating systems, architectures, platforms, devices, and web browsers. In order to support these different technologies developers take advantage of cross platform languages and interfaces to reduce the cost to support the diverse devices their application needs to run on.

To this end [[Scriptel Corporation| Scriptel's]] EasyScript again takes advantage of the fact nearly all devices support USB keyboards. Software written for EasyScript ScripTouch devices can be easily integrated into platform independent applications.

==Changes with version 2.0==
*Compression
*More resolution can be transmitted (now matching our ProScript interface at 500 dpi and 120 samples per second) using similar number of keystrokes
*Signature data streaming
*Data is now sent out as soon as signing starts, OK and Cancel buttons now explicitly detected
*Automatic adapt to keyboard layout
*Signature preamble provides minimum number of keystrokes for the API to adapt to whatever keyboard layout is the current setting in the OS
*Toolbox settings for compression and keystroke packet transmission rate
*Signature data buffer in pad automatically resets after 30 seconds of inactivity
*Signature data streaming (for “real-time signature rendering”)
*Higher resolution signature data (for “biometrics” or “forensics” capability)
*Automatic international keyboard support
*Explicitly detect OK and Cancel

==Models with EasyScript==

*[[ScripTouch Slimline 1×5 Signature Pad|ScripTouch Slimline 1×5 ST1476]]

*[[ScripTouch Compact LCD Signature Pad|ScripTouch Compact LCD ST1551]]

*[[ScripTouch Magstripe LCD Signature Pad|ScripTouch Magstripe LCD ST1526]]

*[[ScripTouch Desktop LCD Signature Pad|ScripTouch Desktop LCD ST1501]]

*[[ScripTouch Desktop 1×5 Signature Pad|ScripTouch Desktop 1×5 ST1401]]

*[[ScripTouch Slimline LCD Signature Pad|ScripTouch Slimline LCD ST1571]]

==Troubleshooting==

*[[Troubleshooting EasyScript Devices]]
*[[Using EasyScript Devices with Remote Desktop]]
*[[Using EasyScript with Citrix]]

Troubleshooting ScripTouch for Epic

2016-09-23T16:08:03Z

William Powell: /* Annotation and Timestamp */

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016]
| ScriptelDevice.3
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 Citrix Guide] to troubleshoot Horizon View USB redirection issues.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Beta Features==
===Annotation and Timestamp===
This feature has been add as of Version 3.1.66 (September 23rd, 2016). When activated, it will bake the annotation and timestamp into the signature.

To activate this feature, please do the following:
*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corperation\Epic'
**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corperation\Epic'
*Change the value 'useAnnotations' from '0' to '1'
To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.

Do note that this feature will NOT add annotations and timestamps to pre-existing signatures.

Troubleshooting ScripTouch for Epic

2016-09-19T20:12:38Z

William Powell: /* Beta Features */

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016]
| ScriptelDevice.3
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 Citrix Guide] to troubleshoot Horizon View USB redirection issues.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Beta Features==
===Annotation and Timestamp===
This feature has not been added yet. When activated, it will bake the annotation and timestamp into the signature.

To activate this feature, please do the following:
*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corperation\Epic'
**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corperation\Epic'
*Change the value 'useAnnotations' from '0' to '1'
To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.

Do note that this feature will NOT add annotations and timestamps to pre-existing signatures.

Troubleshooting ScripTouch for Epic

2016-09-19T20:11:48Z

William Powell: /* Annotation and Timestamp */

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016]
| ScriptelDevice.3
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 Citrix Guide] to troubleshoot Horizon View USB redirection issues.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Beta Features==
===Annotation and Timestamp===
This feature has not been added yet. When activated, it will bake the annotation and timestamp into the signature.

To activate this feature, please do the following:
*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corperation\Epic'
**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corperation\Epic'
*Change the value 'useAnnotations' from '0' to '1'
To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.

Do note that this feature will NOT add annotations and timestamps to existing signatures.

Troubleshooting ScripTouch for Epic

2016-09-19T20:08:05Z

William Powell:

[[Category:Epic Hyperspace]]
ScripTouch for Epic is a piece of software designed to allow ScripTouch Signature pads to work with Epic Hyperspace.

==Installation==
Installation has to be done with your Epic Hyperspace support representative. You will need to install the software on your Epic Hyperspace server and you'll need to know the correct ProgId for ScripTouch for Epic prior to engaging Epic.

The ProgIds for ScripTouch for Epic are as follows:
{| class="wikitable"
! Hyperspace Version
! ProgId
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2012 2012]
| ScriptelDevice.0
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2014 2014]
| ScriptelDevice.1
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2015 2015]
| ScriptelDevice.2
|-
| [https://services.scriptel.com/releases/scriptouch-epic/scriptel-hyperspace-2016 2016]
| ScriptelDevice.3
|}

==Debugging Remote Connections==
Typically Hyperspace is run on a server and clients connect to that server to run the Hyperspace application. In cases like this it becomes necessary to forward signature pads to the remote server in order for them to be useful with Epic. There are various ways to accomplish this.

===Citrix XenApp/XenDesktop===
Citrix XenApp in versions 7.6 and higher as well as XenDesktop 7 and higher natively support USB redirection. Older versions are supported through the use of [[ScripTouch Remote]].
{| class="wikitable mw-collapsible mw-collapsed"
! XenApp Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[ScripTouch Remote]]
|-
| 6.5
| Yes
| [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

{| class="wikitable mw-collapsible mw-collapsed"
! XenDesktop Version
! Supported
! Method
|-
| 7.8
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.7
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.6
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.5
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.1
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 7.0
| Yes
| [[Using Citrix XenApp USB Forwarding|Native]] / [[ScripTouch Remote]]
|-
| 5.x
| No
| N/A
|}

In the event you're using ScripTouch Remote you can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot remote pad redirection. If you're using native Citrix redirection you can check your setup against the [[Using Citrix XenApp USB Forwarding]] guide.

===Microsoft Remote Desktop===
Microsoft Remote Desktop USB redirection is supported through the use of [[ScripTouch Remote]]. You can use the [[Troubleshooting ScripTouch Remote on Windows]] guide to troubleshoot issues with Microsoft RDP.

===VMware Horizon View===
VMware Horizon View natively supports USB redirection. You can use this [https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026991 Citrix Guide] to troubleshoot Horizon View USB redirection issues.

===Wyse TCX===
Wyse TCX natively supports USB redirection. You can use this [http://www.thinclient24.eu/productattachments/index/download?id=121 Wyse Guide] to troubleshoot Wyse TCX USB virtualization.

==Creating Debug Logs==
The ScripTouch for Epic plugin supports debugging in the event something goes wrong. You can turn on forwarding by doing the following on your Hyperspace server:
*Open the system Environment Variable editor as outlined in [http://www.computerhope.com/issues/ch000549.htm this guide].
*Under 'System variables' click the 'New...' button.
*For 'Variable name' put 'SCRIPTEL_DEBUG' and for 'Variable value' put '1' (case matters).
*Hit 'OK' then hit 'OK'.
*Restart Hyperspace.

Once the environment variable is in place and Hyperspace has been restarted the following files should be created when the Scriptel for Epic plugin is used:
*%TEMP%\scriptel-hyperspace_debug-log.txt
*%TEMP%\scriptel-debug-proscript-<pid>.log

These logs can be sent to Scriptel support to help debug problematic issues.

==Create Dump File==
In the case of more exotic issues with ScripTouch for Epic it may be necessary to create a dump file to send to Scriptel support. The dump file should be created at the point that the problematic event is occurring if at all possible. This can be done one of two ways described below. Dump files can be rather large, please contact [[Scriptel Support]] if you need assistance transmitting the file(s).

===Create Dump File with Task Manager===
If Hyperspace continues to run while the exceptional condition (freezing, hanging, slowness, etc) is present the easiest way to create a dump file is with Task Manager:
*Start Task Manager by hitting Ctrl - Alt - Delete and clicking "Task Manager".
*Find Epic Hyperspace in the Processes tab, right click and hit "Create Dump File".
*A dialog will appear containing the path to the created dump file, typically it will be in %TEMP%. Make note of the file location and name.
*Hit 'Windows' + R, type '%TEMP%' and hit 'OK'.
*A file browser will appear, find the file you noted earlier in this window and send this file to Scriptel support.

===Create Dump File with Registry Settings===
If Hyperspace is crashing (the window disappears, or a window appears that indicates Hyperspace has crashed) the easiest way to create a dump file is the following:
*Using the Registry Editor, create a key located at 'HKLM\SOFTWARE\Microsoft\Windows\Windows Error Reporting\LocalDumps'.
*Start Hyperspace and use it until it crashes.
*Hit 'Windows' + R, type '%LOCALAPPDATA%\CrashDumps', and hit 'OK'.
*Collect the dump file for Hyperspace in this location and send it to Scriptel support.

Microsoft documentation describing this feature is available [https://msdn.microsoft.com/en-us/library/windows/desktop/bb787181%28v=vs.85%29.aspx here].

==Beta Features==
===Annotation and Timestamp===
This feature has not been added yet. When activated, it will bake the annotation and timestamp into the signature.

To activate this feature, please do the following:
*Using the Registry Editor, locate the key at 'HKLM\SOFTWARE\Scriptel Corperation\Epic'
**If using a 64-bit OS, the key will be located at 'HKLM\SOFTWARE\WOW6432Node\Scriptel Corperation\Epic'
*Change the value 'useAnnotations' from '0' to '1'
To deactivate this feature, locate the key in the Registry Editor and change the value back to '0'.