Over the past week or so I've had a ton of clients start showing up as inactive and I'm not too sure whats going on.  I can see from the local agent logs that the machines seem to request policy updates but, never actually check in. Does anyone have any ideas on where to start troubleshooting?  I'm running a fully patched CB 1610.  

Current config: Server 2012r2, SCCM CB 1610, SQL 2016 Std. When I was running SCCM 2012r2, statistics for software updates showed for all updates. Now that I've migrated to current branch, I've yet to see any statistics for any of the updates. I get zero required, zero installed, zero compliant, unknown shows a number, and does show downloaded/deployed. Installed roles: App catalog web service point, App catalog website point, Asset intel sync point, Component server, Distribution poin

With SCCM 2007 and SCCM 2012 in All Systems I can see PCs with and without clients installed.  With SCCM CB I can only see systems with the client installed - the client is in the build.  If I copy the ccmsetup folder to a PC that isn't shown in the SCCM CB Console and then run the ccmsetup manually then it will show up in the Console.  I've checked that the boundary groups are the same and Heartbeat discovery is running in SCCM CB.  I'm sure I'm doing something wrong here, just wondering if any

Hi there I have just read the list of deprecated features/operating systems for ConfigMgr 1702 and there's still something i'm not 100% clear on. All of our Primary Site servers are running Windows Server 2012 R2 (so that should be fine). However, some of our Primary Sites do have their SQL databases residing on "other" servers which are running Windows Server 2008 R2 (SQL itself is indeed 2012 on those servers though). The question i have is can i upgrade to 1702 with this infrastructure?

Hello all. During OSD my task sequence is failing with error code 0x80004005 at the very end of "Apply Operating System". The attached smsts.log (smtsprobook) seems to indicate something funny going on with partitions? Test Systems: 1. HP Prodesk 400 G3 SFF 2. HP Probook 430 G3 History: I have created a task sequence for deploying Windows 7 Enterprise X64 w/ SP1. This task sequence works great for the HP Prodesk. No issues at all.       Task Sequence Steps (in order

Bear with me while I try to explain what I am attempting to do and what doesn't work. I am using SCCM 1511 (because I haven't updated it to the latest build), and MDT 2013 integration. I am using an MDT task sequence. So far most everything in my TS works. There are a few things that I cannot get to work properly though, and that's what I need assistance with. (all of this is to deploy Windows 10 1607 LTSB) 1. My reference image had (copyprofile for default profile) a custom background

We are upgrading to Current Branch and want to include patching from this and not WSUS as curretly used. what is the best way to patch 3rd party applications through SCCM Current Branch?

Introduction In a previous post you used PowerShell scripts to quickly install System Center Configuration Manager (Current Branch) version 1606 and then upgraded it using Updates and Servicing to System Center Configuration Manager (Current Branch) version 1610. In case you are not already aware there are two main branches (of Configuration Manager) available: System Center Configuration Manager (Current Branch) System Center Configuration Manager (Technical Preview) Sy