1. 12/7/2018 6:48 PM
SAC-565T
Windows Networking with PowerShell: A Foundation for Datacenter Management
Ross Ortega & Christopher Palmer
Program Managers
Windows Networking Core
Microsoft Corporation
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

2. Windows Server 8 is Cloud Optimized
Enable Multi Tenant Clouds
Network Virtualization. Dynamic VM Placement. Secure Isolation. …
High Scale & Low Cost Datacenters
Leverage Hardware. High Availability. SMB2. Low Cost Storage. …
Manageable & Extensible
WMIv2. PowerShell. Extensible Switch. …

3. Agenda Windows Server 8 Networking PowerShell basics Objects
Developer Platforms
Putting it all together: Create a corporate network
You’ll leave with examples of how to
Manage and optimize your Server and NIC products
Develop on Windows Networking PowerShell and WMI

4. Why We’re Here Datacenters require greater efficiency and larger scale
You need to develop solutions to manage server network configurations across the entire datacenter
You want an extensible and standards-based management framework that works remotely and at scale

5. Take advantage of Windows Server 8 Networking PowerShell to build cloud management solutions

6. An example management experience for Networking
12/7/2018 6:48 PM
demo
An example management experience for Networking
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

7. Windows 8 PowerShell Manageability
Networking
File Services
Windows 8 PowerShell Manageability
Hyper-V

8. World of Networking Enterprise Networking NetAdapter TCP/IP
DNS
DHCP Server
BranchCache
DirectAccess
NetAdapter
NIC Teaming
QoS
Offloads
TCP/IP
IP Addresses
Routes and Neighbors
TCP Settings
Windows Firewall
Firewall Rules
IPsec Rules
Virtualization
Hyper-V Network Virtualization
Hyper-V Extensible Switch

9. Networking PowerShell Basics

10. Get-NetAdapter PowerShell CMDlets Verb Noun
Organized by verbs and nouns separated by a dash
Verb
Noun
Get-NetAdapter

11. Nouns
In Windows Server 8 introduces over 50 PowerShell nouns for Networking, including:
NetAdapter
DNSclient
NetIPInterface
NetIPAddress
NetLbfo
NetQos
NetTeredoConfiguration
NetVirtualization
NetFirewallRule
VMSwitch
VMSwitchExtension

12. Discoverability To find Networking CMDlets run Get-Command *-Net*
To get the syntax of a CMDlet use Get-Help
Get-Help *-Net*
Get-Help Get-NetAdapterBinding
Show-Command New-NetFirewallRule

13. Remote Management Easy access to remote machine objects
Windows Remote Management is on by default
Run CMDlet with –CimSession parameter
Requires secure administrator credentials
Example: Get network adapters on remote machines named SQL1 and SQL2
Get-NetAdapter –CimSession SQL1, SQL2

14. Naming and Wildcards Multiple ways to get at specific network adapters
Get-NetAdapter “Wired Ethernet Connection 2”
Get-NetAdapter W*2
Get-NetAdapter –InterfaceDescription Fabrikam*
Note: InterfaceDescription typically has the format
<NIC Manufacturer Name> <Model Number> <Speed>

15. Extensibility Standardized mechanism to add new advanced properties
New-NetAdapterAdvancedProperty
–InterfaceDescription Fabrikam10GbENic
–RegistryKeyword UltraLowLatencyMode
–RegistryValue 2
–RegistryDataType “REG_SZ” –CimSession SQL1

16. Optimization Opportunities: NIC Vendors
Take advantage of InterfaceDescription to provide customized scripts that fine-tune configurations for specific NICs and scenarios
Use NetAdapterAdvancedProperty for non-standardized keywords so Windows manages registry and simplifies user experience
Make sure your products are manageable with NetAdapter and NetAdapterXXX family of cmdlets

17. Optimization Opportunities: OEMs
Fine tune your server SKUs by configuring NIC settings
For example:
Rename-NetAdapter NIC1 Numa1NIC
Set-NetAdapterRss Numa1NIC –NumaNode 1
Rename-NetAdapter NIC2 Numa2NIC
Set-NetAdapterRSS Numa2NIC –NumaNode 2

