Windows 7 Thread, GPP Printers and Romaing Profiles (again...) in Technical; Originally Posted by sonofsanta
Don't know why, but just running a bat file with "gpupdate /force" in it slowed logons ...
28th September 2012, 09:28 PM #16
That can easily slow logins down quite a lot depending on how you setup your policies.
Originally Posted by sonofsanta
You shouldnt need to do this as it applies this when you login anyway.
One thing to test is the checkbox for applying in the user context rather then system level which is default.
Originally Posted by Liam
I presume its a w7 profile not a xp one migrated?
Drivers are the most common issue usually and certain HP ones especially (points at universHELL driver)
The spooler service can crash with bad drivers losing all printers until you reboot. W7 does have a GP setting though to run spooler drivers in isolation, this means one driver shouldnt be able to kill the service but if the driver crashes the person WILL lose the printer in the printer section of w7 until its readded by relogging in.
Last edited by ZeroHour; 28th September 2012 at 09:30 PM.
IDG Tech News
1st October 2012, 01:01 PM #17
That seems to work better - although it may be that my BAT file did the slow logon because it was just called gpupdate.bat and so resulted in an eternal loop of calling itself, as you mentioned above. Setting it as a logon script still delays the desktop by ten seconds, though, so what I've done is save the script to a shared location and set it to run under User Policies > Admin Templates > System > Logon > Run these programs at user logon - that way it runs but it doesn't delay anything. We'll see if it actually resolves the problem or just shifts it to later in the logon process, now I have a sinking feeling that as often as the extra refresh fixes it, it will break it again, so I will be keeping a close eye on it...
Originally Posted by penfold
Most the time it does, and it applies it fine - but intermittently it decides that the printer can't be found, which is BS as it has found the printer for the last three dozen logons in a row and nothing has changed since then. Logging off and logging on again usually fixes this but it'd be nice (and make me look better) if it just bloomin' worked. No rhyme nor reason to the times it doesn't, 5 people in a row will be fine then the next person comes along and borked. Stupid GPP!
Originally Posted by ZeroHour
1st October 2012, 01:32 PM #18
This is why I ended up sticking the refresh in as I found it didn't apply the default printer 100% of the time and this caused problems with jobs being logged constantly with printers not working when in actual fact they had printed to the wrong printer.
Originally Posted by sonofsanta
Thanks to penfold from:
sonofsanta (1st October 2012)
25th October 2012, 05:30 PM #19
- Rep Power
Do you have any additional details on the specific hotfix and the reg hack?
Originally Posted by deano
25th October 2012, 11:26 PM #20
I'm interested in seeing this too - we are also having intermittant gpp mappings...
Originally Posted by SS07
29th October 2012, 10:30 AM #21
There is an option called "Delete All" in GPP which you can just put at No.1 in the order, that way when the user logs into any machine it removes all printers, then re-installs the ones required.
By 3s-gtech in forum Windows 7
Last Post: 4th October 2013, 01:28 PM
By Stuarte in forum Windows Server 2008 R2
Last Post: 29th November 2011, 10:39 AM
By LeightonJames in forum Windows
Last Post: 27th April 2011, 12:58 PM
By mrbios in forum Windows 7
Last Post: 26th October 2010, 10:00 AM
By Trenton_Lister in forum Wireless Networks
Last Post: 25th September 2008, 03:03 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)