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
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).
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,
The `Get-WindowsFeature` cmdlet gets information about features that are both available for installation and already installed on a computer that is running Windows Server or an offline virtual hard disk (VHD) that is running Windows Server.
26
+
27
+
The `Get-WindowsFeature` cmdlet gets information about features that are both available for
28
+
installation and already installed on a computer that is running Windows Server, or an offline
29
+
virtual hard disk (VHD) that is running Windows Server.
This example gets a list of features that is available and installed on the target computer named Server1.
34
-
The credentials for user user1 in the Contoso.com domain, a user who has Administrator rights on Server1, are provided.
39
+
This example gets a list of features that are available and installed on the target computer named `Server1`.
40
+
The credentials for user `user1` in the Contoso.com domain, a user who has Administrator rights on `Server1`, are provided.
35
41
36
42
### Example 2
43
+
37
44
```powershell
38
45
Get-WindowsFeature -Vhd D:\ps-test\vhd1.vhd
39
46
```
40
47
41
-
This example returns a list of features that is available and installed on the specified offline VHD located at D:\ps-test\vhd1.vhd.
48
+
This example returns a list of features that are available and installed on the specified offline
49
+
VHD located at `D:\ps-test\vhd1.vhd`.
42
50
43
51
### Example 3
52
+
44
53
```powershell
45
54
Get-WindowsFeature -Name AD*, Web*
46
55
```
47
56
48
-
This example returns a list of available and installed features that have a command ID starting with AD or Web.
57
+
This example returns a list of available and installed features that have a command ID starting with
58
+
`AD` or `Web`.
49
59
50
60
### Example 4
61
+
51
62
```powershell
52
63
Get-WindowsFeature -ComputerName Server01 | Where Installed
53
64
```
54
65
55
-
This example returns a list of features installed on a specified server, Server01.
66
+
This example returns a list of features installed on a specified server, `Server01`.
56
67
57
68
### Example 5
69
+
58
70
```powershell
59
71
Get-WindowsFeature -ComputerName Server01 | Where InstallState -Eq Removed
60
72
```
61
73
62
-
This example returns a list of features on a specified server, Server01, that have installation files removed from the local side-by-side store, and require an external file source for installation.
74
+
This example returns a list of features on a specified server, `Server01`, that have installation
75
+
files removed from the local side-by-side store and require an external file source for
76
+
installation.
63
77
64
78
## PARAMETERS
65
79
66
80
### -ComputerName
67
-
Gets the list of available features from the specified remote computer that is running Windows Server.
68
-
The parameter accepts only one computer name.
69
-
If this parameter is not added, or no computer name is specified, the default target is the local computer.
70
-
Valid values for the parameter include a NetBIOS name, an IP address, or a fully qualified domain name of a remote computer.
71
81
72
-
To use a remote computer's IP address as the value of this parameter, your command must include the `Credential` parameter.
73
-
The computer must either be configured for HTTPS transport, or the IP address of the remote computer must be included in the WinRM TrustedHosts list on the local computer.
74
-
For information about adding a computer name to the WinRM TrustedHosts list, see "How to Add a Computer to the Trusted Host List" in [about_Remote_Troubleshooting](https://go.microsoft.com/fwlink/p/?LinkID=135188).
82
+
Gets the list of available features from the specified remote computer that is running Windows
83
+
Server. The parameter accepts only one computer name. If this parameter is not added, or no computer
84
+
name is specified, the default target is the local computer. Valid values for the parameter include
85
+
a NetBIOS name, an IP address, or a fully qualified domain name of a remote computer.
86
+
87
+
To use a remote computer's IP address as the value of this parameter, your command must include the
88
+
**Credential** parameter. The computer must either be configured for HTTPS transport, or the IP
89
+
address of the remote computer must be included in the WinRM TrustedHosts list on the local
90
+
computer. For information about adding a computer name to the WinRM TrustedHosts list, see "How to
The path can either point to a VHD file, or to a location on which the VHD is already mounted by using Deployment Image Servicing and Management (DISM) tools.
147
165
148
-
The VHD can be on a local disk on the target computer, or on a network shared folder.
149
-
If the VHD is in a network shared folder, then the value of this parameter is a UNC path to the VHD.
150
-
In this case, the computer account of the computer that you are using to mount the VHD must have read and write permissions (Read/Write permissions in the File Sharing dialog box, or Full Control on the Security tab of the folder Properties dialog box) on the shared folder, or the VHD will not be accessible.
151
-
Local loopback UNC paths are not supported.
152
-
Use either of the following formats for the computer account: DOMAIN\SERVERNAME$ or SERVERNAME$.
166
+
Specifies the path to an offline VHD. The path can either point to a VHD file, or to a location on
167
+
which the VHD is already mounted by using Deployment Image Servicing and Management (DISM) tools.
153
168
154
-
Add the `ComputerName` parameter to specify the target computer you want to use to mount the VHD.
155
-
If the `ComputerName` parameter is not specified, then the local computer is used.
156
-
The computer that you are using to mount the VHD must be running Windows Server.
157
-
Any local path, such as D:\myFolder, that is specified by using this parameter is always relative to the target computer.
169
+
The VHD can be on a local disk on the target computer or on a network shared folder. If the VHD is
170
+
in a network shared folder, then the value of this parameter is a UNC path to the VHD. In this case,
171
+
the computer account of the computer that you are using to mount the VHD must have read and write
172
+
permissions (Read/Write permissions in the File Sharing dialog box or Full Control on the Security
173
+
tab of the folder Properties dialog box) on the shared folder or the VHD will not be accessible.
174
+
Local loopback UNC paths are not supported. Use either of the following formats for the computer
175
+
account: DOMAIN\SERVERNAME$ or SERVERNAME$.
176
+
177
+
Add the **ComputerName** parameter to specify the target computer you want to use to mount the VHD.
178
+
If the **ComputerName** parameter is not specified, then the local computer is used. The computer
179
+
that you are using to mount the VHD must be running Windows Server. Any local path, such as
180
+
`D:\myFolder`, that is specified by using this parameter is always relative to the target computer.
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).
195
+
196
+
This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable,
0 commit comments