1. System Deploy ADFS : th-adfs2012.mfalab3.com ADFS WAP : th-adfs2012wap.mfalab3.com RDWeb : th-rds.mfalab3.com A public IP for ADFS WAP points to ADFS/RDS as well 2. Setting on ADFS Create a Relying Parth Trust 3. Setting on ADFS WAP Create WAP Application, Add-WebApplicationProxyApplication -Name 'rdweb' -ExternalUrl 'https://th-rds.mfalab3.com/rdweb/' -BackendServerURL 'https://th-rds.mfalab3.com/rdweb/' -ExternalPreAuthentication ADFS -ADFSRelyingPartyName rdweb1 -ExternalCertificateThumbprint '67D438BDDBB455E53CA83D6F5DEC34CC546F711A' 4. Setting on RDS Important : Change authentication method to “Windows” https://social.technet.microsoft.com/Forums/office/en-US/999f56fa-a218-41b0-86ee-2845269d93ef/rdweb-authentication?forum=winserverTS 5. Setting on the Client Computers 6. See how it works
Here goes to add an OU for AAD Connect sync. 1. Open AAD Connect Synchronization Service Manager 2. Select on-prem AD connector and click Properties 3. Configure Directory Partitions -> Containers 4. Enter Password and click OK 5. Select an OU to be added, "AAD Connect" in this example 6. Create an user for test 7. A new user, "new_aad" created 8. "new_aad" not listed in O365 portal 9. Start AAD sync "Delta" 10. "new_aad" is synced/listed in O365 portal
Comments
Post a Comment