PENDING Enablement Package 21H2 showing as compliant when not installed

[david.gardner]

Hi guys,

I´m trying to update a machine to 21H2 from 20H2 via the Enablement Package in SCCM but it´s saying that it´s in Compliant so doesn´t install, but the machine still has the version 20H2 installed. Any ideas why this could be?

Best wishes and thanks in anticipation.

 

[Prajwal Desai]

Is the machine updated with latest patches?.

 

[david.gardner]

Thanks Prajwal, I´ve just checked and it looks like it´s not fully upd-to-date. I´update it now and see if it works and report back.

 

[david.gardner]

Hi Prajwal, it is updated to the latest patches yes but still it is in compiant even though it remains on 20H2. Any other ides?

On a separate point - whats the best way to handle Disk encryption? we have a mixture of Bitlocker and Symantec. Is it a better idea to deploy the enablement pack and the user is unaware of the update, so when he or she restarts the machine it asks for the key as usual?

The client has asked for the disk encryption to be removed and then reconfigured but I see this a security risk in case the deployment fails and it leaves the laptop unencrypted.

Thanks for your advice.

David