Sheridan

If it follows the same issue in April they'll just fix it in a later CU - so Sept at the earliest I'm guessing

I think the KIR package is just the registry changes required anyway? Not sure but I've tested some more and the registry fix is working on a lot of them - so it may have been my initial test set were still having issues from the initial failed sccm deployment

Correction - the registry fix isn't working for us - on an identical test set of 10 it worked on 2 and the other 8 still show the 0X80240069 error I guess we'll be skipping the Aug 2025 updates for a while to see if MS sort this out

Same error April - although we didn't see it then. The registry fix has worked on the test PC I tried. Now to roll out the reg fix across 100s of desktop and laptops....

I started to test the Aug 2025 CU for Windows 11 24H2 on our test collection - all have 24H2 and the last patch was July 2025 SCCM has failed on every one in the test collection with the error: Failed to download update: 0x80240069 This error was around during the April updates, but our systems have have April, May, June and July updates applied since then without error - anyone else tried deploying Aug 2025 yet?

Cheers for the info - I think I'll build a new install and see if I can export and import. Mainly because the server its currently on is a bit of a mess of old stuff and this is the only thing I want to keep!

I've shelved trying to fix this for now - support basically seem to think its the firewall and that I'm too 'stubborn' or 'inexperienced' to accept this 😄 I've proved its not the firewall so my plan is to ditch Solus completely and just use sccm to deploy sims in future

Did you just copy over the new Snipe files and run the update.php? I'm struggling to even get 5.4 to got to 6.3 using this method! I wonder if theres just a way to export from the old, build a new empty system and import the data

Did you do your incremental updates manually then?

Yeah I think I might try 5-6 first and then 6-7 if that works!

I've managed to get around the proxy with a bit of tinkering, but its let me down an absolute rabbit warren! I can get the update.php to start and it generates a huge number of errors in Stage 6 (composer) and then dies at Stage 7 (putting into maintenance mode): Something went wrong with downing your site. This can't be good. Please investig ate the error. Aborting! I'm starting to think that 5 to 8 is just too much of a step - we might be better off trying to start from scratch

I've tried the manual process but it didn't seem to work. Keeping with git seems to be the best option but it fails with downloading that json file (which I can access via a browser on the same server) I wonder if git/php needs to be told to use our proxy to do this

Cheers, I think it was installed initially via git but when I try to run the update process I get an error straight away: Warning: file_get_contents(https://raw.githubusercontent.com/grokability/snipe-i t/master/.upgrade_requirements.json): Failed to open stream: No such file or dir ectory in C:\inetpub\wwwroot\snipeit\upgrade.php on line 12 I can't see any documentation that suggests we can got from v5 to v8 like this - its quite a jump!

Anyone out there using Snipe-It for asset management? I've inherited a working system but it seems quite old (version 5) and I'm not sure if its updateable or I'd have to go for a new install and import the old data?

I just simplified it even more - ran the commandreporter which always outputs .csv and then a second script renames it back to .txt The content of the file it creates is exactly the same so renaming it after the report finishes was the easiest if slightly clumsy way of doing it!

Its the 'you must manipulate the script further' bit I can't seem to find docs for - we're just running it as a batch file

Yes we are outputting to a network path. It appears to work fine in that sense - it appears in the right place in the right format and name, just with an additional .csv tagged on the end! I've tried running the report without the OUTPUT parameter at all to see if it just uses the designer ones but as you say it seems to ignore those

We've started to run an automated report using the CommandReporter (on a scheduled task) to run a simple report overnight This works but the report output is showing the filename as name.txt.csv - the report in the designer is a .txt output and the path in the batch file has the output file as /OUTPUT:\\PATH\file.txt. Running the report via the designer works fine So its working but adding the .csv extension on after the .txt even though this isn't specified anywhere - are there parameters for the commandreporter to make sure it uses the name & path as in the designer or use the OUTPUT path correctly?

I'm not sure if the firewall is an issue here as it uses 52965 and 52966 for the Solus service to perform the update and 8739 to connect to the UI We know 8739 is open when a user is logged in otherwise it isn't. The other two are open all the time and that's why the update seems to begin (and actually complete) but something is hanging or not closing hence the timeout error We're looking at rolling out the next update by a simple copy script instead via sccm

We've had the ports defined by a gpo for a long time. I tried a fresh download as well but no luck

Our Solus clients were 3.12.86.1 already (I believe so anyway - I didn't check to be fair!) Even deleting a solus client completely (manually) and then redeploying I see the same error - so I'm a bit stuck as ess still think its the firewall even when I've tested this a lot and found the firewall ports all correctly open

Ours was working fine until the summer update but our only fix is to remove solus and reinstall it. Haven’t started yet as it’s over 100 computers that showed the error

Anyone else run the Summer 2025? Curious to know if mine is an isolated disaster 🙂

Thanks, looks like my summer now has an extra job to rip this mess out and start again!

We now can't install individual copies using Solus as we see the signature error: 'Sims.Solus3.Agent.PackageDeployer.PackageException: Failed to validate signature' So mass deployments aren't working, neither are individual ones. Is there a good way to completely reinstall Solus?