![Windows Management Technologies Eric Nelson Application Architect [email_address] Finish 2:45 for break Microsoft Confidential](https://image.slidesharecdn.com/05-management-technologies-1193751923685039-2/85/05-Management-Technologies-1-320.jpg)
![Cmdlet – “get-proc” namespace Microsoft.Samples.PowerShell.Commands { #region GetProcCommand [Cmdlet(VerbsCommon.Get, "Proc")] public class GetProcCommand : Cmdlet { protected override void ProcessRecord() { Process[] processes = Process.GetProcesses(); // Write the processes to the pipeline making them available // to the next cmdlet. WriteObject(processes, true); } } Build the cmdlet using System.Management.Automation Build a snapin to install the cmdlet(s)](https://image.slidesharecdn.com/05-management-technologies-1193751923685039-2/85/05-Management-Technologies-16-320.jpg)
05 Management Technologies
- 1. Windows Management Technologies Eric Nelson Application Architect [email_address] Finish 2:45 for break Microsoft Confidential
- 2. Agenda Dynamic Systems Initiative and Design for Operations Windows Server Technologies Microsoft Management Console 3.0 (MMC) Windows PowerShell Windows Eventing 6.0 Task Scheduler 2.0 Also Group Policy Windows Management Instrumentation (WMI) WS-Management
- 3. DSI AND DFO Dynamic Systems Initiative and Design For Operations – ITO?
- 4. Dynamic Systems Initiative The Problem - Complexity IT Systems are Complex What applications are not running? What are the dependencies? Administration is Resource Intensive Automation is difficult The solution – Dynamic Systems Initiative Capturing Knowledge in Software Models SDM/SML Application Architecture, DataCenter, IT Policy Use knowledge throughout application lifecycle Design, Development, Deployment, Operations
- 5. DSI Progress Long term Vision 4 years on...
- 6. What is Design For Operations? Designing and Building Applications to the DSI Vision Building applications that can be deployed Building applications that can be operated Caring about Operations Attempts to address Developers and IT Staff Don’t talk (until there is a problem) Applications can not be configured or proactively monitored with management tools used by IT Staff No Knowledge Sharing Developers required to troubleshoot
- 7. Benefits of Design for Operations To the Customers IT Staff Lowers the total cost of ownership for the application Streamlines datacenter operations Reduces downtime Brings rapid return on the investment Brings problem solving expertise directly to the users To the ISV Reduce frequency of Problem Escalation Spend Less Time Maintaining Existing Applications Lower Support Costs Customer advocacy Facilitate Capture of Next Version Requirements
- 8. Sidebar: Do you recognise a pattern? Client applications hard to deploy and maintain Customers turn to the Browser ISVs with traditional “rich clients” lose out ISVs that switch to the browser bare the cost of increased complexity of development Yet all along, you could build “rich clients” that were good citizens Server applications hard to deploy and maintain Customers switch from on-premise to on-demand ISVs with on-premise lose out ISVs that switch to on-demand bare the cost of increased complexity of development Yet all along, you could build server applications that were good citizens
- 9. Design the Application to be Operated Health Model “What is not working and how bad is it?” How to Detect something is wrong How to Correct problem Realized through Instrumentation Events Performance Counters WMI Management consoles
- 10. Implementing is about… Instrumentation Events Performance Counters Implementing an Administration Surface Microsoft Management Console Windows PowerShell Task Scheduler Windows Management Instrumentation Group Policy Build an Installer Build a Management Pack
- 11. THE NEW BITS That make things a lot easier...
- 12. Microsoft Management Console 3.0 What is Microsoft Management Console 3.0? Provides a common administration GUI Why use Microsoft Management Console 3.0? Build administrative consoles Same technology Windows uses Consistent management experience for administrators Reduced Development Costs (with version 3.0) Managed Code Less Code
- 13. Windows PowerShell What is Windows PowerShell? Command Line Shell and Scripting Language Why use Windows PowerShell? Easy to Adopt, Learn and Use Provides consistent syntax and standard, uniform utilities Automates Bulk System Administration Tasks Accelerates Authoring, testing, and debugging of scripts Easy to build Custom Windows PowerShell Commands Managed Code Easy to Provide GUI (via MMC or Windows Forms)
- 14. MMC 3.0 Layered Over Windows PowerShell Command Line GUI Layered Over Your Application To Manage Windows PowerShell Engine Custom Application Microsoft Management Console 3.0 PSObject Windows PowerShell Cmdlets Windows Forms Early Bound Objects
- 15. Windows PowerShell & Microsoft Management Console 3.0
- 16. Cmdlet – “get-proc” namespace Microsoft.Samples.PowerShell.Commands { #region GetProcCommand [Cmdlet(VerbsCommon.Get, "Proc")] public class GetProcCommand : Cmdlet { protected override void ProcessRecord() { Process[] processes = Process.GetProcesses(); // Write the processes to the pipeline making them available // to the next cmdlet. WriteObject(processes, true); } } Build the cmdlet using System.Management.Automation Build a snapin to install the cmdlet(s)
- 17. Windows Eventing 6.0 What is Windows Eventing 6.0? Logs Event Information to the Application Logs, updated in Longhorn Server Lets Administrators and management tools know what is happening Why Use Windows Eventing 6.0? Better Performance & Reliability Declarative Event Structure Subscriptions Unified API for Eventing and Tracing Event Forwarding Benefits for Administrators Logs Easier to Manage, Search and Filter Better Tools Benefits for Developers Richer Eventing and Tracing Capabilities
- 18. Task Scheduler What is Task Scheduler? Windows Service for executing and managing the execution of jobs Several enhancements in version 2.0: Removed limitations on the number of registered tasks Scripting support Creation/management of tasks through XML-formatted docs New triggers (time, calendar, and event) Prioritization of tasks (i.e. define multiple instance policies, start a task only when it is available or only if the network is available, restart on failure, and set an execution time limit) New actions (send email, show message box, start exe, and fire a COM handler)
- 20. Not forgetting… Group Policy Bulk Manage Windows Client Application Configuration Enforce Configuration to Client Applications Enable mass configuration of client Applications WMI Expose Configuration/Management data and tasks to the OS Allow Scriptable Configuration Changes Allow Remote management WS-Management Standard Specification for accessing management data Common, platform neutral, network friendly access to management data such as WMI Secure
- 21. Summary Easier than ever before for an ISV to make every Administrator whoop for joy when they admin your solution DSI and DFO are “work in progress” – but already an ISV can get great wins
- 22. Resources DSI DSI core principles http://www.microsoft.com/windowsserversystem/dsi/dsicore.mspx DSI home http://www.microsoft.com/windowsserversystem/dsi/default.mspx Powershell http://blogs.msdn.com/powershell/ http://powergui.org/ MMC 3.0 and Powershell downloads http://blogs.msdn.com/ericnel