Maintenance and recovery procedures for VMR Scheduling for Exchange
The VMR Scheduling for Exchange feature includes two scripts that can be run from the Management Node to allow you to restore meetings and to delete old calendar and mail items from the equipment resource's mailbox.
Running the scripts
To run the scripts, you must log into the Management Node over SSH. To allow this, SSH access must be enabled ( and ).
Log in as admin, using the password that was set during initial installation.
Recovering meetings
The scheduling recovery script allows you to reinstate meetings that may have been lost after Pexip Infinity was reinstalled or restored from a backup.
This tool finds Accepted scheduled meetings in the Exchange equipment resource's mailbox and checks whether the corresponding VMR exists on the Management Node. If not, it creates the VMR. In doing so it will assign new aliases to the reinstated VMR (since the Management Node will have no record of the previous alias), so it will therefore also send out updated joining instructions to attendees.
To run this script, enter:
/usr/bin/schedulingrecovery
using the following arguments:
| Argument | Description |
|---|---|
| --config |
The file path of the scheduling_config.json file. Unless this has been changed on the advice of your Pexip authorized support representative, it will be the default so does not need to be specified. Default: /etc/pexip/scheduling/scheduling_config.json |
|
--exchange-connector-id |
The ID of the VMR scheduling for Exchange integration you want to be processed. To process all VMR scheduling for Exchange integrations in the database, do not include this argument. (To find the ID of a particular VMR scheduling for Exchange integration, go to and select the VMR scheduling for Exchange integration. The ID will be the number that appears between the slashes at the end of the URL.) |
|
--time-limit |
The date and time after which meetings must start in order to be saved back to Pexip. You must use the format YYYY-MM-DDTHH:MM:SS in UTC. If you do not specify a time then the current time is used, meaning that only meetings happening in the future will be recovered. |
|
--update-message |
The message inserted at the top of the email update sent to attendees, which will be followed by the text in the Joining instructions template. This argument supports HTML. Default: "This meeting has updated joining instructions." |
Example
To restore all meetings starting after noon on 1 May 2017, enter:
/usr/bin/schedulingrecovery --time-limit 2017-05-01T12:00:00
Deleting old mailbox items
The scheduling room maintenance script deletes old inbox and calendar items from the equipment resource's mailbox. This may be useful if mailbox space needs to be freed up.
To run this script, enter:
/usr/bin/schedulingmaintenance
using the following arguments:
| Argument | Description |
|---|---|
| --config |
The file path of the scheduling_config.json file. Unless this has been changed on the advice of your Pexip authorized support representative, it will be the default so does not need to be specified. Default: /etc/pexip/scheduling/scheduling_config.json |
|
--exchange-connector-id |
The ID of the VMR scheduling for Exchange integration you want to be processed. To process all VMR scheduling for Exchange integrations in the database, leave this blank. (To find the ID of a particular VMR scheduling for Exchange integration, go to and select the VMR scheduling for Exchange integration. The ID will be the number that appears between the slashes at the end of the URL.) |
|
--inbox-time-limit |
The date and time by which inbox items must have been received, in order to be deleted. You must use the format YYYY-MM-DDTHH:MM:SS in UTC. If you do not specify a time then the current time is used, meaning that all inbox items will be deleted. |
|
--calendar-time-limit |
The date and time by which calendar items must finish, in order to be deleted. You must use the format YYYY-MM-DDTHH:MM:SS in UTC. Recurring meeting items are finished only when the last instance in the series has finished. If you do not specify a time then the current time is used, meaning that all calendar items that have already finished will be deleted. |
Example
To delete all emails received before noon on 1 May 2017, and all meeting items that finished by this date, enter:
/usr/bin/schedulingmaintenance --inbox-time-limit 2017-05-01T12:00:00 --calendar-time-limit 2017-05-01T12:00:00