As you may already know, System Center Configuration Manager (SCCM) and Intune can work together, delivering a co-managed device management solution. Well, you can now use the compliance state from SCCM with Intune. This setting will only apply to co-managed devices, if the devices are managed by Intune only, this will not be applicable. To […]
Intune – You can now check the compliance from SCCM Read More »
An update for System Center Configuration Manager Current Branch (SCCM 1810) has been made available and solves the issue with the incorrect Windows version displayed when updating Windows Server 2019 image (as explained here https://t.co/AoTjH1q0pS Additional fixes are also available: see https://support.microsoft.com/help/4486457
If you use System Center Configuration Manager (SCCM) to manage updates deployment, OS deployment and additionally keeping up to date your OS image (WIM), you need to know that SCCM offline servicing is incorrectly detecting Windows Server 2019 WIM image as Windows Server 2016. This has been confirmed as a bug in SCCM and should
SCCM – Offline servicing for Windows Server 2019 is not working Read More »
With the latest System Center Configuration Manager (SCCM) Current Branch update (build 1810), you can now request a client restart using the SCCM console. To do so, open your SCCM console and reach out the Devices section from the Assets and Compliance workspace to select the device you want to restart Right click on the
SCCM – You can request a client restart from the SCCM console Read More »
With the latest update of System Center Configuration Manager (SCCM) Current Branch (build 1810), it is now possible to repair installed application from the Software Center. The option ‘Allow end-users to attempt to repair this application’ need to be enabled when you deploy the application Once your new application is created and available in the
SCCM – It is now possible to repair installed application from the Software Center Read More »
Following the availability of the new SCCM Current Branch build (1810), it is now possible to use the built-in SCCM task sequence to use Autopilot when deploying OS. To use it, you need to create an SCCM package which will contains the Autopilot settings and use the SCCM tasks sequence (this is not available for
SCCM – Use Autopilot when deploying OS Read More »
The latest build, 1810, of System Center Configuration Manager (SCCM) Current Branch is now available. As always it is currently being rolled out and may become available in your In-Console update within the next few weeks, and if you do not want to wait you can use the now famous script available here https://gallery.technet.microsoft.com/ConfigMgr-1810-Enable-57a7c641 As
SCCM – System Center Configuration manager 1810 Current Branch is now available Read More »
It seems it has not been widely and properly communicated As you may know with System Center Configuration Manager (SCCM) you were able to setup an hybrid mobile device management with Intune, meaning you were able to use Intune to register your device and use SCCM to manage them. So, since August 14th 2018, this
SCCM/Intune – Hybrid mobile device management is deprecated Read More »
With the latest update of System Center Configuration Manager (SCCM) Current Branch (build 1806), you can deploy updates without creating a package to be deployed. When you choose to deploy the updates without a package, the client will download the updates from Windows Update servers. The option is available when you create (or edit) an
SCCM – You can now deploy updates without package Read More »
With the latest update for System Center Configuration Manager (SCCM) Current Branch (build 1806), you can now select and use Azure Resource Manager (ARM) when deploying Cloud Management Gateway (CMG) and/or Cloud Distribution Point (CDP); this should now be your preferred option for such deployment. Using the SCCM Console, go to the Administration workspace and
