Friday, March 02, 2012 8:06 AM
Some users in our company are having issues with printers failing to map correctly upon reconnecting to a disconnected session (only at reconnect, login works fine). What I believe is the issue is that when a user reconnects to a session, windows will 'refresh' or re-map the current printers (you can see this if you open Printers And Devices upon reconnect - the window will refresh automatically) and when it does this it will read data from registry so it knows what to map.
When issues occur, windows won't map the printers at all (so maybe 1/5 or 0/5 printer will show up), so the default printer will most of the time change and then it messes with user's printing. Every time windows fail to map, I've noticed that the failed-to-map printers' subkeys in:
will only contain 1 subkey, "guidprinter", instead of 4 (Server, Provider, LocalSomething).
I'm guessing that upon reconnecting to a session, something writes to this place in registry (and messes up), and then when windows reads from these registry keys it will fail to map the printers.
If my guess is sound, my question is this: Does anyone know any services or applications that actually write to \printers\connections in registry?
The issue only occurs rarely, perhaps 1/50 logins. But when you have 1k simultaneous users it becomes alot.
I'm gonna go ahead and use procmon to see if I can find out what actually does this otherwise, but I wanted to hear some input first.
- Edited by Klara66 Friday, March 02, 2012 8:11 AM