Jump to content

Recommended Posts

Posted

Hi all,

 

Was hoping someone could help, we've just had Solus 3 thrust upon us and I'm lost!

 

After reading through the schools manual from Capita myaccount, I can successfully deploy the Solus3 agent to all our clients that need it, it installs almost instantly without any issue on Windows 8.1 or 10. After the initial deployment, most clients downloaded the update for SIMS Workstation and upgraded. However a few (both 8.1 and 10) have just got stuck at "successfully finished downloading update..."

 

Looking in programdata/capita/solus3/deployments/packages the file sizes match the files found in the deployment share.

 

However checking the solus console on the server and using the agent deployment log i see:

"The socket connection was aborted." "Error downloading package" - these packages reference though match the size in the deployment share.

 

I tried to redeploy to this same laptop and its saying the same thing. Client says downloaded successfully - log says failed, and it doesn't appear to update, have left it a good 20 minutes now.

 

Anyone have any ideas?

Posted
When that happens, I remove it from the console, uninstall the agent, then try again. Sometimes, certain machines flat-out refuse to install for me - these either get reimaged or I cheat and copy the SIMS folder onto them manually (along with SIMS.ini in C:\Windows).
  • Thanks 1
Posted (edited)
Thanks @3s-gtech literally just uninstall from control panel on client? Or just use the reinstall client button on the console? Also do I need to clear the files in programdata? I noticed they aren't removed after an uninstall. Edited by beany1
Posted

Thanks again @3s-gtech so I did that, from control panel, reinstalled agent no problem, same messages again after another redeploy. So I thought, just try another redeploy, I forgot to remove the filter so everything was selected all I could see was the 1 laptop! So it redeployed to the SIMS server!

 

However! After it redeployed to the server its installed to these 6 laptops no problem even ones without reinstalling the client! What's going on?!

