Why look at Windows Activation for Web Application Proxies However, this option can’t be used for Web Application Proxy servers that are non-domain-joined and/or placed on a perimeter network (also commonly referred to as a DMZ network). If your Web Application Proxy servers are domain-joined, you can use Active Directory-based activation to take care of Windows activation. This blogpost assumes you’re running Web Application Proxies as non-domain-joined Server Core Windows Server 2016 installations. In this part of the series, we’ll look at best practices to handle Windows activation on non-domain-joined Web Application Proxy servers. In this series, labeled Hardening Hybrid Identity, we’re looking at hardening these implementations, using recommended practices. Most Microsoft-based Hybrid Identity implementations use Active Directory Federation Services (AD FS) Servers, Web Application Proxies and Azure AD Connect installations.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |