Download PowerShell Script to Enable Opt-In Version of SCCM 2006 Early Update Ring

Yes, there is a PowerShell Script to Enable Opt-In version of SCCM. I get many questions related to PowerShell script which you need to use to enable the FAST (Early/Opt-in) Ring version of Configuration Manager.

2006 Upgrade Guide – https://www.anoopcnair.com/sccm-primary-server-upgrade-to-2006-configmgr-guide-step-by-step/

Download PowerShell Script to Enable Opt-In Version of SCCM

You can download the script from the link here. And see the instructions here.

In this post, let’s see from where you can get the PowerShell Script to enable SCCM 2006.

Related Post – The Rings Story of SCCM – https://www.anoopcnair.com/slow-ring-vs-fast-ring-detailsearly-update-ring/

Introduction

You need to have an ONLINE Service connection point to enable the Opt-in (early update) ring of SCCM 2006.

NOTE! – You need to use the PowerShell script to enable the Opt-in version of ConfigMgr 2002 or Fast ring or Early Update ring version of 2006.

Once the 2002 version of Configuration Manager is Generally Available, then all your SCCM infra with the online service connection point will automatically get the 2006 update.

ONLINE Persistent Connection - PowerShell Script to Enable Opt-In Version of SCCM
ONLINE Sevice Connection Point – More details https://www.anoopcnair.com/learn-how-to-install-reinstall-sccm-service-connection-point-configmgr/ PowerShell Script to Enable Opt-In Version of SCCM

How to Run the PowerShell Script to Enable Opt-in RIng

  • You can open PowerShell ISE or prompt with administrative access.
  • You also need appropriate admin access within your SCCM environment (Full Admin is good).
  • Run the PowerShell Script to enable the opt-in ring
  • Enter the Site Server Name (FQDN)
  • Check the return message and confirm whether the command is the completed successfully or not
PowerShell to Enable Opt-in Ring -  Slow Ring Vs Fast Ring Details - Site Server Name (FQDN)
Site Server Name (FQDN) – PowerShell Script to Enable Opt-In Version of SCCM

Resources

SCCM 2002 Installation Step by Step Guide | MEMCM | ConfigMgr

I know you have seen many steps by step videos and installation guides to update Configuration Manager current version. This guide is another one that shows how to upgrade from SCCM 1910 to 2002 version.

New Features of Configuration Manager (A.K.A SCCM) 2002 version is given in the following post https://www.anoopcnair.com/configmgr-2002-list-of-new-features-enhancements-memcm-sccm/

NOTE! – Well, I know it’s not SCCM. It’s called Microsoft Endpoint Manager Configuration Manager (MEMCM) or Microsoft Endpoint Configuration Manager (MECM).

Prerequisites of 2002 Version

NOTE! – If you have SCCM DPs and PXE servers running on Windows server 2008 R2. You need to plan to upgrade it before the latest supported version before upgrading to the ConfigMgr 2002 version of the current branch. Server 2008 R2 DP and PXE are not supported anymore. More details – here.

  1. The following SCCM versions are supported for the upgrade to 2002.
  2. Install update 2002 at the top-level site of your hierarchy (CAS or Standalone Primary)
  3. SCCM version should have online Service Connection Point
  4. Evaluate Checklist
  5. Evaluate SQL Requirements for SCCM 2002 Upgrade – here
  6. Evaluate Windows Server OS Requirements for SCCM 2002 site server – here
  7. Evaluate Supported OS versions for clients and devices – here
  8. Evaluate Supported OS versions for ConfigMgr consoleshere
  9. Evaluate Recommended hardwarehere
  10. Support for Windows features and networkshere
  11. Evaluate Support for virtualization environments – here
  12. Evaluate the Firewall Rules – More details here and here

NOTE! – To download the update when your service connection point is offline, use the service connection tool.

SCCM 2002 Installation Step by Step Guide
SCCM 2002 Installation Step by Step Guide

Upgrade Check List

The following are the high-level checklist provided by Microsoft. Let’s go through this list before starting the upgrade in a production environment.

  • All sites run a supported version of Configuration Manager
  • Review the status of your product licensing
  • Review Microsoft .NET versions
  • Review the version of the Windows ADK for Windows 10
  • Review SQL Server Native Client version
  • Review file and data replication between sites
    • Database replication
    • File-based replication
  • Install all applicable critical Windows updates
  • Disable database replicas for management points at primary sites
  • Set SQL Server AlwaysOn availability groups to manual failover
  • Disable site maintenance tasks at each site
  • Temporarily stop any antivirus software
  • Back up customized files
  • Plan for client piloting
  • Plan to use service windows
  • Review supported extensions
  • Run the setup prerequisite checker (I recommend to run prerequisite check 3-4 day before the production upgrade)
  • Update sites

