Alex Hovsepian and Daniel Stranathan Thanks for reaching out, and happy to address your questions. Alex: Even in Travel Wi-Fi mode filtering policies still apply—an attempt to a domain blocked by t...
Saqib Sorry about that; looks like GitHub had an incident blocking access to repositories. They've updated their status page to full operations, so you should be able to access the script without i...
Thanks for raising this, Saqib—and you’re right, the DNS value sticking at 127.0.0.2 after uninstall is not expected behavior in the Roaming Client.Older 1.X agents could occasionally lose their DN...
That's awesome; thanks for sharing, Kevin McGillicuddy ! Always cool to see folks using API like a pro 🙌
Great question, Jeremy Felpel—and you’re not alone in wanting more flexible filtering in the Query Log. A request for advanced operators (including NOT / Does Not Contain) is already captured in Ca...
Thanks for adding all this detail, Lisa Busby —this is incredibly helpful! We really appreciate you taking the time to document what worked. Contributions like yours make the Community stronger and...
Thanks for sharing this here! I see you’ve already got a support ticket open, which is perfect. We’ll keep an eye on the case, and once everything is resolved, we’ll post a quick summary in this th...
Great catch, Charles Jones—and thanks for flagging this! 🙌 We’ve updated the article to clarify the .NET requirements.To confirm: You’ll need .NET Framework 4.8.1 and .NET Desktop Runtime 8.0 for a...
Jonathan Drever Just wanted to give you a heads up that the 3.0.0 Beta release went out today! Hope this new version works for your environment, but if anything comes up we encourage your IT team t...
Starting with Windows Roaming Client version 3.0.0, configuration preferences are no longer made through the registry. If trying to migrate a 3.x.x agent, remove the appsettings.overrides.json file...