We have an application that has been used for years and is stable. A couple of weeks ago, about the time of the Feb 2015 Patch Tuesday, some of the screens are showing some alternate character set. This of course makes it difficult to read
and work. The application itself is on a disk of a Server 2008 R2 computer. It is run by users who connect via Terminal Services to either a Server 2003 or a Server 2008 (note there is no R2 here. This is a 32-bit OS). On
either machine the problem shows up. However, running this app either right off the file server or either the 2003 or 2008 on the respective console works just fine. My assumption is that this must have something to do with Terminal
Services or the clients.
To make things more interesting, this only happens on one application. I have RDPed in to each server and run all sorts of things. Everything I've tried has seemed quite normal. I do not have access to the failing application from here. I have tried getting in via two clients and thus two versions of RDP. I have tried Win 7 and the ancient XP both of which work fine. The users of this app are all using Win 7 (I believe).
So, timing suggests something changed around the time of Feb 2015 patches. Does anyone know of what all got changed that might affect this? Or, does anyone have an good ideas as to how to diagnose further?