The first casualties

January 20, 2010

Well testing is well and truly under way and already I have ruled out three devices as unsuitable.

Sony Ericsson Satio:

What can I say? This is touted as Sonys flagship cameraphone using the cybershot brand. Running the very mature Symbian S60 OS with a 12.1 megapixel camera and a strong heritage I expected a lot from this. Sadly I have been extremely disappointed. As a former K800i owner, I know that Sony are capable of producing an excellent phone capable of withstanding a lot of punishment with plenty of features that do exactly what you want of them. With the Satio, Sony seem to have gone backwards and concentrated on reducing costs rather than producing a quality product.

Just looking at it in the box I was surprised at just how cheap it looked. On taking it out and handling it it became even worse. Much of the phone is constructed out of plastic and sprayed with a silver finish to give the impression of metal, but it is done so badly that just by looking you can tell it is cheap plastic. Given a reasonable amount of use, I can see this coating flaking off very quickly. It feels very flimsy and you are scared to handle it too much, as it feels like it is going to fall apart in your hands.

I was unsure about the usability of the phone as it is touch screen only, but given the large 3.5″ screen I felt that there was enough room to have a usable virtual keyboard. The room is there, but the implementation of the keyboard is appalling. It isn’t accurate enough and at times struggles to keep up with a moderately fast typing speed. Even the camera doesn’t save this phone as the 12.1 megapixels do not seem to produce a good image, all they do is make the photo size larger. Given the price tag of nearly £500 for an unlocked version, Sony should hang their head in shame. It feels like a <£50 copy of a much better phone.

OK, my job is not really to provide a mobile phone review, but to put them through their paces and find out how well they manage to provide a desktop replacement service to our mobile users. Immediately this phone failed. We need something that will take some real-world use without falling apart, and as I mentioned earlier this is so flimsy I think you would be lucky to get a few months of use out of it before it fell to bits. The keyboard isn’t responsive enough to use comfortably. It didn’t seem to want to let me access our exchange server to retrieve email and it kept dropping my wireless connection. Using 3rd party tools I could connect to our vpn and then rdp to a desktop, but the frustration in doing so because it kept dropping the wireless connection just wasn’t worth the effort.

Overall Rating 2/10

Palm Pre:

Unable to tell you much about this phone other than it was quite comfortable to hold, felt well built but the keys on the keyboard were too small, fiddly and just seemed to be in the wrong position to use for anything other than small text messages or emails. The reason I can’t tell you any more than that is that when you switch it on it needs a sim card before you can do anything. Most phones that are being sold as a mobile computing device rather than a phone will at least let you get to the rest of the phones features without a sim, you just don’t get to make any calls. Not a major problem you might think, just pop a sim in and away you go.

Unfortunately it isn’t that simple. After inserting a sim card I was presented with a screen asking me to log in with my Palm Profile, or create a new one. Apparently you need a Palm Profile to access Palm services such as phone updates and the phone will not let you use it until a profile is registered with it. I tried to create a profile, which had to include some personal details like an email address, but on clicking finish I kept getting the error message that it couldn’t complete the registration as there was no wireless carrier. This was despite me being able to see a full signal. This could be because we bought a unlocked phone and used an Orange sim card in it, but O2 have the exclusive Palm contract in this country and maybe it didn’t like the Orange network. Registration must take place over a mobile network as you cannot get access to the WiFi settings until it is completed and you can get into the settings menus.

Even if I had managed to register a profile, the fact that the phone needs to be tied to one person renders it unsuitable for our purposes as we need to be able to hand the devices out to whoever needs one. We really couldn’t give out phones that were able to access another persons private details. My rating for this phone is purely based on suitability for our use and should not be taken as a reflection on the phone itself as I have not been able to use it. It may be a very good phone for an individuals use, but it is definitely not a corporate device.

Overall Rating 2/10

Nokia N900:

I was really looking forward to getting my hands on this much hyped ‘mobile computer’ from Nokia. As it is running Maemo 5 which is a derivative of Debian Linux you should be able to do pretty much anything with it. Sadly, it looks like Nokia have jumped the gun a bit and shipped it without giving developers enough time to get things running on it. Currently there are only 126 apps available on maemo.org and none of them provide the functionality we need. Currently there is no full Java support, no VPN support for anything other than OpenVPN, no RDP client, seems to have difficulty connecting to Exchange 2003.

