对于Nutanix产品，是最好的做法，是安装最新的软件版本（例如AOS，NCC），无论是首次安装还是升级。
一些供应商可能建议只安装比最新版本稍低的版本。
我的真正用户案例：我们2个月前安装了NX，并计划将其放入Producton，但是Portal.nutanix.com上已有两个新的AOS版本，所以我可以将AOS更新为最新的AOS吗？
最好的答案乔恩
\n\nHaving come from a multi petabyte (10+ PB) traditional FC-SAN shop, as well as spending many years in consulting before coming to Nutanix, I've had it burned into my brain that going to the \"bleeding edge\" absolute latest code is generally not something most enterprises should do.
\n
\nThis was in the days where code releases from old FC-SAN vendors or other vendors would come out no sooner than quarterly, sometimes longer than that, so if you were on a buggy release, it could be a painful few weeks or few months.
\n
\nWith Nutanix, my view has completely changed on this. Given that we release so fast, and we greatly reduce the amount of components that need to interoperate with each other, its easier to be more flexible with what code you run.
\n
\nHOWEVER, THAT SAID, for most customers, we recommend going to the \"dot zero\" releases, such as 4.6.0, 4.7.0, 5.0 whenever that comes out ... if you either need\/want a feature that was released, or it contains a bug fix per release notes or per support. These are what we call \"Feature\" releases that contain a ton of new things at once.
\n
\nThat doesn't mean that feature releases aren't stable, it just means we recognize a lot has changes, so we want people to be cognizant of that.
\n
\nOtherwise, for most \"steady state\" customers, we recommend sticking with the \"dot one or above\" releases, such as 4.6.1, 4.6.2, and so on. These are maintenance releases, and tend to contain a lot of great bug fixes.
\n
\n
\nBasically, bottomline, I'd go with 4.6.2 for most new deployments and only go to 4.7 if you need some feature thats in there.","className":"post__content__best_answer"}">
