I applied KB901034 to my primary site server today. During the installation, you are prompted to choose if you want the installation to perform a site reset or if you want to do one yourself after. Either way, the install wants the site reset. I choose for the install to do it for me. The installation completed without error. Not soon after, I am told that “several” sites are reporting that packages are not deploying. I looked around in the logs and checked the services. Hmmm, the SMS_Ececutive is not started. Ok, I start it. A bit later I am notified that packages are still not deploying. I look at the services again and the bootstrap service is active and the reporting point is not responding to remote site admins. I'm concerned...
I looked everywhere to figure out what the issue was. I opened a ticket with Microsoft and made it critical. I work with a guy I had worked with in the past who is out of Redmond. I love those folks in Redmond as they have access to the right people all the time.A 7 hour story made short..... there is a “known issue” within Microsoft that has not been released to the public in regard to KB901034. It seems that there have been others who have had issues with “bad” site resets during the installation of the KB.
It turns out that the site reset does not log ANYTHING if it is run during the install. The root issue has not been given to me (nor do I think Microsoft knows). If you run the site reset after the install, it works correctly. So, a long day made short, DO NOT run the site reset during the install of KB901034, run it AFTER the installation. Microsoft does confirm that this is not a normal issue, but they have had other calls on this. So, if it ran fine for you that's great, but there is a bug in the update and it IS confirmed.
If you do run the site reset during the install and you notice these issues, run a manual site reset and it should fix the issue. We have also noted at my client that a site reset spoofs the SMS reporting permission in DCOM. You may have to add the reporting group back into DCOM to let non domain admins back into reports. This is also being documented as an issue.
Also, the bad site reset did more than DCOM issues. After the manual site reset and adding the DCOM permission back, we still could not access reports, even as a domain admin. I had to uninstall and reinstall the reporting point on the server in the SMS console.
I hope this helps someone in the future. This information will be updated in my documentation / article Brian and I are working on. I have notes for everything during the preinstall process so far. Even a extra bit of info for those of you who load balance your MPs. More on that soon....