More actions
No edit summary |
No edit summary |
||
| Line 31: | Line 31: | ||
Windows Server Desktop was chosen because [[Authentication: Microsoft Entra ID Connect]] and [[Authentication: Microsoft NPS]] does not support Linux or Windows Server Core. It was easier to run these services from one device and have one point of authentication services in addition to [[Authentication: Microsoft Active Directory]]. The following roles and features are running on this server: | Windows Server Desktop was chosen because [[Authentication: Microsoft Entra ID Connect]] and [[Authentication: Microsoft NPS]] does not support Linux or Windows Server Core. It was easier to run these services from one device and have one point of authentication services in addition to [[Authentication: Microsoft Active Directory]]. The following roles and features are running on this server: | ||
* [[Authentication: Microsoft Entra | * [[Authentication:Microsoft Entra Cloud Sync]] | ||
* [[Authentication: Microsoft NPS]] | * [[Authentication:Microsoft NPS]] | ||
== Network Diagram == | == Network Diagram == | ||
Revision as of 23:06, 29 May 2024
History
Servers:SAD-AUTH01 was built on 5/10/22 to assist in Authentication: Microsoft NPS RADIUS authentication and run the Authentication: Microsoft Entra ID Connect agent.
Authentication: Microsoft Entra ID Connect is running on this server to enable syncing between on-prem Authentication: Microsoft Active Directory and Authentication: Microsoft Entra ID Connect, a component of Cloud: Microsoft Azure.
Finally, the Authentication: Microsoft NPS server role is installed and setup to enable RADIUS authentication to Hardware: SAD-HME-FW01 for Network: Road Warrior VPN to enable a secure connection back to sysadminafterdark networks.
Purpose
Windows Server Desktop was chosen because Authentication: Microsoft Entra ID Connect and Authentication: Microsoft NPS does not support Linux or Windows Server Core. It was easier to run these services from one device and have one point of authentication services in addition to Authentication: Microsoft Active Directory. The following roles and features are running on this server:
Network Diagram
Status
This server has been staged and placed into sysadminafterdark production. There are no plans to replace or upgrade this server until Windows Server 2022 goes end of life on October 14, 2031.