+ Post New Thread
Results 1 to 15 of 15
O/S Deployment Thread, fail to deploy image in Technical; I decided to start from scratch again just to get a clean slate, so i delete all my image, TS. ...
  1. #1

    Join Date
    Jul 2014
    Posts
    54
    Thank Post
    7
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    fail to deploy image

    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.

    fejl.jpg

    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.?
    Attached Images Attached Images
    Last edited by denmyos; 31st July 2014 at 11:18 AM.

  2. #2


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,647
    Thank Post
    229
    Thanked 865 Times in 743 Posts
    Rep Power
    297
    are you still using an x86 boot image for mdt that was created on your old mdt share/setup?

  3. #3

    Join Date
    Jul 2014
    Posts
    54
    Thank Post
    7
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by sted View Post
    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.?

  4. #4
    ADMaster's Avatar
    Join Date
    May 2012
    Posts
    333
    Thank Post
    5
    Thanked 35 Times in 30 Posts
    Rep Power
    23
    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

  5. #5

    Join Date
    Jul 2014
    Posts
    54
    Thank Post
    7
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by ADMaster View Post
    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.

  6. #6
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    1,013
    Thank Post
    42
    Thanked 84 Times in 80 Posts
    Rep Power
    22
    Ate you deploying a x86 with a x64 boot. That is not supported.

  7. #7

    Join Date
    Jul 2014
    Posts
    54
    Thank Post
    7
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by free780 View Post
    Ate you deploying a x86 with a x64 boot. That is not supported.
    yes, i doubled checked.

  8. #8
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    1,013
    Thank Post
    42
    Thanked 84 Times in 80 Posts
    Rep Power
    22
    What happens if you have no product key? Do have KMS deployed?

  9. #9

    Join Date
    Jul 2014
    Posts
    54
    Thank Post
    7
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by free780 View Post
    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.
    Last edited by denmyos; 1st August 2014 at 12:18 PM.

  10. #10
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    1,013
    Thank Post
    42
    Thanked 84 Times in 80 Posts
    Rep Power
    22
    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.

  11. #11

    Join Date
    Jul 2014
    Posts
    54
    Thank Post
    7
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    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.

  12. #12
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    1,013
    Thank Post
    42
    Thanked 84 Times in 80 Posts
    Rep Power
    22
    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.

  13. #13

    Join Date
    Jul 2014
    Posts
    54
    Thank Post
    7
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Quote Originally Posted by free780 View Post
    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.?

  14. #14
    Norphy's Avatar
    Join Date
    Jan 2006
    Location
    Harpenden
    Posts
    2,384
    Thank Post
    54
    Thanked 315 Times in 245 Posts
    Blog Entries
    6
    Rep Power
    120
    Quote Originally Posted by denmyos View Post
    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.

  15. #15
    free780's Avatar
    Join Date
    Sep 2012
    Posts
    1,013
    Thank Post
    42
    Thanked 84 Times in 80 Posts
    Rep Power
    22
    Might be to do with Unicode etc...

SHARE:
+ Post New Thread

Similar Threads

  1. Deploy Studio Failing to copy image
    By mdench in forum Mac
    Replies: 0
    Last Post: 20th March 2013, 01:00 PM
  2. Using Server 2008 WDS to deploy images accross VLANs
    By Rav-Singh in forum O/S Deployment
    Replies: 6
    Last Post: 1st June 2012, 08:15 PM
  3. [Fog] Dell E5420 with XP failing to capture image
    By localzuk in forum O/S Deployment
    Replies: 3
    Last Post: 18th January 2012, 09:40 AM
  4. GPO failed to deploy
    By leco in forum Windows Server 2008
    Replies: 11
    Last Post: 24th July 2009, 06:46 PM
  5. Replies: 3
    Last Post: 7th May 2007, 10:49 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •