What is Deployment 4?
Deployment 4 combines the guidance and toolset from previous releases of Business Desktop Deployment and Beta releases of Windows Server Deployment. This release continues to support Zero Touch Installation of desktop operating systems using Systems Management Server 2003 with the Operating System Deployment Feature Pack and adds new deployment and task sequencing capabilities for desktops and servers using System Center Configuration Manager 2007. Deployment 4 also continues to provide Lite Touch Installation support without infrastructure requirements and adds capabilities for Windows Server 2003 and pre-release versions of Windows Server 2008.
Deployment 4 is available at the Microsoft Deployment Connection (http://connect.microsoft.com).
What applications and operating systems can I deploy using Deployment 4?
Deployment 4 will deploy pre-release versions of Windows Server 2008, Windows Server 2003, Windows XP SP2, Windows Vista, and the 2007 Microsoft Office system using a variety of Microsoft tools and custom scripts.
Can I use Deployment 4 to deploy pre-release versions of Windows Server 2008?
Yes. Deployment 4 is part of the Windows Server 2008 Beta and TAP Programs. It is also available as an open beta download.
Where do I find Deployment 4?
Deployment 4 is currently an open program on Microsoft Connect. To join the Deployment 4 Beta 3 program, follow these steps:
If you have not previously registered with Microsoft Connect, you might be required to register before you continue with the invitation process.
If the link in step 1 does not work for you, copy the full link and paste it into the Web browser address bar.
What new features does Deployment 4 contain?
Microsoft System Center Configuration Manager 2007 support, with the following features:
Lite Touch Installation support for Windows Server 2008:
Lite Touch Installation enhancements:
Lite Touch Installation multicast support:
What is the difference between Deployment 4 Lite Touch Installation and Zero Touch Installation?
Deployment 4 has been updated from Business Desktop Deployment 2007. As with previous releases, Lite Touch Installation requires a minimum set of tools and assumes that the environment does not have systems management utilities, directory services, or deployment servers in place. The highly automated Zero Touch Installation requires Microsoft System Center Configuration Manager 2007 or Microsoft System Management Server 2003 and Microsoft Active Directory® environment for deployment. Deployment 4’s Lite Touch Installation has been updated to share most of the configuration process with Zero Touch Installation. The unified architecture makes it easier to implement both Zero Touch Installation and Lite Touch Installation together if desired, depending on the breadth of tools available in the environment.
What does Deployment 4 include?
Deployment 4 provides the assets required to deliver Windows Vista and the 2007 Microsoft Office system to the corporate desktop.
Included Tools and Related Guidance
Technical Solution Guidance
Sample and Job Aid Documents
Which organizations will benefit from Deployment 4?
Deployment 4 offers a solution targeted to all corporate customers who have 25 or more networked PCs using Microsoft desktops and/or servers who need a high level of operational excellence and scalability. Deployment 4 is especially useful for organizations with varied network and systems management infrastructure. Organizations with low bandwidth or disconnected branch offices or remote users can also benefit from new capabilities in Deployment 4 to create stand-alone media initiated operating system deployments.
Which operating system migrations does Deployment 4 provide guidance for?
Deployment 4 can be used to manage desktop migrations of Windows 2000 and later operating systems to Windows Vista. Deployment 4 also provides functionality for migrating Windows 2000 to Windows XP with Service Pack 2.
How does the workflow process ensure smooth deployment?
The Deployment 4 process is based on Microsoft Solutions Framework (MSF). MSF delivers proven practices for planning, building, and deploying a variety of technology solutions. It combines aspects of software design and development plus infrastructure design and deployment into a single project life cycle. With MSF, organizations can achieve the right balance of flexibility while meeting their commitments, as well as achieve speed while minimizing their risks.
Does Deployment 4 make it easier for implementers to get to technical content?
Deployment 4 has contains feature team guides in two sections: guidance for project management and guidance for feature team technical implementers. The Deployment Workbench MMC application has document navigation features built into the tool.
How does Deployment 4 address the biggest obstacles in deployment?
Microsoft conducted extensive research to prioritize the top “deployment blockers” that prevent efficient migration and designed Deployment 4 to address these:
· Application compatibility
· Office documentation migration
· User state migration
· Automation of deployment
· Desktop Imaging
Which technologies are being applied in Deployment 4?
Deployment 4 is based on deployment tools from Microsoft, as well as custom scripts.
· Hardware and software Inventory—Application Compatibility Analyzer, Microsoft SQL Server™/Microsoft SQL Server™ 2000 Desktop Engine, Microsoft Office Access
· Application Compatibility Testing and Remediation—Application Compatibility Toolkit 5.0, Microsoft Virtual PC 2004
· Core Application Packaging—Office Professional Edition 2007, the Microsoft Office Resource Kit
· Imaging—ImageX, System Image Manager, Microsoft Windows Preinstallation Environment 2.0 (Windows PE 2.0), Sysprep, Deployment Workbench
· Project Management—Microsoft Project 2003
· Application Packaging—Customer choice
· Volume Activation 2.0 – New methods of activation
· User Data and Settings—User State Migration Tool 3.0
· Deployment Process—Windows PE 2.0, Sysprep, Windows Deployment Services, Deployment 4 Deployment Wizard
· BitLocker™ drive encryption support for Lite Touch Install scenarios
Are there technology constraints to Deployment 4?
By design, there are very few. With Deployment 4, Microsoft does not assume that any network management system or specific deployment servers already exist within the organization.
Will desktop users lose all data and settings that they currently have on their computers?
No. Deployment 4 provides detailed, best-practice guidance about user state migration for desktops and employs the User State Migration Tool 3.0.1 to migrate the desired settings and attributes to the new desktop.
Does Deployment 4 support Windows XP Professional with Service Pack 2 and Windows Server 2003 installations?
Yes. Deployment 4 supports Windows XP SP2, Windows Vista and Windows Server 2003 operating system installations.
How do I get Windows PE 2.0?
Windows PE 2.0 is available as part of the Windows Vista and Windows Server 2008 operating systems (boot.wim). It is also available separately in the Windows Automated Installation Kit (Windows AIK), which includes Windows PE for each platform (ia64, x64, x86) and tools to customize it using Windows System Image Manager and Windows Deployment Services. Deployment 4 downloads the Windows AIK from the Deployment Workbench.
What tools are used in the Deployment 4 accelerator for imaging?
Deployment 4 delivers a feature-rich MMC console, Deployment Workbench, which is built on Windows Vista deployment tools including: ImageX, Windows System Image Manager, Windows PE 2.0, and Windows Deployment Services. Deployment 4 also uses Configuration Manager 2007’s stand-alone media initiated operating system deployment feature as well as System Management Server 2003 OS Deployment Feature Pack OS Image package contents and image management.
Does Deployment 4 address security policies necessary for desktop and server hardware?
Deployment 4 helps companies understand how security policies affect the design of operating system images and also discuss strategies for hardening of desktops and servers. However, Deployment 4 is not intended to replace specific security solutions. In parallel with Deployment 4, the Windows Vista Security Guide and Windows Server 2003 Security Guide is available on Microsoft TechNet and available from the Microsoft Download Center. Future Deployment accelerator releases will integrate the 2007 Office Security Guide and the Windows Server 2008 Security Guide.
Can Deployment 4 be tailored to fit a company’s specific project-management methodology?
Yes. Microsoft Solutions Framework (MSF) is a life-cycle model that addresses a number of disciplines, including project management, so good project-management methodology can be used in conjunction with the solution. The solution can even be adapted to operate within a different life-cycle methodology. Although the phases, tasks, and milestones are specific to MSF, the process is generic. Any analyst with a basic knowledge of MSF and the target methodology should be able to adapt Deployment 4 to fit into any project-management methodology.
Who should use Deployment 4 and how much does it cost?
Deployment 4 is freely available to customers and partners to use in planning and testing their operating system migration and deployment projects for pre-release versions of Windows Server 2008, Windows Server 2003, Windows Vista, Windows XP SP2, and the 2007 Microsoft Office System. Deployment 4 is available at the Microsoft Deployment Connection (http://connect.microsoft.com).