Kashif SCCM Blog

How to Setup SCCM Co-Management to Offload Workloads to Intune Windows 10 co-management is a dual management capability available with  Windows 10 1709 version (Fall Creators Update)  and later. Co-management is the bridge between traditional management and modern management. In this post, we will see how to setup SCCM Co-Management to offload 4 (four) workloads to Intune. Prerequisite SCCM Co-Management Configuration Wizard  To start the Co-Management Wizard, you need to have Microsoft Intune subscription. If you don’t have Intune subscription, you need to get a business account or trial version. More details to get a trial version of Intune is in the following post under “How to Start Working with Intune?”. SCCM Co-Management Auto Enrollment Options? To enable co-management for devices managed by SCCM,  configure Auto Enrollment . There are 2  Auto Enrollment in Intune  options available in SCCM CB co-management. Following are the  2 ...

STEP-BY-STEP SCCM 1806 UPGRADE GUIDE It is now time to plan the migration of your SCCM Current Branch environment since Microsoft releases a new version of SCCM Current Branch. If you want to receive the latest updates, this post is a complete step-by-step SCCM 1806 upgrade guide. If you’re looking for a comprehensive SCCM installation guide, see our blog series which covers it all. You won’t be able to install 1806 if you are running SCCM 2012, the baseline version is 1802. To install SCCM 1806 as an update, you must have installed at least SCCM 1706, SCCM 1710 or SCCM 1802. Keeping your infrastructure up to date is essential. You can benefit from the new features and fixes issues, which some of them can be related to your SCCM. It’s also easier to upgrade to the latest version since Microsoft has implemented the new model of update servicing which is the in-console upgrade. SCCM 1806 NEW FEATURES AND FIXES SCCM 1806 include...

HOW TO INSTALL SCCM CLIENT ON WORKGROUP COMPUTERS In this post, we will detail how to install the SCCM client on workgroup computers. PREREQUISITES The client must be able to resolve the FQDN of the management point. Depending on network security, it might not actually ping. The important is that it can associate the FQDN to the IP of the management point. Adding an entry to the  Host file  might be required. Port Client -> Management point :  TCP 80  or  443 Client -> Software Update Point :  TCP 8530  or  8531 More details on SCCM ports requirement,  here Manual installation of the SCCM client There is no way to use the Client Push Installation for workgroup computers Management Point must be provided in the install command line, as the client will not be able to find it in Active Directory Site code must be provided in the install command line SCCM CLIENT INSTALL WORKGROUP COMPUTERS Copy the source o...

Step-By-Step: Configuration Manager Site Database hosted on SQL Server AlwaysOn Availability Group Introduction Configuration Manager 1602 introduced the support of SQL Server AlwaysOn Availability Groups. Now we can host the Central/Primary Site databases into Availability Groups for high availability and disaster recovery purposes. Note  - This feature is supported for existing Site DBs and cannot be used during the initial ConfigMgr setup. Environment Here's a snapshot of the environment I am using to demonstrate this feature. Domain Controller DDC1 Windows Server 2012 R2 SQL Server SQL1 Windows Server 2012 R2 SQL Server SQL2 Windows Server 2012 R2 Primary Site PRIMARY1 Windows Server 2012 R2 SQL Configuration Both the SQL Servers are running identical configuration. Edition SQL Server 2014 Enterprise Sp1 Features Database Engine Management Tools Instance MSSQLSERVER (Default) Port 1433 (Default) Service Account Domain Account Mode Windows...