Jump to content

Solus 3 feedback

zag

By zag
in MIS Systems

 Share

Recommended Posts

Rawns

Rawns

Posted
Posted
Our biggest problem with S3 is that half of our workstations failed with the update and they just won't update, keep reporting as offline even though they clearly are online. Have tried disabling firewall, renewing IP's...just just wont deploy.

All the machines are setup the same with the same policies etc as well.

 

What is confusing is how the other half are working fine. All are on Windows 7 and all deployed S3 and Sims originally with no problems.

This is the first time we have tried updating and despite having great experience with the initial setup and deploy, the update is proving a NIGHTMARE.

 

Sounds like it could be DNS issues. If firewall is off, it's the only other main reason why they would be offline in SOLUS3 (unless the S3 agents had died on all the devices).

MalekoUK

MalekoUK

Posted
Posted
Sounds like it could be DNS issues. If firewall is off, it's the only other main reason why they would be offline in SOLUS3 (unless the S3 agents had died on all the devices).

 

We did think that at first, we noticed some wouldn't ping via their name but would via their IP. However one workstation that keeps failing will ping via its name and keeps appearing as online then when you either deploy or check the agents status it then goes offline again... Yet DNS is a bit on/off it seems so that needs sorting anyway.

Rawns

Rawns

Posted
Posted
We did think that at first, we noticed some wouldn't ping via their name but would via their IP. However one workstation that keeps failing will ping via its name and keeps appearing as online then when you either deploy or check the agents status it then goes offline again... Yet DNS is a bit on/off it seems so that needs sorting anyway.

 

What IP address does the workstation in question have? Does it match the IP address that's returned when you ping the name? If not, do a ping -a xxx.xxx.xxx.xxx and see what name is returned.

  • Thanks 1
MalekoUK

MalekoUK

Posted
Posted
What IP address does the workstation in question have? Does it match the IP address that's returned when you ping the name? If not, do a ping -a xxx.xxx.xxx.xxx and see what name is returned.

 

Interesting, we get a random pupil computer name... So yes the IP doesn't correspond with the workstation in question.

Rawns

Rawns

Posted
Posted
Interesting, we get a random pupil computer name... So yes the IP doesn't correspond with the workstation in question.

 

Good stuff. Hopefully that should point you in the right direction for any other devices you have issues with. :)

 

When it comes to SOLUS3, DNS can be a serious pain in the rear!

matt40k

matt40k

Posted
Posted
worst piece of software I have ever used

 

Worse feedback ever :p

 

Go on, I've taken the bait, (I'm assuming this place is based on logic which is based on facts and not gossip) why is it the worse piece of software you have ever used. List your woes as I doubt it's the first piece of software you've used that was constructed by mere mortals.

 

(Sorry, if it's rather sarcastic it's just been one of those days)

Griff

Griff

Posted
Posted
Worse feedback ever :p

 

Go on, I've taken the bait, (I'm assuming this place is based on logic which is based on facts and not gossip) why is it the worse piece of software you have ever used. List your woes as I doubt it's the first piece of software you've used that was constructed by mere mortals.

 

(Sorry, if it's rather sarcastic it's just been one of those days)

 

- why does a machine show as status failed but comment is update was successfully installed

- why does it show me over 80 agents online but when I hit deploy on the update they start coming in as offline and I am talking large numbers..and I have checked the DNS and IPs etc etc it all looks fine

- the DNS issue..why does it rely on DNS so much? OK I will concede the point about DNS should be in good working order and healthy but we are talking about schools here and anyway I have been banging software out on Group Policy for years no problems why is it so difficult with SOLUS3?

 

I could go on but quite frankly whats the point. I have offered a few times for capita helpdesk to come in and do an upgrade for me and I will watch...no takers so far

 

You've obviously never used Testbase :p

 

Testbase is far easier to install :D

Ghostgame

Ghostgame

Posted
Posted (edited)
- why does it show me over 80 agents online but when I hit deploy on the update they start coming in as offline and I am talking large numbers..and I have checked the DNS and IPs etc etc it all looks fine

 

I would check the heartbeat settings in SOLUS3. If the box is unticked, the only time that S3 knows that a workstation is offline is when you do an update. This happened to me with a school.

 

- the DNS issue..why does it rely on DNS so much? OK I will concede the point about DNS should be in good working order and healthy but we are talking about schools here and anyway I have been banging software out on Group Policy for years no problems why is it so difficult with SOLUS3?

 

I have no idea. If it didn't rely so much on the DNS it would save me alot of work as well.

Edited by Ghostgame
Deleted error to avoid giving bad advice.
matt40k

matt40k

Posted
Posted

I'll let you off as it's Monday morning mate.

 

The original deployment says fails, why doesn't it update - I guess the correct answer is it DID fail and in order to preserve the historical record it needs to remain as failed. Otherwise when you come to pull off reports on the success rate of SIMS deployments it would be 100% every time. It needs a "deployment status" - the status due to that deployment, and a "current status" - ie the status you spent the last 3 hours trying to get to ;) Ideally you'd want a dashboard that shows your current status of all your machines so you don't have to go hunting.

 

The DNS question, it relies on DNS because we don't assign static IP address and we don't work well with large numbers, so we have to rely on a central database that has a friendly name and it's (IP) address. Capita are right not to rely of NetBIOS as they are reasons why it's a legacy protocol.

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
 Share
Go to topic listing


×
×
  • Create New...