Wayne_K

We use Dameware to support our End Users on an internal network. When the user has FMS or NOVA open we find that when Dameware sets up the connection, the application on the End User client, crashes. Has anyone had any experience of this or with other Remote Support Apps causing a similar thing happen? If so, did you find a fix?

Thanks for that Greg, we currently operate in the same manner but I was considering moving to 'Full' mode.

Does anyone have their SIMS Databses set in 'Full' Mode? Allowing restores from the Transaction Logs? I can see the advantages of the 'Full' Mode but am unsure if it has any impact elsewhere? or if it is even supported by Capita?

How would I check the Disc Queue Length? There is an extensive query running that CAPITA have noted but said it was ok, even though it is running at around 3millions operations a second!!! This has been queried multiple times but I have been told by CAPITA Engineers and a CAPITA Dev that this is not the cause of the high CPU.

The homepage widgets were set by the school to show quite a bit of information. We removed the setting to push homepage widgets to staff to see if this would be reduce the load and saw no change in performance.

One of our Servers is performing really poorly, the CPU Utilisation shows SQL running at 100% from around 9am on a morning until 3-4pm on an afternoon. (When the teachers are logged in and using SIMS) CAPITA are really scratching their heads to try and resolve this one, so I wondered if anyone out there had any thoughts. The server follows a pattern on our performance graphs showing the CPU spike daily to 100% and stay that way until mid afternoon, clearly showing this is a load issue somewhere. Any help is really appreciated. We have tried: Reboots, Index Patch (Multiple Times) Detaching and Re-Attaching Databases Increasing RAM from 6GB to 8GB as requested by CAPITA Tech Spec of Server E6250 @ 2.4GHz Quad Core VM 8GB of RAM Windows 2008 SP2 64BIT OS

Rawns - Another quick question. How do you deal with knowing if the site has actually updated the site? Do you just liaise with the onsite network manager? The reason I ask is I know Capita have plans for better reporting to a Central DS at LA level in the future but they have said currently there is no way to know what the local DS on site servers are doing at upgrade time.

Thanks Rawns - Thats very interesting and has given me something to think about over the weekend. I have my setup with the Central Server at LA level but have all the agents listed there rather than at local school server level. I just had my concerns about the Auto Deployment, as I didn't trust Solus3 not to roll out the update automatically without me giving it the ok first! Thanks again..

Hi Rawns - Im quite Jealous! Can you tell me more about your setup. Are you running the Solus3 DS locally to the clients? How long after the 'Partially Successful' message did the offline clients come online? Did you have any other scheduled deployments listed following the Summer Release? Sorry to ask so many questions, I am just trying to get a clear picture in my head how our sites differ and why mine failed if yours worked so well.. (Just to add to the Solus3 fun, as I am writing this all my agents, all 140+ are offline, 90+ of these are servers that I know 100% are online - THE JOY!!)

* Update * - Capita have taken my log files to investigate the problem. I agree with the above, when it works, it works well. BUT. We have our Solus3 DS on a single central server and hope to use the central DS to manage our 90+ sites we support. So when it Fails, it Fails dramatically!!

Can you explain, how your SIMS.INI differed please? I have seen a similair scenario and had to stop and start services and alter the time ranges in-order for the update files to be downloaded to the agents. AFAIK - the SIMS.INI I have set on my sites are correct.

Hi All Spent quite a bit of time with Solus3 over the last few months, and view many threads on here. I was under the impression that with Agent Version 3.4.118 any machines in a Deployment that is OFFLINE would, when it came ONLINE, get the update it was intended as instructed with the Deployment. So to break it down. * Summer Release is Deployed to a site. * Machines on the Site that are online get the update * Machine that are offline do not get the update. * The Deployment ends with a Partially Successful Message * Agents that were offline that come online I thought should now get the update from Spring to Summer.....??? If this is correct?, this is not what I am finding and wondered if anyone else out there has witness anything similar? Going to discuss with Capita but wanted to know what the rest of the community had experienced.

That's very interesting as I rarely get a SIMS deployment that finishes successfully. They always end up Partially successful due to other machines been turned off. I gave up on the reports and use some VBS scripts that run at logon to log the version of Pulsar, FMS, Discover Executables to a CSV file. Hopefully in next release this will be resolved.

Hi Mike_1 What problems were you having prior to the update that you state have now been resolved? I am having problems with my sites and I am trying to gather as much information as possible. Cheers Wayne

Hi Rawns. We have 90+ schools running from a central Deployment Server and have had no end of problems. What problems are you running into? How do you have your sites configured? From your post it sounds as though you have a Deployment Server on each school site, is this correct? Have you attempted a full SIMS.NET Upgrade yet, How did it go? Hope you don't mind sharing your experience. Cheers Wayne