Continuing from the previous post, in this final part of the demo I explain how I provisioned the environment, and demonstrated a script to “rip out” the environment and then effortlessly “regenerate” it again: [PS] C:\Program Files\Microsoft\Exchange Server\Scripts\TR4>Get-MailboxDatabase | get-mailbox Name Alias ServerName ProhibitSendQuota —- —– ———- —————Administrator Administrator e12 unlimited Neil Abercrombie NeilAbercrombie e12…
Year: 2007
Exchange Demos with PowerShell – Finding Things
Continuing on from the previous post, in the third part of the demo I talk about using help and “finding things” in PowerShell. as well as introducing the concept of Exchange identity and filters (both traditional PowerShell client-side and Exchange’s own server-side filters): [PS] C:\Program Files\Microsoft\Exchange Server\Scripts\TR4>get-help *queue* Name Category Synopsis —- ——– ——– Get-Queue…
Exchange Demos with PowerShell – DotNet Objects
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 —- ———– ———…
Exchange Demos with PowerShell – Basics
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…
Exchange Demos with PowerShell
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,…
Matt’s introduction to Exchange PowerShell Automation
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…
AdminDisplayVersion as a structure
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 SysMgmt Team blog posts roundup
I have previously listed the progress we’ve been making in posting ITPro focused Systems Management blog posts to the EHLO team blog in my “Continuing with SysMgmtBlog Posts” and “Exchange 2007 SysMgmt bloggers want your input” postings. To recap – If you’ve not been watching the EHLO (MS Exchange Team) blog, you’ve missed a ton…
Do I really need to upgrade my filters?
After posting the Exchange 2007 OPATH intro and How to Upgrade the Filters posts to EHLO over the past few days, one question that’s come up enough to warrant another blog post is “Do I really need to upgrade my filters”. And the answer is pretty straight forward: maybe. Ok, that’s not fair. Let me…
Wrangling Byte Quantified Size details from Exchange 2007 with Powershell
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…