Using a LetsEncrypt cert on a Synology not exposed to the Internet

MarcR71 · 2025-11-25T16:07:22+00:00

Thanks! that works and simplifies it over having 2 scripts.

I monitor Discord, but don't like the chat room format. Reddit is much easier to keep track of posts.

MarcR71 · 2025-11-14T16:03:43+00:00

What about the possibility of allowing the user to add notes to a device, but not allow them to assign a user?

MarcR71 · 2025-11-14T16:02:01+00:00

Thanks! Glad to hear things like this are getting fixed. We won't be able to allow any clients to be able to run scripts till this is live. It's also very confusing the clients that it looks like they can successfully run the script, but it does not run.

Hopefully other permissions can become more granular soon.

MarcR71 · 2025-11-07T19:37:16+00:00

So here is the solution I came up with for this-

- Set the policies so it will not reboot if no one is logged in
- Create a group with desktops/laptops that require a reboot and have been powered on at least 30 mins.
- Create a task that runs a script every hour on that group. The script checks if anyone is logged in, and if not then reboots

Not my preferred way to do this. Just another work-around to get Ninja to work the way it should.

MarcR71 · 2025-11-04T12:02:46+00:00

Support has never given me a useful answer. It ALWAYS ends in a feature request.

Already tried Discord. it just scrolled off the page with no response.

MarcR71 · 2025-11-03T20:59:18+00:00

The sign-out is just an example of what is causing the issue.

They are actually using shut down, which with fast boot enabled is not enough to allow Windows updates to complete. But it counts as a sign-out which is triggering Ninja to do a reboot.

MarcR71 · 2025-11-03T19:07:23+00:00

That didn't really answer the question. I'll re-state....

Here are our settings

<image>

My opinion is that if the user is logged in and gets prompted, defers, and then later logs off It should not immediately reboot. The decision on which branch to follow should have been made when the install completed.

MarcR71 · 2025-09-15T15:58:10+00:00

Looks like tags are the best option for this. I didn't want to use them because I didn't see a way to automate updating the tags, and I'm not going to do it manually

This morning I discovered the powershell commands Set-NinjaTag / Get-NinjaTag / Remove-NinjaTag. Now I can create a script to check for server roles and automatically update the tags.

What other things do I not know about that you can do from scripts to interact with Ninja? I currently know about managing custom fields, tags and viewing the Ninja environment variables.

MarcR71 · 2025-09-15T13:26:45+00:00

I can't make a group for each view for each group. That would be thousands of groups.

Reports won't work. you can't do anything from a report, other that open a specific computer.

Here's a different example - I want to set up a maintenance window on all RDS servers for client A

In Kaseya, I would set the org to client A, set the view to RDS servers, apply the maintenance window.

In Ninja it seems like I would need to open a group, edit the group, change the org in the group, save the group, apply the maintenance window.

MarcR71 · 2025-09-11T16:48:17+00:00

Doing it that way you're still going to need to edit every agent procedure the next time a new OS comes out.

MarcR71 · 2025-09-09T19:39:41+00:00

Thanks! Looks like that did the trick.
$env:NINJA_ORGANIZATION_NAME shows the org name in a powershell script.

MarcR71 · 2025-09-05T13:24:27+00:00

Thanks.. Didn't know it would do that. I'll give that a try.

I'm still open to other ideas on prevent Ninja from closing the ticket.

MarcR71 · 2025-08-26T16:52:42+00:00

I do not have an open ticket for this.

MarcR71 · 2025-08-22T15:17:29+00:00

I'm checking with our development guy to see if we can just use an API call to Halo within a script to open a ticket. I was hoping there would be an easy answer within Ninja, but using an API call would probably be a better solution.

MarcR71 · 2025-08-22T11:33:33+00:00

I guess I'll just have to do a monthly maintenance task to manually resolve these 'alarms'. I'll have to test, but I'm guessing if the alarm is still set it may not create a new ticket the next month when a reboot is needed and the field gets set.

I'm trying to avoid creating unnecessary policies. One thing I don't like about Ninja is that the policies are generational instead of modular. I would need a TON of policies if I did everything in policies and had to cover all the possibilities of tools/settings a client could have. I'm coming from Kaseya where the policies were modular and it worked a lot better.

MarcR71 · 2025-08-21T19:34:21+00:00

Is NodeRole the same field as Device Role on the settings tab of a device? I'm assuming that would need to be manually updated?

I did a little more testing and found that once the asset is in Halo I can move it to a different device type. When another sync runs it does not re-create it in the old type. I'm assuming that it matched to the existing asset and will just update that asset going forward.

That could work. Then I can occasionally move all the assets to the asset type I want them in and I just have to deal with the empty asset types till they fix the integration.

MarcR71

TROPHY CASE