PowerShell-and-DSC-Enables-DSCDevOps-1.pptx

Editor's Notes

• #2: Title: PowerShell and DSC Empowers DevOps and the Cloud Abstract: Dan Stolts from Microsoft and ITGuru.com comes with a full session on Desired State Configuration! DSC is a new management platform in Windows PowerShell that enables deploying and managing configuration data for software services and managing the environment in which these services run. DSC provides a set of Windows PowerShell language extensions, new Windows PowerShell cmdlets, and resources that you can use to declaratively specify how you want your software environment to be configured. It also provides a means to maintain and manage existing configurations.Practical applications Following are some example scenarios where you can use built-in DSC resources to configure and manage a set of computers (also known as target nodes) in an automated way: Enabling or disabling server roles and features Managing registry settings Managing files and directories Starting, stopping, and managing processes and services Managing groups and user accounts Deploying new software Managing environment variables Running Windows PowerShell scripts Fixing a configuration that has drifted away from the desired state Discovering the actual configuration state on a given node   Name of Presenter: Dan Stolts Bio of Presenter (max 500 spaces): Dan Stolts “ITProGuru” is a technology expert who is a master of systems management and security. He is Chief Technology Strategist for Microsoft, owns several businesses and is a published author. Reach him on his primary blog http://itproguru.com or twitter @ITProGuru. He is proficient in many datacenter technologies (Windows Server, System Center, Virtualization, Cloud, Etc) and holds many certifications including MCT, MCITP, MCSE, TS, etc. Dan is currently specializing in system management, virtualization and cloud technologies. Dan is and has been a very active member of the user group community. Dan is an enthusiastic advocate of technology and is passionate about helping others. See more at: http://itproguru.com/about
• #3: Over the past 5 years, the State of DevOps report has surveyed more than 25,000 technical professionals world wide with companies of ALL sizes and verticals. Employees in high-performing teams were 2.2x more likely to recommend their organization as a great place to work. (2016 – employee Net Promoter Score)
• #4: In the real world, there are real consequences if you are unable to deliver high-quality software quickly or build the wrong thing to begin with: 40% of implementations end up getting reworked because they don’t meet the users’ original requirements The average cost of one hour downtime of a customer-facing app is calculated at 100.000 dollars per hour – and this does not take into account the damage to reputation, which can be even greater.Fixing such production issues takes on average 200 minutes per incident Three quarters of development teams have adopted Agile methodologies today, enabling them to develop faster.While this is a great number, it does not help if a development team is Agile but deployment still takes weeks or months because IT Ops is perceived as not being Agile These are just 3 very high-level examples but all the data we have today points toward the same conclusion – this is about more than just frustration or minor delays. Lack of collaboration between dev and ops can have substantial impact on a company’s bottom line and success
• #6: Declaring a DSC configuration is PowerShell based - You define configuration programmatically(script) which comes to admins naturally and help them define configuration in the way they want. Reusability of Configuration Data - You can separate the configuration data from the logic of your configuration so that you can reuse your configuration data for different resources, nodes, and configurations, see http://technet.microsoft.com/en-us/library/dn249925.aspx Can be used anywhere -DSC can be used on-premise, in a public or in a private Cloud environment. You just need either Windows Server 2012 R2 or Windows 8.1 and local administrator permissions to execute the DSC PowerShell scripts Support for integration with other tools -You can integrate DSC with any Microsoft or non-Microsoft solutions as long as you can execute a PowerShell script on the target system. E.g. using DSC within the Windows Azure Pack portal in conjunction with SMA.
• #21: Advanced task dependencies – talk about “Dependency Type” options enabled only for multi-machine job when Dependencies is clicked in the Task tab. Studio Help -> Contents -> “Working With Jobs” -> “Key Concepts for WTT Jobs” -> Parameters
• #22: Advanced task dependencies – talk about “Dependency Type” options enabled only for multi-machine job when Dependencies is clicked in the Task tab. Studio Help -> Contents -> “Working With Jobs” -> “Key Concepts for WTT Jobs” -> Parameters
• #23: Advanced task dependencies – talk about “Dependency Type” options enabled only for multi-machine job when Dependencies is clicked in the Task tab. Studio Help -> Contents -> “Working With Jobs” -> “Key Concepts for WTT Jobs” -> Parameters
• #24: Advanced task dependencies – talk about “Dependency Type” options enabled only for multi-machine job when Dependencies is clicked in the Task tab. Studio Help -> Contents -> “Working With Jobs” -> “Key Concepts for WTT Jobs” -> Parameters