The things that are better left unspoken : Migration & Integration, Product and Manufacturer News

Microsoft Deployment Toolkit 2010 is here!

Sander Berkouwer — Wed, 09 Sep 2009 00:26:20 GMT

One of the reasons I held back on deploying Windows 7 and Windows Server 2008 R2 centrally is the lack of supported deployment solutions from Microsoft. I outlined my deployment checklist here.

One of my major objections, however, just got solved; Microsoft has released the Microsoft Deployment Toolkit (MDT) 2010 solution accelerator version 5.0.1641.0.

Tip:
It won’t be long now for the release of System Center Configuration Manager 2007 R2 Service Pack 2…

About the Microsoft Deployment Toolkit

Using the Microsoft Deployment Toolkit systems administrators can automate Windows desktop and server deployments.

MDT provides you with the following benefits:

Unified tools and processes required for desktop and server deployment in a common deployment console and collection of guidance.
Reduced deployment time and standardized desktop and server images, along with improved security and ongoing configuration management.

A previous version of the MDT exists. It’s called MDT 2008. In the dark ages before MDT the functionality of the tool was divided between the Business Desktop Deployment (BDD) tool and the Automated Deployment Services (ADS).

In short the following versions exist:

Common Name	Version
Business Desktop Deployment 2003	2.5
Business Desktop Deployment 2007	3
Microsoft Deployment Toolkit 2008	4
Microsoft Desployment Toolkit 2010	5

Only MDT 2008 Update 1 is supported next to MDT 2010 from this moment onwards.

Features

Microsoft Deployment Toolkit (MDT) 2010 supports deploying the following operating systems:

Windows 7
Window Server 2008 R2
Windows Vista SP1 and up
Windows Server 2008
Windows XP SP3
Windows Server 2003 R2

New features compared to MDT 2008 Update 1 are:

Windows 7 and Windows Server 2008 R2 support
Support for hierarchical management of items in deployment shares
Support for drag-and-drop, copy-and-paste, and cut-and-paste operations in the Deployment Workbench
Support for automation of management tasks using Windows PowerShell cmdlets.
Improvements in diagnostics output, logging, and network recovery logic.
Support for WAIK 2.0.
Support for USMT 4.0, including hard-link migration and shadow copy.

Positioning

The Microsoft Deployment Toolkit functionality is positioned between Windows Deployment Services (WDS) and the Windows Automated Installation Kit (AIK) on one side and System Center Configuration Manager (SCCM) 2007 R2/R3 on the other side. Both System Center Configuration Manager (SCCM) and MDT actually build on the foundation of WDS, WAIK and ACT to extend their basic functionality. Using MDT in combination with SCCM even unlocks some nice stuff.

The Microsoft Deployment Toolkit solution accelerator is a free download (Gee, another free Microsoft tool, featuring on this blog…) as are the tools (WDS, WAIK, ACT) it extends.

System Center Configuration Manager (SCCM) is a priced solution, that offers more functionality, beyond the Microsoft Deployment Toolkit. The list of functionality is long, but in short System Center Configuration Manager (SCCM) spans the whole lifetime of Windows desktop and Windows Server installations, whereas the Microsoft Deployment Toolkit aids in installing Windows desktops and Windows Servers.

Downloads

Download Microsoft Deployment Toolkit 2010 here.
Download Microsoft Deployment Toolkit 2008 Update 1 here.

Windows 7 Migration Checklist
Deploying Windows 7 with Windows Deployment Services
Business Desktop Deployment 2007 available

Using Service Pack 1 as a marker

Sander Berkouwer — Mon, 22 Jan 2007 12:16:25 GMT

Microsoft today sent an e-mail today to Technology Adaptation Partner (TAP) testers announcing to release ServicePack 1 for Windows Vista in the second half of 2007 (H2 2007) to collide with the launch of Microsoft Windows Server codename "Longhorn". (rumored to be named Windows Server 2007)

As Mary Jo Foley pointed out there are still a lot of businesses waiting to deploy new software products after it gets its first "overhaul". In Microsoft terms this reads ServicePack 1. On the other hand I got to know a couple of guys recently at a Microsoft Partner that aren't interested in Microsoft products anymore after they reach RTM status. Both attitudes have pros and cons.

"We're waiting for the first overhaul"

Waiting for "the first overhaul" is a sensible thought, when you're concerned about the way the product behaves. When a product functions as the cornerstone in your network the impact of misbehaving products might be huge.

I've had some bad experiences with Cisco's PIX OS 7.0 on an ASA 5510 device in combination with Radius and RSA's Authentication Manager 6.0. At the time this was new technology and it wasn't working as it should: Specifying an IP range for different types of group membership within RSA Authentication Manager was a no-go. Several versions of the PIX OS and RSA Authentication Manager (and even a patch recall by RSA) later it finally worked. Overhauling the products in this case was the solution.

