Uninstalling the ConfigMgr (MECM / MEMCM / SCCM) client, can be as simple as running this command with administrative rights C:\Windows\CCMSetup\CCMSetup.exe /uninstall But when you need to cleanup ALL of the remnants of the ConfigMgr client there’s a bit more
Easy IIS log reading for ConfigMgr
This is just a bit of PowerShell to make reading and filtering IIS logs quick and easy. #.Synopsis # Convert IIS log file to CSV #.LINK # Based on https://stevenaskwith.com/2012/05/22/parse-iis-log-files-with-powershell/ # Performance inspired by http://www.happysysadm.com/2014/10/reading-large-text-files-with-powershell.html ########################################################################################################### #define the ConfigMgr Distribution Point’s IIS log
ConfigMgr: Get primary users with email for a collection
Have you ever needed to send an email to all of the primary / last logged on / currently logged on user for every computer in a collection? Here’s a nice little PowerShell script that can help you out with
Report all ConfigMgr admin console users
So, who exactly has access to the ConfigMgr admin console? This bit of PowerShell will generate a CSV report of each Active Directory user in each role/group*. *Note: nested groups are not yet supported. #.LINK https://github.com/ChadSimmons/Scripts/blob/default/ConfigMgr/Document/Get-MECMAdminConsoleUsers.ps1 $SiteCode = ‘LAB’ $SiteServer
Windows 10 Upgrade without Upgrade Readiness
When Microsoft made the Upgrade Readiness solution freely available to anyone back in the Spring of 2017 it was a major step forward in the monumental task of upgrading Windows 7 and Windows 8.1 computers to Windows 10 and keeping
ConfigMgr Chassis Type Global Condition / Requirement
Working with a customer recently we wanted to deploy a ConfigMgr Application to all all laptops in the organization without creating a new collection of just laptops. Using the ChassisTypes property of the Win32_SystemEnclosure WMI namespace is a great way
Parse env:Path with PowerShell
The environment variable PATH (combined SYSTEM PATH and USER PATH) can be tricky to parse if you want to check for each folder it contains. This is due to the support of various formatting styles. For example, this is a
The many ways to import the ConfigMgr cmdlet Library module
Over the years I’ve seen and used a variety of PowerShell commands to get the ConfigurationManager.psd1 file location to pass to Import-Module Just for fun, I compiled a list of the different methods. It’s all about string manipulation. [read-more-redirect urltext=”CatapultSystems.com”