Friday, March 23, 2018

Step by Step SCCM 1802 Upgrade Guide

Today (23/03/2018) Microsoft has released new branch update (1802) for System Center Configuration Manager.

Read release announcement  and list of new features on Microsoft Enterprise Mobility + security blog
The much anticipated primary site HA is not included in this release.

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

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

Downloading the SCCM CB 1802 update:
If SCCM CB 1802 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 FastRingScript_1802.exe then run on the site server.

1. Click on "Check for Updates" from \Administration\Overview\Updates and 
    Servicing node

2. If update is not available, then get FastRingScript_1802.exe from TechNet gallery
3. Extract the downloaded  FastRingScript_1802.exe
4. Launch PowerShell as Administrator
5. Change the current directory to the FastRingScript_1802 script path
6.  Run the script from elevated PowerShell window (ex: EnableFastUpdateRing1802.ps1 SCCB )
         Note: Just use server name without FQDN.

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

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

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

Then downloading large file with bits;

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

11. Wait until the 1802 update status changes from Downloading to Ready to Install.

Installing SCCM CB 1802 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 1802 update state will change from Available to Installing;

9. We can view the detailed progress of the update installation from \Monitoring\Overview\Updates 
      and Servicing Status\Configuration Manager 1802 node From the ribbon click on Show status.
The update status also can be checked by reviewing hman.log
10. It will take 20-30 min (based on the server performance) to complete the upgrade. 
Once the update is installed, Configuration Manager 1702 update status will be changed from Available to Installed.

Console Upgrade:
After upgrading the site server to SCCM Current Branch 1802, 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.1802.1802.1700).

When prompted, 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: 1802
         Console Version: 5.1802.1802.1700
         Site Version: 5.0.8634.1000

Click here for complete SCCM Current Branch step by step guides, step by step migration guide, step by step monitoring and health check guide and step by step SCCM Current Branch servicing guide.

Monday, February 26, 2018

SCCM Always On Groups on SQL 2016 Standard or SQL 2017 Standard

When you are planning to configure SQL Always on for SCCM, make sure you will use SQL enterprise edition instead of STD.
SQL 2016 and SQL 2017 standard editions offer's only basic Always On Availability Groups, unlike Always On Availability Groups.

Basic Availability Groups has various limitations and one of them is no read access on secondary replica. For ConfigMgr it is required to have read access on all the replicas. Because of this limitation SQL 2016 standard or SQL 2017 Standard editions wont support ConfigMgr always on availability groups.

For further details refer to Microsoft Basic Availability Groups

Sunday, February 11, 2018

Feature Updates Vs Quality Updates Vs Non-deferrable Updates

A good feature comparison table of various types of windows updates Feature Updates Vs Quality Updates Vs Non-deferrable Updates;

Saturday, December 16, 2017

The specified domain either does not exist or could not be contacted. (Error: 8007054B; Source: Windows)

When you are deploying an Operating System using SCCM OSD, you may receive below error on Join domain step;
Failed to run the action: Join Domain or Workgroup. 
The specified domain either does not exist or could not be contacted. (Error: 8007054B; Source: Windows)

To identify the cause, first verify the network connectivity to the domain. If your test device has a valid IP and can reach the domain then it is not an issue with connectivity or network drivers.

On the test device review the SMSts.log (C:\Windows\CCM\Logs\SMSTSLog\smsts.log - I have join domain step after OS setup).

On my test device, I have noticed following entries when the device failed to join the device;
Joining domain W2016.LAB and OU CN=Computers,DC=W2016,DC=LAB (this is based on the task sequence setting)

Attempting to join and create account with OU - As that OU doesn’t exist where we want to create the computer account, hence the result is 0x0000054b

Then the task sequence will fail with;
Failed to join domain. The account may not have permission
The specified domain either does not exist or could not be contacted. (Error: 8007054B; Source: Windows)

If we go back to the task sequence and review the domain join step, I have incorrect setting.

 To resolve the issue, If you want to create the computer account in default computer container then leave the Organisation Unit field empty in Join Domain step as below;

If you have a separate then enter/browse to that OU.

Friday, December 8, 2017

Configuration Manager 1710 available globally

Three weeks ago ConfigMgr 1710 was released for fast ring devices only.
Now for the slow ring devices the wait is over. Today (8th December 2017) Microsoft has released ConfigMgr 1710 servicing update to all the global devices.

To see the update, go to \Administration\Overview\Updates and Servicing in your console and you would be able to see Configuration Manager 1710 in Ready to Install state.

If Configuration Manager 1710 is not present under \Administration\Overview\Updates and Servicing then run Check for updates manually and monitor dmpuploader.log

Happy servicing... :)