rpenhale Posted May 1, 2012 Posted May 1, 2012 http://support.capitaes.co.uk/ChangeRequest/DetailChangeRequest.aspx?Status=Vote&Score=2&id=%c3%97%c3%a0%c3%92%c3%9a%c3%a8%c3%a8%c3%95%c3%9c%c3%a3%c3%a3%c3%92%c3%a1 I don't know if this feature would be useful to others but I have submitted a change request (see link above) and would welcome any other supportnet users to vote in favour of what we feel would be a very welcome improvement to Solus 3.
rpenhale Posted May 1, 2012 Author Posted May 1, 2012 (edited) Details of CR No. 1205-1085174 Deploy to specific machines initially not after a previous deployment We have 265 Solus enabled workstations here at South Dartmoor. When we initially roll out a SIMS release via Solus 3 I need to ensure it is functioning for a number of Key Users such as our attendence officer, Cover manager etc. When we first deploy SIMS via Solus it can take quite some time so the ability to ensure key users are successfully updated before then rolling out to all SIMS workstations is critical to us. Status: Published for consultation Edited May 1, 2012 by rpenhale
matt40k Posted May 1, 2012 Posted May 1, 2012 Mmm... I wouldn't want to be the one to define key users - that's a minefield in itself. It would better in terms if you were going to test something, you would want to limit the impact of rolling back. Personally, unless your on the early release, I can't see it being that useful compared with the other requests on the S3 list. If key staff - bursar, cover, attendance, exams, timetabler etc, they tend to have desktops, want it first, schedule the release in advance - 2 weeks - for a late night, then get them to leave their machines on. They can then come in early, their machine will be upgraded whilst everyone else has to wait whilst it upgrades.
rpenhale Posted May 1, 2012 Author Posted May 1, 2012 (edited) I totally see where you are coming from, but I would have thought seeing you can choose which machines to deploy to after the initial deployment the ability to choose when you first deploy cannot be too difficult to include without a huge amount of effort. I'm sure many would find this useful. Edited May 1, 2012 by rpenhale
matt40k Posted May 1, 2012 Posted May 1, 2012 Not really, the first deployment does a bit more. You would basically require it to support two versions of SIMS... one which would knowingly not work.
matt40k Posted May 1, 2012 Posted May 1, 2012 You could maybe get the way it batches machines up, so give machines weightings, so say the attendance person gets upgraded in the first hit as it were... but scheduling in advance would be better.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now