Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
MDT 2010: Post Tasks to Shutdown, Resume Task and Rename Computer

Proposed MDT 2010: Post Tasks to Shutdown, Resume Task and Rename Computer

  • Tuesday, October 09, 2012 5:56 PM
     
     
    Sign In to Vote
    0

    Hello All:

    I have a semi automated deployment and would like to accomplish some additional steps for our team.

    I would like to be able to create an image which I can supply our vendor to pre-image our laptops before shipping them to us.

    The goal:

    1. Create generic computer account (I have that setup)

    2. Leave computer in workgroup (I have that setup)

    3. After deployment but before final post task shutdown the laptop. At this point the vendor ships the laptops to us.

    4. At first boot, the task resumes

    5. Windows Updates

    5. Input script to prompt to rename computer, add to domain (pre-filled) and prompt to add assigned end user to Local Admin Group

    Need your help and guidance on the best way to accomplish steps 3-5

    Your help is greatly appreciated!!!

     

All Replies

  • Wednesday, October 10, 2012 11:13 AM
     
     
    Sign In to Vote
    0

    Hi,

    Take a fresh machine. Install OS and all related application. Configure your required settings.Capture the image and send to vendor.

    Regards, Shishir Kushawaha "If this thread answered your question, please click on "Mark as Answer"

     
  • Wednesday, October 10, 2012 12:04 PM
     
     
    Sign In to Vote
    0

    Changing deployment methods in the misddle of a task sequence can be problematic.  You have to change the value of several MDT properties, such as deployroot, in the task sequence before you shut down so that the system can find the correct path when it boots up on your network.

    The best way might be to create a task sequence in your environment that accomplishes what you want on first boot and just run that.  MDT 2012 will prompt for Name, domain and admin info and you could have a task sequence that runs the Recover from Domain, Restore Groups and Windows Updates task sequence steps.

     
  • Thursday, October 11, 2012 6:10 PM
     
     
    Sign In to Vote
    0

    eschloss:

    I was able to accomplish my question by including LTISuspend and modifying a vbs script to prompt to rename the computer, add domain user to local admins group and reboot.

    Regarding the Post task sequence, I assume as part of the master image I could add a run once as you mention to automatically connect to the network and launch this task, correct?

     
  • Thursday, October 11, 2012 6:23 PM
     
     
    Sign In to Vote
    0

    I've got to just laugh when I see your first post. You're putting in so much hard work, configuring your build, just to send your image off to some outsourcing company who will then charge you for deploying the image that you've created.

    Why don't they figure this out?

    I've seen this before. We received images that were out of date and we had to re-image them even after paying the supplier to do it.

    Save some money and do it yourself. Hire a guy.

    ...

    But after my rant. . .You should just implement MDT with WDS then have (whoever unboxes the machine) and engineer press f12 then leave. MDT can fully automate the process.

    Blog: http://scriptimus.wordpress.com

     
  • Thursday, October 11, 2012 10:43 PM
     
     
    Sign In to Vote
    0

    I agree with Andrew on this one.

    If you're already making use of MDT in order to build your own image, just use it to deploy the image to the machines when you receive them. MDT isn't really supported in this particular scenario. If you really want to pursue this kind of configuration then you could get something like this to work by using either setupcomplete.cmd or runonce regkeys in order to start a one-time script in order to do some additional tasks upon first boot.

    Kind regards,

    Stephan

    If one of these posts answered your question or issue, please click on "Mark as answer".

    My Blog | Twitter: @Schwarz_Stephan | MCTS, MCITP, MCSA, MCC-2011.
    How to configure Windows RE/OEM Recovery Partition with MDT

     
  • Sunday, October 14, 2012 4:41 AM
     
     Proposed
    Sign In to Vote
    1

    MDT does provide a scenario for this, called the "OEM" scenario.  In it, you create USB (or DVD) media with a special "LTI OEM" task sequence on it, as well as the OS task sequence.  You insert that into a machine and run the "LTI OEM" task sequence, which formats and partitions the drive then copies the media to it and sets it up to boot into Windows PE.  At that point, you can remove the drive and send it to the OEM and tell them to put that image in every new machine they ship.  That way, everything you need is already on the hard drive, so no network traffic (other than for domain joining and maybe Windows Update installation) happens at deployment (first power on) time.

    -Michael

    Thanks,
    -Michael Niehaus
    Senior Product Marketing Manager, Windows Deployment
    http://blogs.technet.com/mniehaus
    mniehaus@microsoft.com

    • Proposed As Answer by Paul_Iddon Tuesday, October 16, 2012 2:04 PM
    •  
     
  • Sunday, October 14, 2012 4:43 AM
     
     
    Sign In to Vote
    0

    Oh, two more things:  Never, ever duplicate a drive with an OS that's already gone through the specialization (first boot) process.  Also, never duplicate a drive that has an active task sequence on it, as the task sequence will fail on any machine other than the one it is presently running on.

    Thanks,
    -Michael Niehaus
    Senior Product Marketing Manager, Windows Deployment
    http://blogs.technet.com/mniehaus
    mniehaus@microsoft.com