I will be posting a new blog series for co-management in the coming months. This post will highlight the undesirable effect some Group Policies will have on a successful co-management Intune enrollment. Co-management will allow you to automatically enroll your SCCM clients into Intune, if they are in scope. Recently I was asked to look […]
Co-management Intune MDM enrollment failure 0x80180026 Read More »
It started with a Tweet… I promised on Twitter that I would write this post if I had 20 peoples interest… Background We had a requirement to deploy Desktop Shortcuts, to the Windows 10 Public Desktop, for a new application. The shortcut was deployed using Group Policy Preferences (GPP). Below is a link to a
Deploy Windows 10 Desktop Shortcuts and Icons with SCCM Configuration Baselines Read More »
What are Servicing Stack Updates? Servicing Stack Updates (SSU’s) are Critical, Security Updates. They are shipped separately to the monthly Latest Cumulative Updates (LCU’s) because they modify the component that installs Windows updates. Microsoft strongly recommend that you install the latest SSU before the LCU. More information on SSU’s can be found at:- https://docs.microsoft.com/en-us/windows/deployment/update/servicing-stack-updates#why-should-servicing-stack-updates-be-installed-and-kept-up-to-date Microsoft
Windows 10 – Servicing Stack Cadence Read More »
Starting Windows 10 1809 Remote Server Administration Tools (RSAT) is now included as a set of “Features on Demand”. In the following post we will show you how to deploy individual features with SCCM. The RSAT tools are added using the “Add-WindowsCapability” cmdlet https://docs.microsoft.com/en-us/powershell/module/dism/add-windowscapability?view=win10-psBecause we are deploying each feature with an appliction, we are going
Deploy RSAT for Windows 10 1809 using SCCM Read More »
Background Since SCCM 2012 Microsoft have been steering us towards using “applications” to install apps over the traditional “packages” method. Applications give us additional benefits over packages like detection methods, dependencies and requirement rules . An example might be:- Install APP-B if the folder “C:\Program Files\APP-B_FOLDER” doesn’t exist (detection), only if APP-A is already installed
Converting legacy packages into applications with SCCM 1810 Package Conversion Manager Read More »
Try saying that title again without taking a breath, phew. We have been playing with ADRs (Automatic Deployment Rules) for a while now. The teams are slowly coming around to the idea that we are now delivering server updates in a more controlled fashion than WSUS could ever provide with useful reports icing the top
I’ve seen this subject discussed and explained very well in other blogs. The following post is my approach and understanding on managing Collection Evaluations using a bit of PowerShell (ok so there is some SQL stuff in here too). Collection Evaluations A Collection Evaluation occurs on a defined schedule, event trigger or user initiation and
Identifying and Updating SCCM Collection Evaluations with PowerShell Read More »
This SSRS Report has been sitting in the side lines for a while now. After spending a bit more time on it over the weekend I feel it is now at a point where it is serving me rather than the other way around. Our teams wanted to know how many updates were outstanding for
SCCM Software Compliance Report Filtered by Update Classification and Update Age Read More »
In this blog post we will look at signing the PowerShell scripts we use in the “App Detection Method” when distributing apps with ConfigMgr. The PowerShell Execution Policy can be modified in Client Settings to allow ConfigMgr to execute unsigned scripts. If your environment needs to be a bit tighter with script execution and you
Signing PowerShell Scripts for an SCCM App Detection Method Read More »
POST UPDATED HERE https://byteben.com/bb/sccm-software-compliance-report-filtered-by-update-classification-and-update-age/ I wasn’t getting what i needed from the built in SCCM SSRS Reports. Admins were asking for it to be made easier to understand how bad the number of outstanding updates were for the systems they have ownership of. For example, how many of the outstanding updates are 0-30 days old
