This content has been marked as final. Show 20 replies
1. Create an agent installation file.
2. Save it to a location that is accessible to users
3. If you can remote to the machine in question do so and navigate to the installation file
4. If logged in as the user use the "Run As" option and try manually installing the agent as either the local Administrator or the Domain administrator.......
Give that a bash....
Oke i will Try that one
From with server is he trying to download it from or install the file ...
is it from the Distributed Repositories to with one i point to.. Or is it from the master repositorie???
I have now now 50 repositories most on FTP and some on http and 3 super agent..
I got the same problem as johanTMF. But a manual installation for more than 1000 clients is not really a solution :(
Does anyone else have that problem, too?
I also get "Failed to authenticate with remote system, system error: The network path was not found.", although I can access the machines (including admin shares, ping, etc.) with the same account I use for installation.
Is name resolution via NETBIOS working ?
Oh I had this same issue on alot of boxes. In order for the agent to be deployed remotely the EPO server needs to access \\MACHINENAME\Admin$
Login to one of the servers / Workstations that are giving you the error, open a command window and type in:
you should see a line like:
ADMIN$ C:\WINDOWS Remote Admin
if you do not see this share, easy to fix, just type:
Net Share Admin$
you should see:
Admin$ share created Successfully
Once this is complete, from your EPO server try to map a drive to \\MACHINENAME\Admin$, if it connects, verify you can create a new file/folder in the Temp folder. Then try your deployment again.
I have try this and the server had the admin$ share..
On the workstation with the full name i can access the admin$ share. and make a folder..
I only can not access from the workstation the admin$ share on the server do i need that????
Thanks for the hint, but as I said - the admin shares including Admin$ can be accessed on the client....
I had exactly the same issue. Make sure the File and Printer Sharing is selected on the network connection. This fixed my problem.