Issue: ConfigMgr 1602 update not visible in the console
The other day I was upgrading a customer’s environment to ConfigMgr 1602 when I ran in to an issue. Following the upgrade to ConfigMgr 1511 I went in to the Updates and Servicing node to upgrade to 1602. I received a No items found message, even though the update had been properly synced according to the logs.
The reason why this happens is due to the scope of the object in the ConfigMgr RBA. If the account does not have access to All Security Scopes, the update will not be visible.
Solving this requires you to add the All Security Scopes to the Administrative User/Group which will run the update.
Go to Administration\Overview\Security\Administrative Users, right-click and go to Properties.
Press Add and All Security Scopes.
Once added, the All Security Scope will be visible.
Once you have added All Security Scopes, close the console and re-open it. Now the update should be visible 🙂
About the author
Daniel Classon works as a Senior Consultant at Mansoft, focusing on Microsoft Configuration Manager, Windows 10 and Powershell
- How to install .NET Framework 3.5 on Windows Server 2012 and Windows Server 2012 R2 948,050 views
- Issue with mounting new ISO files from TechNet in Windows 8 and Windows 8.1 Preview 63,011 views
- Solution to OSD issue 80072ee7 29,140 views
- Powershell: Script to set Outlook 2010/2013 signature using information populated from Active Directory 30,611 views
- Guide: How to get PXE boot to work in Hyper-V 101,067 views
- Guide: How to force specific sites to always run in Compatibility View using Group Policy 136,995 views
- How to change between a Full Installation (GUI) and Server Core in Windows Server 2012 63,172 views
- Hyper-V: Issue when starting virtual machine from downloaded ISO file 7,054 views
- Guide: Solving WDS issue with DHCP port conflict 10,843 views
- How to create a bootable Windows 8 USB using Diskpart 29,716 views