Version 1.6.1 of the Exchange Environment Report is hot off the press and ready for download.
New in this version…
- Added Exchange 2016 support
- Fixed issues with not showing latest Update Rollup
- Fixed issues with not showing latest CU
- Fixed bug detecting Autodiscover Service URI and added support for new Get-ClientAccessService command
- Removed option to schedule – easier done from Task Scheduler directly and the built-in method was buggy
- Added MAPI/HTTP hostnames to site hostname list
- Added detection for Hybrid Server
- Changed font to Segoe UI
As always the script is hosted on the Technet Gallery for Exchange and the original page for the EER is here.
Enjoy!
I get multple warnings like this:
WARNING: The object 2d717b24-52ed-43da-997b-bf1f134eb1d4 has been corrupted, and it’s in an inconsistent state. The
following validation errors happened:
WARNING: Cannot extract the property value of ‘DeletedItemCount’. Source: PropTag(DeletedMsgCount), PropType(Int),
RawValue(-1236), RawValueType(System.Int32). Target: Type(System.Nullable`1[System.UInt32]), IsMultiValued(False).
Error Details:
Any idea where they are comming from?
Pingback: Exchange Quarterly Updates Feb. 2016 Released - msdigest.net - by Peter Schmidt [MVP & MCSM]
It still gives me CU error from passive server, but I was wondering if I could automate the run once so it gets automatically saved from task scheduler and I could use it with another script on task schedule that forwards from my gmail to my gmaiil account. Few warning I get on the report are –
Exception calling “OpenRemoteBaseKey” with “2” argument(s): “The network path was not found.
”
At C:\scripts\Get-ExchangeEnvironmentReport.ps1:361 char:3
+ $RemoteRegistry = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey(‘LocalMachi …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : IOException
WARNING: Cannot detect Rollup Version via Remote Registry for EXCH-DAG
Exception calling “OpenRemoteBaseKey” with “2” argument(s): “The network path was not found.
”
At C:\scripts\Get-ExchangeEnvironmentReport.ps1:383 char:7
+ $RemoteRegistry = [Microsoft.Win32.RegistryKey]::OpenRemoteBaseKey(‘LocalM …
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : IOException
WARNING: Cannot detect CU/SP via Remote Registry for EXCH-DAG
You cannot call a method on a null-valued expression.
At C:\scripts\Get-ExchangeEnvironmentReport.ps1:187 char:3
+ [long]$Size = $Database.DatabaseSize.ToBytes()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull
You cannot call a method on a null-valued expression.
At C:\scripts\Get-ExchangeEnvironmentReport.ps1:188 char:3
+ [long]$Whitespace = $Database.AvailableNewMailboxSpace.ToBytes()
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull
Having the same issue mention in other discussions where Non-DAG Database info is not displayed at all if there’s only one mailbox server in the environment.
Steve, did you happen to find the problem to this?
I’ve got the same result, from 2013 the dags are empty even the 2010 dags.
Steve,
This is great script to report Exchange Environment. I just have one small suggestion to be considered, Would it be possible to add the logic to display Public Folder DB info (Size, WhiteSpace, last Full Backup, etc.) for none Exchange 15 servers (i.e. 2010, 2007, 2003)?? Thanks you for all the time you spend to make this current.
This is an very good @MSFTExchange environment report Script , excellent for everyday use by #stevegoodman https://t.co/OI11qKNmb9
We are running 2010, 2013, and O365. All of the Servers and Databases have info in the DAG section. I would like to know if I can adjust the column widths in that section though.
Steve’s awesome Exchange Environment Report script has been updated http://t.co/OUuQ0CIeN4
Pingback: NeWay Technologies – Weekly Newsletter #165 – September 18, 2015 | NeWay
Pingback: NeWay Technologies – Weekly Newsletter #165 – September 17, 2015 | NeWay
Pingback: Weekly IT Newsletter – September 14-18, 2015 | Just a Lync Guy
“New version of the Exchange Environment Report available now” http://t.co/iHlQAsMU4z
Pingback: Exchange Quarterly Updates Released - msdigest.net - by Peter Schmidt [MVP & MCSM]
New version of the Exchange Environment Report with enhanced UI, bug fixes, and Exchange 2016 support not available. http://t.co/eT1THwwMmo
New version of the Exchange Environment Report available now – http://t.co/uURltVNwFw
@stevegoodman has updated his Exchange Environment Report script for Exchange 2016. http://t.co/op93qzUzCS He’s ahead of the curve…
A great report, minus the issues. The report fails to show all data when in a mixed environment. We Have primarily 2010 and are moving to 2013.
When report run from a 2013 server; Server details for both 2010 and 2013 appear correct. Database Availability Group information does not show server names/databases for both 2010 or 2013.
When report run from a 2010 server; Server details for both 2010 and 2013 appear correct. Database Availability Group information does not show server names/databases for 2013, it does correctly report server names/databases for 2010.
Thanks for reporting this. So on 2013 it’s not showing DAG info at all?
on 2013, only reports DAG names, lines where it would display server name and database name, no information is shown. I could send the two reports I ran and you will see the difference.
Thanks that will be useful if you can. Did this work in the previous version?
no, just didn’t leave a message. Where do you want me to send the reports?
Ah right, steve@stevieg.org
Hi Tony, I’ve not been able to reproduce this yet. :-/