If you are using System Center Configuration Manager Current Branch (aka SCCM, aka Microsoft Endpoint Configuration Manager) a new version – 2107 – has just been released and there few things you need to know. In case you did not follow the previous releases, support for the “Application Catalog Website Point” and “Application Catalog Web […]
As you know, System Center Configuration Manager Current Branch (SCCM CB) – aka Microsoft Endpoint Configuration Manager – can be integrated with Intune (aka Microsoft Endpoint Manager) to provide hybrid device management capabilities, also called co-management. This integration is called tenant attach onboarding. Well, while this hybrid device management provides lot of value for SCCM
Intune – You can now offboard your hierarchy Read More »
If you are using System Center Configuration Manager Current Branch (SCCM Current Branch) version 2006 in a co-management configuration with Intune/Endpoint Configuration Manager, you can now launch the scripts created in SCCM from the Endpoint Configuration Manager portal. Before being able to do it, you first need of course to have created a script in
Intune – You can now launch script from SCCM from the Intune portal Read More »
The close integration of SCCM and Intune/Endpoint Configuration Manager has made one more step. As you know, you can now see Device Collections and SCCM Client Details from the Intune/Endpoint Configuration Manager (see https://t.co/mp0I0MntlM). Well, now you can also get access to the CMPivot feature (see https://docs.microsoft.com/en-us/mem/configmgr/core/servers/manage/cmpivot), a timeline showing the last activities or Resource
Intune – More devices information now available Read More »
As you know, SCCM and Intune/Endpoint Configuration Manager are being more and more close with each other. Well, now you can define and apply Microsoft Defender policy from Endpoint Configuration Manager on devices managed by SCCM. To be able to do it, you need to use the latest version of SCCM Current Branch 2002 with
If you are using System Center Configuration Manager Current Branch (SCCM CB), also known as Microsoft Endpoint Configuration Manager Current Branch, in co-management mode, you can now also use the Company Portal application for the software deployment workload. To be able to use the Company Portal for your software deployment when the Client apps workload
SCCM – You can now use the Company Portal for software deployment Read More »
If you are working with System Center Configuration Manager Current Branch 2002 (SCCM CB 2002) and Intune/Endpoint Configuration Manager in a co-managed configuration, you can now launch Device Sync or Device Action from the Intune/Endpoint Configuration Manager portal. Before you are able to do such thing, you need to meet some requirements: First you need
Following the release of the latest version of System Center Configuration Manager (SCCM) Current Branch, 1910, also known now as Endpoint Configuration Manager (ECM) Current Branch 1910 (see https://t.co/ac1nnORrrN), you can enable support for Windows 10 Multi Session (aka Windows Virtual Desktop) by enabling the setting in the SCCM Client Settings\Client Policy This will allow
SCCM – Enable Windows Multi Session support Read More »
The latest release of System Center Configuration Manager Current Branch (SCCM CB) – now known as Endpoint Configuration Manager Current Branch – is now available. Endpoint Configuration Manager Current Branch 1910 will be made available through the in-console update (as always) over the next few weeks to customers but if you want to get it
Recently I have been running a problematic 100% disk active time on my System Center Configuration Manager (SCCM) environment. SCCM has been running quite smoothly for few years; running on Windows Server 2019 with SQL co-located. One day I noticed the disks, where the databases are save, were continuously active (100% disk active time) and
SCCM – The case of 100% disk active time Read More »