The phone itself feels like a well made piece of kit, and what it can do it does very well indeed. The touch screen is nice and responsive, the qwerty keyboard has nicely sized keys and is easy to use. Everything that is built in is easy to use, and is very quick at loading.  As it stands though, in order to get full Java running on it, there is a developer forum that details how you have to ssh into the phone, download a 90 day trial version of Java for embedded devices, extract the tarball, install to a location and then edit config files using vi in order to set the Java class paths. Not exactly user friendly. Much of what this phone will be capable of is let down by similar problems. I downloaded the OpenVPN client from the Ovi marketplace to find that no icon appears anywhere and to use it you must drop to a command line to configure it and run. For a consumer hand-held device having to issue instructions to your end-user along the lines of add the repository, use apt-get install, open vi, open the correct config files and then explain why you can’t just type like in a word processor as vi requires explicit instructions to do anything, this is really no good. From an admin point of view, we would have to do this ourselves before handing them out and then deal with any slight issue the end user might come across as mostly they wouldn’t have a clue how to fix it meaning just supporting the devices would be very time consuming.

When the developers really get going with it and the number of apps increases, along with fixed installers that actually put an icon in place for you and don’t need you to go to command line this will be an astoundingly capable device. End users should be able to find apps to do just about everything, geeks will love the ability to tinker with every aspect of the device and the developers will be able to reach a larger audience without too much effort as they should be able to port their existing Linux apps to Meamo without too much effort. Hopefully Nokia are doing all they can to support developers and get this device up to its full potential. Until that happens it will remain a niche device only useful to developers and those who are interested in computing, but of no interest to those who just want to use a computer with a minimum of fuss.

Overall Rating 5/10


Safeguarding Children and thin.clusion

January 19, 2010

We are having a few problems getting the nursery placements that we hope to use in our project to agree to letting our learners take mobile devices into the placement. The main issue, if you haven’t already worked it out, is the ability to take stills/video. Whilst use of this feature is not part of our project as we are all about delivering thin apps to the device, we cannot guarantee that the feature will not be used by our learners (although we hope that they would abide by the nursery rules on such matters). Therefore we are in the process of inviting the nurseries to an information lunch to see if there is a way around this barrier. We have great sympathy for the placements and realise that parents are naturally concerned when they read some of the horrific press that has come out of late. However, we hope to be able to resolve the matter as we feel that use of the device by the learner in situ is an important element of the project.


BSFC Virtual Infrastructure – Update

January 19, 2010

Virtual Service Update.

Just thought I would post an update as to our Virtual Service that we have had put in.

Following KGV’s lead (and expertise) we opted for Novus to install and configure our Virtual Service – KGV have dealt with Novus previously so that helped reduce the stress levels.

We opted to purchase the server hardware from Dell and I installed all of the hardware into a nice new shiny server cabinet, all very tidy and a nice KVM Switch to top it off.

Click here for a bigger version.

The actual service took 3 days to install, and tie into our existing infrastructure. We opted to run the service on a FQDN of https://virtual.bsfc.ac.uk/ ( this FQDN routes requests to an internal server via a Microsoft ISA rule – thus reducing the attack footprint ).

A few little niggles were found upon installation that seemed to be bugs with the version we were using (only recently released), these were;

a) Virtual Desktops not being automatically joined to the domain from the Sysprep file – we now have a working solution thanks to Danny @ KGV.

b) Virtual Desktops not defaulting to the domain on 1st startup – the temporary solution is to login to each VM as an admin and then it retains the settings – this is not practical when we roll out 100 desktops!. { Still working on this one }

I did howerver manage to break the system about half a day after the engineer had left – I tried to upgrade the web-interface to the latest version to see if that fixed the problems we had – and failed spectacularly!. The engineer was quite good about it and tried to explain that it wasnt my fault! (I think he was just being polite).

