Why is following command returning 15 and not 16?

> [Microsoft.SharePoint.SPCompatibilityRange]::NewVersion

MaxCompatibilityLevel         MinCompatibilityLevel     DefaultCompatibilityLevel                      Singular
---------------------         ---------------------     -------------------------                      --------
15                            15                            15                          True

Because Microsoft did not introduce CompatibilityLevel 16, yet. Therefore, the currently highest CompatibilityLevel is 15.

  • Ok fair enough - but what does that mean? And does that mean that I have to specify -CompatibilityLevel 15 on the New-SPSite CmdLet even though im working on SharePoint 2016 (with internal version 16)? – Markus Jun 22 '16 at 8:06
  • 1
    I'm not exactly sure, but to me it sounds as if a Site-Collection created in '16 would run in '13 since they share the same CompatibilityLevel. But that's just speculation. Yes you have to specify -CompatibilityLevel 15. – Daniel Stölzner Jun 22 '16 at 8:59

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.