CCS has received reports of users not being able to print to network printers. After troubleshooting and researching the cause of the problem, it is determined that the September Microsoft Windows security updates have caused an issue with network printing for some users. The End-User Computing (EUC) team is investigating options to resolve the issue.
Please accept our apologies for any problems this may cause.
– Computing and Communications Services
On Wednesday September 15, 2021, CCS noticed that some Android phones are unable to connect to the WiFi network. The issue was reported to the vendor for a resolution.
Update: September 17, 2021 aa:30 AM
Authentication issues for Android devices have been resolved
We apologize for any inconvenience this may have caused.
-Computing and Communications Services
On Friday, September 3, 2021 some users may get “Gateway timeout” upon logging in through CAS. Affected users will have to retry logging in.
CCS team is working to resolve this issue
Update: at 14:35
A fix was implemented to prevent the time-out error. Services resumed normally.
We apologize for any inconvenience this may have caused.
-Computing and Communications Services
On Friday August 13, 2021 an access outage to RUFIS occurred between 00:03 AM to 9:40 AM. The problem was traced to a failed automatic update.
We apologize for any inconvenience this may have caused.
-Computing and Communications Services
CCS is experiencing issues with the phone system used by the Help Desk (Student and Facutly/Staff) and the Switchboard. The Telecom team is investigating with the vendor.
Update: at 10:50 AM
All services resumed. Jabber users need do to “Reset Jabber” to get back online
We apologize for any inconvenience this may be causing.
Computing and Communication Services
The D2L Network Operations Center (NOC) advised us that on May 27, 2021 between 3:04AM (ET) and 3:13 AM (ET) an infrastructure event caused D2L Brightspace to be unavailable.
This issue has been resolved.
We apologize for any problems this may have caused.
Computing and Communications Services
On Friday May 21st, 2021, we received a few reports where users were getting “Script Error” when signing on to RU-VPN2 via CAS (Central Authentication Services) from Windows. After investigation, we found that this is due to the internal browser that RU-VPN2 Windows client uses may not be compatible with the script that the recently upgraded CAS runs. CCS technical team is continuing to work to resolve the issue.
Please note that this does not impact existing RU-VPN2 sessions. This also does not impact Mac Users. After getting the “Script Error”, Windows users can either click Yes or No to continue to sign on to CAS to use RU-VPN2.
Update – May 21st, 2021 2:20 PM – The issue has been fixed.
We apologize for any inconvenience this may have caused.
-Computing and Communications Services
Since 7:00 am today (May 10th, 2021), some users have not been able to log in to RUFIS and users may experience the message, “The system has encountered an error when servicing the request. Please try again. If the error persists, please contact the system administrator”. CCS technical team is investigating the issue and will update when there is more information.
If you only need to access the iExpense module, it is not impacted and is available within the my.ryerson portal under the APPS tab (Ryerson Financial Information System (Expense Reports)) and you do not have to use RU-VPN to access it.
Update – May 10th, 2021 11:39 AM – RUFIS system has been restarted and service is back to normal at 10:40 AM. CCS technical team is still investigating the root cause.
Please accept our apology for any inconvenience this may have caused.
-Computing and Communications Services
Starting on Wednesday, April 05, 2021 at 10:00 AM, the departmental shares access experienced performance issues due the implementation and migration to a new backup solution. The migration was suspended today, Thursday, April 06 at 12:34 PM and will be resumed during non-peak hours.
We apologize for any inconvenience this may have caused.
-Computing and Communications Services
Starting April 23rd last Friday, U2F security key stopped working on Chrome (version 90.0.4430.85) in incognito mode and Edge (Chromium 90.0.818.49) in InPrivate mode for Central Authentication Service (CAS). This was due to a Chromium update that was released. A bug request was submitted to the Chromium project. Chrome has since released a new version 90.0.4430.93, which has this issue fixed. If you experience this issue in Chrome, please update to the latest version. We will update when there is an update from Edge. Please note that this issue does not impact both Chrome and Edge in regular mode.
Update – May 7th, 2021 – The latest Edge (Chromium 90.0.818.56) has this issue fixed.
We apologize for any inconvenience this may have caused.
-Computing and Communications Services
