Go Postal – Exchange Report Manager plugin for LabTech

 

gopostal-logo

 

Go Postal Microsoft Exchange Report Manager

 

 

 

 

Go Postal is a Microsoft Exchange 2007, 2010 and 2013 reporting plugin for LabTech that uses Powershell to generate reports on each Exchange server being managed by the LabTech RMM platform. The plugin searches all systems for Exchange server software and if it finds a compatible system it adds it to the list of Exchange servers. By selecting an Exchange server you can request the report from that Exchange server in real time and it will retrieve that report directly from the exchange server.

 

 

mainview

 

Plugin can be viewed on the Dashboard -> Config -> Integration -> Going Postal

or

Selecting the View Menu from the main menu bar and selecting Go Postal.

 

What you will get when running the script, is an overall overview about:

1. Exchange Servers in your organization
[Break down by AD Site]
[Info about External and Internal Web services names]
[Mailbox Count per AD Site]
• O.S version
• O.S Service Pack level.
• Exchange Service health.
• Up time in days.
• Exchange Version.
• Exchange Service Level.
• Exchange Rollup Update Information.
• Exchange Role(s).
• Number of mailboxes in case of MBX role.

2. Database Full Inventory
[Break down by DAG]
[Separate Table for Recovery DBs]
[Separate Table for Non DAG DBs]
[Table per DAG]
• DB Name.
• Server Location.
• Mailbox Count.
• Average Mailbox Size.
• Archive Mailbox Count.
• Average Archive Mailbox Size.
• Mount Status.
• DB Size.
• Storage Group Name (Pre E2010).
• White Space.
• Circular Logging.
• DB Disk Free Percentage.
• Log Disk Free Percentage.
• Last Full Backup Date.
• Backed up Since (Days) – with customized thresholds.
• Quota Info: Prohibit Send.
• Quota Info: Prohibit Send and Receive.
• DB Activation Preference Check [Is it mounted on the preferred Server?].
• DB Copy Location and Activation Preference assignment.

3. Mailbox Type Aggregated Data:
• User Mailbox Count.
• Shared Mailbox Count.
• Room Mailbox Count.
• Discovery Mailbox Count.

4. Exchange Server Aggregated Data
• Total Number of Exchange Servers break down by
i. Version.
ii. Role.

5. Mailbox Aggregated Data
[Overall Statistics for the Organization]
• Total Mailbox Count.
• Total databases Size
• Total Archive Count.
• Total Archive Size.
• Average Archive Size.

 

 

Version 1.0.2 Available

download 

 

 

If your import of the scripts fails to create the PowerShell script in your L:\transfer\Scripts folder then you can download that script here

Get Powershell script

 

 

[Solved] OOF – Out Of Office fails to work using Outlook 2013 and connecting to an Exchange 2007 server.

Had an issue where a customer started having issues setting OOF on a remote Exchange server 2007 when using Outlook 2013. After some digging arround and making sure all autodiscover settings and SSL settings were accuratlly set I stumbled across the issue where installed hotfixes were causing the problem. The culprit is a faulty set of updates recently pushed out by Microsoft. To be specific, the following hotfixes are Outlook 2013 (KB2837618) and Microsoft Office 2013 (KB2837643). They have to manually be uninstalled  and a PC reboot issued to fix the problem.

This is for only Outlook 2013 and Exchange 2007 that I am aware of currently, others maybe affected so use wisely.

 

 

Enjoy

Cubert 😎

[Solved] – MS EXCHANGE 550 5.7.1 Client does not have permissions to send as this sender

 5.7.1 Client does not have permissions to send as this sender

This is what your Microsoft Exchange 2007 and or 2010 server may report when you try to send email through the Exchange server when permissions have been fouled up. The First this to check on is the “Manage Send As Permissions” under the user mailbox properties in the Exchange Management Console. Access the Exchange management console and select the user that is having the issue. Right Click, go to the send as permissions option.. now check that User NT AUTHORITY\SELF is listed.

Edit Send As Permissions
Exchange 2007

 

If it is not listed here then you need to add it in. This allows the authenticated user to send as their “Self”. Now retest your connection an try send a piece of mail.

 

 

Good Luck,

Cubert 😎