LCM DSC Proxy Awareness
Currently the LCM is not proxy aware, in our case there's no direct route to Azure resulting in the LCM to fail when trying to register. It would be great if the Local Configuration Manager had this capability.
Thank you everyone for the continued feedback on this! This has been delivered in Server 2019 and was already a capability in the Linux agent. It is also possible to workaround the issue in previous versions of Windows using the DSC resource to manage proxy settings in NetworkingDSC, though it is a workaround since configuring proxy settings for the system account could impact other services.
For more information see:
Melvin Veenbrink commented
bitsadmin /util /setieproxy localsystem MANUAL_PROXY <proxyaddress> ";*.<domain>" will work to onboard a server to Azure Automation with the LCM.
Is there a way I can get notified when this feature is available?
Would be great to have this feature as we are rolling out a massive fleet of servers & services on Azure and this issue is causing grief.
Michael Waterman commented
Thanks Michael, looking forward for the feature to become available. Would be a great help to us.
Using proxy settings from the user Could be a possible fix with the -Credentials Parameter
Open IExplorer with PSexec.exe and configure the proxy