Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Assign SRM permissions using SRM MOB (78292)

Last Updated: 4/15/2020Categories: How toTotal Views: 5659Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The Site Recovery Manager UI fails to find domain users with the search function when trying to add permissions for SRM.
You may see the error  "Failed to connect to vCenter Server at <VC location>:443/sdk. Reason: <VC location>:443/sdk invocation failed with "java.net.SocketTimeoutException: Read timed out" Read timed out"

Purpose

This article describes how to assign SRM permissions using SRM Managed Object Browser {MOB}.

Resolution

Stage 1: Examine current account permissions

Ensure that the Site Recovery Manager Managed Object Browser is enabled.

Open the SRM MOB

For Windows-based SRM use https://<SRM-fqdn|IP>:9086/mob where 9086 is the default port that the SRM service is listening.

For the SRM virtual appliance use https://<SRM-fqdn|IP>:443/mob.

Log into MOB using vCenter administrator credentials.

Review the current permissions by navigating to the permissions section of the MOB.

In the Properties table, select the permission link.

Look for the specific user you are concerned with. Note the roleId value set for that user.NOTE: The entity is of type "DrServiceInstance" and the roleId is "-1"

There are lots or roleIds defined in vCenter. Identify which roleId you need to set for a specific user:

Connect to ihttps://<vCenter FQDN or IP>/mob

Under the Properties table, select the content link

Select the AuthorizationManager link

Select the roleList link

You see a list of all vCenter roles with roleIDs, These roles match those visible in the vCenter, Administration, Role UI.

Note the roleID value matching the role you want the user to possess.

Note: In this example, SRM specific roles could be seen with roleIds range [1101, 1106] This may not be the case for your environment as it depends on which other solutions are installed in your environment.

Stage 2: Create a new user

Return to the SRM MOB home page.

Select the content link by DrServiceInstanceContent as shown..

Select the DrAuthorizationManager link.

Select the DrSetEntityPermissions link to invoke that method.

The following dialog box will popup:

Modify the items In this dialog box to suit your need:

Set the MOID in both the entity and permission sections to be the same. If working with a global permission set the MOID to "DrServiceInstance" as seen for the other users in step 4 of Stage 1.

Set the principle in the permission section to the account you are setting the permissions on in the DOMAIN\User format.

If the principle is a domain group, set the group tag to true, else leave it as false.

If all child entities have the same permissions, set the propagate flag to true. For example, if you set permission for SRM root object “DrServiceInstance” then this flag must be true so this permission will be global and applied on all SRM objects like Protection Group, Recovery Plans and folders. This matches the meaning of the same parameter seen through the disaster recovery UI.

Set roleId to the integer number representing desired the role (as identified in step 5 of Stage 1). Such as, ‘Administrators’, ‘ReadOnly-Access’ and so forth. Example:, ‘-1’ represents the vCenter Administrator role with full access rights and ‘1101’ represents the SRM Administrator Role.

When finished, select the Invoke Method link.

If the result is successful ti will display the message "Method Invocation Result: void"

Example:

How to set SRM global permission for a Recovery Admin user:
We will use principal VSPHERE.LOCAL\nonadminuser for which we want to set a global permission with “SRM Recovery Administrator” role which means this user will be able to run Recovery Plans only and won’t be able to perform any configuration changes.

For this purpose we need to set the following parameters for

ManagedObjectReference:DrManagedEntity method:
<entity type="DrManagedEntity">DrServiceInstance</entity>

DrSetEntityPermissions method:

<entity type="DrManagedEntity">DrServiceInstance</entity>
<principal>VSPHERE.LOCAL\nonadminuser</principal>
<group>false</group>
<roleId>1105</roleId>
<propagate>true</propagate>

Or as shown below:

As described above this can be confirmed in the SRM permissions pane of the UI:

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
从 BMC 禁用 Ethernet Over USB 设备后，Web Client 中未正确显示状态 (78309)

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vRealize Operations Manager 8.1 でアップグレード プロセスの再起動フェーズを実行した後、ノードにアクセスできない (78302)

KB
•
SR-IOV シナリオで Intel NIC 82599/X520 を使用している場合の VLAN トランク モードの VLAN インターフェイス間の問題 (78245)

KB
•
本地用户帐户在升级 vCenter Server Appliance 后消失 (78148)

Results 1-5 of 5

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Site Recovery Manager

VMware Site Recovery Manager

Related Versions:

VMware vCenter Site Recovery Manager 8.x

Take Our Survey

Support Assistant