PowerShell & BlackBerry Web Services (Part 1 – Preparation)

UPDATE: I’ve made an update to this posting for BlackBerry Enterprise Server 10.1. See the posting here. If anyone is running BlackBerry Enterprise Server 5.0.3 or later, you should be aware that the new web front end also includes what Research in Motion is calling “BlackBerry Web Services.” This allows you to use Java (ew), … Read more

Get Exchange 2010 Move Information

When I’ve migrated mailboxes from Exchange 2003 to Exchange 2007, I was always asked how quickly the mailboxes moved. It wasn’t the easiest to figure this information out, but I was able to report on it after massaging the data for a while. Exchange 2010 moves store the information differently and you can access that … Read more

Mass Migration of Exchange 2007 to Exchange 2010 Users

My company went through a migration a few years ago of all of our users from Exchange 2003 to Exchange 2007.  The mailbox moves were insanely time-consuming.  Each mailbox has to be taken offline during the migration and that meant many, many nights of sitting up all night staring at progress bars. Exchange 2010 handles … Read more

New-WebServiceProxy & SSL

If you’ve been working with New-WebServiceProxy in PowerShell and have insecure (hopefully) internal sites that you are working with, you’ve undoubtedly seen the following message: New-WebServiceProxy : The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. At line:1 char:20 + New-WebServiceProxy <<<< -Uri https://[SERVERNAME]:[PORT]/[URLtoWSDL] + CategoryInfo : ObjectNotFound: (https://[SERVERNAME]:[PORT]/[URLtoWSDL]:Uri) … Read more

Migrating Terminated User Mailboxes

Our organization keeps our terminated user mailboxes for a very long time.  We keep them active for a number of reasons, but most can be summed up as “we like to have the information available if we need it.”  That being said, we don’t really like having the mailboxes on our production (read “high speed/high … Read more

Backing up all DHCP Servers in a domain via PowerShell

The DHCP PowerShell script will dump the “raw” DHCP data to a text file for each Active Directory-aware DHCP server.  The file is saved to “C:DHCP-BackupSERVERNAME-YYYYMMDD.txt.”  This can be easily changed within the last few lines of the script itself.