Remote installation of a local account

Discussion in 'ESET Server & Remote Administrator' started by prince74, Dec 4, 2012.

Thread Status:
Not open for further replies.
  1. prince74

    prince74 Registered Member

    Joined:
    Nov 23, 2012
    Posts:
    4
    Location:
    Россия
    Good afternoon.

    Was a task - remote installation antivirus.
    The version of the console on the server Era - 5.0.122. All workstations and server Era domain member of our company. Because Installing a domain administrator account is not safe, it was decided to create a special service account. This account has been included in the Local Administrators group of all workstations. Her name was also runs Eset Remote Administrator Server on the server Era. Installing the Anti-Virus on this account. When diagnosing the following results:

    Installation result:
    Setting IPC $ Connection: Result Code: 0 (The operation completed successfully.)
    Remote Registry Connecting (OS Info): Result Code: 0 (The operation completed successfully.)
    Remote Registry Opening (OS Info): Result Code: 0 (The operation completed successfully.)
    Remote Registry Reading (OS Info): Result Code: 0 (The operation completed successfully.)
    Remote Registry Connecting (ESET Security Product Info): Result Code: 0 (The operation completed successfully.)
    Remote Registry Opening (ESET Security Product Info): Result Code: 0 (The operation completed successfully.)
    Remote Registry Reading (ESET Security Product Info): Result Code: 0 (The operation completed successfully.)
    Setting ADMIN $ Connection: Result Code: 0 (The operation completed successfully.)
    Copying ESET Installer: Result Code: 0 (The operation completed successfully.)
    Setting IPC $ Connection: Result Code: 0 (The operation completed successfully.)
    Registering ESET Installer as a Service: Result Code: 1460 (This operation returned because the timeout period expired.)
    Diagnostics conclusion: Result Code: 1603 (Fatal error during installation.)



    Please, tell me, what could be the problem? I looked for similar questions in the forum, but did not find it a problem with the use of an 'administrative records. Maybe this is the problem?
     
  2. Marcos

    Marcos Eset Staff Account

    Joined:
    Nov 22, 2002
    Posts:
    14,374
    What operating system are you installing ESET on? Could you confirm you're attempting to install Endpoint on clients? If the computers are in a domain, try using a domain administrator account which has stronger privileges than local admins.
     
  3. prince74

    prince74 Registered Member

    Joined:
    Nov 23, 2012
    Posts:
    4
    Location:
    Россия
    I tried to install on windows 7 x64 and x86. I make the installation of client initially Eset Endpoint Antivirus 5.0.2126.0. For security reasons, we do not want to use this domain administrative account. Perhaps you know of other ways to install antivirus on the workstations?
     
Thread Status:
Not open for further replies.