Description
Pointing the Core Server to a blank database has been performed for a reasons such as:
- The current database is corrupt
- To help narrow down whether a problem is caused by the database.
- The Core Server needs to point to a new database server and a new database is created instead of backing up and migrating the old database.
This is not allowed by default in Configure | Services. It is not allowed to point to an empty database. However, some have edited the registry keys under HKLM\Software\LANDesk\ManagementSuite\Core\Connections\Local to point to a new database and then have run CoreDBUtil.exe manually.
Problem
When trying to configure the blank database using this method, not all database configuration tasks are performed. This leaves the database in a partially configured state. The LANDesk installation runs commands that add to the database during the PostSetupConfig section of the Core Server installation.
One noticeable error is that when clicking on OS Deployment in the 32-bit Console, the 32-bit Console hangs because the provisioning tables are not there or are incorrect.
Other unknown errors may yet be undetected.
Resolution
To resolve this, the database upgrade and configuration needs to be completed. To complete the database upgrade and configuration, run the following commands gathered from PostSetupConfig on the Core Server.
"C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe" /buildcomponents "C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe" /PublishSoftwareConfiguration "C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe" /UpdateCannedReports /silent "C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe" /xml=datamartpm.xml /buildcomponents "C:\Program Files\LANDesk\ManagementSuite\CoreDbUtil.exe" /xml=provisioning.xml /buildcomponents "C:\Program Files\LANDesk\ManagementSuite\alertname2table.exe" -c -d "C:\Program Files\LANDesk\ManagementSuite\alertstrings" "C:\Program Files\LANDesk\ManagementSuite\swdCoreCustomAction.exe" "C:\Program Files\LANDesk\ManagementSuite\alertruleset2table.exe" "C:\Program Files\LANDesk\ManagementSuite\alertrulesets" "C:\Program Files\LANDesk\ManagementSuite\CreateClientConfiguration.exe" "C:\Program Files\LANDesk\ManagementSuite\prov_createstartnet.exe" "C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe" -f "C:\Program Files\LANDesk\ManagementSuite\ENUActionsAndSections.xml" "C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe" -f "C:\Program Files\LANDesk\ManagementSuite\ENUInitialGroups.xml" -u 1 "C:\Program Files\LANDesk\ManagementSuite\prov_Loaddb.exe" -f "C:\Program Files\LANDesk\ManagementSuite\PublicVariables.xml" "C:\Program Files\LANDesk\ManagementSuite\prov_InstallPlugin.exe" -a
Note: A batch file to run these commands is attached.
*** If you are running the Batch file it needs to be ran from the ManagementSuite directory on the core server.
A Change Request has been submitted to have these commands be automatically executed when pointing to a new database under Configure | Services.