Question : Terminal Server users can not open jpg file in MS Photo Editor and other questions

1. Non-admin users can not open .jpg files in MS Photo Editor.
2. One user is getting an error message "office assistant not available"  Run MS Office repair when he tries to print from one of our ordering programs that uses word to print forms.
3. Printers - I want TS to find local printers (which it does), but not make them the default (which it currently is).  I want the user to switch it if they need to.

Answer : Terminal Server users can not open jpg file in MS Photo Editor and other questions

hi there
the solutions

1)  My application runs fine for Administrators, but not for normal users
Download FileMon and RegMon from SysInternals.
Run them as Administrator on the console of the Terminal Server (when no user is connected), start a TS session as a normal user and try to run the application.
FileMon and RegMon will show you all "access denied" errors that occur, so that you can give your users the necessary permissions on a file-to file or Registry subkey basis

2) try to disable the animated office assitants and enable motionless office assistant
this link will help u to do that

http://office.microsoft.com/en-us/assistance/HA011383101033.aspx

3) Providing Client Access to Local Printers
Terminal Services provides printer redirection, which routes printing jobs from a terminal server to a printer attached to a client computer or to a network printer that is available to the client computer.
You can disable printer redirection by using Terminal Services Group Policies or on a per-connection basis by using the Terminal Services Configuration feature.
There are two ways to provide client access to local printers:
 Automatic printer redirection. This works through Remote Desktop Connection.
 Manual printer redirection. Use this option for 16-bit clients, Windows-based terminals, and local printers that require older drivers.
Please note that in Terminal Services:
 Bidirectional printing is not supported.
 Redirected printers are available for use with applications running on the server. Redirected printers appear in the Printers folder in Control Panel.
 Clients see only their own redirected printers in the Printers dialog box.
Automatic Printer Redirection
When you use Remote Desktop Connection to a Terminal Server, printer redirection is automatic as long as the local printer uses a driver that is installed on the server.
When a client connects to Terminal Services, local printers attached to line printer port (LPT), communications port (COM), and universal serial bus (USB) ports that are installed on the client computer are automatically detected and a local queue is created on the server. The client computer printer settings for the default printer and some properties (such as printing on both sides of the page) are used by the server.
When a client disconnects or ends the session, the printer queue is deleted and any incomplete or pending print jobs are lost. Information about the client's local printers and settings are saved on the client computer. During subsequent logon sessions, the printer queue is created using the information stored on the client computer.
If a printer driver is not found on the server, an event is logged and the client printer is not created. To make the printer available, the driver must be manually installed on the server.
Note: Print administrators can see all redirected printers, both on the server and those redirected from their session while normal users can see normal printers on the server and only their own redirected printers.
Please note that in Windows 2000 Service Pack 2 and Windows Server 2003, a fix was added for cases where redirected printing was not working automatically. Issues had one of the following symptoms:

 The Terminal Services client enumerated its local printers and sent information (such as the printer and print driver name) to the server. However if a corresponding driver on the server did not exist, the installation failed.
 If you used an Original Equipment Manufacturer (OEM) driver with a name that did not exactly match the name in the Ntprint.inf file, Windows did not install the driver.
This issue was resolved in Windows 2000 Service Pack 2 and Windows Server 2003, but the resolution also requires some registry value changes. For more information, see Knowledge Base article Q275495, “Printer Redirection or Upgrade May Not Work Because of Signed Ntprint.inf File.”
Manual Printer Redirection
You can redirect printers attached to LPT and COM ports on the client's local computer manually for use with Terminal Services clients.
Note: Terminal Services does not support manual redirection of printers connected through USB ports.
To redirect a client printer manually, contact your administrator and provide the name of your computer (or IP address for a Windows-based Terminal). The client must be connected to the terminal server during manual redirection.