Endpoint Protection

Hi all,

Is it really possible to export a single exe package which can be installed on both 64 bit and 32 bit computers ? in other words is it possible to merge both 64 bit and 32 sep client packages to one?.

No..we can export both 32 bit and 64 bit seperately..

But if we remote install the symantec itself will detect the bit version and install..

Nope not possible to merge the install packages, but they do get created at the same time when you export the package from the SEPM in different folders.

yeah i've seen that while pushing client to computers.

But i'm planning to implement snac, with a policy to download and install sep client if it's not installed already.

If i create a Hi policy as said above and assign to a group which has both 32 and 64 bit computers,  how can i specify two different sep client packages?. If i specify 32 bit package 64 bit computers will not get sep client package right?.

Am i clear?.

Hello,

You could have both SEP 12.1 32 Bit and SEP 64 bit packages in 1single .exe package.

Secondly, the question arises why have both in 1 single.exe package?

Incase, if you are using a Auto-upgrade Feature, you could assign both the packages to the Groups and these deployment would deploy the correct packages to the correct client machines.

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

Hello,

If you are using a Auto-upgrade Feature, you could assign both the packages to the Groups and these deployment would deploy the correct packages to the correct client machines.

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

Hope that helps!!

 If i specify 32 bit package 64 bit computers will not get sep client package right?.

Yes they would not..!

Mr simpson, yeah am aware of that.. What i asked was, the way to overcome this.

As mentioned by Mithun, you could use the Autoupgrade option.

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

my point is not to upgrade clients to latest version but to install the sep client when snac- HI policy fails

Hi

Use separate packages for 32bit and 64bit.

Thanks

Hello,

You would have to use 2 different packages. In this case, check these Articles:

About antivirus conditions

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

Adding Host Integrity requirements

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

Creating and testing a Host Integrity Policy

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

Host Integrity Monitoring: Best Practices for Deployment

https://www-secure.symantec.com/connect/articles/host-integrity-monitoring-best-practices-deployment

Mithun, I've tested an Hi policy with antivirus requirement where dhcp enforcer plugin in configured. All are workign as stated and expected.

I'm planning to implement in my production environment, But i have many as 25 groups in sepm since i'm managing policies by group and all of my groups will have both 32 bit and 64 boxes. Also i'm planning to deploy images with SNAC as per symantec best practises. If a new box is addedd to my environment (either 32 or 64) it will have snac installed and will reside in default group of my sepm.

I can link only one Hi policy with antivirus requirement to default group while the group has both 32 and 64 bit boxes, Here the question arrises..  If i assign a 32 bit packages as a remedy for that HI policy it'll fail in 64 bit clients and vice versa.

Is there any work arrount to address this scenario?.

Hello,

Symantec Network Access Control software does not contain the components that you can select to install or not install. If your client computers run Symantec Endpoint Protection and if you purchased Symantec Network Access Control software at a later date, you do not need to install Symantec Network Access Control software. After you update Symantec Endpoint Protection Manager for Symantec Network Access Control,the Symantec Network Access Control feature on clients appears automatically.

Groups can contain both 32-bit clients and 64-bit clients. However, you must deploy both 32-bit packages and 64-bit packages to separately to the clients. The 32-bit clients ignore the 64-bit installation packages, and the 64-bit clients ignore the 32-bit installation packages.

If your environment has a mix of Symantec Endpoint Protection clients and Symantec Network Access Control clients, it is a best practice to group these clients separately.

For example, a best practice is to not place Symantec Endpoint Protection clients in a group that also contains Symantec Network Access Control clients. Also, if you install the Symantec Endpoint Protection Manager for Symantec Network Access Control, the Symantec Endpoint Protection clients automatically support Symantec Network Access Control.

When you create client installation packages with the Symantec Endpoint Protection Manager Console, you can specify a group to contain the clients. If you reinstall a client software package on clients, and if the package specifies a different group, the clients still appear in their original group. The clients do not appear in the new group. You can only move clients to new groups with the Symantec Endpoint Protection Manager Console.

Reference: Installation Guide for Symantec Endpoint Protection and Symantec Network Access Control.pdf

Hope that helps!!

Sorry i'm gonna leave this thread and start a support case.