Windows Server Management Marketing

Windows Server Management Marketing
9/12/2018 Modernizing Your Datacenter Module 2: Windows Server 2012 R2 Server Management Tools, Simply Amazing! © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. 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.

Agenda Module 1: Discovery and Assessment Tools in one word: Free!
Build 2012 9/12/2018 Agenda Module 1: Discovery and Assessment Tools in one word: Free! Module 2: Windows Server 2012 R2 Server Management Tools, Simply Amazing! Module 3: Windows Server 2012 R2 Hyper-V, Storage and Networking…Oh My Module 4: Microsoft Azure – Hybrid Connectivity, a look at the cloud in a new way Module 5: Migration Tools in another word: Free © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. 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.

Module 2 Agenda Server Manager Server Interface Choices PowerShell
Build 2012 9/12/2018 Module 2 Agenda Server Manager Server Interface Choices PowerShell Desired State Configuration © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. 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.

9/12/2018 Server Manager © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. 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.

How does Windows Server 2012 R2 meet my management needs?
STANDARDS-BASED MANAGEMENT MULTISERVER MANAGEMENT UPDATE MANAGEMENT Windows Management Framework provides a common platform for building automation and integration incorporating Windows PowerShell, WS-Management and WMI Server Manager enables a multiserver management experience that builds on the standardized approach to management and Simplify your routine task capabilities WSUS provides the features that administrators need to manage and distribute updates Centralized virtualization patching SIMPLIFY ROUTINE TASKS INTERFACE OPTIONS The first stop in these scenarios is the standards-based management approach that Windows Server 2012 R2 has adopted. Leveraging the Windows Management framework we can simplify the management of a diverse datacenter ecosystem by adopting standardized models, protocols and APIs to make managing and automating datacenter components easier and more efficient. We’ll take a look at this area first, before discussing the other topics shown here. <review topics> Windows PowerShell provides more features to allow more activities to be automated across the server ecosystem Server Mode GUI, minimal shell, core options

Server Manager redesign - why should I care?
Glance-able Dashboard with overall view of server environment. Fix issues from Server Manager, no need to open other tools. Server Manager dashboard customizable. Easily and quickly see which servers have issues. Works over multiple servers. Start and stop services. Add roles. Create custom groups based on your needs. Actionable Gone are the days when we used to manage one server at a time. Life isn’t that simple anymore! Now cloud computing is here, Server Manager needed to move from a single to a multi server view of the environment. Now you can see all your servers, check their performance and fix any issues – all from the Server Manager dashboard. Windows Server 2012 R2 allows for this with remote management, monitoring, installations and roles. For example, we can now make changes to a group of DCHP or DNS servers – regardless of where they are physically. Glance-able - You can glance at the Server Manager dashboard to get an overall view of the server environment. You can then quickly spot the key issues that need your attention Actionable - You can fix these issues without opening another tool. Via the Server Manager dashboard, you can start and stop services across multiple machines Relevant - The Server Manager dashboard is completely customisable. You can create a custom group – based on your needs – to display on the dashboard Relevant

Remote Server Administration Tools (RSAT)
Remote Server Administration Tools (RSAT) enables IT administrators to remotely manage roles and features in Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 or Windows Server 2008 R2 from a computer that is running Windows 8.1, Windows 8, Windows Vista, or Windows 7. This is similar to installing the adminpak.msi on Windows 2000 or Windows XP client computers. There is one major difference: in Windows Vista and Windows 7, the tools are not automatically available after RSAT is downloaded and installed. You must enable the tools that you want to use by using the Control Panel. To do so, click Start, click Control Panel, click Programs and then click Turn Windows features on or off. However, in the RSAT release for Windows 8.1 and Windows 8, tools are once again all enabled by default. You can open Turn Windows on or off to disable tools that you don't want to use. In Remote Server Administration Tools for Windows 8.1 and Remote Server Administration Tools for Windows 8, GUI-based tools are accessed from within the Server Manager console, on the Tools menu. If you need to install management tools in Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 for specific roles or features running on remote servers, there's no need to install additional software. Open the Add Features Wizard in Windows Server 2008 or Windows Server 2008 R2, or the Add Roles and Features Wizard in Windows Server 2012 and later releases, and on the Select Features page, expand Remote Server Administration Tools and select the tools that you want to install. Complete the wizard to install your management tools. Remotely manage roles and features in… Windows Server 2012 R2, Windows Server 2012, Windows Server 2008 ,or Windows Server 2008 R2 Downloadable Run from… Windows 8.1, Windows 8 Enabled by default Accessed from Server Manager, Tools menu Windows 7, Windows Vista Disabled by default To enable, click Start, click Control Panel, click Programs, and then click Turn Windows features on or off.

