Thanks everyone for the idea. I used Michael’s script and got the answer I
needed. But I will look into these other reporting options.
Thanks!
jb
From: Steve Goodman [mailto:st...@stevieg.org]
Sent: Friday, June 22, 2012 4:35 PM
To: MS-Exchange Admin Issues
Subject: Re: SP2 RU3
I've not
il
--
Phil Randal
Infrastructure Engineer
Hoople Ltd | Thorn Office Centre | Hereford HR2 6JT
Tel: 01432 260415 | Email:
phil.ran...@hoopleltd.co.uk<mailto:phil.ran...@hoopleltd.co.uk>
From: Steve Goodman [mailto:st...@stevieg.org]
Sent: 22 June 2012 12:20
To: MS-Exchange Admin Issues
Subjec
260415 | Email: phil.ran...@hoopleltd.co.uk
From: Steve Goodman [mailto:st...@stevieg.org]
Sent: 22 June 2012 12:20
To: MS-Exchange Admin Issues
Subject: Re: SP2 RU3
If your looking for something a bit prettier you could check out my Exchange
Environment Report which will provide this and so
If your looking for something a bit prettier you could check out my Exchange
Environment Report which will provide this and some additional info:
http://www.stevieg.org/2011/06/exchange-environment-report/
Sent from my iPhone
On 21 Jun 2012, at 14:38, "Michael B. Smith"
mailto:mich...@smithcon
I didn't write this original script, I just modified it to handle some obvious
errors, but unfortunately I didn't keep the original author's byline handy.
The UR information is hidden pretty deeply. This script will get it out.
Get-ExchangeServer |% {
[bool]$known = $false
