Windows 7 Thread, Windows 7 Login times...... in Technical; Hi all,
This is not so much of a problem as such but a discussion on how best to speed ...
23rd November 2010, 11:40 AM #1
- Rep Power
Windows 7 Login times......
This is not so much of a problem as such but a discussion on how best to speed up login times for users connected to windows 2003/2008 domains. I know if users have cached credentials login times are usually pretty good. But how do you fair when a 'virgin user' as to speak logs in. From login screen to usable desktop in around 45 seconds.
Any tips, housekeeping advice, PC spec, roaming profiles etc etc??
From login screen
Non cached user
Over a wireless link 54MB
OS - Windows 7 32 bit
Dell Latitude E5510 - Celeron 1.87 Ghz, 2GB RAM
Time: 35 seconds (non cached user)
Time: 10ish seconds cached user
13th December 2010, 12:18 PM #2
I asked the same question a while ago here Windows 7 logon speed
I spent a long time looking at this and in the end concluded that there wasn't much I could do with regards to initial logon speed. Even experimenting on my core i7 machine at home with a bunch of virtual machines I could never really get it down below 30/20 seconds.
The only thing I could say is that XP disguises the login time, i.e it will show the user the desktop but it actually won't be usable for another 5/10 seconds after that. If you take that into account initial windows 7 login isn't hugely different than XPs
Thanks to DrCheese from:
ojhext (13th December 2010)
13th December 2010, 12:25 PM #3
I addressed this here - Windows 7 login time with Local Profiles (due to working on roaming/mandatory) was around one minute.
I built a mandatory profile for 7, using the local profile from a test user (not the Default Profile and sysprep). I set up all necessary Windows settings, stripped out anything not needed, and set permissions for users on the hive. Login time on Windows 7 is now around 15 seconds for a new user, far faster than the XP mandatory profile user (set up in the same way).
Thanks to 3s-gtech from:
ojhext (13th December 2010)
13th December 2010, 12:28 PM #4
- Rep Power
Cheers for the input guys. its good so see we at least get comparable results! 15 Seconds is very fast for non-cached user!
5th January 2011, 11:35 AM #5
I was a bit wary of doing it the way 3s-gtech did it, as Microsoft says it breaks quite a bit here. It was the way you did things in Windows XP and below in the past.
Configuring Default User Settings
But the thing is, it logs on *so* much faster if I do copy over an existing profile that has already been loaded once. I'm struggling to see any of the issues that MS have warned about above, i.e the Windows 7 broken libraries.
The manual profile copy process can cause issues such as:
- Their list of most frequently run programs is not cleared
- Whether the user has been introduced to the Start menu (will be set to TRUE for the source account, but should be FALSE for new users). Windows Explorer does some special things the first time you log on to introduce you to the Start menu and other new features.
- Whether the user is an administrator (and should therefore see the Administrative Tools, etc).
- The personalized name for “My Documents” will be incorrect. All users documents folders will be called “Administrator's Documents”. This is documented in the Knowledge Base article “The Desktop.ini File Does Not Work Correctly When You Create a Custom Default Profile” (The Desktop.ini file does not work correctly when you create a custom default profile).
- The default download directory for IE will be set to the Administrator's Desktop folder.
- The default Save and Open locations for some application with point to the Administrator's documents folder.
- Windows 7 Libraries are broken.
Has anyone else done it this way and noticed any problems?
5th January 2011, 11:59 AM #6
Deleting the stubpath registry entries speeded up mine (they are not really needed), if they exist you get the preparing your desktop applet in the top left corner when logging on, get rid of the stubpath entries and it does not happen and speeds things up considerably.
5th January 2011, 12:37 PM #7
Not noticed any broken libraries, the personalised name for my docs IS correct, the introductions to the Start Menu are incredibly annoying, default download directory works fine, and the Save and Open locations work. This may be because I did not use the Administrator profile to build the mandatory profile - I used a domain account in the Users OU, which I then moved into the Students OU to test.
Thanks to 3s-gtech from:
DrCheese (5th January 2011)
7th January 2011, 11:36 AM #8
I think I understand what they mean by broken libraries, when I use new profile clicking start > Documents can take anything from 5 to 15 seconds to show, whist if you make a profile the MS supported way it loads instantly. I'm going to have to decide if it's worthwhile trade off, or if I can work out how to resolve it.
Going into a library from word is instant tho
24th January 2011, 01:01 PM #9
Tried that as well, that also breaks the libraries (Loading speed) using the premade profile or deleting the stubpath entries results in libraries taking 10/15 seconds to load every time you click on them.
Deleting the stubpath registry entries speeded up mine
24th January 2011, 01:47 PM #10
On our slowest machines it's 30 seconds - mandatory profiles, the vast majority of that time appears to be group policies applying (mainly the printer policy strangely)
On faster machines it's generally about 20 seconds, overall not a worry at all, never seen any need to attempt to speed it up. The only problem users are the 25-30 roaming profile users we have but of those about 20 of them never change PC so it's not a problem
Libraries are completely disabled on our PCs, didn't seem worth the hassle they cause.
7th June 2011, 09:47 AM #11
In an effort to speed up Mandatory profiles, is it a good idea to have folder redirections by editing the ntuser? i.e. editing Software\Microsoft\windows\CurrentVersion\Explorer \User Shell Folders.
What else could be done to the ntuser?
7th June 2011, 09:55 AM #12
Personally i did that so that if in the unlikely event group policy fails the redirects are still applied (never had that happen, but you never know ), apparently it's not best practice to do it but so long as you document it well so that anyone who comes along after your time there knows it should be ok.
Originally Posted by apeo
7th June 2011, 10:11 AM #13
Thanks for the advise, it does shave off 20 secs and as you say it will apply the redirects even if gpo fails, which i have found in testing wireless. That is I tested it with a laptop that has just had its wireless connected, logoff and logon with mandatory. All the redirects failed, very odd.
Originally Posted by mrbios
Is it worth redirecting appdata?
Do you mind me asking what other tweaks did you do to your ntuser?
7th June 2011, 11:05 AM #14
Mandatory profiles + SSD drives on the client machines make things crazy fast
7th June 2011, 11:29 AM #15
Bet it does, but SSD is still to expensive for us
Originally Posted by zag
Last Post: 9th May 2010, 05:24 PM
By ginger9991 in forum Windows Server 2000/2003
Last Post: 15th November 2009, 03:42 PM
By mortstar in forum Windows
Last Post: 28th March 2007, 11:51 AM
By faza in forum Wireless Networks
Last Post: 18th September 2006, 10:06 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)