1. Avi Shitrit Technology Strategist | Intel | Microsoft Corporation Manageability Shachaf Levi Intel IT Client engineer

2. IT / Help Desk End User

3. Performance Microsoft® Windows PowerShell™ 2.0 Windows Troubleshooting Packs Problem Steps Recorder Reliability Monitor Resource Monitor Windows Events Managed default printer System Restore tool

4. PerfTrack : 300 user-visible scenarios identified Examples: open start menu, open control panel, booting Performance goals set for each feature Instrumented with begin/end events Data sampled from Customer Experience Program and fed back to feature teams Click Start Menu GreatOKBad Start Menu Open

6. Decrease Increase

7. Enterprise-scale Scripting Engine Scripting Group Policy Richer Support Tools Customized Troubleshooting Enhanced Group Policy Scenarios Group Policy Preferences Increased Automation to Reduce Costs Reduce Help Desk Calls and Keep Users Productive Flexible Administrative Control

8. Before Windows 7 Easier to Use Built-in graphical editor/debugger Easier to Extend Develop CMDLETs via PowerShell Able To Manage Across The Enterprise Remotable 1:1 (interactive) and 1:many PowerShell can respond when specific system events occur Windows 7 Enhancements Automate tasks easily with PowerShell Learn scripting easier with graphical interface Quickly configure settings or run tasks in real-time Customer Value Windows Eventing integrated with Task Scheduler to provide automation based on events No built-in scripted automation Administrators needed to deploy PowerShell or use other complex scripting languages to automate common tasks

9. Over 2.6 million downloads Windows XP, Windows Vista, Windows Server® 2003, and Windows Server 2008 Adopted by Exchange, SQL Server®, SCOM, SCVMM, and SCDPM Dozens of 3rd party tools, ISVs, and partners Strong community engagement, 27 PowerShell MVPs

10. Mailbox Statistics Database Management Recipient Management Exchange 2003 (VBScript) Exchange 2007 (PowerShell)

11. GUI over PowerShell Command Line and GUI GUI teaches command line Production Scripting Easy to use Safe to operate Easy to share and support Universal Code Execution Model On one or more machines In restricted or unrestricted environments, using impersonation or supplied credentials Initiated by user input or by events Community Feedback Enhance the language Tweak the engine Add and enhance Cmdlets

12. designed to deal with objects more than just a string of characters carries along extra information that you can use if you need it. do not need text-processing tools to extract specific information. Cmdlets - binary native commands can be argumented by snap-in Cmdlets. Snap-ins must be compiled just like binary tools in any other interface. Unified inputs and output for all commands syntax features, and keywords that are very similar to C#.

13. Don’t need to memorizing each command and each parameter. Different tools  different syntax (for example SC and Net commands) We want the same syntax for actions no metter which object we are working on. For example service or process. Cmdlets Use Verb-Noun Names to Reduce Command Memorization Get-Process, Stop-Process vs. Get-Service, and Stop- Service. Base on those verbs and noun we can find some more opportunities like stop-computer and get-computer

14. Utilities - Discovery CommandFunction Get-HelpHelp about PowerShell commands and topics Get-CommandGet information about anything that can be invoked Get-MemberShow what can be done with an object

15. You can enumerate all commands using a particular verb with the -Verb parameter for Get-Command The –Noun allows you to see a family of commands centered on a particular topic area.

16. Using Format Commands to Change Output View Working with Format-Wide, Format-List, and Format-Table uses the same parameter name, -Property, to specify which properties you wish to display. Compare between: Get-Process -Name powershell Get-Process -Name powershell | Format-list Get-Process -Name powershell | Format-List -Property ProcessName,StartTime,Id Get-Process -Name powershell | Format-List -Property * Get-Process -Name powershell | Format-Table Get-Process -Name powershell | Format-Table -Property Path,Name,Id,Company –AutoSize Get-Process -Name powershell | Format-Table -Wrap -Property Name,Id,Company,Path Get-Process -Name powershell | Format-Table -Wrap -AutoSize -Property Name,Id,Path -GroupBy Company Get-Process | Out-GridView Get-Process | Export-Csv

