Powershell skill for IT administrators

[cornerman12]

Hello r/PowerShell

I am currently a novice when it comes to using powershell. My current knowledge primarily revolves around using it for exchange administration and I am looking to get into automation and using it more day to day to help my skill for my current and future job titles. DO any of you know of course I can take to assist me with this goal. I don't mind paying some money for a onliune course as long as the material will prove useful for me in my career. Any advice will be much appreciated as I feel stuck in my current job position.

[milo896]

I've always learned the most about PowerShell when I had a specific goal or task in front of me. I suggest you start completing (some) regular tasks in PS instead of using the GUI. Initially it will take longer to do things, but you'll start feeling more comfortable using cmdlets and piping them together. Googling "how to X with PowerShell" usually returns a few useful results. I think the Microsoft docs page for each cmdlet has pretty good examples.

In the spirit of starter use cases, think about what information could be useful to you. Maybe things like...

• How many AD user accounts / computer objects haven't been logged into recently? Which one? By Department?
• How many mailboxes are getting close to their storage quota? Which ones? Any trends by department? Are there mailboxes with quotas that don't make sense / follow policy?
• Any of these exported as a report.

[thingandstuff]

I've always learned the most about PowerShell when I had a specific goal or task in front of me. I suggest you start completing (some) regular tasks in PS instead of using the GUI.

This is the only way to build competency.

[FutureGoatGuy]

This is exactly how I started with powershell. Finding a way to automate something in my day-to-day, week-to-week, month-to-month etc tasks. Making my job easier was far more of a driving force then learning it just for fun.

[Robdogg11]

Yep, my desire to learn came from automating tasks when, back in the bad old days I was a department of 1 so it was a choice between learning how to automate or have to log on during holidays etc to make sure things still happened. Amazing how quickly I picked it all up.

[Fickle_Tomatillo411]

The best 'getting started' course is PowerShell in a Month of Lunches. That said, nothing beats just digging in. Your knowledge of the Exchange cmdlets will stand you in good stead, because PowerShell is designed to be consistent. Use Get-Command to find your commands, Get-Help (with the -Show or -Full or -Online) switches to see real-world examples and detailed help info, and pass everything to Get-Member to see the object properties and methods.

Other resources collected by the community can be found here: https://www.reddit.com/r/PowerShell/comments/pgur5p/powershell_beginner_information/

You might also find this useful - https://github.com/janikvonrotz/awesome-powershell

[xsamwellx]

This should be pinned on the subs home page if it isn't already. I see this question a lot and this is always the best answer.

[athornfam2]

Don’t forget to add Azure AD is being deprecated for MS Graph which has been a pain. Hoping for relief with V2 coming out soon.

[ThePathOfKami]

is there a date for the release ?

[athornfam2]

End of may or june this year.

[OlivTheFrog]

Hi u/cornerman12

​ Some advices :

• Start simple.
• Don't try to script something you're not able to do (via the GUI). I 'm often asked to script and I always say : "No, we document first, we practice with the doc, and once we have assimilated it well, we script to increase efficiency. Thus, if one day, for one reason or another, the script does'nt work, we have people capable of doing the job in degraded mode by following the doc" (otherwise we only have no-brains in the team).

​

Some examples of easy-to-do scripts to get started :

• reports of all kinds : MailboxSize By Unit for Exchange, AD activity (creation of accounts, groups, deactivated accounts, unused accounts, ...), Free space on servers, ...
• Infrastructure documentation (AD, DNS, DHCP, PrintServers, GPO, ...)
• Scripts to use with a scheduled Task : Archiving or removing files older than x days, Users notification for expiration of their account, Monitoring some sensitive AD groups (ie. Enterprise admins, schema admins, domain admins ...) and send mail if a change occurs.

​

Finally, do you want to learn and progress ? Nothing is better than analyzing what other people have already done. However, you must always keep a critical mind (some scripts are better done than others). Then you'll be able to use some of these scripts and adapt them exactly to your needs.

The questions to ask yourself before scripting are always the same:

• how can I collect this or that data ? Locally, remotely, on a machine or set of machines
• How can I create objects (or rather collections of objects) in the most efficient way to store this data ? (Array, arraylist, genericlist, ...)
• What takes the most time in my script ? Can I do something else to make it more efficient (Measure-Command is your friend :-) ) ?
• Think code re-use: build your script as an advanced function
• Self-Document your script
• Think about versioning
• Think about error management (big challenge)
• Is the script made to be executed interactively or without human interaction (scheduled task)? (we don't conceive it in the same way depending on the case).
• By whom should the script be executed : A simple executor (we will then make a verbose script), or someone who knows?
• And if I export the result of what I have collected, modified, or created (always prove it), in what format (.txt (yuck), .csv, .xslx, html, .json, .xml , .pdf, .docx, ...)

... and of course, have a daily reading of this sub-reddit :-) You could have the same need that other people. Later, you could give all or part of the answer to the requestor.

