+ Post New Thread
Page 1 of 2 12 LastLast
Results 1 to 15 of 19
O/S Deployment Thread, Anyone using MDT 2010? in Technical; Just wondering if anyone using MDT 2010 could give me a heads up on what its is like to use ...
  1. #1

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,735
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505

    Anyone using MDT 2010?

    Just wondering if anyone using MDT 2010 could give me a heads up on what its is like to use for both OS and App deployment.

    I currently use FOG to image XP clients and GPOs to install software but MDT looks like it might be more flexible, although more complex to use.

    I am looking to deploy on Server 2008 R2 (without WDS or SCCM) to perform LTIs.

  2. #2

    Join Date
    Mar 2007
    Posts
    1,753
    Thank Post
    79
    Thanked 288 Times in 219 Posts
    Rep Power
    85
    its awesome. very flexible.

  3. #3

    sparkeh's Avatar
    Join Date
    May 2007
    Posts
    6,735
    Thank Post
    1,272
    Thanked 1,645 Times in 1,101 Posts
    Blog Entries
    22
    Rep Power
    505
    Quote Originally Posted by strawberry View Post
    its awesome. very flexible.
    Cool thanks, it does look good.

    Actually looking at it I might integrate it with WDS for network installs.

    Edit: Oh I'm a bit confused, the documentation isn't clear, do you need to run WDS for network installs
    ?

  4. #4

    Join Date
    Mar 2007
    Posts
    1,753
    Thank Post
    79
    Thanked 288 Times in 219 Posts
    Rep Power
    85
    nope, you can run it from a cd/dvd or you can use a dvd/cd to call a network share.

    the only extra wds gives you as i can see is pxe boot and multicast.

  5. Thanks to strawberry from:

    sparkeh (8th January 2010)

  6. #5

    Join Date
    Mar 2007
    Posts
    1,753
    Thank Post
    79
    Thanked 288 Times in 219 Posts
    Rep Power
    85
    to do the network share bit change your bootstrap.ini file to read simlar to below
    [Settings]
    Priority=Default

    [Default]
    DeployRoot=\\pc\DeploymentShare1$

    (right click on deploymentshare, rules, edit bootstrap.ini)
    once you've done this you'll need to update the share
    (right click on deploymentshare, update)
    then find the boot file
    \\pc\deploymentshare\boot\....
    and burn to cd/dvd

    to create an all in dvd goto advanced config, media, new media.

  7. Thanks to strawberry from:

    sparkeh (8th January 2010)

  8. #6
    kearton's Avatar
    Join Date
    May 2007
    Location
    Yorkshire, via NZ ;)
    Posts
    853
    Thank Post
    137
    Thanked 94 Times in 82 Posts
    Rep Power
    43
    Quote Originally Posted by sparkeh View Post
    I am looking to deploy on Server 2008 R2 (without WDS or SCCM) to perform LTIs.
    We're just in the process of setting up MDT 2010 for a probable summer conversion from XP to Windows 7. We aren't using SCCM... currently testing LiteTouch, but have found this article about ZeroTouch without SCCM...
    ZeroTouch for MDT 2010 without SCCM! | IThastobecool.com

  9. Thanks to kearton from:

    plexer (4th February 2011)

  10. #7

    Join Date
    Feb 2007
    Location
    Wolverhampton
    Posts
    330
    Thank Post
    18
    Thanked 35 Times in 33 Posts
    Rep Power
    21
    a second vote to say MDT and WDS are really awesome! The only limitation that I find is thatthe workstations cannot be left in a room to build during atypical school day. This is because as the image finishes, the workstation will automatically logon as the local administrator account, join the domain and finish the lite touch scripts.

    I'm not sure whether this is a configuration item I have overlooked somewhere, but its not an issue as we simply pull the computer out to our build area for imaging.

    This is the reason why I'm looking into SCCM, which will give you zero touch image installation, with imaging in the class that finishes with the ctrl+alt+del screen.

  11. #8


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,579
    Thank Post
    228
    Thanked 853 Times in 732 Posts
    Rep Power
    294
    Quote Originally Posted by deano View Post
    a second vote to say MDT and WDS are really awesome! The only limitation that I find is thatthe workstations cannot be left in a room to build during atypical school day. This is because as the image finishes, the workstation will automatically logon as the local administrator account, join the domain and finish the lite touch scripts.

    I'm not sure whether this is a configuration item I have overlooked somewhere, but its not an issue as we simply pull the computer out to our build area for imaging.

    This is the reason why I'm looking into SCCM, which will give you zero touch image installation, with imaging in the class that finishes with the ctrl+alt+del screen.
    can you just add a script that after a certain time forces a reboot?

  12. #9

    plexer's Avatar
    Join Date
    Dec 2005
    Location
    Norfolk
    Posts
    13,343
    Thank Post
    624
    Thanked 1,584 Times in 1,421 Posts
    Rep Power
    414
    I would assume that you can add another action at the end which would reboot it for you in post os installation.

    Ben

  13. #10
    mhundley's Avatar
    Join Date
    Oct 2007
    Location
    Worcester
    Posts
    47
    Thank Post
    11
    Thanked 8 Times in 7 Posts
    Rep Power
    15
    Quote Originally Posted by deano View Post
    a second vote to say MDT and WDS are really awesome! The only limitation that I find is thatthe workstations cannot be left in a room to build during atypical school day. This is because as the image finishes, the workstation will automatically logon as the local administrator account, join the domain and finish the lite touch scripts.

    I'm not sure whether this is a configuration item I have overlooked somewhere, but its not an issue as we simply pull the computer out to our build area for imaging.
    You could add a command into your task sequence to lock the workstation, we do this to allow app installs and domain join things to occur.

    Insert a commandline into the task sequence using the command "rundll32 user32.dll,LockWorkStation"

    This will lock the machine, however you will have to put additional commands in the task sequence if the machine reboots.

  14. #11


    Join Date
    Feb 2007
    Location
    51.405546, -0.510212
    Posts
    8,765
    Thank Post
    222
    Thanked 2,630 Times in 1,938 Posts
    Rep Power
    779
    You could create an AutoIt script which disables/enables the mouse and keyboard?

    DisableK&M.au3
    Code:
    #NoTrayIcon
    BlockInput(1)
    EnableK&M.au3
    Code:
    #NoTrayIcon
    BlockInput(0)

  15. #12
    Exos's Avatar
    Join Date
    Feb 2011
    Location
    North West
    Posts
    21
    Thank Post
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    8
    Quote Originally Posted by deano View Post
    The only limitation that I find is that the workstations cannot be left in a room to build during atypical school day. This is because as the image finishes, the workstation will automatically logon as the local administrator account, join the domain and finish the lite touch scripts.
    Yes they can, you need to enter a sequence in your customsettings.ini to force a reboot. Under [Default] add FinishAction=RESTART, or alternatively within each of you separate deployment or capture sequences.

    Effectively you should have something that looks like this:


    [Settings]
    Priority=TaskSequenceID, Default
    Properties=MyCustomProperty
    DeployRoot=\\xxx-WDS1\DeploymentShare$

    [Default]
    SkipCapture=YES
    SkipAdminPassword=YES
    SkipProductKey=YES
    SkipDeploymentType=YES
    SkipLocaleSelection=YES
    SkipUserData=Yes
    SkipFinalSummary=YES
    SkipSummary=YES
    SkipDomainMembership=YES
    SkipComputerName=NO
    ComputerName=<xx>-<xx>-<xxxxxx>
    KeyboardLocale=0809:00000809
    UserLocale=en-GB
    InputLocale=0809:00000809
    SystemLocale=en-GB
    UILanguage=en-US
    SkipTimeZone=YES
    TimeZone=85
    TimeZoneName=GMT Standard Time
    FinishAction=RESTART

    ;Variable to set task sequence for installation
    TaskSequenceID=DEPLOY001

    ;variable to set WSUS location
    WSUSServer=http://xx-WSUS01

    ;Variable to set organisation name on deployment
    _SMSTSORGNAME= <Insert School Name Here>

    [DEPLOY001]
    OSInstall=YES
    DeploymentType=NEWCOMPUTER
    JoinDomain=x.x.x
    DomainAdmin=xxxxx
    DomainAdminDomain=xxxx
    DomainAdminPassword=xxxx
    MachineObjectOU=OU=x,OU=x,OU=MDT,DC=x,DC=x,DC=x
    FinishAction=RESTART

    You should also edit the unattend.xml for your sequence to change the login from 999 to 1. The reboot happens within about 30s of the final login to run the scripts. Also make sure when your sequence adds items into the domain you use a container not affected by GP (a quarantine zone) otherwise the GP polices screw with the process.

    With regards to MDT and WDS it can be a bit flaky at times, but on the whole is really good and much better than BDD. WDS is good for your PXE boot environments, which for schools makes building workstations a breeze. Mapping drives and using DVD is completely pointless when this is available. The only interaction within the whole process is to select your image deployment or capture and at the point you enter the asset/device ID. (Thats also assuming you are using a KMS server so no requirement for serial numbers etc, although you can do this within the same process)
    Last edited by Exos; 9th February 2011 at 11:44 PM.

  16. #13

    Join Date
    Mar 2011
    Posts
    3
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0
    You can lock the mouse and keyboard automatically during deployment using batch files. You can also unlock it automatically or manually using the second batch file. Full information found at The Decoder Wheel

    I use MDT2010 for deployment and this method works perfectly.

  17. #14

    Join Date
    Mar 2011
    Posts
    3
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0

  18. Thanks to jhiltabidel from:

    SYNACK (13th March 2011)

  19. #15

    Join Date
    Mar 2011
    Posts
    3
    Thank Post
    0
    Thanked 1 Time in 1 Post
    Rep Power
    0

    Disable the mouse and keyboard while deploying with MDT2010

    I am working on a video training series for MDT2010 (see link below) and will be demonstrating how to automatically disable / enable the mouse and keyboard during deployment so that users cannot interfere with the deployment process!

    MDT2010 Video Training @ The Decoder Wheel

SHARE:
+ Post New Thread
Page 1 of 2 12 LastLast

Similar Threads

  1. [MDT] Deploying XP with MDT 2010
    By plexer in forum O/S Deployment
    Replies: 14
    Last Post: 25th January 2010, 04:23 PM
  2. [WDS] MDT 2010 Windows 7 Flat Image Unattended Install
    By Jon_boy1984 in forum O/S Deployment
    Replies: 12
    Last Post: 18th December 2009, 10:22 AM
  3. [SCCM 2007] Setup SCCM 2007 with MDt 2010 and WDS
    By Gatt in forum O/S Deployment
    Replies: 2
    Last Post: 7th November 2009, 11:19 AM
  4. [MDT] MDT 2010 - Some questions
    By Gatt in forum O/S Deployment
    Replies: 0
    Last Post: 4th November 2009, 10:10 PM
  5. MDT 2010 released
    By PiqueABoo in forum Windows Server 2008
    Replies: 1
    Last Post: 13th September 2009, 06:35 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •