Just ran the 21 March 2016 AutoSPInstaller against the SP2016 RTM (trial) media.
Install process went fine.
However the Central Admin content DB has been left in compatibility mode:
```
Database Schema Versions
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 16.0.79.0, Maximum Schema Version: 16.0.79.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSprocsSequence Current Schema Version: 16.0.93.0, Maximum Schema Version: 16.0.93.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 16.0.4.0, Maximum Schema Version: 16.0.4.0
Microsoft.SharePoint.Upgrade.SPGlobalExtensionUpgradeSequence Current Schema Version: 16.0.6.0, Maximum Schema Version: 16.0.6.0
Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__
```
I'll run a PSConfig and see if it cleans it up.
Comments: ** Comment from web user: CraigHumphrey **
Install process went fine.
However the Central Admin content DB has been left in compatibility mode:
```
Database Schema Versions
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence Current Schema Version: 16.0.79.0, Maximum Schema Version: 16.0.79.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSprocsSequence Current Schema Version: 16.0.93.0, Maximum Schema Version: 16.0.93.0
Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence2 Current Schema Version: 16.0.4.0, Maximum Schema Version: 16.0.4.0
Microsoft.SharePoint.Upgrade.SPGlobalExtensionUpgradeSequence Current Schema Version: 16.0.6.0, Maximum Schema Version: 16.0.6.0
Microsoft.Office.Project.Server.Database.Extension.Upgrade.PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
Microsoft.SharePoint.Administration.SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__
```
I'll run a PSConfig and see if it cleans it up.
Comments: ** Comment from web user: CraigHumphrey **
Bugger, can't do BOLD inside of CODE.
It's the last two lines that are key:
PDEUpgradeSequence Current Schema Version: __4.0.0.0__, Maximum Schema Version: __16.1.273.0__
and
SPContentDatabase Current Schema Version: __16.0.4327.1000__, Maximum Schema Version: __16.0.4315.1000__