- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
04-01-2019 07:02 AM
04-01-2019 07:53 AM
Hi,
This error can be down to a number of reasons, not just port 445 not being open, please see some detail on this below ( from 00003414 KB)
PROBLEM:
The PSM detailed Windows Audit feature is using a light-weight agent which must be copied temporarily during the session to the target Windows server.
The file is called PSMWinAgent.exe
The copy fails due to one or more of the following :
SOLUTION:
Note for UAC:
If you are attempting to access (either with PDQ Inventory or PDQ Deploy) a Windows 7, Windows 8, Vista or Server 2008 computer you may get the "Access Denied - Failed to connect to ADMIN$ share" error, even when supplying the appropriate local user credentials that have Administrator access. If the target computer is not a member of a Windows 2003 or later Domain then this is most likely because the target system has Remote UAC enabled. Remote UAC prevents local administrative accounts from accessing ADMIN$ (more appropriately Remote UAC prevents local accounts from running in an elevated mode when connecting from the network).
If you need to be able to access the ADMIN$ using a local account then you will need to disable Remote UAC.
04-03-2019 01:03 PM
Just wondering, is there any plan to allow a manual deploy o the PSMWinAgent?
04-04-2019 06:44 PM
i see that adding the account to the Admin user solves the problem however, we need the account to be in the RDP group only . has anyone tested using it in RDP group only?
06-13-2019 12:35 AM
I have this exact same problem: audit succeeds only if the Windows target user is a member of administrators, and thus have rights to copy the PSMWinAgent.exe to the admin$ share. But I need also to be able to audit users that are not administrators.
07-15-2019 12:11 AM
@Abi Catt @Katja Grahn @s Sha I am also facing the same issue, FAILED TO INITIATE WINDOWS SESSION AUDIT. I have onboarded a local admin account in PVWA which is member of administrator and remote desktop user groups. UAC is also disabled. How to resolve this, Please suggest.
07-16-2019 08:42 AM
Same. CyberArk support states to disable UAC. Adding to administrator works fine.
I have concerns based on Microsoft's documentation around UAC. Doesn't seem secure to do so.
Microsoft:
Be aware that this guidance applies only to well-managed servers on which only administrative users can log on interactively or through Remote Desktop services, and only to perform legitimate administrative functions. If administrators run risky applications such as web browsers, email clients, or instant messaging clients or perform other operations that should be performed from a client operating system, the server should be considered equivalent to a client system. In this case, UAC should remain enabled as a defense-in-depth measure.
09-23-2019 11:13 PM
I am facing the same issue. Adding PSMconnect to Admin Group resolved the issue but is not advisabled. Additionally i have disabled UAC, have enabled File and Printer Sharing and firewall is disable for the end server.
06-09-2020 01:36 PM
I'm also facing the exact same issue, Is anyone having workaround?
07-07-2020 11:35 PM
Problem is with permission to $admin share folder for user which is not member Admin groups.
This is causing issues copying the audit DLL to the $admin share as the user is not an admin because CyberArk expect users on boarded are traditionally privileged users that will be in Admin groups. For user which is not member Admin groups.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

