Avi ShitritTechnology Strategist |

Intel | Microsoft Corporation

Manageability

Shachaf LeviIntel IT Client engineer

IT / Help DeskEnd User

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

PerfTrack : 300 user-visible scenarios identified

Examples: open start menu, open control

panel, booting

Performance goals set for each featureInstrumented with begin/end events Data sampled from Customer Experience Program and fed back to feature teams

Click Start Menu

Great OK Bad

Start Menu Open

http://blogs.msdn.com/blogfiles/e7/WindowsLiveWriter/SomeChangesSinceBeta_12A10/clip_image008_2.jpg

Decrease Increase

Enterprise-scale Enterprise-scale Scripting EngineScripting Engine

Scripting Scripting Group PolicyGroup Policy

Richer Support Richer Support ToolsTools

Customized Customized TroubleshootingTroubleshooting

Enhanced Group Enhanced Group Policy ScenariosPolicy Scenarios

Group Policy Group Policy PreferencesPreferences

Increased Automation Increased Automation to Reduce Coststo Reduce Costs

Reduce Help Desk Calls Reduce Help Desk Calls and Keep Users Productiveand Keep Users Productive

Flexible Flexible Administrative ControlAdministrative Control

Before Windows 7Before Windows 7

Easier to UseBuilt-in graphical editor/debuggerEasier to Extend

Develop CMDLETs via PowerShellAble To Manage Across The Enterprise

Remotable 1:1 (interactive) and 1:manyPowerShell can respond when specific system events occur

Windows 7 EnhancementsWindows 7 Enhancements

Automate tasks easily with PowerShellLearn scripting easier with graphical interfaceQuickly configure settings or run tasks in real-time

Customer ValueCustomer Value

Windows Eventing integrated with Task Scheduler to provide automation based on eventsNo built-in scripted automationAdministrators needed to deploy PowerShell or use other complex scripting languages to automate common tasks

Over 2.6 million downloadsWindows XP, Windows Vista, Windows Server® 2003, and Windows Server 2008Adopted by Exchange, SQL Server®, SCOM, SCVMM, and SCDPMDozens of 3rd party tools, ISVs, and partnersStrong community engagement, 27 PowerShell MVPs

Mailbox Mailbox StatisticsStatistics

Database Database ManagementManagement

Recipient Recipient ManagementManagement

Exchange 2003 (VBScript)Exchange 2003 (VBScript) Exchange 2007 Exchange 2007 (PowerShell)(PowerShell)

GUI over PowerShellCommand Line and GUIGUI teaches command line

Production ScriptingEasy to useSafe to operateEasy to share and support

Universal Code Execution ModelOn one or more machinesIn restricted or unrestricted environments, using impersonation or supplied credentialsInitiated by user input or by events

Community FeedbackEnhance the languageTweak the engineAdd and enhance Cmdlets

designed to deal with objects more than just a string of characterscarries 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 commandssyntax features, and keywords that are very similar to C#.

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

Utilities - Discovery

Command Function

Get-Help Help about PowerShell commands and topics

Get-Command

Get information about anything that can be invoked

Get-Member Show what can be done with an object

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

Using Format Commands to Change Output View

Working with Format-Wide, Format-List, and Format-Tableuses the same parameter name, -Property, to specify which properties you wish to display. Compare between:

Get-Process -Name powershell Get-Process -Name powershell | Format-listGet-Process -Name powershell | Format-List -Property ProcessName,StartTime,IdGet-Process -Name powershell | Format-List -Property *Get-Process -Name powershell | Format-TableGet-Process -Name powershell | Format-Table -Property Path,Name,Id,Company –AutoSizeGet-Process -Name powershell | Format-Table -Wrap -Property Name,Id,Company,PathGet-Process -Name powershell | Format-Table -Wrap -AutoSize -Property Name,Id,Path -GroupBy CompanyGet-Process | Out-GridView Get-Process | Export-Csv

The cost of running a service desk can be as much as 10% of companies' IT operations staffing budgetThe 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

Reduce number of support callsMake support calls more efficientIncrease customer satisfaction

Built-in Windows Troubleshooting Packs are discoverableBuilt-in Windows Troubleshooting Packs are discoverable

User detects a problem and initiates troubleshooting to fix the problemScheduled Troubleshooting detects a problem and informs the user to initiate troubleshootingAn application detects a problem and prompts the user toinitiate troubleshootingUser browsing Help sees a troubleshooter link relevant to his problem and clicks on it

Windows Troubleshooting is user or application initiatedWindows Troubleshooting is user or application initiated

From Action Center – Categories, Sorted list view, SearchFrom Help – Help topics link to troubleshooting packsA standard and consistent GUI wizard with pre-defined set of interactions

Troubleshooting Pack

Root CauseRoot

Cause

Root CauseRoot

Cause

Detect Verify

Identification metadata identifies pack, security signature and user interactionScripts contain the logic to find and fix the problemUser-visible information stored in localized resources (MUI-support)

Identification MetadataIdentification MetadataDetection

ScriptsDetection

ScriptsResolution

ScriptsResolution

ScriptsVerification

ScriptsVerification

ScriptsLocalized ResourcesLocalized Resources

Trouble-shooting Pack

Windows 7 Builds On Windows Vista Tools To Resolve Issues QuickerWindows 7 Builds On Windows Vista Tools To Resolve Issues Quicker

Reliability MonitorReliability data is exposed via WMI for remote collectionIntegration of Reliability Monitor and Problem Reports and Solutions to better correlate system changes and events

Resource MonitorSysInternals Process Explorer features integrated into Resource Monitor for clearer identification of process issues

Windows Recovery EnvironmentWindows 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 RecorderUsers can record steps taken when an issue occurs, giving help desk screen shots and comments to help resolve issues

Started with Resmon.exe, Perfmon /res, or from Open Resource Monitor link in Performance MonitorQuickly drill down on specific performance data

Data available per process if selected, All Processes by default

CPUMemoryDiskNetwork

CPU TabServicesAssociated HandlesAssociated 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)

MemoryPhysical Memory for entire system

Task manager like information shown

Overall system physical Memory utilization broken out into how it is currently allocated

DiskDisk activityStorage

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

NetworkNetwork ActivityTCP ConnectionsListening Ports

Netstat information can be viewed and filtered

Who am I connected to?

What ports am I listening on?

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

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

Enterprise-scale Enterprise-scale Scripting EngineScripting Engine

Scripting Scripting Group PolicyGroup Policy

Richer Support Richer Support ToolsTools

Customized Customized TroubleshootingTroubleshooting

Enhanced Group Enhanced Group Policy ScenariosPolicy Scenarios

Group Policy Group Policy PreferencesPreferences

Increased Automation Increased Automation to Reduce Coststo Reduce Costs

Reduce Help Desk Calls Reduce Help Desk Calls and Keep Users Productiveand Keep Users Productive

Flexible Flexible Administrative ControlAdministrative Control

Do you have any final questions?