Saturday, July 27, 2019

SCCM 1906 Step by Step Upgrade Guide

Today (27/07/2019) Microsoft has released new branch update (1906) for System Center Configuration Manager.

Read release announcement  and list of new features on Microsoft Enterprise Mobility + security blog 

 Before proceeding with SCCM branch upgrade, it is very important to review SCCM Current Branch 1906 servicing readiness as below;
- SCCM CB 1906 can be upgraded only from 1806, 1810 or 1902
- Minimum of .Net 4.5 must be installed and complete the reboot
- ADK version must be 1903
- Change SQL AlwaysOn to manual failover
- File replication and Data replication is current when having multi site hierarchy
- Disable backup, delete aged client operations and delete aged discovery data site maintenance tasks
- Make sure full site backup is available before the upgrade

This step by step SCCM 1906 upgrade guide will guide you through from any supported previous version to SCCM Configuration Manager 1906

Downloading the SCCM CB 1906 update:
If SCCM CB 1906 update is not available (if you are not in first wave of customers) in SCCM console and you want to install without waiting until the global release then you need to download Version 1906 opt-in script  then run on the site server.

Download the Version 1906 opt-in powershell script from https://docs.microsoft.com/en-us/sccm/core/servers/manage/checklist-for-installing-update-1906#early-update-ring

1. Run EnableEarlyUpdateRing1906.exe as Administrator and extract the content to a nominated folder


2. The .exe will extra enableearlyupdatering1906.ps1 file

3.  Launch PowerShell as Administrator, then Change the current directory to the enableearlyupdatering1906.ps1 script path.
Then run the script from elevated PowerShell window (ex: enableearlyupdatering1906.ps1 SCCB )
         Note: Just use server name without FQDN.

4. The command will be completed successfully

5.  Go to \Administration\Overview\Updates and Servicing node in SCCM console then click Check for updates on the ribbon;

 6. Review the dmpdownloader.log file
            The log should have - Found a new available update

Then downloading large file with bits;

7. Refresh the Updates and servicing node in SCCM console, you can see the 1906 update in
    downloading state.

8. Wait until the 1906 update status changes from Downloading to Ready to Install

Installing SCCM CB 1906 update:
 1. Like any other previous updates, first run the Run Prerequisite check or run the Install update Pack directly;

2. The installer will start the Configuration Manager Updates wizard. Click Next on the General tab;

 3.  Select required features to be installed then click Next;

 4.  Select required client update options then click Next;

5. Accept the license terms then click Next;

 6. Review and confirm the selected options then click Next;

7. Close the completion window.

8. Now the 1906 update state will change from Available to Installing;

9. The installation will start checking prerequisites;

10. Detailed progress of the update installation can be viewed from \Monitoring\Overview\Updates 
and Servicing Status\Configuration Manager 1906 node From the ribbon click on Show status.

The update status also can be checked by reviewing hman.log

11. It will take 20-30 min (based on the server performance) to complete the upgrade. 
Once the update is installed, Configuration Manager 1906 update status will be changed from Available to Installed.

Console Upgrade:
After upgrading the site server to SCCM Current Branch 1906, If we re-launch or check the console version, we will get a popup message saying A new version of the console is available( 5.1906.1096.1500).

On the upgrade prompt, Click OK to upgrade the console and follow the-on screen prompts to complete the upgrade process.

Once the update is installed the version number of SCCM will be;
          System Center Configuration Manager Version: 1906
          Console Version: 5.1906.1096.1500
          Site Version: 5.0.8853.1000

Saturday, June 22, 2019

Failed to create temporary file CMTrace loader

Recently on my primary site server (Server 2019) in the lab CMTrace stopped working by throwing Failed to create temporary file.
However, When I launched the CMTrace.exe as Administrator it opened without any errors.

To investigate further, when I opened %Temp% from Run box, it didn't opened correctly instead got below error. 

So it lead me to believe that, my RDP session to the server using Temp\1 as my temp location.
I do not want to use alternate temp location when I use RDP session.

To overcome this issue set local group policy on the server to not to use temporary folders per session.
To do this; Go to Computer Configuration\Windows Components\Remote Desktop Services\Remote Desktop Session Host\temporary folders then enable Do not use temporary folders per session.


By default Do not use temporary folders per session policy is not configured.

Now when launched %Temp% from run box, Windows explorer opened the correct temp folder.

Tuesday, May 28, 2019

Step by Step SCCM 1902 Upgrade Guide

Microsoft has released new branch update (1902) for System Center Configuration Manager.

ConfigMgr Current Branch 1902 provides enhanced features like client health dashboard, enhanced HTTP, SQL pending restart check as setup prerequisite, improvements to cloud services, improvements to real time management, Distribution point maintenance mode, added features to client management, improvements to OSD, improvements to Software center, new features to SCCM console etc..
For complete list of features visit Enterprise Mobility and Security blog.

Before proceeding with SCCM branch upgrade, it is very important to review SCCM Current Branch servicing (upgrade) checklist

This step by step SCCM 1902 upgrade guide will guide you through  upgrading SCCM Current branch from all supported previous versions to SCCM Current Branch 1902.

Downloading the update:
1. Go to \Administration\Overview\Updates and Servicing node in SCCM console then click Check for updates on the ribbon;

2. Review the dmpdownloader.log file

3. Refresh the Updates and servicing node in SCCM console, you can see the 1902 update in
      downloading state.
 The dmpdownloader.log on the site server will show package download status

