DX Infrastructure Management

Expand all | Collapse all

Robot deployment to target servers failing

  • 1.  Robot deployment to target servers failing

    Posted 08-07-2017 12:37 PM

    Hello 

     

    Am trying to deploy nimbus robot to windows servers. but the deployment keeps failing with error "Could not copy file nms-robot-vars.txt to target"

    First I did a discovery of the servers using a domain admin account with local administrator privileges and firewall is disabled on all target systems.

    The file is been copied to C:\tmp on target system,but its fails as the file size is 0 kb.

     

    BR

     

    Valentine Azike.



  • 2.  Re: Robot deployment to target servers failing

    Posted 08-07-2017 02:21 PM

    Hi Valentine!

     

    Are you able to access the target system by \\IPADRESS\C$ from the hub?

    Is there 2 NIC Cards in the Target System?

    Be sure to have Tunnel between the hubs

     

    Notes:
    1) the ports that should be needed for ADE to work through a firewall
    TCP /UDP
    port 135 for WMI this also has a dynamic port after the initial connection.

     

    Some KB articles on this:
    https://msdn.microsoft.com/en-us/library/bb219447(v=vs.85).aspx
    https://msdn.microsoft.com/en-us/library/aa822854(v=vs.85).aspx 

     

    port 445 for windows shares.
    https://technet.microsoft.com/en-us/library/cc731402(v=ws.11).aspx

     

    For UIM port 48000-48020

     

    For linux & Unix boxes :
    port 22 for the installation

     

    For UIM port 48000-48020

     


    Currently ADE will transfer the packages for each job sent.

     

    Regards,

     

    Alex



  • 3.  Re: Robot deployment to target servers failing

    Posted 08-08-2017 09:42 AM

    Hello Alex

    Thanks for your response.

     

    (1)Are you able to access the target system by \\IPADRESS\C$ from the hub?

        Able to have access.

    (2)Is there 2 NIC Cards in the Target System?

         That I cant say because some are virtual machines and are in various locations but we are been provided the IPs.

    (3)The ports that should be needed for ADE to work through a firewall TCP /UDP port 135 for WMI this also has a      dynamic port after the initial connection.?

      All required firewall ports works fine.(A CA support engineer connected and confirmed this).

    (4)For UIM port 48000-48020

        Telnet from primary hub to target system fail using the above ports.

        Telnet form target system to HUB server connects using the above ports.

     

    BR 

     

    Valentine



  • 4.  Re: Robot deployment to target servers failing

    Posted 08-08-2017 10:09 AM

    Valentine!

     

    About this comment from you: "A CA support engineer connected and confirmed this"

    So you have a CA Support ticket already opened in my understanding, it that right?



  • 5.  Re: Robot deployment to target servers failing

    Posted 08-08-2017 12:16 PM

    Yes correct. 



  • 6.  Re: Robot deployment to target servers failing

    Posted 08-08-2017 06:12 AM

    Hi Valentine

     

    Did Alex's reply help you with this?

     

    thanks

    Rich



  • 7.  Re: Robot deployment to target servers failing

    Posted 08-09-2017 10:14 AM

    Has SMB1 protocol been disabled on the network?  (There has been a recent service advisory from Microsoft advising users to disable this protocol.)  Automated deployment engine in its current form uses SMB1 protocol and very often the "failed to copy file" error is a result of SMB1 being unavailable.



  • 8.  Re: Robot deployment to target servers failing

    Posted 08-09-2017 12:14 PM

    Hello Jason

     

    Thanks for your response.

     

    SMB1 protocol is enabled on the HUB server.

     

    Does this need to be disabled or enabled on the HUB or TARGET servers

     

    BR

     

    Valentine



  • 9.  Re: Robot deployment to target servers failing

    Posted 08-09-2017 12:16 PM

    Should be enabled on both.



  • 10.  Re: Robot deployment to target servers failing

    Posted 08-09-2017 12:41 PM

    It is enabled on both servers already.



  • 11.  Re: Robot deployment to target servers failing

    Posted 08-09-2017 12:43 PM

    Is there any antivirus software running on the target system?  If so, try disabling it temporarily as a test.   We sometimes see "real-time shields" on antivirus software blocking the ability to write to the filesystem.



  • 12.  Re: Robot deployment to target servers failing

    Posted 08-15-2017 10:33 AM

    Hello Valentine,

     

    is your question in the meantime answered or do you still have problems deploying robots and probes ? If yes, please open a case with CA Support for further analyses.

     

    Kind regards,

    Britta Hoffner

    CA Support



  • 13.  Re: Robot deployment to target servers failing

    Posted 08-15-2017 10:47 AM

    Hello Hoffner,

     

    The challenge is still pending and have also opened a support case with support as I have stated before 

     

    BR,



  • 14.  Re: Robot deployment to target servers failing

    Posted 08-15-2017 10:57 AM

    Hello Valentine, do you have the support case number ?

     

    Thanks and kind regards,

    Britta Hoffner

    CA Support



  • 15.  Re: Robot deployment to target servers failing

    Posted 08-15-2017 12:14 PM

    Hello Hoffner,

     

    Case Comment 00800203 - Failed deployment of Nimsoft Controller agent.

     

    BR

     

    Valentine