Client Management Suite

Hi,

Over the last week I have been testing the latest NS 7.1 and the OOBM and Intel SCS solution. I have got through most issues and after screaming and shouting then finding out that just to get OOBM installed, my server needed its language changed to United States .

Anyways my current issues is now installing the Intel SCS solution and this is proving to be painful.

I am following this excellent article

http://www.symantec.com/connect/articles/install-oob-site-service-altiris-71

So when I launch the install, in the logs I get an error " Software Delivery task failed exit code 2147213312

I confirmed the package was there so did a manual install and got this error 2147753984

Now I am stuck so has anyone got any ideas ?

Thanks

HI,

Can you add some more info:
Is that 7.1 or 7.1 SP1 (OOB Version)?
What the SQL version, and is it local or remote?

What do you mean on the “manual” install?
On what step of that manual installation this error appears?

Also please check the OOB Site Server information on page “Settings -> Site Server settings  -> OOB Service section, - is there any errors.

Thanks
 

Hi AlexTh,

This is 7.1 SP1 OOB Version is 7.1.1227

SQL Version is 2008 and is remote

Manual I ment by launching the Symantect management agent and forcing it to run the package again.

OOB Site server information says,

OOB Site Service Agent installation succeeded
Intel® SCS installation aborted due to unknown reason. Please verify that Application Identity user has enough rights on the site server computer and able to login to the SQL server, also check network connections.

Run Update Agent Config task to ensure that Altiris Agent has received latest configuration
Open installation settings page to review and set installation settings
Run OOB Site Server Agent Install task to install agent manually
Run Intel® SCS Install task to install Intel® AMT Setup and Configuration Service manually

HI Vidster,

Looks like a problem with connection to SQL from the client where the task runs. It can be the firewall or the user-rights.
Please check that you have connection from that client to SQL with specified credentials.

If that OK:

Please run the ” Run OOB Site Server Prerequisites Check” task for that client with the settings you specified for installation. (Home -> Remote Management -> Out of Band Management ->Configure Additional OOB Site Server section)

If task failed with something like SQL connection failure or the “View the Prerequisites Check Results” report returns the “General support -> false”, drill-down for that report (Double –click on line) and check “SQL availability” option. If that set to true.
Then try to change the task “Advanced option -> Run Options tab -> Specific user: (Set the user to Local admin that have connection to remote SQL).

If task completed successfully in that case then use the same option in “install Intel SCS task”.
If that still failed, please provide the screenshot of that drill-down report “OOB Site Server state”.

I have done what you requested,

Ran OOB Prerequisites,

General support = true

SQL Availability = true

Install OOB task using Run Options tab "Specific user" = Success

Install Intel SCS task using Run Options tab "Specific user" = Fail

Screenshot of the drill-down report for that task, Attached.

Hi,
Still looks like the problems with SQL availability.

Can you try the following:
Open the : “%Altiris Agent folder%\Agents\OOB Site Server Agent\IntelSCS”
Run manual Install of “AMTConfServer” and check is the install passed correctly with the same parameters that you specified on “OOB Site Server settings page”.

AlexTH,

I think you have something here. Although the account can access SQL box and is defined I got an error "SQL login has no sysadmin rights". Just checking with our SQLDBA and hopefully we will have this fixed. I will get back to you.

Well that has fixed it,

Our DBA was not happy giving this account full sysadmin permissions but non the less he did and the install went fine.

When I installed the platform and other modules this level of permission was not required but we did have the Symantec database on the SQL box defined first. I did try this also with the SCS install but during the install that was suggested using AMTConfServer it said that the database was not compatible so I had it deleted and then ran the automatic process with success.

I assume now the DB has been created it will not need this level of permission anymore ?

Yes, that level of permissions seems needs only for creating the DB. It's should not be critical for working with that DB.