Can you scale the output of Terminal Server?
by Volker Weber
A friend is running an MS Access application on Windows Terminal Server 2003. All nice and dandy, but there is one problem: If he remotes into the server with a 17" WUXGA 1920 x 1200 display and Microsoft RDC, the application is just too tiny. Can you make it scale up? I don't see any options in RDC.
Comments
In a remote desktop connection, I don't believe you can increase the resolution above that of the host VGA adapter; although you can downscale as necessary.
Your only hope might be if you run the Remote Desktop mstsc.exe with the -console switch. This allows the user to take over "session 0" on the remote machine...the console itself. This may allow them to increase the remote display, but I find it unlikely it will be higher than that of the host adapter.
To increase resolution higher would require MS to apply a virtual display adapter hardware device to users on terminal sessions, which is doesn't do.
Maybe MS Virtual Server is a better solution?
Mstsc.exe supports the option "smart sizing" when it's used in with RDP-files (not via GUI). Just add the line "smart sizing:i:1" to the end of the RDP-file.
Unfortunately this function works exactly invesrse to the feature that you are looking for. It can only the scale down(!) the window, it's not possible to scale up this way (at least I have not found out yet how to :-)).
I don't know if other RDP-Clients have a similar feature.
I don't know if this helps, but I have on our small business server under 'Accessories'->'Accessibility' a magnifier. Maybe this helps you at least a bit :-)
Maybe i missed something - mstsc.exe -> options -> display -> remote desktop size.
Magnus, this will increase the size of the window, but not the size of things inside the window.
I tried but haven't got it right now. But there must be some option available for resizing.
MS Access isn't exactly known for scalability. Try Oracle or DB2. Sorry, couldn't resist ;-)
Post a comment
Recent comments
Alex Wokurka
on No surprises at the PhilNote at 23:14
Ragnar Schierholz
on No surprises at the PhilNote at 23:02
Volker Weber
on No surprises at the PhilNote at 21:53
Ben Poole
on No surprises at the PhilNote at 21:07
Pieterjan Lansbergen
on No surprises at the PhilNote at 21:03
Jan Tietze
on No surprises at the PhilNote at 20:48
Ben Rose
on No surprises at the PhilNote at 15:14
Ben Rose
on No surprises at the PhilNote at 14:46
Philipp Sury
on No surprises at the PhilNote at 13:40
Sascha Reissner
on No surprises at the PhilNote at 13:28
Ben Rose
on No surprises at the PhilNote at 12:10
Colin Williams
on No surprises at the PhilNote at 09:43
Adalbert Duda
on No surprises at the PhilNote at 09:33
Volker Weber
on No surprises at the PhilNote at 09:28
Jan Tietze
on No surprises at the PhilNote at 08:53
Ben Rose
on No surprises at the PhilNote at 08:14
Volker Weber
on No surprises at the PhilNote at 04:50
Amy Blumenfield
on No surprises at the PhilNote at 01:36
Richard Schwartz
on Peter O'Kelly: I am now a Microsoft employee at 02:49
Hanno Zulla
on Ente Chop Sui at 22:32
Kristof Doffing
on Ich helfe gerne aus der Autokrise at 15:03
Bruce Lill
on IBM is not going to send out a press release at 00:31
Thomas Cloer
on Events of the last few days at 12:38
David M Taylor
on Two screens or one? at 03:27
Henrik Heigl
on Events of the last few days at 18:51



