Endpoint Protection

I created a custom install package and deployed it to 5 test computers/group. 2 of the clients appeared in the right group and the other 3 appeared in the Default Group. I imported the Client machines using a text file into the wizard. I used the Migration and Deployment Wizard. All of the users are local admins on their computers. We are upgrading the client from SAV 10.0. The custom install package had the correct sylink.xml file. Why would two clients join the correct group and the others join the default when they were all deployed together as one group? Anyone have any ideas?

I'm able to put them in the right group of course by moving them in the management console and sending the command "update content". But I'm just wondering why the y would be in the wrong group in the first place.

Thanks for your help in advance.

Which version of SEP are you installing ?As there was an issue with MR3 , where newly installed clients end up in the "Default Group".'


Title: 'After migrating the SEPM to MR3, newly installed clients end up in the "Default Group".'
Document ID: 2008100211442948
> Web URL: http://service1.symantec.com/support/ent-security.nsf/docid/2008100211442948?Open&seg=ent

I'm using version 11.04202.7. MR4 SP2?
Thank you for the link.

Check this document it should help you:)

http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008050113500148

Thank you Kavin :), but that is what I did. For each group I exported the Sylink.xml so then I would only have to deploy one install package and only have to change the sylink.xml before I deployed it to the clients that are in different group
.
What is baffling me is that I have 5 clients that I deployed one package to concurrently with the sylink.xml file of the group I wanted them to appear in the install package. Out of the 5 clients only two appeared in the correct group the others appeared in the default group. The same installation package with the same sylink.xml file was to deployed to all of them at the same time. So why did only two of the clients  appear in the right group?

I might try Prachand's suggestion even though it's for MR3. Maybe the issue still exists?

Thanks again!

I deployed the client to 4 more test computers concurrently with the same install package today.  This time only 1 client installed correctly in the correct group. The other three installed in the Default Group.

What is puzzling is that on the computers that installed into the defualt group instead of in the correct group had the CORRECT registry key in HKEY-LOCAL_MACHINE\Software\Symantec\Symantec Endpoint Protection\SMC\SYLINK\Sylink  > Preferred Group shows My Company\Correct Group. However in the SEP UI under Troubleshooting they appear in the group My Company\Default Group. I have the install logs from the computer that installed correctly and the others that did not, but I'm not sure what I'm looking for.

Anyone know what I should be looking for or have any insights as to why this is happening?

Thanks.

Were these computers built from an image that contained the SEP client?

This is wat we did when the same thing happened with MR3

Right Click on Default Group -> Properties
Check the option Block new clients.

Then try to deploy New Clients

RickJDS: No. We're upgrading from SAV 10.0.

Acretian: Thank you! I tried your workaround and I think it worked. I tested on a few computers today and they all ened up in the correct group. Wonder if this issue was supposed to be fixed in MR4. Hm. But thank you again! I appreciated your insight!

The solution given by  Acretian will only work if you do not want the clients to appear in this group after deployment & u had completed the deployment.

This is the bug of Symantec in MR3 & has been resolved in MR4.MP2. There is no need to block the clients in default group.

Default group helps us to move the clients to proper groups in case of this issue. If you block it Clients will go to any other group & it will be diffcult to trace if you are doing mass deployment.

Regards...
Ramji Iyyer

All Clients appear in correct group after push deployment half appear in default group

SEPM 11 MP4 MR2
update client Sav 9.005 to SEP 11 MR4 PR2

I see what you're saying. That makes sense that the clients that aren't deployed into the right group fall in the default group so that I can put them in the correct group using the management console. Which did work. I suppose that is the bug fix for release MR4 MP2?

Although I did test checking "block clients" in the default group and it appeared to work on a small scale. It might not work on a large one. I did have one client who did not appear in any group but when I used the "find unmanged computers" tool in the management console, the package deployed like a charm and the client was put in the correct group.

@plockel
I guess having clients appear in the "default group" is the solution so that as an admin they're easier to track and that way you can put them in the group they're supposed to be in.

I'll let you know how my mass deployment goes.

You are correct, this bug still exists in MR4 MP2, even worse when the clients are imported from active directory - the SEPM ends up with a client in the imported OU (that is not reporting) and a copy of the same client in the default group which is active and reporting.

Hoping it is fixed in RU5!

what if the default installation package will report on that group which is block, what will we do, do we need to change the installation package?

I am still having this issue with MR5

still issue in MR5

Some of my clients automatically move to Default group infact my SEPM server and SQL server both are in default group rather than in respective groups.