Have you ever tried to deploy an enterprise solution using remote desktop instead of using web-enabled solution like Go-Global or Citrix Metaframe ?
The problem is probably the printer....
If you are using remote desktop to connect to a server where your enterprise application resided, you still have to print back to your client computers.
Remote desktop actually allows that to happen, but not without some extra configuration.
First of all, if you are expecting that it will all work after you have checked the box for "Options/Local Resources/Local Devices/Printers", and if it don't then you should try to follow the following steps.
1. Follow the method prescribed by this article.
2. Login (remote desktop) to your server and install the specific printer driver to it. Install it as 'local printer' and choose just any port possible (including LPT1). Create a dummy name (i.e HP_Dummy).
Make sure you go to obtain the proper driver for your server's operating system (such as Windows Server 2003).
3. Logout from remote connection. Login again.
4. The specific printer on your local client will then be automatically mapped to a printer port designated by 'Remote Desktop Connection'. You can now remove the dummy printer created earlier (i.e HP_Dummy).
5. You should be able to print from remote server to your local printer.
The problem is probably the printer....
If you are using remote desktop to connect to a server where your enterprise application resided, you still have to print back to your client computers.
Remote desktop actually allows that to happen, but not without some extra configuration.
First of all, if you are expecting that it will all work after you have checked the box for "Options/Local Resources/Local Devices/Printers", and if it don't then you should try to follow the following steps.
1. Follow the method prescribed by this article.
- Basically, you need to edit the registry at the client computers to force all remote desktop to redirect all printer ports to remote connection. Just do the following steps...
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR - On the Edit menu, point to New, and then click DWORD Value.
- Type FilterQueueType, and then press ENTER.
- On the Edit menu, click Modify.
- Type FFFFFFFF, and then click OK.
This enables all ports on the client to be redirected.
2. Login (remote desktop) to your server and install the specific printer driver to it. Install it as 'local printer' and choose just any port possible (including LPT1). Create a dummy name (i.e HP_Dummy).
Make sure you go to obtain the proper driver for your server's operating system (such as Windows Server 2003).
3. Logout from remote connection. Login again.
4. The specific printer on your local client will then be automatically mapped to a printer port designated by 'Remote Desktop Connection'. You can now remove the dummy printer created earlier (i.e HP_Dummy).
5. You should be able to print from remote server to your local printer.
Comments
What I really referred to is the issue of usage of remote desktop connection.
You can use universal print driver for your remote desktop printer like Tsprint software. No driver need not to install for your server or workstation. Also have some feature.
1.Print documents to your local printer
2.Send files to your local computer
3.Open files on your local computer
http://terminalworks.com/tsprint.php