Execution error. EXT01::Failed to connect to the registry namespace on the remote machine. Check machine address valid logon credentials and valid authorizations. Error code:8011 The CPM is trying to change this password

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Execution error. EXT01::Failed to connect to the registry namespace on the remote machine. Check machine address valid logon credentials and valid authorizations. Error code:8011 The CPM is trying to change this password

L4 Transporter

Windows Registry Plugin not working in CyberArK, we get the following error

 

Execution error. EXT01::Failed to connect to the registry namespace on the remote machine. Check machine address valid logon credentials and valid authorizations. Error code:8011 The CPM is trying to change this password because its status matches the following search criteria: ResetImmediately.

 

I have original (originalAcc) and logon account cyberlog.

 

originalAcc have the registry tab and in logon setting have cyberlog as logon account.

AutoAdminLogon 1

DefaultDomainName EMPTY

Defaultpassword has a value

DefaultUserName the original account originalAcc

we want to change Defaultpassword

 

 

The CPM changes the password but the registry fails. We did all the config:

 

in Platform Name: Windows Registry (The Tab in the account page):

 

Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

(also tried HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon)

 

Value Name: Defaultpassword (for example the name of the string inside Winlogon . Defaultpassword that have a value test123 )

 

Address: The IP/FQDN of the server.

 

  • We created a LogOn Account with the same safe and host of the original account to be changed.and associated to original account

 

  • "Enable Distributed COM" is checked.

 

  • LogOn account inside administrators group (net localgroup administrators OK ), and have permissions inside Winlogon (as single account full control and as a group administrators full group)

 

  • CPM can telnet to server via 135,139,445

 

  • UAC done: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

LocalAccountTokenFilterPolicy (DWORD) = 1

 

  • Firewall on server enabled for 135,139,445 inbound

 

  • Remote Registry Service is enabled

Get-Service RemoteRegistry

Start-Service RemoteRegistry

 

  • Platform of both accounts tried Windows Server Local Accounts and windows domain account

 

 

Thank you

 

1 accepted solution

Accepted Solutions

L7 Applicator

Hi @ABDOU LAZEZ HUSSIEN EL SHEREDI​ 

 

Please check the DCOM and WMI security settings in the target server.

 

Check that logon account has Remote Launch and Remote Activation permissions set to "Allow" under DCOMand check that logon account has Remote Enable and Enable Account permissions under WMI.

 

Hope it helps !

 

 

View solution in original post

6 REPLIES 6

L7 Applicator

This checklist is designed to assist IT administrators in troubleshooting the error 'EXT01::Failed to connect to the registry namespace on the remote machine' (Error code: 8011) encountered by CyberArk Central Policy Manager (CPM) during password change operations.

Permissions & Credentials

·      Confirm the CPM account has local administrator rights on the target server.

·      Verify the CPM account credentials are correct and not expired.

·      Ensure the CPM account is not locked out or disabled in Active Directory.

Remote Registry Service

·      Check that the Remote Registry service is enabled and running on the target machine.

·      Set the Remote Registry service to Automatic startup type.

Firewall & Network Access

·      Ensure TCP port 445 is open between the CPM and the target server.

·      Verify that Windows Firewall or any third-party firewall allows remote registry access.

·      Confirm there are no network segmentation rules blocking CPM access.

Group Policy Settings

·      Use gpedit.msc or RSOP.msc to check encryption and security layer policies.

·      Ensure UAC remote restrictions are disabled if applicable.

·      Check registry key: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\LocalAccountTokenFilterPolicy is set to 1.

Registry Key Access

·      Confirm the required registry keys exist and are accessible.

·      Check for registry hardening policies that may restrict access.

Manual Registry Test

·      Attempt to connect to the registry manually using the CPM account via regedit.

·      Note any access errors and investigate further.

CPM Configuration

·      Review the platform settings in PVWA for the affected account.

·      Ensure the password change method is set to use Windows Registry.

·      Confirm the registry path, value name, and value data are correctly defined.

·      Check the logon method and connection component used by CPM.

Restart Services

·      Restart the CPM service after making changes.

·      Optionally restart the Remote Registry service on the target machine.

 

 

L4 Transporter

Hi @Robert Stothard​,

Thank you very much for the CheckList, but still no luck.

 

Here are the test:

Registry Key Access OK

 

·   Confirm the required registry keys exist and are accessible. OK

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

DefaultPassword

Type: REG_SZ

 

·   Check for registry hardening policies that may restrict access. OK

No items in Computer Configuration → Windows Settings → Security Settings → Registry

 

Manual Registry Test OK

 

·   Attempt to connect to the registry manually using the CPM account via regedit. OK

it works. with user and password LogonAccount,the modification done on DefaultPassword also shows in the server

 

From CPM -- regedit -- File → Connect Network Registry -- go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon -- modify DefaultPassword

 

also works from CPM (if I logout from Connect Network Registry I get access denied)

reg query "\\IP\HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon" /v DefaultPassword

 

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

  DefaultPassword  REG_SZ  PASSWORDVAULE

·   Note any access errors and investigate further. NONE