More detailed information about the ConfigMgr 2002 installation checklist is given below https://docs.microsoft.com/en

Download and Install 2002 version fo ConfigMgr

  • As this 2002 version of SCCM is part of the opt-in (early update) ring, you need to opt-in to have this update available in the console.
  • Opt-in using PowerShell command. Download and Run the PowerShell command.
  • Launch ConfigMgr console & navigate through \Administration\ Overview \Updates and Servicing.
  • Check 2002 fast or Opt-in version update of ConfigMgr is already available or not?
  • If not, click on the “Check for Updates” button from the ribbon menu
  • Click OK to continue
SCCM 2002 Installation Step by Step Guide
SCCM 2002 Installation Step by Step Guide
  • Configuration Manager 2002 update is available and Downloading

SCCM 2002 Download Stuck

This stuck download issue is a common scenario in enterprise organizations and LAB environments. This issue is mostly because of proxy or some other internet-related issues.

There are a couple of ways to fix this kind of issue if it’s not related to proxy and internet. You can refer to the previous blog posts to solve Update Download stuck problems.

More troubleshooting help on SCCM 2002 Download stuck and upgrade issues here and here .

Microsoft Doc ➡ https://support.microsoft.com/en-us/help/4490424/understand-and-troubleshoot-updates-and-servicing-in-configmgr

Downloading - SCCM 2002 Installation Step by Step Guide
Downloading – SCCM 2002 Installation Step by Step Guide

Log Files are Your Friend

  • DMPDownloader.log for SCCM 1910 source file download issues
  • ConfigMgrSetup.log for Redist Files Download Issue
  • CMUpdate.log for all the upgrade related activities
  • If the update displays as Downloading and doesn’t change, review the hman.log and dmpdownloader.log for errors.
    • The dmpdownloader.log may indicate that the dmpdownloader process is waiting for an interval before checking for updates. To restart the download of the update’s redistribution files, restart the SMS_Executive service on the site server.
    • Another common download issue occurs when proxy server settings prevent downloads from silverlight.dlservice.microsoft.comdownload.microsoft.com, and go.microsoft.com.
  • For more information about installing updates, see In-console updates and servicing.
  • For more information about current branch versions, see Baseline and update versions.

Download Completed

  • SCCM 2002 download is completed successfully
  • 2002 update is Ready to Install
  • Right Click on the Update “Configuration Manager 2002” Update
  • Select PreRequisite Check
    • Once the Prerequisite Check is completed successfully proceed to the next step
  • Right Click on the Update “Configuration Manager 2002” Update
  • Click on Install Update to start the SCCM 2002 installation
Ready to Install - SCCM 2002 Installation Step by Step Guide
Ready to Install – SCCM 2002 Installation Step by Step Guide

SCCM 2002 Update Prerequisite Check Stuck?

The SCCM upgrade prerequisite check can take many hours, depending on your hierarchy/infra. When you have CAS and many primary servers, the 2002 update source files will be copied to primary servers.

You can check the status of the prerequisite checks from the monitoring node. More details about SCCM prerequisite checks here.

Microsoft Documentation – https://docs.microsoft.com/en-us/configmgr/core/servers/deploy/install/prerequisite-checker

NOTE! – Make sure you start the prerequisite checks 3-4 days before the production update/upgrade of SCCM infra.

Configuration Manager Update Wizard

Let’s continue with SCCM 2002 update wizard:

  • Click on “Ignore any prerequisite check settings and install the update regardless of missing requirements” box
  • Click on Next button
  • Select the features you want to enable after the upgrades from Features Included in Update Pack page
    • ….
    • …..
  • Click on Next to continue
Features Included in Update Pack - SCCM 2002 Installation Step by Step Guide
Features Included in Update Pack – SCCM 2002 Installation Step by Step Guide
  • Client Update Settings page configuration
    • Upgrade without validating (Direct Production Upgrade)
    • Validate in pre-production collection (Test the client before the upgrade)
  • Click NEXT button to continue

Client Update Settings Option

Client Update Settings is another important option in Configuration Manager Update Wizard for SCCM 1810 upgrade. SCCM Client update settings include an update for SCCM client. You can upgrade your clients immediately. Or validate this client in pre-production collection before you upgrade all your SCCM clients.

I would recommend validating the client version with pre-production collection devices before upgrading the SCCM 1810 client package to all your clients directly.

Upgrade without validating

