[wds] fail to deploy image

[denmyos]

I decided to start from scratch again just to get a clean slate, so i delete all my image, TS. etc.

 

Imported OS into MDT, made TS, imported image into wds and started to deploy, and now i get this error.

 

 

I have been getting that error for two says now.

 

Done everything, delete images in mdt,wds, delete TS and imported everything again, made new TS, imported in wds,,,,,and im still getting the same error.

 

The weird thing is that, im only getting it with x86, NOT with a x64 images.

 

The image is not corrupt, I installed it on a stand alone client, and it works fine.

 

Its probably something simple that i over looked, but what.?

Edited July 31, 2014 by denmyos

[sted]

are you still using an x86 boot image for mdt that was created on your old mdt share/setup?

[denmyos]

are you still using an x86 boot image for mdt that was created on your old mdt share/setup?

 

 

If I get the boot file from deploymentshare->boot

After importing a OS into MDT, wouldn't that be the lastet bootfile.?

[ADMaster]

No you need to right click the deployment and the click update it will ask you to do full or optimized. For this case you should do full.

The import the updated image into wds.

This will take awhile depending on drivers

 

On the mobile please excuse typos

[denmyos]

No you need to right click the deployment and the click update it will ask you to do full or optimized. For this case you should do full.

The import the updated image into wds.

This will take awhile depending on drivers

 

On the mobile please excuse typos

 

Nope didn't work, but it should be best pratice to do a full, when importing a new image.

 

But i'm wondering why doing but its loading a relaxwinpe.wim instead of a litetouchwinpe.?

 

 

hmmm it seems like the product key is the culprit, when i use the product key and copy+past it in "specify the product key for this opreation system" (which i have done many times before) I get the error in my first post.

But if i do not use a product key i get no error, and the deployment goes through as normal.

[free780]

Ate you deploying a x86 with a x64 boot. That is not supported.

[denmyos]

Ate you deploying a x86 with a x64 boot. That is not supported.

 

yes, i doubled checked.

[free780]

What happens if you have no product key? Do have KMS deployed?

[denmyos]

What happens if you have no product key? Do have KMS deployed?

 

I have no idea what going on now.

I thought it was the product key, but now i get the same error without the product key.

 

I think it has something to do with the boot.wim, as you said, but i can't figure out what.!?

 

Is it correct that the correct boot.wim is in

deploymentshare\boot\litetouchpe_x86.wim

 

When pxeboot i get a choice from

 

Lite touch windows PE (x86)

Lite touch windows PE (x64)

 

I press the x86

 

and the boot proccess starts BUT the it uses a boot\x86\image\relaxwinpe.wim

is this correct.?

 

 

Something is really wrong here

I use a x86 boot, when i get to the "windows Deployment wizard" AND choose the x64 TS i have made for my win7 x64 image,,it works!!!

 

 

 

I forgot to mention I'm on vmware 10 workstation.

Edited August 1, 2014 by denmyos

[free780]

I use a x86 boot, when i get to the TS wizard screen AND choose the x64 TS i have made for my win7 x64 image,,it works!!!

 

That should work as long as you are deploying to BIOS not UEFI.

[denmyos]

I think i finally found the culprit.

 

When you do a task sequence it ask for full name, two days ago i start write Næstved, instead of Naestved, which i have been doing prior to that.

 

writing naestved seems deploy smoothly.

 

 

I still dont know what Full name is for i dont see it anywhere in the OS.

[free780]

Its who its registered to. Usually the highest person in your org. You can find it by opening any explorer windows pressing alt then help>about.

[denmyos]

Its who its registered to. Usually the highest person in your org. You can find it by opening any explorer windows pressing alt then help>about.

 

Why would that tiny little thing cause such a big problem.?

[Norphy]

Why would that tiny little thing cause such a big problem.?

 

Why not?

 

I guess because æ is not a character that's used in English that often, the installer doesn't recognise it or know what to do with it and fails the sequence.

[free780]

Might be to do with Unicode etc...