Full regression testing cycle without long-term stability tests takes about 2 weeks. Do you not find it logical that the OS released long ago is already supported, and the OS released most recently is not yet supported?Īlso, no one said " it takes 90 days for full testing for a company as big as VEEAM". While Windows 10 21H2 is not yet supported because it was literally just released late last month. ![]() I'm not sure I follow what you're saying here 11 is already supported because it was released 2 months ago. I think, if you use a vbr server to deploy the agents, it should already work, but with a warning and of course, officially not supported yet.įind out more about the official support in this topic:ī&R 11. We all want a working and bug less version from veeam. It needs to be tested against the code, sometimes there is a need to adjust the code. So official support will come, but not from day 1. 21H2 was released as GA 1-2 weeks ago I think. It‘s always possible that microsoft has done a code change in the last minute before the GA release.įor official support, veeams commitment is to deliver that within 90 days starting at GA release. Veeam V10 has supported Microsoft Windows 10 (starting from version 1607 up to version 2004). There is a difference between „install is working“ and „officially supported“. There was never an official support for 21H2 from Veeam V10. ![]() ![]() The 11 agent has not had an update since October. How is it an older version of the product supports this OS build but the newer one doesn't? 21H2 has been in preview release for half a year.
0 Comments
Leave a Reply. |