Committee meeting - February 20, 2020

Carol Lu Ìý
Secretary to the Committee Ìý
February 20, 2020 Ìý
 Ìý
Present: Steven Bourque, Don Duff-McCracken, Erick Engelke, Paul Miskovsky, Trevor Bain, AndrewÌýMcAlorum, Bill Baer, JasonÌýTestart, Robyn Landers, Pratik Patel, Lori PaniakÌý
 Ìý
Regrets: Dave Kibble, Andrea Chappell, Daryl Dore, Adam Savage, Greg Smith Ìý
 Ìý
´¡²µ±ð²Ô»å²¹â€¯Ìý

  1. Chair’s remarks [5 min.]Ìý
  2. Approval of the minutes of the meetings of Thursday February 6, 2020 [5 min.]Ìý
  3. Email Security Gateway Review (Steve Bourque) [5 min.]Ìý
  4. O365 Steering Committee (AndrewÌýMcAlorum) [5 min.]Ìý
  5. Microsoft TeamsÌýone yearÌýmessage retention policy (Trevor Bain) [5 min.]Ìý
  6. Active Directory LDAP signing in March – issues, plans to implement and how to test (Don Duff-McCracken) [10 min.]Ìý
  7. Other Business [10 min.]Ìý
  8. Roundtable discussion – all [20 min.]Ìý
  9. Next CTSC MeetingÌý[Will be held Thursday March 5 at 1:30 p.m., in EC2 1021.]Ìý

 Ìý
Chair's Remarks (Steven Bourque) Ìý

  • Re: follow up on an item that is not on the agendaÌý
    • The matter of retired faculty retaining access to O365 is being discussed at UCISTÌý
    • We currently offer temporary access to retirees if a request is madeÌý
      Ìý

Approval of the minutes of the previous meeting Ìý

  • The previous meeting’s minutes were accepted as distributed. Ìý
    Ìý

Email Security Gateway Review (Steven Bourque)Ìý

  • The University currently usesÌýProofPointÌý
  • Email security options will be re-evaluated next yearÌý
  • Would like to gather feedback from different groups on campus Ìý
  • A survey will be created to gauge what features like and don't like about ProofpointÌý
    • Will be sent to the security working group, CTSC, and UCISTÌý
    • Any other suggestions on groups that should participate in the survey? Ìý
  • May be a future presentation topicÌý
  • Will be up for renewal in February 2021Ìý
    Ìý

O365 Steering Committee (AndrewÌýMcAlorum)Ìý

  • Would like to set up a formal committeeÌý
  • The existing committee was informal within IST (AndrewÌýMcAlorum, Steve Bourque, Dave Hinton, Lisa Tomalty)Ìý
    • Met monthly or biweekly to discuss changes in O365Ìý
    • Committee stopped meeting during the O365 employee email investigation projectÌý
  • Please contact Andrew (amcalorum@uwaterloo.ca) if you are interested in joiningÌý

Comments and discussionÌý

  • The committee should include a representative for instructors (somebody from Centre for Extended Learning or maybe Andrea Chappell)Ìý

Microsoft TeamsÌýone yearÌýmessage retention policy (Trevor Bain)Ìý

  • Microsoft Teams channel messages are currently deleted after one year of sendingÌý
    • Channel messages sometimes contain important information users may want to referenceÌýlater on Ìý
    • For those who wish to retain channel messages, the current suggestion is to copy the messages into a Word document; this is not efficient or idealÌý
    • Can the retention period be increased? Ìý

Comments and discussionÌý

  • The University Records Manager and Privacy Officer were consulted during the discussion to determine a retention period for Teams messagesÌý
    • They have now advised increasing it to two years is acceptableÌý
  • In some faculties, DeansÌýare able toÌýgrant exceptions to some University policyÌý
  • Microsoft Teams data retention is a topic the new O365 steering committee can discussÌý
  • Skype for Business will eventually be replaced by Microsoft TeamsÌý

Active Directory LDAP signing in March – issues, plans to implement and how to test (Don Duff-McCracken)Ìý

  • Are there any comments on issues, plants to implement, and how this will be tested? Ìý

Comments and discussionÌý

  • Microsoft has been postponing the release dateÌý
  • The framework will be implemented in March and will be optional Ìý
    • IST does not plan to enable the frameworkÌý
    • IST will conduct the regular testing procedures before enablingÌý
  • NetAppsÌýwill be affectedÌý
    • Will Mac and Linux be affected? Ìý

Other businessÌý

WatSAFEÌýdesktop notifications on MacOS (Andrew)Ìý

  • 1.6 will be deployed soon to fix some known issues; more information will be available March 4Ìý
  • The vendor is investigating remaining issues that will not be fixed by the 1.6 deploymentÌý

ExpiringÌýWatIAMÌýaccounts with no sponsorship (Erick)Ìý

  • Asked for an updated list of accounts with 'last known sponsor' information, which is helpful information to have for updating the sponsorship Ìý

Roundtable  Ìý

À¶Ý®ÊÓƵ Undergraduate Student Association (Pratik)  Ìý

  • Looking for resources on how to migrate from CAS to ADFSÌý
  • Most WUSA applications are Ruby on Rails and PHPÌý
  • Reached out to Environment for consultation Ìý
    Ìý

Engineering (Erick)Ìý

  • mod_auth_mellonÌýfor apache, doesn't meet requirementsÌýat the momentÌý
  • Microsoft documentation is not well supportedÌý
    • Supports IIS butÌýnotÌýother driversÌý
  • Are there any installation resources? Ìý
    • Installation without logs is difficultÌý
  • ADFS supports SAML and OpenID ConnectÌý
    • Currently doing installation without logsÌý

Comments and discussion Ìý

  • Contact the ADFS teamÌý
    • Previously reached out to the team and the ticket was closedÌý
  • For SAML on Shibboleth: coordinated with Sean Mason to get Shibboleth logsÌý
  • Booking time to meet with a member of the ADFS team to go over logs is suggestedÌý

Technology Integrated Services, IST (Steve)Ìý

  • Currently waiting on vendor to provide a bug fix forÌýNexentaÌý
    • The fix is expected to be implemented without issueÌý
    • Data will be mass migrated starting next weekÌý
  • Working on migrating campus video surveillance system to AD authenticationÌý
    • Affected groups will be contacted about this change (e.g. WUSA, Library)Ìý
    • Active Directory credentials will be required to access the systemÌý

Arts (Bill)Ìý

  • Received an email from Adobe about the University becoming a part of a price consortiumÌý