(no subject)
Sep. 14th, 2007 03:45 am![[identity profile]](https://www.dreamwidth.org/img/silk/identity/openid.png)
Windows forces core updates without user consent
Privacy issues and big brother freakouts aside, this is shitting me up the wall because I want to know how the hell it's going to affect WSUS.
We have 2k3 servers that roll out updates. However, the main machines are xp/2k and are enforced by a GPO ONLY to seek and accept updates from our 2k3 servers. We have a proxy server and denied external net access to most staff, so they can't even sneak do it.
So if you can't manually invoke these bastards as the article suggests, and it's fuckin' well not allowed via WSUS and if the spin of "Unless the update is installed, Windows Update won't work, at least in terms of searching for further updates." is true....Then I've got 300 machines here that are stuck in stasis.
Bastards.
Privacy issues and big brother freakouts aside, this is shitting me up the wall because I want to know how the hell it's going to affect WSUS.
We have 2k3 servers that roll out updates. However, the main machines are xp/2k and are enforced by a GPO ONLY to seek and accept updates from our 2k3 servers. We have a proxy server and denied external net access to most staff, so they can't even sneak do it.
So if you can't manually invoke these bastards as the article suggests, and it's fuckin' well not allowed via WSUS and if the spin of "Unless the update is installed, Windows Update won't work, at least in terms of searching for further updates." is true....Then I've got 300 machines here that are stuck in stasis.
Bastards.