February was another rough month for anybody having to apply Microsoft patches. We had a couple of posts already covering the Microsoft patch issues, but due to the number of problems, here a quick overview of what has failed so far:
In addition, an important reminder that the "Group Policy" patch alone does not fix the actual vulnerability. In addition to applying the patch, you have to enable the new group policy options: See https://support.microsoft.com/kb/3000483 for details. --- |
Johannes 4479 Posts ISC Handler Feb 16th 2015 |
||||||||||||||||||||
Thread locked Subscribe |
Feb 16th 2015 7 years ago |
||||||||||||||||||||
Does enabling the GPO patch by requiring SMB signing affect only GPO application or does it turn it on globally? If the latter, those of us running non-Windows file shares such as mainframes cannot enable it.
|
Anonymous |
||||||||||||||||||||
Quote |
Feb 16th 2015 7 years ago |
||||||||||||||||||||
I took KB3013455 off my system on Saturday, and find to my dismay that the automatics have put it back again today. How do I prevent this from being an endless cycle? Vista-64 Home edition.
|
HackerHater 7 Posts |
||||||||||||||||||||
Quote |
Feb 16th 2015 7 years ago |
||||||||||||||||||||
I had the same question. We have a hybrid environment of Windows and UNIX and we need to make sure we will still have compatibility.
As it is, we are only enabling the new features on sysvol and Netlogon like Microsoft recommends since Windows login scripts don't run for our UNIX users. |
Jasey 93 Posts |
||||||||||||||||||||
Quote |
Feb 17th 2015 7 years ago |
Sign Up for Free or Log In to start participating in the conversation!