[KB7171] Push install ESET Endpoint Encryption from the ESET Endpoint Encryption Server

Problém

 
  • Enable and send a push install of ESET Endpoint Encryption from a server to client.

Riešenie

Before you begin:

On the client workstation, make sure that you have enabled File and Printer Sharing through the Windows Firewall to allow for a push install.

Figure 1-1

If the client workstation is not a member of a domain, you need to edit the workstation's registry key to allow for a push install. In the workstation registry editor, type:

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem


Then create a new DWord, name it LocalAccountTokenFilterPolicy, and set its value to 1.

  1. On the ESET Endpoint Encryption Server, click + next to Workstations.
  2. Click Client Software Development. If no workstations are listed, click Rescan Network.
  3. Select the workstation and click Remote Install.
  4. Type the Administrator Username and Password for a user with local admin privileges on the destination workstation. If the workstation belongs to a domain, type the domain details.
    Multiple workstations:

    If you have selected multiple workstations, the account must have local admin privileges on all selected workstations.

  5. Select the Workstation PolicyESET Endpoint Encryption Version, Language, and After Install action from the drop-downs.
  6. Click Post. The workstation will move from the Network Workstations list and be placed in the appropriate Workstation Policy team you set in step 5.
  7. In the client workstation, ESET Endpoint Encryption will install. Depending on the After Install option you selected in Step 5, the user will be asked to Restart now or Postpone.


Troubleshooting

If you are unable to push an install remotely, verify the following:

  • Can you access \machinenameadmin$ from Windows Explorer using the same username and password you enter in the push install window?
  • Are you entering a netbios domain name? Try to enter the username instead as domainusername.

  • Does the password contain any characters that are not alphanumeric?

  • Are you sure the user has local administrative privileges to the remote PC?