Michael Niehaus' Windows and Office deployment ramblings
As we make plans for the next version of the Microsoft Deployment Toolkit, it would be great if you could provide feedback on what you think about the current version, including:
Feel free to post your comments to this blog entry, or if you would prefer you can e-mail them to me directly at firstname.lastname@example.org. Go ahead, bury me in e-mail - make me regret asking for it :-)
1; It's the best way to deploy Zero Touch images via SMS
2. The driver injection
3. No solution yet to boot unknown clients in SCCM
4. A build-in solution to drop machines directly into SMS\SCCM Collections. Today I do it with own vb scripts, should be nice if GUI exists for this.
5. Today BDD 2.5 with SMS 2003 SP3
We planned to upgrade MDT 2008 with SCCM
6. 2800 machines in 20 months.
60% Windows 2000 SP4
40% Windows XP SP2
Hope this helps...
Reading Michael Niehuas' blog I noticed the post below. So like he said, here's YOUR chance to
Reading Michael Niehuas' blog I noticed the post below. So like he says, here's YOUR chance to
1. Fantastic way to deploy to clients using LTI. Could be completely hands-free depending on configuration.
2. I think the best feature is the ability to create a Windows PE boot image that can kick off the TS process. I do love the task sequencer.
3. Driver organization could be better. Perhaps different windows for different driver types...I dont know if it's possible, but perhaps showing which computer/chipset models it is compatible with.
4. (1). Add a Create Windows RE image.
(2). Integration with WDS...so you can add the image to WDS automatically.
(3). Allow for adding "/flags" after image has been added. Prevents the need for recapturing the image.
Sorry, for some reason, i pressed Submit too soon.
(4). Use powershell scripts instead of VBScripts. Although this might be asking a ton.
(5). LTI with MDT 2008.
(6). Probably 100 machines in 3 months.
Why you are (or aren't) using it
- Prior to BDD 2007, we were using an in-house built system that was based on the idea of BDD which was provided by Microsoft in 2004. Even though our system worked, you and your team managed to make a better product than we did.;)
What you think the best feature is?
- Driver injection (A+)
- Automated image capture
- Automated WinPE generation
- task sequencer, etc.
What you think the worst feature is?
- Reporting failed installs and alerting
- Security (Variables.dat)
- Single instance of MMC access
- Call back support (I want to actually talk to someone at Premier Support that knows what they are talking about, including the weekends!) I have yet to speak to someone whom I didn't have to explain to them that an Operating system needs to be created before a build/TS. My observations show that the only thing the engineer on the other end of the phone has over me is the internal knowledgebase.
What enhancements you would like to see?
- I would like to see an option in the LTI deployment wizard for Roles. This way an installer can choose groups of applications.
- EAPHost included in WinPE so that when we implement port authentication 802.1x we will still be able to deploy without changing our network configuration.
What deployment types you are using (Lite Touch, ConfigMgr, SMS 2003)
Currently, Lite Touch using BDD 2007. Will be moving to SCCM and MDT this fall.
How many machines you have deployed, and what operating system you deployed (XP, Vista, 2003, 2008)
We started our deployment this week, and will be deploying approx 4000 systems.
I look forward to seeing these suggestions in future releases!
I agree with the last comment about reporting failed installs. I think in general, there is a problem with that feature. If the TS crashes, and your not watching it intently, you can't actually easily figure out where it crashed. It would be nice if that final window displayed which step it failed at.