Jon Hopkins's questions

A client has rolled out a beta version of an application to a number of Blackberries manually and now wants to delete it ahead of rolling out the new version.

Is it possible to do this remotely using the BES (Blackberry Enterprise Server)?

I'm guessing so but if it is how (just rough pointers would be great) and does it need any user interaction (and indeed could the user interfere with or prevent the deletion)?

Apologies for a relatively trivial question, I just don't have a BES to play around with right now.

I work for a small development house who are increasingly being asked to put together formal SLAs for our products based on particular configurations.

From a development side of things I'm comfortable with this, however there's no point in my saying that we'll meet particular targets from a software perspective if they're not realistic from a hardware/platform perspective - the clients only care about overall system availability.

What should I be looking at from a platform perspective? What sort of metrics and levels?

Also, what are the gotchas (for instance from a software perspective I'd never commit to a fix time - I have no idea whether I'm going to have to rewrite the whole product to correct something so saying that we can fix it in 5 days is potentially impossible - what should I avoid committing to from a hardware/OS/platform point of view)?

I'm looking at putting together a support SLA. As a base line I'd like to know roughly what sort of percentage availability I should expect from a non-clustered Windows 2003 Server.

Assumptions are that the server is comfortably spec-ed for the application it's running (so it won't be labouring) and that by uptime I mean that the server is available. It needs to undergo reasonalbe general maintenance (security patching and the like).

What would people expect?