02-07-2020 03:41 PM
02-07-2020 03:41 PM
Earlier this week we published an update to this tool at https://connectivity.office.com.
We are actively developing this tool in support of your networking evaluation. Please continue to test out the proof of concept and provide feedback. Our teams next planned release is the private preview in the Microsoft 365 Admin Center which you can read about here: http://aka.ms/netignite
If you have used the tool before, I’d recommend using SHIFT-F5 with the new release the first time you are back. Here’s the changes:
02-26-2020 08:26 PM
@HeathG Hi Heath, if you're seeing the error listed above specific to Click Once not being enabled, then most likely you have not successfully enabled Click Once. You can also try using Internet Explorer which will work for Click Once.
02-28-2020 03:05 AM
03-04-2020 09:50 AM - edited 03-04-2020 12:23 PM
@MattBogen thanks for the screenshot. Please try SHIFT-F5 to refresh the page in your browser and see if that resolves it? We did an update a month or so ago which required this for existing users.
Can you share your browser product name and version and your screen resolution? Also, if you are able, please try on other web browsers on the same machine?
03-20-2020 05:05 AM
Well unless there is something to do other that clicking Enable, then I don't see how I could not properly enable ClickOnce Support.
As you can see I have enabled it. And we do not have any administrative policies that would override this setting. I have enabled it, restarted the browser, and even rebooted the system. I still continue to get this message when running the tool.
I have tried this across multiple computers. Some of which are stand alone computers that are not at all administratively managed. I get the exact same behavior.
Now the interesting thing here is while warning is displayed after enabling ClickOnce Support the advanced test works. So this is really just a cosmetic issue. But the bigger problem here is that I am promoting the use of this tool for clients to measure their connectivity from remote locations, like home offices. It does not really build confidence in clients when they receive this warning. And then it does even more damage to the client when I am forced to tell them, "Don't worry about the warning. Its a bug and it always does that." Therefore I wanted to let you know about this so that hopefully we could get this resolved and be able to install confidence in our mutual clients. I know this is small in scope, but little things DO matter.
Thanks for giving me a forum to communicate with you on this. Also thanks for listening to me and taking these notes into consideration.
03-20-2020 09:06 AM
@Paul Andrew Hi Paul, we're looking to implement split tunneling for our VPN users as per this article: https://techcommunity.microsoft.com/t5/office-365-blog/how-to-quickly-optimize-office-365-traffic-fo....
Can your tool be used to test benefits of split tunneling? i.e. what changes should we expect to see in the results with O365 traffic (except auth) outside the tunnel?
03-20-2020 09:09 AM
Thanks for the feedback.