sywitt

We recently had a situation where a SCCM patch broke our imaging capability. After weeks, I finally found the solution. My boss asked if there was a way to have a secondary server that we didn't patch, for availability in case we have this problem again. I suspect that in this particular situation, it wouldn't have helped because the issue was in the DB, but it's worth checking for future 'situations'. Our server is virtual, I'm thinking we can clone the existing instance (including sql) and if we have a problem, we can shut down the existing server and bring up the clone with the old version-or maybe restore from a snapshot. Will this cause problems with the newer clients? What high availability solutions are you folks using? Thanks in advance.

Thanks all, Found the solution here: http://www.techlimbo.com/software/sccm-1702-osd-imaging-issue-there-are-no-task-sequences-available-for-this-computer/ I was banging my head against the wall for over a week. I'll finally sleep tonight.

Thanks for replying. We are currently at SCCM 1702. I'm trying to get to my TS menu of Win 7 and Win 10 OS's for imaging. I'm not doing Win10 in place upgrades yet. In the past, we'd PXE boot into winPE - get the menu of available OS task sequences, pick one and image. We can't even get winPE to finish booting when doing PXE - when booting it from USB, there are no TS available. When we deploy win 10 beyond one-offs , we're planning to go with 1703.

Hello all, I've been using SCCM OSD to image machines for about 2 years. Suddenly last month, it stopped working. I assumed that we had a corrupted driver or boot wim. I re-created both the x64 and x86 boot wims, downloaded the newest WinPE 10 drivers, etc. and am still having the issue. When doing PXE boot, I"m getting the failure at preparing network connections. When loading PE from a usb, it loads but then says "There are no task sequences available for this computer." If I do an F8 , ipconfig shows an IP and diskpart shows the drives, which I assume means that I have the correct drivers. Fwiw- I've tried just about every driver combination that I can think of, to no avail. To make matters worse, our MS premier support contract ended the day before it broke and we're waiting for our legal dept. to sign the new enterprise agreement, so I have no MS support. I'm including the smsts.log from one of the machines and wireshark packet traces from a mirrored port for both PXE and USB PE boots. Any assistance is greatly appreciated, as I need to start pushing Win10 out by the end of the month. SCCMPXE-WINPE-Fail-1.pcapng SCCMUSB-WINPE-Fail-1.pcapng smsts-z230.log