When executing a Cmdlet, a keepalive/ping is sent to the DSClient API, if this fails the Cmdlet does not execute. In some cases this is due to an unreliable network connection rather than the session timing out.
Adding an option to set the number of connection attempts should allow Cmdlets to complete more reliably on poor network connections.
Also, marking the session as disconnected after the connection attempt count has exceeded will provide a more accurate view of the connection state when using the Get-DSClientSession cmdlet.
When executing a Cmdlet, a keepalive/ping is sent to the DSClient API, if this fails the Cmdlet does not execute. In some cases this is due to an unreliable network connection rather than the session timing out.
Adding an option to set the number of connection attempts should allow Cmdlets to complete more reliably on poor network connections.
Also, marking the session as disconnected after the connection attempt count has exceeded will provide a more accurate view of the connection state when using the Get-DSClientSession cmdlet.