Let's Take A Look Server Manager Tech Ready 15 9/12/2018
Use the MinWin Let's Take A Look.docx file for instructions. © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. 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.

Server Interface Choices
Windows Server Management Marketing 9/12/2018 Server Interface Choices © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. 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.

Interface choices Configuration levels Classic “Full Server”
9/12/2018 Interface choices Configuration levels Server with a GUI Classic “Full Server” Full GUI shell Install Desktop Experience to run Windows Store-style apps Full Server without Server Graphical Shell No Explorer, Internet Explorer or associated files MMC, Server Manager, and a subset of Control Panel applets are still installed Provides many of the benefits of Server Core for those applications or users that haven’t yet made the transition Server Core Can move between Server Core and Full Server by simply installing or uninstalling components Minimal Server Interface Windows Server 2012 provides three levels of User Interface to choose between: Server Core Traditional server core with command line only interface Minimal Installation Shell (“MinShell”) Server Core plus select UI elements such as MMC support and Server Manager Enables you to run Server Manager Supports graphical driver management Supports limited graphical applications Full Shell Full Windows desktop, which can also include the Desktop Experience This presentation will discuss the benefits of using Server Core and MinShell, as well as how to change the interface being used without reinstalling Windows. Server Core

Interface choices - why should I care?
The challenges… Lowering the attack footprint of the server to the smallest size possible while keeping it fully patched is a primary responsibility of administrators Many administrators are uncomfortable with only a minimal command-line interface (Server Core) The Windows Server 2012 solution… multiple interface options Allows administrators to use the same familiar graphical tools to administer the server without using remote management tools Removes the overhead of the other operating system elements not needed to perform that task Does not require a re-installation to modify the level of GUI on a server; modified in the same manner as any other role or feature Allows for a single server deployment image Minimizing the disk space and memory requirements for Windows Server enables administrators to increase the density of their servers (especially when virtual machines are involved) and scale out their deployments significantly. With Server Core, you can not only accomplish considerable space savings (thereby reducing storage costs), but also minimize the attack surface area (thereby increasing security and reliability). Reducing the overall footprint of Windows also enables you to minimize the servicing footprint. By limiting the number of components that must be patched on a given server, you are able to naturally minimize the number of applicable patches, thereby reducing the frequency of reboots and increasing server availability. Windows Server 2012 R2’s focus on being a great platform for private cloud deployments further underscores the importance of their efforts to enable a minimal system footprint. The Minimal Server Interface is designed to be a state in between Server with a GUI and Server Core. As it is intended primarily as a transitional layer, it is not directly exposed in the Windows Server installation options dialog box. You’ll need to install the Minimal Server Interface on top of Server Core, or remove the Server Graphical Shell from a Server with a GUI installation. Changing server requirements – If you have deployed Server Core and then there is a change in what needs to run on the server that requires either Minimal Server Interface or Server with a GUI you can now convert up without having to reinstall and rebuild the server. Troubleshooting or configuration – If there are any issues that you need to trouble shoot or configuration changes you want to make and find it easier to do either with the local GUI tools, you can convert to either Minimal Server Interface or Server with a GUI. Initial configuration – You can install Server with a GUI, configure the server as desired for your environment, and then convert to Server Core for production and get all the servicing and reboot reduction benefits of Server Core. Single master image – With the ability to switch between Server Core and Server with a GUI you can create a single master image for deployment. Once installed on a new server it can then be converted to Server Core if that is the planned configuration for the server. There is no longer a need to create and maintain two Windows Server images.

Minimal Server Interface
Server Core Minimal Server Interface Server with a GUI Desktop Experience Command Prompt a Windows PowerShell/.NET Server Manager x MMC Control Panel CPL Applets Some Explorer Shell Taskbar System Tray Internet Explorer Help Themes Start screen Modern apps Media Player [review the differences in feature sets between the available interfaces]

