As technology professionals, we live in an interruption-driven world — responding to incidents is part of the job. All our other job duties go out the window when a new issue hits the desk. Having the right information and understanding the part it plays in the organization is key to handling these incidents with speed and accuracy. This is why it’s critical to have the ability to compare apples-to-apples when it comes to the all-important troubleshooting process.
There are a plethora of software packages out there to report against your Exchange Infrastructure and many of them are great. I’ve worked with several in the past. However, if you want just a simple report for mailbox sizes, and you have access to a SQL Server, you can write your own process. My script … Read more
Like many of you, I’ve run into the fun situation of moving the Exchange 2003 Recipient Update Services to Exchange 2010’s Email Address Policy. Although the Exchange Team Blog has a great script (which I highly suggest that you use) for migration, I thought that it might be best to get a list of accounts … Read more
The International Legal Technology Association asked me to contribute an article for their trade magazine a few months ago. The article was specific to my company’s care study for BlackBerry Enterprise Service 10.1 with regard to High Availability. Although BlackBerry Enterprise Service 10.2 has been released, the framework which was discussed stays the same. If … Read more
This is a follow-up to my previous four-part post about PowerShell & BlackBerry Web Services. If you need a primer on where this is coming from, see the first series. Like before, I’m going to run through each step that I used when setting this up, though there will be fewer references to the specifics … Read more