Overview

This video tutorial will look at the different options we have to deploy a Configuration Manager client to Windows computers. We’ll cover the following methods:

• Install Method 1:Client push installation
• Install Method 2: Software update-based installation
• Install Method 3: Group Policy installation
• Install Method 4: Manual installation

Topics in Video

• Introduction: (0:00)
• Reviewing Prerequisites for deploying clients to Windows Computers: (0:54)
• Best practices for deploying clients: (2:23)
• Have you extended the Active Directory Schema?: (2:30)
• Client Push Installation Method: (5:01)
• Advantages and Disadvantages of the Client Push Installation Method: (5:13)
• Overview of the current lab setup: (6:50)
• Attempting a client push installation: (7:40)
• Reviewing the ccm.log: (9:07) Creating Group Policy for Firewall Rules: (10:37)
• Running gpupdate /force on Demo Client: (12:29)
• Second attempt at client push installation: (13:23)
• Reviewing the ccm.log after the second attempt: (13:50)
• Configuring a Client Push Account: (14:07)
• Creating a local admin Group Policy: (15:24)
• Final attempt at client push installation: (17:50)
• Verifying installation of client: (18:04)
• Performing an Automatic Client Push Installation: (22:45)
• Verifying Installation of client: (27:55)
• Software Update-Based Installation: (29:05)
• Advantages and Disadvantages of Software Update-Based Installation: (29:29)
• Best Practices for Software Update-Based Installation: (30:35)
• Initiating the Software Update-Based client installation: (31:50)
• Viewing the Configuration Manager Client update in the Patch My PC Publisher: (33:37)
• Creating a policy to scan against the Software Update Point: (34:53)
• Verifying policy applied on the client machine: (40:57)
• Running a Windows Update check: (41:37)
• Verifying installation of client: (41:59)
• Configuring site assignment by creating an SCCM Site Assignment Policy: (43:55)
• Group Policy Installation Method: (47:00)
• Verifying installation of client: (54:00)
• Manual Installation Method: (56:02)
• Advantages and Disadvantages of the Manual Installation Method: (56:02)
• Initiating Manual Installation of client: (58:23)
• Verifying installation of client: (1:00:12)
• Performing manual installation when you do not have your site information published to Active Directory: (1:00:23)
• Verifying installation of client: (1:02:21)
• Wrap-up: (1:03:03)

Helpful Resources:

• Install Method 1: Client push installation
• Use software update-based client installation for Active Directory computers
• Specify Intranet Microsoft Update Service Location local policy
• Extend the Active Directory schema and publish the site so that you can run CCMSetup without command-line options
• If you install the client with client.msi properties, use SMSMP and FSP

Registry Updates

Note: A full guide for this process in the video is available on: https://www.anthonyfontanez.com/index.php/2021/09/01/configmgr-client-deployment-via-software-update/ 

• SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
  WUServer
  • WUServer
  • String
• SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
  • WUStatusServer
  • String
• SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
  • UseWUServer
  • DWORD = 1
• SYSTEM\CurrentControlSet\Services\CcmExec

Command Lines and Other Examples

• ccmsetup.exe command lines options = SMSSITECODE=DM1 FSP=DEMO1.CONTOSO.LOCAL MP=DEMO1.CONTOSO.LOCAL
• gpresult /R /SCOPE COMPUTER /Z

Overview

In this video, we will be covering how to migrate from one ConfigMgr site to another. Specifically, we will look at migrating a ConfigMgr 2103 Site to another 2103 Site. This process is similar if you were migrating from a different version of ConfigMgr (Source Site) to the ConfigMgr Current Branch (Destination Site). All the same concepts would apply to those situations.

Topics in Video

• Introduction – (0:00)
• Reviewing Microsoft Doc on Migrating data between hierarchies in ConfigMgr – (0:39)
• Lab Overview – (1:22)
• Reviewing the requirements, concepts, and prerequisites for the ConfigMgr Site Migration – (2:09)
  
• Reviewing the objects we plan to migrate from the source site – (5:35)
• What objects can you migrate? – (7:37)
• Configuring the source hierarchy on the destination site – (8:30
• Going over the migmctrl.log – (10:48)
• Configuring the Infrastructure Administrator role on the source site – (11:28)
• Attempting another data gathering on the destination site – (13:12)
• Revisiting the migmctrl.log – (13:29)
• Configuring the Source Site Database Account – (14:01)
• One more attempt at gathering data – (16:47)
• Successful data gather – (17:15)
• Creating a Migration Job – (17:30)
• Reviewing migmctrl.log to view permission errors – (21:12)
• Taking a look at the built-in Infrastructure Administrator security role – (21:42)
• Options for how to fix the permission errors – (22:20)
• Restarting the Migration Job – (23:22)
• Creating another Migration Job – (24:33)
• Deploying application to see what it looks like to also migrate deployments to the destination site – (25:22)
• Running another Data Gather to re-evaluate the source site – (26:15)
• Creating another Migration Job – (27:02)
• Looking at the migmctrl.log after creating the Migration Job – (29:55)
• Reviewing the Object Migration Progress – (30:33)
• Digging into the objects that failed – (31:11)
• Starting the Migration Job again – (35:13)
• Digging into the remaining failed Object – (36:50)
• Let’s talk about the content source location – (39:15)
• Overview of the ConfigMgr Content Source Update Tool – (40:02)
• Wrap-up – (41:41)

Helpful Resources:

• Migrate data – Configuration Manager | Microsoft Docs
• Migration job planning – Configuration Manager | Microsoft Docs
• Migration prerequisites – Configuration Manager | Microsoft Docs
• ConfigMgr Content Source Update Tool 1.0.0 – MSEndpointMgr