u/EmicationLikely

We manage a few dozen Synology units for clients, and I guess I've never tried to do this before. I've always put DSM updates on my daytime schedule if the unit is used purely as a backup target, and on my nighttime schedule if it is used as a file share. This is tricky because there is always someone working, so the best time for an after hours update is 3am. If folks are still working then, I don't feel bad for interrupting them. I'm not staying up until 3 to do that, though.

I also don't like the "automate all updates" choice because, well, I want some time to pass after an update is made available to find out if it breaks anything before loading it for my clients.

I'm making a diligent effort to reduce the amount of things on my nighttime schedule so I can, you know, lead more of a normal life. Looking into this a bit, I'm surprised that Synology doesn't build in an option to schedule a one-off DSM update for a future time. Your choice is either to turn on auto-updating for everything, or do everything manually.

To schedule a DSM update, you must manually download the update from the Synology download center, upload it to one of the shared folders on your NAS, then do a scheduled task to run a script to install the update, something like this:

/usr/syno/bin/synoupgrade --patch /volume1/path/to/your/update_file.pat

This opens up some more possibilities for human error, but apparently is the only way. I'm testing this on my own NAS, so ask me tomorrow if it worked - haha.

Also, when you just click the button to download but not install the DSM update (which would eliminate the human error possibility of a manual download), it is stored in a hidden temporary directory that I expect is NOT available with a scripted installation.

Looking into this whole issue, I found questions in the community forums as far back as 2014 looking for this capability - I'm surprised Synology hasn't made this easy by now. Is there anything I'm missing?

I have a setup where wired devices are getting DHCP from the domain controller, and wifi devices are getting DHCP (in two different VLANS) from the Sonicwall. Not sure if this is best practice, but it all works fine.

I'm getting repeated alert 1068s from the Sonicwall for "Multiple DHCP Servers are detected on network". Well, yes - there are 2, so that seems right. I cannot find a way to configure the Sonicwall to expect 2 as the normal condition and then alert if it ever detects >2. I think that only leaves the choice to turn off this alert, lest I continue to get spammed with these alerts. The IP address in the alert is the domain controller, so I can only presume (since this alert is not elaborated-upon in any documentation I have found) that the alert is triggered if it finds DHCP traffic going anywhere by the DHCP configuration on the Sonicwall itself. This would lead to the conclusion that this alert doesn't work at all if the Sonicwall isn't doing DHCP at all, but who knows.

I have enabled DHCP Guarding on the switches (Unifi) and specified the 2 known DHCP servers, but that hasn't changed the problem, which seems to support this conclusion.

Am I doing anything wrong here? Is there a configuration I'm missing that would let that alert work as desired?

Since I upgraded all of my clients' units to 7.3.2-7010, I'm seeing this UX problem. Both in the NSM screens and in the NetExtender 2FA screen. Particularly the NetExtender screen is scaring clients - understandably. Posting here to see if it's just me.