Skip to content

Commit 0467b28

Browse files
sdwheelerchasewilson
sdwheeler
and
chasewilson
authored
Fixes MicrosoftDocs#5281 - fix broken URLs and remove locale (MicrosoftDocs#5286)
* Formatting updates and link updates * Fixes MicrosoftDocs#5281 - fix broken URLs and remove locale * Updates for links and formatting * Fixes MicrosoftDocs#5281 - fix broken URLs and remove locale * fix typos and build warnings Co-authored-by: Chase Wilson <31453523+chasewilson@users.noreply.github.com>
1 parent 21b34e8 commit 0467b28

File tree

32 files changed

+2353
-939
lines changed

32 files changed

+2353
-939
lines changed

‎reference/6/Microsoft.PowerShell.Core/About/about_Remote_Requirements.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -231,7 +231,7 @@ installing a certificate on the target server. The certificate must have a
231231
CN name that matches the hostname, is not expired or revoked. A self-signed
232232
certificate may be used for testing purposes.
233233

234-
See [How To: Configure WINRM for HTTPS](https://support.microsoft.com/en-us/help/2019527/how-to-configure-winrm-for-https)
234+
See [How To: Configure WINRM for HTTPS](https://support.microsoft.com/help/2019527/how-to-configure-winrm-for-https)
235235
for additonal details.
236236

237237
The following command, run from an elevated command prompt, will configure the
@@ -272,7 +272,7 @@ $session = New-PSSession -Computer <hostname> -Credential $cred `
272272
> administrators, other than the built in administrator, to connect using NTLM.
273273
> Refer to the LocalAccountTokenFilterPolicy registry setting under Negotiate
274274
> Authentication in
275-
> [Authentication for Remote Connections](https://msdn.microsoft.com/en-us/library/aa384295(v=vs.85).aspx)
275+
> [Authentication for Remote Connections](/windows/win32/winrm/authentication-for-remote-connections)
276276
277277
## SEE ALSO
278278

‎reference/7.0/Microsoft.PowerShell.Core/About/about_Remote_Requirements.md‎

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,8 @@ using Microsoft .NET Framework methods to retrieve the objects. They do not
2525
use the PowerShell remoting infrastructure. The requirements in this
2626
document do not apply to these cmdlets.
2727

28-
To find the cmdlets that have a ComputerName parameter but do not use PowerShell remoting, read the description of the ComputerName parameter of the
28+
To find the cmdlets that have a ComputerName parameter but do not use
29+
PowerShell remoting, read the description of the ComputerName parameter of the
2930
cmdlets.
3031

3132
## SYSTEM REQUIREMENTS
@@ -231,7 +232,7 @@ installing a certificate on the target server. The certificate must have a
231232
CN name that matches the hostname, is not expired or revoked. A self-signed
232233
certificate may be used for testing purposes.
233234

234-
See [How To: Configure WINRM for HTTPS](https://support.microsoft.com/en-us/help/2019527/how-to-configure-winrm-for-https)
235+
See [How To: Configure WINRM for HTTPS](https://support.microsoft.com/help/2019527/how-to-configure-winrm-for-https)
235236
for additonal details.
236237

237238
The following command, run from an elevated command prompt, will configure the
@@ -272,7 +273,7 @@ $session = New-PSSession -Computer <hostname> -Credential $cred `
272273
> administrators, other than the built in administrator, to connect using NTLM.
273274
> Refer to the LocalAccountTokenFilterPolicy registry setting under Negotiate
274275
> Authentication in
275-
> [Authentication for Remote Connections](https://msdn.microsoft.com/en-us/library/aa384295(v=vs.85).aspx)
276+
> [Authentication for Remote Connections](/windows/win32/winrm/authentication-for-remote-connections)
276277
277278
## SEE ALSO
278279

‎reference/docs-conceptual/components/web-access/troubleshooting-access-problems-in-windows-powershell-web-access.md‎

Lines changed: 66 additions & 66 deletions
Original file line numberDiff line numberDiff line change
@@ -19,35 +19,40 @@ and includes suggestions for resolving the problems.
1919

2020
Failure could occur because of any of the following.
2121

22-
- An authorization rule that allows the user access to the computer, or a specific session configuration on the remote computer, does not exist.
22+
- An authorization rule that allows the user access to the computer, or a specific session
23+
configuration on the remote computer, does not exist.
2324

24-
Windows PowerShell Web Access security is restrictive; users must be granted explicit access to remote computers by using authorization rules.
25+
Windows PowerShell Web Access security is restrictive; users must be granted explicit access to
26+
remote computers by using authorization rules.
2527

26-
For more information about creating authorization rules, see [Authorization Rules and Security Features of Windows PowerShell Web Access](authorization-rules-and-security-features-of-windows-powershell-web-access.md).
28+
For more information about creating authorization rules, see
29+
[Authorization Rules and Security Features of Windows PowerShell Web Access](authorization-rules-and-security-features-of-windows-powershell-web-access.md).
2730

28-
- The user does not have authorized access to the destination computer. This is determined by access control lists (ACLs).
31+
- The user does not have authorized access to the destination computer. This is determined by access
32+
control lists (ACLs).
2933

30-
For more information, see [Signing in to Windows PowerShell Web Access](use-the-web-based-windows-powershell-console.md#signing-in-to-windows-powershell-web-access), or the Windows PowerShell Team Blog.
34+
For more information, see
35+
[Signing in to Windows PowerShell Web Access](use-the-web-based-windows-powershell-console.md#signing-in-to-windows-powershell-web-access),
36+
or the Windows PowerShell Team Blog.
3137

3238
- Windows PowerShell remote management might not be enabled on the destination computer.
3339

3440
Verify remote management is enabled on the computer to which the user is trying to connect.
3541

36-
For more information, see [How to Configure Your Computer for Remoting](/powershell/module/microsoft.powershell.core/about/about_remote_requirements#how-to-configure-your-computer-for-remoting).
42+
For more information, see
43+
[How to Configure Your Computer for Remoting](/powershell/module/microsoft.powershell.core/about/about_remote_requirements#how-to-configure-your-computer-for-remoting).
3744

3845
## Internal Server Error
3946

40-
When users try to sign in to Windows PowerShell Web Access in an Internet
41-
Explorer window, they are shown an **Internal Server Error** page,
42-
or *Internet Explorer* stops responding.
47+
When users try to sign in to Windows PowerShell Web Access in an Internet Explorer window, they are
48+
shown an **Internal Server Error** page, or *Internet Explorer* stops responding.
4349

4450
This issue is specific to Internet Explorer.
4551

4652
### Possible cause
4753

48-
This can occur for users who have signed in with a domain name that contains
49-
Chinese characters, or if one or more Chinese characters are part of the
50-
gateway server name.
54+
This can occur for users who have signed in with a domain name that contains Chinese characters, or
55+
if one or more Chinese characters are part of the gateway server name.
5156

5257
#### Workaround
5358

@@ -60,106 +65,101 @@ gateway server name.
6065
1. Disable automatic proxy configuration in Internet Explorer 10.
6166
1. Click **Tools**, and then click **Internet Options**.
6267
1. In the **Internet Options** dialog box, on the **Connections** tab, click **LAN settings**.
63-
1. Clear the **Automatically detect settings** check box. Click **OK**, and then click **OK** again to close the *Internet Options* dialog box.
68+
1. Clear the **Automatically detect settings** check box. Click **OK**, and then click **OK**
69+
again to close the *Internet Options* dialog box.
6470

6571
## Cannot connect to a remote workgroup computer
6672

67-
If the destination computer is a member of a workgroup, use the following syntax to provide your user name and sign in to the computer: `<workgroup_name>\<user_name>`
73+
If the destination computer is a member of a workgroup, use the following syntax to provide your
74+
user name and sign in to the computer: `<workgroup_name>\<user_name>`
6875

6976
## Cannot find Web Server (IIS) management tools, even though the role was installed
7077

71-
If you installed Windows PowerShell Web Access by using the
72-
`Install-WindowsFeature` cmdlet,
73-
management tools are not installed unless the `-IncludeManagementTools`
74-
parameter is added to the cmdlet.
78+
If you installed Windows PowerShell Web Access by using the `Install-WindowsFeature` cmdlet,
79+
management tools are not installed unless the **IncludeManagementTools** parameter is added to the
80+
cmdlet.
7581

76-
For an example, see [To install Windows PowerShell Web Access by using Windows PowerShell cmdlets](install-and-use-windows-powershell-web-access.md#to-install-windows-powershell-web-access-by-using-windows-powershell-cmdlets).
82+
For an example, see
83+
[To install Windows PowerShell Web Access by using Windows PowerShell cmdlets](install-and-use-windows-powershell-web-access.md#to-install-windows-powershell-web-access-by-using-windows-powershell-cmdlets).
7784

78-
You can add the IIS Manager console,
79-
and other IIS management tools that you need,
80-
by selecting the tools in an **Add Roles and Features Wizard** session that
81-
is targeted at the gateway server.
82-
The Add Roles and Features Wizard is opened from within Server Manager.
85+
You can add the IIS Manager console, and other IIS management tools that you need, by selecting the
86+
tools in an **Add Roles and Features Wizard** session that is targeted at the gateway server. The
87+
Add Roles and Features Wizard is opened from within Server Manager.
8388

8489
## Windows PowerShell Web Access website is not accessible
8590

86-
If Enhanced Security Configuration is enabled in Internet Explorer (IE ESC),
87-
you can add the Windows PowerShell Web Access website to the list of trusted
88-
sites.
91+
If Enhanced Security Configuration is enabled in Internet Explorer (IE ESC), you can add the Windows
92+
PowerShell Web Access website to the list of trusted sites.
8993

90-
A less recommended approach, due to security risks, is to disable IE ESC.
91-
You can disable IE ESC in the Properties tile on the Local Server page in
92-
Server Manager.
94+
A less recommended approach, due to security risks, is to disable IE ESC. You can disable IE ESC in
95+
the Properties tile on the Local Server page in Server Manager.
9396

9497
## An authorization failure occurred. Verify that you are authorized to connect to the destination computer.
9598

96-
The above error message is displayed while trying to connect when the
97-
gateway server is the destination computer, and is also in a workgroup.
99+
The above error message is displayed while trying to connect when the gateway server is the
100+
destination computer, and is also in a workgroup.
98101

99-
When the gateway server is also the destination server,
100-
and it is in a workgroup, specify the user name, computer name,
101-
and user group name.
102-
Do not use a dot (.) by itself to represent the computer name.
102+
When the gateway server is also the destination server, and it is in a workgroup, specify the user
103+
name, computer name, and user group name. Do not use a dot (.) by itself to represent the computer
104+
name.
103105

104106
### Scenarios and proper values
105107

106108
#### All cases
107109

108-
Parameter | Value
109-
-- | --
110-
UserName | Server\_name\\user\_name<br/>Localhost\\user\_name<br/>.\\user\_name
111-
UserGroup | Server\_name\\user\_group<br/>Localhost\\user\_group<br/>.\\user\_group
112-
ComputerGroup | Server\_name\\computer\_group<br/>Localhost\\computer\_group<br/>.\\computer\_group
110+
Parameter | Value
111+
------------- | -----------------------------------------------------------------------------------
112+
UserName | `Server_name\user_name`<br/>`Localhost\user_name`<br/>`.\user_name`
113+
UserGroup | `Server_name\user_group`<br/>`Localhost\user_group`<br/>`.\user_group`
114+
ComputerGroup | `Server_name\computer_group`<br/>`Localhost\computer_group`<br/>`.\computer_group`
113115

114116
#### Gateway server is in a domain
115117

116-
Parameter | Value
117-
-- | --
118+
Parameter | Value
119+
------------ | ----------------------------------------------------
118120
ComputerName | Fully qualified name of gateway server, or Localhost
119121

120122
#### Gateway server is in a workgroup
121123

122-
Parameter | Value
123-
-- | --
124+
Parameter | Value
125+
------------ | -----------
124126
ComputerName | Server name
125127

126128
### Gateway credentials
127129

128130
Sign in to a gateway server as target computer by using credentials
129131
formatted as one of the following.
130132

131-
- Server\_name\\user\_name
132-
- Localhost\\user\_name
133-
- .\\user\_name
133+
- `Server_name\user_name`
134+
- `Localhost\user_name`
135+
- `.\user_name`
134136

135137
## A security identifier (SID) is displayed in an authorization rule
136138

137-
A security identifier (SID) is displayed in an authorization rule instead
138-
of the syntax user\_name/computer\_name.
139+
A security identifier (SID) is displayed in an authorization rule instead of the syntax
140+
`user_name/computer_name`.
139141

140-
Either the rule is no longer valid, or the Active Directory Domain Services
141-
query failed.
142-
An authorization rule is usually not valid in scenarios where the gateway
143-
server was at one time in a workgroup, but was later joined to a domain
142+
Either the rule is no longer valid, or the Active Directory Domain Services query failed. An
143+
authorization rule is usually not valid in scenarios where the gateway server was at one time in a
144+
workgroup, but was later joined to a domain
144145

145146
## Cannot sign in with rule as an IPv6 address with a domain
146147

147-
Cannot sign in to a target computer that has been specified in authorization
148-
rules as an IPv6 address with a domain.
148+
Cannot sign in to a target computer that has been specified in authorization rules as an IPv6
149+
address with a domain.
149150

150151
Authorization rules do not support an IPv6 address in form of a domain name.
151152

152-
To specify a destination computer by using an IPv6 address,
153-
use the original IPv6 address (that contains colons) in the authorization
154-
rule.
155-
Both domain and numerical (with colons) IPv6 addresses are supported as the
156-
target computer name on the Windows PowerShell Web Access sign-in page,
157-
but not in authorization rules.
153+
To specify a destination computer by using an IPv6 address, use the original IPv6 address (that
154+
contains colons) in the authorization rule. Both domain and numerical (with colons) IPv6 addresses
155+
are supported as the target computer name on the Windows PowerShell Web Access sign-in page, but not
156+
in authorization rules.
158157

159-
For more information about IPv6 addresses, see [How IPv6 Works](https://technet.microsoft.com/library/cc781672(v=ws.10).aspx).
158+
For more information about IPv6 addresses, see
159+
[How IPv6 Works](/previous-versions/windows/it-pro/windows-server-2003/cc781672(v=ws.10)).
160160

161161
## See Also
162162

163-
- [Authorization Rules and Security Features of Windows PowerShell Web Access](https://technet.microsoft.com/en-us/library/dn282394(v=ws.11).aspx)
164-
- [Use the Web-based Windows PowerShell Console](https://technet.microsoft.com/en-us/library/hh831417(v=ws.11).aspx)
165-
- [about_Remote_Requirements](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/about/about_remote_requirements)
163+
- [Authorization Rules and Security Features of Windows PowerShell Web Access](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/dn282394(v=ws.11))
164+
- [Use the Web-based Windows PowerShell Console](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/hh831417(v=ws.11))
165+
- [about_Remote_Requirements](/powershell/module/microsoft.powershell.core/about/about_remote_requirements)

0 commit comments

Comments
 (0)