Video Screencast Help

Upgrade from 11.x to 12.1.x AND change group in SEPM

Created: 23 Oct 2012 | 6 comments
Alex_CST's picture


We have been testing a 12.1 SEPM to upgrade an 11.x client who resides in one group, export the installation package to be used with SCCM and install 12.1.  We want to change the group that the endpoint is in alongside the installation, but when we choose the option "Add clients automatically to the selecterd group" this does not work.  Only new clients seem to obey this setting.

Is there something similar for endpoints who want to upgrade their SEP version AND change groups?  It has to be done in 1 seamless function

Comments 6 CommentsJump to latest comment

Ashish-Sharma's picture

Installing clients with Microsoft SMS 2003


This topic also applies to Microsoft System Center Configuration Manager (SCCM).

Check this comments

Mick2009 Symantec Employee

Hi Dan,

"Thumbs up" to the advice above.  There is also a “Installing clients with Microsoft SMS 2003” section of the Symantec™ Endpoint Protection Implementation Guide has additional details that has additional details about deployments via SMS 2003 and SCCM 2007.  In my experience, following the steps there should be successful.

Workstations, and VM's. I have exported my exectuable's, created single .exe's and checked the boxes to have the installations put the workstions into the Workstations group and to get the associated policies, and the same for the VM group. If I manually run the executable on a machine, the machine get's put into the correct group and gets the correct policy. If I have SCCM push the installation, every machine no matter what executable is used, the machines end up in the DEFAULT group. Is there a reason for this?

Are there duplicate clients appearing in the SEPM, or are all the clients just in the wrong group?  If it is that all clients are in the wrong group, then the most likely situation is that the setup.exe created for the default group has been rolled out to all clients, not just the machines intended for that group. 

Another possibility.... Those setup.exe files created have a sylink.xml inside of them which has details about which client group to apply to the installed client.  If you have time, open both setup.exe's with winrar, 7z etc and extract the two sylink.xml's.  Do they specify the desired groups or are they both for the default group?

Check this thread

Thanks In Advance

Ashish Sharma

Alex_CST's picture


They are not creating duplicates, they are just not moving from one group to the other

I checked the sylink.xml file within the setup.exe

<RegisterClient PreferredMode="1" PreferredGroup="My Company\Workstations"/>

This is the group that i want the client to go into, the client is currently in \servers

At the moment SCCM is not even a factor, I am just doing this manually to test

Please mark posts as solutions if they solve your problem!

Ashish-Sharma's picture


Also you can use Client Deployment Wizard.

How to install clients using "Client Deployment Wizard" in the Symantec Endpoint Protection Manager 12.1

Overview of Push Deployment Wizard in Symantec Endpoint Protection 12.1

Upgrade clients to SEP 12.1 by Auto upgrade feature

Thanks In Advance

Ashish Sharma

pete_4u2002's picture

have you tried the script for the clients to be move to different group?

MadTheory's picture

Make sure when you setup the new package, that under "Client Install Settings" you choose to "Remove all previous logs and policies, and reset the client-server communications settings" under the "Upgrade Settings" under the "Install Tab." 

A. Wesker's picture

Hello Alex_CST,

Your issue should be dated before the upgrade to the SEPM to 12.1 for sure.

For the SEP client registration work flow, it's the SEPM database information which gets the priority on everything (Domain ID, Connection Mode, Prefered Group, ...) and it's like that by design no matter if you uninstall SEP completely on the client machine and you reinstall it with a custom Client Install Settings in order to remove all previous logs, policies and force the reset of the communication settings client-server.

Here is a link for more details regarding the SEP client registration work flow =>

Your existing SEP clients are already known on the database to a specific PreferedGroup so as long as these information are on the SEPM Database, these SEP clients will come back to the Prefered Group already known on the database.

Is it an Embedded or SQL Database ? How many SEP clients are in this situation ?

Do you still have a SEPM Database backup from the SEP 11.X version ?

As Pete mentioned previously, the MoveClient.vbs script "might" help to resolve that, however it will probably not work with a SEPM 12.1 version (it's supposed to work correctly from 11.0 RU5 to 11.0 RU6 MP3)

MoveClients.vbs script =>

Please read carefully the article and recommendations provided on it before to use this tool.

Kind Regards,

A. Wesker