I was directed by support to force updates, en mass, through the RMM console which did work.

I have the Allow automatic updates option enabled, if that's what you're referring to. But it's not working for the affected clients.

So far that does seem to work. I've got to spend time installing it on each client, as the Powershell script provided seems to fail 90% of the time with an error about the package manager being in use and to please close the program and try again. However, if I just run the executable in GUI mode, it works fine. Kind of annoying when I'm dealing with dozens of machines and I would like to script it. And, setting it to 'Public' doesn't seem to let the clients update, either, probably because they're not being authorized due to the issue in the previous release.

Thanks, David. I did contact them, they asked for logs, which I sent last night, but haven't heard back yet. Maybe the new patch will help, because I see now that it's affecting some other clients, as well.

Okay, thanks.

I have tried uninstalling and re-installing, but that made no difference. After hours, I'll try rebooting the machine to see if that changes anything. Otherwise, I'll try going back to a previous installer. Thanks.

No help. I tried changing the user account in the management console, tried changing the password, and tried changing it all back to normal, between each step I restarted the services and attempted to open the agent - all resulting in the same error. I can't get into the agent to change the user account from there because I get this error screen immediately upon attempting to open the agent.

Thanks. I figured they were working on it already and didn't want to add to their burden of communication if others had already been informed of what's going on, so I figured if I posted on the forum, someone who already had a case open for this issue would be able to fill in the rest of us without increasing the case load for an already known issue.

Not sure if this is your issue, but Windows security settings due to updates sometimes cause this. Try the following:

1 - run regedit
2 - locate HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft/Windows/CurrentVersion/Policies/System
3 - create a new DWORD entry with the name EnableLinkedConnections and value 1.
4 - restart Windows Explorer or restart your computer
5 - now you can see and use network drives with these installers or applications.

Oh, okay. The option, when presented, looked like it was going to automatically report every job result to all the individual clients. I'll try turning it on and see if I can make the necessary adjustment. Thanks for the clarification.

Okay, I'll wait for the October release. I don't want users inundated with e-mails. Every time a minor issue occurs and one out of six jobs fails for the day, I don't need users who don't understand how anything works contacting me concerned that their backups are failing.

Great! Thanks for your quick response to this.

eh, more backups are better, anyway.

Great, thanks. For now, I'll just set up an RSync to copy my local files to the TrueNAS box and then back them up via the share. Kind of round-about, but it's better than wiping my system and rebuilding to change to EXT4.

I chose it because of its general superiority over other file systems and since I've had no problem choosing file selections from my NFS and SMB mounts located on my TrueNAS server which also uses ZFS, I thought it wouldn't be a problem. Is this something that will be supported in the future? It's becoming more prevalent now that it's in the kernel.