Client Management Suite

I am seeing some errors of my pc's in my server logs that they are being blocked or unmanaged.  They are not showing up in the blacklist filter, but if I query sql directly they are in the agentblacklist table.  I do have a hierarchy and checked my other 2 NS servers and they don't exist there for other machines either.

here is the error I am seeing It appears they are happening about every couple minutes or so.

Attempt to save messaging resource 0654c50f-7a88-43dc-9a6b-5f7cf1564022 has been blocked by the Host Resource Blacklist.

Exception of type 'Altiris.NS.TaskManagement.TaskStoppedException' was thrown.
   [Altiris.NS.TaskManagement.TaskStoppedException @ ]

There's a couple of KB articles that should help:

"Report for Agent Blacklist"

http://www.symantec.com/docs/TECH215803

And this one should tell you why it's blacklisted:

"What is Altiris Agent Blacklisting in NS 7.0?"

http://www.symantec.com/docs/HOWTO9748

Check the thread

https://www-secure.symantec.com/connect/forums/client-black-listed

Didn't get a chance to check out the above links you guys referenced yet, but was able to find the computer names by searching for the guids in the logs and did an uninstall reinstall of the agent which appears to be resolving the specific cause of my errors

In future, try to reset a GUID, since it could help as well

https://www-secure.symantec.com/connect/forums/client-black-listed

Yeah we tried this on a couple, didn't think it helped but once we found out it was over 200 machines maybe it did and it was just so many things scrolling that we didn't notice

We've had this come up lately as well, and we think the primary reason was a lot of shared GUIDs. We have a batch script that we can run on an admin box that goes out and resets the GUIDs. We then delete the computers in the console that share that shared GUID.

After that is complete, you either let the computers check back in, or force them to check back in. I'll use RAAD for onesie twosie stuff, but we have another batch script that we can run on a large number as well.

There is a "Shared GUID cleanup script":

http://www.symantec.com/docs/TECH212345

It identifies Computer Resources that have changed name recently.