AGA

We encountered this issue and this thread was faster than ESS support in helping us to resolve so thankyou. Have noticed that "Patch 31425 - Fix for Dex sync schedule" has been released. But no word from support yet to confirm whether this is the proper fix or not, unless i'm missing some obscure blog post they've issued elsewhere.

3 of us moving away from SIMS in this thread then. We'll also be on iSAMS by Sep 2027. Have switched off all the next gen redirects they listed. None of our staff are even setup to use it since there was such a poor reaction to it when demoed and trialled. Just ignoring it until we've departed, or they don't let us anymore.

With their guidance we found it was more of a migration between the two SQL instances on the same server. Depending on what you use, there's the need to migrate SOLUS and Discover as well, and there's a fair few caveats. So we opted to have ESS support do it for £425 I watched them the whole time, and assisted with a couple pieces of info. The guy was very knowledgeable, but it still took a long time for him to work through the intricacies, so I was glad to have paid to remove the headache. In case it helps inform your decision.

Thanks. We aren't using the PowerShell method, so our case is slightly different from most in that thread. I had a look through the scripts used and couldn't identify a specific part that would align with our needs without concern that it'd break something else or involve starting from scratch. Noted though that this replier has had the same 'fix' that we stumbled across given to them by MS Support, but it's far from ideal.

We've been using the Microsoft 365 School Data Sync for a number of years to sync our classes from SIMS to Teams via the csv uploads. This works well, but we've noticed that when a team is created for each class, the connected SharePoint site for each team isn't created automatically. Because of this, when the teacher activates the class they are unable to start setting up the class notebook. It shows the message "We're still setting up your class. Please check back soon." This is presumably because it needs to be saved into the connected SharePoint site. Another symptom is that the class's home page will show the tenant home page instead of the class's. The method we have found that triggers the SharePoint site's creation, is to click on the 'files' tab of the team's general channel. An error message will be displayed at first (because the SharePoint site doesn't exist yet), but after clicking away to another tab and back again, the site will have been created. This is confirmed when looking under 'active sites' in the SharePoint admin centre. It will appear. Once this has been done it allows the class notebook to be setup as expected and the site's own homepage is displayed. My question is if anyone else has encountered this? And if so, does anyone know how it might be possible to trigger this for all our classes in bulk? Possibly using PowerShell? We have raised it with Microsoft, but we all know how fruitless that is. Thanks

Select the top dropdown shown there 'Exclusion Type'

In Sophos central its under Endpoint Protection > Global Exclusions > Add Exclusion > Exclusion Type > Scroll down the list

Thanks both, that looks to have worked

We still haven't properly resolved this, and also have Sophos Central AV, so I did some tests. Deployment works if we disable Real Time Scanning for Files in the Sophos Agent on the client. We have Global Exclusions in place for all the known SIMS file paths and .EXEs. We also can't see any Sophos Central logs to suggest it's taking any action? but it clearly is.

Thanks for the reply. I think we've tried everything except a complete reinstall of the SOLUS deployment service on the server. Is that what you're suggesting? Have tried both restarting the service and rebooting the SIMS server. Have tried deleted both the update package within 'D:\SIMSRoot\Repository' and the extracted copy inside 'D:\SIMSRoot\Repository\DoNotDeleteThisFolder', then redownloaded through SOLUS. We're seeing the issue on both fresh installs, and on our existing PCs that were on the Spring update. Uninstalling the solus agent and then deleting everything within these locations on the PCs and redeploying also hasn't helped: C:\ProgramData\Capita C:\ProgramData\Solus 3 C:\Program Files (x86)\SIMS C:\Program Files\Solus3 We've found we can manually copy the 'C:\Program Files (x86)\SIMS\SIMS .net' folder over from a working PC and SIMS can be launched etc. But solus is insistent on still trying to reinstall, so the agent will keep popping up trying again and again.

Think we're seeing the same issue trying to deploy the SIMS summer update. All the PCs that we pushed the update to have returned with 'Deployment timed out' in the SOLUS upgrade deployment logs. The PCs now report as being on the latest SIMS version (7.224.27), but when testing a handful we found that it's only functional on some of them. On others, when trying to launch SIMS it can't find the connect.ini In the SOLUS systemlog file on each PC affected, the line that stands out is: Info|Sent ProgressUpdateType: DeploymentJobId:70dffa0d-280f-4df3-9d6a-e72805280786 PackageId:e8fd29b0-20b5-4625-89fc-8abdabdfd746 TaskId:00000000-0000-0000-0000-000000000000 ActionType:General ProgressType:Finish Message:'One or more errors occurred.' MoreInfo:'System.AggregateException: One or more errors occurred. ---> Sims.Solus3.Agent.PackageDeployer.PackageException: Package failed. Rollback was executed. ---> Sims.Solus3.Agent.PackageDeployer.TaskException: Execution of task 2b05c745-cf87-46db-9615-a9bf15631d3e failed. ---> System.InvalidOperationException: Process must exit before requested information can be determined. And the other error message we're seeing returned in the solus agent logs is: 'Decompiling of the package SIMS Summer 2025 Full Release (7.224.27) (SIMS Workstation) failed' Solus version on all our PCs is 3.12.86.1 Had no issues installing the spring update. Has anyone had anything useful back from Support they can share?

I've just tested on iPadOS 17.4 as well and confirmed issue does appear to have been fixed. Papercut is also reporting the issue as resolved: https://www.papercut.com/support/known-issues/?id=ios%2017#mobility

For anyone else that comes across this thread looking for related solutions. There are two issues we ran into using the %localappdata%\Microsoft\WindowsApps\ms-teams.exe path. 1) The shortcut won't work for any users that haven't launched the new teams yet, because they won't have the exe in their local appdata. This is particularly an issue because new teams won't launch automatically until it has been launched manually by the user, once per PC. It's even more of an issue if you have users that log into multiple PCs / don't have 1:1 devices, or if you clear local appdata regularly, as this issue would then reoccur for users all the time. Instead we are using a shortcut to shell:appsfolder\MSTeams_8wekyb3d8bbwe!MSTeams, which we created by navigating to the shell:appsfolder in file explorer, right clicking on the new teams icon to create a new shortcut, and copying it to a shared location. If you have the new teams as a provisioned app, then this shortcut works for all users regardless of if they have opened Teams before or not. 2) A shortcut using either of these paths will fail to deploy when using the shortcut deployment method in the 'computer' group policy preferences, because it can't find the destination file/path. So instead we are using the 'files' group policy preference to just copy the new shortcut to all PCs public desktop.

Unfortunately we're still seeing this issue on iPadOS 17.3, with any file type (jpg, png, heif) when printed from the Photos app. Running latest Papercut Mobility update v.1.0.3668, and latest Canon firmware and UFR II drivers. Printing from MS Word app etc on the iPads works no problem. That's our only real workaround at the moment as well.