Passwords: Thy Word have I hid in my heart

Everyone is talking about more secure passwords. Church folks are concerned about memorizing the Bible. Why not combine the two? In this post, I’m going to show you a few samples of using the Word as a password.

How many times do you type in your password every day? I’m in IT, so I probably type my passwords quite a bit more than the average user. Every time I get up from my desk, I lock my computer. When I return, I type in my password. When I log into my admin sites, It type in my password. I probably type my passwords in over 20 times every day.

Also, to be secure, every password that you have to use should be different. If you use one for email, you should not use the same for your online bank account. If a hacker should grab one of your passwords, all is not lost if you use different ones for each site.

So, you ask “How do I come up with secure passwords?”

One way is to use a random character password generator. However, “p+DGJM}4-B!t” might be secure, but remembering that would be near impossible.

Passwords are usually scored on a number of attributes;

    Length – Must meet a specific character count
    Mixed case – Must contain upper and/or lower case characters
    Digits – The numbers between 0 and 9
    Symbols – “&, %, !, @, etc”

Ok, so how do you wrap up a Bible verse into a password?

Let’s consider Genesis 1:1 English Standard Version (ESV)

In the beginning, God created the heavens and the earth.

Use the beginning letter from each word, you’d have “ItbGcthate”. OK, you would have mixed case and a good length of 10 characters. If you want to throw in a symbols, change the a (for “and”) into an ampersand. “ItbGcth&te”. You can add the reference to the end as well since verse memorization should include the reference. “ItbGcth&teG11”. That password should give you high marks for length, mixed case, digits and symbols. Now each time you type that password, you’ll be quoting and committing to memory Genesis 1:1.

Let’s try Matthew 7:7

“Ask, and it will be given to you; seek, and you will find; knock, and it will be opened to you.

This would make a very long password. However, you don’t need to use the entire verse. Let’s use just the first third and append the reference. You’d end up with “A&iwbgtyM77”. A very nice password with high marks. You also know where to find the verse if you ever need it in its entirety.

You can try Revelation 3:20 on your own.

Behold, I stand at the door and knock. If anyone hears my voice and opens the door, I will come in to him and eat with him, and he with me.

You can even have a little fun with this. Consider the second half of 1 John 4:4…

greater is he that is in you, than he that is in the world

You might come up with a password like “He>world1J44”

This will work perfectly for any verse. Well, maybe not John 11:35 (“Jesus wept.”)

I hope this post will help you stay secure and in the Word!!

Posted in Uncategorized | Leave a comment

Top 20 Largest Mailboxes

Here is a script that will report your top 20 largest mailboxes. This could easily be changed to report the top 5 or top 50. You can also use my previous post to schedule this to run every morning or once a month.

There is additional code here to send to to your mailbox so you don’t have to go and track it down. You know the status just by looking at your email (which you do anyway).

$subject = "Exchange 2010 Mailbox Statistics"

$mailboxes = Get-Mailbox -ResultSize 'Unlimited' -RecipientTypeDetails Usermailbox | Get-MailboxStatistics | Sort TotalItemSize -desc | select-object DisplayName,ItemCount,TotalItemSize -First 20

$20LargestMailboxes = $mailboxes | ConvertTo-HTML -fragment

$Head = "<!DOCTYPE html PUBLIC '-//W3C//DTD XHTML 1.0 Transitional//EN' ''><html xmlns=''><head><style type='text/css'>TABLE{font-family: verdana,arial,sans-serif;font-size:11px;color:#333333;border-width: 1px;border-color: #a9c6c9;border-collapse: collapse;background-color:#a9c6c9;}TH{border-width: 1px;padding: 8px;border-style: solid;border-color: #a9c6c9;}TD{border-width: 1px;padding: 8px;border-style: solid;border-color: #a9c6c9;background-color:#d4e3e5;}</style></head>"

$Body = "<body><p><h2>Top 20 Largest Exchange 2010

$Tail = "<p>This script is run from PUTIL2DSM. D:\PSScripts\MailboxStats.ps1.</p>"

$Message = $Head + $Body + $Tail

Send-MailMessage -To -From -Subject $subject -SmtpServer -Body $Message -BodyAsHtml

Now, a bit of explaination of the code…

The variables $subject, $head, $body, $tail & $message all have to do with the sending of the email. the $head is where the table is built. If you don’t like the look of the table, try modifying this variable.

$Body is the table itself including the table header

$Tail is just a reminder as to where this script is ran from so the person that follows me will have a chance of finding it to modify it.

The $Message is the combination of all three. Make sure you update the Send-MailMessage line with your specific details. Otherwise, you will not get the email.

So, the Exchange specific line is really just the one or two at the top. Study it and let me know if you have questions.

Here is a sample of what the email will look like.

Exchange Top 20 Email

Top 20 Email Sample

Posted in Exchange, PowerShell, Scripting | Tagged , , | Leave a comment

Scheduling Exchange Powershell Scripts

Even an average  scripter knows that scripting can save days and weeks worth of manually doing a task over the coarse of a year. This post will start Exchange 2010 administrators toward scheduling those scripts that save so much time.

To use the Get-Mailbox command, you have to load the Exchange Shell into Powershell. While this is easy once you know the trick, it is not intuitive at all. I had to do a bunch of digging thru Internet searches to find out exactly how to do it. I hope you find this page quickly (which will give you even more time to do other tasks)

OK, we all know the Windows Scheduler, so I won’t bore you with the details. Create a new task. On the Actions tab create a new action. In the Settings box, type “Powershell.exe” in the Program/Script: textbox.

So far, so good. That is the intuitive part. Pretty straight forward don’t you think?  The next step is to add information to the Add arguments (optional): textbox.

-PSConsoleFile “<path to Exchange>\Exchange\V14\Bin\ExShell.psc1” -Command <path to scripts>\<filename>.ps1

Note the three variables in this line. <path to Exchange>, <path to scripts> and <filename>. These will change based on your implementation so you will need to substitute your information here.

I also put <path to scripts> in the “Start in(optional): textbox. That way, if my script generates a log file, I don’t always have to put the full path in my script.

Finish creating the task with your triggers, etc. and your script should now run on a schedule.

Let me know how things work out.

“There is nothing so permanent as a temporary solution” – Me

Posted in Exchange, PowerShell, Scripting | Tagged , , | Leave a comment