4 ms·

This may or may not work for you but it's now I forced myself to learn PowerShell. First you need to understand that PowerShell (because of WMI and .net snapin

by zupreme 10y ago

This may or may not work for you but it's now I forced myself to learn PowerShell. First you need to understand that PowerShell (because of WMI and .net snapins) can do literally anything that can be done on a windows environment either via click, keystroke, or code. Second you need to understand that PowerShell is an object-oriented scripting language. You can certainly use it in a procedural fashion, if you're so inclined, but you will be severely hobbling yourself in the process. Third you need to decide to write (or locate, test, and study) scripts to do a fair percentage of the things you might normally seek small single-purpose third party software to do. Want to scan your network for devices, use PowerShell. Want to bulk, edit AD users, do it in PowerShell. Need to clone a directory structure? You get the idea... Take this approach and look for legitimate reasons to use PowerShell every day.

selmat 10y ago
Seconded. In my last job i automated all tedious tasks via powershell. Need to verify connectivity and documentation accuracy (credentials, snmp strings, vendors, versions...)? Powershell is solution for me. Even tcl scripts was parsed, compared and exported to xls with Powershell. Verify and implement configuratiom template was another case where powershell was solution. For me this is my strongest weapon on windows automation and system management. And i like it beacuse you can edit in notepad++, sublime, atom, whatever...save... a run ps1 file. No insane and complex IDE needed, no compilers. If you need you can do exe files. It's dirty solution, but it works. My last project (app for coffe shopps and restaurants) is written in powershell. "The biggest issue" for me is support of my scripts on windows with lower version of powershell or .NET In regards to original question. "Powershell in action" is my favorite resource about powershell.

by zupreme 10y ago

selmat 10y ago

Seconded. In my last job i automated all tedious tasks via powershell. Need to verify connectivity and documentation accuracy (credentials, snmp strings, vendors, versions...)? Powershell is solution for me. Even tcl scripts was parsed, compared and exported to xls with Powershell. Verify and implement configuratiom template was another case where powershell was solution. For me this is my strongest weapon on windows automation and system management. And i like it beacuse you can edit in notepad++, sublime, atom, whatever...save... a run ps1 file. No insane and complex IDE needed, no compilers. If you need you can do exe files. It's dirty solution, but it works. My last project (app for coffe shopps and restaurants) is written in powershell. "The biggest issue" for me is support of my scripts on windows with lower version of powershell or .NET In regards to original question. "Powershell in action" is my favorite resource about powershell.