Obviously I don't know the internal workings of Capita but even agreeing to take on a project like this could prove to be a complex bureaucratic task itself.
I have voted too, but here I have a program I wrote (c#) that I run which monitors the solus3 agent temporary extract directory and pulls out the MSIs (along with some other stuff that can be safely ignored). I only have solus 3 agents on 2 machines here, the server and my PC (out of SIMS running on about 200 PCs). I simply start the deployment, fire up my monitor program on my PC (I called it solus3 harvester) and wait. When the agent has installed the client software on my PC, I pull the MSI out, push it out to a test PC to check it works and then distribute it across the network to clients which need it - simples.
If anyone would like a copy, let me know.
I suppose it comes down to the old phrase "big ships turn slowly".
@woodham if you have the CR numbers i'll go and support. Can't currently get on due to an error at their end, and don't fancy the nightmare of a CR search.
As for the web-based MIS, i'm sure it's being worked on, but in the meantime they do offer SLG (Don't shout at me, i'm just saying) which allows web reg. Plus there are add-ins from TASC and Bromcom which will do it also. So there's enough out there that they can work on the major project rather than rushing to get a single module up in a hurry.
There is pro solution which has a basic web part and a msi based client.
Anyway on topic I have to ask "what for". People don't bat an eyelid when software doesn't come MSI'd and they spend an hour or so doing it themselves. Why is it different for SIMS? (That's rhetorical, it isn't different, but I'm asking why people think it's any different)
Ok, so again how is that different? You still can't deploy to machines that aren't physically there/on with MSI. You can redeploy them at your leisure with either solus 3 or MSI. If you're having that level of difficulty then can I assume you've yet to install solus 3.5?
That's when you need sccm.
- Standard install/uninstall/upgrade procedure including handling permissions.
- Standard patching procedure
- Management and reporting - you can easily collect install state, features/versions/patches installed.
- Rollback if install failure
- Logging to windows logs
- Self heal for damaged installations
- Can be advertised for on demand installations
It's not so much "why don't they do it" which we all believe including myself would be nice, it's just the amount of hate people levy towards Capita for not doing it that I find odd. There's been far worse after all, I'm sure many of us remember trying to package any crap from Pearson-Heinemann back in the day before they realised the error of their ways.
I think its that this particular issue sums up Capita's attitude.
We asked for an msi, they looked at it, said they would do it, then u-turned and told us they knew better than us and came out SOLUS 3, which has generated no small amount of stress among us, and refuse to comment on the msi thing.