Got confirmation from Capita as well about this.
Very true but some schools will just work, many will have LA support in place, and all the risk takers on here who have been dabbling will know how to fix our issues ;)
Plus after another 12 months i'm hoping the remaining issues will be cosmetic.
But my main point was more that it's not happening in 'the next couple of months'
I think what Capita are too afraid to say is, SOLUS3 ok (give or take a few bugs), if your network is setup correctly and your working correctly.
IE your removing pc from AD when they get decomissioned etc, machines don't have S3 in the image, your DNS actually works and isn't fudged with host file workarounds. Basically schools have 18 months to move over to Win7/8, Windows Server 2008 R2\2012, Office 2007/2010 and they need to include SOLUS3 in the plan.
Also it's worth checking you don't have any proxy issues - that normally takes months to sort out - unless your using smoothwall of course ;)
Sure you'll be find vikpaw, but they'll be a fair few people who'll be going back to the drawing board on pretty much everything.
SOLUS3 : No likey, no lighty ;)
I was quite fond of the Before Solus 3 @bossman , still i'm sure the new look will grow on me.
I too, like you had a perfect Solus 2 setup that just worked, having worked with Solus 3 now as I have stated its not 100% but that I feel is the nature of the beast and we have to move on to pasture's new.
I do think Capita in their defence created this monster from the needs and requirements bourne from BSF which then fell by the wayside.
Things can only get better as that song goes hehe! :D
Only when these things are included/fixed will I be truly happy using SOLUS3:
- Workstations check SIMS/FMS/Discover version against the and auto-update as soon as they come online
- Automatic housekeeping of the SOLUS3 Repository
- A way to update the Discover config files on ALL devices when you move Discover to a new server
- Auto-attempt to reinstall the SOLUS3 agent intermittently if the install failed because the device was offline.
- Save Admin credentials for the deployment of the SOLUS3 agent
If only microsoft had created a way to deploy MSI files, and self healing MSIs, and the registry.
Yer, if only, and if only Microsoft had created a way to distribute updates and restrict updates for paying customers... and give reports for the support team (la) to confirm the status of the install. And tell me the spec of my machines etc - without buying an extra license (SCCM), and all this without forcing a small primary to buy a Windows Server license...
Oh if only... (waits for the cloud MIS folks to appear)
PS: Please don't talk about ClickOnce, I may start twitching...
bossman, i was actually referring to the photo of "BEFORE SOLUS 3 Bossman" ;)
******* *** **** ****** **** *** solus 3!
What a ****pile!
How unnecessarily complicated do Capita have to make *everything they do* even for their own staff?
Sometimes you need to step back, look at what you've done and think it over for a minute. Think it over from someone else's point of view. Think "Would they think I'm an imbecile for doing that? Is it too complicated? Does it need to be this complicated?"
If unable to do so, ask someone else.
Are you having a Dilbert moment?
Yes. Sitting here, watching solus3 :censored: up another update. I'm having a lot of fun.