Forum Discussion
Cannot install a new Light Gateway: TaskCanceledException
This makes sense.
the initial registration will try to use negotiate authentication, using proxy settings from the current user.
The service run is using certificate authentication, and proxy settings from local service.
the policy might have been applied after the previous GWs were already installed, so it did not break them.
There's no obvious difference between the new machine and the working one, they're both in the same OU and were built using the same automation.
The Center is domain-joined.
I'm using the same user for deployment as the one I authenticate with on this machine to the Console UI.
Microsofttry to capture a netmon 3.4 trace while you run the deployment, and look in the trace to see what was broken exactly in the process, if there was really an authentication issue, or some other issue that blocked communication.
Also, try to browse the console from the machine using Internet Explorer, are there any warnings or errors that IE displays?
If still no luck, contact support for more in depth research.
We found the issue, although it's a weird one. We have a GPO which does stuff with the proxy settings, which seems to interfere with the LGateway registration task. The GPO is also applied to the other DC, which is sat happily connected to the Center, so it appears that our settings were only causing issues for the Registration of the new LGateway, not for the normal Running operations.
Thanks for the suggestions. If you need any more info for development or for your docs, let me know and I can supply.
- EliOfek
This makes sense.
the initial registration will try to use negotiate authentication, using proxy settings from the current user.
The service run is using certificate authentication, and proxy settings from local service.
the policy might have been applied after the previous GWs were already installed, so it did not break them.
Yes, that makes sense. The DC that was working was already registered months before when the proxy GPO was added, so it wasn't affected. It's only when registering a new LGateway service on a new DC that we would see the issue.
Thanks again.