It seems like it is switching between focusing on two different IE windows.

I doubt this is necessarily LBS related but it is worth checking that maybe there are some more URLs that need to get to the list of urls to open in both browsers in case what we are seeing is switching between IE and Chrome because of some random redirect that is not yet captured in the SSO flow.

Hi, thanks for looking into this. I was wondering if there were any updates on this.
Thank you!

I am afraid there is not much I can do on my end because I can not reproduce the issue here. 

In my previous comment I have suggested that you can verify that there might be some special SSO related redirection that happens only every n-th time or something that causes the navigation to flip between the browsers.

Can you share the log and configuration data from the customer in the bug (in a private drive doc) for me to try to see if there is any helpful information in there.

Adding Milestone for the current trunk chrome version.

@ligimole - LBS release cycle is not bound to Chrome's so there is not really need to bind this to a particular Chrome release but I'll leave it in to have on if some process requires it :)

David: Can you respond to request from Julian.

Hi, just a quick update, is there any updates?
Thank you :)

This is the same as the information provided previously. Please let me know if there is any specific configuration that you are interested in ?


Please find all log information located in this folder here: https://drive.google.com/drive/folders/0B9BQIK7d0CYNTkxtdHVoQnJ3R2M?usp=sharing

I can see there are 2 IE windows which constantly steal the focus from each other but because I don't see the tray of the virtual desktop I cannot tell if it is really two windows flipping between each other or tons of new windows being spawned.

One last thing to try is to change the policy from ${ie} to the actual path to IEXPLORE.exe on that machine and see if this will fix the issue. This would then mean that the new way of start IE somehow gets in trouble in your particular setup but this workaround should fix it.

Anyhow I don't see anything wrong with the configs. I can see the issue happens in some form of a remote desktop environment from the video. Would it be possible to provide us with a test account for this environment and maybe set up a VC to try to diagnose this live if the suggestions above doesn't help.

Is there a better component for this bug than Internals>Network?  I'm not sure what LBS is, but I don't think it has to do with the network stack, and that component means the network stack triager (me, at the moment) will be repeatedly looking at this bug.

Network is certainly not the right one :) Thanks for pointing this out.

Hi djeche is this still relevant? 

If so can you please answer the questions from comment 10?

Affected customer told us they cannot replace LBS policy to the actual IE path nor provide us with test user credentials, and agreed to close the support ticket as the issue repro rate has been low. I am changing the status to WontFix, until we receive additional reports. Thank you for your help!