18. Increase customer satisfaction and simplify development by using PowerShell for network adapter management

19. Objects

20. Integrated Object Model
Network
Adapter
TCP/IP
Firewall
PowerShell
Pipelining enables integrated network stack management

21. Value of Objects #Simple to save and restore state (remotely)
$Backup= Get-NetAdapterBinding –cimsession RemoteMachine
Export-CLIXML -InputObject $Backup -Path
“BackUp Config.xml”
Import-CLIXML “Backup Config.xml”
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

22. Developer Platforms

23. Windows Networking Manageability Based on WMIv2 and DMTF Standards
PowerShell Session
CMDletization
WMIv2 Client
Windows Management Instrumentation
WMIv2 Server
WS-MAN

24. Windows Networking Manageability Based on WMIv2 and DMTF Standards
PowerShell Session
WMIv2 Client
WMIv2 Server
CMDletization
WS-MAN
Get-NetAdapter is run in PowerShell
CMDlet generates WMI query
WMIv2 server returns network adapter objects

25. Leveraging Network Manageability in Windows
PowerShell Window
WMIv2 Client
WMIv2 Server
CMDletization
WS-MAN 1 2 3
Three major entry points that can be used by developers

26. Entry Point 1 - PowerShell
.NET PowerShell API
Rapid development using .NET APIs for PowerShell
PowerShell Window
WMIv2 Client
WMIv2 Server
CMDletization
WS-MAN
Script Directly
PowerShell itself provides a powerful framework for programming.

27. PowerShell via .NET
//Get-NetAdapter –CimSession remotemachine1,remotemachine2
PowerShell ps = PowerShell.Create().AddCommand(“Get-NetAdapter");
string[] cimsession_parameters= {“remotemachine1”,”remotemachine2”};
ps.AddParameter("cimsession", cimsession_parameters);
IAsyncResult async = ps.BeginInvoke();
foreach (PSObject adapter in ps.EndInvoke(async)) {
Console.WriteLine(result.Members[“IfAlias"].Value); }
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

28. Entry Point 2 – New APIs for WMI
.NET APIs
PowerShell Window
WMIv2 Client
WMIv2 Server
CMDletization
WS-MAN
Native APIs

29. Entry Point 3 – WS-MAN
3rd party WMI clients available for multiple platforms
3rd Party WMI Clients
PowerShell Window
WMIv2 Client
WMIv2 Server
CMDletization
WS-MAN

30. There are multiple entry points and frameworks for different scenarios and varied platforms for Networking Manageability

31. Possibilities of Windows Networking PowerShell
12/7/2018 6:48 PM
demo
Possibilities of Windows Networking PowerShell
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.

32. Optimizing for the Datacenter
We’re going to quickly show
Renaming network adapters
Configuring NUMA nodes
Marking IP addresses skip as source
Creating a Firewall rule

33. Creating a Virtual World
Internet
Intranet
Domain Controller
DNS Server
Internet Web Server (IIS)
Intranet Web Server (IIS)
Router
Corporate
Gateway
Client

34. Recap
Datacenters are trending towards lights-out management which requires remote management at scale
Windows Server 8 Networking provides scalable and simple remote management via PowerShell and WMIv2
Multiple developer frameworks provide many platform choices to access PowerShell and WMIv2 functionality

35. Call To Action IHVs OEMs Management Tools
Manage proprietary NIC advanced properties with NetAdapterAdvancedProperty cmdlets
Make sure NetAdapter and NetAdapterXXX cmdlets work on your products
OEMs
Optimize networking settings for specific scenarios and SKUs
Management Tools
Build upon Windows Networking PowerShell

36. Related sessions
[433] Network Acceleration and other NIC Technologies for the Datacenter
[644] Making your product manageable
[646] Manage a Highly Efficient Environment at Scale using Windows Management Framework (WMF)

37. Further reading and documentation
Link to MSDN
System.Management.Automation
System.Management
Contact info –

38. 12/7/2018 6:48 PM
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.
© 2011 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.