Search the Community
Showing results for tags 'compliant'.
Hi all, I've headed here to post my problem as I've spent the best part of 2 weeks on and off troubleshooting and I'm not getting anywhere. The company I'm currently working for now have a mixture of Windows 10 clients in their environment. 1511, 1607, 1703, 1709. We've been plugging away for months now to try and clear the last few hundred 1511 clients as we suffered from the WSUS decryption key issue with Feature Updates, but this was resolved and seemed to be working fine. We don't use servicing plans at all as we prefer to control the deployments more manually via direct deploym
Hi everyone We are having a weird issue, which I cannot see the reason why! - I have a Windows 10 Servicing Plan setup for CB deployment to a collection. The plan worked a few months ago when I put one machine into it (if i remember rightly)... However we have just started to look into it a bit more and we're coming back with something odd. We add a machine into the collection, it is picked up by SCCM and shows in the deployment monitoring, but they show as compliant! - One machine is on 1511 and the other is on a very very old release, perhaps the first ever release to public. I h
Hi, Could someone please help me better understand how the compliance report actually determines which machines are compliant and not compliant. i have a sccm 2007 r3 wsus and mdt 2010 integration environment.... we have around 75% machines compliant and around 20% machines none compliant and the rest unknown. ive gone through the logs of machines and machines are receiving windows updates but i cannot workout what actually determines machine from being compliant and not compliant.... i need to have the compliance above 90% to keep the managers happy. any help would be