SIMS Summer 2025 loads of failed installed

[David44]

1 minute ago, 5nowman said:

 

Did you do the following in sophos too - server and workstation?:

 

AMSI Protection:

C:\ProgramData\Capita\Solus3\Deployments\
C:\ProgramData\Capita\Solus3 - Real-time only
 
Exploit Mitigation And Activity Monitoring:

C:\ProgramData\Capita\Solus3\Deployments\**

These appear to relate to Solus, which we don't use, so I didn't add those paths. We don't have a Capita folder within ProgramData anyway so we don't have anything attempting to run from there.

[jamiehall]

30 minutes ago, David44 said:

Is SIMS now installing without the exe file hanging for everyone else or have you just learned to live with it?

We have been deploying SIMS by launching SIMSApplicationSetup.exe (and the other exe files) and then forcing it to close after 5 minutes to get around the issue but I'd like to sort this out properly, especially for SIMS updates. Did the Sophos exceptions work for anyone in the end?

We want our users to be able to run SIMSLoad.exe to update SIMS. Currently when they do this, they see the same issue as is being reported with SOLUS, SIMSApplicationSetup.exe will launch (and get to 100%, before disappearing from the Windows task tray) but it will remain running and SIMSLoad will never move on to the next exe.

We don't use SOLUS so the only exceptions I have added to Sophos, under Endpoint Protection - Global Exclusions are the following...
C:\Program Files (x86)\SIMS\SIMS .net\

 

S:\SIMS\Setups\SIMSApplicationSetup.exe

S:\SIMS\Setups\SIMSManualSetup.exe

S:\SIMS\Setups\SIMSAMPARKSetup.exe

 

I also tried adding \\servername\capita\SIMS\Setups\SIMSApplicationSetup.exe

These changes don't seem to have made any difference, the .exe files still run successfully and then hang when they are run silently from the command line or called by SIMSLoad.exe

Is everyone running SIMS and Sophos still seeing this issue?

Yeah still having the same issues, still need to whitelist any of the installer files - primarily "Exploit Mitigation And Activity Monitoring".

[psydii]

45 minutes ago, jamiehall said:

Yeah still having the same issues, still need to whitelist any of the installer files - primarily "Exploit Mitigation And Activity Monitoring".

Edu app installers behaving like malware is *so* 2004.

[Sheridan]

We're still seeing random issues with the Autumn 25 update - same end result 'one or more errors occurred' but a lot less than the summer 25 update

[David44]

I've finally got this to work, don't get too exited through, we don't use Solus here so I don't know a fix for that.

In Sophos, I just needed to exclude the paths
\\SIMSServer\Capita\SIMS\Setups\SIMSApplicationSetup.exe
\\SIMSServer\Capita\SIMS\Setups\SIMSManualSetup.exe
\\SIMSServer\Capita\SIMS\Setups\SIMSAMParkSetup.exe

from 'Exploit Mitigation And Activity Monitoring (Windows)' (and turned off all Mitigations) in Sophos Central.

Of course, I could have also made a single entry of
\\SIMSServer\Capita\SIMS\Setups\**

but the three entries seemed slightly safer.

This means that users can run SIMSLoad.exe once again (which we will now put back as part of the standard SIMS shortcut) and it is able to update the three components.

To test, make the above change, update Sophos on the client (About, Update), delete c:\program files (x86)\SIMS\SIMS .net\simsload.ini and then run SIMSLoad.exe, watch as it installs the three SIMS components and creates/updates SIMSLoad.ini and be glad that you never got involved with Solus.

Of course, this doesn't resolve the issue when we use MCM to deploy SIMS because it isn't being deployed from the SIMSServer. It makes me think that perhaps we could deploy it from there though. I will look in to that. A luxury that I assume Solus users don't have.
 

[Homer]

Sorry to drag this up, those lumbered with SIMS and running Sophos Intercept in conjunction with Sophos Central - what settings have worked for you? I'm still having a lot of issues with SIMSApplicationSetup.exe hanging open on these machines. 

 

SIMS is making me greyer. 

[TooOld4This]

This has been posted before but worked for us...

 

AMSI Protection:

C:\ProgramData\Capita\Solus3\Deployments\
C:\ProgramData\Capita\Solus3 - Real-time only
 
Exploit Mitigation And Activity Monitoring:

C:\ProgramData\Capita\Solus3\Deployments\**

Edited January 6 by TooOld4This

[David44]

Where is SIMSApplicationSetup.exe running from?

It sounds like the paths that @TooOld4This has given you are for Solus, but if you are deploying SIMS using another method, you'd need to apply similar exceptions to those path(s) instead.

[markwilfan]

We've added the relevant paths into Endpoint Protection - Global Exclusions and we are still getting issues with solus deployments

 

[markwilfan]

Strike that last post it's working!