http://www.symantec.com/business/support/index?page=content&id=HOWTO55425

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?

Please do keep this thread up-to-date with your progress!

A few forum threads may also have info that helps:

https://www-secure.symantec.com/connect/forums/problem-installing-endpoint-protection-11-12-through-sms-andor-sccm

https://www-secure.symantec.com/connect/forums/sep-ru6-distribution-sccm

https://www-secure.symantec.com/connect/forums/1603-install-issue-sccm-solved-me

https://www-secure.symantec.com/connect/forums/sep-installation-sccm-task-sequence

Thanks Mick,

I am going to do that extraction right now. The only executables I created were for my 2 groups, I didn't create any for the default group. So i am guessing that something happened witht the sylink.xml file during the creation process. I will do the extractions and take a look and update you!!!

Cheers Dan!  Do let me know what you find.

Very odd, I have opened the EXE's and the sylink.xml is correctly pointing to the proper groups. Starting to think that it may be an issue with SCCM.

Cheers for checking, Dan- that rules a lot of things out.

Are your SEPM's client groups synched to Active Directory, by any chance?

Also: these are existing computers, correct?  You're not rolling out a new master image to all the enterprise at the same time? 

None of my client groups are syncing to AD and these are all existing PC's. Either way I can manage these as they get added by manually moving them to the correct groups. I only have 1200ish total clients so I am not going to lose sleep over it.

Hi,

I am having the same problem - reports as failed, but it has installed.  I simply created a program pointing to setup.exe.  The package I mkade in SEPM was silent.

Are there any extra command lines or config I need to do so it reports OK?

I was able to figure it out on my own. What I was doing was creating packages as a SINGLE .exe file. I unchecked that so it creates the separate folders and files. I then had SCCM package that and the installs went fine and it also reports as fine. Hope this helps.

Thanks for coming back - so did you deploy the msi that is in the folder or the setup.exe with bunch of files?

Thanks

I asked my SCCM guy and he said he did the MSI.