Goal: Push out 1709 upgrade to any computer that is 1703  via a Task Sequence. Problem #1.    I have a collection that looks for os build 15063. It finds 109 computers.  out of these computers 30 of them are actually running 1709 not 1703.  WTH?   What process pushes this information from the client?   Is it the machine policy? Is there a better way to build this collection?  Problem #2 When i deploy the image to this collection, some of the computers are getting it

windows-noob.com has been around for many years, and during that time I’ve written hundreds of step-by-step guides with screenshots. You may not be aware, but I’ve created indexes of these guides that cover multiple versions of System Center Configuration Manager (SCCM), Microsoft Intune and Microsoft Deployment Toolkit (MDT). These indexes are popular as you can see below. The indexes sort the guides into an easy to read format so that you can quickly find content

I'm using the following report and checking against all systems for %iTunes%. My report comes back with around 35 systems.  However, I've created a collection for iTunes, and it is only showing 9 systems. The query I am using for the collection is the following.   select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_ADD_REMOVE_

Hello all, I became the administrator of a SCCM site recently.  To my dismay, we've been imaging workstations with a USB thumb drive, not by SCCM OSD through PXE booting.  I've been trying to setup PXE booting without success.  Since I have limited knowledge on managing SCCM, hopefully I can resolve this issue with your help. The SCCM Site contains 1 Primary site server (CB 1706) and 2 distribution points.  The Primary site has all roles except the DP role installed (Is the DP role req

Background Information Sorry for the long post, but I'll try to be as detailed as I can. We are running ConfigMgr 1710 in our environment which consists of a single Site Server in our HQ datacenter.  Our environment is not huge and has around 500 clients (computers) being managed at this time in about 35 geographically separated sites.   Most of these sites have 10-20 computers, some only a couple each and most are not well-connected to the corporate network.  A few of our smallest sit

Dear Experts, I would like to get an advice from you Please. You may see multiple forums from me – As my Environment is bit complicated. Environment implemented by 3rd party and handover to us as part of transformation – Which we are struggling to upgrade or proceed further. Current Infrastructure: SCCM 2012 SP2 with Windows 7 Clients (Managing – Application, Patch, Operating System Deployment) This is running on Windows Server 2008 with SQL 2008 Required Infrastruc

Hi, I have heard that it was announced at the recent Geek Week in Germany that the SCCM client push account is stored in plain text and is therefore vulnerable. Is anyone able to confirm this as I cannot find anything mentioned on any sites? Apparently Microsoft released some news about it 3 weeks ago but kept it very quiet. Thanks, Andrew

Out of my 300 Windows 10 clients about 100 still haven't upgraded to 1709 despite a servicing plan which targets all of them. The old Windows versions are mostly running 1703 and some are still on 1607. The problem seems to be that no matter which criteria I use in the plan, the number client requiring the upgrade remain much to low: It's not clear to me why this is happening or how I can fix this. I guess that if the upgrade packages aren't detected as required any servicing plan