MrMat

Ahh excellent. Cheers guys. We're using SQL 2008 as well so hopefully it should work okay. Will try installing later today and see how we get on (not going to do it now, only 'officially' been in this role since Friday so will wait for the boss to return and run it past him before I try installing anything on the shiny new server haha )

Hmmmm at what point did you get that message? I've managed to extract all the MSI files. I havent tried installing yet but they all seem to load up alright on the Server. Have you had any issues specifically with these 2012 servers Rawns?

Sorry to bump an old thread but I just wanted to add that we are having the same trouble as Synaesthesia. New server running 2012. Brand new install of Solus 3. The thing completely refuses to install, we don't even get to chance to configure anything. Run the EXE and pow "This operating system is not supported". Logged a call with Capita who responded with: 'This is expected...We are very optimistic that this will be supported in the 3.6 release'

I think I hate your brother just a little tiny bit

Woooooow!!! That looks awesome! That certainly makes me feel like it's time to upgrade my setup (which currently consists of a steering wheel bolted to a cheap ikea desk lol).

So who plays? I've seen it mentioned once or twice throughout the forum but noticed there aren't any actual threads about it. It's utterly fantastic for anyone into Motorsport.

Job done!

Saw it last week and thoroughly enjoyed it. It's a Ronseal film, it does exactly what it says on the tin.

Aha. I did not know that although actually now you've mentioned it it's obvious really as it's essentially doing the same thing i.e. restarting the agent.

We've just had to deal with an abundance on Incompatible database errors after upgrading about 60 schools via Solus 3. As mentioned above this error is purely done to the workstation being 'out of date' in comparison to the server. To resolve these errors we first tried to redeploy to see if that picked up any that were missed. We then asked each school to create a list of badge numbers for those workstations that still werent working (there were two of us doing this and we split our upgrades so we had a maximum of 10 going per night over 6 days to soften the blow). We then checked these badge numbers to see if they were listed in our deployment service. If they werent listed in the DS we simply added them to SOLUS. The agent downloads and the upgrade goes through. If they were listed but still werent working it was usually because users either didn't see the warning upgrade message or just decided to ignore it completely and leave SIMS open. If SIMS is left open when the upgrade is due to go through the SIMS.net folder cannot be accessed and the upgrade will fail (obvious comment is obvious). To resolve these - First find these comps in the Deployment Service and check the version number (view agent details). Important note, more often than not these workstations will still display 'Update was successfully installed' even though they have in fact failed (good old Capita eh). Get the user to get out of SIMS and then redeploy. Alternatively, get the user out of SIMS, open network path in explorer, locate the SIMS.Net folder and either delete it or rename it to 'SIMS.net old' or something similar, then connect to that workstations Services and restart the SOLUS3 agent service. The agent will then realise there's no SIMS.net folder and will download and install the correct version. For us at least (besides a few abnormalities) SOLUS3 worked exactly as it should have and the vast majority of problems were down to user error or outdated information.

DNS seems fine. IP addresses came back all okay. I'm pretty much stumped. I've got our network/ICT guys looking into who seem think it's most likely a permissions issue even though I have domain admin rights. Hmmm. Thanks for your help buddy

Yes indeedy!

Thanks for the reply Rawns. They are indeed all on the domain and actually they are also all Desktop PC's.

Morning all. Hope you’re all having a good ‘last day of term’. I’m once again in need of a little assistant. We’ve installed agents on a good 1000ish workstations so far mostly without hiccup however we are having problems with about 6 or 7 which simply refuse to install and return this 'Access Denied to the remote machine' message. We use a third party firewall which is fine, these computers have the same policy as all the other computers which have gone through successfully. Windows firewall is definitely turned off. I’ve checked the ‘User Account Control Settings’ to ensure its set to the lowest setting (as advised by a chap at Capita). I’ve also tried messing with the Computers Management Administrators Groups to make sure we are in the right group with correct permissions etc. (I'm not 100% but this does seem to only be affecting Windows 7 machines) Still nothing. Anyone else come across this before? Any help would be greatly appreciated. Cheers, Alex

All I know is the conversation with my mom to remove this filter so my lifetime membership of big butts bonanza doesn't go to waste is going to be awkward...

Cheers buddy. At least I know it's not just me being completely stupid We are indeed using 3.5. I've logged a call with Capita so will see what they say when they respond. On a related note, I noticed at the top of this page you guys refer to the location where the upgrades are stored locally on each workstation i.e. C:\users\all users\capita... Is this still the same or has it now changed? I can't seem to locate it on XP or 7 machines. Would be useful to know if the upgrade files have actually gone out. Thanks again. (For some reason my crappy Internet Explorer isn't allowing me to respond directly to posts...DOH!)

Thanks Rawns! You will no doubt be seeing alot of me around these parts over the next few months while I try get my head around this Solus 3 lark. Back to Solus...We've already downloaded the latest upgrade (a week or so ago) so that's just sitting in the repository. We've currently got Auto Download turned off so all the agents are happily sitting there minding their own business. When we deploy to a school (we're doing 1 at a time at the minute) the workstations for that estab all start downloading the upgrade and then begin installing. This all works relatively well. However what I want to happen is for the upgrade to download prior to us deploying so that when we do deploy, each workstation is ready to install straight away without having to wait for the upgrade to download. Now as soon as we turn Auto Download to Agents on, even if we havent scheduled any upgrades to take place AND we've set the maximum concurrent downloads to 5, 30 odd agents all from different establishments start trying to pull the download. I was under the impression that by setting the maximum to 5 it would only allow 5 agents at a time to pull the upgrade from the repository so not to put excess load on the server? Have I understood this wrong or is Solus playing tricks on me? Thanks for your help. Ps. Love this ლ(ಠ_ಠლ) 'Solus, y u try to download to all ma agents'

Afternoon all, Sorry to bump an old thread. We've recently upgraded to SOLUS 3 and have just started pushing out our first batch of upgrades to a select handful of schools (so far pretty successfully too) but we are having a bit of trouble with the auto download to agents feature. From the Updates tab within System Settings on our main SOLUS 3 Deployment Service we set the maximum concurrent downloads to 5, tick the auto download box, set the times accordingly and then hit save. Now this is the part where things start going a bit wrong. Instead of 5 agents trying to download the upgrade, we get a huge bunch (probably around 30-40 agents) going mental all trying to pull the upgrade at the same time. Any ideas? Am I missing a step? I've looked through the Capita notes and don't think we have but you never know. I have logged a call with Capita but not heard anything back yet. Cheers. Ps. Hellooooo everyone!