Outch !! We couldn't access the admin share (\\systemName\admin$) on the target system.

Posted October 12, 20213 yr

Hello to all,
I currently have a problem to deploy the agent on a machine. I have activated the Administrator account on the machine, but nothing works.

I created another administrator account but still this error: "We couldn't access the admin share (\systemName\admin$) on the target system."

I would like to understand in order to be able to do a mass deployment in the future.

Sincerely

October 13, 20213 yr

It's disabled by default in Windows. If you're not on a domain where you can use GPO, you have to do this to the registry on each machine.

“HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System”

Set a DWord called LocalAccountTokenFilterPolicy and set the value to 1. Reboot. Should do the trick.

Paul
1

October 14, 20213 yr

Author

It works !!!!
Thank you very much, but unfortunately, you have to change the registry before launching a mass deployment.
So it's not the ideal solution. But thanks

October 15, 20213 yr

11 hours ago, dimitri.gillet said:

It works !!!!
Thank you very much, but unfortunately, you have to change the registry before launching a mass deployment.
So it's not the ideal solution. But thanks

Oh, I know, but that's why I asked if you were on a domain environment. You could deploy those changes via GPO first. And no problem, glad it worked.

Edited October 15, 20213 yr by Mark G38

October 20, 20213 yr

Author

Yes, I have a Domain environment, GCPW.

My idea was to do a mass deployment so that all my machines would go up on pulseway and then deploy GCPW.
But if I have to change the registry on all the machines before doing a mass deployment it's useless.

Sorry for my English. Sincerely dimitri

October 20, 20213 yr

No worries about your English Dimitri. Doing my best to understand lol.

Assuming the domain environment is the environment you are trying to deploy Pulseway to, then you can push Pulseway via a GPO, and you don't have to worry about enabling the admin share, because Active Directory will have the needed permissions to be able to deploy the software. OR, even with GPO you can make registry changes. So you could hit every machine one way or another super easy with a GPO.