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
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.)
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
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.
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.
Several ConfigMgr scenarios require that the content Source Path be changed. This typically includes migrating to a new ConfigMgr environment (2007 to 2012, 2012 to Current Branch, etc.), and simply moving the source content to a new location such as
At one time it became routine to manage Windows local account passwords with a Group Policy Preference. However, some time ago the process was was discovered to have a significant venerability and Microsoft released security bulletin MS14-025 to address the
Awhile back I had an issue distributing a new Package in ConfigMgr (SCCM). There didn’t seem to be anything unique about the package, it just didn’t want to process. Digging into the SMS Distribution Manager log (distmgr.log), I noticed a