Community
Agent with UN-checked IPv6 by default
Links used in this discussion
It turned out UN-checking IPv6 fixed the problem.
Is it possible to deploy an agent with IPv6 UN-checked to start out? Or do i have to walk the customer thru the process of un-checking it, which would be difficult.
Or maybe have the agent try both methods without any user intervention?
Note i still have v5.6
Any settings that you can find in the Agent/Host can be altered on the MSI configuration step. At the last step of the configuration process https://www.remoteutilities.com/support/docs/agent-package/ you need to select "Specify new settings for Host" radiobutton and click Finish. This will launch a Host/Agent settings window that looks almost exactly like the vanilla Host settings window. Uncheck the IPv6 there and then close the settings window - the configured Agent will be created.
Another question is that why you couldn't access the Agent using that option on. Are you sure that was the reason? If so, we'll need to test that , perhaps it's a bug we didn't know about.
As for why connection actually failed....
How long does it take from an agent.exe invocation to the Internet-ID being available on your gateway? Another time i tried to connect in this same location it took about 1-2 min. I did not know to wait that long. Perhaps un-checking IPv6 just bought me the time for the agent to register.
And does a brand new host take longer to register than a 2nd invocation of agent.exe on the same host?
Thanks for the reply, Conrad.
Usually no more than a couple of seconds. Sure, 1-2 min in not normal at all.How long does it take from an agent.exe invocation to the Internet-ID being available on your gateway?
Only one instance of the Host/Agent can run at the remote PC. I.e. if the Host is running, you won't be able to run the Agent because it's essentially the same program.And does a brand new host take longer to register than a 2nd invocation of agent.exe on the same host?
The Agent is supposed to be used when no Host is installed. In the near future we'll possibly simply combine Host and Agent in a single installer and make them "convertible" to each other.
Just wanted to clarify this issue with ipV6. When you enable it and cannot connect - is it through our hosted service or your self-hosted RU Server?
Thanks!
That explains it. IPv6 doesn't work with our hosted service as of yet.john kumpf wrote:
It was with your hosted service, the default. I dont have my own RU server running. And i have not tried this again since i posted so i dont have any more data on it. But thanks for looking into it.
Will the agent.exe resulting from the configurator be digitally signed by Usoris under your certificate?
No while you are using the offline MSI configurator. And that's why we have an online configurator in our plans. This will allow us to sign the output file with our digital signature.john kumpf wrote:
Will the agent.exe resulting from the configurator be digitally signed by Usoris under your certificate?
No ETA for that , unfortunately.
Oh yes, faster please! This is our biggest non-technical issue with RUT. Trying to explain to a customer that the host or agent we are trying to get them to install is safe (in the face of more and more 'warning' prompts) is tedious and sometimes challenging.Conrad Sallian wrote:
...And that's why we have an online configurator in our plans. This will allow us to sign the output file with our digital signature.
No ETA for that , unfortunately.
Could you not embed the digital signature into the RUT licence key?
* Website time zone: America/New_York (UTC -5)