Hello, I have recently encountered extremely slow download of the Image.wim files while in PXE environment. I have verified that IIS is not being limited and in monitoring the switch port the server is connected to I have getting on between 8-10% utilization of the 1GB port and the Server Resource monitoring is showing a max network at 100Mbps. The Image.wim file is 8.2GB and is taking roughly 6-7 hours to download.   This is not a question about TFTP transfer of the Boot.wim and have in pla

Hello,   After I upgraded ConfigMgr to 1610, I found none of my Windows 7 task sequences are able to complete. They fail at the "add driver" step and I believe it is due to the fact that the latest ADK 10.1.14393.0 is not backwards compatible with Windows 7. Since the ADK that is compatible with Windows 7 is not compatible with Windows 10 I had left the original working boot images for Windows 7 deployments and created a new boot image on the new ADK for Windows 10.   Unfortunately during th

Hi there, Recently we upgraded from SCCM 2012 to 1606 Current Branch. Most clients are updated successfully. I have some of them that are Failed. As show here: However, when I look at the details, it's hard to understand why. The correct client version should be: 5.00.8412.1307 In this screenshot you can see some clients that have the Failed status. Client Version Reported From DDR has the correct version. Client Version Reported From FSP/MP has the wrong ersion.

So just for the hell of it (and because I wanted to see what was involved) I decided to go full worse case scenario on my 1511 SCCM lab (1 Pri, 2 Sec). I deleted one secondary VM to emulate a total loss, decommissioned the second secondary as well as the primary. Then I created a new VM where I installed a clean 1606. I got everything running (cleaned the schema as well) and all my content reloaded.   My question is after enabling AD system discovery I see the systems again as expected but the

have a situation where at a couple of sites that if you configure the machine for UEFI and attempt to PXE boot it only works the first time. Though if you take the computer to a different VLAN it will again PXE boot one time, but subsequent PXE boots fail. However if you configure the computer for BIOS it can PXE boot all day long. We also then have a site where they can not PXE boot at all if the machine is configured for UEFI. Though we have a number of sites that PXE boot with BIOS or UEF

Hello SCCM Folks,   We are seeing an abnormally high CPU usage on our primary site server and have tracked it down to the WSUSPool of the IIS Worker Process. Digging even further we are finding that it is being caused by our Server 2016 boxes hitting the WSUS site consistently almost every three minutes.   We run our primary site server on Server 2012 R2 using System Center Configuration Manager 1610 (site version: 5.0.8458.1000). The resources on this machine have been sufficient for some

Everyone,   I've been on a mission to get a wireless task sequence working off of a USB jump drive/Stand-alone media OSD scenario, and i'm 99% there. I still have some long-term tweaks, but I am pretty pleased with it so far. The only thing I cannot get going is the computer rename script I have that works FLAWLESSLY over the wire, but since i'm having to join the wireless profile at the end of the task sequence I have to put the Gather/rename script there as well since it pulls our computer

Unable to add install.wim file in operating system upgrade package.   Error#   the specified unc path does not contain a valid WIM file or you do not have permissions to access it. please specify a valid path