Microsoft Kills Off Patch Tuesday Advance Notifications.....

CommanderFrank

Cat Can't Scratch It
Joined
May 9, 2000
Messages
75,399
..... with no advance notification. Microsoft is receiving negative feedback from the Internet community for the company’s decision to discontinue notifications and descriptions of upcoming ‘Patch Tuesday’ updates. The Advance Notification System (ANS) will no longer be posted for the general public the week prior to Patch Tuesday.

While some customers still rely on ANS, the vast majority wait for Update Tuesday, or take no action, allowing updates to occur automatically.
 
Is this really because they don't want to publicize the tons of updates every month? The reasons (excuses) sound like BS to me.

"Customer feedback indicates that many of our large customers no longer use ANS in the same way they did in the past due to optimised testing and deployment methodologies."
 
Sounds like we are killing the start menu because people just pin the most used programs.. Yes I use the start menu and the all programs folder too!, sure less often than the pinned stuff.. that is why it is pinned. I am not sure the fact that most people just let the update happen means they did not check the notification. Might mean that they looked, saw its all good and let it be... I don't really know but it would be my guess anyway.
 
Of all the penny pinching ideas I have heard, this might be the dumbest. First he lays off a lot of their core server OS dev staff... I am still trying figure out what this means about Microsoft's future. Now killing ANS. My guess is they want to kill anything that isn't cloud based, so if your server isn't in the cloud, where they will handle the patches, they want to make your life as hellish as possible until to you migrate to the cloud. The problem, of course, is that there are still a lot of businesses and people relying on software that is old and breaks every time a new patch is installed.
 
"Customer feedback indicates that many of our large customers no longer use ANS in the same way they did in the past due to optimised testing and deployment methodologies."

Didn't they claim 'customer feedback' indicated that customers don't use or want the start menu any more? That worked out well...
 
Is this really because they don't want to publicize the tons of updates every month? The reasons (excuses) sound like BS to me.

"Customer feedback indicates that many of our large customers no longer use ANS in the same way they did in the past due to optimised testing and deployment methodologies."

No it's because their was absolutely no way to automate uploading a list of files and descriptions to a webpage. It required tons and tons of manual human labor to compile that information and create a new webpage every couple weeks.

I mean if you know of some way to manage packages so that names and descriptions can be pulled together and then invent some "language" that can dynamically create a webpage based on an external trigger or schedule then maybe YOU should be in change or a multi-billion software company. As for me I will leave that decision making to guys who own sports teams and save Africa.
 
The problem, of course, is that there are still a lot of businesses and people relying on software that is old and breaks every time a new patch is installed.

I just noticed that one of my Excel documents didn't work on one of my computers that gets regular patches. A simple fucking VBA button....just didn't work anymore. The culprit? A patch a couple weeks ago that broke something as simple as ActiveX in Excel :confused: :confused: :confused: How does that get past QC????

http://excelmatters.com/2014/12/10/office-update-breaks-activex-controls/
 
[gordon ramsay voice]
Have you given up, Microsoft? It looks like you've given up. Get out!
[/gordon ramsay voice]
 
If you are a premier customer, you can still get the info from your account rep. If you are apart of Active Protections you'll still get ANS notifications. And no they aren't making anyone sign a NDA to receive the info.

Finally if you are neither, you can get notifications from Mybullitins. http://mybulletins.technet.microsoft.com/

The only thing that changed was how the information was distributed, it's all is still there.
 
That's not really true. As detailed in this blog post, the older information is no longer publicly available, but there is an alternative with a different selection of data presented to the public if they sign up and select products to be notified about:

... discontinue the Deployment Priority matrix in favor of the [MyBulletins] Exploitability Index, modify the Exploitability Index to account for more threat scenarios, simplify security bulletin content to help customer understanding, and create a centralized glossary for bulletin definitions. The change being announced today fits within that context.

We are making changes to how we distribute ANS to customers. Moving forward, we will provide ANS information directly to Premier customers and current organizations involved in our security programs, and will no longer make this information broadly available through a blog post and web page.
 
You now what Microsoft should stop? Their support forums. Worst on the planet. Filled with nothing but repeated level 1 tech support drivel.
 
No it's because their was absolutely no way to automate uploading a list of files and descriptions to a webpage. It required tons and tons of manual human labor to compile that information and create a new webpage every couple weeks.

I mean if you know of some way to manage packages so that names and descriptions can be pulled together and then invent some "language" that can dynamically create a webpage based on an external trigger or schedule then maybe YOU should be in change or a multi-billion software company. As for me I will leave that decision making to guys who own sports teams and save Africa.

huh?

I used to create web-based CMS systems, and it would be very easy to write something that would automatically update the webpage without any manual labour.

presumably there already documenting every patch anyway that's just good business practice, write a php script that can access a copy of the notes and parse to a html document, use a cron script to manage the schedule...

something like this:

1. cron script copys notes to webserver
2. php/java/asp script pulls out title and description and shows it in a HTML format
3. show it in a css/iframe object.

The only requirement would be that the notes would be formatted the same every-time, which following good business practice, they would be.
 
Another reason why I setup a patch management system to wait 2 weeks to push those updates out to our environment.
 
Back
Top