From my experience I’ve seen this when the SCCM Primary site server are on Server 2016 and Server 2019 and the new DP server is running 2019. If you for example install a new Site server with an Image that does not contain all the latest patches you might run
Auto MDM Enroll: Device Credentials (x1), Failed (Unknown Win32 Error code: 0x8018000a) A while back I was working with a customer who was in the process of co-manage their devices in their ConfigMgr environment and most of the computers enrolled just fine but they had some devices who kept on
Late January Microsoft introduced something they called phased deployment in the technical preview 1801 for ConfigMgr and I went through the feature in a blog post here: https://timmyit.com/2018/01/22/configmgr-technical-preview-1801-phased-deployment 2 months later we now have a new ConfigMgr current branch release version 1802 and with that we now have the
The ConfigMgr product group just keeps on producing builds for us to test out and here is the latest one, ConfigMgr Technical Preview 1801. One of the new features they introduced that caught my attention was something they called “Phased deployment” and in the documentation they wrote: Phased deployments
Last night for us Europeans there was another ConfigMgr Technical Preview release and this time its version 1710. There are many new great features indroduced to this Technical Preview and the full overview you can find over at Microsoft. https://docs.microsoft.com/en-us/sccm/core/get-started/capabilities-in-technical-preview-1710 In this post I will focus on one
I recently stumble upon a bug in ConfigMgr that can cause issues with application deployments so that applications won’t install. When you are creating and application and gets to the step where you are supposed to create a Deployment type and you give the deployment type a name containing some