Interface Choices Server Core
.Net Framework 4.5 Active Directory (AD) Active Directory Lightweight Directory Services (ADLDS) Active Directory Certificate Services (ADCS) DHCP Server DNS Server File Services BITS Server BranchCache Hyper-V Internet Information Services (IIS) Printing Services Streaming Media Services iSCSI Load Balancing MPIO qWave Telnet Unix Migration SQL Server 2012 Server Core Microsoft promotes Server Core as the primary server deployment option While remaining committed to GUIs, Microsoft believes the primary place GUIs should exist is on the administrator’s desktop – not on the Server, Server resources are much more expensive than client resources and running GUIs on servers requires additional software components. Every component increases the security and serviceability exposure of that server so you should only install those components that are necessary to that server workload. Fewer things running on the server means fewer patches and more resources available to the server workload. Beginning with Windows Server 2012 several investments were made to help administrators succeed in choosing Server Core as the primary deployment option for Windows Server. The traditional “Server with a GUI” is still provided as a backwards compatibility option. The number of server roles that run on Server Core has increased with support for .Net Framework 4.5 included. SQL Sever 2012 now installs, eliminating the most common reason administrators cited for not being able to run in the Server Core configuration. Firewall-friendly remote management (WinRM) and Windows PowerShell are now enabled and installed by default on all servers, removing any configuration needed before being able to manage the server remotely. Windows PowerShell’s cmdlets provide the command line coverage necessary for most admin scenarios. Perhaps most significantly however, there is now the ability to move between Server Core and Server with a GUI (MinShell) without the need to reinstall the server! This means administrators can safely start with their server deployed in the Server Core configuration and if they find they need the GUI they can add it, and also remove it as needed using the SCONFIG CLI tool, Windows PowerShell or the Add/Remove Roles and Features Wizard. This “in-between” option provides many of the benefits of Server Core while still having the safety-factor of being able to run GUIs should the administrator need to log into the Server directly. Server Core now supports more roles and services, including .Net Framework 4.5 and SQL Server 2012 Firewall-friendly remote management (WinRM) and Windows PowerShell are enabled and installed by default Added the ability to easily move between Server Core and MinShell

Limitations of the MinShell
Common Dialog box is functional (except networking) Any UI with dependencies on items implemented as Shell Namespace Extensions will fail Certain CPLs are namespace extensions, e.g. Networking Internet Explorer is not available when Server Graphical Shell is uninstalled Links in UI won’t work Help isn’t available – calls Some file associations and protocol handlers broken file:// *.chm Some DLL files not installed Check for dependencies or delay loads might fail! DUMPBIN (Windows SDK) Dependency Walker ( freeware) Test your applications on the Minimal Server Interface! to HTML Help API will return NULL! [Review content of the slide]

Enabling/Disabling MinShell
Install-WindowsFeature Server-Gui-Mgmt-Infra Install-WindowsFeature Server-Gui-Shell Install-WindowsFeature Desktop-Experience Uninstall-WindowsFeature Server-GUI-Shell Uninstall-WindowsFeature Server-GUI-Shell -remove MinShell can be enabled through the Add Roles and Features Wizard of Server Manager or by using Windows PowerShell to install the appropriate Windows Features: Server-Gui-Mgmt-Infra: infrastructure and a minimal server interface that supports GUI management tools Server-Gui-Shell: provides the full Windows graphical user interface for server, including Windows Explorer and Internet Explorer. Uninstalling the shell reduces the servicing footprint of the installation, while leaving the ability to run local GUI management tools Desktop-Experience: includes features of Windows Server 2012, such as Windows Media Player, desktop themes, an photo management. Desktop Experience does not enable any of the Windows Server 2012 features; you must manually enable them. In previous versions of Windows, even if a server role or feature was disabled, the binary files for it were still present on the disk, consuming space. Beginning with Windows Server 2012, not only can you disable a role or feature, but you can also completely remove its files, a state called “disabled with payload removed.” To reinstall a role or feature that is disabled with payload removed, you must have access to an installation source, such as an installation DVD. To completely remove a role or feature, use –Remove with the Uninstall-WindowsFeature cmdlet of Windows PowerShell. For example, to completely remove Windows Explorer, Internet Explorer, and dependent components, run: Uninstall-WindowsFeature Server-Gui-Shell -remove

Let's Take A Look Using the MinShell Tech Ready 15 9/12/2018

9/12/2018 PowerShell © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. 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.

