This is something I have noticed as well but not got round to logging as an issue.

With older releases of Sage CRM like 2022 R1 the http://servername/CRM/eware.dll/sysadmin URL returns the sysadmin page

However, this stopped working with the release of 2023 R1 / R2 and now returns

Must be a System Administrator and on server, to run sysadmin

If you take a 2022 R1 system with a working sysadmin page and perform an over the top upgrade the sysadmin page stops working.

In the past the "Must be a System Administrator and on server, to run sysadmin" could be resolved by granting IUSR Full Control to the eWare registry keys, but this no longer appears to work.  Even granting EVERYONE FC to the eWare does not resole the issue in my test environment.

This is something I have noticed as well but not got round to logging as an issue.

With older releases of Sage CRM like 2022 R1 the http://servername/CRM/eware.dll/sysadmin URL returns the sysadmin page

However, this stopped working with the release of 2023 R1 / R2 and now returns

Must be a System Administrator and on server, to run sysadmin

If you take a 2022 R1 system with a working sysadmin page and perform an over the top upgrade the sysadmin page stops working.

In the past the "Must be a System Administrator and on server, to run sysadmin" could be resolved by granting IUSR Full Control to the eWare registry keys, but this no longer appears to work.  Even granting EVERYONE FC to the eWare does not resole the issue in my test environment.

It should be possible to call the SysAdmin page using

http://localhost/crm/eware.dll/sysadmin?SID=148328653728462

This is due to a change in 2023 R2.  

So how does that work? How do you get a SID? as per my screenshots, the initial URL has no SID in it, and you used to be able to just swap out the UK at the end and do Sysadmin. 

As you could get to this screen without logging into CRM (useful when all the licences are in use and you need to kick someone out)

I used to use this often as the 'Current user' list (within Activity) is completely unreliable as it returns incorrect data. 

I've tried that but it does not appear to work.

1. Logged into Sage CRM as admin and got the SID from the URL
2. Tried - localhost/.../sysadmin
3. Tried - servername/.../sysadminxxxxxxxxxx

sysadmin is a really useful feature as 

1. You can see who is logged in - so you know it is safe to perform an IISRESET when CRM misbehaves itself
2. You can see which escalation rules are running slowly - so escalation rules which are causing performance issues can be stopped

Hi Matthew

It was changed in 2023 R2 as part of a set of security changes.  (+) Sage CRM 2023 R2: Implementation Improvement: Internal Security updates - Sage CRM Hints, Tips and Tricks - Sage CRM - Community Hub 

The SID has to be a valid Session ID for a System Administrator.  It appears that in Sage CRM 2024 R2 this is broken.  Please log this.  I have already logged an internal bug it would be helpful to have your issue logged too.

Will do, but to confirm then that the SysAdmin option will now only work if you're able to log in first in order to get the SID? 

Hi Alison 

Yes - SysAdmin is fantastic.  Please log an issue.

Yes.  I needs a SID so a System Administrator must have logged on.

Still great feature - but slightly less useful as it was a brilliant way to see who was logged in if all the licences are in use so you know who to ask to come out of the system. (Would be great if 'Admin' (or user_userid 1) never took up a licence and could always log in regardless) 

Anyway I have it logged 

CASE-04483798

Also great if this feature was available through the User Interface in admin area... (not need to go to the server...) 

That's actually on the roadmap.