PaulWhite@pickens.k12

I will start a new thread about the Hash Values. Thanks

I don't know what happen to my text. So for some reason the clients stopped reporting I guess and all updates after 9/2018 were showing as 0 required, also no of the updates that were deployed were installing. 1. I removed all setting from the group policy for updates except I left the server as the source. 2. I don't know if this is right but I added my Site server to the default site boundary group. Updates started working again but in the last 2 days deployments have stopped. They start to install but get the error about incorrect hash values. I don't know what happened to my text.

Here is a screen shot from that error.

I got it thanks. This was the link it sent me to which really didn't help( https://docs.microsoft.com/en-us/sccm/core/plan-design/changes/deprecated/removed-and-deprecated). After I looked at the log it was pretty clear, i had a Distribution Point that was still running 2008R2 and it was causing the issue. I upgraded the server last night and now the prereq passes. I will do the upgrade tonight. Thanks

Wanted to update to 1806 this weekend but for the first ever I am failing the prereq check says because of OS. Primary server only running on 2012R2 and SQL 2012 SP$ running on 2012R@ as well. Any ideas would be welcome. Thanks

Yes, Yes even though I have the hotfix installed it was the "previous" button that got me. I ran the a search for id on all systems and found one with the same id as the unknown x64 computer. Thanks for every ones help on this one. I am connected by VPN but I just imaged a VM and it work fine.

I do have the hotfix installed but it does seem very suspect. The reason I say that it just imaged a lab then stopped. We don't image known computers but I could build TS and deploy to some test computers.

I just created boot media usb and it does pretty much the same thing, it says no task sequences were found.

I did not have F8 enabled on the boot image, but I changed that yesterday. I was looking at my smsts.log this morning and I noticed something strange. If you look right under that line that is high lighted "there are no task sequences available for to this computer.

That looks like it is trying to write to C: drive but cant, are you sure that it's loading win 10 to the c drive. Have you tried to do the UEFI partiton step.

Can you post a screen shot of your task sequence, I had this but got through it though I can't remember how. Are you doing secure boot, UEFI?

So around lunch time today imaging just stopped. I am on 1702 with the update installed and have one primary site server and 24 DP's. One of our techs imaged a lab this morning around 11:00 and when he tried to start another after lunch, the pc's will boot get an IP and when they will download the boot wim and go through the windows start up. Once they get to initialising network connections it just dies, screen goes blank and the computer restarts. I have not changed anything in the boot image but it is the same kind of behavior you get when the boot image is missing the network drivers and since we have 27 different models of PC I doubt this is the issue. It couldn't come at a better time, we have about 15 labs left to image and School starts on Thursday. There are no issue in the console everything looks healthy. I am at a loss, I have read all day and even tried removing PXE from one of my DP's and adding it back. I did run updates on the Site server and database server on Thursday of last week but it stopped today not on Thursday after I ran the updates. Any and I mean any suggestion would be appreciated.

I re-imaged the laptop yesterday with one our teacher images. Student computers get Avast for Business and our teacher/administrator computers get webroot. It upgraded fine with the webroot so Avast is the culprit even when uninstalled the upgrade fails. Thanks

Sorry that was from the client, this is from the server. If you need the original client file I will have to wait for this image to be done and try the cycle over again. smsts.log

It is uploaded, I am running another image on that laptop now. The image I tried to upgrade has Avast on it and even though I removed it I am thinking it could be the culprit. The virtual PC that worked had Webroot. I uploaded the SMSTS log earlier. Here it is again. smsts-20170530-075210.log

Did you get an answer to this, I am having the same problem. Works fine on a virtual PC but it will not on a real PC. I created a new thread before I saw this one. I am doing Enterprise to Enterprise.

I created an upgrade package in SCCM and the task sequence runs fine on a VM, but when I try it on a physical laptop it fails. The error is just the generic code and the smstslog just stops, no errors. here is the error screen shot and log. Configuration Manager CB 1702 Windows 10 Enterprise CB 1703 X64 Dell Latitude E5420 Windos 7 Enterprise X64 smsts-20170530-093550.log

So I removed the classification for Upgrades from the console and opened wsus on the server and ran the cleanup wizard and it freed up 147Gb of space on that drive which may hold me over until I can build another raid on the server. That's a lot of space for files.

I upgraded from 1610 to 1702 Last Friday and everything went great until I turned on the upgrades classification in SUP in the console. I ran a update sync when I left yesterday and over night the updates filled up my source drive using over 250Gb of hard drive space. When I came this morning the d:\where my source file are was completely full. I checked and the WSUS content is folder is at 1.17Tb today. Do windows 10 updates take that much room? Any way to turn off upgrades classification and purge those up dates from the server?

I have about 6 class rooms throughout our school district that have a wol at 2pm every day. They are at different schools (boundaries groups) and in different collections within SCCM. If I track down the event id on any of the machines the wol is coming from Cofig manager. I have checked random computers in the reports of SCCM for pending wol messages and all the deployments to those machines for wol and I can't find the answer. If I were to take one machine that is doing this what would be the steps to track down where the wol is coming from. A check list if you will? Any help would be appreciated at this point. Thanks

Still struggling with this, one of the techs imaged 6 Dell e5450's yesterday. All of the applications installed except 2 of the machines were missing Office 2013. Office 2013 is the only application that seems to not install. I have to move to the top of the list so it installs first and I did add the Task Sequence variables you suggested above.

I just did a very old computer HP 6730s, yes we still have some of those. It installed everything but Office 2013 here are the logs. Thanks for the help. AppEnforce.logsmsts.log

For some reason 2 days ago my task sequence that we use became very hit or miss for installing applications during OSD. It worked fine before, then it started missing Office 2013 so I removed it from all TS's and DPs made a new package and sent it out again. Today we have imaged about 10 machines and all but one got Office 2013 but some were missing another Application. Here is the task sequence what's going on.

Thanks that was it. I had read about the bug but it just didn't click for some reason. Thanks again