SEP deployment using Altiris Integration Component
Updated: 21 May 2010 | 17 comments
I'm trying to deploy the SEP client to several test machines through Altiris. All of my Altiris integration component options are setup and working properly. My SEP client install packages are built and work correctly if deployed through SEP Manager or via unc path.
When I attempt to push the install package out through Altiris, the package downloads to the client pc, but gives me a status of "Run Failed" when I check the Altiris agent gui. So basically, I can get the install package to the client computer through Altiris, but the package fails to run/install.
Any help would be appreciated.
discussion Filed Under:
Comments
Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint
Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint
Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint
Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint
Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint
Paul Murgatroyd
Principal Product Manager, Symantec Endpoint Protection
Endpoint twitter feed: http://twitter.com/symc_endpoint
I noticed the threads on the
I noticed the threads on the SEP Integration Component. I am about to deploy several thousand clients. There are some articles on Group Policy deployment and I'm wondering which method is more robust. What is your opinion?
Any links would be appreciated.
thanks
SEPIC Comments
I can only comment on the SEP Integration Component since I chose that route. Naturally this method relies on the client having Altiris on it and there are a few PCs in my environment where this isn't the case for whatever reason. We previously deployed SAVCE via NT logon script and I liked this method because, to me, it's not as finicky as GPOs and almost guaranteed to run 100% of the time. However, Symantec never included this deployment option in SEP (maybe login scripts are too old school?).
A Group Policy deployment would've had more complete coverage in my opinion where you wouldn't have to worry about a functioning Altiris Agent. On the flip side with SEPIC, you can more easily manage your computer collections via Altiris and target only machines you want SEP installed on. I required this scenario but it may not be a concern for you in your environment.
Anyhow, go through the SEPIC Release Notes where you'll find the Help pdf file extremely useful as well.
http://www.altiris.com/Support/Documentation.aspx#s
Clint
Clint
Re
We are having the same problem, we are migrating SAV clients to SEP, after the altiris job, SAV has been uninstalled but SEP is not installed.
The SEPIC works well but why
The SEPIC works well but why didn't Symantec put a task server piece in there for the oncey - twocy deployments? In fact why did you use software delivery over task manager?
There are some issues in our environment with MS Outlook. There is a SAV plugin that got loaded in the outlook Trust Center. This problem is documented for resolution but is there a preventative step out there?
Would you like to reply?
Login or Register to post your comment.