Windows 10 Toast Notification Script Update: Check for Active Directory Password Expiration

July 23, 2020September 24, 2019 by Martin Bengtsson

Introduction

My Windows 10 Toast Notification Script has received another update, now being on version 1.4. What’s new and delicious are mentioned in details below.

Note: I know that expiring passwords are not ideal, but reality is that many still have them configured like so while trying to find their way out with Windows Hello for Business, Password-Less etc.

The toast notification might even serve as a good entry point into enrolling into WhFB when one are ready to do so. I’ll make an example of such in the future 🙂

Find the original page for the Windows 10 Toast Notification Script here: https://www.imab.dk/windows-10-toast-notification-script/

Windows 10 Toast Notification Script updated to version 1.3

July 23, 2020August 21, 2019 by Martin Bengtsson

Introduction

As the topic suggests; my Windows 10 Toast Notification Script has been updated to version 1.3 and here’s what’s new and delicious. 😀

Note: The screenshot below is intentionally in jibberish (danish). This is to illustrate that all text elements now are customizable through the config file.

Find the Windows 10 Toast Notification Script here: https://www.imab.dk/windows-10-toast-notification-script/

Windows 10 Toast Notification Script Update: Personal greeting and protocol based reboot

July 23, 2020June 4, 2019 by Martin Bengtsson

Introduction

Short and sweet. My Windows 10 Toast Notification Script have received a minor update. Now being at version 1.2. The changes mentioned in details below.

Find the original page for the Windows 10 Toast Notification Script here: https://www.imab.dk/windows-10-toast-notification-script/

SCCM Client Health Monitor: Automatically remediate Provisioning Mode and corrupt local Group Policy files

August 16, 2019July 5, 2018 by Martin Bengtsson

Introduction

Update: This post has been superseded with this: https://www.imab.dk/sccm-client-health-monitor-script/

A ConfigMgr/SCCM client stuck in provisioning mode or having corrupt local group policy files (Registry.pol) are two very common and nagging issues in a Configuration Manager environment. Where it’s rather easy to use Configuration Manager to remediate the corrupt policy files, it’s another story with a SCCM client stuck in provisioning mode (the client has very limited functionality). I haven’t personally been seeing clients in provisioning mode that often, but I do occasionally see it happen following an Windows in-place upgrade .

Both scenarios will cause a drop in compliance in regards to Software Updates and general software deployments, and unless being very thorough when walking through compliance reports, clients being affected by either issues can be difficult to spot, especially in larger environments.

So I hereby give you my solution to how you can automatically remediate both issues outside of Configuration Manager using Powershell and thus increase the compliance and overall health of your environment.

Powershell snippet from running the SCCM ClientHealthMonitor script