SQL Database content doesn't match SEPM Console
I am trying looking for better ways to administer SEP in our environment, so I am testing out certain SQL statements.
Here is one for example, it gives the name and ID for a group where a Name is like a particular value
Select NAME, ID from IDENTITY_MAP WHERE TYPE like 'SemClientGroup'
AND IDENTITY_MAP.NAME LIKE '%Snow%'
And the result is
NAME ID
My Company\Snow 037FEF020AFB0A2B018E0F0F3386DA0F
So far, this matches the client group in the SEP Console. But now, I want to rename this group
UPDATE IDENTITY_MAP
SET IDENTITY_MAP.NAME = 'My Company\Snow White'
WHERE TYPE like 'SemClientGroup'
AND IDENTITY_MAP.NAME LIKE '%Snow%'
And the result is successful because 1 row(s) affected
And when I run the original SQL query,
Select NAME, ID from IDENTITY_MAP WHERE TYPE like 'SemClientGroup'
AND IDENTITY_MAP.NAME LIKE '%Snow%'
The result is
NAME ID
My Company\Snow White 037FEF020AFB0A2B018E0F0F3386DA0F
But here is the problem, when I see the client group in SEPM console, the Group Name has not changed. And when I log out of SEPM and log into SEPM again, the client group name is the same, "Snow"
Why is this happening?
EDIT:
This problem does not occur with other SQL statements. For instance, if I want to move a client from one group to another
UPDATE SEM_CLIENT
SET SEM_CLIENT.GROUP_ID = '037FEF020AFB0A2B018E0F0F3386DA0F'
WHERE SEM_CLIENT.COMPUTER_NAME = 'DoE-31'
AND SEM_CLIENT.COMPUTER_ID = '3286BF850AFB0A2B004A79AD024086E0'
This works perfectly.
Please tell me how to resolve this issue.
Comments 4 Comments • Jump to latest comment
if you rename the group using the SEPM console, does the change reflects in the table?
Cheers!
Pete
Help Link: http://www.symantec.com/business/support/overview.jsp?pid=54619
Yes Pete, the change reflects in the table, as it is supposed to.
However, it does not reflect in the SEPM, and this if quite frustrating!!!!
On the other hand, if I move SEP clients by simply updating the group ID to which they belong, then they move, and this change is reflected in BOTH the database table, and the SEPM console.
Marriage Made in Heaven
If God is for us, who can be against us? --- Romans 8:31
BUMP
Can anyone help???
Marriage Made in Heaven
If God is for us, who can be against us? --- Romans 8:31
Performing SQL queries directly on the SEPM's SQL database to modify its contents is unsupported and can and likely will result in corruption of the database.
Sr. Technical Support Engineer
Endpoint Security Advanced Team
Symantec Corporation
www.symantec.com
Would you like to reply?
Login or Register to post your comment.