1 / 18

Business Desktop Deployment: Roadmap and Futures

Business Desktop Deployment: Roadmap and Futures. Michael Niehaus Senior Software Development Engineer Microsoft. BDD 2007: History. Released in January 2007 Already over 150,000 downloads Several case studies have been posted Source code released in April 2007 To be updated shortly

ken
Download Presentation

Business Desktop Deployment: Roadmap and Futures

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Business Desktop Deployment:Roadmap and Futures Michael Niehaus Senior Software Development Engineer Microsoft

  2. BDD 2007: History • Released in January 2007 • Already over 150,000 downloads • Several case studies have been posted • Source code released in April 2007 • To be updated shortly • Patch 1 released in June 2007 • Details on what was fixed can be found in http://support.microsoft.com/?id=937191 • See http://blogs.technet.com/mniehaus/ for more information • No additional patches planned, unless required • Escalations through Microsoft Support • Yes, full support is available, including hotfixes!

  3. BDD 2007: The Future • New versions are to be delivered in “waves” • Deployment “4” – Current wave, development underway • Deployment “5” – Work beginning later in 2008 • Beyond… • Multiple releases within each wave • Corresponding to major product releases • Naming is still in flux • Potentially one package with multiple payloads • Until names are firmly established, expect to see references to Deployment “4”, BDD 2008, Windows Server Deployment, etc.

  4. Deployment "4" Scope • Continue to support all existing technologies • SMS 2003 OS Deployment Feature Pack • Windows XP • Windows Vista • Windows Deployment Services • Provide a simple path for upwards migration • BDD 2007 Lite Touch to Deployment “4” Lite Touch • BDD 2007 Lite Touch to Deployment “4” Zero Touch (SCCM) • BDD 2007 Zero Touch to Deployment “4” Zero Touch (SCCM)

  5. Deployment “4” Scope • Expand into server deployment • Windows Server 2003 and Windows Server 2008 • Hardware configuration • Advanced disk configuration • Static IP support • Operating system role installation and configuration • Server product installation (hydration)

  6. Deployment “4” Scope • Integrate with System Center Configuration Manager 2007 • Integrated experience • One administrative interface: the SCCM MMC • Extensions for Deployment “4” added functionality • New wizards, actions, nodes • “Workbench”-less • Full SCCM alignment • Same task sequence-based methodology, task sequence engine for Lite Touch and SCCM • Lite Touch and SCCM will strive to do things the same way • Migration from Lite Touch to SCCM + Zero Touch will be a wizard-drive process • Support for combining Zero Touch and SCCM data sources for data-driven deployments

  7. Deployment “4” Scope • Integrate with System Center Configuration Manager 2007 • Support “mix and match” • Don’t require implementing all of WSD if you just want to use some small pieces of it • Custom actions can be used without the other components • Images created by Deployment “4”, SCCM, and Windows Deployment Services (WDS) should be fully interchangeable • No hooks in the images

  8. Deployment “4” Scope • Integrate with System Center Configuration Manager 2007 • Provide pre-built task sequence samples • Fully configured task sequences for complete end-to-end deployment process • Similar to what we have today for Lite Touch • Designed to show how to have a single task sequence support multiple scenarios, and how to integrate all tools into the task sequence • Task sequence “snippets” • Partial task sequences, e.g. a 10-step process to install a product • Wizards to assembly together “snippets” into useful, complete task sequences

  9. Deployment "4" Scope • Enhanced data-driven deployments • Support multiple data sources • SCCM collection variables • SCCM computer variables • BDD rules-based processing • Database • Web service calls • Static configuration via CustomSettings.ini • Use the data to determine what needs to be done • Instead of creating multiple configurations or task sequences, decide what to do on the fly • Leverage WMI and other local information • Based on computer location, make, model, role, etc.

  10. Deployment “4” Scope • Simplify, streamline, enhance • New documentation structure: CHM-based • More checklists, step-by-step guides, troubleshooting • Leverage new technologies • Multicast capabilities from Windows Deployment Services in Windows Server 2008 • Management pack for System Center Operations Manager 2007

  11. Deployment “4” Timeline Q4 2007 H1 2008 Q32007 Now Beta version to TAP customers only Lite Touch only Windows Server 2008 and Windows Server 2003 support Minor changes from current functionality Initial SCCM 2007 support Client and server OS support Architectural changes to align with SCCM 2007 First release! Support for Windows XP, Windows Vista, Windows Server 2003 deployment Beta support for Windows Server 2008 Second and third releases! Full support for Windows Server 2008 RTM Support for upcoming SCCM 2007 service pack

  12. Deployment "4": The Tools BDD Methodology and Best Practices Guidance SCCM 2007 will offer great improvements All may be needed to cover required scenarios. BDD ZTI SCCM 2007 OSD BDD ZTI Tools SMS 2003 OSD BDD LTI WDS and WAIK tools Good Better Best

  13. Features not in SCCM • Rules-based deployment process (CustomSettings.ini and database access) • Dynamically deciding where to save user state • Offline patching • Generalized ability to update unattend.xml, unattend.txt, sysprep.inf during the deployment • Capture and restore security groups • Install language packs • Potentially a few more…

  14. Features to add to SCCM • Provide new task sequence actions to extend the core set of 28 provided with SCCM • Operating system role installation and configuration • Active Directory, DHCP, DNS, IIS, File & Print, WINS, etc. • PowerShell and other components • Hardware configuration • Array controller configuration, BIOS configuration, management processor configuration • iSCSI, SAN attachment • Server product installation and configuration • As many as we can • Other miscellaneous • IPv6 configuration, “Run command line as”, send status messages, simple semaphore support, etc.

  15. SCCM 2007 Built-in Actions • Run Command Line • Install Software • Install Software Updates • Join Domain or Workgroup • Connect to Network Folder • Reboot Computer to Windows PE or hard disk • Set Task Sequence Variable • Format and Partition Disk • Convert Disk to Dynamic • Enable BitLocker • Disable BitLocker • Request State Store • Capture User State • Restore User State • Release State Store • Apply Operating System • Apply Data Image • Setup Windows and ConfigMgr • Install Deployment Tools • Prepare ConfigMgr Client for Capture • Prepare Windows for Capture • Capture Operating System Images • Auto Apply Drivers • Apply Driver Package • Capture Network Settings • Capture Windows Settings • Apply Network Settings • Apply Windows Settings

  16. Deployment "5" Ideas • Continue to expand in knowledge • Support installation of more Microsoft client and server products • More hardware configuration functionality • Integrate with System Center Service Manager • End-to-end deployment workflows • Complete server lifecycle support • Continue to simplify, streamline, enhance • Shift towards model-based deployment, the Dynamic Systems Initiative vision

  17. Q&A

  18. © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions,it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

More Related