(some understand, some don't, and many caught between these two issues) If you tell one of these customer's that they cannot install an update from Microsoft for months due to the backup it does not always go down too well. Something we are also starting to see more of are customers that also have cyber insurance policies which (stupidly) mandate that they must install all available updates within a week or two of release to remain covered and also MFA on everything (which is the very reason V12 is incorporating it into the console). Do we wish these tools were in place? Of course, but it just isn't reality for us unfortunately. These tools however are just not present in many small businesses and we don't have control over this side of things where we only provide backup services. It's not just data protection either, anti-virus solutions need to confirm compatibility and it's not uncommon with the traditional on-premises AV management systems to have to ensure your endpoints are on newer updates before they can support the feature updates.įor larger and enterprise customers LTSC/WSUS/SCCM/Intune makes perfect sense, and when an admin team are using Veeam in-house they can make sure to roll out updates in a regulated manner.
Veeam aren't the only data protection vendor making these decisions, you would be furious if Veeam claimed day 1 support and all subsequent backups didn't function because of a lack of QA. There should be a process of testing within your environment for these new builds, making sure all applications and policies work before release. Whether via GPO, an RMM solution, or Intune.ĭevil's advocate moment here, if you've selected Veeam as your data protection solution, and you know that Veeam's goal is to support new operating systems within 90 days of release, and that Windows support their feature updates for 18 months, why not put in a policy to delay by 6 months for the new feature update? My head would've rolled if I allowed all devices to patch on whichever lifecycle they chose, especially with the history of breaking changes these feature updates have released in the past (remember 1607 breaking nearly all webcams?). But my advice that you can choose to take or leave is: If you're happy that Veeam is processing as is, then there isn't a problem.
Having seen the insider build bug submissions, everything feels like it breaks on a frequent basis, so they need to focus on RTM. We see ReFS drivers break in monthly updates, so what hope do Veeam have predicting what will break if they tried to QA the insider builds. Just like with VMware, until the build has reached RTM, the QA process can't begin. And it still attempts to backup any of these new Windows builds that hasn't gone through QA. You're correct that Veeam's job is to backup.
0 kommentar(er)