If you select the SCCM client upgrade without validating option, this overwrites your current SCCM client package with the new SCCM client update. All new client installations and client upgrades use this new client update.

Validate in Pre-production collection

If you select the “Validate in Pre-production collection” option, then you will get an option to validate the new client update on members of pre-production collection while you keep your production client package intact. Later once you are confident with the new client package, you can overwrite the production package using Client Update Options in the Updates and Servicing node of the SCCM console.

Client Update Settings page configuration - SCCM 2002 Installation Step by Step Guide
Client Update Settings page configuration – SCCM 2002 Installation Step by Step Guide

NOTE! – More details about SCCM Client Upgrade options “SCCM Client Upgrade Promote Pre-Production Client to Production.”

  • Click on “I accept these License Terms and Privacy Statement
  • Click on NEXT button to continue
License Agreement - SCCM 2002 Installation Step by Step Guide
License Agreement – SCCM 2002 Installation Step by Step Guide
  • Click on Close to continue to the installation process of 2002
Close - Start the Installation Process - SCCM 2002 Installation Step by Step Guide
Close – Start the Installation Process – SCCM 2002 Installation Step by Step Guide

Installation Progress

Once you complete the Configuration Manager update wizard, the SCCM 2002 upgrade process will kick start. And the updates and servicing node in the ConfigMgr console will show that the update is in installing state.

You can start monitoring ConfigMgr 2002 upgrade from this stage.

  • You can click on a link “Show Status” from related objects. 
  • Show status will show you the details about the installation status in monitoring workspace.

I would recommend following the below screenshot to see the real-time updates of the SCCM upgrade. Let’s monitor the installation Monitoring workspace:

  • Navigate to – \Monitoring\Overview\Updates and Servicing Status
Updates and Servicing Status - SCCM 2002 Installation Step by Step Guide
Updates and Servicing Status – SCCM 2002 Installation Step by Step Guide

Finish – SCCM 2002 Installation

The following sections have been successfully completed as part of the 2002 installation.

  • Download – Completed
  • Replication – Completed
  • Prerequisite Check – Completed with some warnings
  • Installation – Completed
  • Post Installation – Completed
Finish - SCCM 2002 Installation - SCCM 2002 Installation Step by Step Guide
Finish – SCCM 2002 Installation – SCCM 2002 Installation Step by Step Guide

Console Upgrade to 2002 Version

The last step of the ConfigMgr 2002 installation is by upgrading the console of Primary servers & CAS server.

You need to make sure all your remote SCCM console installations are upgraded to the latest version. This is not very critical if your remote SCCM console is already running with the n-1 version  (where n = 2002 in this scenario).

But, if your remote SCCM console is not n-1 then, you need to make sure your console is updated otherwise you won’t be able to connect to the SCCM console.

SCCM 2002 Version Numbers

Let’s see what are the Configuration Manager version numbers.

  • Site Server Full Version Number – 5.00.8968.1000
  • Site Server Version Number – 5.0.8968.1000
  • Console Version Number – 5.2002.1083.1700
  • Client Version Number – 5.00.8968.1008

Resource

Do Not Setup SUP with Default WSUS Product Selection ConfigMgr SCCM

Really need to setup SUP with default WSUS product selection (Default WSUS Product Selection)? The quick post to let you know the WSUS product list which is automatically selected underneath Windows and Products category for your ConfigMgr infrastructure.

Related Post – Install New ConfigMgr Software Update Role Setup Guide|SUP|SCCM

Introduction

I don’t think there is any cleanup done to remove the legacy products from the WSUS products list for many years. I could still see Server 2003 and Windows XP are part of the product list which are automatically selected by default.

Why do we need those? What you think? Let’s check out the default WSUS product selection (this is out of box experience).

Default WSUS Product Selection
List of Products

At first look, you will feel there are NO products selected! You are Wrong! When you expand, you could see there are many “LEGACY” office products and Windows versions are already selected by default.

I don’t know how many of you still need the following products. And moreover, the latest OS version Windows 10 is not selected by default 🙂

  • Office XP
  • Office 2003
  • Office 2007
  • Windows XP
  • Server 2003
Office - Windows Old version products -  Default WSUS Product Selection
Office – Windows Old version products

Best Options

My advice would be to remove all the default product selections and start from scratch.

If you are setting up a new ConfigMgr | WSUS, you just need Windows 10 and Server 2016 (optionally server 2012). What you say?

Windows 10 and Server 2016 - Default WSUS Product Selection
Windows 10 and Server 2016 – Default WSUS Product Selection

Let’s remove all the office versions except Office 365 Client during the initial setup SUP (Software Update Point) within your ConfigMgr|SCCM environment.

