Windows Server Longhorn Beta 1
Transcription
Windows Server Longhorn Beta 1
Windows Customer Feedback Systems: Technical Overview for SoCal IT Professionals April 2007 Ashish Parikh- Senior Lead Program Manager Microsoft Corporation Olga Ivanova-Program Manager Microsoft Corporation Agenda Windows Longhorn Server Roadmap Customer Focused Design Automated Feedback Mechanisms Live Demo of Longhorn Server Longhorn Server Component WMI Provider How can IT Pros get involved & help? Q&A… Release Roadmap 2009 2007 2006 2005 Windows Server LH R2 ►Windows Server Longhorn ►2H/2007 RTM ►1H/2007 Beta 3 ►Windows Server 2003 Compute Cluster Edition ►Windows Server Longhorn ►Q2/2006 Beta2 ►Q4/2006 IDS-1 ►Windows ►Windows ►Windows ►Windows ►Windows Server 2003 R2 Server Longhorn Beta 1 Server Update Services Server 2003 x64 Editions Server 2003 Service Pack 1 Windows Longhorn Server Key Investments Manageability from the ground up Role-based deployment reduces maintenance and attack surface Server Manager Tool for easy configuration Enhanced PC and server deployment and management Next generation Web Services Application platform Integrated management of IIS, ASP.NET & “Indigo” Focus on shared usage and hosting scenarios Enhanced fundamentals, including security IPV6 aware roles, App Compatibility with Windows Server 2003 New hardware and standards support Dynamic partitioning for Windows “mainframes”, Diskless blades support, PCI-Express Server Core Install Option Powershell integration Broad Customer Feedback – Reducing Signal to Noise Ratio Area Verbatim Product Feedback Today Many sites and methods Each its own “destination” with no connection to other sites or products Often no response Often aligned with “programs” and disappear when the program ends Tomorrow Consolidate Automated Product Feedback Windows Content Error Reporting (e.g. Watson) Requires auth to send for each error Reports on the binary that crashed No context WER, CEIP, Reliability Analysis Consolidated opt-in Ecosystem knowledge of crash Richer data – how and why things aren’t working Help Help ships “in-box” Quick search and retrieval, but… Content is stale at RTM Rapidly loses relevance -> people routinely go to the web for help sites into connect.microsoft.com Destination as well as integrated with products Contextualized In-process Full lifecycle Transparency is dynamic Some Help still ships in-box Augmented automatically from online repository Customers rate content, MS quickly updates Maintains offline story for disconnected servers Build the Right Product First Time Customer Focused Design Customer Requirements Development Critical to Quality Release Criteria Product Lifecycle Start Customers Interacting with customers early in your project Establishing Critical to Quality Release Criteria Validating with customers along the way End Need for Windows Error Reporting Goal: to surface and fix problems most frequently encountered by Server customers WER Curve: Worst 20% of the defects = 80% of the failures We need WER reports from you to identify and fix these problems! Unique Problems Longhorn Server Customer Experience Improvement Program (CEIP) BASICS… If you opt-in to CEIP it sends basic information about your Server machine to Microsoft CEIP Information: Hardware/Performance/Reliability/Program Usage CEIP reports do not contain any personal identifiable information We do not use this information for marketing or promotional purposes ADMINISTRATIVE DETAILS… A single opt-in consent Group Policy, Unattend, & Sysprep is also supported You can opt out anytime Virtually undetectable performance hit No security exposure HTTP/HTTPS POST (SSL if available) Examples of Typical CEIP Business Questions Asked… Generic Question: Specific Question: Product, memory size, number of CPUs What Server roles are installed? File Replication Service (FRS) UI: How many replication groups are managed? How often is Cancel used in wizards? Goals: scalability testing and better Wizard help. Examples of decisions taken from pre-release feedback: Added time zone to the Server welcome screen We used “Roles most frequently installed together” to prioritize testing of roles together Demos: Consent WER Mechanism for CEIP & WER Service Crash Experience New Longhorn Server WMI Provider Introducing: A New WMI Server Provider WMI DETAILS… Developed by request from customers to show Roles Data collected through CEIP (IT Pros & MVPs) Enables enumeration of Server Roles, Services, & Features Available in Longhorn Server starting in IDS-1 release Will deliver documentation & samples on MSDN & SDK BENEFITS TO SERVER ADMINISTRATORS… Allows the Server admin to have an additional means of managing systems Enables the Server admin a way of specific targeting of patches and installs Provides support through WMI for the enumeration of all installed inbox server roles & optional components Join the feedback loop! Go to http://connect.microsoft.com Choose to participate in: Server Feedback Systems (Longhorn Server Customer Outreach) Invitation ID: SCUG-D876-4V97 Survey Presentation Slides Connect Web Site Improvement Available connections/programs Appendix Out Of Box Experience-Initial Configuration Unified Opt-In User Experience Windows Update Windows Error Reporting Customer Experience Improvement Program CEIP Discovery Mechanism In Server Manager Server Manager Tool Single experience for configuring Server Portal for management operations WER Discovery Mechanism In Server Manager Problem Reports & Solutions Console View Displays problems Check for solutions Configure settings Windows Error Reporting Experience In Longhorn 3) “User sends more information to Microsoft” 2) “WER prompts user that service stopped & there is a problem” 1) WER is set to “Ask Me About Sending Reports” Raffle/Gift give away © 2006 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.