Client Management Suite

Hello:

We recently had update our Altiris Server from 7.5 version to 7.6 version. But the clients there are in the version 7.5.

When I tried to push the Symantec Management Agent to my Clients using Altiris Server I received the next error message:

"Failed to push Symantec Management Agent. Error: 1722"

¿ Can you help me please ?

Thanks.

Have you tried running the new agent executable manually to see what happens?

MSI install return code 1722 means the package is corrupted.

Hello:

I tried run the new agent manually on one machine and this was sucesfull.

But If I try send the package by push. This send the code error 1722.

Can I do comeone to repair the damaeged MSI ?

Thanks

As far as I see, there is an error:

• http://www.symantec.com/docs/TECH159985

About similar push install issue:

• http://www.symantec.com/docs/TECH54213

To make sure that SMA installation package isn't corrupted -> copy SMA installation .exe package from SMP machine to client PC and manually install it.

Thanks,

IP.

Actually I did have a comment until I took at look at your screenshot.  Normally when I do an upgrade, I have upgrade polices that are created under the normal agent policies... something like "Symantec Management Agent Upgrade", "Deployment Solution Upgrade" etc....

These policies should automatically update the client software like any other software package.

The screen you are showing here, rollout, is what I normally use for one-offs.  Not a mass deployment.  I'm not sure if that has anything to do with it but I would definately use the policies if I were you.

Thanks,

1722 is also "The RPC server is unavailable" and can appear if server failed to contact agent over RPC (during push initiation when push service must be installed). If you will gather and provide server side logs we will be able research further.

Also, can you search for AexNSC.log file (Windows or windows\system32 folder) on client for what push just failed - it will show client side flow for case if failure occured on client side. But I think that this is "server to client" connection problem.

Thanks.

Hi richiegz,

this problem with push install probably caused due:

- Your client PC has 2 different Network Adapters where 1 is routable to NS machine but 2nd isn't.

-- During push Agent installation, NS machine reaches your client PC by client PC's 1st NIC, but after that tries to download Agent installation package to your client PC, using client PC's 2nd NIC, which isn't routable for NS.

1. Make sure that NS machine is able to communicate with client PC by both NICs.
2. If you have 7.x clients which are directed to your NS 7.6 machine, then make sure that you have "Legacy Agent Communication" enabled and also you can use "Symantec Management Agent Upgrade" rollout policies, to perform an upgrade of SMA 7.1 to 7.6 version, without "Push Install Agent" page usage.

Thanks,

IP.