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
Copy file name to clipboardExpand all lines: articles/active-directory/hybrid/how-to-connect-install-prerequisites.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -156,17 +156,17 @@ Prior to version 1.1.614.0, Azure AD Connect by default uses TLS 1.0 for encrypt
156
156
When using Azure AD Connect to deploy Active Directory Federation Services or the Web Application Proxy, check these requirements:
157
157
158
158
* If the target server is domain joined, then ensure that Windows Remote Managed is enabled
159
-
* In an elevated PSH command window, use command `Enable-PSRemoting –force`
159
+
* In an elevated PowerShell command window, use command `Enable-PSRemoting –force`
160
160
* If the target server is a non-domain joined WAP machine, then there are a couple of additional requirements
161
161
* On the target machine (WAP machine):
162
162
* Ensure the winrm (Windows Remote Management / WS-Management) service is running via the Services snap-in
163
-
* In an elevated PSH command window, use command `Enable-PSRemoting –force`
163
+
* In an elevated PowerShell command window, use command `Enable-PSRemoting –force`
164
164
* On the machine on which the wizard is running (if the target machine is non-domain joined or untrusted domain):
165
-
* In an elevated PSH command window, use the command `Set-Item WSMan:\localhost\Client\TrustedHosts –Value <DMZServerFQDN> -Force –Concatenate`
165
+
* In an elevated PowerShell command window, use the command `Set-Item WSMan:\localhost\Client\TrustedHosts –Value <DMZServerFQDN> -Force –Concatenate`
166
166
* In Server Manager:
167
167
* add DMZ WAP host to machine pool (server manager -> Manage -> Add Servers...use DNS tab)
168
168
* Server Manager All Servers tab: right click WAP server and choose Manage As..., enter local (not domain) creds for the WAP machine
169
-
* To validate remote PSH connectivity, in the Server Manager All Servers tab: right click WAP server and choose Windows PowerShell. A remote PSH session should open to ensure remote PowerShell sessions can be established.
169
+
* To validate remote PowerShell connectivity, in the Server Manager All Servers tab: right click WAP server and choose Windows PowerShell. A remote PowerShell session should open to ensure remote PowerShell sessions can be established.
170
170
171
171
### TLS/SSL Certificate Requirements
172
172
* It’s strongly recommended to use the same TLS/SSL certificate across all nodes of your AD FS farm and all Web Application proxy servers.
0 commit comments