Danny from KGV came over and gave me a good few hours training on the system, including how best to create our desktop images and take snapshots of the servers, etc – he also had a run through of our system to make sure it was all running smoothly. He also helped me upgrade the Provisioning Client to the latest version (which will also be useful for Danny as they can have a look around our one before they upgrade their live version.).

Danny also fixed the problem of the Virtual Desktops not being automatically added to the domain – he wrote a brand new sysprep file and that seemed to work.

KGV also loaned us a Wyse S10 Thin Client Desktop and a Wyse X90 laptop – again Danny sent over the configuration files that they use and I had to fit them to suit.

I’m really impressed with the thin client desktop – I managed to get it up and running very quickly and then skinned it to look like the rest of our college machines.

Click here for a bigger version.

The laptop was very straightforward (after I remembered to turn off the write protection on the drive!) – I just had to alter the settings on the laptop to use our college wifi and also point at our Web Interface;

Click here for a bigger version.

Again I really must make a point of thanking Martyn & Danny at KGV. Their tolerance of my newbie questions has been great.


KGV Device Update

January 18, 2010

Hi all,

Quick update on where we are up to. Martyn wrote 0n 4/12/09 that we were expecting our mobile devices to start evaluating and I was looking forward to spending christmas playing with the new toys and finding out just what they are capable of. Unfortunately,our supplier failed to notify us that we needed to fill in a credit agreement before they would release the devices. This wouldn’t have been a problem, but the college was closed early just before the Christmas holidays due to the 1st lot of bad snow and then closed for a further week after the holidays because of the 2nd bad snowfall meaning I was unable to do anything to find out why we hadn’t received delivery.

But now some good news! We have received our order and testing can now begin. I have picked devices that represent a good cross section of what is available today. Each device is running a different OS and the aim is to be able to connect to a full desktop with the minimum of effort and the ability to use it comfortably. The device must be easy to configure as having to spend say, half an hour per device before we can give them to the end user is unacceptable.

The devices being evaluated are:

Samsung Omnia Pro B7610 – Windows mobile 6.5

Palm Pre – Palm OS

Toshiba Portege G910 – Windows Mobile 6.1

Sony Ericsson Satio – Symbian S60

Nokia N900 – Meamo 5 (Debian linux)

Motorola Milestone – Android 2.0

Apple Iphone 3GS – Iphone OSX

Elonex Websurfer – Windows XP

Archos 5 – Archos custom linux


BSFC WiFi Update – Jan 2010

January 15, 2010

BSFC Update – Wireless

Well just to give a brief (knowing me it will turn into an essay!) update on our Wireless Infrastructure.

After the small-scale teething problems associated with the change from TKIP to AES we haven’t had a problem with the Wireless setup. We (Computer Services) have been really impressed with the system and now that we are starting to get ‘11N’ spec wireless devices, we can start to see the true value of getting an ‘11N’ solution – login time is 1/2 that of an 11g laptop.

The students are actively connecting to our “BSFC Public” open access wireless. How this works is;

1. They search for the “BSFC Public” WiFi SSID and connect to it (it’s open access)
2. Their device is assigned a DHCP address and given a gateway IP address to our Microsoft ISA 2006 server
3. When they connect to the Internet they are prompted for a username and password box – which is their college network username and password (authenticated against our Microsoft ISA server) – this stops people from outside the college from being able to connect to our system
4. The Wireless controller has an access rule setup within it, stating that any device on “BSFC Public” can only talk to our ISA server on port 8080, so they can’t browse our network.

Again we must give thanks to Martyn & Danny over at KGV who have been a big help.


Calling all the MoleNet’rs (with apologies to Cumbrian legends It Bites)

December 9, 2009

Just a thought – how many fellow Molenet’rs read our blog? I would just like to know if our message is getting across. Maybe people don’t know we exist. If you read the blog how did you find out about it?

If you do follow our blog please email me (mab@bsfc.ac.uk) just so I know you are out there! Maybe we should be following what you are doing? Maybe it’s only us!

Also is there any aspect of our project you would like to know more about? I know it’s in its infancy but we would like to ensure that we blog about what you wish to know as well as just generally rambling on about what we think is important.

Thanks


