CMS over Microsoft Remote Desktop
From NewHaven Software Wiki
(Created page with 'Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running …') |
|||
| Line 1: | Line 1: | ||
Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running CMS over RDP, here we will discuss them and provide solutions. | Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running CMS over RDP, here we will discuss them and provide solutions. | ||
| - | * '''Note:''' You'll want to have the most current version of Remote Desktop Connection for this to work as expected. Also note, that while these solutions have been tested and work, | + | * '''Note:''' You'll want to have the most current version of Remote Desktop Connection for this to work as expected. Also note, that while these solutions have been tested and work, Remote Desktop is a 3rd party application. As a result we do not provide direct support for it. |
== Printing == | == Printing == | ||
Revision as of 01:06, 25 January 2014
Remote Desktop, sometimes refered to as RDP allows a client to connect to a remote machine as though they were sitting in front of it. With CMS there are some hurdles to running CMS over RDP, here we will discuss them and provide solutions.
- Note: You'll want to have the most current version of Remote Desktop Connection for this to work as expected. Also note, that while these solutions have been tested and work, Remote Desktop is a 3rd party application. As a result we do not provide direct support for it.
Contents |
Printing
- Open remote desktop connection
- Click on the Options >> button to open more options
- Click on the Local Resources tab
- Make sure Printers is checked.
After setting these configurations, you'll want to save the connection.
- Click on the General tab
- Click Save or Save As if this is a new connection
Note: In order for most printers to work on Remote Desktop, they need to be installed on the host system, the computer you are connecting to.
Once the printers are configured and tested in windows, you can configure your workstation settings to use those new printers.
Scale
Com ports can be finicky some time. If you can't get them working restart both the host and client system to reset the ports.
- Open remote desktop connection
- Click on the Options >> button to open more options
- Click on the Local Resources tab
- Click on the More... button
- Make sure Serial ports is checked.
- Click OK
After setting these configurations, you'll want to save the connection.
- Click on the General tab
- Click Save or Save As if this is a new connection
Scanner
If the scanner creates a com port see the Scale setup info. If the scanner is strickly USB see the credit card swiper info.
Credit Card Swiper / Pole Display
Note: You'll need to turn off the redirector to use the card swiper locally. Also this requires a third party software that costs money, though it has a 15 day trial for testing. See USB Redirector for more information.
- Install http://www.incentivespro.com/downloads.html on both the Terminal Server (host) and the workstation (client)
- Start the redirection software on the server
- Start the redirection software on the client
- Connect to the RDP session
- Connect the USB device.
At this point if the USB device requires a driver it will ask for that information on the host. Otherwise it will be available and ready to go.
Troubleshooting Info
- Outgoing (from CMS) is communicating on standard ports 443, 80 (for most webservices/ecms) and the default Sybase port of 2638 and email can communicate on the ports you specify in email setup default is 25 other smtp port include 465, 587.
- Adding CMS to the "trusted" list is usually the recommended solution.
- DEP does do a lot of blocking with webservices which is what AVM, eCMS, etc use. Also, if the rest of CMS workstation is working, then most likely it's not a port blocking issue or I'm sure 2638 would also be blocked.
