[wds] Frozen Deployment on Wizard.hta

[Warwick_Tech]

Hi All,

 

Wierd issue we are now experiencing;

 

Around 50% of new machines built on cat6 cables now freeze on a blank wizard.hta screen

 

 

A restart either thinks the deployment is complete, or constantly logs in as administrator or default0

 

This is on a new WIM of 1909

 

MDT 6.3.8450.1000

 

The others go to deployment completed successfully or report failure as normal.

 

Anyone else had this?

 

-----

 

On a seperate note, some newer machines also take an age to download the NBP file, does anyone have any advice on this?

 

All my boot images are x64 as we run a purely 64bit environment now.

 

Regards,

[Warwick_Tech]

Hi All,

 

Wierd issue we are now experiencing;

 

Around 50% of new machines built on cat6 cables now freeze on a blank wizard.hta screen

 

[ATTACH=CONFIG]58786[/ATTACH]

 

A restart either thinks the deployment is complete, or constantly logs in as administrator or default0

 

This is on a new WIM of 1909

 

MDT 6.3.8450.1000

 

The others go to deployment completed successfully or report failure as normal.

 

Anyone else had this?

 

-----

 

On a seperate note, some newer machines also take an age to download the NBP file, does anyone have any advice on this?

 

All my boot images are x64 as we run a purely 64bit environment now.

 

Regards,

 

Reddit to the rescue!

 

However, I don't like loading drivers onto my MDT as I've had disasterous consequences before from this;

 

Does anyone have any other ideas/solutions?

[Steve21]

Add regkey during the task to disable windows updates on drivers? Then gpo it back in once built

 

Steve

[FragglePete]

I had this! It was essentially windows loading up a new driver for the network card, loosing the network connection which interrupted the task sequence causing this failure. I tired initially injecting the right drivers but that didn't solve it - bizarrely it still insisted on installing the older Realtek Drivers. The way I fixed it in the end was to put a 60 second pause in the sequence (essentially ping 127.0.0.1 60 times ) - just at the top of the State Restore group.

 

We had done 80% of the site without any issues, but then just hit this on a couple of rooms using newer PCs. Head scratching for a bit but works all ok now.

 

Pete

[Warwick_Tech]

I had this! It was essentially windows loading up a new driver for the network card, loosing the network connection which interrupted the task sequence causing this failure. I tired initially injecting the right drivers but that didn't solve it - bizarrely it still insisted on installing the older Realtek Drivers. The way I fixed it in the end was to put a 60 second pause in the sequence (essentially ping 127.0.0.1 60 times ) - just at the top of the State Restore group.

 

We had done 80% of the site without any issues, but then just hit this on a couple of rooms using newer PCs. Head scratching for a bit but works all ok now.

 

Pete

 

Hi Pete,

 

Thanks for this, can I grab a screenshot of the command/task sequence?

 

Cheers.

[FragglePete]

Hi Pete,

 

Thanks for this, can I grab a screenshot of the command/task sequence?

 

Cheers.

 

See attached. Hope it helps.

 

Pete

[evasion]

Is this going to help if I only have slow response form wizard.hta script during initial winpe loading stage?

Both 64 and 84 bit PE images are regenerated with fresh drivers and when F12 is pressed and PE starts to load I see wizard.hta presenting blank screen for couple of minutes, before it loads interactive screens to enter credentials. Any thing else to speed up this script?

[evasion]

Is this going to help if I only have slow response form wizard.hta script during initial winpe loading stage?

Both 64 and 84 bit PE images are regenerated with fresh drivers and when F12 is pressed and PE starts to load I see wizard.hta presenting blank screen for couple of minutes, before it loads interactive screens to enter credentials. Any thing else to speed up this script?

[3s-gtech]

Just hit this issue and just tried it - so far so good - 60 seconds of pinging has got the task sequence working!

[Olliedawg]

I'd just like to say thanks! Suddenly our task sequence started doing the same. Applied your suggestion & it now works!