|
|
|||
|
|||
|
After using commit on a TS for the past 2 years we have ran into a few issues that we would like to learn how to bypass / work around.
1) Email issues - anything like email ticket history to customer, send asset details, etc doesn't work since there isnt an email client on the server. Each workstation has outlook install running hosted exchange, but that doesnt help us using commit on the TS. 2) Printing issues - we can print easily in the shops since the printers are part of the network and setup in AD. When users are home, most cannot print. It shows their local printer [redirected] but when you hit print nothing happens. |
|
|
|||
|
|||
|
1. Email: Yes, you should use Outlook for this to work and you should be able to run it via Terminal Services as well. Yet it needs to be installed on the machine (I guess the server) you remote to.
2. Printing issues - please send us your logs, maybe something will show up regarding redirected printing. BTW, did you try that with the latest 7.0 release? |
|
|
|||
|
|||
|
For printing is TS we use a product called Print To RDP. This application allows the user to print from any printer they have installed on their local PC. You do not have to install the same driver on the TS server.
When a user adds a printer to their desktop it does not require any support from us. It just works. We have been using this product for 4 years now. Here is a link for more info: http://www.blackice.com/Remote-Deskt...FS7xOgoda3YAUg |
|
|
|||
|
|||
|
The problem with using outlook on the server is that it requires a terminal server license. Big $$$ just to be able to send emails.
If we were to use OL on the server, does every remote user need a profile setup? That rdp printing program looks nice. I think i heard of it before. It is expensive though. Is it licensed by machine, or user? |
