This QFE updates the System Center Operations Manager 2007 Agent to allow it to monitor Windows Server 2008 Internet Information Services 7.0 Servers.
Great. Has this actually been re-released - if it has why does the filename not carry some notifcation that its a V2..... This isnt the first fix that has been released in this way....
Also the article still states that "there is a problem with this update", even though the download is now available (it had been replaced by a text file....)
I also ask if this is a fixed verison of the previous failed release of the IIS 7.0 MP for WS2008. The wording on the hotfix KB article doesn't give much away. Come on Microsoft, be a bit more descriptive! Please update with some more details.
Yeah, I echo those comments. I've been burned by patches related to OpsMgr agents in the last couple of months, i.e. released, I download, silently withdrawn by MS and then I install them not knowing any better - to get broken servers.
Some change control and communications would prevent a great product getting these black eyes.
Yes the documentation here is very lacking. Is this supposed to be working or not? I'm having all sorts of troubles with it.
Any word yet? Is this legit? After applying this latest update my IIS7 systems still show an error status...
I have applied this hotfix and it errors out with: Error 2762. Cannot write script record. Transaction not started - does not complete - still generating alerts for this
Hello everyone and thanks for the constructive feedback. The initial release was dated around 2/23/2009 and was roughly 5.5mb if I recall correctly. We don't have a way to mark a QFE as a v2, but it is good feedback and noted on our end. The update, released on 4/8/2009 is roughly 8mb in size so that should help with some of the confusion. The version remains the same. We have also removed the "problem" statement from the download. This was an oversight.
If you are still experiencing issues with the hotfix, please open a support case with CSS (Customer Support Services).
Again, we apologize for any inconvenience this release, and subsequent re-released has caused.
It seems to me, that the update changes the agent version back to 6.0.6278.0. All my agents that were at version 6.0.6278.32 and get this fix go back to this.