Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Delay Domain Join process in MDT 2012

Answered Delay Domain Join process in MDT 2012

  • Thursday, January 24, 2013 8:14 AM
     
     
    Sign In to Vote
    0

    Hi,

     have MDT 2012 update 1 installed. I am using it to deploy Windows 8 Enterprise. The problem is that my GPO disclaimer and policies break the autologon. I need to delay the domain join process in MDT 2012. I know how to do this in MDT 2010. There I have a step in the task sequence which I could move down, however there is nothing like that in MDT2012. Unfortunately a prestage OU is not a possibility.

    Thank you in advance.

     

All Replies

  • Thursday, January 24, 2013 2:23 PM
     
     
    Sign In to Vote
    0

    Take a look at this link - Domain Policies that break MDT 2010

    http://www.deployvista.com/Default.aspx?tabid=78&EntryID=147

    S

     
  • Thursday, January 24, 2013 2:29 PM
     
     
    Sign In to Vote
    0

    Take a look at this link - Domain Policies that break MDT 2010

    http://www.deployvista.com/Default.aspx?tabid=78&EntryID=147

    S


    I had a look at that, but it does not help me. I use that in my MDT 2010 / WIN7 deployment. I need something that will work in MDT2012 and WIN8.
     
  • Thursday, January 24, 2013 6:02 PM
     
     Answered
    Sign In to Vote
    1

    Try using the process described at  http://blogs.msdn.com/b/alex_semi/archive/2009/08/28/avoiding-legan-notice-that-breaks-mdt-autologon.aspx

    I've never had to deploy Windows 8 to production but I know the process works just fine with MDT 2012. It should work fine in Windows 8, since you're really just saving variables, joining a workgroup, and then using the saved variables after the initial boot into Windows.

    -Nick O.


    • Edited by FNO1980 Thursday, January 24, 2013 6:02 PM
    • Marked As Answer by EbenFourie Monday, January 28, 2013 6:39 AM
    •  
     
  • Thursday, January 24, 2013 10:14 PM
     
     Proposed
    Sign In to Vote
    1

    I recommend a different approach:

    Join the domain, but do not join your ou.
    Instead join a staging ou which has very limited (if at all) policies applied.

    Afterwards you can move the computer to the correct ou with a script (one-liner in PowerShell).
    Will do that soon too, but currently moving the computer by hand as I also want to add a description afterwards.

     
  • Friday, January 25, 2013 11:38 PM
     
     Proposed
    Sign In to Vote
    1

    I use the process described here to handle disabling ALL group policy assignments during deployment.  Works great!  I've been using it for all my Windows images in MDT 2012, including Windows 8.

    http://www.microtom.net/deployment/temporary-disable-legal-notice-dialog-during-windows-7-deployment

    Hope this helps!

    • Proposed As Answer by Darth Mongo Friday, January 25, 2013 11:38 PM
    •  
     
  • Monday, January 28, 2013 6:39 AM
     
     
    Sign In to Vote
    0

    Try using the process described at  http://blogs.msdn.com/b/alex_semi/archive/2009/08/28/avoiding-legan-notice-that-breaks-mdt-autologon.aspx

    I've never had to deploy Windows 8 to production but I know the process works just fine with MDT 2012. It should work fine in Windows 8, since you're really just saving variables, joining a workgroup, and then using the saved variables after the initial boot into Windows.

    -Nick O.



    Thank you for the link Nick, this worked perfectly on MDT2012 and Windows 8.