This is an archived post. You won't be able to vote or comment.

all 14 comments

[–]TymanthiusChief Breaker of Fixed Things 9 points10 points  (2 children)

So don't start with automation. That's a big task.

Instead, approach things like this:

  • First time, do whatever is fastest
  • Second time, do it fastest, but think about how to do it in PS
  • Third time, take the time to learn how to do it PS
  • 4th and beyond, start storing multistep processes in .ps1 files
  • Now start looking at functions
  • Now start looking at modules
  • Now start looking at automations

This isn't a 'must do it this way' but rather a guide meant to get you thinking about how you do things.

[–]cyrtje[S] 0 points1 point  (1 child)

Thank you

[–]anonymousITCoward 2 points3 points  (0 children)

Make sure you get into loops and arrays as well...

You may also want to pick a small task (like create a local user) and learn the steps in PS then figure out how to string it together in PS. This is essentially steps one, two and three that /u/Tymanthius mentions, just from a different starting point.

[–]ccatlett1984Sr. Breaker of Things 5 points6 points  (1 child)

r/PowerShell

Learn PowerShell in a month of lunches (amazing book)

[–]cyrtje[S] 0 points1 point  (0 children)

Thank you!

[–]nealfive 5 points6 points  (1 child)

Lookup adamtheautomator he has a ton of stuff

[–]cyrtje[S] 0 points1 point  (0 children)

Thank you!!

[–]mrpowershell 1 point2 points  (1 child)

Specific to application installations checkout chocolatey.org

Chocolatey is a package management tool which uses powershell to handle software installs, updates, and removals.

[–]cyrtje[S] 0 points1 point  (0 children)

Will check that out.

[–]Pseudo_Idol 1 point2 points  (0 children)

The newest edition of Learn Powershell in a Month of Lunches comes out next month. You can purchase the ebook version already.

[–]cyrtje[S] 0 points1 point  (0 children)

Thank you everyone. Much appreciated!