none
WDS with MTD - Client laptop want to connect to an other deployment server

    คำถาม

  • Hello everybody,

    I'm on this problem since few weeks and I can't found the solution, please help !!

    First of all, excuse my english, I'm french and my english in not perfect.

    This a a company with 2 sites on the same domain, the two sites have a deployment server.

    One of them, the server in France works as well, there is no problem for the deployment, I don't have installed theses server I'm came in the company after, and now I have to add a new image of deployment of laptops. I have uploaded the image of laptop from the server of France to the server of the USA, uploaded the drivers too. 

    The problem today is that When we run the network deployment at the USA, we arrive to the Wizard with the choice of the keyboard, static IP settings and the button "Run the Wizard" I have a windows Wizard Error :

    A connection to the deployment share

    (\\FR-SERVER\DeploymentShareMDT$) could not be made.

    The following networking device did not have a driver installed.

    PCI\VEN_8086&DEV_1502&SUBSYS_21CE17AA&REV_04 

    Abord

    Retry

    Ignore

    Ok, so it seems that it's an error of driver, perhaps yes, but the driver is well on the USA-SERVER. The strange point is : Why the error concern the FR-SERVER if I launch the installation from the USA-SERVER.

    I have checked the Bootstrap.ini and it is written :

    [Settings]
    Priority=Default

    [Default]
    DeployRoot=\\USA-SERVER\DeploymentShare$

    I don't know where watch now...

    Best regards all !

    29 พฤษภาคม 2555 15:49

คำตอบ

  • One of the few things defined in the boot.wim or LiteTouch.wim in bootstrap.ini is the name of the deployment share.  So you can't simply copy the LiteTouch.wim to U.S. or client machines will try and connect to share in France.  I think ensuring that the drivers for the machine are injected into the LiteTouch.wim is best place to start.  You may need to recompile the LiteTouch.wim after adding drivers so they get injected.

    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog

    • เสนอเป็นคำตอบโดย James XiongModerator 5 มิถุนายน 2555 1:03
    • ทำเครื่องหมายเป็นคำตอบโดย James XiongModerator 6 มิถุนายน 2555 7:07
    30 พฤษภาคม 2555 13:41
  • It sounds like the LiteTouch.wim file does not have a driver injected into for the device above.  You could use drvload.exe from PE and inject what you think is the driver and verify that it works.   This is an article from WDS but contains troubleshooting information which may be helpful. Did you ensure that the LiteTouch.wim or boot.wim is the same between sites?

    http://support.microsoft.com/kb/923834


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog

    • เสนอเป็นคำตอบโดย James XiongModerator 30 พฤษภาคม 2555 6:31
    • ทำเครื่องหมายเป็นคำตอบโดย James XiongModerator 6 มิถุนายน 2555 7:07
    29 พฤษภาคม 2555 19:08

ตอบทั้งหมด

  • It sounds like the LiteTouch.wim file does not have a driver injected into for the device above.  You could use drvload.exe from PE and inject what you think is the driver and verify that it works.   This is an article from WDS but contains troubleshooting information which may be helpful. Did you ensure that the LiteTouch.wim or boot.wim is the same between sites?

    http://support.microsoft.com/kb/923834


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog

    • เสนอเป็นคำตอบโดย James XiongModerator 30 พฤษภาคม 2555 6:31
    • ทำเครื่องหมายเป็นคำตอบโดย James XiongModerator 6 มิถุนายน 2555 7:07
    29 พฤษภาคม 2555 19:08
  • Because I'm not on site, (I'm in France) I have to wait that somebody in the US do the actions. I 'll follow this link and I give you some news concerning this problem.

    Concerning these files (LiteTouch.wim or boot.wim ) I'm not sure, but I can copy these files from the FR to the US server. That will don't give problem?

    Thanks a lot I try that and I give you some news !

    30 พฤษภาคม 2555 9:20
  • One of the few things defined in the boot.wim or LiteTouch.wim in bootstrap.ini is the name of the deployment share.  So you can't simply copy the LiteTouch.wim to U.S. or client machines will try and connect to share in France.  I think ensuring that the drivers for the machine are injected into the LiteTouch.wim is best place to start.  You may need to recompile the LiteTouch.wim after adding drivers so they get injected.

    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog

    • เสนอเป็นคำตอบโดย James XiongModerator 5 มิถุนายน 2555 1:03
    • ทำเครื่องหมายเป็นคำตอบโดย James XiongModerator 6 มิถุนายน 2555 7:07
    30 พฤษภาคม 2555 13:41
  • Ok, the problem is solved for this error message.

    Thank you very much for your help, I have double checked the driver and imported them one by one and then create a new boot image in WDS.

    Now I have an other error : The list of task sequences is empty but it's an other subject and there is probably some messages concerning this error.

    Thank you very much again !

    6 มิถุนายน 2555 8:05