Another day, another old call to try to get caught up on.<\/p>\n
User called last week…maybe the week before…stating that it was taking a minute and 15 seconds to get logged on.\u00c2\u00a0 This was the time he measured from the time he put in his network password and clicked ok, before the desktop would finally begin to appear.\u00c2\u00a0 During that 1:15 of unbearable waiting, all he would see is a dialog box showing “Loading user profile”.\u00c2\u00a0 This particular computer is shared by two people in the office, and according to the one who called in the trouble call, the other guy was having the same exact problem.<\/p>\n
I should point out that the majority of our systems are running WindowsXP Service Pack 2, Office Professional 2003 Service Pack 2 and some flavor of Symantec Antivirus in the 10.x family.\u00c2\u00a0 This system was right in line with that standard.<\/p>\n
Knowing that I had been having problems trying to push updates to that system, I figured the first place to start would be to update the network drivers.\u00c2\u00a0 The only problem was…the network drivers were already the most current (even if they are three years old).\u00c2\u00a0 But what the heck.\u00c2\u00a0 I logged on with a local admin account (most of our users are in the Power Users local group, not Administrators),\u00c2\u00a0 downloaded a new copy of the latest, deleted the adapter from the Device Manager, rebooted, then pointed Windows to the folder of drivers I had downloaded.\u00c2\u00a0 Had the original user log on – and it still took over a minute.<\/p>\n
Realized at this point though that the local account I used to log on did NOT<\/strong> have the same lag time during log on – log on was fairly immediate.<\/p>\n Took a look around the Event Logs, and noticed that Symantec Antivirus (the software that everyone seems to love to hate nearly as much as Microsoft) was having some issues at start up, so I ended up removing the slightly older version that was on the system and installing the latest SAV.\u00c2\u00a0 We haven’t moved to Symantec Endpoint Protection (SEP) yet, and as things stand right now, perhaps we won’t, but that is a different story.\u00c2\u00a0 Suffice it to say, that didn’t help with the logon problem.<\/p>\n Grasping at useless straws, I did a quick defrag of the hard drive, which someone else must have done recently.\u00c2\u00a0 The 80 GB drive in the system only took about 20 minutes to run through the entire defrag.\u00c2\u00a0 Once again, the problem was not resolved.<\/p>\n I decided to log on with my network account, and low and behold, I get logged in immediately.\u00c2\u00a0 No minute plus wait before I got to the Desktop.<\/p>\n Now it is looking more and more to be profile specific.\u00c2\u00a0 The only problem was the user’s insistence that the other guy who uses the workstation is having the same problem.\u00c2\u00a0 Easy enough to find out – and it turns out the other guy was NOT<\/strong> having problems getting logged on.\u00c2\u00a0 He managed to download and install a Freeze.com screensaver and wallpaper application, which I really wish he had not done, but that wasn’t what I was there for.<\/p>\n Back to the original guy, and I see a print queue to a non-exisitent server that we remove.\u00c2\u00a0 I check for drive mappings to non-existent servers, but there aren’t any.\u00c2\u00a0 Another log off\/log on, and still the wait.<\/p>\n Somehow I get this wild idea that maybe it is the actual Desktop itself that is the problem.\u00c2\u00a0 So I take what I think is going to be a quick look at the Display Properties….and I wait…and wait…and wait…before the dialog box finally comes up.\u00c2\u00a0 And that plain blue screen that I think is the “None” wallpaper is in fact – Internet Explorer Wallpaper?\u00c2\u00a0 Now THAT<\/strong> is strange.\u00c2\u00a0 So I change the Wallpaper to “None”, log him off, and 15 seconds later, he is logged back on and at the Desktop.<\/p>\n Broken wallpaper causes excessive logon time.<\/p>\n Whodathunkit?<\/p>\n","protected":false},"excerpt":{"rendered":" Broken wallpaper causes excessive logon time Continue reading