Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2012 U1: Changed server name, now can't authenticate to Deployment Wizard

Unanswered MDT 2012 U1: Changed server name, now can't authenticate to Deployment Wizard

  • Wednesday, October 03, 2012 3:35 PM
     
     
    Sign In to Vote
    0

    I've configured a server, we'll call it IMAGESERV, for one of our branch offices.  I set up WDS and MDT 2012.  Configured the deployment share to my liking, and it is shared as \\IMAGESERV\DeploymentShare$.  Tested out some deployments using PXE boot and everything worked fine.

    As I suspected this would be an issue, I then renamed the server to IMAGESERV-1 (because the machine will have to be renamed before it goes into production).  I went into the Properties of the deployment share.  I saw in the General tab that the Network (UNC) path field was still pointing to the old share location (\\IMAGESERV\DeploymentShare$), so I changed it to \\IMAGESERV-1\DeploymentShare$.  I then went into the Rules tab and, clicked the Edit Boostrap.ini button, and noted that under [Default] was the following entry:

    DeployRoot=\\IMAGESERV\DeploymentShare$

    I changed it to:

    DeployRoot=\\IMAGESERV-1\DeploymentShare$

    Then I updated the Deployment Share and added the updated boot image to WDS.

    PXE boot succeeds, but when I'm prompted for credentials, I get "Invalid credentials:  Network path not found."

    I'm stumped. I haven't tried booting with a boot disk yet, but I'm not sure what success or failure would prove.

     

All Replies

  • Wednesday, October 03, 2012 5:46 PM
     
     
    Sign In to Vote
    0

    HIt F8 get the commando prompt, then check X:\Deploy\Scripts\Bootstrap.ini to see if it is the right bootstrap on you boot media.

     
  • Wednesday, October 03, 2012 6:29 PM
     
     
    Sign In to Vote
    0

    Thanks Henrik for your reply.  I opened the command prompt and looked at Bootstrap.ini, and it was the correct path as noted in the first post.

    However, while I was there, I thought I'd take the time to run DISKPART and clean the Windows volume, which had a Windows 7 image deployed as a test from IMAGESERV before I changed the name to IMAGESERV-1.  For some inexplicable reason, that fixed it.  I was able to authenticate successfully after that.

    If someone wants to take a crack at explaining that, I'll buy you dinner.