Hi.   I have a strange behavior in my SCCM environment. Actually the SCCM 1606 is installed and fully patched. Until a few weeks ago it was working with no problem at all. I have been distributing windows 10 successfully. I need to reinstall the OS in one machine through PXE. Everything works ok during the initial phases (The pc boot from WDS, the image is downloaded to the pc, the HD is partitioned and the OS is installed). The problem occurs at the time when the pc rebooted in order to cont

After upgrading to SCCM 1610, systems which have automatically upgraded the configuration manager client to version 5.00.8458.1005 are unable to perform Windows Update. In Software Center they are stuck at "Downloading (0% complete)". Systems with older versions of the client (e.g. version 5.00.8412.1307, and possibly older client) have no problem downloading and installing the updates.   Any idea what might be the problem?

Getting Upgrade Windows 7 to Windows 10 Please help me  

Hello everyone. Thanks for all the great information on the site. I've frequented often in my quest for learning SCCM.   I have a problem now for which I'm hoping someone can offer a suggestion. I have a Task Sequence that has a boot image enabled. I need to change the current x86 boot image to a different x64 boot image. However, when I click the Browse button, I get the 'Select a Boot Image' window and it just sits at 'Loading...' forever. I can view all the Boot Images successfully from

I haven't seen much discussion about the new boundary group changes in 1610. I am still testing it in the lab environment, but things aren't happen to what I am expecting. So after upgrade from 1602 to 1610, boundary group with "slow connection" DP before, is automatically copied to a new boundary group, as described below.   https://docs.microsoft.com/en-us/sccm/core/servers/deploy/configure/define-site-boundaries-and-boundary-groups#a-namebkmkboundarygroupsa-boundary-group/ This boundary

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 Com

hi every one i have a strange problem in SCCM 2012 when i use F12 its doesn't work i search alot then i fond when the PC have an OS the F12 doesn't work ( btw its was work fine ) when the PC is free Dos i can use F12 normally also i can't fin smsts.log on my server i look at cmtrace i saw all log file except smsts i really need help

IntroductionMicrosoft has released yet another update for System Center Configuration Manager (Current Branch), this time it’s version 1610, that means that since System Center Configuration Manager’s (Current Branch) first release there have been the following releases: 1511 (Initial release, soon to be unsupported) 1602 1606 followed by Update rollup 1 1610 So what’s new ? Windows 10 Upgrade Analytics integration allows you to assess and analyze device readiness and compatibility wit