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;


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... :)

Saturday, November 25, 2017

Expand SCCM CB Primary site with CAS

If you are planning to expand SCCM Current branch site with CAS, it is not a simple running Setup.exe from install media. If you try to install using setup.exe from newly downloaded ISO, the install will fail with multiple different error MSG’s.
This short Expand SCCM CB Primary site with CAS article will explain how to add a CAS to existing primary SCCM site;

Prepare the environment to install CAS;
- If you have installed service connection point role on Primary site, then remove this from primary
- Give NT SYSTEM account to sa permissions on existing DB
- Make sure the listener of SQL Always On Availability Group for primary site server (if using SQL     always on) is pingable from all the servers

Installing CAS;
- Copy the CD.latest folder from existing primary to the CAS
- Install CAS select option to add existing site server to this hierarchy
- Use standalone SQL at this stage
- Once the installation completed, wait for the replication to be completed
- Configure SQL Always On for CAS then move the CAS to Always On Availability Group

At this stage PRI and CAS will be Always On Availability Group.

Wednesday, October 18, 2017

Windows 10 1709 (Fall Creators Update)

Hey Guy's
Today Microsoft has released Windows 10 1709 (Fall Creators Update) worldwide. Soon the update will appear in our consoles and in VL center.
If you have synced your WSUS this morning then you can see 1709 feature update in your console.

If you are downloading ISO, then it is different than previous versions of windows 10 ISO's. With 1709 release, Windows 10 Pro (volume licensing version), Windows 10 Enterprise, and Windows 10 Education, all three will be bundled together. So when you use the media with your task sequence make sure to use the correct index number. Otherwise you will end up with incorrect type of Windows 10 Edition.

Changes to media:
- Unlike previous versions, few versions bundled together
- Changes to WSUS package as well


What’s new:
- Windows AutoPilot deployment
- Subscription based activation for Windows 10 Enterprise
- Windows Update for Business (WUfB) with additional controls
- Introduction to Mixed Reality Apps
- More changes to windows defender
- improved Analytics for Windows

Changes to ADK:
With the release of Windows 10 1709, Windows ADK for Windows 10, Version 1709 now available.
Hope unlike the previous version of ADK, this is a bug free release…..
The new ADK is available here

So folks happy servicing……

Friday, October 13, 2017

OnSearchComplete - Failed to end search job. Error = 0x8024401c

Recently I have noticed that the update scan started failing  on all the Windows 10 1607 devices with; 
OnSearchComplete - Failed to end search job. Error = 0x8024401c.
Scan failed with error = 0x8024401c


At the same time SUP's CPU usage went as high as 99%, soon after deploying a servicing update to Windows 10 1607 devices. The server (SUP) became unresponsive, however as soon as I shut down the 1607 client machine the CPU usage on the server was dropped.
According to the Microsoft the issue was caused by large metadata of Windows 10 1607 updates. 

To resolve this issue, Microsoft has released hotfixe's for various server platforms as below;
KB4039396 for Windows Server 2016
KB4041693 for Windows Server 2012 R2
KB4041690 for Windows Server 2012

This hotfix will fix the update metadata processing  and should be applied to all WSUS servers in your environment.

Once the hotfix is applied, the client devices should complete the scan process successfully.