mhaddon

me too so I've submitted it to Smoothwall Block Page for category check. I'm guessing there are some keywords in that json file that are triggering the category alerts

hmmm. Issue went away for a few days and then came back with no changes to the RDS environment. Starting to wonder if it's the SQL backend (which is on a separate SQL box). Also wondering whether it could be a pc issue e.g. AV kicking in but it's strange that it's only when you hit those 2 buttons. I think those buttons open up a query form for students or Staff though without actually doing anything? Dunno if that's just calling a saved form or something like that? I don't really know anything about SIMS

Seems to work fine if you run it from a published desktop (.rdp) but if you run it as a published app (.rdp) then these 2 functions (Staff and Student) are slow, the screen sometimes flickers and sometimes you get a Nor Responding message. I think my colleague also tested the published app through webclient and that had the same issues.

thanks for the suggestion. i'll have a look

Clutching at straws here but hoping someone might know of a tweak that we're missing. Migrating from RDS2012 to RDS2019 and testing SIMS as a published app. It's generally ok. Few seconds between clicking icons etc. But when you click the staff and/or student icons for the first time it can take several seconds before opening those pages. Sometimes the screen flickers and and sometimes we get a not responding message in the SIMS app. Strangle enough we don't seem to get these issues when logging onto the session host server and launching SIMS locally. We also don't seem to get these issues when logging onto a published desktop and launching SIMS from the desktop. The session hosts are pretty beefy so we don't think it's a server sizing issue. Other published apps, including FMS, all seem to work fine. Only other consideration is that we have installed SIMS onto a D: drive on the session host because the disk can fill and bring down the server when installed on C:. We did create the SIMSLink virtual mapping though so that the app knows where it is. Struggling to fault find this one. Not even sure what process is called when you hit those buttons to see if something could be timing out but it's just strange that this only seems to happen with the published app.