SRS Dual Display Windows Size Issue

%3CLINGO-SUB%20id%3D%22lingo-sub-288745%22%20slang%3D%22en-US%22%3ESRS%20Dual%20Display%20Windows%20Size%20Issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-288745%22%20slang%3D%22en-US%22%3E%3CP%3EHI%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20hitting%20an%20issue%20with%20multiple%20Logitech%20SmartDock%2FFlex%20SRS%20deployments%20with%20dual%20screens%20failing%20to%20size%20the%20SRS%20windows%20correctly%20on%20any%20of%20the%203%20display%20(2%20x%20Front%20of%20Room%20and%201%20x%20SRS).%20On%20screen%20wake%20up%20the%20SRS%20windows%20do%20not%20revert%20to%20full%20size%20and%20only%20occupy%20a%20quarter%20of%20the%20screen%20estate%20on%20all%20of%20the%203%20displays.%20This%20is%20only%20resolvable%20via%20a%20restart.%20This%20is%20running%20the%20very%20latest%20Windows%201803%20and%20SRS%204.0.51.0%2C%20but%20it%20did%20happen%20on%201709%20and%20earlier%20SRS%20releases%2C%20so%20is%20not%20a%20new%20issue.%20In%20general%20the%20frequency%20of%20this%20issue%20seemed%20to%20reduce%20once%20a%20full%20upgrade%20from%201703%20all%20the%20way%20through%20to%201803%20was%20completed%2C%20but%20it%20has%20not%20gone%20away.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anybody%20seen%20this%20issue%20%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnybody%20got%20a%20workaround%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20would%20like%20to%20try%20an%20Gefen%20EDID%20minder%20to%20see%20if%20that%20resolves%20this%20but%20that%20will%20not%20work%20inside%20a%20SmartDock%20Flex%20system%20as%20there%20is%20no%20space.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20assuming%20this%20is%20down%20to%20some%20sort%20of%20race%20condition%20occurring%20and%20the%20SRS%20and%20displays%20failing%20to%20agree%20on%20the%20resolution%20to%20use.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJed%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-288745%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeployment%20%26amp%3B%20Operations%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-352046%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Dual%20Display%20Windows%20Size%20Issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-352046%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20still%20finding%20it%20occurring%20too%2C%20but%20not%20often.%20I%20don't%20think%20the%20MS%20development%20team%20are%20aware%20of%20it%20as%20previous%20discussions%20have%20expressed%20surprise%20on%20this%20one.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-343862%22%20slang%3D%22en-US%22%3ERe%3A%20SRS%20Dual%20Display%20Windows%20Size%20Issue%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-343862%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20experiencing%20this%20issue%20as%20well%2C%20Windows%201803%20and%20Skype%204.0.64.0%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

HI,

 

I am hitting an issue with multiple Logitech SmartDock/Flex SRS deployments with dual screens failing to size the SRS windows correctly on any of the 3 display (2 x Front of Room and 1 x SRS). On screen wake up the SRS windows do not revert to full size and only occupy a quarter of the screen estate on all of the 3 displays. This is only resolvable via a restart. This is running the very latest Windows 1803 and SRS 4.0.51.0, but it did happen on 1709 and earlier SRS releases, so is not a new issue. In general the frequency of this issue seemed to reduce once a full upgrade from 1703 all the way through to 1803 was completed, but it has not gone away.

 

Has anybody seen this issue ?

 

Anybody got a workaround?

 

I would like to try an Gefen EDID minder to see if that resolves this but that will not work inside a SmartDock Flex system as there is no space.

 

I am assuming this is down to some sort of race condition occurring and the SRS and displays failing to agree on the resolution to use.

 

Jed

2 Replies

I am experiencing this issue as well, Windows 1803 and Skype 4.0.64.0

We're still finding it occurring too, but not often. I don't think the MS development team are aware of it as previous discussions have expressed surprise on this one.