What is Windows PowerShell?
Windows PowerShell is a distributed automation engine with a scripting language and interactive shell(s) Focuses on the business Makes change safe through automation Bridges the gap between operators and developers Windows PowerShell 4.0 is available for the following operating systems: Built-in Windows Server 2012 R2 Windows 8.1 Downloadable for Windows 7 SP1 Windows Server 2008 R2 SP1 Windows PowerShell has always focused on people using computers in a business context. Windows PowerShell needed to be consistent, safe, and productive. Much has been made of the similarities between Windows PowerShell and UNIX but in this regard, Microsoft’s ties are much closer to VMS/DCL and AS400/CL. Consistent: Operators and developers don’t have a lot of time to learn new things. A consistent experience lets them to invest once in a set of skills and then use those skills over and over again. Windows PowerShell uses a single common parser for all commands and performs common parameter validation delivering absolute consistency in command line syntax. Windows PowerShell cmdlets are designed in a way that ubiquitous parameters can provide consistent functions to all commands (e.g. –ErrorAction, –ErrorVariable, –OutputVariable, etc) Safe: An Operator once said that occasionally he was about to do something and realized that if he got it wrong, he would be fired. In Windows PowerShell, if you ever execute a cmdlet which has a side-effect on the system, you can always type –WhatIf to test what would happen if you go through with the operation. It also supports –Confirm, -Verbose and –Debug. Despite these safeguards, things can go wrong and when they do, Windows PowerShell spends a lot of effort to speed up the process of diagnosing and resolving the error. Productive: Every aspect of Windows PowerShell’s design maximizes the power of users (ergo the name). Windows PowerShell makes it easy to perform bulk operations across a large number of machines. Windows PowerShell also makes it easy to have productive engagements between your operators and developers because it allows them to speak a common language and to help each other with their scripts. Microsoft’s goal has always been to deliver a single tool which could span the needs of operators doing ad hoc operations, simple scripting, formal scripting, advanced scripting and developers doing systems-level programming. Most importantly, they wanted to develop a tool which could be used by BOTH operators and developers to bridge the gap between the groups and allow them to create common scripts, learn from each other and work together. As you’ll see, Windows PowerShell 4.0 continues that effort. <Discuss the operating systems that support Windows PowerShell 4.0 – see slide> Windows PowerShell 4.0 is backward-compatible. Cmdlets, providers, modules, snap-ins, scripts, functions, and profiles that were designed for Windows PowerShell 3.0 and Windows PowerShell 2.0 work in Windows PowerShell 4.0 without changes. However, due to a change in the runtime activation policy in Microsoft .NET Framework 4.0, Windows PowerShell host programs that were written for Windows PowerShell 2.0 and compiled with Common Language Runtime (CLR) 2.0 cannot run without modification in Windows PowerShell 3.0, which is compiled with CLR The Windows PowerShell 2.0 engine requires Microsoft .NET Framework at a minimum. This requirement is fulfilled by Microsoft .NET Framework 3.5 Service Pack 1. This requirement is not fulfilled by Microsoft .NET Framework 4.0 and later releases of Microsoft .NET Framework.

Windows PowerShell 4.0 - Why should I care?
The challenge… Reduce errors during configuration changes Reduce the skill set required for authoring automation of complex solutions Locate and import the numerous Windows PowerShell modules into each session Reduce the syntax learning curve, especially for people new to Windows PowerShell Bridge the gap between operators and developers The Windows PowerShell 4.0 solution…. Allows for use of tested scripts, reducing the number of errors that impact production environments Improves efficiency due to the dramatic increase number of built-in cmdlets Includes features designed to speed understanding and correct usage of syntax (Show-Command, Intellisense) Makes excellent progress toward bridging the gap between operators and developers Simplifies routine tasks!! Make change safe through automation There has been a lot of discussion about whether Windows PowerShell is a .Net language, a scripting language, or an interactive shell. Windows PowerShell is a distributed automation engine with a scripting language and interactive shell(s). Interactive shells and a scripting language are critical components but the focus has always been on automation through scripting. Automation is the process of reducing and/or eliminating operations performed by a human. A script documents what is going to happen. People can review a script and you can modify it based upon their feedback. You can test the script, observe the outcome, modify the script and if modification is good, keep it and it if is bad back it out. Once you have an automated process, you can safely apply it over and over again. These processes can now be performed reliably by lower skilled administrators, which isn’t possible when you use traditional GUI admin tools. The dramatic increase in built-in cmdlets reduces the skill set required for administrators to automate complex solutions and reduces the need to locate and install individual Windows PowerShell modules for various technologies. Figuring out a cmdlet from its syntax can be overwhelming, especially for people new to Windows PowerShell. Show-Command is a cmdlet that displays a graphical user interface for a command with a simpler overview of a cmdlet. Windows Server 2012 R2 and Windows PowerShell 4.0 are excellent DevOps tools DevOps is a relatively new term and there is some disagreement about what it entails but at the heart it is all about making change safe through automation and bridging the gap between operators and developers. According to Jeffrey Snover (Lead Architect for Windows Server) “there is a lot to do in this area but Windows Server 2012 and Windows PowerShell 3.0 make excellent progress towards accomplishing those goals. Windows PowerShell won’t be the only tool in your DevOps toolbox but it should be in every DevOps toolbox.” Windows PowerShell 4.0 has continued to improve upon this.

