Now, my skills in JQuery are very minimal, never really used it much but I have just started picking bits up so I’ve decided to start using it where I can, so there is probably an easy way round this that I am unaware of.
In previous blogs we have described the difficulty in editing the public facing website outside of the sandbox tools,and not being able to locate let alone edit the root.master page. Since then we have discovered more permission settings that were only available to Tim, we now have majority access to the files containing the public facing site, including root.master. I thought this might be a nice time to add some JQuery in after opening the master page in advanced settings and inputting/referencing the JQuery library I clicked save, Sharepoint Designer asked me if I was sure as this would change it from the site definition (I was aware of this, after all, I did just add some extra code in). Before adding any actual JQuery into the site pages I decided to check the site in the browser, it didn’t load, for some reason it wont accept any variation of the root.master page, it has to be to the site definition so I was forced to reset the root master page. Now I could create an entirely new master page mimicking the root master, but this would be time consuming and quite annoying.
There must be a better way to add Java into the site as recreating the root master doesn’t seem like the right way, it shouldn’t be so difficult, the only thing I am wondering is if it would be any easier for the Enterprise version of 365 as the P1 plan claims that no IT professionals are required, so obviously that leads to very little customization beyond the sandbox.
In an article by Steven Vaughan-Nichols, he suggests that if many people were to move to web based systems for work and not just Office 365, bandwidth may become a problem in the future especially with the web already saturated with many video sites streaming content to its users. For Steven’s full article see: http://www.zdnet.com/blog/networking/office-365-8217s-potential-fatal-flaw-not-enough-internet-bandwidth/1204?tag=search-results-rivers
In an article on nathanneil.com there are some valid points about how the system works should any circumstances change. The first being what happens if the organisation wishes to leave the Office 365 service for something else. How will users be able to keep their data, emails and even retrtact any domain name they have linked to the service.
Another potential problem that could occur is when an employee leaves. What happens to their account (emails & data)? The article suggests that the organisation would be required to continue paying the subscription for this employee to keep the data secure and available.
A third point to note is that Microsoft say Office 365 can encrypt your emails, which is essential if you are in the medical or legal fields, but it will only work if you buy extra equipment and have an IT professional that is trained and experienced in connecting the rights management system to Office 365.
A fourth point to note is that although Microsoft offers a 99.9% uptime, this is only scheduled uptime. This means that Microsoft could give advance warning of any scheduled downtime. This time would not be included in the guarantee. The message here is that the organisation would not have any control over any downtime, and this ultimately could cause disruption to its staff and or students. I posted a question about this to the Office 365 community, here is the link: http://community.office365.com/en-us/f/148/p/5707/22878.aspx#22878.
From a review written by Mary Branscombe for PC Pro, it is suggested that there are a few features missing from the beta version of Office 365. It is not yet clear when or if the features discussed will be implemented.
The first point Mary discusses is the lack of tools available for partners to manage Office 365 for customers. It is said that these tools will become available at some point, possibly once the service goes live to the public. At the moment these tools are said to be missing due to the fact Microsoft are still working on privacy concerns. At this stage I cannot see this being an issue for the implementation of the service within the University.
Another issue Mary discusses is that voice has not been fully integrated with the online service. It is not yet possible to give out one telephone number for all your possible locations; desktop, deskphone or mobile. Currently Lync offers voice and video conversations, but only through a desktop client, meaning that you cannot take advantage of this feature should you be on the move.
Another potential problem is the lack of federation of public IM services. Lync will only let you connect with Windows Live users, and not Google, AOL or Yahoo.
Lync Online does not have many management tools, although you can control domain federation to allows connections with partnering companies, using blacklists or whitlists. However, currently in the beta version you require a Lync Online hosting provider to on-premise Lync servers to make this function work. This is expected to be fixed before the service goes live to the public later this year.
Office Web Apps
Office Web Apps is a great way for anyone to access a document from almost any device at anytime. However Office Web Apps may not be able to fully replace the software version, as they are only light in their functionality. This means that Office Web Apps will not have the same feature rich facilities that users are familiar with. This may or may not be a problem for some users. The system can be combined with the software version to provide a more complete package.
It is important to note that there may be limitations depending on the web browser you use or your clients use. Microsoft notes that it [Office 365] is fully supported by Microsoft Internet Explorer (7.x or higher) and partially supported by Mozilla Firefox (3.x or higher) and Apple Safari (3.x or higher). Other web browsers may have functionality issues.
This link details known issues with specific web browsers: http://technet.microsoft.com/en-us/library/cc263526.aspx
It should be noted that Windows XP Home and XP Media Center don’t support federated identity for authentication across firms’ IT infrastructure or partner IT systems using single sign-on (SSO).
Office 365 Plans
General feature limitations could occur as Office 365 has different plan levels, at different pricing levels. Potentially this means that depending on the budget the organisation has for the system, all the desired features may not be available.
Inactivity Periods are a good method to detect when a user’s activity stops and to then log them out of the system for security of personal data etc. Office 365 does not have this feature, and could potentailly leave data at risk of unauthorised modification or theft. Ultimately it’s the user’s responsibilty to protect their data either by logging out of the system when they move away from the PC or by locking the PC. Inactivity Periods are an extra layer of security, but not essential if users act responsibly.