I am still very unclear as to why having an MSI wrapper for SIMS deployment is considered to be so necessary by some on this forum but it really has hardly hit the radar on our SupportNet site which is really well used by schools. I know some of you wags have said that is because we have worn them down but I have strong evidence to suggest that our standard routines for upgrades are working well in thousands of schools.
•Over 2000 schools will download an upgrade automatically within 24 hours of a release (we have a web service which monitors the success or otherwise of upgrades). Taking upgrades like this would not happen if those schools experienced problems.
•Primary schools are doing unattended upgrades using our standard deployment. I understand that doing it via MSI would require technical knowledge beyond many of these school's reach.
•A posting on the last thread suggested that upgrades hadn’t really been a problem for 18 months and even then the problem had been caused by someone pressing cancel.
One issue is the time it takes to do a client upgrade on a low bandwidth wireless LAN. We are researching to see if possible to move to a more incremental approach and do have some ideas.
An argument for an MSI wrapper was allowing the administrator to chose the time of the upgrade however unless machines are left switched on overnight I don’t see how that helps. If the database has been altered the client must be upgraded before a teacher can use SIMS. SIMS is in use throughout the working day.
A standard install is so simple these days, so I am not certain how MSI would save a huge amount of time.
I would really appreciate constructive help as without a clear understanding I cannot justify diverting resources to this project and away from what our school consultation groups have told us to concentrate on.