Like many I've had some bad experiences with Windows Server 2003 Service Pack 1. Don't get me wrong: I think everyone running Windows Server 2003 should by all means install Service Pack 1! I just also think they should read Knowledge Base articles 898060, 899148 and 899409.

Furthermore the IT business has changed. I guess a lot of administrators for small businesses already have people that use Windows Vista at home (don't ask me where they get it from, I'm as stupefied as you are...) complaining it takes the company a long time to use it too. Your IT manager might be sensitive to these questions, especially when the big boss asks them...

"After RTM it's no fun anymore!"

There is money to be made in the Technology Adaptation Program and the Rapid Development Program:

Customers can benefit by using the newest technology to address their needs, staying ahead of the technology curve and getting considerable licensing discounts. You'd be surprised how many customers really contemplate on joining the programs, despite the apparent drawbacks.
Microsoft Partners can benefit by rapidly building knowledge on the new technology, showing their skills to customers and the Microsoft eco system, gaining valuable Microsoft Partnership competencies, improve their reputation and of course sell their services more easily (because of the discounts).
When a Microsoft Partner participates in one of the programs IT Professionals benefit by learning the new technology and of course gain respect within the community by blogging about it!

In my opinion there's also a risk involved for Microsoft Partners providing access to the Technology Adaptation Program and the Rapid Development Program. They will have to rely on the troubleshooting skills of their technical people to solve or work around even the hardest and most obscure problems. If these people can't "fix" it in a timely fashion the customer might lose his trust in you, walk out on you and damage your reputation, which might eventually get you out of business. If Microsoft can't "fix" it in a timely fashion the customer might even choose non-Microsoft technology next time, which might eventually get Microsoft partners in trouble.

The two guys I've recently got to know told me they're into pre-RTM software only. They're specialized in deployments of these versions and join programs for new versions when a version reaches RTM. They're busy doing 20 Microsoft Exchange Server 2007 and Microsoft Office Sharepoint Server (MOSS) 2007 deployments now and are looking to join the programs for codenames "Nitrogen" and "Centro". You can rest assured the TAP program for Windows Vista Service Pack 1 is on their shortlist too.

The Microsoft Beta Program, the Connect website and MSDN subscriptions are also great repositories for pre-RTM versions of software. If you can't handle risk use these resources. You might not make any money though...

Concluding...

Your environment might be ready for a product while you're not.
A product might be ready for your environment while you don't know about it.

Business Desktop Deployment 2007 available

Sander Berkouwer — Thu, 18 Jan 2007 00:19:00 GMT

This morning I received a much anticipated e-mail stating the Solution Accelerator for Business Desktop Deployment (BDD) 2007 is now available.

What is BDD 2007?

As many of you might have read in my post about Deploying Windows Vista Centrally this tool really makes it easy to deploy hundreds and thousands of Microsoft Windows Clients by providing guidance, tools, scripts and sequencing scenarios.

The Solution Accelerator for Business Desktop Deployment (BDD) 2007 is the successor to BDD 2003, which allowed administrators to deploy Windows XP and Office 2003. These products can still be deployed with BDD 2007.

Where can I find BDD 2007?

There are two main pages of interest:

What's in BDD 2007?

The setup program for the Solution Accelerator for Business Desktop Deployment (BDD) 2007 is only 27,6 MB in size. If you download both the x86 and the x64 version of it you end up with downloading 55 MB of data. Of course size isn't everything, but the last beta I saw was just over 700 MB in size, so there must be something missing... and there is!

Prerequisites

Before you can deploy BDD 2007 you have to manually install the following prerequisites on your server:

Microsoft Windows Installer 3.1
Microsoft .Net Framework 2.0
Microsoft Management Console (MMC) 3.0
Windows Script Host (WSH) 5.6.

The client also needs the Windows Script Host (WSH) 5.6, but requires only Microsoft Core Extensible Markup Language (MSXML) Services 3.0 besides it.

WAIK

The Windows Automated Installation Kit (AIK) was part of the Beta download of the Solution Accelerator for Business Desktop Deployment (BDD) 2007, but you have to manually download and install it in the final release.

Windows Deployment Services

Another thing missing from the final release of the Solution Accelerator for Business Desktop Deployment (BDD) 2007 is Windows Deployment Services (WDS). Windows Deployment Services (WDS) is part of Microsoft Windows Server 2003 ServicePack 2 and part of the Windows Automated Installation Kit (AIK).

Windows PE 2.0

Microsoft Windows Preinstallation Environment is also not part of the download. This isn't a problem if you deploy Windows Vista, because you'll find the *.wim file on the DVD. You will also find this file within the Windows Automated Installation Kit (AIK).

Conclusion

The Solution Accelerator for Business Desktop Deployment (BDD) 2007 is a great tool if you want to deploy Windows Vista in a structured way: It provides tools, scripts, documentation and deployment scenarios and helps you not to overlook certain areas of attention.

