Central Management Server left out in the cold

Question

Post reply

Central Management Server left out in the cold

facemann

Right there with Babe

Points: 797
More actions
July 18, 2013 at 8:46 pm

#280339

I just set up a Central Management Server and can now check my policies against a whole group of SQL Server instances. This is great! However, it seems the instance that is designated as the Central Management Server is not checked when policies are evaluated. Is there any way to include this instance or do all policies need to be checked twice: once for the central server, and again on the target group?

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

tutupouet SSCommitted Points: 1512 More actions · Answer 1

hello,

just add the @@SERVERNAME

SELECT

s.server_name as ServerName,

ssg.name as GroupName

FROM [msdb].[dbo].[sysmanagement_shared_registered_servers_internal] s

INNER JOIN [msdb].[dbo].[sysmanagement_shared_server_groups] ssg

ON s.server_group_id = ssg.server_group_id

UNION

SELECT @@SERVERNAME, 'Sql Server'

facemann Right there with Babe Points: 797 More actions · Answer 2

Chauchs,

I am not sure if I understand your reply. Are you suggesting I add the central management server to the sysmanagement_shared_server_groups table? I tried adding it via the Registered Servers GUI but get the error: "You cannot add a shared registered server with the same name as the Configuration Server."