AFter I'm done customizing windows, I sysprep. (shift+F3 before minisetup) I tweaked the image and did remove most provisioned apps with the 'windows 10 Debloater' powershell script from GitHub. When building the 1803 the image (UEFI) I used Audit mode. This PC gets stuck in the above 'Downloading disk imagge.' / Red 'X' status 1 loop.Īnyone aware of the problem with 'Generalize ' in sysprep for windows 10?īuild 1709 went flawlessly - 1803 is another animal The PCs had the same previous image, so they are exactly the same SW. I let this go since last Friday Morning, and it was still going like this today (Monday morning) before i stopped it. This continues every ~16 seconds, and nothing ever happens. I Booting to Automation blank Deploy Server Eventually, the Status (in console) shows 'Downloading disk image.'ģ. I drag the restore job to the appropriate PC object in console.Ģ. Because 1 identical PC was able to boot and reimage without problem, I know the boot disk and PXE boot are correct.ġ. Both the problem PC and the other PC had the same previous image,before pushing this new image.Ĥ. This image pushed to an identical PC without problem, on the same subnet. This PC has the altiris agent, and the automation folder installed.Ģ. This particular issue is about a PC that needs to receive a new image, but I cannot make it happen.ġ. PC's don't want to rename to their current name after reimaging just being one of the problems. Then I had 25% of them upgrade to windows 10, and I had to upgrade to GSS 3.x and everythig that was simple became very complicated. I have over 400 PCs that I used GSS 2.5.1 almost flawlessly on. MTFTP is disabled.Īny help on resolving this issue would be greatly appreciated! I've attached our PXE Configuration to this post, although it is pretty run-of-the-mill. I've tried rebooting the DHCP/PXE server for VLAN 93, to no avail. I've tried restarting the DHCP Service, to no avail. I've tried restarting Altiris PXE Services, to no avail. Switching that same client computer to VLAN 85 results in a successful PXE boot menu. I have verified the DHCP Scope for VLAN 93 contains Option 60 'PXEClient'. We also have Microsoft DHCP and PXE servers installed on separate servers in VLANs 83, 85, 87, 91, 93, 95, and 97.Īt our VLAN 93 location, clients booting through network boot ARE assigned DHCP addresses, but receive the message 'PXE-E55: ProxyDHCP service did not reply to request on port 4011'.Īll other locations are working properly. We have GSS, DHCP, and a PXE server installed at our prime location in VLAN 253. Here's a problem that just started happening last week.

Ghost solution suite 3.3 download