The test db upgrade does exactly that, upgrades the test db to the new version of the ConfigMgr DB. That's why you have to use a test copy of the DB; it's a complete upgrade to validate that it doesn't run into any issues.
To run testdbupgrade for upgrades to non-bassline builds of ConfigMgr CB (like 1602), you can copy the files from EasySetupPayload to the SQL Server hosting the copy of the DB and run setup from these files. You can't use these files to setup a new site (not in a supported fashion and not without a lot of risk of things breaking in the future) but using them to simply test the upgrade of the DB is perfectly supported and fine. J -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John Aubrey Sent: Friday, May 20, 2016 7:02 AM To: [email protected] Subject: RE: [mssms] 1511 to 16xx TestDBUpgrade I use to do it before everything except CU. I don't see an option or anything to do it in the new upgrade method. I use the upgrade in the console, not sure if there is another way or not. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Kolumbus Sent: Friday, May 20, 2016 1:12 AM To: [email protected] Subject: [mssms] 1511 to 16xx TestDBUpgrade Hi Are there any detailed info about setup.exe /testdbupgrade? I know in generally what that option does. I have done it several times. But I can't found any detailed info about it. And what's your opinion.Do we need to run that every time we upgrade using that new console upgrade (1511->1602 for example...)? Any hints, links appreciated, Cheers, Rane Summanen Fujitsu Finland Oy
