Step-By-Step: Cloud Management Gateway

Introduction ConfigMgr 1610 introduced the Cloud Management Gateway, an Azure based solution to manage clients on internet. The benefit is that you don’t expose your infrastructure on the internet. The Azure VM(s) running behind the Cloud Management Gateway (Azure web service) are managed by Microsoft. At a high level, the clients communicate to an Azure…

42

Step-by-step: Highly available Site server

The release of ConfigMgr 1806 introduced the concept of high availability of the Site server by adding an additional primary site as passive node. This post takes you through a step by step journey in configuring a highly available Site Server. Here’s a high-level architecture overview of the configuration which depicts a remote SQL AlwaysOn…

22

Windows 10 Compatibility Scan with Configuration Manager

Before deploying Windows 10, it’s a good idea to check the readiness of your existing machines running Windows 7, 8/8.1, Or even Windows 10. In this blog post I will use setup.exe with /compat scanonly switch to check the compatibility without performing the upgrade. The reason for not choosing the Upgrade task sequence for this…

18

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…

14

Modern Management of Internet Clients

The release of ConfigMgr Tech Preview – 1705 introduced new cloud based client management capabilities like on-boarding Azure AD users and deploying ConfigMgr client over Internet. Common scenarios like BYOD or Un-Managed/Workgroup devices in the field can now join Azure-AD which gets enrolled into Intune & automatically pushes the ConfigMgr agent for full management. The…

10

Step-By-Step: Cloud Management Gateway on ARM

Introduction Starting ConfigMgr 1802 Cloud Management Gateway is NO longer a Pre-release feature and introduced the option of Azure Resource Manager [ARM] deployment. This removes the requirement of the traditional Azure Management Certificate and relies on Azure AD auth. to create the modern resources. Note – The CMG deployment with ARM continues to use the…

8

Step-By-Step: Installing a fresh Configuration Manager 1606 Site hosted on SQL Server AlwaysOn

Introduction With the release of Configuration Manager 1606 full media, you can install a fresh ConfigMgr database on SQL AlwaysON configuration. Here’s a Step By Step procedure to go about installing one. Environment A snapshot of the environment I am using to demonstrate this feature. Role Server Name Operating System Domain Controller DC1 Windows Server…

7

Client Installation over Internet

System Center Configuration Manager 1706 simplified the capability to install (bootstrap) the client over internet, this blog post walks through two scenarios – AAD joined device – Modern management of Windows 10 devices leveraging Azure. Workgroup device – Servers on DMZ without corporate network access Prerequisites The table below lists the requirements for each scenario…

6

CMG with just One Cert

You read it correct! Cloud Management Gateway has evolved and its now easier than ever to deploy one. All you need is a single Web Server Authentication Certificate from a public CA. What changed? Primarily the introduction of a new feature in ConfigMgr 1806 called Enhanced HTTP Site System which replaces the requirement of an…

6

SQL Server Native Client Update Warning Prerequisite for ConfigMgr 1810

If you are planning to upgrade your ConfigMgr infrastructure to the latest 1810 release, plan for updating the SQL Server Native Client to support TLS 1.2 If the SQL Server native client isn’t already updated, the prerequisite check will fail with below warning. The details are available in the ConfigMgrPrereq.log <11-27-2018 20:27:21> PRIMARY1<FQDN>; SQL Server…

3