Automatic Australian Holiday Rulesets for Response Group Service

By | September 5, 2018

New-CSRgsAustralianHolidayList.ps1

Update 5/11/2018 Released Version 2.3 to fix an an issue with single pool selection using the ISE and add last run reminders

About the tool

This is a script that adds/maintains the relevant Australian Holidays to your Skype4B  / Lync environment for the next 12 months based on data available from the Australian Government Website.

I re-wrote most of the script from scratch and added a whole bunch of code to try and catch a lot of the errors etc that happened in the older versions. I’ve also tried to make it alot simpler to use for everyone that’s not me 🙂

Data is taken from http://www.australia.gov.au/about-australia/special-dates-and-events/public-holidays and I have done my best to be as error free as possible.

Shout of to Greig in Sydney for beta testing and providing the red pen. That guy would have made a brilliant English teacher.

Instructions

Download, and run on a Frontend or any machine with the Lync / Skype4B management tools installed

The script will attempt to detect your Skype4B Setup and proceed accordingly

  • If it only detects a single FrontEnd it will prompt you to confirm the selected pool and then configure new Holiday sets
  • Should it detect multiple pools it will ask you to confirm which pool to use and configure new Holiday sets
  • If it finds Holiday sets with the same name they will automatically have any existing entries removed

If you already have holiday sets with the name names or you need to add a country code. You can specify a string with the -RGSPrepend parameter to prepend to the Holiday set names.

Unattended (Scheduled Task) execution

You can also use the script on a scheduled task to automatically pull and update the latest holidays on a monthly basis if your server has internet access.
Simply specify -FrontEndPool <FEPoolFQDN> and -Unattended in the scheduled task.

You can also still specify the -ServiceID and -Unattended parameters at the commandline if you want to specify the ServiceID directly.
Use Get-CsRgsConfiguration -Identity Frontend.Skype4bAdmin.com to see valid service id’s

Note either of these options will disable script update checking. So it pays to check manually every now and again.

Applying the Holiday sets

After you have run the script, you can find the time frames in the Response Groups Editor, Simply tick the states you want the workflow closed for.
Each of the states already includes the National holiday set, so there is no need to tick both.
I’ve also added a new reminder feature showing when the script was last run in the RGS editor.

Download

You can grab it from the TechNet Gallery here Download

Fork Me

As alot of my code is open source, I’ve moved from storing my Git repo on VSTS over to GitHub. Feel free to fork the code for your own purposes over here

Advanced

The default holiday set names are “National”,”Victoria”,”New South Wales”,”Queensland”,”ACT”,”Northern Territory”,”South Australia”,”Western Australia”,”Tasmania”
If you need to change these for whatever reason update the following lines in the script

1
2
3
4
5
6
7
8
9
10
<br>
$National = $RGSPrepend+"National"<br>
$Vic = $RGSPrepend+"Victoria"<br>
$NSW = $RGSPrepend+"New South Wales"<br>
$QLD = $RGSPrepend+"Queensland"<br>
$ACT = $RGSPrepend+"ACT"<br>
$NT = $RGSPrepend+"Northern Territory"<br>
$SA = $RGSPrepend+"South Australia"<br>
$WA = $RGSPrepend+"Western Australia"<br>
$Tas = $RGSPrepend+"Tasmania"

Version history

:v2.30: The Feedback Build

Update 5/11/2018 Released Version 2.3
Added display of dates to logs
Added a notification at the end of the script showing the last imported date.
Added last run date
Added RGS Update Time Stamp
Added Error handing for 0 FrontEnds
Fixed a bug with 1 FrontEnd Pools throwing errors when updating existing holidays

Update 19/05/2018 Released Version 2.2
Fixed a bug with logging system culture
Removed some old redundant code
Passed script through ISESteriods PSSharper and applied corrections
Fixed a few typos
Fixed a few bugs introduced cleaning up my dodgy code
Fixed a bug with multiple pools using the same holiday set names
Deprecated the ServiceID parameter, Specify the pool FQDN instead
Added warning for deprecated ServiceID
Updated Pat Richard’s website
Removed PowerShell 5.1 cmdlet (Get-Timezone), now using a WMI query instead

Update 11/05/2018 Released Version 2.1 with TLS 1.2 support
Added Script logging
Updated to use my new autoupdate code
Added ability to switch between devel/master branches
Added timezone offset detection / warning
Added TLS 1.2 support for the new Govt website requirements

Update 09/10/2017 Released Version 2.0 with a Massive Overhaul, updated for 2018!
Added Autodetecton of single RGS pool : Added Autodetecton of single RGS pool
Complete Rewrite of existing rule rewrite code , Should make for alot less red text!
More User friendly and better instructions
Fixed a few typo’s causing dates to be incorrect.
You no longer need to “Reassign” the holiday sets to response groups anymore.

Update 2/11/2016: Released Version 1.1 of the script. Fixed Onedrive download link

Fix for Typo in Victora Holiday set causing import to fail
Fix ForEach loop not correctly removing old time frames
Fix Documentation not including the SID for ServiceID parameter

Update 26/09/2016: Fixed some Typo’s. Thanks Grieg

8 thoughts on “Automatic Australian Holiday Rulesets for Response Group Service

  1. Pingback: Announcement: New version of my Australian Response Group Holiday Rules, Now fully automatic every year! | Skype4BAdmin.com

  2. Corey

    I really like this one, however it seems that the Linux DateTime is the wrong in the XML

    Easter Friday for Australia, the RawDate in the XML is 1522328400

    PS H:\> $udate = get-date “1/1/1970”
    PS H:\> $start = ($udate.AddSeconds(1522328400).ToLocalTime() | Get-Date -Format dd/MM/yyy)
    PS H:\> echo $start

    returns a Start Date of 29-03-2018 Which is the day before Easter Friday

    I have changed the following lines to fix it

    Line 527-537

    $udate = get-date “1/1/1970”
    if ($ConvertTime) {
    #American Date format
    $StartDate = ($Udate.AddSeconds(([int]$event.rawDate+86400)).ToLocalTime() | get-date -Format MM/dd/yyyy)
    $EndDate = ($Udate.AddSeconds(([int]$event.rawDate+172800)).ToLocalTime() | get-date -Format MM/dd/yyyy)
    }
    else {
    #Aussie Date format
    $Startdate = ($Udate.AddSeconds(([int]$event.rawDate+86400)).ToLocalTime() | get-date -Format dd/MM/yyyy)
    $EndDate = ($Udate.AddSeconds(([int]$event.rawDate+172800)).ToLocalTime() | get-date -Format dd/MM/yyyy)
    }

    Reply
    1. James "UcMadScientist" ArberJames Arber Post author

      Government department getting date formats wrong? never! Let me have a look.
      Edit, the date in the XML is correct.
      Time Conversion

      Correct Timestamp

      Also seems to work fine from my machine.
      Can you raise an issue on GitHub so I can try this?
      Also what’s the output of get-culture and get-timezone from your server/management box

      Reply
      1. Corey

        Yep, the problem is that it is returning the UTC date. It needs to add the timezone offeset for this to work properly

        Reply
  3. James "UcMadScientist" ArberJames Arber Post author

    That’s a powershell function (.tolocaltime) which suggests your timezone or culture is set incorrectly.
    Many of my customers use this script and I haven’t had any reported incidents yet, but its something I’m looking at catching in future.

    Did you have any luck with the get-timezone or get-culture?

    Reply

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.