Asset Management Group

 View Only
Expand all | Collapse all

Altiris Agent redirect from one NS to Another

  • 1.  Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 09:00 AM

    Hello

    We using Altiris Client Management Suite 7.6 and we have two NS i.e Testing and Production.

    From testing server we trying to redirect altiris agent and it got failed through command prompt as well as script on all the machine but from production to testing server redirection is succeeded with the same command. We using below command line to redirect altiris agent.

    We tried to redirect through script as well as, we have directly run the below command on machine

    C:\program files\altiris\altiris agent\aexagentutil.exe /server:NS Name with FQDN http://NS name:8016/altiris



  • 2.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 09:13 AM

    Hi,

    any error code ? What is the exact failure you get? Is your productive NS running on different port? Is there any firewall issue between test and production?

    Regards

    MD



  • 3.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 09:24 AM

    It looks like you're using HTTPS.  Are you requiring it for all communications with the NS?  If so, you may need to import the certificates for the new server into the agent before redirecting. I believe you can automate this process using the communications profiles settings that 7.6 introduced. 

     

    This document may help with redirecting using communication profiles.  It's 8.0 specific, but I believe the process is similar in 7.6:

     

    http://help.symantec.com/cs/ITMS8.0/SMPLAT/v39770580_v113932717/title?locale=EN_US



  • 4.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 09:55 AM

    Hey All

    We can redirect production to Test server through directly command prompt as well as script from user machine  but cannot redirect Test to Production from user machine through directly command prompt as well as script



  • 5.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 10:21 AM

    Hi Vikas,

    maybe you want to answer the question to give you the appropriate answers.

    If you want to use the command line the correct syntax is: C:\program files\altiris\altiris agent\aexagentutil.exe /server:NS Name /Web:http://FQDN:8016/altiris

    What is the exacty error you get? You are using port 8016. Is there any firewall between the test and production? Maybe it is only allowed one way to communicate on this port?

    The article meant by PreppieTechie is the normal approach to get this working.

    Regards

    Michael



  • 6.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 10:36 AM

    Hello

    We receive error Failed to switch server http://servername/altiris, see logs for details

    Untitled.jpg



  • 7.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 10:40 AM

    Are both servers on the same version with same hotfix?  

    Your example isn't entirely clear to me regarding the command you are using.  Whenever I've used the AexAgentUtil command to redirect to a server, I don't include the http url, just the server name.  example:  AexAgentUtil /server:nsname.domain.com



  • 8.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 10:45 AM

    Hi JoeVan

    I tried the AexAgentUtil command to redirect to a server. example:  AexAgentUtil /server:nsname.domain.com that works well not the issue.

    Both command working fine no issue in command.

    but yes both servers are same version of 7.6 but with different hotfix like Test server having 7.6 HF7 and Production having 7.6 HF1



  • 9.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 11:18 AM

    Assuming you have the agent upgrade policies enabled on your test server, the agents are probably on a newer version than the production server and may not be compatible to register on the older server code.  I'd suggest you either upgrade your production server to HF7 or turn off the agent upgrade policies on the dev server if you plan to move agents back and forth.  



  • 10.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 11:31 AM

    Yes upgrade policies enabled on test server but i think i should affect to redirect another NS.

     



  • 11.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 12:38 PM

    You could test the version theory by switching a production machine to the test server and then immediatly switching it back before the agent updates. If that works but you can't switch agents that have been upgrade, you know the agent version to be the cause.  

    I also notice on your screen shot for the event viewer a few other events that look interesting, can you share the entire message string from the other errors / warnings?  For example, one says "failed to send data to 'HTTP...."



  • 12.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 22, 2016 03:54 PM

    vikas1101,

    Have you tried using the AeXNSAgent and new parameters to update them.... Just a thought.. possibly use the /reinstall

    for example:

    AeXNSAgent.exe -s -a ns="NewSVR" nsweb="http://NewSVR/Altiris" NOSTARTMENU /s

     



  • 13.  RE: Altiris Agent redirect from one NS to Another

    Posted Jun 24, 2016 06:39 AM

    Your highlighted warning states that you are trying to connect to port 80; whereas, your opening comment to the thread states that your production NS is using port 8016!

    As its a speed test warning, the targeted server may be a PS, which would be a red herring for this investigation.



  • 14.  RE: Altiris Agent redirect from one NS to Another
    Best Answer

    Posted Jun 24, 2016 09:34 AM

    Hello All

    Thanks for all u r reply. My problem got resolve but the way which i was looking for. I used second optional method

    https://support.symantec.com/en_US/article.TECH127618

    I am looking redirect one NS to another becouse we doing image deployment from one NS and after we have to add that machine to Production NS and this needed in Image deployment task. So that one image gets deployed and its reboot to production then after other task it gets redirect to Production NS through with that task only.