Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

When installing several new client PC's (or servers) How do I get the installation to direct them to the group I want them to be in and NOT the default group?

Updated: 26 Jul 2011 | 11 comments
Bryan S's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Say, I have 10 PC's in Los Angeles, and I have a group for LA. I want the Installation to put them DIRECTLY in there instead of ME moving them manually. Is this possible?

Thank you

discussion Filed Under:

Comments

Rafeeq's picture
04
Sep
2009
0 Votes 0
Login to vote

Yeah

When you create the package..you need to select the group

admin- install packages

you need to check a group ( LA )

export the package

when you install..it should report to that particular group

if you are using find unmanged computer option

then at the bottom u need to change the default group to LA group

P.S: you need create a group inside sepm

right click my company and select add group..create LA group

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

Please don't forget to mark your thread solved with whatever answer helped you : ) Rafeeq

Prachand's picture
04
Sep
2009
1 Vote +1
Login to vote

To create the new custom

To create the new custom install package

  1. In the Symantec Endpoint Protection Manager Console, on the Admin tab, under Tasks, click Install Packages.
    The current default client installation packages appear on the right.
  2. Under View Install Packages, click Client Install Packages.
  3. Under Tasks, click Export client install package.
  4. Browse to or create a preferred export folder, and select it.
  5. Select whether or not you want to create a single ".exe" file.
  6. Select Installation Settings and Features.
  7. Select Custom Install Settings from the settings drop down.
  8. Select Custom feature set from the features drop down.
  9. Select the group to which the client will be installed. If no group has been created, select the Default group.
  10. Select the Preferred Mode. The default is Computer mode.
  11. Click OK.
    The new install package is created in the location that you specified.
     

Creating custom Client Installation packages in the Symantec Endpoint Protection Manager Console

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

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

Bryan S's picture
04
Sep
2009
0 Votes 0
Login to vote

Looks like each group needs it's own package

As opposed to having one universal package. OK.

Prachand's picture
04
Sep
2009
0 Votes 0
Login to vote

Yes its better to have a

Yes its better to have a package for each group. if we have a universal package then all th clients will go the group for which the package is created and then you have to manually move the clients into there respective groups. In order  to avoid this we assign/ create package for each group.

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

Bijay.Swain's picture
05
Sep
2009
0 Votes 0
Login to vote

Just  select the group while

Just  select the group while creating the installation package.

Bryan S's picture
08
Sep
2009
0 Votes 0
Login to vote

Does not work

I have tried, and it keeps going to the default group.

Bryan S's picture
08
Sep
2009
0 Votes 0
Login to vote
Acretian's picture
08
Sep
2009
0 Votes 0
Login to vote

You can give this a try

If you are saying that even after creating different packages you are having this issue

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 with the respective package of the group
 

plockel's picture
09
Sep
2009
0 Votes 0
Login to vote

(No subject)

edited for confidential information.

Bryan S's picture
09
Sep
2009
0 Votes 0
Login to vote

Once again this was my bad

When I created the package, I left it at the drop down, and did not select the install and feature sets I had previously created to facilitate this. Once I selected this, it worked as it should have. The mistake was made when I went to export the package. Once I selected the right ones, it works fine.
Thank you again.