its awesome. very flexible.
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.
its awesome. very flexible.
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.
to do the network share bit change your bootstrap.ini file to read simlar to below
(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
and burn to cd/dvd
to create an all in dvd goto advanced config, media, new media.
plexer (4th February 2011)
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.
I would assume that you can add another action at the end which would reboot it for you in post os installation.
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.
You could create an AutoIt script which disables/enables the mouse and keyboard?
Effectively you should have something that looks like this:
TimeZoneName=GMT Standard Time
;Variable to set task sequence for installation
;variable to set WSUS location
;Variable to set organisation name on deployment
_SMSTSORGNAME= <Insert School Name Here>
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.
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.
SYNACK (13th March 2011)
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
There are currently 1 users browsing this thread. (0 members and 1 guests)