Client Management Suite

I want to deploy SEP to all computers so I have a job/task made for 32 bit and also one for 64 bit. I have a policy with the target of 'all computers' and want to be able to assign both these jobs and let the agent decide if it needs to run 32 bit or 64 bit instead of having a seperate policy for each version. Is this possible?

Yes this is possible, but just with a managed delivery policy. You have to put both components into the policy and define a applicability rule in both components in the Altiris software catalog.

The applicability rule has to check in the 32bit SEP component if it's a x86 bit machine and in the 64bit SEP component, the rule has to check if its a x64 bit machine

are you talking about the packages?

You can assign both 32 and 64-bit client packages to the same group with no issues. 64-bit OSes will only allow you to install a 64-bit version os SEP, same with a 32-bit OS. You don't need to know which machines have what because when you assign a package to a group for migrating to the latest version the program is smart enough to know which package goes to which OS.

https://www-secure.symantec.com/connect/forums/how-can-you-tell-if-32-bit-or-64-bit-sep-installed#comment-4469011

 

Yes the packages (but through managed software delivery rather than SEP management), using the job 'install symantec endpoint protection client' (one for 32, one for 64).

So if I assign both packages to all computers, is it able to work out not to even run the incorrect version, or will it try to run both and the installer will fail for whichver is incorrect?

Update to that - I applied it as above and it ran the installer for 32 bit then 64 bit, the 32 bit one quit as it needed 64bit. So ideally a better way that doesnt even run would be best, else it will happen over and over again...

Use applicibility rules for the software packages and then setup a MSD policy with both in it.

did you look into the logs? it will be checking once . once upgraded it will check if new package is available if not it will not take.

Hi all, I think this comes down to confusion between deploying SEP through SWD or deploying it through the SEP integration component. I've tried it with the aplicability rules as suggested and it does what I want (chooses 32 or 64 bit) but the install actually fails, it seems because I'm trying to use the packages that were created through SEPIC.

According to this article, http://www.symantec.com/business/support/index?page=content&id=HOWTO60858 the only official way to deploy SEP is through SEPIC, which creates a task rather that using SWD. If I go this route, I have to have two tasks, one for 32 and one for 64 bit, so back to the original problem!

Should I just go for using SWD instead?

We used SWD because it offered additional control not allowed through the IC.  Just upload the same packages you uploaded into the SEPIC into SWD and deploy from there.  That's my suggestion anyway...

Yep I think you're right, thanks for your input.