Powershell

Also would it be worth it to learn C++ or .NET to help learn powershell and become a better admin/script writer?

>>56254850
Powershell is almost literally .NET in shell form. You can even load .NET dlls into a Powershell script and leverage its objects/functions directly. So if you care about Powershell, you will want to care about .NET for sure.

The real question is, why the fuck bother with Powershell? Every instance I've seen of someone using Powershell is either to prototype some kind of workflow or used as a stopgap for a more permanent solution later. If you want to go the .NET route, just learn C# and make C# applications, don't bother with Powershell.

>>56254885
Mainly for automating my Sysadmin work/Writing more advanced automated scripts in the future

>>56254843
I do a fair amount of Hyper-V automation in PowerShell. Learn how to work with the Windows unattended.xml. It's a good starting point.

>>56254885
PoweeShell is great for sysadmin work.

It's best feature is its ability to perform ops on a domain/ad.

>>56254899
Perhaps it has more use in that context, my experience with Powershell has been in the form of engineering utilities. The company I work for right now has a ton of them floating around to do all sorts of things, but they've been converting them all into C# because they just got so damn complex that no one could maintain the spaghetti script anymore.

Just keep your scripts relatively small and succinct. You will absolutely hate yourself if you make some 10000 line script file and then two years later something breaks and you have no idea what's going on anymore.

>>56254843
Powershell is not fully free software, most of it was free'd up but there are still blobs and proprietary licenses in it, if you want a good shell you should try ZSH, Bash or MXSH (Google Fuchsia shell)

Anyone have any links for good PowerShell learning resources?