Tag: Powershell

Continuing from the previous post, during the second part of the demo I introduced the details on how to interact with other .net objects, along with some of the PowerShell glue that makes manipulating Exchange objects so powerful: [PS] C:\Program Files\Microsoft\Exchange Server\Scripts\TR4>$dl = Get-DistributionGroup Homelandc*[PS] C:\Program Files\Microsoft\Exchange Server\Scripts\TR4>$dl Name DisplayName GroupType PrimarySmtpAddress —- ———– ———…

The first part of the demo I describe in my previous post was to introduce the crowd to the basics of interacting with the Exchange cmdlets in PowerShell: [PS] C:\Documents and Settings\Administrator\Desktop>Get-ExchangeServer Name Site ServerRole Edition AdminDisplayVersion —- —- ———- ——- ————–E12 Default-First-Sit… Mailbox,… Standard… Version 8.1… [PS] C:\Documents and Settings\Administrator\Desktop>$server = Get-ExchangeServer[PS] C:\Documents and…

I’d previously blogged about Vivek posting the details and a link to the “Scriptacular Demo Pack”. This download can be very useful in preparing/provisioning an environment to use for demos, and then knocking the socks off your audience with the coolness of the demo scripts. I highly recommend it. Why bring it up again? Well,…

I’m very happy to have recently run across Matt Stehle’s “CDOs and CDONTS of Messaging Development” blog (and it’s a great blog name too, btw — Bravo Matt!) He’s currently running a series of posts called “Introduction to Exchange PowerShell Automation”, where he’s providing a lot of consolidated insight into how to write code that…

Neil posted this morning about how to find your Exchange 2007 server’s “installed bits” version using powershell and the “AdminDisplayVersion” property. Great post, and a simple way to determine — particularly in bulk for many servers — what version of Exchange 2007 you’re running. Now, what’s interesting is that if you just do “Get-ExchangeServer |…

Exchange 2007 has some very powerful cmdlets which can be used to generate fairly effective reports, out of the box. However, sometimes they’re just a bit TOO powerful, and it leads to some confusion about how to get out the data you want. Example of this — an email I responded to today: Customer was…

More details about the “True”/”False” vs $true/$false behavior posted to the Powershell team blog (Boolean Values and Operators) over the weekend. I’m very relieved (“whew!”) to see they reached same conclusion as my Exchange-related blog post (When ‘false’ means $true), but with a bit more detail provided thanks to Jeffrey Snover.

Finally, I’m able to “scoop” the EHLO team blog on something. And all it took was Nino being OOF to vacation while I am not! 🙂 Last night Vivek posted the much-anticipated “Scriptacular Demo Pack” for Exchange Server 2007 to his blog. This is a great ZIP file with Powershell scripts you’ve proably seen Vivek…

Recent customer question: “Why does it treat the boolean as ‘true’ when I explicitly entered ‘false’?”. This question is normally followed up by something like “This is obviously a bug since when I tell it ‘true’ works just fine.” Great real world example syntax that will exhibit this behavior would be setting a RecipientFilter to…

Recent question across my mailbox: “How can I get a count of how many mailboxes are on each of my mailbox databases?” The simple answer is to use something like this: Get-Mailbox -ResultSize Unlimited | Group-Object Database | Format-Table Name, Count You can refine it further (with -Server parameter or some other Filter details), if you…