hipsterdoofus

Senior Member
Joined
Apr 13, 2010
Messages
7
Hey all, hope you can help me.

I'm attempting to use MDT for deployment. I've been partially successful, but have had a lot of interruptions and keep having to restart the process. My understanding and how I hope to do it is this:

Build a reference image with items that do not install well automatically and which are not frequently updated. Capture this reference image and use it to deploy and when deploying, install applications that update frequently.

In trying to get this process to work, I've had to go through multiple iterations of my reference image. I've also tried to do things like install RSAT on my reference image so I don't have to mess with that on deployment.

My problem is that the final time I added components to my reference image, it seems to have messed it up. On deployment, it reboots to finish and wants an administrator login, which I have not set (so I don't know what it would be). When I look at monitoring, it shows it at step 52. I'm pretty frustrated because I don't know what is causing it to do this and I'm kind of stuck at this point. Could adding RSAT (or something else) be messing with it? Is my whole process wrong?

I am on MDT 2013.
 
It sounds like you're facing some challenges with your MDT (Microsoft Deployment Toolkit) process. Let's break down your situation and provide some guidance to help you troubleshoot your deployment issues:

Reference Image and Deployment Strategy​

Your approach of creating a reference image with stable components and then deploying applications that update frequently is a common strategy and can be quite effective. Here are some key points to consider:
  1. Reference Image:
    • Include only stable, basic components and configurations in the reference image.
    • Avoid updating or changing this image frequently; instead, periodically update it to incorporate essential changes.
    []Application Deployment:
    • Handle frequently updating applications separately during deployment.
    • Deploy these applications separately from the reference image to keep it lean and stable.

      Troubleshooting Steps:​

      Now, let's address the issues you are facing with the deployment process:
    [
    ]RSAT Installation:
    • Installing RSAT (Remote Server Administration Tools) on the reference image should not cause the deployment to prompt for an administrator login during the process unless there were errors during installation.
    • Check the RSAT installation logs in the reference image to ensure it was successful and didn't cause any issues.
    []Authentication Issue:
    • The prompt for an administrator login during deployment could indicate a problem with your deployment task sequence or unattended settings.
    • Ensure that your deployment task sequence is correctly configured and doesn't require manual intervention.
    • Review your unattended settings to make sure they are properly set up.
    [
    ]MDT Monitoring:
    • Step 52 in MDT monitoring is related to the State Restore phase, where the system restores the previously captured state.
    • Check the logs (found in the deployment share under Logs) for any errors or warnings that might indicate what's causing the authentication prompt.

      Next Steps:​

      To troubleshoot further and resolve your deployment issues, consider the following steps:
    []Review Logs:
    • Examine the MDT logs, especially the BDD.log, for detailed information on where the deployment process is failing.
    • Look for any error messages or warnings that could give you clues about why the process is requiring an administrator login.
    [
    ]Task Sequence:
    • Double-check your deployment task sequence steps to ensure they are correctly configured.
    • Verify that the task sequence is handling user authentication and other settings as intended.
  2. Testing:
    • Test the deployment process in a controlled environment to observe the behavior and identify where it's deviating from the expected process. By following these steps and investigating the logs, you should be able to pinpoint the issue causing the authentication prompt during deployment and take corrective actions. If you need further assistance or encounter specific errors in the logs, feel free to provide more details for targeted help.