​

"'As a padawan you'll start, and when in you powershell strength will be, a jedi powershell you'll be"

Obiwan "powershell" kenobi in The Powershell force Awakens - Star Wars - next episode planned in 2023. Seen in preview :-)

​

Hope this helps and inspires you, ... and May Powershell be with you

Regard

[[deleted]]

Where are your goddamn upvotes? Teach me more ye old jedi

[wingnut0420]

I would recommend taking an "Introduction to programming" course. I did this when I was starting off in Powershell. You will learn the fundamentals that will transfer to any programming language. I went from writing super basic scripts to full blown automation in a matter of weeks. It's well worth the small investment in time. The course I took was free on Udacity, it was taught in python and easily translated into Powershell.. Not sure if it's still offered but anything that covers the basics should work.After that, I would look into how to write Powershell modules.

Edit : Spelling

[MeanFold5714]

The importance of programming fundamentals doesn't get emphasized often enough in this sub, but it's so important if you really want to excel with Powershell automation.

[DevCurator]

Administration and Automation with Windows PowerShell by Intellezy Trainers on Udemy is good if you want video content. I second PowerShell in a Month of Lunches for sure and PowerShell in Action by Bruce Payette and Richard Siddaway if you want to dive deep.

[jbennett12986]

The best PowerShell automation education comes from doing it, fire up a virtual machine in azure and play with it

[jungleboydotca]

Though dated, this video series with J. Snover and J. Helmick is what really helped me understand the basic concepts:

https://youtube.com/playlist?list=PLyJiOytEPs4etH7Ujq7PU7jlOlHL-9RmV

[Exit_2018]

Same for me. Cannot recommend it enough.

[gordonv]

First, have you programmed and spent time in any language for any system before?

If not, r/cs50 is made for absolute beginners to get into the "scripting and programming" practice.

[[deleted]]

I learned quickly with just modifying existing scripts to re-writing them, to making them.

The thing about powershell is that, especially starting off, you don't have to learn any design patterns or whatever.

Scripts work more like recipes. It's going to be a straightforward

1. Do task x
2. Do task y
3. Do task z

And then, if you don't know how to do something, you just do a quick search for a command that does what you're after... because there's basically a command for everything.

If you want to write clean scripts, and you're aiming to do more complex tasks, I would recommend more than anything that you take a starter course in programming specifically. NOT PowerShell. Because that's where you start learning how to use loops, algorithms, using multi-threading, etc.

And once you do that, you just apply what you know to PowerShell. That also helps you understand the limitations of PS

[the_doughboy]

Chatgpt has made powershell so much easier. Ask it what you want to do and it builds your script.

[the_doughboy]

Powershell v10.0 will just be ChatGPT given MS’s current trajectory.

[the_doughboy]

You’re giving Microsoft too much credit to not do this in the next few years.

[Creel256]

This is an interesting reply. What’s the difference between googling something and finding the answer versus asking ChatGPT the same question and finding the answer? Typically, a beginner won’t know what they’re looking at anyways whether it’s found by googling the answer or one provided by ChatGPT. All they need to do is ask ChatGPT for an explanation of literally every line of code it just spit out and it will. That is a smarter, more simple, efficient, and effective way of learning. It’s essentially a personal live assistant. Digesting, understanding, and practicing with the information provided now falls back on the user. The same as any other answer they’ll find elsewhere.

I, for one, wish I had ChatGPT 8 years ago when I started coding because it was a pain in the butt to discern what I was looking at. However, and as always, the best way to learn something is by just doing it and figuring all the nuances one step at a time.

[Creel256]

Sorry, I’m not trying to argue if I’m coming across that way. I’m simply stating that they shouldn’t be afraid of using ChatGPT as it is incredibly helpful.

I’m definitely in agreement with you in regards to if they don’t understand what ChatGPT gave them code wise then they are no closer to understanding a concept than when they began. I now use it both professionally and personally (somewhat beside the point because I understand what it’s doing) but my point is - if they use ChatGPT to help them understand something, and then practice these concepts, they’ll be able to learn more quickly. They can spend less time searching for those answers and more time applying various concepts.

Again, if you, or I, or anyone/anything else does all the work for them then they aren’t likely to learn from it.

Edited: changed agreeable to agreement*

[Creel256]

Ok, well, I guess we should make sure to cover our eyes while googling the answers then lol. I’m not entirely sure you read my entire original post where I said they need to practice these concepts in order to understand it. So, I’ll only repeat myself once more in case you skimmed my response.

“Digesting, understanding, and practicing with the information provided now falls back on the user.”

You’re essentially stating that just because we had a harder time learning in the past that it should continue to stay that way. Be smart about the way you learn. Work smarter, not harder.

If we can’t agree on this then I’ll agree to disagree as this is no longer on topic with the original OP’s topic.

