If this is your circumstance, make sure to get KB2919355 applied today. So, I'll stop assuming and remember that there are unique circumstances where Windows Server 2012 R2 might be utilizing Windows Update for patching. However, if Windows Update is being used to provide patching for the Windows Server 2012 R2 server, it will also stop receiving updates from Microsoft. Again, if the Windows Server 2012 R2 server sits on the company network and updates are managed centrally by an IT organization, the deadline is August 12, 2014. Some in a domain environment as a member server, some stand-alone. Why? Because its assumed that Windows Server 2012 R2 is being updated through managed services by local IT. Created on ApOffice Pro 2013 0n Terminal Server Using server 2008 R2, in Remote Desktop Services mode. I've mentioned it a few times, but much more in passing than as a highlight. Those companies utilizing WSUS or System Center Configuration Manager (or other patch management product) actually have until Augto ensure that Update 1 has been delivered before the stream of available patches ceases.īut, it's important to clarify that Update 1 is just as important to Windows Server 2012 R2 as it is for Windows 8.1. The deadline is for home users, or end users in companies that have decided to point computers to Windows Update instead of managing patching centrally. This month's deadline is strictly for those Windows 8.1 users that don't participate in a company-wide patching process. The big underscore here is "consumer" users. And, this month, it's more important than ever to realize this, as June's Patch Tuesday represents the stop-dead date for Windows 8.1 consumer users to keep secure. We've spent a lot of time talking about how Update 1 (KB2919355) for Windows 8.1 is required if you want to continue receiving security updates from Microsoft.
0 Comments
Leave a Reply. |