Michael Niehaus' Windows and Office deployment ramblings
If you haven’t already seen the official announcement at http://blogs.technet.com/msdeployment/archive/2009/06/26/microsoft-deployment-toolkit-2010-beta-2-is-now-available-for-download.aspx, the bits are now available for download from http://connect.microsoft.com. (If you need the instructions for how to sign up check out http://blogs.technet.com/msdeployment/archive/2008/12/03/a-new-version-is-coming-soon.aspx.) Please try this out and let us know what you think (the sooner the better – the march to RTM has already begun).
MDT 2010 Beta 2 is a significant change over previous versions (even beta 1), so be sure to check out the release notes and updated documentation.
In the coming days, I’ll start posting more messages about the changes in MDT 2010 Beta 2, from the large obvious ones (folders everywhere, PowerShell support, Windows 7 support) to the much more subtle ones.
It's an excellent tool and the new features are exactly what I've been looking for.
There are a few bugs, but I'm sure those will be taken care of before the final release. Do you know if updates to Beta 2 will be available as issues are fixed?
Sorry if it is wrong place to post the question. Is MDT gives an option to group the applications based on its fucntionality? ie, If I import Office prof, std, enterprise, etc, into MDt store, is there a way to group these applications so that only one application of the same kind can be selected by the user?
Thanks in advance..
MDT does allow you to group applications into bundles, but there is no provision for what I would call "anti-dependencies" (e.g. if one of these is selected, none of the others can be).
Thanks for your reply. I have got another query:
Is there a recommended way to use the litetouch script without connecting to distribution share? I am creating an OS image using litetouch process. But when I deploy the wim image to another computer, distribution share may not be available (in case of remote computer). What is the best way to deal in this case? I need to run few of the post clone scripts as well.
Normally we need the deployment share to be around. However, you can create a media deployment share and then stage that onto the hard drive, even if you aren't using it to deploy an OS - it can just include custom task sequences.