We have finally hit the final event of the 2013 Scripting Games! The past 6 weeks have given us many amazing scripts and some that were in need of extra work. Regardless, for those of you who have finished all 6 scripts in your respective, I say Congratulations! You have hit the finish line sprinting hard to the end! Now you can sit back and know that you made it and have learned (hopefully) some great things along the way. Remember, not only have you learned some new techniques, but also the techniques that you have used have taught others […]
http://blog.powershell.no/2013/06/08/2013-scripting-games-learning-points-from-event-6/Â has Jan Egil’s thoughts on the final event. Related posts: More Judges’ Notes on Event 2 Jan Egil’s Event 4 Notes
Oops! Looks like I totally forgot about posting what I did over here. Sorry! In order of appearance: Event 5 – script Event 5 – notes Event 6 – script Event 6 – notes This is last event, and I would like to thank everybody who took part in this games. Thank you guys for great ideas, inspiration, feedback… It was really educational experience for me (as it was in the past), and I hope it was educational for you too. And – congratulations for all the winners. No related posts.
When I read the instructions for event 6, I thought that here’s a tough one. A lot of competitors won’t have access to a test environment with Windows Server 2012 and Virtual Machines that they can actually work with. So, I expected that many of the entries wouldn’tÂ get testedÂ andÂ intended to forgive minor errors that would have shown up in testing. Well, there was one thing that really surprised me. The instructions were quite clear about minimizing “Are You Sure” queries to the user, but you can count on one hand the number of entries that included -Confirm:$false. This is just […]
With week 5 in the books, I can see that everyone just continues to grow and show some great submissions. Of course, nothing is perfect and can always show areas of improvement, but trust me, you are all doing an excellent job! I was hoping to have this article completed prior to now, but between a flight to Tech Ed and forgetting my power cord for the laptop, I am just now getting this accomplished. Better late than never :). With that, head over to my blog to check out my notes on Event 5 here. No related posts.
I loved this weekâ€™s challenge as it had the right wiggle room to bring out the best in our participants.Â Of course, this is also the point in the games when we start to get everyoneâ€™s â€œAâ€ game.Â At this point even our new competitors are all warmed up and in the zone, and let me tell you the entries this week show it! Â Â I want to start with the beginners as I actually ran almost every entry this week.Â Honestly everyone fell into one of three buckets Select-string, Import-CSV or ,Foreach.Â Let me explain there where three primary means […]
Find ’em at http://www.powertheshell.com/scripting-games-task-5-commentary/ No related posts.
Into the home stretch and the entries just keep getting better! The only advice I’d like to offer this time is to be careful to read the instructions carefully. They included the specific folder where the files were located and I noticed several misinterpretations in the scripts. Some included a mandatory Path parameter and others had a default Path that was not the specified folder. Including an optional Path with the correct default would certainly be acceptable, but not those variations. The instructions also included some ambiguity about what the log file actually contains. Was the client IP address in […]
Jan Egil, or Norwegian expert commentator/judge, has posted his learning notes for Event 5:Â http://blog.powershell.no/2013/05/28/2013-scripting-games-learning-points-from-event-5/ No related posts.
Active Directory is one of those things I just love to work with. That’s why I was really looking forward to this event. As always, I learned few things, but still – seen some mistakes that I would like to highlight. As always – you can read about those both in Polish and in English. Enjoy! No related posts.
Again if youâ€™re participating in the games this year youâ€™ve already won!Â If youâ€™re not and youâ€™re reading this post what are you doing!Â Iâ€™ve watched authors step there game up over the past month, and I can tell you from personal experience the games will make you better at your real job.Â Itâ€™s like sharpening an axe, an axe made of super juice that can automate the world Well that’sÂ clever! I came across this script this morning. $prop = Write-Output Name,Title,Department,LastLogonDate,PasswordLastSet,LockedOut,Enabled Get-ADUser -Filter * -Properties $prop | Get-Random -Count 20 | Select-Object $prop | ConvertTo-Html -Title "Active Directory Audit" […]
It is all downhill from here folks! Event 4 is in the books and we only have 2 more to go! Everyone has been doing an outstanding job with their submissions and it is becoming clear that people are learning new things and showing some great techniques with their code. Of course, thisÂ doesn’tÂ mean that thereÂ isn’tÂ room for improvement with some submissions to make them even better or just some simple mistakes that can be cleaned up to make average submissions into amazing submissions. With that, its time to dive into my notesâ€¦ You can check out the rest of this article […]
Loved seeingÂ [OutputType([PSObject])] in an entry this morning… that helps the help system document what your script produces. It’s a shame it doesn’t work well with custom type names (since those are a bit of a fake-out on the object), but it’s an attention to detail I appreciate. IÂ am seeing a little bit of misunderstandings. Keep in mind that the lastLogonTimestamp attribute in AD is the one that replicates, although there is a long possible delay in that replication. There are other “last logged on” attributes thatÂ don’t replicate so you can’t rely on them unless you’re querying every DC (pretty inefficient). […]
Â Wow! That’s the only word I can think of to describe the submissions this time. I’m really impressed with the approaches taken to solve this problem. The only thing that could have been better is quitting when the ActiveDirectory module or the Quest snapin weren’t found. I chalked that up to not having experience with an actual audit where no answer is not acceptable, so I didn’t count against it when evaluating the scripts. But, on this point kudos to the one script that tested for the AD module, then the Quest snapin, and fell back to the ADSI accelerator […]
Jan offers some perspective on Event 4 atÂ http://blog.powershell.no/2013/05/22/2013-scripting-games-learning-points-from-event-4/ Related posts: Event 6 Judge’s Notes from Jan Egil Ring