Windows Update Service Enabled after OSD
OSD build and capture of win7 x64 with Windows Update
service disabled, enables itself after TS/Imaging process. Anyone know why this happens or how I can permanently disable...it is for a public facing machine I do not wish to ever update. Turning off automatic updates doesn't seem to do the trick...it
still updates periodically when reboot. Thanks in advance!
March 25th, 2015 12:38pm
So you disabled the WUA agent and ConfigMgr enabled it during the task sequence? And you want it to remain disabled? Have you already tried adding a (final) step to the TS that disables that service?
March 25th, 2015 12:50pm
As a side note, isn't that *the* most critical type of system to update: a public facing one?
March 25th, 2015 5:11pm
I would second the question that Jason throws out but I'll digress since I don't have all the details. And to Torsten's point, I would just add a step in the Task Sequence to disable the service.
sc config <service_name> start= disabled
March 25th, 2015 5:37pm
I thought the Windows Update service was started each time by the ConfigMgr client and you couldn't disable it or am I thinking of something else?
March 25th, 2015 6:44pm
The public machines I am imaging are frozen via deepfreeze so I am ok to not have them run updates automatically. I don't want the service to be running because it starts to run the service at reboot sometimes. Not sure if started by configmgr?
March 25th, 2015 6:52pm
I'm pretty sure it's started by the client.
Why not create some maintenance windows for your devices for updates and thaw the machines during the MW? You can therefore keep your machines patched.
Yeah I've had the pleasure of Deep Freeze before.
March 25th, 2015 7:06pm
I would second the question that Jason throws out but I'll digress since I don't have all the details. And to Torsten's point, I would just add a step in the Task Sequence to disable the service.
sc config <service_name> start= disabled
-
Proposed as answer by
William Bracken
16 hours 38 minutes ago
March 25th, 2015 9:35pm
Adding sc config <service_name> start= disabled to my TS worked. Thanks a lot for the
assistance all!
-
Proposed as answer by
Paul Winstanley [SCCMentor]
16 hours 49 minutes ago
March 26th, 2015 10:54am