Deploying Secondary Management Server after SQL 2014 upgrade

Published Feb 16 2019 02:08 AM 109 Views
First published on TECHNET on Jul 30, 2015

From SCSM 2012 R2 UR6 onwards, SM officially supports SQL Server 2014.


The issue arises when customer wants to deploy an additional Secondary Service Manager after the migration to SQL2014.


The UI installation will give you error saying that “SQL Server XXX is not running SQL Server 2008R2 or SQL Server2012. Please update a newest version and retry”.

In order to get around this problem use the command line to install the secondary management server


:\temp\amd64>setup /Silent /Install:Server /AcceptEula /UseExistingDatabase:<servername>\<instancename>:<dbname> /AdminRoleGroup:<adminrolegroup> /ManagementGroupName:<managementgroupname> /ServiceRunUnderAccount:<serviceaccount>/<password> /WorkflowAccount: :<serviceaccount>/<password> /EnableErrorReporting:<No/Yes> /CustomerExperienceImprovementProgram:<No/Yes> /ProductKey:*****


This works only if an in-place upgrade of SQL2012 to SQL2014 was done and fails for the fresh installation of SQL2014

Even though command line bypasses the checks which are made though UI, it also checks for the SQL2012 Namespace in the SQL server machine. If the namespace “Root\Microsoft\SqlServer\ComputerManagement11” is not present in SQL server machine then the command line installation fails. One can check in the setup log if the following messages is seen

“Connection attempt to SQL Server 2012 management scope <servername> unsuccessful”

One can quickly check whether the namespace is present or not in sql server machine by invoking the following power shell command


“Get-WmiObject  -Namespace "Root\Microsoft\SqlServer\ComputerManagement11" –List”


If the command fails to return any object then installation will fail even using the command line.

In order to get over this issue you can install a dummy instance of SQL2012 on the sql server machine and then install the SM using the command line as given above.

Once the installation is succeeded you can remove the dummy instance of SQL 2012.
Version history
Last update:
‎Mar 11 2019 10:23 AM
Updated by: