u/EmicationLikely

If I update an existing script check by uploading a new version of the script with Script Manager, that new version gets (at some point) automatically pushed down to endpoints that were using the check with the previous version. ....or so I thought. This seems to mostly work, but there are definitely times when something goes wrong and a particular endpoint doesn't get the update.

• Is there a particular pattern of events that prevents the update?
• Is there any way to identify endpoints that DIDN'T get the update?
• Is there a better way to update scripts than this?

As soon as I find an endpoint that didn't get the update, then I lose faith that it was consistently applied and I end up re-pushing the entire monitoring template to the site...which comes with the potential side benefit of doubling checks even though I checked "replace existing checks". Ugh - is it Friday yet?

Every month when I do this, I wonder why this weird design decision was made. I have one report I want to export. Show me all of the sessions and their details for the last month. So on August 1st, I want to run a report for all of the sessions in July. On September 1st, I'll want to run a report for all of the sessions in August. This seems like something every manager or business owner would want to do.

So I go to Take Control using the link on my NSight dashboard. I select Reports, Session History, then click on the default "Last Week" period. First I try "Last One Month". I notice the automatically selected period is July 1st at 10:30 to August 1st at 11:00. That is obviously not what I want because it would exclude any session started before 10:30am on July 1st. We start work between 8 and 9 depending on the technician, so what I really want is July 1st at 8am through July 31st at say, 19:00 - 22:00 to be safe. I try to make those changes and it won't work. As soon as I select any time before 10:30 on July 1st, the cell changes to 19:00, and I cannot change it to any time before that. Just for fun, I try to change the ending period from August 1st at 11:00 to July 31st at 22:00 - maybe there is a problem with mor e than a one-month period. Nope. When I change to July 31st and try to set the time to 22:00, it changes to 19:30, and cannot be set later than that.

So to get the period I want, I have to change the start date to 6/30 at 19:30 through August 1st at 19:00, doing the export, then deleting any sessions that this sort caught on either 6/30 or 8/1.

Why is this so stupid? NAble, please make your developers USE THE SYSTEM they are designing. Maybe then stuff like this won't make it into the finished product.

This might just be a UX quirk but I've noticed the following:

When you are adding a check to monitoring template, there is no ability to assign an automated task on failure of that check. You can add an automated task, though, and set it's run parameter to "on check failure" then specify the check.

If, however, you are editing an existing check for a machine, you can check the "Assign a task after editing check", which let's you choose an automated task. This bit doesn't explicitly say "on failure", but I have to presume that is the case. You can also edit an automated task and set it's run parameter to "on check failure", just like if you were editing a template.

So, there are apparently two different ways to do this thing if you are editing an existing workstation, but only one way to do it if you are editing/creating a monitoring template.

Is this conclusion correct? Is there any difference in doing it one way or the other? Obviously, it's rare to want to make a change like this to one particular machine (rare, but not never) - it's more common that you want to make a change like this to an entire client, or your entire estate of managed computers.

We're replacing our server, and given the price of RAM & Storage these days, I don't want to buy more than I need (but also don't want to underbuy just to save a few bucks).

As I understand it, all model processing (including fly though rendering - we use Enscape) happens on the local workstation, and the fileserver that stores all of the data only needs to have fast storage and network. However, I don't use the software at all, so would like to gather recommendations from others before we spec and replace our server. We've currently got 40 workstations, and our server currently has a 20GbE connection to our network switch.

Some random thoughts:

• For the new server, I'd like to bump the connection to the network to 40GbE to give as much bandwidth as possible to each workstation.
• SSDs where possible on the server, but we have a large data store so it just isn't practical/affordabe to make it all SSD. I'm thinking of a RAID1 SAS/SATA SSD array for the server OS, a smaller "current projects" RAID10 array with NVMe, and a larger RAID10 HDD array for completed projects.
• I don't see any necessity for a discrete graphics card in the server
• As it is primarily just a file server, I don't see the need for anything but a middle-of-the-road processor, either.

What do you think, anything I'm missing?

I have a non-local client that has an office in an office building and a home office. Up until recently, he had a SOHO-250 in the office and a SOHO-250W in the home office with a VPN tunnel between. The office has Spectrum Business internet and the home has Spectrum home service.

A couple of years ago, we replaced the SOHO250 in his office with a TZ270. This swap went fine, no issues whatsoever. We configured the unit, shipped it to him and talked him through the swap. It's been running fine for 2 years with no problems.

Last month, we replaced the SOHO-250W in his home office with a TZ280 and a standalone access point. Same deal as before, we configured the unit, shipped it out to him and talked him through the swap. There were problems right out of the gate with the internet dropping and then re-establishing. Cycling every couple of minutes.

I suspected a bad cable as the easy possibility, so had him purchase a new cable, but that didn't change the symptom. Seeing no immediate solution, I had him put the old unit back in place and plug the NEW unit's WAN connection into one of the free LAN ports of the OLD unit - it was already expecting DHCP WAN, so this worked right away. At least that way he could still work and I could (theoretically) still connect to the new box to troubleshoot.

I ended up factory resetting it, and configuring it from scratch instead of migrating the old settings. I used a different IP scheme for the LAN just in case there was something conflicting somewhere. It stayed up for a good week until the client had time to help troubleshoot again. When we took the old Sonicwall out of the loop again, though, the same symptom returned. It seemed based on his description of the light patterns like it might be rebooting over and over again.

I had him put the old sonicwall back in, and connect the new sonicwall's WAN connection to one of the LAN ports on the old sonicwall, but this time, connect the computers and access point to the NEW sonicwall. This worked fine, and stayed up for 3 weeks without complaint.

Since there was a new firmware release recently, I just spent some time again today with the client trying to take the old Sonicwall out of the loop, but the same symptom returned. We have power-cycled everything a dozen times throughout this process, and power-cycled the Spectrum modem every time we changed what device was connect to it. The Sonicwalls all have the latest firmware. At this point I don't have any arrows left in my quiver, and it seems unlikely that there is anything wrong with the TZ280. It worked just fine on my bench for a week, and works just fine as long as it is using the TZ250 to get it's internet connection.

Spectrum, of course, isn't willing to entertain any support of our problem, but I'm left thinking it has got to be something to do with their service or their modem. We have at least 10 other TZ280s installed at client locations, all now on the latest firmware, but no other clients that have Spectrum.

I'm already opening a support ticket because I don't really have any other option, but just in case, have I missed anything in troubleshooting this issue?

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.