ta123
-
Posts
3 -
Joined
-
Last visited
Posts posted by ta123
-
-
Update
Its working now. I searched by IP address to get my computer list and the install worked. It was failing when I used active directory ldap to get my list.
-
Hi I am testing out Eset and I can not get the push install to work. I have went through the check list but it still fails on IPC$. IPC$ and Admin$ are not disabled. I am using a domain admin account to install.
Operating System: Windows 7 Professional x64 EditionOperating System Version: 6.1Installation result:Setting IPC$ Connection: Result Code: 67 (The network name cannot be found.)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: 2 (The system cannot find the file specified.)Setting ADMIN$ Connection: Result Code: 67 (The network name cannot be found.)Setting IPC$ Connection: Result Code: 67 (The network name cannot be found.)Registering ESET Installer as a Service: Result Code: 0 (The operation completed successfully.)Diagnostics conclusion: Result Code: 1603 (Fatal error during installation.)
Installing ESET remote Administrator 6 on Amazon AWS
in ESET PROTECT On-prem (Remote Management)
Posted
Will this work? What will my client push options be since it is not connected to our domain?