sparkeh Posted January 8, 2010 Posted January 8, 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.
sparkeh Posted January 8, 2010 Author Posted January 8, 2010 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 ?
strawberry Posted January 8, 2010 Posted January 8, 2010 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. 1
strawberry Posted January 8, 2010 Posted January 8, 2010 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. 1
kearton Posted February 3, 2011 Posted February 3, 2011 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 1
deano Posted February 4, 2011 Posted February 4, 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.
sted Posted February 4, 2011 Posted February 4, 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. can you just add a script that after a certain time forces a reboot?
plexer Posted February 4, 2011 Posted February 4, 2011 I would assume that you can add another action at the end which would reboot it for you in post os installation. Ben
mhundley Posted February 4, 2011 Posted February 4, 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. 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.
Arthur Posted February 4, 2011 Posted February 4, 2011 You could create an AutoIt script which disables/enables the mouse and keyboard? DisableK&M.au3 #NoTrayIcon BlockInput(1) EnableK&M.au3 #NoTrayIcon BlockInput(0)
Exos Posted February 9, 2011 Posted February 9, 2011 (edited) 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=-- 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= [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) Edited February 9, 2011 by Exos
jhiltabidel Posted March 13, 2011 Posted March 13, 2011 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.
jhiltabidel Posted March 13, 2011 Posted March 13, 2011 The Decoder Wheel post being here: Disable Mouse and Keyboard during deployment [success] @ The Decoder Wheel 1
jhiltabidel Posted May 3, 2011 Posted May 3, 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
karlr Posted May 5, 2011 Posted May 5, 2011 We've just started using MDT in production. It can take some fine tuning, but works really well when you've got it set up. What we're deploying now is essentially a "thin" image of Xp (plain install with just updates), and then using the MDT windows update functionality to ensure the system and apps are fully up to date (actually had to do a slight tweak and run both Pre and Post application install updates twice to get it to really install all updates that were applicable...ZTIWindowsUpdate flags a lot of updates as installed when they're not really... In terms of installing applications, if you can install it properly using a single command then it should work fine on MDT, so you should be set as far as MSIs or well known installers go. In the worst case scenario you could create a standalone AutoIt script that launches and clicks through an installation wizard... Having MDT hooked up to a database is a must have if you're looking for unattended installations to multiple different computer types. We've simply added a room full of computers using their MAC addresses as their identifier, and assigned them to a role specific to that room. The role picks up the OS, drivers, and applications specific for the room/hardware. Using WDS (a CD/USB would work just as well, but would be more painful), all it then takes is pressing the network boot key on the computer, and we're done with it. 1h 30m later the computer will shutdown and be ready for use the next time someone turns it on. For reference, we're deploying the following software to this particular room off the top of head: AVG 2011 Business Adobe Creative Suite CS3 Web Standard Adobe Reader X Adobe Flash Player Adobe Shockwave Adobe AIR Java JRE Microsoft Office 2003 Professional (with 2010 Pro Plus ready to go) Codec Packs Office 2007/works file conversion packs Note that Office 2003 and components get updated to SP3 and updates applied as part of the MDT update process. The only real caveats I've come across so far are the fact that a computer will require deleting and re-prestaging (or moving) in Active Directory as certain Group Policies can break MDT's automation, and the fact that systems in the middle of deployment are vulnerable to people sitting down in front of them and getting access to stuff they shouldn't be or just breaking the process (as people are trying to mitigate throughout this thread). I have managed to get the process working without using Domain Admin Credentials however, which lsessons the security implications somewhat (special accounts have been set up to access the DeploymentShare and join computers to the domain). Might look into writing an app that both locks the workstation and executes some UI in the WinLogon session so our energy efficient teachers don't then turn the computer off... I'm guessing there will still be a brief window between logon and the lock taking effect however.
garethEds Posted May 19, 2011 Posted May 19, 2011 (edited) 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. Don't forget this book: Deployment Fundamentals - Volume 1 Migrating to Windows 7 using MDT 2010 Lite Touch and WDS eBook: Johan Arwidmark, Mikael Nystrom: Amazon.co.uk: Kindle Store I posted about it the other year. At the time it was only available through Amazon.com - but I ordered it and it arrived. I'm currently working through it. My Windows 7 development in school has taken setback after setback (see my blogs) - but this time it is going to happen. Rather annoyingly they have recently updated the book to include chapters on Windows XP with MDT2010 GJE Edited May 19, 2011 by garethedmondson
Arthur Posted May 19, 2011 Posted May 19, 2011 Another good book is Mastering Windows 7 Deployment by Aidan Finn et al. Johan Arwidmark and Mikael Nystrom contributed to it too. Like Gareth, I also bought Deployment Fundamentals from Amazon.com on release, but if I had to choose between the two I would pick Mastering Windows 7 Deployment. Personally, I found it explained things better and in more detail, and it covers topics which Deployment Fundamentals doesn't (SCCM, KMS, Office 2010 etc.)
garethEds Posted May 20, 2011 Posted May 20, 2011 Another good book is Mastering Windows 7 Deployment by Aidan Finn et al. Johan Arwidmark and Mikael Nystrom contributed to it too. Like Gareth, I also bought Deployment Fundamentals from Amazon.com on release, but if I had to choose between the two I would pick Mastering Windows 7 Deployment. Personally, I found it explained things better and in more detail, and it covers topics which Deployment Fundamentals doesn't (SCCM, KMS, Office 2010 etc.) Just ordered the second one now from Computer Manuals. Great success with Windows 7 and MDT2010 today. Very happy with it - the basics all done. Now for research into extending it. KMS and MAK keys next for us. Gareth
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now