Closed Bug 1210344 Opened 9 years ago Closed 8 years ago

initial disk format step lost in MDT changes?

Categories

(Infrastructure & Operations :: RelOps: General, task)

task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: arich, Assigned: q)

Details

(Whiteboard: [windows])

When I went to reimage the w732 machines I had shut down in the middle of the MDT process earlier this week, none of them completed a touchless install because they were all stuck at the screen saying there was already an MDT install in progress in a bad state (and waiting for human intervention). If I recall correctly, we had an initial fdisk step that wiped any stale MDT installs in progress to avoid this state in the past. Did that get lost with the recent changes to MDT to support windows 10? I cleared most of them by hand but left t-w732-ix-203 in this state for further investigation.
Flags: needinfo?(q)
The hard disk image is still in MDT/WDS however the order of operations has changed in mdt 2013 so the dirty bit check happens first.
Flags: needinfo?(q)
That's disappointing... Any way to work around that?
I can alter the unattended xml on the winpe image to get this in place. Doing that now
Rolled in for x86 testing on 203.
mounted the LTI wim and altered the order option in the below code in unattended.xml to 1 <RunSynchronousCommand wcm:action="add"> <Description>Lite Touch PE</Description> <Order>2</Order> <Path>cscript.exe X:\Deploy\Scripts\ZTICleanSetupInprogress.vbs</Path> </RunSynchronousCommand> Looking good on 203. WIll need to do the same for x64
Changes rolled for x64 which covers windows 10/8/2008
DId we also test on XP? I assume that it will function as it did for w7, but testing is a good verification.
Not yet it is on the list. However, the win pe environment is exactly the same ( uses the same boot media file) for xp and 7 Q
I tried reimaging t-w864-ix-181, but it appears to just be sitting there at the cmd.exe window.
This has been re added and a low level format added for win 10.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.