18. The cost of running a service desk can be as much as 10% of companies' IT operations staffing budget The typical support center supports over 300 applications The average call volume increased from less than 1 call per employee per month to 1.36 calls from 1995 to 2001

19. Reduce number of support calls Make support calls more efficient Increase customer satisfaction

20. Built-in Windows Troubleshooting Packs are discoverable User detects a problem and initiates troubleshooting to fix the problem Scheduled Troubleshooting detects a problem and informs the user to initiate troubleshooting An application detects a problem and prompts the user to initiate troubleshooting User browsing Help sees a troubleshooter link relevant to his problem and clicks on it Windows Troubleshooting is user or application initiated From Action Center – Categories, Sorted list view, Search From Help – Help topics link to troubleshooting packs A standard and consistent GUI wizard with pre-defined set of interactions

22. Troubleshooting Pack Root Cause DetectVerify Resolve

23. Identification metadata identifies pack, security signature and user interaction Scripts contain the logic to find and fix the problem User-visible information stored in localized resources (MUI- support) Identification Metadata Detection Scripts Resolution Scripts Verification Scripts Localized Resources Trouble- shooting Pack

24. Windows 7 Builds On Windows Vista Tools To Resolve Issues Quicker Reliability Monitor Reliability data is exposed via WMI for remote collection Integration of Reliability Monitor and Problem Reports and Solutions to better correlate system changes and events Resource Monitor SysInternals Process Explorer features integrated into Resource Monitor for clearer identification of process issues Windows Recovery Environment Windows Recovery Environment (WinRE) easily deployed via normal setup on all PCs Restore to OEM or IT image without data loss or reimage with recent system backup System Restore Users will now be able to view the list of software changes before rolling their PC back Restore points will be available from system backups allowing users to roll-back to a point further back in time Problem Steps Recorder Users can record steps taken when an issue occurs, giving help desk screen shots and comments to help resolve issues

26. Started with Resmon.exe, Perfmon /res, or from Open Resource Monitor link in Performance Monitor Quickly drill down on specific performance data Data available per process if selected, All Processes by default CPU Memory Disk Network

27. CPU Tab Services Associated Handles Associated Modules Handles can be searched to find specific item CPU-Total and each processor also broken out to graphs All Dll’s listed for selected process(es)

28. Memory Physical Memory for entire system Task manager like information shown Overall system physical Memory utilization broken out into how it is currently allocated

29. Disk Disk activity Storage Only lists processes with disk activity See what files are in use and filter by type of activity (Read/Write) Quick overview of Storage Available on the system

30. Network Network Activity TCP Connections Listening Ports Netstat information can be viewed and filtered Who am I connected to? What ports am I listening on?

31.  Central logging of events vs. private logs  Events and traces unified in single viewer  High-level event summary on home page  Easy-to-define notifications and actions on events  Richer online information about events  Enhanced filtering, sorting & grouping, preview  Define and save Custom Views  Default Views, Define and Save Custom View  Event forwarding – Subscriptions  View multiple logs from one machine  Cross-log queries  Self-contained saved logs  Log configuration  Enable/disable detailed logging to troubleshoot

33. This new Windows Event Forwarding (also known as Windows Eventing 6.0) is exceptional for the following reasons:  Standards Based  Agentless  Down-Level Support  Multi-Tier  Scalable  Group Policy Aware  Schematized Events Pre-Rendering  Resiliency  Security

35. Enterprise-scale Scripting Engine Scripting Group Policy Richer Support Tools Customized Troubleshooting Enhanced Group Policy Scenarios Group Policy Preferences Increased Automation to Reduce Costs Reduce Help Desk Calls and Keep Users Productive Flexible Administrative Control

36. Do you have any final questions?