Hi

We're experiencing slow logon times on our Windows 7 Enterprise x64 workstations. I've found that applying hotfix KB2617858 dramatically speeds up the login time but as it relates to carrying out validation of the WMI repository, I'm slightly nervous about deploying it to our workstations given the reliance of the ConfigMgr client on WMI.

Has anyone any experience of deploying this hotfix in a ConfigMgr environment or whether I'm likely to start encountering WMI/Client Health issues if the full validation of the WMI repository no longer runs at logon?

Thanks

Stewart

We have it in our image.  It doesn't hurt Configmgr. It does help with boot time and we have tracked it.

Hi,

I share the same expirience as Matthew, I have it both in the images and have distributed it afterwards for some customers without any issues.

Regards,
Jrgen

We had terrible problems with the "Welcome" startup screen being slow for around 250 user machines, eventually found that it was a corrupt WMI repository, but for us, running the hot fix didn't "fix" the problem as such. We had to rebuild the WMI which fixed the problem, but running the hot fix after running the rebuild then kept it away (if we didnt run the hot fix it returned...)

It took me ages to get this all sorted out, so if it helps I put together a guide with all the files for what helped my problem here:

http://itguru82-sccm.blogspot.co.uk/2012/10/welcome-screen-hanging-cannot-run.html

I updated our images as well with the hot fix and I've had no more problem since, so from my experience, I would install this hot fix on the images. I havent pushed it out to all machines although I am very, very close to doing so for machines that I know are not affected by the corrupt WMI repository.

Thanks for the responses everyone, this gives me confidence to rollout the hotfixes with out Win7 image.

Cheers

MS Suggested we only apply it where needed, so we only applied it to our lab environment where mutiple people login and the wbem repo would get enormous, and it would take upwards of 45 mins from login to desktop. I haven't evaluated it much since sccm 2012 has came on the scene but I believe sccm 2012 has it's own way of repairing the repository and it was my understanding that the hotfix merely canceled checking at startup, I can't check b/c the kb site is down right now but I'd have to say you shouldn't have too many issues w/ this combination. We haven't had issues with those machines receiving updates or software deployments either.

Faced with the fact that our client were complaining that the logon times were unacceptably slow and given the dramatic improvement afforded by this hotfix, we were left with little choice but to roll it out across the board. I've not encountered any problems so far on the newly deployed Win7 machines so hopefully this will continue. I'll be looking to update to ConfigMgr 2012 once we've finished our Win7 rollout, I'd read about the WMI healing built into the 2012 client so that gives me more confidence that hopefully there won't be any long term issues.

Hello, i just came across this post. I am unable to find KB2617858 in either SCCM, or WSUS (within the SCCM Server). Any ideas as to why?