Office 365 - Default WSUS Product Selection
Office 365 – Default WSUS Product Selection

Best Option

  1. Validate the default or out of box selection of products.
  2. Remove all the legacy products from the WSUS product list while configuring SCCM SUP.
  3. Understand the Microsoft products which you want to patch.
  4. Select only the required products (#3) from the WSUS product list.

Resources

Use Existing SCCM Config to Help to Reduce VPN Bandwidth | ConfigMgr

Let’s learn how to use an existing SCCM configuration to help to cater to remote work scenarios. In this post, let’s understand the opportunity to improve end-user experience in Work from home scenarios.

I hope, this post helps to Learn and Use Existing SCCM Config to Help to reduce VPN Bandwidth.

Related Post Bits Throttling options for SCCM Distribution Point and SCCM Clients. & SCCM IBCM Vs CMG Differences a Real World Comparison

Updated on April 4th, 2020 -You can refer to the post from Rob York on 1.” Managing remote machines with cloud management gateway in Microsoft Endpoint Configuration Manager” 2. “Managing Patch Tuesday with Configuration Manager in a remote work world“.

Updated on April 5th, 2020 – Post from Jonas, Roland and Stefan. ✔ Mastering Configuration Manager Bandwidth limitations for VPN connected Clients

Introduction

We have modern options like cloud management gateway (CMG) & Cloud distribution points (CDP) to avoid traffic coming into the on-prem data center. Yes, also WUfB policies controlled by Microsoft Intune.

But the main question is “Are these options help to reduce the VPN bandwidth without slipt tunneling and appropriate proxy configurations.“?

Yes. If you have Configuration Manager infrastructure is cloud-enabled or cloud-attached with all modern features, then you are in good shape already.

Existing Path -  Credit to Microsoft - TechCommunity Pos
Existing Path – Credit to Microsoft – TechCommunity Post

NOTE! – CMG & CDP might not be efficient if you don’t have spilt tunneling enabled for those kinds of traffic.

Many organizations are not using cloud management gateway or cloud distribution points. In this scenario what are the best options to avoid SCCM using all VPN bandwidth two batch windows devices?

Let’s see whether we can use the existing SCCM Config to Help to reduce VPN Bandwidth. Mainly to cover critical scenarios like Software updates (patching).

NOTE! – This is critical because if all of your workforces forced to work from home in a scenario like COVID19 for several coming months.

Split Tunneling & Proxy

Split tunneling and proxy configurations are pretty much critical in these scenarios. Even if configure everything OK from SCCM and Intune.

NOTE – When there is no appropriate spilt tunneling and proxy configurations, then the SCCM|Intune configuration changes might not help at all.

More details available in the following Microsoft documentation to build exceptions for Microsoft related services.

SCCM CMG - Firewall Ports Proxy Requirements - SCCM Config to Help to reduce VPN Bandwidth
SCCM CMG – Firewall Ports Proxy Requirements – SCCM Config to Help to reduce VPN Bandwidth

Office 365 Communications

Even spilt tunneling and proxy configuration changes are applicable for Office 365 traffic as well. If you have a VPN and proxy are configured to route all the traffic via a VPN tunnel, then this is going to impact the entire VPN tunnel.

More Details – Microsoft Office 365 Network Team’s Take on Split Tunnelling – TechCommunity Post

This shall in term impact your entire business application echo system as well. The users are connecting through the VPN in a work from home scenario won’t be able to perform any work at all.

Credit to Microsoft Details about Split Tunnelling - TechCommunity Post
Credit to Microsoft Details about Split Tunnelling – TechCommunity Post

Network & Proxy Team

In this scenario, we should get in touch with our network team members to understand the possibility of enabling split tunneling for these kinds of cloud services. Probably, they can help us to implement split tunneling for the following Microsoft services which impact the workplace.

Network Proxy Team to help Workplace - SCCM Config to Help to reduce VPN Bandwidth
Network Proxy Team to help Workplace – SCCM Config to Help to reduce VPN Bandwidth
  • Office 365
  • Software updates (Patching)
  • CMG or CDP connectivity

NOTE! – This will help to reduce the VPN bandwidth usage and the critical business applications which need connectivity to on Prem so worse can work seamlessly in a remote working scenario like this.

SCCM Config to Help to Reduce VPN Bandwidth

Even if you don’t have CMG or CDP enabled for your SCM|ConfigMgr infrastructure, you can use the following option to keep your Windows 10 devices or Windows 7 devices secured.

Software update or patch deployment is a critical activity for all device management admins. SCCM can perform this activity without impacting critical business deliverables.

Let’s check the following option and test whether this is useful for you or not. This configuration as per Microsoft documentation helps to reduce VPN traffic.

Starting in version SCCM 1806, deploy software updates to devices without first downloading and distributing content to distribution points. This setting is beneficial when dealing with extremely large update content. More details – here.

Patch Windows 10 from Internet – SCCM Config to Help to reduce VPN Bandwidth

NO Deployment packageClients download contents from peers or the Microsoft cloud

Clients download contents from peers or the Microsoft cloud - SCCM Config to Help to reduce VPN Bandwidth
Clients download contents from peers or the Microsoft cloud – SCCM Config to Help to reduce VPN Bandwidth

While creating software updates packages in SCCM, there is a default option to download the content from the Internet instead of downloading the software update content from your on Prem distribution points. This SCCM Config to Help to reduce VPN Bandwidth.

TRY the following option – If software updates are not available on distribution point in current, neighbor or site boundary groups, download content from Microsoft Updates.

Select the following setting to have clients download software updates from Microsoft Update. The Internet-based clients always go to Microsoft Update for software updates content (if you have appropriate VPN spit tunneling and proxy configurations).

download content from Microsoft Updates - SCCM Config to Help to reduce VPN Bandwidth
Download content from Microsoft Updates – SCCM Config to Help to reduce VPN Bandwidth

Hopefully, this setting along with split tunneling might help you to reduce the VPN bandwidth usage from SCCM perspective.

Download Settings -  SCCM Config to Help to reduce VPN Bandwidth
Download Settings – SCCM Config to Help to reduce VPN Bandwidth

Boundary Group Options

Boundary group option – Prefer cloud based sources over on-prem sources is another useful option that you can think about.

If you have a branch office with a faster internet link, you can now prioritize cloud content. In ConfigMgr 1902, this setting is now titled Prefer cloud based sources over on-premise sources. Cloud based sources include the following – More details here.

Boundary Options – SCCM Config to Help to reduce VPN Bandwidth
  • Cloud distribution points
  • Microsoft Update (added in version 1902)
Prefer cloud based sources over on-prem sources  - SCCM Config to Help to reduce VPN Bandwidth
Prefer cloud based sources over on-prem sources – SCCM Config to Help to reduce VPN Bandwidth

BITs Throttling Options for SCCM DP MP SUP

I have posted about the BITs Throttling Options for SCCM DP, MP, and SUP over https://anoopcnair.com/vpn-bandwidth-control-via-bits-throttling-for-sccm-dp-client

Results

Let me know what you think about it how many of you are thinking to implement this kind of option.

Resources

Out of Band SCCM Hotfix Installation Guide | MECM

Let’s check the above video how to install Out of Band SCCM Hotfix. Let’s understand what is SCCM| ConfigMgr update registration tool.

Subscribe to Post via eMail

[jetpack_subscription_form show_only_email_and_button=”true” custom_background_button_color=”undefined” custom_text_button_color=”undefined” submit_button_text=”Subscribe” submit_button_classes=”undefined” show_subscribers_total=”false” ]

Introduction

SCCM out of band hotfix updates for SCCM are not available from the Microsoft cloud service. One example of out of band hotfix of SCCM 1910 version is KB 4538166. You need to get these type of updates by manually downloading it.

NOTE! – An out-of-band release hotfix file name ends with the extension update.exe. The example is “CM1910-KB4538166.ConfigMgr.Update.exe.”

Update Registration Tool

You use a tool called the “update registration tool” to manually import the update to the ConfigMgr console. This tool enables you to extract and transfer the update package to the stand alone primary or CAS site server, and register the update with the SCCM console.

NOTE! – When update has a file name that ends with the extension .exe (NOT update.exe), then you need to use you use the hotfix installer that is included with that hotfix download to install the update directly to the SCCM site server.

 SCCM | CofnigMgr Update Registration Tool  Out of Band SCCM Hotfix
SCCM | ConfigMgr Update Registration Tool (Out of Band SCCM Hotfix)

Prerequisites

You need to make sure the tool’s (SCCM | ConfigMgr Update Registration Tool) prerequisites.

  • Service connection point can be ONLINE or OFFLINE
  • Run Update Registration Tool from the server where the service connection point role is installed
  • The computer where the tool runs (the service connection point computer) must have the .NET Framework 4.52 installed
  • The account you use to run the tool must have local administrator permissions
  • Your account must have write permissions to the following folder on the computer that hosts the service connection point: \EasySetupPayload\offline

Installation

I have already explained the installation process which you shall follow to install out of band SCCM hotfix.

Resources

Reinstall Management Point Role|ConfigMgr

In this blog post, You are going to see the videos to remove Management point and install it. So basically this process is called re-installation of SCCM Management point role (Reinstall Management Point Role).

Impacts – Reinstall Management Point

You need to make sure that you are aware of all the impacts before you remove the Management point from your SCCM|ConfigMgr infrastructure.

Basically Management points provide policies and content location to clients. If you don’t have a Management point your SCCM client is useless or not managed at all.

The above scenario could cause many client management issues as well as bandwidth issues if the clients fall back to remote Management Point.

Before removing the ConfigMgr Management point, you need to make sure that you are NOT going to cause bandwidth or network issues for your businesses.

You can stop all the deployments or you should not deploy any new applications or policies (policies are fine) to those remote office clients to eliminate the network impacts.

NOTE! – You can reduce the impact of re-installation of SCCM MP by making an other management point available in the same remote office or not.

Reinstall Management Point - Remove and Install Management Point
Reinstall Management Point – Remove and Install Management Point

Remove Management Point

Once you are able to confirm you are fine with all these impacts, you can proceed with the following actions.

The removal of management point is straightforward process. You can refer to the video above to get more details on the removal process. You can complete re installation “Reinstall Management Point” process using this guide.

My recommendation would be to validate the removal of management points (MP) from the log files. Also, you can validate all the other components like IIS. This process will help you to have a clean reinstall or removal of management point.

More details – Learn How to Remove Management Point Role|SCCM|ConfigMgr.

Reinstall Management Point

Once you are OK with the removal of Management point, you can give a restart it’s not mandatory to restart the server but you can restart the server before installing the Management point again (or re-installing the MP).

Now you can install the management point (Reinstall Management Point) from SCCM console.

How to perform re-installation of MP is explained in the video above. After the installation, from the log files as you can see in the below post you can verify MP is working fine.

More details – Learn How to Install a New Management Point Role|SCCM|ConfigMgr

Resources

How to Reinstall Distribution Point Role|ConfigMgr

In this blog post, You are going to see the videos to remove distribution point and install it. So basically this process is called re-installation of SCCM distribution point role (Reinstall Distribution Point Role).

Impacts – Reinstall Distribution Point

You need to make sure that you are aware of all the impacts before you remove the distribution point from your SCCM|ConfigMgr infrastructure.

Basically distribution points provide source files to clients. If you don’t have a distribution point and if you are not using any peer to peer caching mechanism, probably your client will go over van connection and download the source files of your applications from the remote distribution point.

The above scenario could cause many network related issues if you have bandwidth concerns or if you are on a low bandwidth connected remote office.

Before removing the ConfigMgr distribution point , you need to make sure that you are NOT going to cause bandwidth or network issues for your businesses.

You can stop all the deployments or you should not deploy any new applications or policies (policies are fine) to those remote office clients to eliminate the network impacts.

NOTE! – While removing the distribution point all the packages distributed do that DP will get removed or the source files in the DP will get deleted. So make sure to DP group, otherwise you need to distribute all the packages manually or using some automation after reinstalling the distribution point.   

You can reduce the impact of re-installation of SCCM DP by making an other distribution points available in the same remote office or not.

Reinstall Distribution Point SCCM ConfigMgr
Reinstall Distribution Point

Removal of SCCM DP

Once you are able to confirm you are fine with all these impacts, you can proceed with the following actions.

The removal of distribution point is straightforward process. You can refer to the video above to get more details on the removal process. You can complete re installation “Reinstall Distribution Point” process using this guide.

My recommendation would be to validate the removal of distribution points (DP) from the log files. Also, you can validate all the other components like IIS. This process will help you to have a clean reinstall or removal of distribution point.

More details – Learn How to Remove Distribution Point Role|SCCM|ConfigMgr.

Reinstall ConfigMgr Distribution Point Role

Once you are OK with the removal of distribution point, you can give a restart it’s not mandatory to restart the server but you can restart the server before installing the distribution point again (or re-installing the DP).

Now you can install the distribution point (Reinstall Distribution Point) from SCCM console.

How to do that that is explained in the video above. After the installation, there are two default packages which will automatically get distributed to the newly installed DP. From the log files as you can see in the below post and in the above video you can verify DP is working fine.

More details – Learn How to Install a New Distribution Point Role|SCCM|ConfigMgr

Resources

         

SCCM Task Sequence Check Readiness Options Before Windows 10 Upgrade

SCCM Task Sequence Check Readiness Options Before Windows 10 Upgrade ConfigMgr | Endpoint Manager. Microsoft MEMCM team introduced new read-only variables to the Task Sequence in this version 2001.

Introduction

Let’s see more details about Task Sequence Check Readiness with Windows 10 upgrade. Configuration Manager 2001 Task Sequence has out of box checks to confirm the existing device configuration before Windows 10 upgrade.

The readiness check is the built-in options availability in SCCM Task Sequence with Windows 10 upgrade options.

More Details – https://www.anoopcnair.com/configuration-manager-2001-technical-preview/

Task Sequence Check Readiness

The step also now sets read-only variables for whether the check returned true (1) or false (0). If you don’t enable a check, the value of the corresponding read-only variable is blank.

  • _TS_CRMEMORY
  • _TS_CRSPEED
  • _TS_CRDISK
  • _TS_CROSTYPE
  • _TS_CRARCH
  • _TS_CRMINOSVER
  • _TS_CRMAXOSVER
  • _TS_CRCLIENTMINVER
  • _TS_CROSLANGUAGE
  • _TS_CRACPOWER
  • _TS_CRNETWORK
  • _TS_CRWIRED

The smsts.log includes the outcome of all checks. If one check fails, the task sequence engine continues to evaluate the other checks. The step doesn’t fail until all checks are complete.

If at least one check fails, the step fails, and it returns error code 4316. This error code translates to “The resource required for this operation does not exist.”

The following are the new options available in the Task Sequence

  • Architecture of current OS: 32 Vs 64
  • Minimum OS version: for example, 10.0.16299
  • Maximum OS version: for example, 10.0.18356
  • Minimum client version: for example, 5.00.08913.1005
  • Language of current OS: select the language name, the step compares the associated language code. This check compares the language that you select to the OSLanguage property of the Win32_OperatingSystem class on the client.
  • AC power plugged in
  • Network adapter connected
    • Network adapter is not wireless
Configuration Manager 2001 Technical Preview Version 1 Task Sequence Check Readiness
Task Sequence Check Readiness

Resources

What’s New in ConfigMgr Orchestration Group|SCCM

Let’s see what are the improvements Microsoft included in the latest version of Orchestration MEMCM|SCCM 2001 Technical Preview. I have a previous post which talks about SCCM Orchestration Group Setup Step by Step Guide for Server Patching.

What is Orchestration Groups

The Orchestration groups are the advanced version of server groups in ConfigMgr. Do you know server groups? How to Patch the cluster servers and exchange servers domain controllers etc..

Orchestration Groups
ConfigMgr Orchestration Groups

Step by Step Guide Orchestration

I have explained step by step guide in the previous post – https://www.anoopcnair.com/sccm-orchestration-group-setup-guide/

Improvements in Orchestration

The following are the improvements or orchestration group of Configuration Manager. https://docs.microsoft.com/en-us/configmgr/core/get-started/2020/technical-preview-2001#bkmk_orch

Video Orchestration – Tutorial to explain in the above link.

  • You can now specify custom timeout values for:
    • The Orchestration Group
      • Time limit for all group members to complete update installation
    • Orchestration Group members
      • Time limit for a single device in the group to complete the update installation
  • When selecting group members, you now have a drop-down list to select the site code.
  • When selecting resources for the group, only valid clients are shown. Checks are made to verify the site code, that the client is installed, and that resources aren’t duplicated.
  • You can now set values for the following items in the Create Orchestration Group Wizard:
    • Number of machines to be updated at the same time in the Rules Selection page
    • Script timeout in the PreScript page
    • Script timeout in the PostScript page

Video Technical Preview 2001

More details about in the below 2001 preview version of Configuration Manager – Configuration Manager 2001 Technical Preview Version.

Resources

MECM SCCM 1910 Update Step by Step Guide

MECM is the new name of SCCM. In this post, you will see how to upgrade the SCCM infra to 1910 version. Let’s see SCCM 1910 Update Step by Step details.

Related Post What is New in MECM SCCM 1910 Features a Walkthrough

MECM 1910 Released
MECM 1910 Released Microsoft Docs here

How to Download SCCM 1910?

Don’t you see the SCCM 1910 production version in your console? How did I get the SCCM 1910 production version? There is no secret here.

Steps to Follow

  • You can download the PowerShell Script from Microsoft ( these instructions on how to use the PowerShell script  )
  • Run the Script with the account which has Full Admin access
  • Make sure you have successfully run the script
  • SCCM 1910 is Generally Available
  • Open the SCCM console and click Check updates as you can see in the below screenshot
MECM 1910 Released
MECM 1910 Released

Check out Microsoft’s Announcement about the 1910 release. MECM 1910 Fast Ring (opt-in version) now. This version of MECM is not generally available for all applicable SCCM Infra.

MECM 1910 Applicability Checks

With each version of SCCM, there will be an SQL applicability script that will check whether this particular update 1910 should be made available or not.

I have a blog post about this applicability script and the logic of the SQL script in detail. More details “SCCM Update is Not Visible in Console – Here is the Reason.”

SCCM 1910 Applicability Check - SCCM 1910 Update
SCCM 1910 Applicability Check – SCCM 1910 Update

Prerequisites of 1910 Version

As I mentioned above, the MECM 1910 production version will be available within the SCCM console after you run the PowerShell command and your SCCM site meet the following conditions:

  1. If your MECM CB version is SCCM 1810 or SCCM 1902, or SCCM 1906 (Read More details about SCCM Life Cycle)
  2. If your MECM CB version has online Service Connection Point

NOTE! – Make sure you have gone through best practice check list before starting the upgrade.

More Detailshttps://docs.microsoft.com/en-us/configmgr/core/servers/manage/checklist-for-installing-update-1910

Update Download Stuck?

This stuck download issue is a common scenario in enterprise organizations and LAB environments. This issue is mostly because of proxy or some other internet-related issues.

There are a couple of ways to fix this kind of issue if it’s not related to proxy and internet. You can refer to the previous blog posts to solve Update Download stuck problems.

More troubleshooting help on SCCM 1910 Download stuck and upgrade issues here and here.

FIX SCCM Updates Stuck in Downloading State & CM Update Reset Tool Fixes SCCM CB Update Download Issue

Microsoft Doc ➡ https://support.microsoft.com/en-us/help/4490424/understand-and-troubleshoot-updates-and-servicing-in-configmgr

Log Files are Your Friend

  • DMPDownloader.log for SCCM 1910 source file download issues
  • ConfigMgrSetup.log for Redist Files Download Issue
  • CMUpdate.log for all the upgrade related activities

SCCM Update Prerequisite Check Stuck?

The SCCM upgrade prerequisite check can take many hours, depending on your hierarchy/infra. When you have CAS and many primary servers, the 1910 update source files will be copied to primary servers.

You can check the status of the prerequisite checks from the monitoring node. More details about SCCM prerequisite checks here.

Microsoft Documentation – https://docs.microsoft.com/en-us/configmgr/core/servers/deploy/install/prerequisite-checker

NOTE! – Make sure you start the prerequisite checks 3-4 days before the production update/upgrade of SCCM infra.

SCCM CB Prerequisite Checks - SCCM 1910 Prerequisites - SCCM 1910 Update
SCCM 1910 Prerequisites – SCCM 1910 Update

Install Update Pack

Once the prerequisite checks completed successfully, you can start the installation or update of MECM 1910.

  • Select Configuration Manager 1910 update
  • Click on Install Update Pack to start the installation wizard
Install Update Pack
Install Update Pack
  • Features Included in Update Pack
  • Select the features you want to enable after the upgrades
    • Bitlocker Management
  • Click on Next to continue
 Bitlocker Management SCCM 1910 Update
Bitlocker Management – SCCM 1910 Update
  • Client Update Settings
    • Upgrade without validating
    • Validate in pre production collection
  • Click NEXT button to continue
SCCM 1902 Client Upgrade Options Promote Pre-Production Client - SCCM 1910 Update
Direct Production Client Package Update – SCCM 1910 Update

NOTE! – More details about SCCM Client Upgrade options “SCCM Client Upgrade Promote Pre-Production Client to Production.”

1910 Update Completed Successfully

The installation or update process might take more than a couple of hours, depending on the size of the database and performance, etc..

1910 version update completed
1910 version update completed

Upgrade SCCM Remote Console

The 1910 update process completes the installation of the latest version of the console. The console installation on the site servers (primary and CAS) are straight forward.

More details about the remote console installations/updates are explained in the following post. More information, “Install SCCM Remote Console on a Windows 10 Machine.”

  • Version 1910
  • Console Version 5.1910.1067.1300
  • Site Version 5.0.8913.1000
Endpoint Configuration Manager v1910
Endpoint Configuration Manager v1910

Client and Server Version

Let’s check the client and server versions of 1910.

  • Version 1910
  • Full Version 5.00.8913.1000
  • Client Version 5.00.8913.1006
1910 Full Version Client Version
1910 Full Version Client Version

Pre-Released Features

Following are the pre-release features of 1910 version!

Pre-Released Features - SCCM 1910 Update
Pre-Released Features – SCCM 1910 Update

New Features of 1910

I have explained all the new features in the following blog post. More details “What is New in MECM SCCM 1910 Features a Walkthrough.”

Resources – SCCM 1910 Update