Posted
Possible that the redeploy pushed the config back out, if you have that set in the SOLUS 3 console. Sounds like you had something a bit skewed on your original deployment (don't worry, you probably did nothing wrong) and another push has corrected it. Best to remember that the software is a bit of a black art, but IME it's actually pretty good.
  • Thanks 1
Posted
There is a software utility apart with sims where you can clear out old errors from machine which don't need to be there. I Assume you use the SA username within your company/ school
Posted

Thanks @ITJS2015 by old errors do you mean the "The socket connection was aborted." "Error downloading package" ones? if so those are time stamped they aren't old!

 

Not sure what the SA username is!

 

However, now that I accidentally redeployed to the server new installs seem to be working ok. I've just had a part timer come in who has a laptop so SIMS hadn't updated and solus client hadn't been installed, I installed the client using a domain admin account, then ran a new deployment for just her laptop and it installed pretty sharpish.

 

Is that how it's supposed to happen, once a deployment has failed or couldn't connect does it just give in? Or is it supposed to keep trying? The client installed instantly when I asked it to, but didn't install SIMS workstation till I ran a new redeployment...?

Posted (edited)

That would be S3Unlock: http://www.edugeek.net/forums/mis-systems/124621-solus3-reset-install-active-agents-utility-matt40k.html

 

 

However, now that I accidentally redeployed to the server new installs seem to be working ok. I've just had a part timer come in who has a laptop so SIMS hadn't updated and solus client hadn't been installed, I installed the client using a domain admin account, then ran a new deployment for just her laptop and it installed pretty sharpish.

 

Is that how it's supposed to happen, once a deployment has failed or couldn't connect does it just give in? Or is it supposed to keep trying? The client installed instantly when I asked it to, but didn't install SIMS workstation till I ran a new redeployment...?

 

It should 'check in' whenever they reconnect. I have some machines in my office as spares - they get turned on once every few months and they will always pick up the latest SIMS updates without needing any intervention.

Edited by 3s-gtech
  • Thanks 1
Posted
Thanks @3s-gtech so do you think something is wrong? I mean I left the laptop sat there with client a good 15 mins, what I don't understand is that the solus server shows the agent "agent responded to status check" but it just sat there doing nothing. Deployments show as "Partially successful"
Posted

Unfortunately I had the same problem where sims said it had installed successfully but sims wasn't there, I called my support team who logged in and they ran a utility which is apart of solus 3, I will try and dig it out for you. It cleared the errors from machines which had tried to deploy out and then once that had been done you can redeploy sims.

 

 

As I am still working with a backwards network (don't ask why lol) I have to install the agent on a local machine first and then go into sims add the machine but on the network tab which then starts the solus deployment.

 

Sims silly but works great, im in the middle of trying to get my boss to go domain so we don't get problems like these again

Posted
Try a manual check-in on the laptop - open the Solus3 Agent Notifier in the tray and click on Applications then Check for update.

 

From reading other posts on here, I was under the impression this doesn't work currently that there is a bug?? If not then there is really a problem! When I click check for updates I get the error "Cannot deploy SIMS Summer 2016 Full Release (7.170.46) as the update is missing from the repository." This does it on all clients - even those who did update successfully from the first initial solus deployment!

Posted
Haha, oh dear. That error comes up on them ALL including the ones who updated successfully originally! Have tried reinstalling like previously still same error!
Posted

Have you paid in to capita support ? I know they are useless but you may actually find someone who knows what they are talking about.

 

We use a 3rd party company called OSMIS which are a company who with capita on the side and they are better to work with.

 

Its worth a shot to try and get down to the bottom of this and call capita

  • Thanks 1
Posted

Thanks @ITJS2015 . We have a SIMS support company contract in place, I'm just assuming its a problem with the workstations configuration (which I'm responsible for!), rather than SIMS/Solus (that they're responsible for!). I'm going to give them another call today.

 

As I've never seen Solus in action, its hard to tell whats working as its supposed to and what isn't!

Posted

Depending on what support you have bought in they should be able to at least give you a rough idea what it is or just actually fix the problem.

 

It seems to be it would be a server problem, have you ever tried exporting the agent from the server then mapping the S drive and installing the agent from a location on the server.

 

Then go on to you server (make sure then computer name is removed from the list before installing the agent) add the computer name back in to solus console but with in the agents tab.

 

This should be located after when you click on the sims.net tick box and then you have network and agents on the top, if you click agents your computer name should be there and hopefully it should work.

 

 

Have you ever tried that it could be a multiple computer name issue within DNS

 

Have you every tried UAC to a low level

 

Have you tried it could be a firewall issue on your laptop

 

Have you given access to your cryto folder withing the appdata on your current user with full permissions ?

 

 

Please give them a try above and hopefully crossing fingers it should work

  • Thanks 1
Posted

SIMS and SOLUS will work with UAC on fully. I would never recommend lowering that level.

 

It may be worth doing another sync with your upstream SOLUS server - whether that's LEA or Capita. It may be that you're missing some required updates. Click on Check for updates in the SOLUS3 Deployment Service console under Upgrades.

  • Thanks 1
Posted (edited)

Thanks for all the suggestions everyone!

@ITJS2015 - tried all of those apart from UAC. the permissions for the crypto folder I'm assuming its just on the server that needs changing like the solus handbook states? Win 10 have firewall - but all ports enabled from the solus handbook, Win 8.1 firewall off.

 

I've now officially run out of borked clients! I spoke to our support who suggested the same as you @3s-gtech to re-download. The check for update button on the client instantly started working and they think this could of been causing the problems! Hopefully this has solved the issues! Failing that, ill start crying in this thread in a few months time!

Edited by beany1
  • 2 weeks later...
Posted
From reading other posts on here, I was under the impression this doesn't work currently that there is a bug?? If not then there is really a problem! When I click check for updates I get the error "Cannot deploy SIMS Summer 2016 Full Release (7.170.46) as the update is missing from the repository." This does it on all clients - even those who did update successfully from the first initial solus deployment!

 

We have had this a number of times - we just re-download the Full release in the update library again (even though it says downloaded) and it springs back into action again. Curious!

Posted

There's a known bug that Solus3 DS likes to delete it's updates for no reason in the latest release "work in progress" so says Capita engineers :p

 

Steve

  • 2 months later...
Posted

Just an update for those interested, Capita have raised the issue of the deleting updates up to their 3rd line developers. There's a workaround for now by moving the auto-extract from "after deployment" back to "after download" and this seems to stop the issue occurring, but the developers are having a look at the reason.

 

You can easily replicate the bug (at least from all our and Capita testing) by deploying it once, after the deployment finishes the package will extract and delete the source (Not supposed to happen). Thus causing the no update in repository error if you try to update again after this deployment :)

 

Steve

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 account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...