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
ConfigMgr Package/Program… will retry later
Jason Sandy’s has a great blog explaining ConfigMgr Package/Program retry behavior including the Retry return/exit/error codes and how often the retry occurs. One bit of info missing from the blog that I couldn’t find anywhere else (documentation, forums, blogs, etc.)
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
ConfigMgr Status Filter Rule with alternate credentials
A recent customer wanted an automated SSRS Report Email Subscription anytime a new deployment was created. I’d been pondering how do accomplish that for some time, but finally got a catalyst and a bit of time. I found a PowerShell
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”
GitHub embedding
This is an example of embedding a GitHub repository script in WordPress using the WP-GitHub plugin (with customized prism.js to add PowerShell, Batch, SQL and AutoIt language support) And an example of a custom plugin (not yet published) with shortcode:
ConfigMgr and SQL – NTFS allocation unit size
It’s been many years since I read that SQL databases should use an NTFS volume formatted with at 64KB file allocation unit size (block size). So long that I didn’t remember why or if it is still considered best/good practice.