Skip to main content

Update SCCM Console to 1806

To be compliant and allow Windows 10 Branching Updates to 1803, the SCCM console needs to be updated to the latest version, which is 1806. This is available as an in console update, providing that you are currently on one of the Current Branch Console Versions.

To see the support tree see the following link from Microsoft - https://docs.microsoft.com/en-us/sccm/core/plan-design/configs/support-for-windows-10

The current support timeline is as below

Windows 10 versionConfiguration Manager 1706Configuration Manager 1710Configuration Manager 1802Configuration Manager 1806
Enterprise 2015 LTSBSupportedSupportedSupportedSupported
Enterprise 2016 LTSBSupportedSupportedSupportedSupported
1607
(see editions)
Supported 1Supported 1Supported 1Supported 1
1703
(see editions)
SupportedSupportedSupportedSupported
1709
(see editions)
Backwards compatibleSupportedSupportedSupported
1803
(see editions)
Not supportedNot supportedSupportedSupported

The first step in doing this is to update to ADK. If you do not do this prior then you will need to do this after the console update, which is a lot longer process. For details on how to do this then follow this guide from System Centre Dudes - https://www.systemcenterdudes.com/how-to-update-windows-adk-on-a-sccm-server/

1.) First of all you need to download the latest Windows 10 ADK from Microsoft here - https://docs.microsoft.com/en-us/windows-hardware/get-started/adk-install

2.) Remove the current installation of you ADK on your SCCM Server, which will require a reboot afterwards

3.) Run the ADK installer which was downloaded in step 1 above. Once you run the installer it is best to choose the second option which is to download the Windows Assessment and Deployment Kit - Windows 10 for installation on a separate computer. This will take a fair bit of time as the full installer is several GB in size.

4.) The next step is to install the ADK on your SCCM server. Launch the adksetup.exe file in the directory where you saved the install to in step 3 above.



5.) The next few steps are pretty straight forward, just hit accept on the licencing agreement and no for the Microsoft reporting. After this you then need to select which features you want to install with the ADK. For me I only saw value in choosing the below options.


6.) This will take a while to install, once it is done go to Programs and Features and check to make sure the version has updated to 10.1.17134.1.



7.) You will now be ready to install the latest SCCM version. I prefer to run a Prerequisite check first from within the console. You do this by doing to Administration > Updates and Servicing and then selecting the most recent update and choose "Run Prerequisite Check"



8.) You can check the status of the Prerequisite check, which should take about 10 - 15 minutes to complete. If there are any errors it is best checking the log file which is located in c:\ConfigMgrPrereq.log. When I first ran this I had 2 issues, one being I didn't have enough disk space for the install (minimum 15GB required) and one of my site servers which were running the Fallback Role was still running Server 2008. I had to do an OS in place to fix this issue and expand the disk space of the C drive to allow the install to complete.

9.) The next step is to do the actual update. On the same Updates and Servicing screen choose the update which you just ran the Prerequisite check on and choose "Install Update Pack"



10.) To view the progress of the update go to Monitoring > Update and Servicing Status > Choose your update and then select Show status. This will bring up a monitoring screen where you can click refresh at the top to keep an eye on the update. When I did it the update took around 30 minutes to complete. Once it is done you should have all steps marked as completed.

11.) I also faced a problem where my Boot Images did not update automatically to the same version as the ADK. To fix this up I had to select the boot image and then choose Update Distribution Points with Boot Image. In here it gave me the  option to Reload the boot image to the latest version - 10.0.17134.0.



Comments

Popular posts from this blog

SCCM - Required Application Not Installing to a collection based on an Active Directory Security Group I recently had an issue where I was trying to install Office 2013 as a required application to a collection based on an AD Security group. This would work fine if I was advertising the install as  'available', however when I set as 'required' it would not install and not even show up in Software Centre. After looking through the Monitoring section in SCCM and had a look at the deployment status I noticed it said success however the Message ID was 10040 and the description was "program will not rerun" I managed to fix this by going to the deployment settings for this collection and then going to scheduling and altering the "Rerun behaviour" to always rerun program.

Office 2013 Silent Install

Office 2013 Silent Install Setup To setup a silent install of Office 2013 follow the below steps. If you have an ISO mount the file and then copy all the files out to a folder.  Run the command \\locationoffolder\setup.exe /admin. This will bring up the Office 2013 customisation tool.  You can apply which settings you require. The main ones you probably need to apply are  Licensing and user interface - choose here if you want to use a KMS key or a MAK key. In the options for the licencing agreements it is best to Tick "I accept the terms of the license agreement" Display level - none Suppress modal - ticked Set feature installation states. Tick the appropriate install options and features which you want. Configure shortcuts. I came across an issue in here which appears to be a known bug. If you try to create desktop shortcuts for any of the applications it would try to force you to enter something in the "start in" field saying this is required. ...

SCCM Task Sequence Fails on SSD Drives Error Error: 87D00267

If you get the error code  87D00267 in a task sequence when deploying an Operating System it  basically means the machine is unable to talk to the DHCP server. From a bit of investigation it  seems that some machines with SSD's actually boot up into the task sequence quicker than it  gets an IP Address! The get around this problem you need to put some pauses in the task  sequence.  The best way is to put the pause in the task sequence just before the point where it  fails. There is  some further reading into this issue below, the sites credited with links.  Part 1 Source: http://ericsccm2012.blogspot.com.au/2013/04/applications-fail-to-install-on-ssd.html Applications Fail to Install on SSD Drives. We received several of the new Dell Latitude 6430U models with SSD drives.  Very nice laptops in a small case.  Easily found drivers for them and loaded into SCCM.  Started the task sequence on one and all look...