Removed the nut installation, config files and did a complete Raspbian upgrade ... Now after reinstalling nut with the bare minimum configuration, it is finally talking to the ups.
Even though I have been technically involved with computer tech going back to the late '70s, this install was certainly not for the faint of heart ... I can understand why people walk away in frustration from this stuff
@dustinb3403 What do you mean disabling autodiscover for a user? Are you talking about a registry key?
No, within O365 you can either selectively disable authentication protocols because you're a glutton for punishment or you can do so with conditional access policies or Security Defaults.
Well you can disable Autodiscover as a whole organization through the modern authentication setting, however in order to have conditional access you have to have higher licensing than normal which is why I am confused at the disabling comment.
Just a P2 license to setup a conditional access license for the administrator account(s). The user accounts don't require this level of licensing.
@DustinB3403 I'd love to hear your thoughts so you downvoted my post. I have no problem debating you and anytime I downvote you it is because I don't agree with you. You also know that I upvote you as well even if we aren't best buds 💔
Any vote of yours that I've downvoted is because what you said is wrong or at a minimum disagree. You've been downvoting people out of spite, unless you have a really good argument to what I've posted then I recant the above statement and welcome your debate.
Also everyone that's downvoted you except maybe @stacksofplates has downvoted me before when they disagreed with stuff I've said. @JaredBusch@Obsolesce , @travisdh1 but they've had a reason or an argument to why they've disagreed with me. That's how it's supposed to work.
Build out a site to site to a their datacenter and slowly build / upgrade things.
A lift and shift can be a good idea. But it isn't very likely. Taking applications that aren't well maintained on premises and just shifting them off premises is just "moving" a problem, it isn't addressing it in any way.
That doesn't mean that you might not benefit from keeping these applications in this way. It's not to say that colocation is bad. But you can't start with the assumption that the "less common" solution will automatically be the right one with no evaluation at all.
For anyone curious, I was trying to migrate a Windows VM from QNAP to Proxmox, and this came in handy. Notes...
The VM type can be set to Q35/UEFI.
There may be multiple disk images on the QNAP box for the same VM: you need all of them in the same directory for the QCOW tooling to work correctly. Turn off the VM in Virtualization Manager, and copy them over to Proxmox via SSH; you can also download them via File Manager first.
importdisk on the latest file; it'll rebuild a RAW file where Proxmox keeps the data.
Mount the file in Proxmox as an IDE drive, and don't forget to set the boot order ahead of CD-ROM & Network.
https://github.com/virtio-win/virtio-win-pkg-scripts has the latest guest drivers for QEMU/KVM. https://superuser.com/questions/1057959/windows-10-in-kvm-change-boot-disk-to-virtio has some strategies for migrating from IDE to VirtIO; again, don't forget to check the boot order when detaching/re-attaching the disk image. Adding a tiny VirtIO drive while the system was up, shutting down, detaching the two drives & attaching the main as VirtIO; was the working solution for me.
Side note: unless you remember to look up your virtual MAC address in the QNAP VM, you'll need to reconfigure your network adapter after migration.