Jump to content

ichadji

Members
  • Posts

    8
  • Joined

  • Last visited

About ichadji

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Greece
  1. Yes i see the xml. i don’t want to activate it “locally” i want the “classic” procedure- remotelly
  2. Hello Dear All, lastly, i performed an Upgrade Components procedure.. My versions are: RAS 6.5.522.0 Agent: 6.5.522.0 ERA Web Console: 6.5.388.0 Everything WERE working fine. After the upgrade, i joined to the SAME domain with RAS, a Win 10 Prof (v.1803) client. Firstly i had some issues with agent deployment(i found a solution with enabling SMB parameter in the client! This was not mentioned nowhere in this forum! Many Thanks to JDED), afterwards, i tried to install Eset Antivirus 6.6.2078.5, and of course during the installation i checked the option to activate the software with the appropriate license.. The Installation finished successfully, but the client did not activate! I ran an extra client task - product activation, BUT nothing changed! My client is still not activated! The error / Status i have in my ERA Web Console for the specified task is: FAIL.. and from the client's log file i found that: Activation Not Successful. Could not reach activation Server.. I haven't changed ANYTHING on my network since the last successful install i made.. What is going on with the last version!??!
  3. Hello to everybody, i Have Just updated my Remote Administrator Server Components to the last version, through the upgrade components Task.. Everything is working fine, EXCEPT this: I have a client in my network, Win 10 Prof v.1803, joined to the same domain as my Remote Administration Server. I am trying to install the Agent, through the 'normal' procedure (Server Task - Deploy Agent Install..), and i get the following error: WnetAdd Connection 2 Failed with 0x40, The Specified network Name is no longer available. Error Code : 0x40 Please Helppp Thanks
  4. Unfortunately, i still receive the error message while trying through Remote Web Console to deploy the Agent Install... The error Message (i saw it through the report procedure) is : WnetAdd Connection 2 Failed with 0x40, The Specified Network Name is no longer available. Error Code : 0x40 PS: I haven't changed the Computer Name, since i joined the PC to the Domain. The PC is a Win 10 Prof, updated to the last Ver. 1803
  5. Good Morning (morning in Greece! ), first of all thank you VERY Much for your responses! Yes, you were right! There was this option, that i didn't notice it in the past :S Do you believe, the issue with the remote install of the agent, now , will be solved!?!?
  6. ??? no! do i have this option during task’s setup? how am i doing this? Also, do you believe this is the reason I can’t remotely setup the agent???
  7. I Have installed Remote Server in Windows 2003 Server SP2. Everything is working fine! Except one NEW client [windows 10 Prof x64 v.1803]. (Both Ra Server and the "problematic client" are joined in the same domain!) I cant remotely install agent in the w10 client... I Guess this may happening because i have old versions... Remote Administration Server: 6.4.295.0 Agent: 6.4.283.0 Rogue Detection: 1.0.959.0 Web Cosnole: 6.4.266.0 I am trying to update the Components through Remote Web Console via the normal procedure [Client Task-Eset Remote Administrator-New Task - Remote Administrator Components Upgrade...etc], although the task is completed successfully, when i check the versions i have, i see the same versions... What is happening...!? And of course, i still have the error when i am trying to remotely install the agent in the windows 10 client.. Any Help????
×
×
  • Create New...