Problem
If using the Payment Terminal on a Windows Remote Desktop/RemoteApp, Citrix XenDesktop/XenApp, or other multi-seat/multi-head products, the Payment Terminal may need to be configured for this type of environment.
Solution
A handful of changes are recommended for server installations, described below.
Enable "Server Installation" mode
The Payment Terminal will need to be configured to run in server mode, which allows multiple copies of the program to run at once (as well as optimizing itself for multi-seat environments).
The procedure to accomplish this is mentioned in the installation guide.
Open Payment Terminal with QuickBooks
The Payment Terminal can be configured as an event listener to QuickBooks, which will launch the Payment Terminal whenever QuickBooks is opened. Note that this is only recommended for server environments, as performance may be impacted otherwise.
Open an administrative Command Prompt window.
Open the Start Menu, type cmd, and press Ctrl-Shift-Alt-Enter. This launches a Command Prompt window with administrative privileges.
Register the Payment Terminal as a COM server.
Run the command "C:\Program Files (x86)\Payment Terminal\Payment_Terminal.exe" -regserver and close the Command Prompt window when finished.
This command may need to be modified depending on your installation path for the Payment Terminal.
Open a non-administrative Command Prompt window.
Open the Start Menu, type cmd, and press Enter. This launches a Command Prompt window.
Subscribe the Payment Terminal to QuickBooks events.
Run the command "C:\Program Files (x86)\Payment Terminal\Payment_Terminal.exe" -subscribe and close the Command Prompt window when finished.
This command may need to be modified depending on your installation path for the Payment Terminal.
Restart current user sessions (if needed).
Affected users may need to log off of Windows to see changes take affect.
Add Payment Terminal registry key
Depending on your environment, the Payment Terminal may prompt for an update/installer every time it's launched. If so, it may be necessary to add the Payment Terminal data to each user's registry.
Open the Registry Editor.
Open the Start Menu, type regedit, and press Enter.
Find the Payment Terminal registry keys
Navigate to HKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Verosa, LLC. (or HKEY_CURRENT_USER\SOFTWARE\Verosa, LLC. if on a 32-bit architecture). If the key exists, right-click on it, and click Export.
Depending on your environment, a similar key may exist in HKEY_LOCAL_MACHINE - if this is the case, disregard this section.
Add the exported registry keys to affected users.
The exported keys need to be present in each user's registry. These keys can be distributed in a variety of ways:
- Open the registry editor on each affected user, and import the keys from there.
- Create a login script/group policy object to add the exported keys to affected/all users.
- Import a copy of the exported keys, and move them to the
HKEY_LOCAL_MACHINEhive.
Deploy remote application (if needed)
If using RemoteApp, XenApp, or another remote application system, the Payment Terminal will need to be added to your system. As this is implementation specific, consult your remote application system's documentation for information on accomplishing this.
Comments
0 comments
Article is closed for comments.