Hi,
I am updating the agent of computers that already have an agent loaded on them. enough setting where changed to warnnt pushing out the whole agaent again.
The scheduled job started and run for a little while. in the meantime a staff member restatred the Core server for a different reas whent he server restarted all the cilent moved tot he failed seciton.
I restart to agent push job and in about 20 seconds all the clients computer go to the failed folder wi t tth e following error message.
[Operation failed] RemoteExecute, cmd /c mkdir C:\$ldcfg$
A remote operation failed, no additional information is available.
On unmanaged systems this operation will attempt to access the ADMIN$ file share and remotely start a service
After reading posts about thi issue I have check the permission nd all are OK.
What i have found is that the $ldcfg$ folder already exisits onthe client computersome of the computers have a tmp file in this folder.
I delete the folder of the client computer and reun the push and it worked perfectly.
To me this looks like the the command tryies to create the direcory and because it alread exisits the command fails, then this failure is sent back tot he script that then terminates the whole script..
Is this expected behavour. I would of though that is the diretory existed is could just carry on not stop the hole process.
As these computers alread have an agent I am going to run a script to delte this folder and rerun the agent push. However I do not think i should need to do this as the agent should be able to recover from this situation by itself.