• This was fixed today. It was due to a missing Security Group in Active Directory.