Skip to main content

Office 365 for students

On Monday, undergraduate and taught postgraduate students returning for the new semester were greeted with a new e-mail service.  Using Microsoft's cloud-based system, Office 365, this new service gives students a modern web interface and a maximum mailbox size of 25GB each.

The service also provides a new student e-diary. In due course, this will become an important source of information, as further projects will automatically populate students' diaries with personalised timetables and other key appointments. 

In addition, students also have access to web versions of Microsoft Word, Powerpoint, Excel and OneNote; and space to create a personal web site. These are currently not explicitly supported by IS; we are simply giving students access to this functionality for them to use if they wish.

A lot of work went into this move.  Last semester we moved research postgraduate students onto the staff e-mail systems, as feedback from the schools showed that this was the option preferred by a significant majority.  Infrastructure was set up to federate our Active Directory credentials to Office 365 and to route all mail via the University's mail routers.  Tools and strategies were tested for migrating students' existing mail, with mail migration happening behind the scenes since October.

There were hiccups along the way.  Despite a wide consultation to choose the best (or least worst) date to make the move, there a few staff were still caught out and unhappy about the timing.  Also, at one point before Christmas we were quite worried about the time being taken to migrate the mailboxes, until we discovered that the poor performance was caused by an unnecessary virus checker on the migration servers. 

The actual transition seems to have gone very smoothly for the vast majority of people.  Yesterday we had nearly 18,000 unique logins.  On the first day, we had only about 50 support calls, most referring to the same problem which we quickly fixed.  Yesterday, we discovered a cohort of visiting students who had not been migrated across, which we will sort out tomorrow.  While any oversights are regrettable, these are small numbers compared to the overall number of students.

The big question, of course, is whether the students like the new service.  Our service and support staff are keeping a close eye on this.  The informal feedback that I'm hearing third hand is very positive, with far more "likes" than "dislikes".

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…