A problem is just a solution waiting to be found
A vulnerability was found in 7-Zip 21.07 that can be exploited through the 7-Zip Help file. This post will show how to remediate this vulnerability by deleting the 7-zip.chm file. In this post I will show you 2 ways you can accomplish this:
With a MECM (SCCM) configuration item deployment and with Intune script. In this post I will remediate the 7-zip (all versions) 64 bits version with MECM, and only the 21.07 (32 and 64 bits) version with Intune.
If you have setup Co-management in your MECM console you can now manage devices from the Microsoft Endpoint Manager Admin Center. If you want to know what you can do with the Microsoft Endpoint Manager Admin Center read this walktrough from Microsoft.
In this post I will show you how you can fix the Configuration missing error if you want to use one of the following features when selecting a device that is Co-managed: Resource explorer (preview), Client details (preview), Timeline (preview), Collections (preview), Applications (preview), CMPivot (preview) and Scripts (preview). In this post i will be using MECM version 2010.
A lot of company’s are still managing there devices on premise with domain joined devices and with MECM (SCCM). But with the pandemic most employees are working at home on there personal device or on a domain joined mobile device. Managing the domain joined devices that are being used at home is quite challenging. Off course you can deploy your applications and windows update with MECM and an active vpn connection.
But still how often do employees connect with the vpn application? If they don’t the device will become unsecure because of missing windows updates and missing application updates. You want these kind of devices to be updated and managed even without an active vpn connection. To be able to do this we can setup co-management in MECM. In this post I will show you how to setup co-management in MECM 2006.
