Evaluate ConfigMgr Client Policy with PowerShell

This is how I use PowerShell to force the Configuration Manager client to force evaluate policy.

The following PowerShell code will force machine policy evaluation.

$trigger = "{00000000-0000-0000-0000-000000000021}"
Invoke-CimMethod -Namespace 'root\ccm' -ClassName 'sms_client' -MethodName TriggerSchedule -Arguments @{sScheduleID=$trigger}
Start-Sleep -Seconds 10
$trigger = "{00000000-0000-0000-0000-000000000022}"
Invoke-CimMethod -Namespace 'root\ccm' -ClassName 'sms_client' -MethodName TriggerSchedule -Arguments @{sScheduleID=$trigger}

The list below is a reference of ScheduleIDs and their respective policy

Read More
Microsoft 365 Apps

Auto Update M365 Apps installation package in MEMCM with PowerShell

How to auto update M365 Apps installation package in MEMCM with PowerShell and a scheduled task.

I wanted a process that would automatically update the installation package files for Microsoft 365 Apps on a schedule and then update the distribution points in Microsoft Endpoint Manager Configuration Manager (MEMCM). This would ensure that whenever an OSD task sequence ran, M365 apps / Office 365 would install using the latest version for the selected channel, and no updates where required once the task sequence was complete.

Read More
ConfigMgr Client Health

ConfigMgr Client Health 0.8.0 – Introducing Webservice

I’m happy to release version 0.8.0 of ConfigMgr Client Health, and introduce a webservice to communicate with the database.

The script now supports updating the database through a RESTful API, which simplifies and secures communication with the database. Using the -Webservice parameter, the script sends the results to the webservice, which then updates the database. Computer accounts no longer requires write access to the database in order to update it. Read More

ConfigMgr Client Health

ConfigMgr Client Health 0.7.6 Released – Important bugfix

ConfigMgr Client Health version 0.7.6 is released, and this version includes an important bugfix.

The previous version (0.7.5) introduced a new test that added a dependency on the smstsmgr service. Unfortuenatly this change ended up breaking the upgrade task sequence, something that my tests never caught as I never tested running an upgrade task sequence before releasing a new version. My test protocol is now updated, and this is something I will start testing from now now. Read More

adk 1703 missing tabs sccm

ADK 1703 Missing Tabs in SCCM

ADK 1703 missing tabs in SCCM. I ran into a weird issue today after upgrading one of our customers to ADK 1703. We previously upgraded SCCM to version 1702 but choose to wait with ADK because of the driver signing issue. When we finally upgraded ADK to 1703 and created a new boot image, the tabs in SCCM to service the new 1703 boot image where missing and I could not add any drivers or optional components with the console. Read More

SCCM Upgrade stuck checking prerequisites

SCCM Upgrade Stuck Checking Prerequisites

Today I upgraded a customer to SCCM 1702, but I ran into an issue that made things difficult. For some reason, they had a SCCM upgrade stuck checking prerequisites. A previous hotfix that was not installed had been in this state for a very long time and blocked all upgrades for them. Restarting SMS_Executive service or even rebooting the server did not fix this, and the option to upgrade was not available as SCCM thought some other upgrade was running a prerequisite check. This is how I fixed it. Read More