OpenEdge Admin Service Freezes Windows Server when set to Automatic start and Log on set to Domain user

OpenEdge Admin Service Freezes Windows Server when set to Automatic start and Log on set to Domain user
A Domain user account is configured to start the AdminServer using Windows Services
Remote login to the Windows virtual machine is refused
Service Control Manager System EventLog Error 7001 reports:

The Domain account used to start the AdminService is set to a separate group role to use Windows Active Directory
All the Windows local Policies are granted as described in Article:

•  How To configure windows to Start A Broker Under a Windows User?

Setting up the AdminService to start with log on set to Local System account works without any issues
Setting up the AdminService to start with log on set to the Domain account with Automatic(Delayed Start) works without any issues

The OpenEdge AdminServer (Service) start sequence within the first 3 Services (Alphabetical listing) in the Windows Services.  Dependency services need to be started first in order to authorise and authenticate the Domain user before windows can come up successfully.  While AdminServer is starting, it causes other necessary services in the queue to wait until AdminServer successfully completes it starting process which causes windows to hang.  This prevents users from being able to log in to the Virtual Windows Server using Remote Desktop.

When using the standard 'Local System Account' account to start the AdminService, this is not needed as the local system account is always reachable.

The Services that raised dependency errors are listed below.  

• Each of these Windows Services have dependencies on other windows services.  
• They may overlap each other for dependent services.  
• Depending on Windows releases and how the Domain architecture and authentication are configured, the list provided below covers the most common dependent services

1. The Network Interface failed to initialise properly due to a device attached to the system is not functioning, which needs to be removed or fixed.

2.  Set the AdminService to: Automatic (Delayed Start) 

This will cause the AdminService to delay startup whenever the system reboots, allowing additional time for other services to start first.

• [WIN+R]: services.msc
• OpenEdge AdminService > Properties > General [tab]:
• Startup type: Automatic (Delayed Start)

3. Add Service Dependencies specifically for the OpenEdge AdminService (service)

A. Dependent Services, once identified for the specific Windows environment can be added with elevated rights from a command shell.
Example:
B. Service dependencies can be added to the Registry (with the usual caveats)

1.  Export the registry key for the AdminServer: 2.  Download the attached registry key export: [ AdminService.reg.txt ]
3.  Add the "DependOnService" string entry with the exact hex value to your exported AdminService registry key in a text editor (Notepad)
4.  Reapply the AdminService keys to the registry by double clicking on your updated .reg file
5.  Once the registry is set with the service dependencies, these dependent services can be reviewed from services.msc for the AdminService by viewing the Properties and then selecting "Dependencies" Tab  

• Verify that these dependent services are found in this server's Windows Services   
• Remove unused Services and add additional Services not listed from the AdminServer registry key "DependOnService" string  

Progress Articles:

How To configure windows to Start A Broker Under a Windows User?   
Database and AdminServer not shutting down when rebooting a Windows 10 machine
How to shut down the Database and Adminserver on Windows when the system is restarted ?