the place to look would be that client repair check log. It list what it
checks. If it checks it I would assume it fixes it. Also might tell you in
the console on client health actions.
On Fri, Mar 17, 2017 at 8:28 AM, David Jones wrote:
> I have found the same to be
That I'm unsure of. I know it needs it to be enabled to function, so I
would say 'yes.'
On Fri, Mar 17, 2017 at 9:49 AM, David Jones wrote:
> Actually, yes I meant the Windows Updates service on the Exchange servers.
> My understanding is it wasn't disabled by GP, just
Actually, yes I meant the Windows Updates service on the Exchange servers.
My understanding is it wasn't disabled by GP, just manually disabled.
So could the ConfigMgr Client re-enable a manually disabled Windows Updates
service on a client if SUP was set to yes in the client settings?
On Fri,
The actual Service? That shouldn't be disabled.
The only thing you want to disable in Group Policy is 'Automatic Updates.'
The service is still leveraged for WU through the ConfigMgr Client.
On Fri, Mar 17, 2017 at 8:28 AM, David Jones wrote:
> I have found the same to
I have found the same to be true. But does anyone know, is it
expected/normal behavior for the SCCM client to enable Windows Updates
service on a computer/server that has it disabled if the SUP policy is
enabled in the client settings?
On Thu, Mar 16, 2017 at 4:26 PM, Todd Hemsell
I have found the best approach to take when accused of something is to own
it.
Oops, yes.. I certainly is possible that there was an unintended
consequence of what I did. Let me go and investigate.
Then come back to them with the names of logs, and screenshots or
copy/paste of the relevant lines
Thanks Todd!
On Thu, Mar 16, 2017 at 3:36 PM, Todd Hemsell wrote:
> For the exchange servers, look in the event logs, specifically the setup
> log. It will be in there.
> SCCM can install something and not reboot, THEN the AU agent on the server
> kicks in, sees it needs a
For the exchange servers, look in the event logs, specifically the setup
log. It will be in there.
SCCM can install something and not reboot, THEN the AU agent on the server
kicks in, sees it needs a reboot, and bounces the machine.\
For the WSUS, look in the C:\Windows\WindowsUpdate.log for
8 matches
Mail list logo