This project has moved. For the latest updates, please go here.

Directions for use

Unpack the zip in an empty directory.
Open a command window in that directory.
Run "meetinganalyzer" and press enter.
Follow the prompts.

Example of the tool running:
Meeting Analyzer
Creates a timeline of a meeting and reports any problems found.

Enter a connection URI for remote powershell.
You can leave this blank for Office 365 connections, or enter a
URI like ""
or "" :

Enter the tenant admin name (eg.
Enter the password for *********

Attempting to connect to the service.
Successfully connected.

Enter the SMTP address of the user for the meeting to analyze:
Enter the Subject of the meeting to analyze (leave blank to enter a Meeting ID instead): Meeting01

Running command to retrieve the meeting data...

The tool will output a timeline of sorts that is the version history of the meeting. Exchange stores this version history on the server for each user in hidden folders in each user's mailbox.

Then it will tell you about the files it created that you can use:

Timeline output written to: C:\MeetingAnalyzer\1.0.0\user01@reprohouse.orgMeeting01.log
Calendar item property data written to: C:\MeetingAnalyzer\1.0.0\user01@reprohouse.orgMeeting01.csv

The LOG file contains pretty much the same thing output to the command window.
The CSV file contains the raw data output from Exchange - each row is a "message" in the version history, and each column is a property that the tool requested for each "message" in the version history.

Seeing where a particular property changed in an unexpected way can help in troubleshooting what happened when something has gone wrong with a meeting item in your calendar.

When there is a problem meeting - it is always good to pull this calendar diagnostic data for the Organizer, the Organizer's delegate (if there is a delegate involved) and the attendee who is experiencing the problem (if it's an attendee who is having the problem). Viewing what is happening with the meeting across mailboxes like this will tell a more complete story of what has happened with the item.

Last edited Jan 25 at 3:54 PM by rtopken, version 4