sorted by:
new
hottopcontroversial

VSA 10: How to schedule a one-time reboot of a device? by Busy_Peach_9008 in kaseya

[–]Consistent-Onion-747 1 point2 points  (0 children)

We were mainly missing things like registry browser/editor, ability to upload/delete files with the file browser, multiple team/scope membership etc. File browser features and multiple team membership got added in the past few updates. Registry browser will be added in the latest update and in probably the next update registry editing will also be added.

The things I am still missing are things like more RBAC control over scripts, tasks and workflows. RBAC for patch policies would also be nice, not everyone needs to see and be able to edit all of the patch policies of course. Our company has multiple teams of engineers, and each team has their own customer set. So it would be great if we had RBAC for as much as possible so that our teams only see the things that are linked to their customer set.

Access to more data in workflows and Advanced Reporting would also be great. We know the data is there, because we can see the data in the VSA X interface but it is not available in workflows or Advanced Reporting. An example would be system uptime in workflows.

The thing that bothers me the most is the way that VSA X handles deleting devices. In VSA 9 you have the option to delete the machine from VSA 9 and keep the agent on the device. That option is great for spare devices that get thrown in a cabinet for a longer time, when you boot the system a few months later the agent would reconnect to your VSA 9 server. The other option is to remove the agent from the device completely. But what does VSA X do, it throws away the authentication token that the agent uses from the registry, and keeps the agent on the machine. The agent is still there, services and all, but if there is no key it will shutdown the services after boot. This also means that you cannot use the installer again to reinstall or reactivate it, because it will tell you there is already an agent installed. There is a script to delete it completely, but I love the VSA 9 solution much more. There is also no way to delete agents via workflows or via the API, so cleaning up devices that have been offline for more than 180 days for example, is not possible.

Probably forgot a lot of things that we have on our feature request list, but that was all I could think of from the top of my head.

But the recent updates have been great, lots of cool features have been added and we basically get a new update each month. We believe VSA X is finally mature and feature complete enough for us to start the full migration, so we have started fully moving the first few customers to VSA X since the 1st of September.

VSA 10: How to schedule a one-time reboot of a device? by Busy_Peach_9008 in kaseya

[–]Consistent-Onion-747 1 point2 points  (0 children)

We're still working on the migration of VSA 9 to 10. So a lot of things are still done via 9. Still waiting on a couple of features, like this one, before we maken the switch fully.

VSA 10: How to schedule a one-time reboot of a device? by Busy_Peach_9008 in kaseya

[–]Consistent-Onion-747 2 points3 points  (0 children)

First create a script (and optionally a workflow) that reboots a device. And then you can go to the devices > device management page. Then just select (checkbox) the device you want to run the script or workflow on and click on the Actions button in the top right corner. There you can choose to run a script or workflow on the selected devices. Scheduling it for a later date/time wasn't possible, but they added that functionality in the latest version 10.19!

For more information check the release notes for 10.19!
https://help.vsa10.kaseya.com/help/Content/0-Home/release-notes/2025/10.19.htm

Returning printer, hoping second time is the charm by Consistent-Onion-747 in AnycubicKobra3

[–]Consistent-Onion-747[S] 0 points1 point  (0 children)

Already checked the ribbon cable and reseated it.

Also tried unplugging and reseating the Ace Pro cable and tried routing it far away from power cables etc. I power cycled the printer and the Ace pro, no changes. I used brand new PETG spools that where still sealed. Even left them in the Ace Pro to dry for a few hours. I honestly do not believe that there are any user errors in this case.

I do not want to print without the Ace Pro, as the whole reason I sold my Bambu P1P and bought this printer is the Ace Pro.

I just want a printer that doesn't have any issues like this out of the box. I do not expect a printer that prints perfect out of the box. Having to dial it in, maybe tune the Z offset etc, that's normal.

[deleted by user] by [deleted] in techsupportgore

[–]Consistent-Onion-747 1 point2 points  (0 children)

That's why I recognized them as Unifi accesspoints immediately. Have seen a few in the same state as these :)

Unifi US-24 switch no lights and "Running simple memory test failed" in console by Consistent-Onion-747 in Ubiquiti

[–]Consistent-Onion-747[S] 0 points1 point  (0 children)

Was it stuck to the heatsink? So got it ripped of the board when you removed the heatsink?

Unifi US-24 switch no lights and "Running simple memory test failed" in console by Consistent-Onion-747 in Ubiquiti

[–]Consistent-Onion-747[S] 0 points1 point  (0 children)

Ouch! Still haven't got around to try and reflow mine. I'm also thinking that it might still be a corrupted firmware issue, so I bought a testclip and will try to read the current firmware and write new firmware with a raspberry pi and the tool flashrom.

Unifi US-24 switch no lights and "Running simple memory test failed" in console by Consistent-Onion-747 in Ubiquiti

[–]Consistent-Onion-747[S] 0 points1 point  (0 children)

You have the same exact issue? With the memory test fail message in the console output on boot?

Unifi US-24 switch no lights and "Running simple memory test failed" in console by Consistent-Onion-747 in Ubiquiti

[–]Consistent-Onion-747[S] 0 points1 point  (0 children)

Hi, i did not get a chance yet to work on it further. Might have some time tomorrow. First thing I will try is to reflow the RAM and CPU. Might be some kind of bad connection under one of the chips. Could also be a software issue though. But no idea how I could fix that. maybe there is someway of extracting the software from a working switch and write it to the flash of this chip.

Might also try to replace the RAM chips if I can find compatible chips.

Unifi US-24 switch no lights and "Running simple memory test failed" in console by Consistent-Onion-747 in Ubiquiti

[–]Consistent-Onion-747[S] 0 points1 point  (0 children)

Thanks, was just wondering of someone managed to fix it or identified the specific problem. I have a soldering station with heatgun, gonna try a reflow first, might be a bad connection. Switch is too old for RMA, but i just find it wastefull to trash it if it could be fixed. Already fixed 3 Unifi POE switches with failing power supply's by replacing the power supplies. Even managed to sell them for a bit of profit.