When deploying a SEDR Cloud DAS, you may need to throttle the DAS to compensate for busy or low bandwidth networks, busy clients, or a DC with low resources.
You may see errors in the DAS logs about RPC exhaustion:
Connect share: The RPC server is too busy to complete this operation (1723).
Connect share: The specified network name is no longer available (64).
RPC initialization and network exhaustion errors can also be caused by latency between the Endpoints and their Domain Controller, since they need to authenticate the Domain Admin credentials provided by the DAS. This can overwhelm a DC and authentication requests time out before they can be answered.
There are a few DAS registry settings available to help with throttling how many connections are made to Endpoints. The following keys can be defined under [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OutlierSecurity]