We’ve had an outpouring of support for the upcoming games, with more volunteers than we know what to do with! At this point, we have our judging panel completely full; we’re operating with a fairly small group of celebrity judges this time around. Games Master Richard Siddaway will introduce our judges in a few days. We’ve also filled our roster of Coaches, and Head Coach Mike Robbins will provide that lineup soon also. If you’ve volunteered but not heard from Richard or Mike, then you should definitely start recruiting a team for when registration and team formation opens in a couple of weeks!
$computers = Get-ADComputer -filter * -searchBase "ou=test,dc=company,dc=pri" foreach ($computer in $computers) { write-host "computer $computer" $result = Do-Something -computername $computer Write-Host "$($result.property) and $($result.value)" } Would you ever consider that acceptable? Some folks might well say, “sure! if I was just testing this, throwing in those Write-Hosts is no big deal. Heck, even if I was the only one who was going to use this, Write-Host isn’t bad.” And the point I’m going to make doesn’t just apply to Write-Host. It applies to anytime when you’re doing something that you know breaks “best practices,” but you justify it because it’s “just for you” or because “it’s just for testing.” To wit: if you need your script to output some status or tracking information, as in the above, use Write-Verbose. Yes, Write-Verbose requires a script or function to have this at the top:
The Charlotte Powershell Users Group meeting was held on Dec 5th. Jim put together a nifty challenge related to image manipulation. We started off with this nifty image. Pretty huh? The challenge was to manipulate the image using PowerShell to find the hidden message. After some discussion, the code was cracked and the image was displayed. As is normal with Powershell, there were multiple ways to achieve the end goal. Feel free to stop reading here and grab the image if you want to give this a go yourself. Spoilers are below.
Windows Azure has advised us of scheduled downtime on Friday, December 6, from approximately 15:00 hours (US Pacific) until approximately midnight Pacific time.
Released in our new Git repo: _The Community Book of PowerShell Practices, _an ongoing book started from this past Summer’s “Great Debates” blog post series. Grab it from https://github.com/PowerShellOrg/ebooks/blob/master/Practices/2013Sep_Practices/2013Sep_Practices.doc and enjoy!
I’m in the midst of working on 10961C, the Windows Server 2012 R2 / Windows 8.1 / PowerShell 4.0 update of Microsoft’s 10961A/B course, “Automating Administration with Windows PowerShell.” I anticipate this being closed out by the end of November, 2013, so if you’ve taken or taught this course and have any feedback - even a typo - now’s the time to tell me. Drop a comment below, or e-mail me (if you have my address). Please, no Twitter replies on this one. The course will not be substantially changed from the B rev; because PowerShell v4 doesn’t change much, especially at the entry-level covered by 10961, there wasn’t much to alter. But I’m trying to sweep up as many lingering bugs and typos as possible. Kudos to MCT Jason Yoder for firing over a list of fixes!
John Mello gave a presentation on a script that searches a mailbox for an email by subject and downloads any attachments it may contain. A copy of his scripts can be obtained here.
We are still trying to arrange for a PowerShell Saturday sometime in 2014, if you are interested in presenting please let us know!
We are assigning homework this week! Hopefully this will be a fun task that we can discuss during our next meeting, so try your hand at the following problem:
A quick note and an apology: I’ve had to modify the site configuration to require users to be registered and logged in before they can comment. We’ve been taking a ridiculous amount of comment spam, and it’s consuming more and more time to weed through it. You can register using any major social media account, so you don’t have to remember yet another username and password with us, so hopefully that’ll mitigate the inconvenience. Have a great week!
One of the most important tasks for the** **DBAs is to ensure that there is a maintenance plan to recover data from a given disaster.
Â
As a DBA we need to design a maintenance plan according to our scenario and business requirements. Do we want to be able to recover data at any point of time? How much data loss can we accept? All these questions and many more must be answered before designing the plan. In this post we will assume a basic daily full backup to keep our data safe, we will assume that there is a job performing full backups to our databases every day at midnight.
