SOLVEDSecurity Scope "All instances of the objects that are related to the assigned security roles" greyed out for a user having Full Administrator role

Status
Not open for further replies.
M
18
0
1
Security Scope "All instances of the objects that are related to the assigned security roles" greyed out for a user having a Full Administrator role.
I tried to turn it on because I was unable to turn on a feature in the Administration->Overview->Updates and Services->Features and then clicked on "Turn On" to find a message that would say "You do not have permission to enable features".

Greyed out permission.png


no permission.png
Solution
M
Here is what I tried and it worked. It helped me comply with the policy as well as correct the mistake that happened a long time back. The situation is as under:
An old IT tech installed the SCCM a long time back, apparently, earlier than 2015 using the domain administrator account.
Later a new service account, CMAdmin, was introduced by another IT tech to have all the actions with a specific identity and somehow comply with the new policy that no one can use the administrator account for any of such operational purposes.
I first viewed the current data in the table by"Select [AdminSID] from [dbo].[RBAC_Admins]", took note of the adminIDs in the SQL Studio, and customised the following script to suit my needs to swap adminSID
Therefore, the...
hth华体会体育全站

hth华体会体育全站

Forum Owner
Staff member
4,194
878
413
There are two known workarounds if the option 'All Instances Of The Objects That Are Related To The Assigned Security Roles' is grayed out. (pictured above)
  • Log into Windows as the original user who installed the SCCM server. This is the only user able to change the Security Scope option.
  • If all else fails, Microsoft advises rebuilding your SCCM environment.
Garth

Garth

Well-Known Member
Staff member
1,812
156
63
If you have MS Support I would contact them before rebuilding your site server.
OP
M
18
0
1
  • Thread Starter
  • #4
Thanks for the responses. Just wondering if there is a way to launch the management console with the original user id. like run as kind of thing?
Garth

Garth

Well-Known Member
Staff member
1,812
156
63
Assuming the user has not been deleted from AD then yes. Just logon with that account.
OP
M
18
0
1
  • Thread Starter
  • #6
Here is what I tried and it worked. It helped me comply with the policy as well as correct the mistake that happened a long time back. The situation is as under:
An old IT tech installed the SCCM a long time back, apparently, earlier than 2015 using the domain administrator account.
Later a new service account, CMAdmin, was introduced by another IT tech to have all the actions with a specific identity and somehow comply with the new policy that no one can use the administrator account for any of such operational purposes.
I first viewed the current data in the table by"Select [AdminSID] from [dbo].[RBAC_Admins]", took note of the adminIDs in the SQL Studio, and customised the following script to suit my needs to swap adminSID
Therefore, the following had to be done:

USE [CM_SITEID] /*SWAP SID*/ GO DECLARE @NEWSID varbinary(85) DECLARE @OLDSID varbinary(85) SET @NEWSID = (Select * from [dbo].[RBAC_Admins] WHERE [AdminID] = 16777**8) /*get sid of the new user that SCCMmust use, which is domain\cmadmin*/ SET @OLDSID = (Select [AdminSID] from [dbo].[RBAC_Admins] WHERE [AdminID] = 16777**7) /*get sid of the user that originally installed and configured SCCM with, that is domain\administrator */ UPDATE [dbo].[RBAC_Admins] SET [AdminSID] = CONVERT(varbinary(85), @NEWSID, 1) WHERE [AdminID] = 16777**7 UPDATE [dbo].[RBAC_Admins] SET [AdminSID] = CONVERT(varbinary(85), @OLDSID, 1) WHERE [AdminID] = 16777**8 GO

Attachments

  • table data.png
    table data.png
    15.5 KB · Views: 3
Last edited:
Solution
Status
Not open for further replies.

最新的文章

Forum statistics

Threads
5,723
Messages
22,305
Members
12,505
Latest member
Squuiid