Win7 Itpro Session 1 Windows 7 And The Optimized Desktop V20
•Download as PPTX, PDF•
1 like•802 views
Windows 7 Launch slides
Recommended
More Related Content
Viewers also liked
Viewers also liked (18)
More from john weston
Win7 Itpro Session 1 Windows 7 And The Optimized Desktop V20
- 1. Windows® 7 for the Optimized Desktop John weston Microsoft jweston@microsoft.com
- 2. Windows 7: Works the Way You Want Windows 7 for the Enterprise The Windows Optimized Desktop Agenda
- 3. The Making of Windows 7 video
- 5. Windows 7: Works the Way You Want Design Fundamentals Faster, more reliable
- 7. Built-in troubleshooters“Overall, I’m impressed with how reliable this Windows release has been.” —Ed Bott, ZDNet
- 8. Windows 7: Works the Way You WantDesign Fundamentals Faster, more reliable More secure
- 10. Windows 7: Works the Way You WantDesign Fundamentals Faster, more reliable More compatible More secure
- 12. Windows 7: Works the Way You WantDesign Fundamentals Faster, more reliable More compatible Easy to use More secure
- 14. Windows 7: Easy to Use demo
- 16. Keep PCs running
- 17. Virtualization
- 18. At their desk
- 19. In a branch
- 20. On the road
- 21. Protect data & PCs
- 23. BranchCache™ : Users in branch office wait less to download files across WAN.
- 24. Search Federation: Consistent experience to find documents on the PC or SharePoint.
- 26. Enterprise Desktop Virtualization (MEDV) enables compatibility of older applications on a modern desktop.Office Home Search Federation BranchCache™ DirectAccess
- 27. Make People Productive Anywhere Search Federation demo
- 29. BitLocker: Improved in Windows 7 to simplify setup by automatically creating parturitions.
- 30. AppLocker™: Application control to specify what software is allowed to run on user PCs
- 32. Advanced Group Policy Management provides greater flexibility & control over Group Policy. + Fundamentally Secure Platform BitLocker To Go AppLocker
- 33. Enhanced Security and Control User Account Control demo
- 35. PowerShell™ 2.0: With graphical editor, easier to automate repetitive tasks.
- 36. Troubleshooting Platform: Diagnose and resolve issues with built-in or IT-created troubleshooters e.g. Problem Step Recorder
- 38. Desktop Error Monitoring let’s you spot potential support issues early so you can take action. Windows Troubleshooting Platform Deployment and App Compatibility Tools PowerShell 2.0 VDI Enhancements
- 40. Improved security and remote execution capability
- 41. Easier to extend and manage across the enterprise
- 42. Automate Group Policy Object Management
- 43. Configuration of registry-based Group Policy settings
- 44. Automate tasks easily with PowerShell
- 45. Learn scripting easier with graphical interface
- 46. Quickly configure settings or run tasks in real-time
- 47. Frequent request for richer Group Policy management
- 48. Reduces time and risk of error
- 50. Out of the box diagnostics built using Windows PowerShell scripts
- 51. Authoring tools to create additional custom troubleshooting packages
- 52. Additional on-demand troubleshooting packages available from Microsoft
- 54. Richer support tools e.g Problem Steps Recorder
- 55. Automatically run maintenance tasks
- 56. End-user tools
- 57. Help desk tools
- 60. BranchCache
- 63. Windows Troubleshooting Platform
- 64. Deployment Tools
- 68. The New Efficiency Virtual Launch Experience
- 71. © 2009 Microsoft Corporation. All rights reserved. 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.
Editor's Notes
- Slide Title: Windows 7 for the Optimized DesktopSlide Builds: 0Slide Script:Hello, and welcome to this session to the first session in the Windows 7 IT Pro Track. My name is {insert name}. In this session we’ll provide a quick overview of Windows 7 highlight core fundamentals and key features and solutions.Slide Transition: Let’s review the agenda for this session.
- Slide Title: Today’s Agenda Slide Builds: 0Slide Script: In this session we will be covering:Cover some of the fundamentals around Windows 7Application and OS VirtualizationSlide Transition: Let’s quickly review some of the workforce trends that IT has to manage.
- Slide Title: Today’s Agenda Slide Builds: 0Slide Script: In this session we will be covering:Cover some of the fundamentals around Windows 7Application and OS VirtualizationSlide Transition: Let’s quickly review some of the workforce trends that IT has to manage.
- Slide Title: Windows 7 Design FundamentalsSlide Builds: 3Slide Script: You and millions of customers like you have told us what you want in an Operating System. When did you tell us this, you ask? Every time you sit down to use your computer you provide us with valuable feedback on what works and what doesn’t work. Every time you voluntarily send feedback to Microsoft® after a crash or a bug, every time you click on the start menu, or plug in a printer, we log it in our telemetry database. We’ve been listening. [BUILD 1]We’ve poured over automated feedback from millions of Windows Users to understand what the most common issues are. Coupled with feedback from surveys, focus groups, customer support calls, and other sources, we’ve heard you.You’ve told us that you want your PCs to be faster and more reliableSlide Transition: Let’s review improvements in Windows 7 designed to make it faster and more reliable.
- Slide Title: Faster & More ReliableSlide Builds: 0Slide Script: Let’s start with how we designed Windows 7 to startup quickly.1) Fewer services run by defaultWhat we did in Windows Vista: we launched many services during system startup so that they would be ready and waiting when the user needed them.What we learned from telemetry: Most users only use a fraction of the services on their PC; unneeded services were delaying startup and consuming memory.How we designed Windows 7: Services initialize (“trigger-start services”) when the user runs a program or plugs in a device that requires this service. This speeds upboth startup and shutdown. Examples:Bluetooth, Bitlocker Drive Encryption, Remote Access, Encrypting File System2) Devices startup simultaneouslyWhat we did in Windows Vista: We start one device at a time, so that we could make sure it is up & running before moving on to the next. How we designed Windows 7: Device drivers startup simultaneously,saving a significant amount of time on startup.3) Shorter service timeout & forced shutdownWhat we did in Windows Vista and Windows XP: We had a long timeout window (20 seconds) during shutdown so that running services had plenty of time to gothrough their own shutdown routines and close.What we learned from telemetry: In many cases the services that exceeded the timeout period had long since locked up. Furthermore, many users were shuttingdown Windows Vista by holding down the power button for five seconds. How we designed Windows 7: We reduced the timeout to 12 seconds (Client SKUs only) and enabled users to force shutdown of unresponsive applications. This willmake shutdown much faster, and will encourage users to shut their PCs down properly.4)Optimized for common user scenariosWhat we learned from telemetry: Benchmarks do not reflect the activities of the average user.How we designed Windows 7: We identified & optimized the most common user scenarios, so that the majority of users would feel like their PC was “snappier” andmore responsive.Examples:Time from clicking the start button until the start menu is painted & ready is much smaller in Windows 7.Time from inserting a USB device until the device is ready to use is much smaller.Time it takes Search to index the hard drive is much smaller.5) Manages memory more efficientlyWhat we did in Windows Vista: we duplicated the graphics data required for each open window in both system memory and graphics card memory, which madethose windows more responsive, especially when the user had only a couple of open windows. What we learned from telemetry: most users had between five and fifteen windows open at a time, which used up a lot of system memory and hurt performance.How we designed Windows 7: we duplicate only the data required for the active window; data for the inactive windows are stored only in graphics card memory. Thisfrees up valuable system memory for applications without sacrificing responsiveness of the active window.In addition, We reduced the memory utilization of over 500 runtime components of Windows, and made the core of Windows at idle smaller by 10% to 30%. And withthe introduction of trigger-start services which I discussed on the previous slide, we reduced the amount of programs competing for system memory.6) Goes into Sleep Mode reliably, resumes quicklyWhat we learned from telemetry: we found that a lot of computers were not going to sleep reliably. Users would close the lids on their laptops and put them in theirbackpack, only to find out later that the computer was overheating because it never went to sleep properly. The biggest culprits were device drivers that were notsuspending properly.How we designed Windows 7: we worked very closely with our hardware partners. We shared our telemetry data with them, and even tested their devices in ourlabs. We’re including their improved drivers in the Windows 7 installation. As a result of this outreach, we believe that users will experience fewer problems with driverspreventing their computers from going to sleep.More Reliable 1) Engineered for uptimeHow we designed Windows 7: Windows 7 shares the system core with Windows Server, which means that the same kernel that is designed for the world’s largest datacenters (where uptime is critical to business) is inside your PC.2) Automatically fixes common memory errors & network glitchesWhat we learned from telemetry: A common reason behind application crashes is memory errors: Freeing unallocated memory; Allocating too much memory; orAccessing memory that has already been allocated or freed.How we designed Windows 7: Windows 7 detects when applications cause certain memory errors and “patches” them on the fly, so the user never knows there was aproblem.What we learned from telemetry: It is not uncommon for users to experience a delay when visiting a website, because of network hangs or glitches. How we designed Windows 7: Windows 7 detects when a process is hung waiting on a network call and lets the user cancel the call and restore the application. Inthis way the user can get to the website without ever realizing there was a problem.3) Built-in troubleshootersWhat we did in Windows Vista: We provided some basic tools to maintain the system.What we heard from customers: Customers want to have access to better tools to help fix computer problems without having to call technical support.How we designed Windows 7: We introduced “troubleshooters” in the action Center to help users fix or improve things.Examples:Performance, Program compatibility issues, Aero effects, Power utilization, Internet connection problems
- You’ve also told us you want your PC to be secure. Here are some of the ways in which we’ve designed Windows® 7 to protect your data and identity.
- Slide Title: More SecureSlide Builds: 0Slide Script: Windows 7 is designed to keep your data safer. In Windows® Vista we introduced BitLocker™ to enable businesses to protect confidential data from unauthorized access. IT Professionals loved this, but told us that we had not gone far enough, because employees load files on removable media (like thumb drives) which are outside the control of BitLocker. So in Windows 7 we introduced BitLocker To Go™, which is a mobile version of BitLocker for precisely those scenarios. With a few easy clicks an employee can extend the same level of protection to a removable device.Windows 7 is designed to give you better control of system security. In Windows 7 we did several things to reduce the volume of UAC prompts and still keep Users safe. For example we reviewed the prompts and were able to eliminate unnecessary ones (such as actions that can only be initiated by the mouse or keyboard). In this manner we were able to reduce the total number of prompts by 29%. We also gave Users more control over UAC prompts in terms of when to get notified. We believe this will make Windows easier to use without sacrificing security.Windows 7 includes Internet Explorer® 8. More than 90% of vulnerabilities affect either today’s Applications or browsers. To help protect Users while surfing the Web, Windows 7 ships with Internet Explorer 8, the most secure Web browser on the market today. Internet Explorer 8 is another, vital layer of defense against threats like phishing, cross-site scripting, and click-jacking. The new SmartScreen Filter provides protection against malware, a threat that is growing significantly faster than phishing.Our telemetry data show that every week, one in forty Internet Explorer 8 Users attempts to download malware that is blocked by the SmartScreen Filter.
- You also said your PCs should be compatible with your Applications, devices, and lifestyle. One of the things that Windows® has really built a great reputation around is being open, compatible, and providing great choice for our customers.So naturally the top question on customers’ minds is, “Will the software and hardware that I use on my Windows® Vista or Windows® XP PC work on Windows® 7?” So let’s talk about some of the ways in which we’ve designed Windows 7 to work with the software and devices you use every day.
- Slide Title: CompatibleSlide Builds: 0Slide Script: Windows 7 benefits from the joint engineering with our hardware & software partners. We have done more ecosystem outreach during the Windows 7 development than ever before. We increased the number of 3rd party hardware and Applications we test in our labs and shared the results with our partners. We even invited some of the partners into our labs to show them the results we were getting and enable them to make the changes necessary to ensure their products work flawlessly on Windows 7.Late in the Windows Vista development cycle we were still removing and changing underlying code; this was causing a lot of our partners’ Applications to break. So with Windows 7 we held it API-complete at the end of Alpha, and feature-complete partway through Beta. In this way we were able to make sure that our partners had a stable platform to develop on, and were able to provide them with better tools and documentation, such as earlier access to the Windows® Application Compatibility Toolkit, as well as powerful tools in the Windows® Performance Toolkit.Windows 7 is designed to be compatible with most Windows Vista hardware & software. In Windows 7 a principle design tenant was that if something worked on Windows Vista, it should work on Windows 7.With that in mind we’ve started out by keeping out changes to the device driver model that would break compatibility in a broad way.We discovered through our telemetry that 18% of all Application failures are due to hard-coded version checking, where the Application would not install if it detected a newer version of the operating system than what it was designed to run on. So in Windows 7 we kept the major version number the same, and we added Application Installation Failure Detection, which re-runs the installation and allows it to complete, thinking it is on the older Operating System.Innovations build in to improve compatibilityWe’ve also added a new technology called Switchback. Switchback allows Applications designed for Windows 7 to run a new set of APIs known to correct legacy API issues. For Applications not designed for Windows 7, we switch back to the original APIs.This enables older Applications to run fine on Windows 7, even though they were written for Windows Vista or Windows XP. And for legacy line-of-business Applications written for Windows XP that simply will not run on Windows 7 we offer Windows XP Mode as a separate download. This allows the IT Manager to create a virtual Windows XP machine on the Windows 7 desktop on which these legacy Applications can run (we don’t recommend this for consumers, however). Slide Transition: Let’s jump right in and check out Windows 7.
- Last but not least, you told us that you PCs should be easy to use.