----------------------------------------------------------------------------------------------------------------------------------------------------

CPM Configuration ???

 

·   Review the platform settings in PVWA for the affected account. OK

Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Value Name: DefaultPassword

Address: IP OF SERVER

 

·   Ensure the password change method is set to use Windows Registry. ???

password change method is set to use Windows Registry? I can't find it anywhere.

The Platform Name: Windows Server Local Accounts and one of the tabs inside the account says Windows Registry, inside Windows Registry I can add the Registry Path, Value Name and Address and logon account.

 

·   Confirm the registry path, value name, and value data are correctly defined.???

What is value data?

Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Value Name: DefaultPassword

Address: IP OF SERVER

 

·   Check the logon method and connection component used by CPM.???

How?

----------------------------------------------------------------------------------------------------------------------------------------------------

Permissions & Credentials OK

 

·   Confirm the CPM account has local administrator rights on the target server. OK

logon account is in administrators group: net localgroup administrators OK

 

·   Verify the CPM account credentials are correct and not expired. OK

Are correct, I can login in with the logon account without problem.

 

·   Ensure the CPM account is not locked out or disabled in Active Directory. OK

net user LogonAccount OK (Account active Yes)

----------------------------------------------------------------------------------------------------------------------------------------------------

Remote Registry Service OK

 

·   Check that the Remote Registry service is enabled and running on the target machine. OK

Get-Service -Name RemoteRegistry

Status  Name        DisplayName

------  ----        -----------

Running RemoteRegistry   Remote Registry

 

Set the Remote Registry service to Automatic startup type.

Set-Service -Name RemoteRegistry -StartupType Automatic

Start-Service -Name RemoteRegistry

----------------------------------------------------------------------------------------------------------------------------------------------------

Firewall & Network Access OK

 

·   Ensure TCP port 445 is open between the CPM and the target server. OK

from CPM:

Test-NetConnection -ComputerName IP -Port 445 also OK

Test-NetConnection -ComputerName IP -Port 135 also OK

telnet also OK from CPM for port Port 135 and port 445

 

·   Verify that Windows Firewall or any third-party firewall allows remote registry access. OK

Test-NetConnection -ComputerName IP -Port 445 also OK

Test-NetConnection -ComputerName IP -Port 135 also OK

telnet also OK from CPM for port Port 135 and port 445

 

·   Confirm there are no network segmentation rules blocking CPM access. OK

Test-NetConnection -ComputerName IP -Port 445 also OK

Test-NetConnection -ComputerName IP -Port 135 also OK

telnet also OK from CPM for port Port 135 and port 445

----------------------------------------------------------------------------------------------------------------------------------------------------

Group Policy Settings OK

 

·   Use gpedit.msc or RSOP.msc to check encryption and security layer policies. OK

gpedit.msc

Computer Configuration → Administrative Templates → System → Credentials Delegation: all set to Not Configured

Windows Components → Remote Desktop Services → Security all set to Not Configured

Network access: Sharing and security model for local accounts: Classic – local users authenticate as themselves

Computer Configuration → Windows Settings → Security Settings → Local Policies → Security Options everyhting not defiend

Computer Configuration → Administrative Templates → System → Credentials Delegation everyhting not defiend

 

·   Ensure UAC remote restrictions are disabled if applicable. OK

Get-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Name LocalAccountTokenFilterPolicy

LocalAccountTokenFilterPolicy : 1

----------------------------------------------------------------------------------------------------------------------------------------------------

 

L7 Applicator

Hi @ABDOU LAZEZ HUSSIEN EL SHEREDI​ 

 

Please check the DCOM and WMI security settings in the target server.

 

Check that logon account has Remote Launch and Remote Activation permissions set to "Allow" under DCOMand check that logon account has Remote Enable and Enable Account permissions under WMI.

 

Hope it helps !

 

 

Hi @Malhar Vora​ 

 

I checked and all are allowed. I have a feeling that the problem is from CyberArk side (manual connection via regedit in CPM works). I'm using these values in the Windows Registry Plugin

 

Registry Path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

Value Name: DefaultPassword

Address: IP OF SERVER

L7 Applicator

Hi @ABDOU LAZEZ HUSSIEN EL SHEREDI​ 

 

Okay, based on your manual test it further suggests the issue is within the Windows Registry plugin execution context or configuration parameters.

 

Can you try HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon

 

Also valdiate that the path is in the registry path parameter on the Account Details page is matching.

 

If the logon account is a domain account, the address can be the domain FQDN, but if it's failing then try using to the server's IP which might force the authentication path needed for the plugin.

 

Please enable the debug and share more information.

 

Hope it helps !

L4 Transporter

Hi @Malhar Vora​ ,

we fixed the problem by allowing ports TCP 49152–65535 in the server and in our firewalls.

When the Windows registry Plugin starts, the connection from CPM first uses tcp 135, but then it switches to TCP 49152–65535 to contact the server and change the registry.

Thank you very much for the support, mentioning WMI was a vital clue.

  • 1 accepted solution
  • 291 Views
  • 6 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!