Danp Posted January 10, 2013 Posted January 10, 2013 Feel like I am fighting a losing battle here, but I am going to try at least! as 5 mins for a 2 year old RM desktop to reboot to a usable desktop is not good. One thing I have seen is a GPO that can be set Computer Configuration\Administrative Templates\System\Logon\ Always wait for the network at computer startup and logon We have gig networking for 97% of machines, so network traffic should be the issue, is anyone else using this GPO? Any other suggestions?
SYNACK Posted January 10, 2013 Posted January 10, 2013 Rsop logging is a big one but I heard that messing with that stuff directly in an RM network.
X-13 Posted January 10, 2013 Posted January 10, 2013 2 year old RM desktop That's your problem right there. Is it hanging on a specific part? Or just slow in general? Do you use roaming profiles? If they're large, it can take a while to load them. What about login/startup scripts? [do you got them? is they working? [bad grammar for no reason.]]
themightymrp Posted January 10, 2013 Posted January 10, 2013 Have you turned on verbose messages to see where the slow down is occuring? We had headaches with printer drivers causing slow logins. Or if you are using non-mandatory roaming profiles you might have a large file stuck in the profile somewhere causing the slowdown?
Danp Posted January 10, 2013 Author Posted January 10, 2013 Roaming off. Verbose on but only really shows "please wait for the user profile service" for any really length of time. How do I get a full report of whats going on? Boot log via msconfig does not really give many clues (attached from one machine) ntbtlog.txt
themightymrp Posted January 10, 2013 Posted January 10, 2013 This area of Event viewer should show you how long each section is taking to process: Event Viewer --> Applications and Services --> Microsoft --> Windows --> GroupPolicy --> Operational However if you are getting stuck on the wait for user profile service you either have a network issue in general of the profile is huge. How big is the users profile once it finishes logging in?
psydii Posted January 10, 2013 Posted January 10, 2013 Windows 7 Slow Boot / Slow Logon (Why I do what I do) - Dude where's my PFE? - Site Home - TechNet Blogs
Danp Posted January 10, 2013 Author Posted January 10, 2013 Thanks guys, I will have a look and poke about more. I have rebuilt my test machine again so it's a fresh build to play with tomorrow.
DrCheese Posted January 10, 2013 Posted January 10, 2013 List of Performance hotfixes post SP1 for Windows 7 SP1 - The troubleshooters and problem solvers... - Site Home - TechNet Blogs This is why MS need to make an SP2 for Windows 7 It would have all of these performance hotfixes rolled in. (You have to download them manually at the moment & not via WSUS) 2
Danp Posted January 11, 2013 Author Posted January 11, 2013 This area of Event viewer should show you how long each section is taking to process: Event Viewer --> Applications and Services --> Microsoft --> Windows --> GroupPolicy --> Operational However if you are getting stuck on the wait for user profile service you either have a network issue in general of the profile is huge. How big is the users profile once it finishes logging in? I see these on one machine Group policy bandwidth estimation failed. Group policy processing will continue. Assuming fast link. Group Policy dependency (Network Location Awareness) did not start. As a result, network related features of Group Policy such as bandwidth estimation and response to network changes will not work.
psydii Posted January 11, 2013 Posted January 11, 2013 I know. We've got various combinations of 32 'hotfixes' deployed, and a few more in testing. Quite a few are now included in WU Security updates, but once a hotfix moves you to the LDR branch you can never be sure if the Latest update to the componant via WU contains the fix from the LDR version, unless you go back and check to see if the LDR version has been replaced by a non LDR version.... oh the madness of trying to make this stuff work. Here's a random one.. BACKSPACE or arrow keys do not work in MMC on a computer that is running Windows 7 or Windows Server 2008 R2 I'd settle for a hotfix rollup pack, but since they release new versions of TCPIP SMB and CSC every six weeks or so, it would be significantly out of date before they even released it!
Arthur Posted January 11, 2013 Posted January 11, 2013 This is why MS need to make an SP2 for Windows 7 It's called Windows 8.
psydii Posted January 11, 2013 Posted January 11, 2013 (edited) It's called Windows 8. Sadly so true: http://support.microsoft.com/kb/2801075 "This is a known issue in Windows. This issue has been fixed in Windows 8." Edited January 11, 2013 by psydii
DrCheese Posted January 11, 2013 Posted January 11, 2013 BACKSPACE or arrow keys do not work in MMC on a computer that is running Windows 7 or Windows Server 2008 R2 oh god that errors drives me insane! It's mostly whist editing GPO's I get it. So cheers for the fix But yeah :/
spc-rocket Posted January 11, 2013 Posted January 11, 2013 @psydii We downloaded all the performance related fixes and inlcuded in the image before sysprep/mdt process and its working well. I've noticed that most of these also apply to server OS as well. Have you also patched your server 2008 r2 manually? with these hotfixes? I'm a bit relectant to do this just in case they break anything. It always has that silly message that this hotfix is intended to correct.....and has not gone through full regression testing... which i ignore on the client OS anyway. Ash.
psydii Posted January 11, 2013 Posted January 11, 2013 (edited) We've got the following on our servers: "ERROR_SHARING_VIOLATION" error message in Windows XP or in Windows Server 2003 when you try to open a file on an SMB share on a server that is running Windows 7 or Windows Server 2008 R2 A robocopy command updates DACLs incorrectly in Windows 7 or in Windows Server 2008 R2 Slow performance when you enable IPsec encryption on a specific TCP port number in Windows 7 or in Windows Server 2008 R2 A hotfix that lets you diagnose mini-filter-based performance issues in Windows Server 2008 R2 is available SQL Server data corruption when a memory range is accessed by the SetFileIoOverlappedRange function and an I/O operation in Windows Vista, in Windows Server 2008, in Windows 7, or in Windows Server 2008 R2 SMB commands run serially when the SMB packet-signing feature is enabled in Windows 7 SP1 or in Windows Server 2008 R2 SP1 "The file or folder does not exist" when renaming or saving to DFS share from a Windows 7 computer Home folder is not mapped to a client computer when multiple users are logged on to a computer that is running Windows 7 or Windows Server 2008 R2 "0x00000050" Stop error in Windows 7 or in Windows Server 2008 R2 Computer stops responding after you connect to an SMB 1 server in Windows 7 or in Windows Server 2008 R2 High CPU usage on a file server that is running Windows 7 or Windows Server 2008 R2 with ABE enabled Several of these are client side fixes, but since Windows Server access another file server is a client, I figured they out to be at the same patch level as the rest of the clients. I have not had *ANY* complaints about network performance since we deployed these updates to the servers and client. Edited January 11, 2013 by psydii
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now