I have a couple virtual machines that work properly in 1703, but fail in 1709. Microsoft hasn't seemed to put out a fix for it yet. If RemoteFX is enabled, when people disconnect from RDP and try to reconnect, it builds new sessions rather than reconnecting to old ones, orphaning in-progress work. If RemoteFX isn't enabled, it works, but you lose out on GPU acceleration. Not really acceptable when doing renders and computations. I'm managing updates via WSUS, and before I just go drill down and create a new group for just those 3 virtual machines out of 1500+ systems, is there a way to make Windows permanently stick to 1703 until updates are no longer visible? I know I can defer for 6 months, but I honestly don't know that MS will have a fix in 6 months, and unless we decide to spend $12,000 to buy new physical machines, I don't know when we can move to something else. I'd prefer we pick up a new system and go a GPU passthrough w/ VMware route, but while it takes less rack space, it does make things more complicated than just tossing PCs on a shelf to just chug there and get RDP'd into. Something that I could set in Group Policy would be great, so I don't have to choose which AD group I want to put it in ("Do I want mapped drives and other things engineers use to be easy, or do I want to treat it like a server, where it doesn't get unnecessary crap that isn't applicable to an RDP session user?"), or always have 2 updates set at 44/45 for installation. This 1709 rollout has been problematic with it breaking Outlook MAPI, and at this rate, by the time I've rolled it out to everyone properly, it'll be time for 1803.