About PSMUnmanagedSessionAccounts not modify in PrivateArk Client and not visible in PVWA

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

About PSMUnmanagedSessionAccounts not modify in PrivateArk Client and not visible in PVWA

L4 Transporter

Field_Content_versions_oct20__068Vy00000k6huHIAQ.pngWe are installing an additional PSM on PAM Cyberark to manage a new tenant. During installation, we encountered error ITATS048E, as shown in the attached image. We tried to follow the instructions in the article “https://community.cyberark.com/s/article/00003431”, but we cannot see the Safe on the PVWA, and on the Vault it appears to be uneditable, as shown in the attached image.

How can we resolve this?

 

Thanks in advance

Bye

Simona Vittori

 

Translated with DeepL.com (free version)Field_Content_versions_oct20__068Vy00000k6vHGIAY.png

1 accepted solution

Accepted Solutions

Basically, if you are using administrator account for installation

1- create new account (admin2) in vault with vault admins right

2- add new account (admin2) as the member of PSMMaster Group

3- Login using privateark and modify

A-Select PSMUnmanagedSessionAccounts safe

B-Right click and select open

C-Right click and select owners

D-Select administrator and select "Remove" on the right side

4- Update administrator user to add PSMMaster group membership

 

Retry the installation using administrator account again. should be good to go

View solution in original post

8 REPLIES 8

L4 Transporter

You need to add user who is installing the PSM in the PSMMaster Group.

L4 Transporter

You need to add user who is installing the PSM in the PSMMaster Group.

Basically, if you are using administrator account for installation

1- create new account (admin2) in vault with vault admins right

2- add new account (admin2) as the member of PSMMaster Group

3- Login using privateark and modify

A-Select PSMUnmanagedSessionAccounts safe

B-Right click and select open

C-Right click and select owners

D-Select administrator and select "Remove" on the right side

4- Update administrator user to add PSMMaster group membership

 

Retry the installation using administrator account again. should be good to go

Basically, if you are using administrator account for installation

1- create new account (admin2) in vault with vault admins right

2- add new account (admin2) as the member of PSMMaster Group

3- Login using privateark and modify

A-Select PSMUnmanagedSessionAccounts safe

B-Right click and select open

C-Right click and select owners

D-Select administrator and select "Remove" on the right side

4- Update administrator user to add PSMMaster group membership

 

Retry the installation using administrator account again. should be good to go

Basically, if you are using administrator account for installation

1- create new account (admin2) in vault with vault admins right

2- add new account (admin2) as the member of PSMMaster Group

3- Login using privateark and modify

A-Select PSMUnmanagedSessionAccounts safe

B-Right click and select open

C-Right click and select owners

D-Select administrator and select "Remove" on the right side

4- Update administrator user to add PSMMaster group membership

 

Retry the installation using administrator account again. should be good to go

Hi,

But do you mean the user who launches setup.exe to install the PSM component, or the user who logs in during the PSM installation, which in our case is the Vault Administrator?

 

Thanks in advance

bye

Simona

The user who logs into the vault for installation. The user who launces the set.exe is not part of the resolution as presumption is that you are logged on Windows machine using administrator user and running the exe the same user scope.

The user who logs into the vault for installation. The user who launces the set.exe is not part of the resolution as presumption is that you are logged on Windows machine using administrator user and running the exe the same user scope.

  • 1 accepted solution
  • 188 Views
  • 8 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!