From the early beginning of NAV2013R2, I tested it only as standard client option (Windows 7/8/8.1 and Windows Server 2008/2012). I never tested it on Terminal Server. I think, there are not a reason to use Terminal Server, because this is 3-tier application and all works fine on very complicate infrastructure.
But, I was wrong. I have client who want to use NAV2013R2 client on Terminal Server. Reason for this is simply, they have many computers with Windows XP. They already use NAV for many years and they want to upgrade NAV to the newest version. They have budget for upgrade, but in this moment, they have not a budget for newer OS (they need new Windows and new HW, as well). On the other way, they already bought a lot of TS licenses.
I didn’t think about this, but this is reality. In practice, nothing is perfect and we need to configure system we have. In my example, my client has Terminal Server – Windows Server 2008R2. When you read system requirements, you can find that NAV2013R2 is compatible with this Windows Server.
We install NAV and configure it. Everything worked fine until we run reports. When we logon on TS from computer with 4:3 aspect ratio, everything looks fine. But when we logon from computer with 16:9 aspect ratio, there is a problem.
When we start standard Preview, everything looks fine. But in Print Layout rendering or when printing to paper it would look like that the fonts have been scrunched and it's hard to read. These reports are completely unusable. Even worse, the most of computers in my example has 16:9 aspect ratio. Small problem becomes a big problem. If we use Windows Server 2012, there isn’t problem, but I have Windows Server 2008R2. My client don’t want to upgrade TS to Windows Server 2012 (because in system requirement Windows Server 2008R2 is compatible). This is additional cost and this is not fair. Also, we cannot provide screen resolution of 4:3.
But thanks to Microsoft, we got a hotfix Article ID: 2768741. If you also have the same problem, go to http://support.microsoft.com/kb/2768741/en-us. You need to read article very carefully and do all steps. We try this and now everything works fine. Thanks to all my friends in Microsoft for fast help in this case.