O/S Deployment Thread, It works! in Technical; Finally got MDT 2010 to play nicely and will install a variety of apps with no user interaction!
This includes ...
12th July 2010, 09:56 PM #1
Finally got MDT 2010 to play nicely and will install a variety of apps with no user interaction!
This includes AutoIT scripts and even SIMS.net!!
Time to start creating MSI and AutoIT wrappers for a bunch of apps now!
12th July 2010, 10:19 PM #2
Can you elaborate on the context - do you mean install a variety of apps with no user interaction immediately post-OS installation (or something else)?
Finally got MDT
2010 to play nicely and will install a variety of apps with no user interaction!
PS: You do know about the recent MDT 2010 Update 1 don't you? I've been playing, but fortunately the claim in the release docs about "Removed Features: None" appears to be correct and so far things that used to, still work.
13th July 2010, 10:24 AM #3
Ooh, sounds exciting! Let us know what you have managed to install. We are looking at moving to Windows 7 on clients and are having a few issues with fog so would like to find alternative methods.
13th July 2010, 10:28 AM #4
- Rep Power
13th July 2010, 10:30 AM #5
here's the list of stuff so far:
Windows 7 (Duh!)
Expression Studio 3
McAfee VirusScan Enterprise 8.7i
Fireworks MX (via AutoIT)
Password Control 2.4
Custom MSI - Win7 Lgon Background, Bulletin Display Softwre, Poweroff, USBDLM
13th July 2010, 01:50 PM #6
I am not liking the way LiteTouchPE_x86.wim keeps getting bigger and bigger the more drivers i add, and the fact its a boot image, so have to wait ages on machines for it to load the whole WIM and its only going to get longer. Why is there not a smaller Boot WIM to get it started first then pull down the larger image once you have clicked buttons.
13th July 2010, 07:05 PM #7
It would, but why do you need to keep adding drivers? WinPE3 is the Win7 version and because that is relatively recent and has lots of driver support in it by default I've rarely had to add any drivers - and then all you should normally need to add is a NIC and/or mass storage driver.
LiteTouchPE_x86.wim keeps getting bigger and bigger the more drivers i add
13th July 2010, 07:13 PM #8
got it to deploy a vanilla image of xp/win7 havnt tried apps yet just drivers. anyone found a way of adding windows updates into it as without them with xp needing 90 aftter install wds still seems the way to go
13th July 2010, 07:32 PM #9
Not as yet, because it interferes with Application installation - I have to disable the WU Service until the apps are installed...
If we could slipstream the updates in with the install it would be perfect..
13th July 2010, 07:42 PM #10
I do an offline install using the logistix update packs saves having to connect to anything else.
This is the last thing that is done when an os is deployed.
13th July 2010, 07:55 PM #11
any more info on how to do that
Originally Posted by plexer
13th July 2010, 08:09 PM #12
I use nLite to slipstream both SP3 and the latest xable SP3 update pack into the XP source before importing the OS into MDT. Having done that every now and again I slipstream new xable updates into the MDT distribution share copy of XP.
I don't sysprep, capture and deploy XP images i.e. all XP builds copy down that updated XP source which MDT installs the old fashioned way, then adds apps (workstation locked), joins the domain (OU is selected in the few remaining pages I haven't nuked from the initial MDT deployment wizard), reboots which gets policy including WSUS => done.
For Win7 you've got the MDT packages feature which works with CABs or **MSUs**.
Last edited by PiqueABoo; 13th July 2010 at 08:12 PM.
13th July 2010, 08:13 PM #13
while its been mentioned how do you get mdt to put it in the right ou do you have to type cn=blah,dc=blah,dc=local as typing in the ou name diddnt seem to work for me but ive not had much time on it yet
ive had issues in the past using nlite for adding updates with system verification checker going nuts on just about every file possible rendering installs useless
13th July 2010, 09:36 PM #14
I statically pre-populate the deployment wizard's OU drop-down via entries in bootstrap.ini e.g.
how do you get mdt
to put it in the right ou
I did contemplate dynamically grabbing them from AD at deploy-time but WinPE didn't (easily) have the traditional APIs for talking to AD.. not sure if that's changed.
14th July 2010, 08:23 AM #15
An easy way to fix that would be to use selection profiles. These would prevent unnecessary drivers from being added to your LiteTouchPE_x86.wim and keep it as small as possible. As PiqueABoo mentioned, you only really need NIC and MSD drivers for the boot image (to enable it to connect to your deployment share).
Originally Posted by Quackers
By Butuz in forum Thin Client and Virtual Machines
Last Post: 6th August 2009, 10:35 PM
By free870 in forum Windows
Last Post: 3rd April 2009, 01:59 PM
By mrforgetful in forum Windows
Last Post: 13th August 2008, 02:44 PM
By dhicks in forum Thin Client and Virtual Machines
Last Post: 2nd July 2008, 11:36 AM
By kurtz05 in forum Educational Software
Last Post: 27th November 2007, 08:42 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)