[sims] SOLUS3 3.4.103

[Mike_1]

Hi,

 

Has anyone upgraded SOLUS3 to 3.4.103 yet? Whats new in this release?

 

Also does anyone know if you can go from 3.4.24 straight to 3.4.103? I only ask as a few of our schools where we haven't yet made the transition to SOLUS3 are still on 3.4.24, i just wondered if i'm going to have to go over them and upgrade to 3.4.64 first and then do 3.4.103.

 

I've read quite a few negative comments about SOLUS3 but its going ok here so far, we have had a few issues along the way but they have turned out to be more issues with the schools network such as DNS etc than SOLUS3.

 

Thanks

Edited December 2, 2011 by Mike_1

[matt40k]

Would install the new version. You can go from any version of SOLUS3 to the new version.

 

It's resolved (not yet checked), if your SQL service is stopped\times out, but the S3 service is still running it thinks it needs to re-reg it's self.

Redeploy is very useful

Fix with deploying FMS where it would only deploy FMS Apps and not BDE, SQL 2005 Native client etc.

You ping the clients every x mins to confirm the online\offline status - useful for laptops as they tent to just disappear and poor s3 is stuck thinking it's online when in fact it's offline - Network traffic hasn't increased greatly - maybe 1~4kb for every 10 workstations.

[Mike_1]

Nice one, cheers Matt. Will give it a try then.

[Kaz77]

How do I get the latest update? I thought the point of Solus 3 was that updates would be released automatically however, I seem to have to contact Capita each time I need an update via Solus 3, for both Solus and SIMS updates. Does anyone else have this issue? Our school doesn't have SIMS updates managed by the LA.

[matt40k]

Well SIMS is currently withdrawn, the others - FMS Autumn 11 and SOLUS3 3.4.103 should automatically get released to single sites and LAs (which you are?) - LA managed have to wait on the LA to authorise as they tend to have a master plan and do additional testing.

[Cache]

I've just spoken to the helpdesk about this (didn't get chance on Friday) and was told that 3.4.64 was the latest version available and that the Solus 3 update was withdrawn also.

[matt40k]

I've just spoken to the helpdesk about this (didn't get chance on Friday) and was told that 3.4.64 was the latest version available and that the Solus 3 update was withdrawn also.

 

Err, they got that wrong. Currently deploying it to a school as we speak!! @PhilNeal can you confirm and follow up please

[Mike_1]

Err, they got that wrong. Currently deploying it to a school as we speak!! @PhilNeal can you confirm and follow up please

 

I've deployed it to a school this morning too

[Cache]

Err, they got that wrong. Currently deploying it to a school as we speak!! @PhilNeal can you confirm and follow up please

 

I've deployed it to a school this morning too

 

Didn't think it seemed right, but the guy I spoke to went and checked with someone else and they both came back and said that 3.4.64 was the latest version. Will hope @PhillNeal checks the thread and replies and I'll phone helpdesk back again.....

[PhilNeal]

I'e checked with the desk and SOLUS has not been withdrawn. Autumn SIMS is being issued today.

[Cache]

I'e checked with the desk and SOLUS has not been withdrawn. Autumn SIMS is being issued today.

 

Thanks Phil, I'll phone up again tomorrow and ask for it to be released again.

[matt40k]

Also SIMS Autumn 11 out now.

[Cache]

I'll leave that another week before I go near it

[matt40k]

I'll leave that another week before I go near it

 

Wimp

[Heebeejeebee]

Just installed 3.4.103 today and a few niggles are fixed but it's still a bit irritating that if you re-image your machines you'll get loads of redundant entries in the database due to the UID SOLUS assigns them. SOLUS doesn't seem to detect that they no longer have the client installed (it's not built into our image and it wouldn't help if it was due to the UID anyway) and you can't just re-deploy the client on it's own so you still have to use the remove PC option and then re-install again (along with re-deploying SIMS, FMS and Discover). It's a bit anoying and time consuming to do that if you've just deployed an image to 600 or so PCs.

 

So far so good though and no great reliability issues so far.

 

HBJB

[matt40k]

Just to check, when you say re-image? Do they get the same SID id as before?

[Heebeejeebee]

Just to check, when you say re-image? Do they get the same SID id as before?

 

No. Sysprep assigns a new one at the end of the imaging process. (I haven't checked to see if SOLUS uses the SID of the machine or its own.)

 

HBJB

[matt40k]

Err... doesn't this duplicate accounts in AD??

[Cache]

Wimp

 

I had enough problems yesterday after a powercut at the weekend, can do without SIMS causing me any more this week

[Simcfc73]

Baby steps from Sims. The redploy is fine but flawed.

 

If I redploy say 30 machines and 3 of them fail, if I go into redploy again then all the machines say successful NO.. so if I click Select unsuccessful all get deployed again. Also, why does it list all the machines again when you redploy 30?? I have 130 deploys to look through. This morning I had around 30 with deployment timeouts when I suspect they were off which solus 3.4.103 should have fixed.

 

Its just a mess and we shouldn't have this with every update.

[matt40k]

So they failed because SOLUS3 believes they are online, but they're not?

[Simcfc73]

So they failed because SOLUS3 believes they are online, but they're not?

 

Not sure, I think so. I have a nice mix of successful, offline and failed. I've increased the timeout now for the deployment so see if that helps because I am getting partially successful deploys everytime.