AAD Connect and WinRM on WAP

Copper Contributor

I'm looking at these WinRM on WAP prerequisites and not sure it's explained well, so have couple questions


1. When using Azure AD Connect to deploy Active Directory Federation Services or the Web Application Proxy

I am not using AAD Connect to deploy ADFS or WAP. Does this chapter still apply to an env with existing ADFS and WAP servers?


2. On the machine on which the wizard is running - is that the AAD Connect machine?


3. Set-Item WSMan:\localhost\Client\TrustedHosts –Value <DMZServerFQDN> -Force –Concatenate

<DMZServerFQDN> is the WAP server?


4. On the target machine (WAP machine) - does this need to be done on each WAP server?

1 Reply
best response confirmed by Michele Casazza (Copper Contributor)

@Michele Casazza  Hello 


1. If you are not going to deploy ADFS or WAP in your environment then this does not apply.

2. Yes, the machine running the wizard would be your AAD Connect server.

3. Yes, That is referring to the name of the WAP server but if you are not deploying ADFS and WAP no need to worry about this. 

4. Yes if you are deploying ADFS with WAP then you would need to do the action on all WAP servers


These steps are to ensure that the AAD connect wizard will be able to execute the PowerShell cmdlets necessary to deploy ADFS and WAP servers.


Hope that helps!