News

  • Google Calendar now moves events to Trash

    posted Thursday, November 5, 2015

    Ever deleted a calendar event by mistake and wanted to get it back, just like you can with email? Now you can. Google has added Trash functionality to its Calendar on the web, providing an easy way for users to view, permanently delete, or restore individual and recurring deleted calendar events.

    Trash is accessible from the calendar's dropdown menu in the "My calendars" section as well as from Calendar Settings. This functionality is available for both primary calendars and secondary calendars for which people have edit rights.

    http://googleappsupdates.blogspot.com/2015/11/restore-deleted-events-in-google.html

  • Google Calendar Outage

    posted Wednesday, November 4, 2015

    Google Calendar experienced a service disruption on November 4, 2015 from around 8:20am until 10:25am. A cause has not yet been reported.

  • Service Center Announcement

    posted Tuesday, October 6, 2015

    On Monday, October 12, 2015 campus Connect users will be re-directed from the UCSB Connect website to the UCSB Enterprise Technology Service Center (ETSC) website to submit service requests.  As of that date, if you have an issue or request regarding Connect Email and Calendaring, you can submit a service request on the ETSC website. 

    EXCEPTION:  If your local IT department has advised you to use an alternate process for Connect support, this change will not affect you.  You will continue to follow those procedures.

    This change is being made to provide you with more efficient and timely responses to service requests.  Also, each service request will include a Service Level Agreement.  These are agreements with the Connect customer community regarding the response and resolution times for each submitted request.

    If you have any questions or concerns, please contact the ETSC Call Center at (805) 893-5000.

    Below are some basic instructions for filing on-line Connect service requests as of October 12.  Additional information and instructions will also be posted prior to this change.

    BEGINNING OCTOBER 12 – HOW TO REQUEST HELP FOR CONNECT EMAIL AND CALENDARING SERVICES

  • Google Calendar for iOS & Android guides published

    posted Sunday, September 13, 2015
    We recommend the Google Calendar app for either iOS or Android. Guides are published here:
     
  • Migration to Google Calendar is underway

    posted Friday, September 11, 2015

    Reminder: Do not use Oracle Calendar today. The current status of the migration can be seen at http://www.connect.ucsb.edu/about/google-calendar-migration-status

  • Migrating from Oracle Calendar to Connect (Google) Calendar in one week.

    posted Saturday, September 5, 2015

    As has been previously announced, we are migrating from Oracle Calendar to Connect (Google) Calendar in one week. Please review the notes below to prepare yourself for the migration.

    • Please do NOT access Oracle Calendar (or Google Calendar) beginning 5:00pm on Thursday, September 10th through 8:00am on Monday, September 14th. This includes using your mobile devices as well.
    • Your Meetings, Day Events, and Daily Notes from January 1, 2013 into the future will be migrated to Connect Calendar. If you want to retain information prior to that date, instructions for exporting your calendar can be found at: http://www.connect.ucsb.edu/usage/corporatetime/exporting-corporatetime-data
    • Prior to September 10th, we strongly recommend that you print out your Oracle Calendar schedule for the month of September so you can refer to it during the outage.
    • Sharing of your Connect Calendar (i.e., “Access Rights” in Oracle Calendar) will be set to “See only free/busy (hide details)”. You will need to configure sharing for individuals who need to see more or who manage your calendar. NOTE: Please be aware that if you make someone your delegate, s/he can see your “private” events.
    • Depending on your department’s directive, resources (e.g., rooms, vacation schedules) will be migrated. Their names will be slightly different and sharing will need to be assigned. Please contact your local department support if you need access to a resource.
    • Day Events (flag) and Daily Notes (pushpin) in Oracle Calendar will both become “All day” events in Connect Calendar.
    • Tasks in Oracle Calendar will not migrate. To retain a copy, “show all tasks” and print to a PDF. Ask your local department support if you don’t see this option.
    • Meeting “Details” (notes you shared with invitees in Oracle Calendar) will migrate to Connect Calendar, but “Personal Notes” (notes only you could see in Oracle Calendar) will not. Meeting attachments will not migrate.
    • Some complex repeating meetings may not stay “chained” together; there is a possibility that they will appear as individual events.
    • The default for event reminders is 10 minutes in Connect Calendar (the default in Oracle Calendar was 15 minutes). You will be able to change this after September 14th.
    • There is a chance that meeting notifications for past meetings may be re-sent during the migration.

    Connect Calendar training information may be found online at: http://www.connect.ucsb.edu/training

  • 100% Migrated to Google Apps

    posted Wednesday, August 19, 2015

    As of today we have completed the migration of e-mail accounts from Office 365 to Google Apps. In total, 1673 Person accounts & 498 Functional accounts were migrated.

  • Office 365 Unexpected Outage

    posted Wednesday, July 15, 2015

    Office 365 is currently experiencing an unexpected outage which is affecting the ability to use desktop, mobile & web-based clients. We will follow up once we know more.

  • Connectivity Issues with Office 365

    posted Tuesday, June 30, 2015 to Wednesday, July 1, 2015

    Wednesday at 6:00PM, Microsoft reported that issues with Office 365 related to mailbox connectivity have been resolved. Here is the official response:

    Final Status: After engineers completed the corrective actions on the remaining mailbox capacity, engineers have confirmed that the service is restored.

    User Experience: Affected users were unable to connect to the Exchange Online service when using multiple protocols including Outlook, Outlook Web App (OWA), Exchange ActiveSync (EAS), and Exchange Web Services (EWS). Additionally, affected users were unable to receive email messages.

    Customer Impact: A higher than average number of customers reported this issue. Analysis indicates that customers likely had some users experiencing this issue. This event affected approximately five percent of users. For customers on a small portion of mailbox capacity, the majority of users were impacted by this event.

    Incident Start Time: Wednesday, July 1, 2015, at 7:05 PM UTC

    Incident End Time: Thursday, July 2, 2015, at 12:00 AM UTC

    Preliminary Root Cause: A high-level portion of the network infrastructure became degraded, which caused an interruption to Exchange Online connectivity. 

    Next Steps: The following is a list of known action item(s) associated with this incident. As part of the Office 365 problem management process, additional engineering actions may be identified to improve the overall service.
    - Action: Review network routing to avoid communication interruptions related to network infrastructure issues.

    A post-incident report will be available on the Service Health Dashboard within five business days.

  • Connectivity Issues with Office 365 Resolved

    posted Wednesday, May 13, 2015

    At 1:30am Microsoft reported that issues with Office 365 related to mailbox connectivity have been resolved. Here is the official response:

    Final Status: Engineers connected the affected users to replicated capacity to restore service availability.

    User Experience: Affected users were unable to connect to the Exchange Online service. As a workaround, users may have been able to retry connecting as the issue was intermittent.

    Customer Impact: Customers reported that they experienced this issue. 

    Incident Start Time: Tuesday, May 12, 2015, at 11:50 PM UTC

    Incident End Time: Wednesday, May 13, 2015, at 8:30 AM UTC

    Preliminary Root Cause: A portion of the Exchange Online service infrastructure became degraded. 

Pages

Subscribe to News