4. Wait until the 1902 update status changes from Downloading to Ready to Install in the console
If you are installing the update after Microsoft released the update as an in-console update, then it will be already in Ready to Install state.

Installing SCCM CB 1902 update:
1. Like any other previous updates, first run the Run Prerequisite check or run the Install update Pack directly;

2. The status will change from Ready to Install to Checking prerequisites

3. Once the prerequisite check is completed, Right click on the update pack (Configuration Manager 1902) then select Install Update Pack;

4. The installer will start the Configuration Manager Updates wizard. Click Next on the General tab;

5. Select required features to be installed then click Next;

6. Select required client update options then click Next;

7. Accept the license terms then click Next;

8. Review and confirm the selected options then click Next;

9. Close the completion window;

10. Now the 1902 update state will change from Ready to Install to Installing;
 
11. We can view the detailed progress of the update installation from \Monitoring\Overview\Updates
    and Servicing Status\Configuration Manager 1902 node From the ribbon click on Show status.

The update status also can be checked by reviewing hman.log

12. Once the update is installed, Configuration Manager 1902 update status will be changed from Available to Installed.

Console Upgrade:
1. After upgrading the site server to SCCM Current Branch 1902, If we re-launch or check the console version, we will get a popup message saying A new version of the console is available (5.1902.1085.1700).

2. When prompted, Click OK to upgrade the console and follow on screen prompts to complete the upgrade process.

3. The installation of the new console will automatically start and will complete without any input.

4. Once the update is installed the version number of SCCM will be;
          System Center Configuration Manager Version: 1902
          Console Version: 5.1902.1085.1700
          Site Version: 5.0.8790.1000

Saturday, April 20, 2019

Check for updates greyed out sccm

Suddenly you may have noticed that Check for Updates under \Administration\Overview\Updates and Servicing greyed out in your SCCM environment;


Also, Synchronize Software updates tab missing under \Software Library\Overview\Software Updates\All Software Updates


Also, Latest Configuration Manager update pack is available in the console with status Ready to Install, but all the options are greyed out when right click on the update pack under \Administration\Overview\Updates and Servicing;

If we review the event viewer, we will notice Event ID 1, Critical error as below;
The evaluation version of System Center Configuration Manager that is installed on this computer has expired. To purchase a licensed version of Configuration Manager, contact your reseller. For more information about how to upgrade from the evaluation version to the licensed version, see the TechNet documentation library.

Now, Look at the ribbon on the top of the console, it will be clearly marked as the Evaluation is Expired.

To fix above all, enter the product key or if it is lab like mine, then re-install a new instance of Configuration Manager.

Monday, December 31, 2018

Step-by-Step SCCM 1810 Upgrade Guide

Few days ago, Microsoft has released new branch update (1810) for System Center Configuration Manager.
ConfigMgr Current Branch 1810 update is available as in-close update, which can be updated from all supported Current branch versions (1702, 1802 and 1806)

For complete list of features read whats new in 1810

Before proceeding with SCCM branch upgrade, it is very important to review SCCM Current Branch servicing (upgrade) checklist

 This step by step SCCM 1810 upgrade guide will guide you through  upgrading SCCM Current branch from all supported previous versions to SCCM Current Branch 1810.

Downloading the SCCM CB 1810 update:
 1. Use FastRingScript_1810.exe to upgrade the site to 1810 without waiting for global release.
 2. Download FastRingScript_1810.exe from TechNet gallery
 3. Extract the downloaded FastRingScript_1810.exe
 4. Launch PowerShell as Administrator
 5. Change the current directory to the FastRingScript_1810 script path
 6. Run the script from elevated PowerShell window (ex: EnableFastUpdateRing1810.ps1 SCCB )
       Note: Just use server name without FQDN

 7. You will get the command(s) completed successfully

 8. Now go to \Administration\Overview\Updates and Servicing node in SCCM console then click           Check for updates on the ribbon.

 9. Refresh the Updates and servicing node in SCCM console, you can see the 1810 update in
       downloading state.

10. Review the dmpdownloader.log file
     The log should have - Found a new available update then downloading large files with BITS;

 11. Wait until the 1810 update status changes from Downloading to Ready to Install in the console

Installing SCCM CB 1810 update:
1. Like any other previous updates, first run the Run Prerequisite check or run the Install update Pack directly;

 2. The installer will start the Configuration Manager Updates wizard. Click Next on the General tab;

3.  Select required features to be installed then click Next;

4.  Select required client update options then click Next;
5. Accept the license terms then click Next;


6. Review and confirm the selected options then click Next;

7. Close the completion window;

8. Now the 1810 update state will change from Available to Installing;

9. The detailed progress of the update installation can be viewed from \Monitoring\Overview\Updates and Servicing Status\Configuration Manager 1810 node From the ribbon click on Show status.
The show status will provide detailed progress of the upgrade process.
The update status also can be checked by reviewing hman.log
It will take 20-30 min (based on the server performance) to complete the upgrade.

Console Upgrade:
After upgrading the site server to SCCM Current Branch 1810, If we re-launch or check the console version, we will get a popup message saying A new version of the console is available (5.1810.1075.1400).

When prompted, Click OK to upgrade the console and follow on screen prompts to complete the upgrade process.


Once the update is installed the version number of SCCM will be;
           System Center Configuration Manager Version: 1810
           Console Version: 5.1810.1075.1400
           Site Version: 5.0.8740.1000