I think it's understandable that there is an RTS and RTW date. However, when the SNS message gives a date without specifying RTS or RTW, I think it's reasonable for us, as customers, to make the assumption that 'release date' means RTW. If it was an RTS date, I would expect the SNS system to mention that. This is especially true in my opinion because this patch has been significantly delayed.
Fair point, the SNS should have been more specific. Perhaps that is all that's needed should the need arise again.
The RTS phase of a patch's life is controlled by Tier 3 Support, it's a managed release. We deliver it to customers reporting issues solved by the patch, and to some Platinum Support customers who have voiced their interest to be included in the managed release program. For those who wish to be included in the program we set expectation of some level of commitment and participation, to add value to the program, thus not all Platinum Support customers qualify. We try to be reasonable and flexible, of course .
If you are experiencing an issue solved by the patch, know that the patch will be released for general availability 9/28, the RTW date. If the issue requires a more urgent solution then Support should be contacted, that we may verify and diagnose the issue. Once confirmed, Patch 4 could then be provided as the solution to that issue.
So, I got the patch 4 installed it on a few machines. So far, no new issues observed, but unfortunately, the issue it was supposed to fix (the reason I got it) is still not resolved. My problem is with a flood of 577 events in the Windows Security log. This problem was supposed to be addressed with the release of this patch, but parsing the release notes, there's no reference of such issue/resolution!?!
As per the article:
William, I sent you a screen shot...
To answer some previous questions, I believe that to receive the RTS version, you need to have an open support case who's resolution depends on this patch release.
David.G wrote:...My problem is with a flood of 577 events in the Windows Security log...
I have an open incident for the exact same thing! Hopefully there will be one more incremental update to P4 before it's finally released to fix this.
Added quote on 9/1/10 4:48:49 AM CDT
I've been able to confirm the issue regarding the Event ID 577.
Patch 4 contains a solution to one of its causes, but that code path is executed only when admins are logged in. We still need to address the behavior for non-Admins.
I do not expect Patch 4 to be revised for this remaining symptom - we'll see; that's not entirely my call to make. What I expect is for the issue to be resolved, and for a hotfix deliverable to be made available for those that need it.
Many thanks to the folks who've been able to bring this to our attention.