Any idea when? That would seem to mean that not all our machines got the
update. That’s certainly possible given the propensity of some of our offices
to turn machines off and put them in a closet when they aren’t actively in use,
but I would expect it to have been most updated and a few didn’t instead of a
few updated and most didn’t. ☺
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
From: listsadmin@lists.myitforum.com [mailto:listsadmin@lists.myitforum.com] On
Behalf Of Mayo, Bill
Sent: Tuesday, April 12, 2016 12:54 PM
To: ntsys...@lists.myitforum.com
Subject: RE: [NTSysADM] Service config change
The behavior changed after some specific update was applied. We noticed it,
too. As far as we can tell, everything seems to be working as expected under
the new method.
From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com>
[mailto:listsadmin@lists.myitforum.com] On Behalf Of Charles F Sullivan
Sent: Tuesday, April 12, 2016 12:44 PM
To: ntsys...@lists.myitforum.com<mailto:ntsys...@lists.myitforum.com>
Subject: RE: [NTSysADM] Service config change
If I run the same query against a Windows 10 machine as well as a Windows 2012
R2 server, I get the same results even though they are linked to different GPOs
(other than the default domain one). Both are Manual (Triggered) Start. I don’t
think anything is being determined by Group Policy for you since we see the
exact same thing. I assume most others out there are as well(?).
I noticed the start type myself recently. It seemed odd, but I guess I assumed
it had already been that way on newer Windows versions and that I had never
noticed.
From: listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com>
[mailto:listsadmin@lists.myitforum.com<mailto:listsadmin@lists.myitforum.com>]
On Behalf Of Melvin Backus
Sent: Tuesday, April 12, 2016 10:35 AM
To: ntsys...@lists.myitforum.com<mailto:ntsys...@lists.myitforum.com>
Subject: [NTSysADM] Service config change
We’re seeing a rather disturbing change in systems here. The disturbing part
may just be lack of understanding, but we’re seeing machines change from having
the Windows Update service set as Automatic (Delayed Start) to Manual
(Triggered Start). So far my investigation has lead me to find that the
trigger is tied what appears to be a group policy event. Can anyone enlighten
me? This is the output from all the changed machines. They don’t appear to be
version dependent so I’m leaning toward a possible Windows Update change. So
far my google-fu is only turning up explanations about what the configuration
means, nothing about when/why it might have changed.
>sc qtriggerinfo wuauserv
[SC] QueryServiceConfig2 SUCCESS
SERVICE_NAME: wuauserv
START SERVICE
GROUP POLICY : 659fcae6-5bdb-4da9-b1ff-ca2a178d46e0
[MACHINE POLICY PRESENT]
START SERVICE
GROUP POLICY : 54fb46c8-f089-464c-b1fd-59d1b62c3b50
[USER POLICY PRESENT]
--------------------
Melvin Backus | Sr. Systems Engineer | Byers Engineering Company | 404.497.1565
Service Desk | 404-497-1599 | http://servicedesk.byers.com
--
There are 10 kinds of people in the world...
those who understand binary and those who don't.
