You won't be worrying about deploying it via Group policy when SOLUS3 phase 2 comes out.
SOLUS 3 phase 2 (will refer to as P2) is included as part of your normal license cost (shocking as it may seem that Capita isn't charging for it). P2 will be able to use AD to discover your machines. Once you've got a nice list of computers you can then deploy the agent out, which in turns installs SIMS (and FMS etc), sound like MSI over AD? Well once you've got the agent out you can report on basic info (CPU, RAM, HDD space), so you can print it off, go to SLT and go, hey I need x new machines because there rubbish and won't run SIMS well. Come upgrade day, the server pushs the update out to the client, because the agent is running as a service it doesn't use the users permissions, nor if they've tried to open SIMS or indeed logged on!
Say you have 5 SLT fixed workstation, you could have it set to roll back should those 5 machines fail to upgrade successfully. It should be able to WOL as well, but we'll see. They are talking about using it more, so when they mess up a release rather then making us re-download the same release, minus the one file they had to change, we could just download that one file.
That's all assuming they do what they say, still looks promising, field trial soon. So fingers cross, SIMS upgrades will be breese - we'll be showing off how quick we now do upgrades ;)
so they've recreated microsoft's deployment system because they couldn't make an msi?
Because again, it goes back to the orginal issue, i have just rebuilt a workstation, when will SIMS get installed? When will this Solous 3 V2 "agent" get installed? Straght away? After 2 days? When it feels like it? or am i going to have to manually install SIMS. Why do Capita "just not get it"
That's a real shame, my hopes for proper .MSI are dashed, hopefully RM will continue to provide a blue print so that we can deploy SIMS.net through the industry standard method we all know, love, and respect.
localzuk - I typed my comments at exactly the same time as you ... I guess it shows that great minds think alike
Most of that structure already exists via BITS, using MSI, MST and MSP files, using GPOs and other pre-existing tools. Why are they reinventing the wheel?
Hopefully SOLUS 3 P2 will work well... as I know for a fact that P1 doesn't quite work as intended. There are still some issues with it not seeing all of the machines on the network and it sometimes fails to push out upgrades and installations. Still, it's in the testing phase so hopefully all of that will be ironed out once it does get released. :)
Unfortunately this scenario seems all too farmiliar
10 Ask user what they want
20 Get wrong answer from user
30 Promise them what they asked for but will take time
40 Do something else
I don't see why this is such a huge problem. Just run the EXEs silently. It's worked for us perfectly for the past five years.
I people would actually be happy that they are doing something positive. Not every school has SMS, not every school as a domain. SOLUS3 isn't costing the schools anything and will allow a single tool to pushing out SIMS to the desktops\servers across the school\LA.
It's going to far better than if they create MSI's.
(SOLUS3 agent is actually an MSI by the way, I believe they looked at creating MSI for all the apps, but it wasn't flexiable enought - couldn't cope with the multiple installs)
The problem is all that functionality they've added just replicates what I already have in a way that won't integrate with my existing reporting / deployment.
Reporting and audit (GLPI/OCS) doesn't require SMS and many, many schools do have domains.
They've made SIMS easier to deploy if you don't already have anything in place, but if you do it's just another tool that won't get used and isn't really I'd been hoping for.
It drives me mad that every software company under the sun thinks it's a great idea to have their own auto-update app rather than tying into existing infrastructures*.
(*yes, this is partially a Windows problem).