You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disables access for specified standard users to event, service, performance counter, and role and feature inventory data that is collected by Server Manager for a server.
15
-
This cmdlet performs the opposite action, for specified users, of the Enable-ServerManagerStandardUserRemoting cmdlet.
14
+
15
+
Disables access for specified standard users to event, service, performance counter, and role and
16
+
feature inventory data that is collected by Server Manager for a server. This cmdlet performs the
17
+
opposite action, for specified users, of the `Enable-ServerManagerStandardUserRemoting` cmdlet.
Disables access for one or more standard, non-Administrator users to event, service, performance counter, and role and feature inventory data for a server that you are managing by using Server Manager.
25
-
The cmdlet restores the default, administrator-only access to this data, and must be run locally on the server that is being managed by using Server Manager.
26
-
The cmdlet works by performing the following actions:
27
26
28
-
- Deletes access rights for specified standard users to the root\cimv2 namespace on the local server (for access to role and feature inventory information).
27
+
Disables access for one or more standard, non-Administrator users to event, service, performance
28
+
counter, and role and feature inventory data for a server that you are managing by using Server
29
+
Manager. The cmdlet restores the default, administrator-only access to this data, and must be run
30
+
locally on the server that is being managed by using Server Manager. The cmdlet works by performing
31
+
the following actions:
32
+
33
+
- Deletes access rights for specified standard users to the `root\cimv2` namespace on the local server
34
+
(for access to role and feature inventory information).
29
35
30
-
- Removes specified standard users from user groups (Remote Management Users, Event Log Readers, and Performance Log Readers) that allow remote access to event and performance counter logs on the local server.
36
+
- Removes specified standard users from user groups (Remote Management Users, Event Log Readers, and
37
+
Performance Log Readers) that allow remote access to event and performance counter logs on the
38
+
local server.
31
39
32
-
- Removes access rights in the Service Control Manager for specified standard users who have access to the status of services on the local server.
40
+
- Removes access rights in the Service Control Manager for specified standard users who have access
In the following example, the administrator disables access to event, performance counter, service status, and role and feature inventory data for a server that is being managed by using either a local or remote Server Manager console, and for which there is a standard user named JennyL.
51
+
In this example, the administrator disables access to event, performance counter, service
52
+
status, and role and feature inventory data for a server that is being managed by using either a
53
+
local or remote Server Manager console, and for which there is a standard user named `JennyL`.
In the following example, the administrator views the outcome of running a command to deny a standard user named JennyL access to event, performance counter, service status, and role and feature inventory data for a server that is being managed by using the Server Manager console running on either the local or a remote computer.
49
-
The `WhatIf` parameter is added, meaning that the command actions are not carried out.
61
+
In this example, the administrator views the outcome of running a command to deny a standard user
62
+
named `JennyL` access to event, performance counter, service status, and role and feature inventory
63
+
data for a server that is being managed by using the Server Manager console running on either the
64
+
local or a remote computer. The **WhatIf** parameter is added, meaning that the command actions are
In the following example, the administrator denies a standard user named JennyL access to event, performance counter, service status, and role and feature inventory data for a server that is being managed by using the Server Manager console running on either the local or a remote computer.
57
-
The `Confirm` parameter is added, meaning that the command prompts for confirmation before performing the action.
73
+
In this example, the administrator denies a standard user named `JennyL` access to event, performance
74
+
counter, service status, and role and feature inventory data for a server that is being managed by
75
+
using the Server Manager console running on either the local or a remote computer. The **Confirm**
76
+
parameter is added, meaning that the command prompts for confirmation before performing the action.
Specifies the user account name of a standard user who runs Server Manager, and no longer requires access to event, performance counter, service, and role and feature inventory data for a server that is being managed by using either a local or remote Server Manager console.
97
+
98
+
Specifies the user account name of a standard user who runs Server Manager and no longer requires
99
+
access to event, performance counter, service, and role and feature inventory data for a server that
100
+
is being managed by using either a local or remote Server Manager console.
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
148
+
149
+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
Provides one or more standard, non-Administrator users access to event, service, performance counter, and role and feature inventory data for a server that you are managing by using Server Manager.
14
+
15
+
Provides one or more standard, non-Administrator users access to event, service, performance
16
+
counter, and role and feature inventory data for a server that you are managing by using Server
Provides one or more standard, non-Administrator users access to event, service, performance counter, and role and feature inventory data for a server that you are managing, either locally or remotely, by using Server Manager.
24
-
The cmdlet must be run locally on the server that you are managing by using Server Manager.
25
-
The cmdlet works by performing the following actions:
26
26
27
-
- Adds access rights for specified standard users to the root\cimv2 namespace on the local server (for access to role and feature inventory information).
27
+
Provides one or more standard, non-Administrator users access to event, service, performance
28
+
counter, and role and feature inventory data for a server that you are managing, either locally or
29
+
remotely, by using Server Manager. The cmdlet must be run locally on the server that you are
30
+
managing by using Server Manager. The cmdlet works by performing the following actions:
31
+
32
+
- Adds access rights for specified standard users to the root\cimv2 namespace on the local server
33
+
(for access to role and feature inventory information).
28
34
29
-
- Adds specified standard users to required user groups (Remote Management Users, Event Log Readers, and Performance Log Readers) that allow remote access to event and performance counter logs on the managed server.
35
+
- Adds specified standard users to required user groups (Remote Management Users, Event Log Readers,
36
+
and Performance Log Readers) that allow remote access to event and performance counter logs on the
37
+
managed server.
30
38
31
-
- Changes access rights in the Service Control Manager to allow specified standard users remote access to the status of services on the managed server.
39
+
- Changes access rights in the Service Control Manager to allow specified standard users remote
40
+
access to the status of services on the managed server.
32
41
33
-
This cmdlet does not provide standard users access to bpa (BPA) results, or allow standard users to run BPA scans.
34
-
Aside from the preceding list of changes, this cmdlet provides no additional access that a standard user does not already have, by default, on managed servers.
42
+
This cmdlet does not provide standard users access to bpa (BPA) results, or allow standard users to
43
+
run BPA scans. Aside from the preceding list of changes, this cmdlet provides no additional access
44
+
that a standard user does not already have, by default, on managed servers.
35
45
36
-
Running this cmdlet has security implications for your network environment because it grants specified non-Administrator users access rights to information that, by default, is restricted to members of the Administrators group on the local computer.
37
-
The cmdlet provides access to other WMI providers in the root\cimv2 namespace, but only those providers that can be used by standard users.
38
-
We recommend that you run this cmdlet only when you must add a specific standard user to the users who require access to remote server data by using Server Manager.
39
-
Additionally, you should promptly run `Disable-ServerManagerStandardUserRemoting` to deny this access to users as soon as they no longer require it.
46
+
Running this cmdlet has security implications for your network environment because it grants
47
+
specified non-Administrator users access rights to information that, by default, is restricted to
48
+
members of the Administrators group on the local computer. The cmdlet provides access to other WMI
49
+
providers in the root\cimv2 namespace, but only those providers that can be used by standard users.
50
+
We recommend that you run this cmdlet only when you must add a specific standard user to the users
51
+
who require access to remote server data by using Server Manager. Additionally, you should promptly
52
+
run `Disable-ServerManagerStandardUserRemoting` to deny this access to users as soon as they no
In the following example, the administrator gives a standard user named JennyL access to event, performance counter, service status, and role and feature inventory data on a server that is being managed, either locally or remotely, by using Server Manager.
63
+
In this example, the administrator gives a standard user named `JennyL` access to event, performance
64
+
counter, service status, and role and feature inventory data on a server that is being managed,
65
+
either locally or remotely, by using Server Manager.
In the following example, the administrator views the outcome of running a command to give a standard user named JennyL access to event, performance counter, service status, and role and feature inventory data on a server that is being managed, either locally or remotely, by using Server Manager.
56
-
The `WhatIf` parameter is added, meaning that the command actions are not carried out.
73
+
In the following example, the administrator views the outcome of running a command to give a
74
+
standard user named JennyL access to event, performance counter, service status, and role and
75
+
feature inventory data on a server that is being managed, either locally or remotely, by using
76
+
Server Manager. The `WhatIf` parameter is added, meaning that the command actions are not carried
In the following example, the administrator gives a standard user named JennyL access to event, performance counter, service status, and role and feature inventory data on a server that is being managed, either locally or remotely, by using Server Manager.
64
-
The `Confirm` parameter is added, meaning that the command prompts for confirmation before performing the action.
85
+
In the following example, the administrator gives a standard user named `JennyL` access to event,
86
+
performance counter, service status, and role and feature inventory data on a server that is being
87
+
managed, either locally or remotely, by using Server Manager. The `Confirm` parameter is added,
88
+
meaning that the command prompts for confirmation before performing the action.
Specifies the user account name of a standard user who runs Server Manager, and requires access to event, performance counter, service, and role and feature inventory data for remote servers that are managed by using the local Server Manager console.
109
+
110
+
Specifies the user account name of a standard user who runs Server Manager, and requires access to
111
+
event, performance counter, service, and role and feature inventory data for remote servers that are
112
+
managed by using the local Server Manager console.
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable, -InformationAction, -InformationVariable, -OutVariable, -OutBuffer, -PipelineVariable, -Verbose, -WarningAction, and -WarningVariable. For more information, see [about_CommonParameters](https://go.microsoft.com/fwlink/?LinkID=113216).
159
+
160
+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
0 commit comments