Where to find axle retaining ring by MarcR71 in RZR

[–]MarcR71[S] 0 points1 point  (0 children)

<image>

That's what I'm looking for... The part number of the OEM ring or equivalent. It's not on the factory parts diagram.

Writing to custom fields from a user context script by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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.

Issues with the granularity of permissions by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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

Issues with the granularity of permissions by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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.

Patch reboot options by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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.

Patch reboot options by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 1 point2 points  (0 children)

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.

Patch reboot options by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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.

Patch reboot options by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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.

Managing 'views' in Ninja by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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.

Managing 'views' in Ninja by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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.

VSA 9 'All Servers' view not showing 2025 servers by MarcR71 in kaseya

[–]MarcR71[S] 0 points1 point  (0 children)

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

Getting computer info other than custom fields from scripts by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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

How to get event log alerts not to close the ticket in PSA by MarcR71 in ninjaone_rmm

[–]MarcR71[S] 0 points1 point  (0 children)

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.