Let’s take up busking in time for Christmas!

December 9, 2009

Well, at the risk of passing a cap around for contributions, we are still waiting for the funding to be released to us and are worried that the heavies will be sent around as both colleges have already spent a small fortune on infrastructure! With hindsight I think it was a bit late in the year to start the whole Molenet 3 thing (controversial?). Had it begun even a month earlier we would have had time to get the kit in and pay for it before Christmas. In the current economic climate companies are pushing for payment before the standard 30 days and without the funding we are not in a position to pay.

Having said this we should have it by the end of next week – however we finish next Thursday and will be in our homes preparing for the Queens speech!

Still – at least the kit is in and working well (see previous posts from Col and Martyn). After the holidays we get to play with some mobile devices. I wonder if I can buy myself some for pressies and tell my wife they are for the project? 8-)


BSFC Update

December 4, 2009

I’ll pretty much echo what Martyn has said. Nexgen have completed the installation of our Ruckus wireless solution and the whole campus is now covered – this time by a centrally managed solution … a big step up from our (now defunct) wireless system – 24 AP’s around the college all using the same SSID and WPA key – crude but effective.

I suppose it served us well when we had a small wireless platform, but as the times have moved on the system hasn’t stood up to the task, so we are very pleased with the solution that Nexgen have supplied.

At the same time we have also deployed a DHCP server, which will help us to move away from static IP addressing on our clients, this coupled with our ISA Server now allows students to connect their own devices to connect to the internet via our proxy server.

Thanks must go out to both Martyn and Danny from KGV who have been very very helpful in getting both of these up and running. Your support is gratefully appreciated (I promise I’ll sort your Moodle theme out ASAP).

Back to the topic, We have already seen that a few inquisitive students have connected their devices to the Public Access Wi-Fi , even better they have realised that you need to put in your network Username and Password to authenticate you onto the system.

We have had some great feedback from staff who have already noticed the difference in speed/reliability. We did come across a problem with some of our existing clients trying to connect to the new Wireless (which is named the same as our old wireless) – we needed to change the WPA algorithm from TKIP to AES and the devices then automatically connect.

With regards to the students using their own devices, we plan to mirror what Martyn and his team have done at KGV and offer some sessions on helping students connect their own devices.

Next up is our Virtual Infrastructure, which I for one am really eager to get stuck into.

Also not related to the project, we hosted the Merseyside ILT Conference on Thursday and a colleague from Skelmersdale College would like me to visit and help them out with their migration from Athens to Shibboleth (I also got a mention in this months RSC Northwest magazine!)


KGV Update

December 4, 2009

Well things are moving along nicely at KGV. Nexgen have completed the installation of our Ruckus wireless solution and the whole campus is now covered. This has some instant benefits and others which will take a little while to bed in. Firstly, we no longer have to drag around access points with us as we move our wireless thin client laptop trolleys and smaller groups of laptops can break out from the pack.

Our fleet of devices in use by Learning Support are being added to the network to increase the functionality of them in college and our tutors are now able to move their laptops freely around the college for the first time.

We have had our first session with the students and their devices at this morning’s break time. The outcome was mixed. We have had no problems adding Microsoft based devices to the student guest network, Symbian devices also worked, but we had a lot of problems with Apple devices. Annoyingly they all worked fine yesterday, but then that’s IT for you.

Next on the agenda is to expand our virtual infrastructure and to open up the virtual college desktops and applications to mobile devices in college. This has been delayed slightly as we still have not received the funding! I was hoping to have the money in the bank before I started writing out any more big orders, but time is moving on so the orders have been placed. My Finance Director will sleep much better when the money arrives.

Our selection of mobile devices will also arrive in the next few days which means we can start working with the Nursery / Health & Social Care students to see which device would be most suitable for work in their placements. The students here cannot wait to get their hands on them and give their opinions. There is a definite buzz in college at the moment about mobile devices and we are going to have to work hard to keep apace with expectations!


something to ponder

December 4, 2009

I made this entry on my personal blog, so have just placed a link to it from here.  I think it is really relevant to how our learners might behave during our MoLeNET project and quite possibly other projects too.