none
MDT Error: "Unable to connect to the deployment share" in a disconnected scenario RRS feed

  • Question

  • I'm testing MDT to prepare and deploy few Windows 10 Images.

    I read on some official MS documents MDT can be used even in a disconnected scenario and it's what I'm trying to do: no WDS, no Domain, no WSUS, no Internet connection, no DHCP.

    The problem is the process of building and capturing an image soon stops with the infamous error: "Unable to connect to the deployment share... Connection OK. Possible cause: invalid credentials.". The credentials are fine and the share path is ok; indeed, I can manually "net use" the share with the credentials I can read in X:\Deploy\Scripts\Bootstrap.ini.

    I noticed in the logs that this error appear just after the error "<![LOG[IP Address could not be obtained]LOG]!...>". So I suspect the fact that a DHCP cannot be contacted is used by the process to "guess" that the share in not accessible despite the fact that the build machine already has an Automatic IP Address and the share can be contacted well.

    Indeed If I connect both the computer and the VM Build Machine to my Internet Router (with its DHCP server), build process starts fine. But, I think the process stops if the build machine lose Internet connection, despite the fact I have disabled Windows Update action in task sequence.

    So my question is: Can MDT be really used without DHCP and Internet Connection? How to configure so that it accept adn use an automatic IP and no Internet connection?


    Friday, December 8, 2017 12:26 PM

All replies

  • Let me see if i got this straight your deployment server and your build machine are connected but you'd like them to  have manually set ip addressed as opposed to setting up on DHCP?

    How are you setting your ip on the build machine, what are you specifying as the gateway and DNS? 

    Could i inquire more into why you don't want either of these systems online? 

    Friday, December 8, 2017 7:30 PM
  • My build machine and the computer hosting the deployment share are VM connected to a virtual switch without any DHCP. Il build machine could use the automatic IP it get instead of searching and waiting for a DHCP I think would be enough.

    Friday, December 8, 2017 9:34 PM
  • Usually you would want to specify static IP adress either manually during deployments (assuming you did not set SkipBDDWelcome to YES) or by modifying your Bootstrap.ini and subsequently regenerating your boot image: https://scriptimus.wordpress.com/2012/09/03/mdt-2012-automating-network-interface-configuration/

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Sunday, December 10, 2017 5:05 PM
  • I don't want to configure a static IP. Once the image has ben captured, I want do deploy to a computer on a network where there IS a DHCP.

    It is not possible to tell the MDT Build process to accept and use the Automatic IP the build computer get?

    Sunday, December 10, 2017 5:15 PM
  • Build and capture process usually has little to do with the actual deployment process. In fact, you could set up your Bootstrap to apply static IP configuration only to your VM in case you are using same deployment share to build and deploy your images. However, you need to apply static IP configuration if you are using an internal Hyper-V network switch which is not connected to your internet router / DHCP server to ensure you can connect to your deployment share.

    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Sunday, December 10, 2017 5:29 PM
  • So, if I configure a static ip on the BDDWelcome screen, this setting is only for building/capturing and is not persisted in the image captured? When I later deploy that image on a computer in the real network with DHCP the computer will search for the DHCP?
    Sunday, December 10, 2017 6:38 PM
  • Assuming you are using same deployment share for both and assuming you are reusing your VM, here is how you could work around the issue. Modify your Bootstrap.ini as follows:

    [Settings] Priority=MACAddress, Default Properties= [00:0C:29:98:E6:9F]
    OSDAdapter0EnableDHCP=False
    OSDAdapter0IPAddressList=10.0.0.2
    OSDAdapter0SubnetMask=255.255.255.0
    OSDAdapter0Gateways=10.0.0.1
    OSDAdapter0DNSServerList=10.0.0.1
    OSDAdapter0Name=Corporate LAN
    OSDAdapter0DNSSuffix=scriptimus.wordpress.com

    [Default]

    ...

    Personally I never tried applying static IP configuration in this manner as I usually have a separate deployment share but from my understanding, the process outlined above should work.


    Cheers,
    Anton

    Vacuum Breather Blog | Wing Commander Saga | Twitter

    Note: Posts are provided "AS IS" without warranty of any kind. If posts are helpful please don't forget to rate them as "Helpful" or as "Answer".

    Sunday, December 10, 2017 7:00 PM
  • Thanks for your support.

    I found that using a static IP address solve the issue but there is still some delay waiting for DHCP.

    Moreover using a Bootstrap.ini bound to MAC addresses is difficult to use.

    I found the easy solution is to run a tiny DHCP server as application while making these offline tests.

    Can also easily boot my VMs and Physical Machines with PXE this way.

    Monday, December 11, 2017 9:53 PM