Export (0) Print
Expand All

Enable-ServerManagerStandardUserRemoting

Windows Server 2012 R2 and Windows 8.1

Updated: February 25, 2014

Applies To: Windows 8.1, Windows PowerShell 4.0, Windows Server 2012 R2

Enable-ServerManagerStandardUserRemoting

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.

Syntax

Parameter Set: Default
Enable-ServerManagerStandardUserRemoting [-User] <String[]> [-Force] [-Confirm] [-WhatIf] [ <CommonParameters>]




Detailed Description

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. The cmdlet must be run locally on the server that you are managing by using Server Manager. The cmdlet works by performing the following actions:

 ● Adds access rights for specified standard users to the root\cimv2 namespace on the local server (for access to role and feature inventory information).

 ● 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.

 ● Changes access rights in the Service Control Manager to allow specified standard users remote access to the status of services on the managed server.

This cmdlet does not provide standard users access to Best Practices Analyzer (BPA) results, or allow standard users to run BPA scans. 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.

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. The cmdlet provides access to other WMI providers in the root\cimv2 namespace, but only those providers that can be used by standard users. 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. Additionally, you should promptly run Disable-ServerManagerStandardUserRemoting to deny this access to users as soon as they no longer require it.

Parameters

-Force

Aliases

none

Required?

false

Position?

named

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-User<String[]>

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.


Aliases

none

Required?

true

Position?

1

Default Value

none

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-Confirm

Prompts you for confirmation before running the cmdlet.


Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

-WhatIf

Shows what would happen if the cmdlet runs. The cmdlet is not run.


Required?

false

Position?

named

Default Value

false

Accept Pipeline Input?

false

Accept Wildcard Characters?

false

<CommonParameters>

This cmdlet supports the common parameters: -Verbose, -Debug, -ErrorAction, -ErrorVariable, -OutBuffer, and -OutVariable. For more information, see    about_CommonParameters.

Inputs

The input type is the type of the objects that you can pipe to the cmdlet.

Outputs

The output type is the type of the objects that the cmdlet emits.

Examples

Example 1

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.


PS C:\> Enable-ServerManagerStandardUserRemoting -User JennyL

Example 2

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. The WhatIf parameter is added, meaning that the command actions are not carried out.


PS C:\> Enable-ServerManagerStandardUserRemoting -User JennyL -WhatIf

Example 3

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. The Confirm parameter is added, meaning that the command prompts for confirmation before performing the action.


PS C:\> Enable-ServerManagerStandardUserRemoting -User JennyL -Confirm

Related topics

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft