Symantec Management Platform (Notification Server)

 View Only
Back to discussions
Expand all | Collapse all

"altiris failed to copy symantec management agent install service", Cannot push the Agent to a redeploy PC, checked log, the ns still using the old name to access. Re-discover cannot update the old hostname

  • 1.  "altiris failed to copy symantec management agent install service", Cannot push the Agent to a redeploy PC, checked log, the ns still using the old name to access. Re-discover cannot update the old hostname

    Posted Sep 01, 2015 04:01 AM

    HI All,

    I have a All-in-One Altiris Notification Server 7.1 (Virtual Machine) for PC inventory & software deployment with MSSQL database 2008 R2.

    Error when push agent "altiris failed to copy symantec management agent install service" to a redeploy PC (deleted the XP and reinstall to Win7), checked log, the ns still using the old name to access. Re-discover cannot update the old hostname

     

    Log:

    <event date="Sep 01 07:46:44 +00:00" severity="2" hostName="ATS-NS04" source="Altiris.NS.Utilities.RemoteServiceMgr" module="AeXSVC.exe" process="AeXSvc" pid="5488" thread="194" tickCount="1802065876"><![CDATA[Failed to copy the eXpress Client service to \\PC01-NEW\ADMIN$\AltirisAgentInstSvc.exe. Error:The network path was not found.
     This type of failure can occur if a client push is currently in progress or has completed but some files are still locked. This problem can typically be solved by rebooting the computer]]></event>

    Error:

    The network path was not found.

    \\PC01-NEW\ADMIN$\AltirisAgentInstSvc.exe

    The hostname already rename from PC01-NEW to PC01, how can I update this name?

    - I tried re-discover, but the hostname still using the old name in altiris

    1) What can I do? To push the agent to PC01?

    2) Any steps are needed to perform for redeploy PC next time?

     

    Thanks

     

     



  • 2.  RE: "altiris failed to copy symantec management agent install service", Cannot push the Agent to a redeploy PC, checked log, the ns still using the old name to access. Re-discover cannot update the old hostname

    Broadcom Employee
    Posted Sep 02, 2015 03:54 AM

    Hi A-Law,

    1. Does NS is properly pings your new PC by it's hostname/fqdn? (Does correct IP return from a new PC during pinging from NS?)
    2. If new PC has a new IP Address, then have your tried to manually add this new IP address and push Agent from SMP Console?

    Here are some links about similar problem:

    Thanks,

    IP.



  • 3.  RE: "altiris failed to copy symantec management agent install service", Cannot push the Agent to a redeploy PC, checked log, the ns still using the old name to access. Re-discover cannot update the old hostname

    Posted Sep 04, 2015 04:07 AM

    Hi IP,

     

    1) Yes can ping correctly, just NS still using the OLD hostname with that IP. I think because the reinstalled OS still haven't the Altiris agent on it, it don't know to update. If so, how to install the agent in this new name PC? As the error still found when pushing agent with "\\PC01-NEW\ADMIN$\AltirisAgentInstSvc.exe"  <-- the hostname is PC01 now not PC01-NEW, it's must fail~

     

    2) How to add by IP? I always use discovery only

     

    Thanks



  • 4.  RE: "altiris failed to copy symantec management agent install service", Cannot push the Agent to a redeploy PC, checked log, the ns still using the old name to access. Re-discover cannot update the old hostname

    Broadcom Employee
    Posted Sep 04, 2015 06:07 AM

    Hi A-Law,

    well, if this old computer "PC01-NEW" record isn't required for you in your NS database, then you can just delete it via mouse right click menu from SMP Console and re-run network discovery to re-discover your new PC-01 client computer for further SMA Push installation.

    How you can install SMA on client pc:

    1. You can use Agent push install page and manually specify there IPv4, Hostname of client computer  or use "Select Computers" button to add existing computers for further push installation of  Symantec Management Agent.

    SMA PUSH.jpg

    2. You can open this NS URL on client computer and click "click here to manually download and configure" link ⇒ then it will automatically download installer and install Symantec Management Agent on client PC.

    3. You can download "AeXNSC.exe" installer on client computer and manually install it

    • On client computer, open \\Your NS Server Address\NSCap\bin\Win32\x86\NS Client Package\ and download "AeXNSC.exe" ⇒ install it on client computer.

    ⇒ after completed manual installation of SMA on client computer, you need to specify NS URL for installed agent via mouse right click menu on Agent tray icon and then send basic inventory and refresh policy.

    NSweb2.jpg



  • 5.  RE: "altiris failed to copy symantec management agent install service", Cannot push the Agent to a redeploy PC, checked log, the ns still using the old name to access. Re-discover cannot update the old hostname

    Posted Sep 06, 2015 10:16 PM

    Hi lgor,

    Thanks, some questions:

    1) I cannot the delete the old PC record as I need to keep a record of OLD PC also.

    2) I cannot use IP to put in the Push agent page because:

    - The PC new's IP (From DHCP) also is an OLD PC's IP, thus I cannot add it. THe discovery also don't scan that IP as a new PC....

    3) Can I force the push install use IP \\192.xx.xx.xx\admin$ instead of the hostname to access \\PC-NEW\admin$?

    Any idea to slove it? Thanks.

     

     



  • 6.  RE: "altiris failed to copy symantec management agent install service", Cannot push the Agent to a redeploy PC, checked log, the ns still using the old name to access. Re-discover cannot update the old hostname

    Broadcom Employee
    Posted Sep 07, 2015 02:25 AM

    Try to add IP address and push agent or install agent manually on your new PC, then problem will be solved.