J
JW
Looking for a true Microsoft type fix. Microsoft should have had a fix for
this by now. What we have come up with so far in our case is:
This is a function of the new Remote Desktop client. What is happening is
that when you remote into a Vista PC it tries to set your local default
printer on the remote box. When the session is ended, it is not getting the
remote PC default printer set back. The next time someone logs in local it
looks for the default printer (which exist on another PC, possibly at home)
and when it cannot find it, it defaults to the first one on the list. I am
looking for the correct solution but all of the solutions I have come across
so far also have side effects. The best one so far is a group policy
setting that would keep the remote desktop client from trying to remap the
printer.
Thanks
JW
this by now. What we have come up with so far in our case is:
This is a function of the new Remote Desktop client. What is happening is
that when you remote into a Vista PC it tries to set your local default
printer on the remote box. When the session is ended, it is not getting the
remote PC default printer set back. The next time someone logs in local it
looks for the default printer (which exist on another PC, possibly at home)
and when it cannot find it, it defaults to the first one on the list. I am
looking for the correct solution but all of the solutions I have come across
so far also have side effects. The best one so far is a group policy
setting that would keep the remote desktop client from trying to remap the
printer.
Thanks
JW