The script logs onto Outlook using that profile, and exports the calendar data to a CSV.When it is complete, it combines all of the calendar export files into a single CSV containing all the exported data.As always, your comments and suggestions are always welcome.

The new script has the following requirements: If any exported calendar CSV data files exist from a prior runs, the script will backup these files.

The script runs thought each room, in the file and creates / updates a profile on the local machine.

The script assigns full mailbox permissions to the current user, for the calendar to be exported.

You need to modify the script for your servers SMTP parameters and if you prefer to run the script remotely you can use -computername on the the get-eventlog cmdlet.

Admittedly, this is not the best way if you have something like SCOM in place, but as a rudimentary solution it does exactly what they need.

The previous version of this script, proved far more popular than I could have ever imagined.It was however very complex, which caused numerous failures during execution.Just a quick little script I developed for a client this week.As you know Windows 2012 DHCP server has some pretty cool Powershell cmdlets built in, but sadly, in the case of Windows 2008 there are none.My customer needed to know when scopes are starting to run out of addresses.I found that the DHCP server logs an event each hour after startup for all scopes that are at 80% utilisation or more. The script is triggered by the 1020 event in the system log, and then finds the events for the last hour, and send an email to the guys to alert them.