IT Management Suite

Hi guys, I am not sure If this is the right forum to ask this question but if this is not the right forum then please move this thread to the appropriate forum where it can be answered.

I dont have any experience with Altiris. One of my customer is using Altiris and we are trying to install Symantec Endpoint Protection onto the computers. We have the below batch file which will check if the machine is 64BIT it will install the 64BIT package and if it is 32BIT then it will install the 32BIT package. SEP is installed fine without any issue. However they are getting the following in the Altiris code.

Status:Failed         Return Code:1

Can any 1 please tell me why Altiris is giving false return code whereas the package is installed just fine onto the computers and how can it be fixed from Altiris side so that it give Return Code:0 which is succuess.

Here is the simple batch file:

+++++++++++++++++++++++++++
@echo off

IF %PROCESSOR_ARCHITECTURE% == x86 (

echo this is x86 platform...

AVNOFW_86.exe

) ELSE (

echo this is x64 platform...

AVNOFW_64.exe)

+++++++++++++++++++++

You really should be using the full functionality of the Symantec system, a batch file will tend to abstract any real error code. It may be something simple like the echo output keeps the hidden CMD window open which then gives an error if the Symantec Management Agent forcibly closes it after a 30 minute timeout.

The best practice way to do it is to create a Software Release for the 32 bit version, command line type Install and with a detection rule that identifies that specific version of SEP. Have an Applicability Rule of NOT 64 bit OS. Create another Software Release for the 64 bit version, similar command loine and detection rule and Applicability Rule of 64 bit OS.

The create a Managed Software Delivery Policy with both Software Releases in, either way round. Edit the Advanced properties of each to Continue on Failure. I put in two Compliance Schedules, 00:00 No repeat, will cause the Compliance Check to run as soon as the PC gets the Policy, and then 12.30 Daily so that it checkss for Compliance every day. In a large deployment there will always be the odd PC that's shutting dow as it tries to do the install the first time. Remediation can be left at the default of Immediate.

You can run the Software Execution Report to check on successful executions and failures.

For each Software Release you can click on the Action icon in the top left hand corner > Actions > Create Installed Software Filter. As each install runs successfully the Agent should report that back and it will appear in Installed Software in the Computer's inventory and hence the Filter. You may need to update the filter manually, Filters only update automatically if they've got anything applied to them.

Are you by any chance telling the install to not reboot?  We have the same issue regarding SEP and the reboot flag being set.  The problem is that the setup.exe doesn't know how to pass the reboot code correctly and instead passes a code of 1.  I've simply added 1 to the success codes on the package command line options, which mind you isn't the correct option.  The best way would be to find whatever registry key SEP flags for the reboot, check if it requires the reboot, and reset the error code to 0 or 3010.  If you map the error code to 3010, be sure to specify that as a success.

You can also extract the EXE with 7-zip or something similar and distribute the MSI.  That should pass the correct reboot codes.

Hi SymSpec.

If I were in your shoes, I would chosen another way to do that.

First thing is generate the SEP installer. You can access the SEP Manager and generate the installers to windows x86/x64 and Mac. After that, extract the exe to see all the content inside the package.

Then import the extracted SEP package in Altiris console. Go to Manage > Software, right click on any blank part on left pane and chose "import package".

*Pick "setup.exe" as your default installation file. Altiris will create the installation command lines automatically.

In the end, create a task called "Quick delivery", pick the SEP package, chose the install command line and deploy the software to the desired machine.

Also I'm attaching a link that explains more what I said (+more prints) and another options as detection and application rules, how to create a policy to deploy a software, etc.

https://support.symantec.com/en_US/article.HOWTO59040.html

I hope this process helps you.

Best Regards,