Windows 7 Thread, Weird login times OU's makes no sense. in Technical; Has anybody experienced this before, I haven't:
I created a fresh windows 7 64bit image of a PC and placed ...
26th July 2011, 07:11 PM #1
- Rep Power
Weird login times OU's makes no sense.
Has anybody experienced this before, I haven't:
I created a fresh windows 7 64bit image of a PC and placed it in its nested OU as normal.
Tested logging in as roaming users, fine no problems.
took it off the domain (Took an image) and then re added it to the domain once image was completed. Put it back in its nested OU.
now when I log in as the same users (Any user infact) log in times exceed 80 seconds!!!!
Checked Event VWR and its clean across the board except for the event saying login shell took over 80 seconds...
After updating drivers etc still nothing...
So then I move the computer outside the OU and put it in the default computers OU.
Login times are back to normal!
What I don't understand is what would make it change so drastically? It's the same freaking computer...
I tried then re adding it to my nested OU and wham login times exceed 80 seconds again...
Wondered if anybody might have an idea of what is going on?
26th July 2011, 07:31 PM #2
Dont know if it works for Windows 7... it works great for WinXP
SysPro Software -> Policy Reporter
Gives you a log showing exactly whats going on when you logon - do a log for the default OU and one for the computer OU and check where the big differences are....
I managed to drop off about 15 seconds from a 30-40 second logon by finding out how to stop IE Branding on logon!
Last edited by siuko; 26th July 2011 at 07:33 PM.
26th July 2011, 09:21 PM #3
- Rep Power
I think I might have found the culprit. I was RD'ing in and discovered an old printer script that references printers that no longer exist. This would mean it would never complete and might cause a hang.
Still doesn't really explain why it was working until i removed and readded the PC to the domain.. but hey..
Will see if it has helped tomorrow.
26th July 2011, 09:31 PM #4
check all scripts...kixstart scripts run the fastest followed closely by VBS then batch...perhaps look at your scripts and see if there is anything that could possibly cause it to go funny
26th July 2011, 10:02 PM #5
- Rep Power
It all makes sense now after going through it in my head.
the printer script used a text file list: with *ICT to map the missing printers to any computer with the name ICT in the computer name.
this script was run on standard users login . The reason that I was logging in without issues before I took the PC off the domain was that it had a computer name: HP.. so the list wouldn't have picked it up on the user login.
That explains why when I logged in as an administrator it wouldn't hang because the administrator does not run the printer script at login..... yes I think I'm there.... well proof will be when I check my theory tomorrow. I think I should named inspector MaXIM Holmes
thanks for the posts..
Last edited by MaXiM; 26th July 2011 at 10:06 PM.
27th July 2011, 08:50 PM #6
- Rep Power
By ojhext in forum Windows 7
Last Post: 14th June 2011, 02:20 PM
By Mr.Ben in forum Windows 7
Last Post: 28th April 2011, 03:59 PM
By DaveP in forum Jokes/Interweb Things
Last Post: 19th January 2010, 08:54 PM
By faza in forum Wireless Networks
Last Post: 18th September 2006, 09:06 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)