You have to still (buy, ) download and install al the deployment tools for your preferred deployment which reduces the Solution Accelerator for Business Desktop Deployment (BDD) 2007 to a mere layer of guidance. At least the download fits on a CD-Rom... Most of the tools are now part of the Windows Automated Installation Kit (AIK) which weighs about a GigaByte.

I recommend the Solution Accelerator for Business Desktop Deployment (BDD) 2007 to everyone that is not very 'into' Windows client deployment and because it's graphical it is most suitable for women.

Don't get stuck with SUS

Sander Berkouwer — Wed, 23 Aug 2006 10:22:00 GMT

As some of you might already have read Microsoft will stop delivering updates to SUS servers on wednesday December 6, 2006 This effectively gives it's administrators exactly six days to get their act together for patch tuesday on December 12, 2006.

The story on Update Services

Version 1.0

Microsoft introduced Software Update Services (SUS) in September 2003 and it has since helped many systems administrators all over the world to update Microsoft Windows 2000, Microsoft Windows Server 2003 and Microsoft Windows XP systems. The tool was positioned as 'the local Windows Update' website.

Version 2.0

On June 6, 2005 Microsoft announced Windows Server Update Services (WSUS) as the successor of SUS after a 8 month evaluation known as Windows Update Services. (WUS) Windows Server Update Services (WSUS) is also known as WSUS 2.0, effectively versioning the original Software Update Services as SUS 1.0. Microsoft WSUS 2.0 solves many problems systems administrators had with Software Update Services (SUS 1.0) like we see with many 'version 2.0' programs:

More features
Better performance
New interface

The biggest improvement on SUS 1.0 in WSUS 2.0 was the ability to update Microsoft Office, Microsoft Exchange, Microsoft SQL and Microsoft Windows Vista (with ServicePack 1 installed)

Version 3.0

On the Microsoft Windows Update Services Home website you can find WSUS 3.0 Beta 2 which is undergoing rigorous testing in an open evaluation, just as WSUS 2.0 did in it's WUS days.

End to SUS 1.0

Microsoft announced an end to Software Update Services (SUS 1.0) when it released Windows Server Update Services (WSUS 2.0) as of June 6, 2006 After that date, no new update content would be delivered to SUS 1.0, effectively rendering it useless. Microsoft later delayed the end-of-life scenario with six months to December 6, 2006 when they found out many organizations were merely in the process of introducing SUS 1.0 instead of enjoying it to the fullest.

Another data in Microsoft's announcement is the end to the download availability of Software Update Services (SUS 1.0) per August 24, 2006. Hery, wait a minute! that's tomorrow!

Migrate to WSUS 2.0 or wait for 3.0?

One of the options systems administrators jave is to upgrade to WSUS 3.0 as soon as it gets released. When testing the product you could use the Beta 2 version, which is available in an open evaluation.

There's a pretty good chance WSUS 3.0 gets released before December 6, 2006. This would not only widen options for administrators still working with Software Update Services (SUS 1.0) but would also make sense in terms of readiness for Microsoft Windows Vista, Microsoft Office 2007 and Microsoft Exchange 2007. On the other hand ýou might get in pretty big problems when your Software Update Services stop working after December 6, WSUS 3.0 isn't available and some scriptkiddie wrote an exploit for a security hole that gets patched on patch tuesday six days later. Furthermore remember Microsoft WSUS 3.0 Beta 2 was released only two weeks ago and WUS was publicly available for almost seven months.

Skipping WSUS 2.0 might prove useful when you already planned to implement your Update Services on Microsoft Windows Server 2003 with ServicePack 1 or Microsoft Windows Server 2003 R2. When you want to keep using your existing Windows 2000 Server for updating your clients then I suggest you upgrade to Windows Server Update Services (WSUS 2.0)

Conclusion

Be quick to download Software Update Services (SUS 1.0) when you want to implement it to use it for the next three months or to complement your IT collection to show your grandchildren referring to those crazy years when products needed security fixes.

Get ready to upgrade to Windows Server Update Services when you're already enjoying the joy of completely patched networks and want to keep it that way when Microsoft denies your SUS server access to new updates. Depending on the availability of WSUS 3.0 you might choose to upgrade to it before that date.

The things that are better left unspoken : Migration & Integration, Product and Manufacturer News

Microsoft Deployment Toolkit 2010 is here!

About the Microsoft Deployment Toolkit

Features

Positioning

Downloads

Related posts

Further reading

Using Service Pack 1 as a marker

"We're waiting for the first overhaul"

"After RTM it's no fun anymore!"

Concluding...

Business Desktop Deployment 2007 available

What is BDD 2007?

Where can I find BDD 2007?

What's in BDD 2007?

Prerequisites

WAIK

Windows Deployment Services

Windows PE 2.0

Conclusion

Don't get stuck with SUS

The story on Update Services

Version 1.0

Version 2.0

Version 3.0

End to SUS 1.0

Migrate to WSUS 2.0 or wait for 3.0?

Conclusion

Further reading