PHGustavsson

I just wanted to stop by and say thanks for this! I really think that something like this should be included as standard in ConfigMgr. Snyggt värre, tack! /P-H

I'm REALLY confused right now. I've think I followed the "Steps to manage updates for Windows 10" guide to the letter (https://technet.microsoft.com/itpro/windows/update/waas-deployment-rings-windows-10-updates). I changed in two GPO's to Defer Updates. One for all clients in production, that was set to Current Branch for Business and to wait 90 days after the release of a new CBB version. The other one is for the test clients, that was set to Current Branch, and wait 30 days. Then I followed the SCCM part of the guide and created two Device Collections based on the Branch Readiness settings on the machines and setup two different Servicing Plans based on those collections (https://technet.microsoft.com/itpro/windows/update/waas-manage-updates-configuration-manager). All is well, or so I thought... I just found this Microsoft blog post, I read Scenario 2 and went "WTF?!" (https://blogs.technet.microsoft.com/windowsserver/2017/01/09/why-wsus-and-sccm-managed-clients-are-reaching-out-to-microsoft-online) This is confusing... Can you guys explain this to me? Thanks P-H

Ok, thanks

SCCM 1610 with all hotfixes. Windows 10 Enterprise 1607. I have an application that have two dependencies. It's setup so that both dependencies are installed before the application itself. Both of them are .msi files and both are recognized by SCCM with MSI Product Codes. The installation part is working fine. But they are not uninstalled if I uninstall the main application (using the old control panel and/or Win 10 Settings / Apps). The uninstall button is greyed out in Software Center. How do I get the uninstall button in Software Center to uninstall the application and the two dependencies? Is it possible? Regards P-H

Are you using the same computername but in another OU?

I think I found the cause of this problem, it seems that the client isn't getting a lease for the IP adress it receives from the DHCP. I booted the PC that I am using as a test machine into the factory Windows 10 installation. It got an IP adress from the DHCP and a 2 hour lease in the DHCP. I then did a restart and could PXE boot in UEFI without any issues. It started the deployment, installed, joined the domain, encrypted the disk with Bitlocker, sent the key to AD and installed all applications that I had added to the TS. Any ideas on where to check?

Getting three similar errors with ConfigMgr 1606 with both hotfixes installed. Missing management class description for class 'SMS_AppConfigTemplateSettings'\r\nSystem.Collections.Generic.KeyNotFoundException\r\nThe given key was not present in the dictionary.\r\n at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at Microsoft.ConfigurationManagement.AdminConsole.FrameworkInitializer.ReadSecurityInformationFromXml.Initializer(QueryProcessorBase queryProcessor, ConnectionManagerBase connectionManager, SmsNamedValuesDictionary namedValues)\r\n Missing management class description for class 'SMS_DeviceThreatProtectionSettings'\r\nSystem.Collections.Generic.KeyNotFoundException\r\nThe given key was not present in the dictionary.\r\n at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at Microsoft.ConfigurationManagement.AdminConsole.FrameworkInitializer.ReadSecurityInformationFromXml.Initializer(QueryProcessorBase queryProcessor, ConnectionManagerBase connectionManager, SmsNamedValuesDictionary namedValues)\r\n Missing management class description for class 'SMS_MDMDeviceCategory'\r\nSystem.Collections.Generic.KeyNotFoundException\r\nThe given key was not present in the dictionary.\r\n at System.Collections.Generic.Dictionary`2.get_Item(TKey key) at Microsoft.ConfigurationManagement.AdminConsole.FrameworkInitializer.ReadSecurityInformationFromXml.Initializer(QueryProcessorBase queryProcessor, ConnectionManagerBase connectionManager, SmsNamedValuesDictionary namedValues)\r\n Haven't got the 1610 update yet?!

Hi, I've setup SCCM Current Branch following the guides here on this forum, and I am now trying to deploy Windows 10 Enterprise x64 (v.1511v2) using PXE boot. I followed the SCCM MDT 2013 Update 2 guide and created a task sequence for Windows 10 and boot images for x64 and x86. It's done according to the guide, both boot images have PXE enabled and are distributed to the DP. The only thing that's not according to the guide is that I deployed the task sequence to the "All Unknown Computers" collection. I am connected on the same subnet as the SCCM server but get the following error: PXE-E55: ProxyDHCP service did not reply to request on port 4011 I can see in the SMSPXE.log that the client is connected to the server. I have attached the part of the SMSPXE log. The PXE boot has worked before, when I followed the same guide but with Windows 10 Enterprise x64 v.1607 ( that was before we decided to deploy Current Branch for Business (1511v2)). I uninstalled the Windows ADK and installed Windows ADK for Windows 10 v.1607 a while back, could that have anything to do with this problem? 1606 Hotfix 2 is installed. Thanks for a great forum and any help in solving this issue. Regards P-H SMSPXE.log