+ Post New Thread
Results 1 to 12 of 12
O/S Deployment Thread, Boot.wim looses mouse and keyboard while installing on vmware in Technical; Hi First post I have this problem with MDT / WDS When I try to install a boot.win (x86) on ...
  1. #1

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0

    Boot.wim looses mouse and keyboard while installing on vmware

    Hi
    First post

    I have this problem with MDT/WDS
    When I try to install a boot.win (x86) on my client (on vmware workstation) When I get to the "Run deployment wizard to install a new Operation system" screen, my mouse and keyboard stops working.
    The funny thing is that, it works when i use the boot.wim (x64)

    I guess its some kinda driver problem, but I'm new to both MDT/WDS and vmware so i dont know where to begin.

    My host machine is a x64 bit, don't know if that has something to do with it.

    Vmware v10
    MDT 2013
    Server 2012 R2

  2. #2
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,290
    Thank Post
    219
    Thanked 237 Times in 205 Posts
    Rep Power
    76
    You may need to extract more drivers.

    Try mounting the VMware tools ISO (c:\program files (x86)\VMware\VMware workstation\windows.iso) in something. Then extract the 32bit drivers from setup.exe using:

    Code:
    setup.exe /A /P C:\Extract
    For 64bit drivers use
    Code:
    setup64.exe /A /P C:\Extract
    Once you have these files, import them into your MDT drivers folder. You may have to regenerate your deployment share/boot image afterwards

  3. Thanks to themightymrp from:

    denmyos (4th July 2014)

  4. #3

    Join Date
    Jul 2009
    Posts
    605
    Thank Post
    56
    Thanked 115 Times in 100 Posts
    Rep Power
    70
    Usually I have no issues with the mouse/KB not working. If it helps, the only driver I import into MDT is the VMXnet3 driver for networking (only needed if you use the VMXnet3 NIC). A few years ago I had issues when I imported all the drivers from the VMware tools installer causing random crashes and hangs during the deployment.

  5. Thanks to computer_expert from:

    denmyos (4th July 2014)

  6. #4

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Thank you, for you quick respond. I'll try that.
    My MDT/WDS is also vmware 10, just to clearify

    Working on it now, will report back with result.

  7. #5

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by computer_expert View Post
    Usually I have no issues with the mouse/KB not working. If it helps, the only driver I import into MDT is the VMXnet3 driver for networking (only needed if you use the VMXnet3 NIC). A few years ago I had issues when I imported all the drivers from the VMware tools installer causing random crashes and hangs during the deployment.
    I imported all drivers, and i do mean ALL drivers. :S Just to make sure i didn't miss anything.

    I'm new to MDT/WDS, but is it correct that the BOOT.wim should be taken from deploymentShare\Boot\Boot.wim
    AND
    the IMAGE should be taken from Deployment\operation system\Windows 7x86\sources\install.wim
    ?

  8. #6
    themightymrp's Avatar
    Join Date
    Dec 2009
    Location
    Leeds, West Yorkshire
    Posts
    1,290
    Thank Post
    219
    Thanked 237 Times in 205 Posts
    Rep Power
    76
    Yes, the BOOT.wim is the initial WinPE section of the deploy. The install.wim (or whatever you may have) will be the Operating System that will be installed onto the machine.

    Once you have imported your drivers and updated the deployment share, you will have to import the updated boot.wim file (from the location you mentioned) into WDS so that it can take advantage of the changes.

  9. Thanks to themightymrp from:

    denmyos (4th July 2014)

  10. #7

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by themightymrp View Post
    Yes, the BOOT.wim is the initial WinPE section of the deploy. The install.wim (or whatever you may have) will be the Operating System that will be installed onto the machine.

    Once you have imported your drivers and updated the deployment share, you will have to import the updated boot.wim file (from the location you mentioned) into WDS so that it can take advantage of the changes.
    yes that's what I'm doing.

    I install vmware tools drivers, and Imporeted them to out-of-box driver, updated everything. Imported to WDS, restarted WDS.
    pxeboot into the new boot.wim (lite touch windows PE x86.)

    Didn't work.

    BUT

    Then i delete ALL my drivers in OUt-of-box drivers,,, Everything!!!
    And that seem to work

    BUT
    When I get to user credentials, it wants me to enter a DOMAIN, which i don't have, I'm sure i made the image as a workgroup. hmmm?

    But again i'm new and i have no idea of what im doing

  11. #8

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    I would like to say thank you, both of you.
    The trick of deleting all drivers worked.

  12. #9
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,505
    Thank Post
    10
    Thanked 508 Times in 445 Posts
    Rep Power
    116
    I've seen something similar twice recently. Did you have the intel USB3 drivers on the server? I'm guessing as you are using workstation it's added USB3.0 ports on newer VMs too.

  13. #10

    Join Date
    Jul 2009
    Posts
    605
    Thank Post
    56
    Thanked 115 Times in 100 Posts
    Rep Power
    70
    Quote Originally Posted by denmyos View Post
    When I get to user credentials, it wants me to enter a DOMAIN, which i don't have, I'm sure i made the image as a workgroup. hmmm?

    But again i'm new and i have no idea of what im doing
    It will be the name of the domain that the WDS/MDT server is a member of (if that doesn't work, try using a local user account on the MDT server with the domain set as the hostname of the MDT server).

    Providing that you haven't configured any domain join options in MDT, it will deploy the image as part of a workgroup.

  14. #11

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by DMcCoy View Post
    I've seen something similar twice recently. Did you have the intel USB3 drivers on the server? I'm guessing as you are using workstation it's added USB3.0 ports on newer VMs too.
    I have the workstation 10
    But I used USB 2.0 (in the virtual Machine settings)

  15. #12

    Join Date
    Jul 2014
    Posts
    84
    Thank Post
    7
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by computer_expert View Post
    It will be the name of the domain that the WDS/MDT server is a member of (if that doesn't work, try using a local user account on the MDT server with the domain set as the hostname of the MDT server).

    Providing that you haven't configured any domain join options in MDT, it will deploy the image as part of a workgroup.
    I sat up the customsettings.ini to Joinworkgroup=workgroup

    That worked.



SHARE:
+ Post New Thread

Similar Threads

  1. Mouse and Keyboard age to install
    By rob998 in forum Windows 7
    Replies: 10
    Last Post: 14th February 2013, 11:51 PM
  2. Replies: 0
    Last Post: 5th August 2012, 05:05 PM
  3. Wireless Mouse and Keyboard
    By JPS in forum Hardware
    Replies: 5
    Last Post: 11th August 2010, 12:10 PM
  4. Mouse and keyboard on laptop not working
    By Little-Miss in forum Hardware
    Replies: 7
    Last Post: 22nd March 2010, 05:30 PM
  5. Mouse and Keyboard not working past post
    By sharkster in forum Hardware
    Replies: 13
    Last Post: 25th June 2008, 10:30 AM

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
  •