Hi, I've updated from 1610 to 1706 and i'm getting the below in both Parent and Child Sites for my CAS and 2 x Primary Sites.  I've checked the logs and there are no errors so wondered if anyone else has came across this issue?

Introduction Microsoft has just released System Center Configuration Manager Technical Preview 1709, and that Technical Preview release allows you to configure co-management. Microsoft announced co-management at Microsoft Ignite (September 2017) and now with this release you can begin testing that scenario (however you still need the yet to be released Windows 10 Fall creators update edition, aka Windows 10 version 1709), so for now you'll need to test with a Windows Insider preview release

We are planning to use SCCM instead of WSUS server to manage windows and office updates for clients . What are the most valuable advantages of using SCCM ? . Is there is any warnings or issues that we must take care of ? . Any advice regarding moving updates to SCCM . Can we use old WSUS server DB instead of download all updates again after installing WSUS service on SCCM server .Thanks guys in advance.Can I test SCCM software update on certain collection using my current WSUS server as downstre

I get my client to install but it's not setting a site code. The client has installed ok on most servers and on one client machine out of 200. Boundries are configured, schema is extended, and I have permissions set in AD for the SCCM server. All these clients were apart of a different sitecode with a different server. That server had corrupt OS files the Microsoft couldn't fix and told me to reinstall the server with a new server name, sitecode, and IP. On my machine I have run the cc

Hi Experts, We are currently implementing SCCM Current Branch 1702 afresh for one of our customers replacing BMC Marimba, and it was only a week back that we were informed about another existing installation of SCCM in one of the regions. They are using SCCM 2012 SP2.for managing patching for both server and desktop endpoints, with one Primary site and 8 distribution points. Now in our current implementation, we are looking to manage approximately 10000 endpoints and 1500 servers via a standa

We started with Config Manager 1702. Since then we upgraded to 1706. The new client version is 5.00.8540.1007. We enabled Hierarchy Settings Properties of our site to Upgrade all clients using the production client within 4 days. One month later half of our computers are still showing "Client Version Reported from DDR" as 5.00.8498.1711 with Compliance Status of "Not Compliant." We are a Windows 7 and Windows 10 mixed environment. Can anyone shed some light as to what might be going on here

Hello Guys, I am deploying Windows 10 v1703 and wish to get rid of cortana talking through windows setup in my office environment (Cortana during the "Lets get your connected" step of OOBE). I am referring below article what I  wish to get rid of: https://www.windowscentral.com/windows-10-creators-update-features-cortana-setup-screens I referred below link but no luck in getting any direction: https://docs.microsoft.com/en-us/windows-hardware/customize/desktop/unattend/c

What would be really cool is if someone could create a step by step on how to set this up and working so that we get the in-app notifications and countdown timer, deployment required. I have scoured all sources and some people say this is working and others are saying that the experience hasn't changed and that SCCM is still force closing office proplus apps.