mstsc: micro text ???

On 8/23/19 11:07 PM, rp wrote:
On Fri, 23 Aug 2019 18:36:52 -0700, T wrote:

YIKES !!!!ÂÂ*ÂÂ* Micro textÂÂ* !!!ÂÂ*ÂÂ*ÂÂ* It is so small that it is
impossible to read !!!

How do I increase the font size?

Sometimes you can hold down the 'Ctrl' key and rotate the mouse wheel
to increase or decrease the font size.


It only affects the icon sizes. Program text is still microscopic.

Ctrl +/- changes text size in applications sometimes.


I will try next time I am on the customer system.

Thank you!

T wrote:

Unfortunately, I can set the screen to a different resultion, but
unfortunately, it just creates a different sized window
with the same micro text.

It's 18 months or so since I set it up for the chap with the surface, so
I'm hazy on details, but there's a scaling option buried somewhere

On 8/23/19 2:02 PM, T wrote:
Hi All,

Yes, I am cross posting. The subject matter deals with both.


Client: Windows 10 Pro - 1809
Server: Windows 7 Pro SP1

YIKES !!!!Â*Â* Micro textÂ* !!!Â*Â*Â* It is so small that it is
impossible to read !!!

How do I increase the font size?Â* (wfreerdp scales fine,
but it has issues of its own.)

https://social.technet.microsoft.com...10itprogeneral

was ZERO help.

Many thanks,
-T

This might work. It is a lot of work though.

[Fix] Remote Desktop DPI scaling issues:
https://blog.brankovucinec.com/2016/...caling-issues/

On 8/23/19 11:31 PM, Andy Burns wrote:
T wrote:

Unfortunately, I can set the screen to a different resultion, but
unfortunately, it just creates a different sized window
with the same micro text.

It's 18 months or so since I set it up for the chap with the surface, so
I'm hazy on details, but there's a scaling option buried somewhere

It does not change the DPI, it just gives you a window with a
scroll bars.

I may have stumbled on a fix. See my latest post before this one.

On Sat, 24 Aug 2019 00:50:00 -0500, VanguardLH wrote:

Did you make sure the client's remote host's resolution is smaller than
your local host's resolution.

That's not required for RDP.

The local host has to show its own
desktop, the window for the RDP client, and then the remote host's
desktop inside the window.

Or you can just show the remote desktop full screen on the local host.
That's what I do. I use a dedicated monitor for RDP and all of the
sessions are full screen. I always have one particular session
established, and then specific other sessions come and go as needed.

T wrote:

There "was" a now pulled hot patch for this at M$:

You cannot change the DPI setting through a Remote Desktop session
on a computer that is running Windows 7 or Windows Server 2008 R2


https://support.microsoft.com/en-us/...top-session-on

The description is pretty clear and will help you understand the issue:

Symptoms:

Assume that you use a Remote Desktop session to connect to
a computer that is running Windows 7 or Windows Server 2008 R2.
In this situation, you cannot change the dots per inch (DPI)
setting on the computer.

Note The DPI setting enables you to change the size of all fonts
and other UI elements on the computer. For example, you change
the setting to increase the legibility of the UI.

I had mentioned changing the DPI but apparently RDP has/had a bug with
in Win7/2008 in letting you change it on the remote host. Sure makes
RDP look screwy.

Although the article itself was last updated in Oct 2017, the file
attributes it lists for the replacement files are back in 2012. That's
pretty old. That page must've been written for version 2 of the hotfix.
There was a version 3 (Windows6.1-KB2726399-v3-x86.msu); however, the
Update Available link in the old article goes to a page saying the
hotfix is no longer available and attempts to push the user to Win10.

I didn't realize ANY remoting software would prevent the remote host
from changing its DPI. That's also why I didn't bother to hunt down any
DPI issues. I just hunted around and found:

https://www.nextofwindows.com/how-to...server-2008-r2

The MS KB page didn't have a download link. When searching on that KB,
I found:

http://thehotfixshare.net/board/inde...howtopic=17457

Of course, this means getting hotfixes from a source other than MS.
From that article, it says KB2726399 got rolled into the hotfix rollup
of KB2775511 containing 90 hotfixes released after SP-1 for Win7, with a
link to:

http://thehotfixshare.net/board/inde...showfile=16296

That mentions even more hotfixes are needed after the above one. Seems
a hydra hotfix: cut off one head, more grow in its place. Hotfix
2775511 has its brothers 2732673, 2728738, 2878378, and 2878378.
Searching on KB2775511 found:

https://support.microsoft.com/en-us/...p1-and-windows
https://www.catalog.update.microsoft...px?q=kb2775511

I found forum articles by users posting in 2015 complaining that MS
should've included the hotfix rollup as a normal update available via
Windows Update (unless you run your own WSUS server), as the hotfix
rollup also supposedly fixes some network errors. Some claimed it also
shorted the Windows boot time; see:

https://aidanfinn.com/?p=14302

Looks like MS later came out with a "convenience update" that included
the hotfixes.

https://blogs.technet.microsoft.com/...r-2008-r2-sp1/
"If I have not deployed KB2775511, do I need to deploy it first? No."
Some of the commenters noted some updates were superseded by others.

The MS catalog shows the 2775511 hotfix rollup was dated way back to
2013, but was available as a normal update (classification = update),
not a hotfix update (classification = hotfix). The catalog does list
hotfix updates, but not for 2726399 (probably because it got
superseded). Since 2775511 appears a normal update, have you fully
updated your Win7 host? Looks like RDP got fixed back in 2013 regarding
DPI and other issues.

On 8/24/19 12:51 PM, VanguardLH wrote:
I didn't realize ANY remoting software would prevent the remote host
from changing its DPI. That's also why I didn't bother to hunt down
any DPI issues. I just hunted around and found:

https://www.nextofwindows.com/how-to...server-2008-r2

Thank you for the wonderful and thoughtful write up!

wfreeRDP lets you set the dimensions (scaling) of the
clients machine, but MSTSC does not. I would say a stain
on some otherwise nice programming.

I fid RDP to be the fastest emote access tool out
there for Windows. And the cheapest too, so long
as yo have the Pro version of Windows. You do have to
do a port forward though. (I mask the port.)

I will have to read over the above link really closely.


-T

wfreerdp Windows nightlies:
https://ci.freerdp.com/job/freerdp-nightly-windows/

By the way, the C in /drive:home:c: is lower case.
Had to find that out the hard way

On 8/24/19 12:51 PM, VanguardLH wrote:
T wrote:


https://www.nextofwindows.com/how-to...server-2008-r2

This hotfix is no longer available

T wrote:

VanguardLH wrote:


https://www.nextofwindows.com/how-to...server-2008-r2

This hotfix is no longer available

Why I mentioned the hotfix rollup which is available.

On 8/24/19 10:45 PM, VanguardLH wrote:
T wrote:

VanguardLH wrote:


https://www.nextofwindows.com/how-to...server-2008-r2

This hotfix is no longer available

Why I mentioned the hotfix rollup which is available.


I have been looking it over.


I does mot seem to me that the issues is on the w7 serve
as wfreerdp scales just fine. So, I am doing a lot of
thinking.