Jump to content


Zantec

Established Members
  • Posts

    7
  • Joined

  • Last visited

Zantec's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. it's OK it works by going through a local backup of the capture before manually copying it to the WDS server. it does not solve the problem but bypasses it hope that Microsoft makes a quick fix
  2. Hello everyone here is the answer from microsoft support: Hello, We have worked on this problem and we have succeeded in reproducing the behavior you are experiencing. We are still working to find out why this is happening, but it will probably take time. For the moment, as a workaround and not to prevent the deployment of Windows 10, I propose to use the local upload for the .wim image. Do not check the "Upload image to Windows Deployment Services server (optional)" option and save the .wim file to the machine. Then copy the .wim to the WDS server and continue with the deployment.
  3. with boot.wim windows10? I test boot.wim 2012server & get error <<the version of kernel information provided is invalid>>
  4. @marcel78 you'r solution doesn't work when I click on CONNECTION from the capture sequence I get an error message : the version of kernel information provided is invalid
  5. I take boot.wim server2012r2, launch sysprep & boot pxe : contact with server wds isn't possible I added the network driver on my wds I restart the capture process on the pc I do not get the "start" page of the capture menu hp probook 650G2 laptop pc network drivers I tested drivers windows10 & windows8 ... an idea ?
  6. we encounter the same problem with server 2012 r2 & w10 1709 (and 1703 ...) We contacted Microsoft support ... I'm at the 3rd rack scaled at the support without solution for the moment (sorry for my english, i'm french)
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.