We experienced this on 8.5.2-027, too, and arrived at the workaround organically and had to quickly scramble to deploy an updated Windows GPO. Two questions: 1) does 8.8.0-085 resolve this but it's just not mentioned in the release notes, and 2) does anyone have a successful method of monitoring for this breaking to avoid the surprise?