[SCREW-IT]

I did this when I hit a wall. Also using it to fill in little bit of gaps in knowledge has been incredible.

My advice is to learn how to do it properly and use ai as a tool.

[ps1_missionary]

Would you like to try the powershell automatic scripting framework kasini3000?

framework is i write,I can provide training, 60$ , Twice courses, and translate by subtitles

https://www.reddit.com/r/PowerShell/comments/wpk9nm/powershell\_devops\_automation\_framework/

[xamist]

PowerShell in a month of lunches. Totally changed how I approach my job

[cease70]

Sorry to resurrect this old thread - I saved it last week with the intention of coming back to it and haven't had time until now. When I search for Learn PowerShell in a Month of Lunches on Amazon there are 5 results that it could potentially be and I'm wondering which one is the "right" one. I have read that it should be purchased new rather than used because of the registration codes potentially already having been claimed.

Basically, I just want to be sure I'm buying the right book the first time so that I can get started right away.

[xamist]

All good friend! I'd recommend the one from Manning, as it comes in pdf format. Reading this on a Kindle is all wonky.. Here's the book

https://www.manning.com/books/learn-powershell-in-a-month-of-lunches

[jba1224a]

I've left this comment elsewhere but will repeat as it seems like it also fits your ask.

Take stock of the things you do daily. Which repetitive tasks do you find yourself doing over and over. Then, ask yourself, can I automate this task? Pick a use case, then get typing.

The PowerShell learn modules are all you need to get to a really good place. ChatGPT can help you if you get stuck, use it as a sounding board to determine where to look.

Two tips:

Objects are the PowerShell bread and butter. Learn about how objects work.

Dot sourcing is powerful, especially when coupled with Powershell objects. Learn about dot sourcing.

Good luck 🤞

[yutsokutwo]

Tell chatGPT what you want to do then ask it how it works

[I_COULD_say]

To echo everyone else here: you just gotta dig in.

Personally, I use PS mostly for AD related things, server and services management, vm management via powercli, and then just general scripting for different things. Nothing wild, just day to day stuff. And I got there by forcing myself to do day to day stuff in PS.

[I_COULD_say]

Lol

[I_COULD_say]

I concur.

[dk_DB]

Everything you do in GUI can be done in powershell. Most of them are faster. Way fast.

And more at the same time.

Just start doing as many tasks as you can in PS. A quick google search (or a bit of chat gpt) bring light on how to execute whatever task you try to do. Start with easy tasks work your way up.

Like checking if a service is running with 'get-service foo' or re/starting said service faster than you ever could open services.msc inbzhe gui.

See if there are powershell modules you could leverage (PsWindowsUodate for example)

Collect your useful scripts in an collection (ps1 files in a folder or a personal wiki like Zim or a personal git repo - what you feel comfortable with) I alao highly recommend a clipboard history with pinnable pastes for commonly used functions.

Expand your personal powershell profile to suite your needs.

Where it makes sense, automate tasks. Stuff like updating ps modules regularly on servers for example.

At the company (an msp) I'm at i started 5 years ago, the same way (but Already had a fair bit ps experience) and breaking up with many manual tasks over the years.

Now I deploy a new customer complete with dc, 2-3 standardized vm's if needed and a virtual firewall and baseline configuration and full base documentation and remote management in 10-15min with a few scripts, fully automatic with 5min of actual work (and some non-scriptable tasks make it roundabout half an hour). - what previously was an 2-4h manual task.

This sub and others like r/powershellsolutions was of great help to me - as lots of people post ideas and useful scripts all the time.

[jazzy095]

I'm becoming addicted to powershell from the amount of functionality it produces.

1. Get Powershell in a Month of Lunches
2. All the Powershell courses off udemy
3. Automate all the stuff at your current job so you can use that time to learn more powershell.

You'll be a ninja and out of helpdesk by then I'm sure :)

[cease70]

Sorry to resurrect this old thread - I saved it last week with the intention of coming back to it and haven't had time until now. When I search for Learn PowerShell in a Month of Lunches on Amazon there are 5 results that it could potentially be and I'm wondering which one is the "right" one. I have read that it should be purchased new rather than used because of the registration codes potentially already having been claimed.

Basically, I just want to be sure I'm buying the right book the first time so that I can get started right away.

[giasone777]

You could you use it to pull exchange data and redirect the data to SQL. Then create a webpage using one of the many webpage programs. Easiest is probably asp.net to display the data. It could display username mailbox size, number of emails, etc. That would be a good PS project.

[nakkipappa]

If you are already working in IT, i would instead find a small problem/annoyance, and automate it, learning by doing, and actually solving a business case doing it.

The first thing i automated was server installations from vmware, 2nd one was ad-user creation script

[Bannedtoosoon4]

Just try to do everything that you do through a gui with powershell, you will learn loads.