Best products from r/PowerShell
We found 99 comments on r/PowerShell discussing the most recommended products. We ran sentiment analysis on each of these comments to determine how redditors feel about different products. We found 51 products and ranked them based on the amount of positive reactions they received. Here are the top 20.
1. Learn Windows PowerShell in a Month of Lunches
- Nylon ripstop upper with lightweight welded synthetic overlays
- Adjustable hook-and-loop instep strap
- Breathable mesh lining
- Padded tongue and collar
- Grippy rubber FastLift outsole
Features:
2. Learn Windows PowerShell in a Month of Lunches
- Used Book in Good Condition
Features:
3. Clean Code: A Handbook of Agile Software Craftsmanship
- Prentice Hall
Features:
4. Learn Windows PowerShell in a Month of Lunches
- Nylon ripstop upper with lightweight welded synthetic overlays
- Adjustable hook-and-loop instep strap
- Breathable mesh lining
- Padded tongue and collar
- Grippy rubber FastLift outsole
Features:
5. Windows PowerShell Cookbook: The Complete Guide to Scripting Microsoft's New Command Shell
- Used Book in Good Condition
Features:
6. Learn PowerShell Toolmaking in a Month of Lunches
- Vintage Twilight Style PU Leather Pencil Case
- Durable, washable canvas construction features upper and lower flaps to keep pencils in place and protect the tips
- Bag to hold pens, pencils and multiple other uses
- Size:21*8cm
Features:
7. Windows PowerShell 3.0 Step by Step (Step by Step Developer)
- Used Book in Good Condition
Features:
8. xUnit Test Patterns: Refactoring Test Code (Addison-Wesley Signature Series (Fowler))
10. Deployment Fundamentals, Vol. 6: Deploying Windows 10 Using Microsoft Deployment Toolkit
- Used Book in Good Condition
Features:
11. Secure By Design
- √【BRAND GUARANTEE】- MILISENTE is American Brand, our design is high quality & fashionable, This clutch purses for women posted were doing market research which is matching most ladies favorites
- √【ELEGENT FEATURES】- THis flower evening bag(7.9*2.4*4.7 inches), made of quality fabric decorated by multicolored 3D flowers (such as glitter sequins flowers, crystal flowers, beaded flowers). All of them are sturdy sewing on the elegent clutch purse. And it totally matches your party,gala,ceremony,prom, wedding occasion
- √【SPECIAL DESIGN】-Top Sparkling triple diamond clasp closure with rhinestones.It is easy to open and close. In addition, A large ca[acity appears inside the clutches. Suitable and convinient for many mini makeup thing, fit in 5.8 inches phone and cards
- √【ACCESSORIES UPDATES】- Each evening clutch, attching Stronger gold metal Wristlet thin Chain. Meanwhile, an upgrade for stronger metal shoulder/Crossbody chain. It stays sturdy and won't snag your dress
- √【SERVICE GUARANTEE】- Any defective problem happened on our flower clutch purse, we promise to send you a same new handbags for replace or refund . Have any questions and suggestions? Just contact us by email. Our customer service team is always be here to help you solving the problem within 24 hours
Features:
12. Writing Secure Code (Developer Best Practices)
- √【BRAND GUARANTEE】- MILISENTE is American Brand, our design is high quality & fashionable, This clutch purses for women posted were doing market research which is matching most ladies favorites
- √【ELEGENT FEATURES】- THis flower evening bag(7.9*2.4*4.7 inches), made of quality fabric decorated by multicolored 3D flowers (such as glitter sequins flowers, crystal flowers, beaded flowers). All of them are sturdy sewing on the elegent clutch purse. And it totally matches your party,gala,ceremony,prom, wedding occasion
- √【SPECIAL DESIGN】-Top Sparkling triple diamond clasp closure with rhinestones.It is easy to open and close. In addition, A large ca[acity appears inside the clutches. Suitable and convinient for many mini makeup thing, fit in 5.8 inches phone and cards
- √【ACCESSORIES UPDATES】- Each evening clutch, attching Stronger gold metal Wristlet thin Chain. Meanwhile, an upgrade for stronger metal shoulder/Crossbody chain. It stays sturdy and won't snag your dress
- √【SERVICE GUARANTEE】- Any defective problem happened on our flower clutch purse, we promise to send you a same new handbags for replace or refund . Have any questions and suggestions? Just contact us by email. Our customer service team is always be here to help you solving the problem within 24 hours
Features:
13. SCFM: Secure Coding Field Manual: A Programmer's Guide to OWASP Top 10 and CWE/SANS Top 25
15. Windows PowerShell Cookbook: The Complete Guide to Scripting Microsoft's Command Shell
- O Reilly Media
Features:
17. Learn PowerShell Scripting in a Month of Lunches
- Size RECOMMEND:US 4/6(Small), US 8/10(Medium), US 12/14(Large), US 16/18(X-Large),US 20 (XX-Large)
- Above Knee,Wrap V Neck, Half Sleeve, Zipper at Back
- Floral Lace Retro Elegant Style, Suit for Evening,Cocktail,Wedding Party and Formal Occasion
- Please Note that This Dress is Stretchy and Please Refer to the Size Chart in Left Product Description Picture
- Care Instructions: Please Put The Dress Into A Laundry Bag For Wash It With Low Temperature and Iron Carefully in Low Temperature Too
Features:
18. Windows Server 2016 Automation with PowerShell Cookbook: Powerful ways to automate and manage Windows administrative tasks, 2nd Edition
- [Durable maintaince and replace support] Provided by LK to ensure the maximum protection for the life of your screen protector.
- [Smart Film Tech] Self-healing properties enable the film to recover from minor scratches over time to keep your watch looking great.
- [High Response] 0.1mm thickness provides a quick and smooth touch response, ensuring quick app launching.
- [Ultra HD] 98% high transparency keep original color and brightness of the watch screen.
- Include 6pcs Flexible Clear TPU Film Screen Protector Compatible with Apple Watch Apple Watch 40mm Series 6 SE Series 5 Series 4 and 38mm Series 3.(Item Dimension: 34.02mm*28.14mm*0.18mm)
Features:
Hey /u/Dude_with_the_pants! So this is a wall off text now that I've written it..sorry about that but honestly when I start talking PowerShell I can go on forever (as my peers at work can attest). So I hope this is kind of useful for you.
So you're looking for some real-world examples...so here goes from where I sit. I've been using PowerShell since it was in beta...so a long time. Prior to PowerShell I was a point-n-click guy. No scripting experience (beyond embarrassingly bad batch files). I'd open VB scripts and kind of zone out. PowerShell really opened a door for me. For the past 20 years I've been working for some really large companies (5,000 - 160,000) as an Exchange\AD guy with my current stint...about the last 13 years or so, I've worked for the same company. This has been an evolution of sorts, but ever since PowerShell v1.0 dropped in my lap during the Exchange 2007 beta I was hooked and started to automate and built tools.
This was a long time ago now, so my skills and uses have matured quite a bit (at least I'd like to think so). Looking through this thread you've already gotten a lot of really good responses. In terms of using PowerShell and where to start I like what others have said. When you reach for the mouse and start clicking on stuff to complete a task, note somewhere what that task was and then when you have down time, look up how to do it with PowerShell. Odds are really good, especially now, that there is a way to do it with PowerShell. If I may be so bold, but I'd recommend taking a look at Learn Windows PowerShell in a Month of Lunches. I recently did a manuscript review of it for the publisher which required me to slowly read through every single page. It's a good staring point and I highly recommend it.
That all said, daily PowerShell usage.. So I've spent the last decade automating and tool-making which my employer has really taking a liking to (not sure why, but I enjoy myself). Here are some examples of what I've done with PowerShell:
For day-to-day stuff, not long ago I needed to query the Windows time configuration status of all our domain controllers. Using remoting this was trivial. If you had 2 DC's then I guess it isn't a big deal, but for us fanning out through remoting to audit this data is absolutely necessary. I find remoting is a quality of life kind of thing. Yes I could RDP into something, but 9/10 times it is way faster to just run
Invoke-Command -ComputerName machineName -ScriptBlock {do something}
So day-to-day, for what I do, I'm honestly writing tools or working in automation projects 90% of the time. I only get into the shell to do something if something is really broken and none of my automation tools have already handled it. Not everyone has that luxury (and it is btw). If I was you I'd look for every opportunity to learn how to do stuff with PowerShell. I think you'll find that in most cases it will free you up to do other things. It'll be awkward at first as you fumble around, but you'll soon find ways to speed things up.
I wouldn't be too obsessed with just looking at remoting stuff. It's true that this does expose some of the power of ..well.. PowerShell, but there is sooo much more to it. Look for ways to improve your daily life. Jot down the stuff you do a lot (and repeatedly). Those are your prime targets. It could even be something as simple as processing your mail in the morning. If there are certain patterns you follow and do a lot of...you can absolutely hook in PowerShell into that too if writing Outlook rules won't do what you need (I've done this too).
Good luck and happy shelling!
The smaller the better. From a development point of view there is a lot of god materials on writing clean code that is easy to read, work with and maintain. (https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882/ref=sr_1_1?ie=UTF8&qid=1468632974&sr=8-1&keywords=clean+code)
I break everything into smaller functions. Each function gets it's own file. The vast majority of my functions and scripts fit on one screen (once you get past the help and parameters). You build a library of functions that are very easy to find. Because the name of the file is the name of the function, I can look at a tree view of the folder and see all of my functions and go right to it.
When you use source control, you have all the changes and edits very cleanly defined. All the comments are more localized to that file. If you have pester tests, it is easy to pair them up and know you have coverage. If you need to track down a old version of a function, it stands on its own. You can much easier tell the last time that piece of code was changed. (even if you are looking at filesystem based backups.
These functions become reusable as modules and only have to exist once. If you copy the same functions over and over into other scripts, then you also copy bugs around. If you fix something, how do you know you fixed it everywhere it was used? If it is a standalone function in a module, improvements to that one file benefit every script that uses it (This is where you benefit from automated tests).
When you have small functions, your nesting is less deep. Your variables are also tighter in scope. This means you can use very basic simple variable names. You can call that thing
$user
and get away with it. Those giant scripts are full of$userName
$tempUser
$userObject
$user2
$newUser
$ADUser
$userList
and the longer the script, the more creative you have to get. Also in smaller functions, you can see the initiation of all the variables are you using on the same screen that the code using it is on.The monolithic file works great when you are just in the zone and laying out code. For those 2-6 hours, you have the whole script in your head. Scrolling around is not a big deal. But when you return to it, that mental map is gone. You have to scroll all over to see what is going on. Often you will see giant blobs of comments telling you to stop scrolling.
The smaller the better and each in their own files. However small your functions are, they are still too big. My functions are about 1/3 help, 1/3 parameters and 1/3 code. I'll stop ranting there. But you get my point.
Learn PowerShell in a Month of Lunches is one of the most widely-recommended books on starting PowerShell. I'd recommend following along and physically typing commands in to see what happens - don't just read it.
Alternatively, if you've got the time, one of the most comprehensive introductions is the Microsoft Virtual Academy course on PowerShell 3.0. Don't worry - even though PowerShell 5.0 has been released, this is still very relevant information. It's long - almost 8 hours of videos - but these guys know what they're talking about and they explain it quite well.
Beyond that, check out the resources in the sidebar of this sub. There are a couple other intro books and guides, as well as a lot of script resources to look at.
Finally, once you have a feel for what the language is, the best way to discover what the language can do is to find something you already do a lot, and figure out a way that PowerShell can automate that process. It sounds like your senior engineers have some examples of this already, but don't be afraid to expriment. I have to produce a lot of Excel reports, so the PSExcel module for PowerShell lets me automatically create those reports.
Hope that helps!
As a beginner (still am), I have found the easiest way to learn is to just dive in using Powershell for any tasks that you do during your normal day (especially the repetitive ones).
With that said, I have found it highly beneficial to use a couple resources:
To be honest, the most important tip in my opinion to learn how to use PS is the get-help command. This will teach you how to use just about every command out there minimizing most questions that you are looking to ask. A second tip: Learn what it means to "Pass by value" and "Pass by Property Name." This will help you immensely when combining commands using the pipeline.
Quick warning: Powershell will quickly get addictive. Also, it is a community where people enjoy sharing and giving back.
Last note, I swear. Learn shortcuts. It will save you a HUGE amount of time (i.e.like hitting esc on your keyboard to clear the line.)
I'm not sure why it's not running, but you should think about changing your if-elseif to a switch statement. Here is a link that will explain it more. In this script it won't make much of a difference, but eventually you will begin to do more things with Powershell, and it's better to start with good practices before making bad habits.
I recommend this book. I haven't read it, but I have heard many good reviews on it from many different people.
Hope that helps some, and enjoy Powershell. It will really assist you as an admin, and it is very powerful once you start to understand the basics of how to work with it.
Okay, /u/kd9333, don't take this the wrong way, but have you considered brushing up on some POSH basics, maybe something like PowerShell in a Month of Lunches. You have been asking a lot of questions about this script (and general PowerShell questions) in the past few weeks, and honestly, some of your responses are literally you asking people to do 100% of the work for you, even after they point you in the right direction.
Many people are willing to help you learn PowerShell, but many of the questions are you asking are pretty basic, and they would likely be answered if you took the time to really learn the basics of the language. That, plus a few questions that look like homework make me question if this is just us doing schoolwork for you or if this is an actual question you need assistance with.
To your question, you don't need to type your date field as
[datetime]
when you send it toOut-File
. It's already in that format. You will likely want to convert it to a string before hand using either a method or a format operator so that it is in the format you want.This is great. i'd like to add:
- it's very handy to keep your unit tests and integration tests in separate files like ModuleName.Unit.tests.ps1 and ModuleName Integration.tests.ps1 to keep things organized as your tests grow over time. If you don't do this, someone reading your code may have to read through every test to determine if a system is being changed each time they are executed.
- When writing integration tests, I've found the pester commands BeforeEeach and AfterEach are very useful for adding live data into external systems before executing the test itself. Some examples might be: Inserting rows into a database, creating AD objects or creating a file. Once the test has completed, the AfterEach function should be used to cleanup or fix any data that may have been left as a side effect of the test. (You might want to clone parts of your prod environment into an isolated test environment using powershell )
- Unit tests should be run frequently and finish executing extremely quickly (ideally in milliseconds.) Integration tests will take longer because they are supposed to deal with external systems/the outside world.
- Automated tests can themselves be refactored to keep them DRY and maintainable.
- It's fine to write utility functions to assist with reducing the amount of test code, as long as readability is not affected at all. "Clever" test code is so much worse than "clever" code without any tests. Been there, done that.
- I haven't properly dived into the Pester / classes problem yet but it looked messy a few years ago and required boilerplate. Would love to hear more about this.
- Object dependencies from 3rd party code is a separate issue, but they will be Integration tests. If objects don't have public constructors / interfaces then they weren't designed to be mocked or tested. Some code may not be possible to test.
For reference:
A really good book i've been reading is xUnit Test patterns: https://www.amazon.com/xUnit-Test-Patterns-Refactoring-Addison-Wesley-ebook/dp/B004X1D36K/ref=mt_kindle?_encoding=UTF8&me=
And the classic Working Effectively with Legacy Code which is amazing https://www.amazon.com/Working-Effectively-Legacy-Robert-Martin-ebook/dp/B005OYHF0A/ref=pd_sim_351_3?_encoding=UTF8&psc=1&refRID=JQG9XXQCMQ2R1K56JNWC
MDT (Microsoft Deployment Toolkit) is your best option. Free and a large user community. Get a book to help you understand the concept. https://www.amazon.com/Deployment-Fundamentals-Vol-Deploying-Microsoft/dp/9187445212 is a great book to get you started. You DO NOT need a deployment server. Just a network share will work. You then use your workstation to create the deployment. The boot media will boot and point to the network share. Look at the Deployment bunny and other MDT focused sites for more help.
For my situation, my helpdesk use scripts I've created on a daily basis to make new users, terminate users, and check on what locks people out. Small things like this make a 10-30 minute task take seconds which frees up a lot of time. If you're really wanting to learn powershell and have very little knowledge of it, I recommend picking up "PowerShell in a Month of Lunches". It will give you a good idea on how to export and import data. If I remember correctly it also gets into loops which helps immensely.
PowerShell takes time to learn, but if you want to learn it, I recommend googling how to do whatever task you're trying to do in powershell. Maybe don't do it at the time the task needs to be completed if you're understaffed and overwhelmed. But definitely go back and learn how to do it in PowerShell. After some time doing this, you'll be surprised at what you can accomplish when it comes to tasks involving all of your users or at least a good handful of them.
It's alway sa asgood thing to see different per spectives on a given topic or strategy.
However, how do you see your offering as being different, more informative, etc., than the courseware the SANS.org offers on the topic...
https://www.sans.org/webcasts/purple-powershell-current-attack-strategies-defenses-109700
... or the Secure Code strategies that have been in play via the MS SDL (Secure Development Lifecycle) for the last couple of decades?
>About Microsoft SDL
>
>https://www.microsoft.com/en-us/securityengineering/sdl/about
>
>Microsoft Security Development Lifecycle (SDL)
>
>https://www.microsoft.com/en-us/securityengineering/sdl
>
>SDL Resource List
>
>https://www.microsoft.com/en-us/securityengineering/sdl/resources
>
>Writing Secure Code (Developer Best Practices) 2nd Edition, Kindle Edition
>
>https://www.amazon.com/Writing-Secure-Code-Developer-Practices-ebook/dp/B00JDMP718/ref=sr_1_2?keywords=secure+code&qid=1555311132&s=gateway&sr=8-2
>
>Secure By Design 1st Edition
>
>https://www.amazon.com/Secure-Design-Daniel-Deogun/dp/1617294357/ref=sr_1_1?keywords=secure+code&qid=1555311132&s=gateway&sr=8-1
>
>SCFM: Secure Coding Field Manual: A Programmer's Guide to OWASP Top 10 and CWE/SANS Top 25
>
>https://www.amazon.com/SCFM-Secure-Coding-Manual-Programmers/dp/1508929572/ref=sr_1_4?keywords=secure+code&qid=1555311132&s=gateway&sr=8-4
Though there are particluars to a given language, and none of the above are PowerShell specific. The SDL thought, design and implemention relative to a give goal is the same.
Now, the real issue here is all the noise about PowerShell hacking and org leaders using that as the excuse to not allow PowerShell, without fully realizing that the use of PowerShell is a post exploit thing. The hacker got into your system another way, that was not properly defined, managed, protected, understood and or reacted to.
​
Also, there are whole websites and business offering conver Defensice PowerShell, and PowerShell forRed/Blue/Purple Teams.
Example:
https://devblogs.microsoft.com/powershell/defending-against-powershell-attacks/
http://www.defensivepowershell.com/
https://artofpwn.com/offensive-and-defensive-powershell-ii.html
https://adsecurity.org/?tag=powershell-defenses
https://devblogs.microsoft.com/powershell/powershell-security-at-derbycon/
https://nsfocusglobal.com/Attack-and-Defense-Around-PowerShell-Event-Logging
​
Learning how to attack with adn defend against, grants one greater edification on how they need to be thinking about writing and using PowerShell.
But good article. Looking forward to the rest.
Would I create new lines below that one for the other OUs?
No, absolutely not. :)
The line I wrote is all you need.I'll try to explain it line by line.
​
$data = Import-Csv -Delimiter "," -Path C:\temp\data.csv
This line will import csv data from path C:\temp\data.csv into variable $data and it will use , as delimiter.Run it on your data and then run just $data to check what is inside your new variable.
$OU = ($data | select OU -Unique).OU
This line will select only OU column from your csv data in variable $data and it will select only unique values, so if you have users that are in same OU it will not duplicate it.After you run it check what's inside your variable by call it $OU.
​
Now we come to foreach loop.
foreach ($item in $OU) { New-ADOrganizationalUnit -Name $item -Path "dc=contoso, dc=com" }
It does exactly what it say, for each item, value inside variable OU it will run following code
New-ADOrganizationalUnit -Name $item -Path "dc=contoso, dc=com"
So let pretend you have this inside your variable OU.$OU
Finance
Accounting
Sales
IT
Quality
​
If we were to ran this code:
foreach ($item in $OU) { Write-Host "test" }
This would be the result in my terminal
test
test
test
test
test
Since we have 5 items inside $OU and command Write-Host "test" will be ran 5 times.
Now if I were to ran this code:
​
foreach ($item in $OU) { Write-Host "$item" }
This would be the result in my terminal
Finance
Accounting
Sales
IT
Quality
​
It will take each item from OU and output it to terminal.
​
I hope that makes it clear for you why all you need is this one line.
New-ADOrganizationalUnit -Name $item -Path "dc=contoso, dc=com"
​
If you really want to learn powershell and not just finish you project I strongly suggest this book:
Learn Windows PowerShell in a Month of Lunches
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617294160
​
It's great book, really accessible and written in such approachable way that I guarantee if you finish it, you will understand and know powershell basics. :)
If you are more video guy this is old but great video series that will explain powershell basics.Big plus it's Jeffrey Snover talking about powershell. Can't beat that with a baseball bat :)
https://www.youtube.com/playlist?list=PLyJiOytEPs4etH7Ujq7PU7jlOlHL-9RmV
I'd also recommend Windows PowerShell Cookbook Scripting but it isn't cheap ether. I've always found cookbooks useful because they are just a bunch of examples of how to create tooling once you know the foundation for anything. I'd also recommend reading some of the Powershell MVPs blogs they do some excellent content for the community. I learn a lot from them as well.
Hi!
I keep a list of resources I've found helpful for learning PowerShell here. Books, cheat sheets, videos, etc.
Highlights (from my perspective)
If you prefer videos:
If you prefer books:
If you learn by example:
Stop by #powershell on IRC (Freenode), and check out twitter. Many folks idle or chat in the IRC channel, and from my perspective, you can't beat twitter for up to date PowerShell content.
If you want to see the vision for PowerShell, check out the Monad Manifesto
Good luck!
> Is there any prior knowledge needed and if so what?
No prior knowledge needed. Of course, if you have experience with other scripting languages and some core concepts (if statements, variables, etc), it certainly helps.
> Just wondering if there is a best practice for newbies of powershell?
Try to think of something you want to do. It could be as simple as creating folders that have a unique name (like based off the date created), but the more you practice even mundane tasks in Powershell, the more you are going to learn about how it works and how to make it do what you want.
> If anyone could recommend some resources to help me get started that would be greatly appreciated.
There is no shame in going onto Google and searching for Powershell scripts that others have made. If you do take this approach, I would recommend trying to break down and analyze what the script is doing with each command and line. Also, this book really helped me get my foot in the door (well worth the ~$36):
The book makes no assumption on where your skill level is at and starts explaining concepts from the entry level. (what is Powershell, how the commands are structured, how to make a variable, etc.)
PowerShell in a Month of Lunches is kind of the defacto starter book.
From there, I would recommend diving into The PowerShell Scripting and Toolmaking Book.
Naturally, this sub is also an excellent resource. You could also join the PowerShell Slack, where tons of good discussions/examples can be found.
It took me a while to get good at PowerShell and I had a pretty extensive programming background prior to trying to learn it.
The Exchange cmdlets are also less than ideal when trying to learn... but it was also my first experience with PowerShell. They're usually pretty slow to run and aren't great from a syntax standpoint. The AD and file system cmdlets (
Get-ChildItem
/Get-Item
) are more consistent, faster, and generally easier to work with.Trial and error, as well as looking at code examples on /r/PowerShell is the way I ended up learning. You'll notice on /r/PowerShell people usually post very different ways of solving a problem and one isn't necessarily better than the other, but just use different features or logic.
PowerShell in a month of lunches is usually the recommended book / guide.
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080
https://www.youtube.com/playlist?list=PL6D474E721138865A
The best PS book I've come across is Learn PowerShell in a Month of Lunches: https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617294160/ref=sr_1_1?ie=UTF8&qid=1535785632&sr=8-1&keywords=powershell+month+of+lunches
​
Also, keep an eye out for the authors in blog posts as you're Googling. Don Jones and Jeff Hicks are both really active on Powershell.org as well as Pluralsight.com.
if you're just starting out i recommend these books in order
http://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080
http://www.amazon.com/Windows-PowerShell-Action-Second-Edition/dp/1935182137
https://www.manning.com/books/learn-powershell-toolmaking-in-a-month-of-lunches
*edit: i haven't read this one, but I'm sure it's worth a look if you're interested. it's written by the scripting guy himself, ed wilson.
http://www.amazon.com/Windows-PowerShell-3-0-Step-Developer/dp/0735663394
Grab Don Jones' PowerShell in a Month of Lunches, it's well worth it, and an easy way to become proficient. That said, Ed Wilson's Hey Scripting Guy blog is also a fantastic resource.
not a problem. Google and ms technet are your friends.
I have heard great things about
beginner level:
http://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617290211/ref=sr_1_1?ie=UTF8&qid=1323979474&sr=8-1
more of an intermediate/advanced:
http://www.amazon.com/Windows-PowerShell-Cookbook-Scripting-Microsofts/dp/0596801505/ref=sr_1_1?ie=UTF8&qid=1323979485&sr=8-1
I was like you no programming experience at all. I learned from these videos, I suggest you download them as MS is decommissioning this site soon.
and everyone will recommend reading Learn Windows PowerShell in a Month of Lunches although I'm not a big reader and have not gone through most of this book. The two video modules will give you a good start. This reddit has also helped ALOT.
I was in the same boat as you when I first started learning PowerShell. I had experience in C++, C and Java. I bought The Windows PowerShell Cookbook to use as a reference and just started to wing it. It helped that I'm a sysadmin at a large company and I'm pretty much left to my own devices as long as I get my tickets and projects done. Each time I'd want to do something in PowerShell, I'd just plunk away at it. I'd use Get-Help, the reference book, and Google to help me along. A lot of it was just thinking about how I'd do something in another language, then figuring out the equivalents in PS.
When I first started, I would write structured scripts, but now I pretty much do everything on the command line.
Learn Windows PowerShell in a month of lunches is a great start!
https://www.amazon.com/dp/1617294160
That walks you through some of the basics.
Once you feel comfortable using Get-Help and Get-Member, you should be able to slowly work through any problem that you want to solve, by reading documentation on each cmdlet via get-help and analyzing objects with get-member.
PowerShell.org free ebook: Secrets of PowerShell Remoting
There is also more information in the books PowerShell Deep Dives or PowerShell In Depth.
Not only because they explain how remoting works thoroughly, but because they also will cover the security aspects as well as remote session configuration files, which you can use for various aspects of your remoting.
Start with this:
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617294160/ref=sr_1_3?crid=26462OWKXC9YH&keywords=learn+windows+powershell+in+a+month+of+lunches&qid=1568013284&s=gateway&sprefix=learn+windows+%2Caps%2C231&sr=8-3
Then this:
https://www.amazon.com/Learn-PowerShell-Scripting-Month-Lunches/dp/1617295094/ref=sr_1_4?crid=26462OWKXC9YH&keywords=learn+windows+powershell+in+a+month+of+lunches&qid=1568013284&s=gateway&sprefix=learn+windows+%2Caps%2C231&sr=8-4
And finally this:
https://leanpub.com/powershell-scripting-toolmaking
​
I'd also recommend spinning up a virtual environment with at least 1 server and 2 workstations. Windows Server 2016 and Windows 10 Enterprise both have evaluation editions you can download and install for free.
The best way I found to learn something is to find a project that relies on it.
For example, I never knew any powershell a few years ago, but I was given a project to write some QA scripts for work. That turned into a 8000+ line modularised script that anyone can use and create plugins for.
I am currently working on building servers and applications using PowerShell (installing and configuring AD, SQL, MSCS, RDP, ...)
If you haven't already, buy the book "Learn PowerShell In A Month Of Lunches" (https://www.amazon.co.uk/dp/1617291080) It's the top rated book by everyone.
Such a good book. Also I've gotten good mileage out of Windows Powershell 3.0 Step by Step (was handed out at a workshop I attended)
https://www.amazon.com/Windows-PowerShell-3-0-Step-Developer/dp/0735663394
Decent.
Powershell in a month of lunches is apparently quite good, that will cover Powershell from the basics to relatively advanced concepts, although I don't recall it covers AD.
Once you have a grasp of PowerShell, the AD modules are not much trouble to learn at all, MCSA should at least cover some of that.
Also - Take a look under the "resources" tab on the right of this sub.
There's a menu to the right of this subreddit with various links and book recommendations. You'll need to be on desktop version of the reddit website to see these though.
Personally I really like the Getting started with PowerShell 3.0 Jump Start.
Most will recommend the Learn Windows PowerShell in a Month of Lunches book.
Powershell in a month of lunches by Don Jones...
http://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617290211/ref=sr_1_1?ie=UTF8&qid=1311721510&sr=8-1
I'm a big fan of Don Jones... That's a really good intro book imho.
The book "Learn PowerShell in a month of lunches" is a great first read!
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617294160/ref=asc_df_1617294160/?tag=hyprod-20&linkCode=df0&hvadid=312091457223&hvpos=1o1&hvnetw=g&hvrand=4435694643250366932&hvpone=&hvptwo=&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9002018&hvtargid=pla-406163967273&psc=1&tag=&ref=&adgrpid=62820903995&hvpone=&hvptwo=&hvadid=312091457223&hvpos=1o1&hvnetw=g&hvrand=4435694643250366932&hvqmt=&hvdev=c&hvdvcmdl=&hvlocint=&hvlocphy=9002018&hvtargid=pla-406163967273
Great book to start with: http://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080
STLPSUG: May 19, 2016
Presentation: PowerShell Functions
Micah Battin, PowerShell Functions
A link to Micah's Demo notes/scripts will be put up ASAP
Links
If you are looking for an actual book, check out "Learn Windows PowerShell in a Month of Lunches"
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080
That's come up more times in various IT forums. The link I posted had the video version by the same author. I am going to get started on this myself. I know enough to get by, but think it will be good to go through the entire thing.
> I am new to PowerShell and I am unsure on where to start.
Please choose your option:
Are you sure?
https://www.reddit.com/r/PowerShell/comments/4ad8or/create_user_menus_from_objectsarrays/
https://www.reddit.com/r/PowerShell/comments/8afs51/create_dynamic_menu_from_array/
https://www.reddit.com/r/PowerShell/comments/2wk94i/creating_a_better_menu_structure/
https://www.reddit.com/r/PowerShell/comments/6cs2z5/adding_a_menu_to_a_variable/
https://www.reddit.com/r/PowerShell/comments/4or5s7/writemenups1_cli_menu_incl_keyboard_navigation/
The Powershell class i'm taking right now uses this book: http://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080
It does a good job explaining the how things work.
Learn Powershell in a month of lunches
and DNS and BIND are two I always recommend to people looking to learn about the windows side of things.
I started by reading a book which you can see by Clicking Here
After this I started changing my day to day admin process to use PowerShell instead. Learning other languages might help for looking into loops and things.
I would take a look at Don Jones, PowerShell in a month of Lunches
https://www.youtube.com/playlist?list=PL6D474E721138865A
http://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080
Not sure if the book is the latest, so have google first.
If you see yourself repeating a task 2 /3 times or more, then look into scripting it, start small and simple and go from there. Once you start seeing the time put into scripting paying off, it'll get easier.
PowerShell in Action is apparently quite good. I read somewhere if you wanted a more in depth read on what/how powershell is doing, more so than in 'A month of lunches' then this is the one you want. I haven't read it myself, but I have the 3rd edition on order and its due in May
This is probably the most recommended book: https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080
Books aren't really my learning style - to me, it's just solve a problem, then solve it gooder
Maybe I should read more....
You want this
Learn Windows PowerShell in a Month of Lunches
Here is the mobile version of your link
I taught a powershell class at work a few years ago. We went chapter by chapter through "Lean powershell in a month of lunches"
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080
https://www.amazon.com/Windows-PowerShell-Cookbook-Scripting-Microsofts/dp/1449320686/ref=sr_1_2?keywords=PowerShell+moDULE&qid=1555182385&s=books&sr=1-2-catcorr
That and
My advice would be to get this book.
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617294160
​
All you need to start
"Learn PowerShell in a month of Lunches" by Don Jones and Jeffrey D. Hicks.
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080/ref=sr_1_1?s=books&ie=UTF8&qid=1466023782&sr=1-1&keywords=learn+powershell+in+a+month+of+lunches
I started with Powershell in a month of Lunches
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617294160/ref=dp_ob_title_bk
You need this book in your life: https://www.amazon.com/gp/aw/d/1617294160/ref=dp_ob_neva_mobile
https://www.amazon.com/Learn-Windows-PowerShell-Month-Lunches/dp/1617291080