When Microsoft launched Windows Server 2012, one of the most talked about changes was the increased reliance on PowerShell scripting. With more than 2,300 cmdlets to pick from, Windows administrators have the chance to take advantage of Windows PowerShell cmdlets and automate tasks more simply than ever before.
We compiled the best tips that put the spotlight on what makes Windows PowerShell cmdlets work so well in Windows Server 2012. We included one expert's argument for why PowerShell is the best scripting language as well as tips that highlight what cmdlets admins can use for tasks like troubleshooting clusters, administering Group Policy and managing Hyper-V 3.0.
Table of contents:
Why is PowerShell better than CMD and Bash?
Our expert tells readers why he thinks PowerShell is the best choice when it comes to a scripting language and how its capabilities far outweigh those of CMD and Bash.
Multi-server management made easy with cmdlets
With remote management enabled in Windows Server 2012, admins shouldn't be surprised that using Windows PowerShell cmdlets in the latest version of Windows Server is the preferred way to locally and remotely manage multiple servers.
Failover cluster cmdlets expand in Windows Server 2012
Although Windows Server 2008 R2 started to take advantage of the power of Windows PowerShell cmdlets, there are 81 failover cluster cmdlets in Windows Server 2012 that can manage tasks like adding new scale-out file servers.
Cmdlets that can ease Group Policy administration
Some admins may prefer their GUI when it comes to administering Group Policy, but there are PowerShell cmdlets in Windows Server 2008 and Windows Server 2012 that make administering Group Policy easier for admins, including Get-GPO and Get-GPPermissions.
Cmdlets that manage Hyper-V Replica, extensible switch
Having PowerShell management built right into Windows Server 2012 helps make Hyper-V 3.0 a solid product for admins, especially with cmdlets that can script and automate daily tasks for Replica and the extensible switch.
The cmdlets that configure virtual switches in Hyper-V 3.0
With Windows Server 2012, PowerShell switch cmdlets for Hyper-V 3.0 extensible switches take the tedium out of automating and configuring hosts. Some added benefits include cmdlets that support the virtual switch and work over PowerShell remoting, where an administrator can connect a local PowerShell session with a session running on a remote system.
Using cmdlets to help with Hyper-V operations
This tip highlights the differences between Windows PowerShell cmdlets in Windows Server 2008 R2 Hyper-V and Windows Server 2012 Hyper-V while looking at the operations that PowerShell cmdlets in Hyper-V can work well with.
Still need more information on PowerShell and Windows Server 2012?
If you want to learn more about the features in Windows Server 2012, or if you just need more details about what's in PowerShell v3, be sure to check out these guides.