none
LocationServer.xml not loading RRS feed

  • Question

  • I'm trying to use the LocationServer.xml ability to choose from multiple deployment shares.  From the little I can find about how to do this, I think I have it set up right, yet when I boot from litetouch it merely asks me to enter the deployment share path.  To me, this indicates that my changes to bootstrap.ini have taken effect but not the locationserver.xml.

    If I drop to console in the litetouch deployment, I can go to x:\deploy\Control\ and see LocationServer.xml .  If I do a type LocationServer.xml, it is the one I created and is in the appropriate format, so my extras directory is copying.  I feel like I'm missing something simple here but not sure what it is.  Any recommendations?

    Monday, March 13, 2017 5:10 PM

All replies

  • I'm trying to use the LocationServer.xml ability to choose from multiple deployment shares.  From the little I can find about how to do this, I think I have it set up right, yet when I boot from litetouch it merely asks me to enter the deployment share path.  To me, this indicates that my changes to bootstrap.ini have taken effect but not the locationserver.xml.

    If I drop to console in the litetouch deployment, I can go to x:\deploy\Control\ and see LocationServer.xml .  If I do a type LocationServer.xml, it is the one I created and is in the appropriate format, so my extras directory is copying.  I feel like I'm missing something simple here but not sure what it is.  Any recommendations?

    Did you take DeployRoot out of your CS and Bootstrap?
    Monday, March 13, 2017 7:28 PM
  • I'm trying to use the LocationServer.xml ability to choose from multiple deployment shares.  From the little I can find about how to do this, I think I have it set up right, yet when I boot from litetouch it merely asks me to enter the deployment share path.  To me, this indicates that my changes to bootstrap.ini have taken effect but not the locationserver.xml.

    If I drop to console in the litetouch deployment, I can go to x:\deploy\Control\ and see LocationServer.xml .  If I do a type LocationServer.xml, it is the one I created and is in the appropriate format, so my extras directory is copying.  I feel like I'm missing something simple here but not sure what it is.  Any recommendations?

    Did you take DeployRoot out of your CS and Bootstrap?

    I did take it out of the bootstrap.ini.  It isn't booting automatically to a deployment share anymore, so I take it that change took place.  I don't have the deployroot in my cs that I can see.
    Monday, March 13, 2017 7:34 PM
  • DeployRoot being set should only create the default choice. Can you link an example bdd.log?

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    Monday, March 13, 2017 8:06 PM
    Moderator
  • DeployRoot being set should only create the default choice. Can you link an example bdd.log?

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    I'm not sure I understand what you mean?  DeployRoot isn't set, but also locationserver.xml isn't being pulled from, so instead I just get a screen asking where the deployroot is. 

    I looked in bdd.log and there is no reference to a deployroot.

    Monday, March 13, 2017 8:25 PM
  • DeployRoot being set should only create the default choice. Can you link an example bdd.log?


    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it. Also if you don't post logs your problem won't be easily solved.

    I'm not sure I understand what you mean?  DeployRoot isn't set, but also locationserver.xml isn't being pulled from, so instead I just get a screen asking where the deployroot is. 

    I looked in bdd.log and there is no reference to a deployroot.

    Did you create the folder structure correctly?

    C:\DeploymentShare\Extrafiles\Deploy\Control

    If so, post your LocationServer.xml file

    Monday, March 13, 2017 9:02 PM
  • Did you create the folder structure correctly?

    C:\DeploymentShare\Extrafiles\Deploy\Control

    If so, post your LocationServer.xml file

    Well that was one thing I was a bit confused by in the documentation.  My MDT server is NOT where my deployment share is, but all the documents I've seen show the extra files entered as something like c:\extrafiles\... so what am I entering here?  A directory on the deployment share or one on the MDT server?  I ended up creating the directory structure on the MDT server, and yes, I believe I have it structured correctly.  Again, when I boot into litetouch, I can hit F8 and find my LocationServer.xml file under x:\deploy\Control\LocationServer.xml, so I am guessing what I did should work...but it isn't working.

    Here is what I have:

    <?xml version=”1.0? encoding=”utf-8? ?>
    <servers>
        <QueryDefault></QueryDefault>
        <server>
            <serverid>1</serverid>
            <friendlyname>
                Production Deployment Share
            </friendlyname>
            <UNCPath>\\myserver1\myshare</UNCPath>
        </server>
            <server>
            <serverid>2</serverid>
            <friendlyname>
                Test Deployment Share
            </friendlyname>
            <UNCPath>\\myserver2\myshare</UNCPath>
        </server>
    </servers>

    Monday, March 13, 2017 9:08 PM
  • First make sure Bootstrap.ini does not have a DeployRoot set, as in delete the whole line DeployRoot=

    "Extra files" can reside anywhere, you just tell MDT where they are.

    Your extra files folder would then contain LocationServer.xml file.

    Make sure that you update your deployment share so that it builds a new bootable image. This boot image is the one you must use so that when it boots up you will see the wizard screen with drop down menus to choose which deployment share to connect to.

    I've been using this for years and it works great since you only have to keep and distribute one boot image but can connect to multiple shares.


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Tuesday, March 14, 2017 2:24 PM
  • End result, you get to choose which DS you want to connect to


    If this post is helpful please vote it as Helpful or click Mark for answer.

    Tuesday, March 14, 2017 2:28 PM
  • It looks like my xml file had some issues with it in the first line.  Have fixed those and will see if that takes care of it...man, is there anyway to speed up regenerating?  It takes FOR-EVER

    Tuesday, March 14, 2017 2:30 PM
  • Yep, that was the issue.  It is working now...I do have one more question though.  My understanding is that using locationserver.xml wipes out authentication seettings.  I had the "domain" prepulated, which it isn't now.  Is there a way to put that back on a per-share basis?

    Tuesday, March 14, 2017 3:49 PM