I have replicated SEPM servers with 1 parent server and replicated partners. Im a global monitoring person in Symantec in all BUs. We're just upgraded from version 11 RU7 to 12.1 RU2. Upon checking on the clients from different BUs all are ok until I noticed in the My Company>Default Group. Many clients are still in that particular folder. Everyday when I am checking that Default Group it keeps on increasing the number of clients. Its a hassle for me to always move the client back and then replicate .. I am having troubles also with other BUs/countries that keeps on coming back. Clients moved to Default Group acquires deifferent policy.. so users are complaining because of that.. Please help me for a possible solution for this,. I already searched on KBs it didnt help because this problem is already exist before since 2009?
I need your expertise on this. Please Help me.. Thanks!
hello,
Do you have AD intergated SEPM ?
P.S.
I already tried to check the Location Awareness and Remember the Last Location but it seems doesnt work...
BTW, the version of the clients that I have are mixed with ver 11 RU3,RU4,RU5,RU6 and RU7,
Right now, I am not using AD integration because we are using the embedded database..
have you checked remember the last known group?
Hi Joash,
Follow the steps in this link to resolve this issue.
https://www-secure.symantec.com/connect/blogs/clients-move-default-group-automatically
Keep me posted on the status.
If you still find the same issue follow this article.
Article URL http://www.symantec.com/docs/TECH98339
yes.
Hi Berino,
Is it applicable to SEPM 12.1 RU2? never saw this KB.
Check this artical
It should work for 12.1 RU2 as well cause the Agent Info Concept is retained in 12.1 RU2. So go ahead try the steps and let me know the status of the issue :)
How to do this solution?
Do I need to break the replication?
When a client appears in the Default Group as a result of the conditions above, move the client back to its appropriate group within the SEPM. For clients that are routinely moving out of the IP range of the network without VPN access, it is best to set a policy to ensure virus definitions are downloaded via LiveUpdate to the mobile client. Do not have the client try to reach back to a SEPM from a foreign IP address as this can trigger the undesired behavior. When setting the client to use LiveUpdate to retrieve definitions while mobile and not attempt to reach back to a SEPM, once the client returns to the home network it should still report back to its appropriate group in the SEPM with an appropriate local IP address.
So, does this mean that I should not set a policy that will try to reach SEPM? how about using VPN?or Location specific policy? I'm also wondering that this happens also to other BUs(replicated partners) eventhough they have no policy assigned about trying to reach the SEPM server? Like in our case here... all cllients in a particular group of a replicating partner went all to the Default group.. seems weird eh..
You need not break the replication. Just do this in the SEPM in which the clients are reporting with a Green Dot!!
should I apply this to all SEPM?
Follow the steps in all the SEPMs where you have clients jumping to the Default Group without your approval!!