>That's a pet peeve of mine, too.
>
>A couple of suggestions:
>
>1. If a remote user is not going to remote-print, then they should de-select that option when they connect via Remote Desktop
>
>2. If it's Server 2003, you get those errors if the user does want to remote-print, and one or more of their installed printers is not also installed on the Terminal Server itself. The only way I know of to get around that is to install all possible printers of all remote users on the TS, which is a big job and a PITA.
>
>My understanding is Server 2008 and later recognize this issue and are a lot smarter about not recording spurious "errors".

Well, actually, all of them are Windows Server 2008.

But, thanks for providing some feedback.