With Windows 8 and Windows Server 2012, PowerShell v3 firmly establishes itself as the “go-to” choice for almost everything an IT administrator needs to manage the Windows operating system platform. Be it administration of storage disk pool, network configuration, remote access and control, security, group policy, Active Directory user or Branch Cache, there is (surely) a cmdlet* or two to fit your management needs.
Although still supported, the veteran netsh utility covering the networking, security and firewall space, is gradually going to make way for its cmdlet counterparts as evidenced here:
PS C:\Windows\system32> netsh
netsh>firewall
In future versions of Windows, Microsoft might remove the Netsh functionality
for Windows Firewall with Advanced Security.
Microsoft recommends that you transition to Windows PowerShell if you currently
use netsh to configure and manage Windows Firewall with Advanced Security.
Type Get-Command -Module NetSecurity at the Windows PowerShell prompt to view
a list of commands to manage Windows Firewall with Advanced Security.
Visit http://go.microsoft.com/fwlink/?LinkId=217627 for additional information
about PowerShell commands for Windows Firewall with Advanced Security.
netsh firewall>exit
PS C:\Windows\system32>
Starting with this tutorial, I am going to help get you up to speed with the essence of working with PowerShell v3 that really matters to IT Professionals, ease the pain along the way and bridge the learning gap towards efficient IT automation. What better way to begin than looking at common TCP and IPv4, IPv6 networking tasks? This works on Windows Server 2012 full GUI graphical version or Windows Server 2012 Server Core Edition, and Windows 8 client. No connectivity = no remote access ¿de verdad?
Continue Reading »
An der Worldwide Partner Konferenz 2012 (
