Today I tried to update an SCCM 2012 environment to 2012 SP1 according to the manuals from Microsoft and the checklist from Jason Sandys. Then we got a lot of questions about the TESTDBUPGRADE Step, because we had no test environment and have to run it in the production on a copy of our DB:
- Where do we have to run this Command? On the Site Server or on the SQL Server?
It’s possible to run it on both. You can specify the connection parameters like that: setup.exe /TESTDBUPGRADE SERVERNAME\INSTANCENAME\DBNAME
- Does this command change something on the system?
Yes it does. We discovered, that it creates certificates on the SQL server, restarts SQL services and installs a bootstrap service on the database server!
So you should definitely run this command on a test database server with the same version of SQL installed as in the production. With the described command line arguments you can run it also on a remote system like in the screenshot below.
Latest posts by Thomas Kurth (see all)
- Office 365 DLP – Add detection of the swiss social id to detect personal data - February 8, 2019
- Take action: Default permissions in the Microsoft Compliance Manager gives all users full access - February 2, 2019
- Test connectivity to various Azure and O365 services - January 9, 2019