WinXP SP3 being offered by Automatic Updates: Change in plans?
@Chris:
<QP>
We will begin automatically distributing Windows XP SP3 in early summer.
</QP>
Source: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3299543&SiteID=17
<QP>
For customers who use Windows XP at home, Windows XP SP3 Automatic Update distribution for users at home will begin in early summer.
</QP>
Source: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=3214173&SiteID=17
Why is Automatic Updates (AU) offering WinXP SP3 now? Is this a change to the above?
Is AU only offering SP3 (literally) but it won't download/install until "early summer"? If so, is this documented anywhere?
Thank you.
All Replies
It's Microsoft, there's always a change in plans, it's just that they rarely tell us about them.
In addition, I'd check with microsoft.com or use google to search for the documentation you want/need.
Hope this posting helps you this time.
- From other reports it seems the SP3 is offered only to users with Automatic Updates set to 'Notify me but don't automatically download...'.
User with the 'Automatic' setting shouldn't get the SP3.
You may be correct, Thomas. Since I posted here, a confidential MS source has told me that SP3 is not being offered yet to machines where Automatic Updates is configured to automatically download and install updates without notification.
That being said, "Windows XP SP3 Automatic Update distribution for users at home will begin in early summer" contradicts what we're seeing, when taken at face value. Many of my clients were taken completely unaware when AU offered SP3 this past week. I and the majority of my colleagues fully expected 5 or 6 more weeks to prepare clients (and their machines) for SP3.
Thomas Scheidegger wrote: From other reports it seems the SP3 is offered only to users with Automatic Updates set to 'Notify me but don't automatically download...'. My Auto Updates setting is Notify but don't download, and I got the SP3 notification a few days ago. I didn't realise there were still issues with it (thinking that they would have been resolved before it would be made available to auto update). I posted my woes here.
If this is still in beta, that should have been made clear (I wouldn't have attempted it).
