We are running 2 terminal servers (Server2003 SP2) with ThinPrint RDPengine v7, enabling abstraction of print drivers at our remote branches.
We are experiencing the following problem on some of our most recently issued client machines, both XP, and Windows7:
After logging-on to windows on the client and opening an RDP session, the ThinPrint client is visible in the taskbar, and the client’s locally attached printer appears in the list of available printers in the terminal session. If the terminal session is terminated, no matter by which method, the ThinPrint client is not initialized when establishing a new RDP session. In order to enable the ThinPrint client it is necessary to log off the user session on the windows client.