Endpoint Protection

Hello.  I am trying help my boss with an issue we just noticed after migrating from SEP 12.1.2 to 12.1.4.  We are a large company, with multiple groups depending on machine type(desktop, laptop, etc), special requirements for vendors, test machines, etc..  About 12 groups in total, with a few of them having their own sub-groups.

What is happening is when we re-install for whatever reason, previously the machine would be placed in a group called My Company\Unassigned.  The Tech would then call us to have it moved to it's proper group and scanned.  But we're seeing now with 12.1.4, that new machines are being placed in the My Company\Default Group, which we don't want to happen due to different security levels.  Also, the admins usually hide the default group from other limited admins like me, so if a machine gets dumped in the Default Group, I can't move it to the correct group, and need to have an admin stop whatever they are doing to move it, sometimes not a problem, sometimes they are not available right away.

Is this something in the install package we create that has to be set, to automatically place machines in the My Company\Unassigned Group?  If so, where would we look for that setting?

Thanks,

RS

 

Edit:  On a whim, I just right clicked on the Default Group, and noticed under the Properties, there was a check box to Block New Clients?  Is it that simple?  i don't want to check off the box until I have a better idea, and even then I need to run it by my boss....

When you create the package, select the group you want it to be placed in.

yes, if you select that, clients won't be able to go there.

Thanks for the reply. I showed my boss your screenshot, and he asked if we check off that box, where would the clients than be placed? He doesn't want them in an unmanaged state or group. We have our Unassigned group to hold new clients. Unless we had to just recreate the install package, if that was the best practice to prevent them from being placed in the Default group.

Go thru this article before deciding to check that box:

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

Well, I think that answers our questions. We will recreate the install package. Seems to be the best way to correct the issue, without having to do something not reccomended by Symantec. Thanks for the replies. I marked your first answer as the solution. RS

Adding another reference link:

https://www-secure.symantec.com/connect/articles/sep-no-support-tools-please-do-not-publish-i-am-working-it