Windows PowerShell 4.0 Key features Ease of use Greater resiliency
9/12/2018 Windows PowerShell 4.0 Key features Ease of use Integrated Scripting Environment: IntelliSense, Code Snippets Windows PowerShell Web Access Greater resiliency Robust session connectivity Job scheduling Windows PowerShell workflow Extensive coverage Rich management through more than cmdlets Real world scenario Domain join System Center integration More Intuitive Enhanced ISE with Intellisense Simplified language syntax Updatable help system Easy command discovery and import Extensive coverage Over 3,000+ cmdlets across Windows Support for thriving community Script Explorer & Script Library Greater Resiliency Robust session connectivity Integrated workflow Connect/disconnect remote sessions Scheduled jobs Windows PowerShell 4.0 is a better 3.0 Many suggestions addressed On-the-fly compilation allows scripts to run up to 6x faster Enhanced interactive console experience Core cmdlet and provider improvements <Discuss some real world examples for using Windows PowerShell>

Windows PowerShell Web Access
Greater Resiliency Corporate Network Server 1 Server 2 Server 3 Manage multiple computers running Windows by using Windows PowerShell within a browser Broad support for popular browsers Built for tablets and mobile devices Enable through the Add Roles and Features wizard in Server Manager Web-based console user Internet Perimeter Network Windows PowerShell Web Access Gateway Value added to the Windows PowerShell ecosystem: End-Users Remote management Access anywhere Partners Return from their Windows PowerShell investment Requirements: Client Browser (HTML + Ajax) Gateway Windows Server 2012, Windows PowerShell Web Access role Target Windows PowerShell Remoting You can install and configure Windows PowerShell Web Access, and use a browser session to manage multiple computers to perform management of any server with remote management enabled by connecting to a single gateway, which can be externally facing. Installed as a feature through Add roles and features in Server Manager. Windows PowerShell commands are used to configure web access. You can then log in to a url which provides full Windows PowerShell capability from the browser.

Robust sessions Greater Resiliency
Allow for reconnection to disconnected remote sessions Robust Networking In previous releases, Windows PowerShell shipped with remoting disabled by default and required operators to go to each machine and issue the Enable-PSRemoting cmdlet in order to remotely manage it. As a cloud OS, remote management of servers via Windows PowerShell is now the mainstream scenario, so Microsoft reduced the steps required and enabled Windows PowerShell remoting by default in all server configurations. Extensive security analysis and testing were done to ensure that this was safe. WS-MAN is Microsoft’s primary management protocol, while COM and DCOM are kept for backwards compatibility. WS-MAN is a Web-Services protocol using HTTP and HTTPS. While these are effectively REST protocols, Windows PowerShell establishes a session layer on top of these to reuse a remote process for performance and to take advantage of session state. These sessions were robust in the face of modest network interruptions but would occasionally break when operators managed servers from their laptops over Wi-Fi networks while roaming between buildings. The session layer of WSMAN has been enhanced. By default, it will survive network interruptions up to 3 minutes. Beginning with Windows PowerShell 3.0, disconnected sessions support was added to Windows PowerShell sessions, which give users the option to disconnect from an active remote session and later reconnect to the same session without losing state or being forced to terminate task execution. You can even connect to the session from a different computer (just like a Remote Desktop session). Create and disconnect a robust session In this example, we will create a new robust session, and then disconnect from it. This series of commands creates a new session on a remote server, stores data in that session, and then disconnects, while leaving the remote session running. The name of the running session is Server1Session. The local connection variable is $RemoteSession. 1. Click Windows PowerShell. 2. Type the following commands, pressing ENTER after each one. ↪ Enable-PSRemoting –Force Remember, you are no longer required to configure Remoting. It is setup by default for use by Server Manager. ↪ $RemoteSession = New-PSSession –Name Server1Session –ComputerName Server1 ↪ Invoke-Command –Session $RemoteSession –ScriptBlock {$date = Get-Date } ↪ Disconnect-PSSession –session $RemoteSession ↪ Exit Reconnect to a robust session In this step, we reconnect to the previously created session. In this particular example, we will do this by logging on to the machine where the Server1Session is still running, but disconnected. 1. Open Windows PowerShell and type the following commands, pressing ENTER after each one. ↪ Get-PSSession –ComputerName localhost ↪ $LocalSession = Connect-PSSession –ComputerName localhost –Name Server1Session ↪ Invoke-command –Session $LocalSession –Scriptblock { $date } This example creates a new session on a remote server, stores data in that session, and then disconnects it while leaving the session running. The name of the running session is Server1Session. The local connection variable is $RemoteSession. The following commands reconnect to the remote session (in this example, from the server where the session is still running) ↪ Enable-PSRemoting –Force ↪ $RemoteSession = New-PSSession –Name Server1Session –ComputerName Server1 ↪ Invoke-Command –Session $RemoteSession –ScriptBlock {$date = Get-Date } ↪ Disconnect-PSSession –session $RemoteSession ↪ Exit ↪ Get-PSSession –ComputerName Localhost ↪ $LocalSession = Connect-PSSession –ComputerName localhost –Name Server1Session ↪ Invoke-command –Session $LocalSession –Scriptblock { $date }

