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.
Principal Security Consultant | MVP at baseVISION AG
I’m a consultant, trainer and architect for modern workplace and enterprise mobility projects with Microsoft Technologies in the past ten years. I love to push and design the modern workplace based on Microsoft 365 for my customers which is the only answer for the current security threats, agile world and the fast-changing business requirements of my customers. Important for me is to simplify and automate the operational processes, because there are the highest costs.
Latest posts by Thomas Kurth (see all)
- Microsoft Sentinel ASIM Parser demystified - March 31, 2024
- Enhancing Network Security Insights with IDS/IPS of Ubiquiti Dream Machine Pro and Microsoft Sentinel - March 10, 2024
- Ubiquiti Dream Machine Pro Logs to Microsoft Sentinel - February 6, 2024
0 Comments