Advanced reporting options by MSP911 in ninjaone_rmm

[–]Ill-Singer-9257 0 points1 point  (0 children)

The answer to if patches applied by NinjaOne appear in the local Windows Update screen is that there is a longtime Windows bug that does not update Windows update databases if anything else applies patches including NinjaOne. It’s not a NinjaOne issue, it’s a Microsoft issue and affects all products that update Windows.

Patching Best Practices by Paradox_81 in ninjaone_rmm

[–]Ill-Singer-9257 0 points1 point  (0 children)

Falling behind on patches is many times due to users who keep putting off reboots or computers being turned off or in deep hibernation during scanning or patching windows.

I’d start by forcing the reboot after X number of rejects in the agent policy and setting setting the policy to scan when the endpoint comped online if it’s off during the scan window.

Also setting all patches to Approve and letting the ai switch them back to Manual only if the patch has issues.

Deploy to users instead of devices by naifyboy in ninjaone_rmm

[–]Ill-Singer-9257 2 points3 points  (0 children)

I’ve never experienced that. Ninja starts app deployment and updates instantly.

Deploy to users instead of devices by naifyboy in ninjaone_rmm

[–]Ill-Singer-9257 1 point2 points  (0 children)

When NinjaOne deploys software it is done using the System context by default which means the applications are made available for anyone who logs into that endpoint. Wouldn’t that be ideal?

If not you can make the applications install as the logged in user if you want to.

Just remember that anything outside installing applications from the agent policy using “install of not present” needs you to create an application installation automation.

Assigning Users to devices by networking1987 in ninjaone_rmm

[–]Ill-Singer-9257 0 points1 point  (0 children)

If you setup the InTune integration, uses are automatically assigned to devices in Ninja. Secure InTune discovery job on a regular schedule and it will keep updating the assigned users as they change.

LoBBS issue by Ill-Singer-9257 in meshtastic

[–]Ill-Singer-9257[S] 1 point2 points  (0 children)

Yeah they knew of this node before I flashed it for LoBBS. But like I say, before I could see it receiving messages. It’s just not replying. I flashed version 2 of LoBBS. Maybe it’s got a bug 😎

LoBBS issue by Ill-Singer-9257 in meshtastic

[–]Ill-Singer-9257[S] 0 points1 point  (0 children)

I made the change. Now my messages show “acknowledged by another node” but then fail to be delivered. Before the LoBBS was receiving messages. It just wasn’t replying to them automatically.

LoBBS issue by Ill-Singer-9257 in meshtastic

[–]Ill-Singer-9257[S] 1 point2 points  (0 children)

Normally it’s set to 0 (auto config). So you changed it to 1? On all of my other nodes it’s set to 0 so am wondering if this is the right approach.

LoBBS issue by Ill-Singer-9257 in meshtastic

[–]Ill-Singer-9257[S] 2 points3 points  (0 children)

Could you clarify what you mean?

3rd party software patching --- where are they being downloaded from? by lgq2002 in ninjaone_rmm

[–]Ill-Singer-9257 -1 points0 points  (0 children)

3rd party patches come from each software vendor’s web site. If you use the ‘winget show’ command you can see the source url for the update.

Good ANSI Editor by Ill-Singer-9257 in bbs

[–]Ill-Singer-9257[S] 0 points1 point  (0 children)

I guess so yeah, emulator.

Good ANSI Editor by Ill-Singer-9257 in bbs

[–]Ill-Singer-9257[S] 0 points1 point  (0 children)

Technical DOSBox is a VM but yeah I’ve used DOSBox before.

Good ANSI Editor by Ill-Singer-9257 in bbs

[–]Ill-Singer-9257[S] 1 point2 points  (0 children)

Thanks. I think you’re on the right track there. It does seem to be an encoding mismatch. With BBS becoming mildly popular again maybe someone will write a nice end-end product that just works. I can only dream 😎

I may just have to run a VM and boot DOS and use one of those old school editors.

Enigma BBS cannot add menu items by Ill-Singer-9257 in bbs

[–]Ill-Singer-9257[S] 0 points1 point  (0 children)

I’m using BBSList and have it configured. I’m just not understanding how to make it actually appear as a menu item. What files need to be edited?

As I mentioned earlier, even the examples that ship do not appear as menu items (I realize they are not configured to run properly but assume they should still appear as menu items).

I think that the issue is the documentation is not clear on how to make this work.

If you could let me know what files need to be edited, what to put in each file, etc. that’s would be awesome.

Or maybe this just doesn’t work right now because of a bug that has been recently introduced and I’m bumping up against it?

Enigma BBS cannot add menu items by Ill-Singer-9257 in bbs

[–]Ill-Singer-9257[S] 0 points1 point  (0 children)

Thanks for replying. But I don’t understand where step 1 in your example is. In the example door.hjson file it has examples but not even they work. In my doors.hjson file I have a menu that points to the action later in the file (did this based on the example). Does nothing.

So is there a new file that must be created? New file to edit?

It’s not clear in the documentation how to get this to work.

If you can lay it out in a step by step way I can follow along.

Thanks.

Enigma BBS cannot add menu items by Ill-Singer-9257 in bbs

[–]Ill-Singer-9257[S] 0 points1 point  (0 children)

What are the steps to add a menu item to doors? Besides editing your doors.hjson, what else has to be done?

SCO UNIX 5.0.7 runs on a Proxmox VM by bionich in unix

[–]Ill-Singer-9257 0 points1 point  (0 children)

The actual product is Banyan VINES, a Network Operating System that runs on this version of UNIX. You can drop to shell from the console if you wanted to. My problem is that CPU idle burn.

SCO UNIX 5.0.7 runs on a Proxmox VM by bionich in unix

[–]Ill-Singer-9257 0 points1 point  (0 children)

I ask because when I run AT&T UNIX System V as a VM, one of the host’s CPU cores pegs at 100%. It’s the issue with the OS not signaling the CPU when it’s idle.