Robust session connectivity with PSWA
9/12/2018 Robust session connectivity with PSWA 03 Greater Resiliency Corporate Resource Server 1 User connects via the browser through the Windows PowerShell Web Access Gateway to run a script on Server 1. User loses connection to the internet. User reconnects to internet at a later point in time and reconnects to the Windows PowerShell session which is still in a connected state and still running. Internet Web-based console user Perimeter Network Windows PowerShell Web Access Gateway Script Robust session connectivity is now extended to PSWA

Let's Take A Look PowerShell Tech Ready 15 9/12/2018

Desired State Configuration
Windows Server Management Marketing 9/12/2018 Desired State Configuration © 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. 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.

9/12/2018 Desired State Configuration DSC Components of your data center have the correct configuration. PowerShell language extensions and providers which enable declarative, repeatable deployment. Define the exact configuration of target nodes (computers or devices) and prevent “configuration drift.” New Windows PowerShell ISE Features. The Windows PowerShell Integrated Scripting Environment (ISE) 3.0 includes many new features to ease beginning users into Windows PowerShell and provide advanced editing support for scripters. Some of the new features are: Show-Command pane lets users find and run cmdlets in a dialog box. IntelliSense provides context-sensitive command completion for cmdlet and script names, parameter names and enumerated values, and property and method names. IntelliSense also supports paths, types, and variables.

9/12/2018 Desired State Configuration “Make it so” phase Declarative configuration is reified through imperative providers. Providers implement changes: Monotonic. Imperative. Repeatable. Staging phase Fully declarative configuration representation using DMTF standard MOF instances. Configuration is calculated for all nodes. Authoring phase May include imperative as well as declarative code. *** When authoring in PowerShell, on top of PSV3 imperative features, PSV4 adds: Declarative syntax extensions. Schema validation (early-binding). Agent of consistency Imperative providers Local DSC cache 3rd party languages and tools PS V1, V2, V3 PS V4*** Configuration staging area (Contains DSC data) (This is a PUSH model) Show: Simple Provider Show: Ability to execute Get-Website, etc. Note: Others (puppet, chef, cfengine… anyone) can plug in and utilize different components of this architecture. LCM:…. Consider this: The mechanics are that PS produces a MOF file that is consumed by the agent which makes it so. What that *really* means is that we are shipping a Desired State Configuration agent which consumes standards-base-management documents which can be produced by *any* tool. In other words, we are delivering a single agent which ANY and ALL configuration management tools (e.g. Chef/Puppet/CfEngine/System Center/etc) can use. Today, each of these tools is out trying to convince everyone in the world to write providers for their tools. In the new world, people will write a single provider and will be able to light up all the tools (once the tools use our agent).

Let's Take A Look DSC Tech Ready 15 9/12/2018

Windows Server Management Marketing

Similar presentations

Presentation on theme: "Windows Server Management Marketing"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Windows Server Management Marketing

Similar presentations

Presentation on theme: "Windows Server Management Marketing"— Presentation transcript:

Similar presentations

About project

Feedback