Windows 8.1 DPI scaling and remote desktop issues

On my desktop display (2560*1080 21/9 display) I am using no DPI scaling. (100%)
When I remote into this machine from my Surface Pro tablet the display changes to 1920*1080 to fit the surface's display and scaling also kicks in. (125%)
When I afterwards login to the main machine directly, scaling is completely off. Large text and headers in explorer and small icons. Any way to fix this issue ? Loging off and back on fixes it but usually I'd like to keep the user logged on so my programs
keep on running.

If you change the scaling to 100% while logged in over RDP, then disconnect or log off, does it stick?
I had to grin just a bit... Microsoft has been touting the integration of their tablets and yet last time I remoted into my Windows 8.1 desktop workstation from my
iPad using a free RDP app It just kept the monitor 1 display size (1600 x 1200) and didn't mess at all with the desktop settings.
-Noel
Detailed how-to in my eBooks:
Configure The Windows 7 "To Work" Options
Configure The Windows 8 "To Work" Options

Similar Messages

Windows XP see blank screen when remote desktop to Windows 7 with fast user switching disabled

All computers are in workgroup environment, no AD.
Windows 7 pro are configured with fast user switching mode disabled so that only one login session can run at a time. When a Windows 7 machine remote desktop to another Windows 7 machine, the remote desktop 'server' will give 30 seconds count-down for the
console logged in user to accept remote connection, or when timeout expires it kicks out the console logged in user. This is completely ok.
This become a problem when a Windows XP rd client try to remote desktop to these Windows 7 machines, Windows XP see a blank screen if the remote Windows 7 machine has a user logged in, as it is waiting for the user to log off first. This is not desirable
as our administrators want the console session to be logged out automatically if they (administrators) want to remote desktop in.
Is this a configuration problem? Is this a OS design, can't be changed?
Valuable skills are not learned, learned skills aren't valuable.

Hi,
As I know, for RDP session in Windows 7, you don't need to configure the fast user switch option disabled. Windows 7 doesn’t support multiple Remote Desktop sessions by design, that means only one RDP session at a time.
I remote into my Windows 7 machine (which has a user logged in) from my XP machine, all work fine, the user logged in Windows 7 machine is automatically "kicked off".
May I ask a question? Does this issue happen in all XP machines? If you leave Windows 7 machine started and no user logged in, the RDP session in Windows XP established quickly?
I would suggest you keep latest drivers graphic card and latest updates paches for both Windows XP (Windows XP has come to its end of the lifecycle)and Windows 7.
Yolanda Zhu
TechNet Community Support

Remote control and remote desktop client in sccm 2012 ?

What is the difference between remote control and remote desktop client in sccm 2012 ?

Remote Control is a built-in feature for SCCM 2012 and uses the RPC protocol. When you use this, the user can still be logged on while helping.
Remote Desktop is a buit-in feature for Windows and uses the RDP protcol. When you use it, the user will be logged off.
Why you would use one over the other depends on your requirements.
Blog: www.danielclasson.com/blog |
LinkedIn:
Daniel Classon | Twitter: @danielclasson

Issue: Windows 8.1 - DPI Scaling

I want to know if there is a way to disable auto scaling on start screen in windows 8.1. My laptop does not have a touch screen, so this scaling is useless for me and it get worse when I connect my laptop into my TV, the Tiles on my screen get even bigger
that it already are.
Normally on my laptop I can use the option show more tiles, this options enables 6 rows of tiles, but I don't know why on my TV this option doesn't have any effect and the start screen and it shows only 4 rows of tiles.
My TV is a Sony 42" Full HD and my laptop a Sony Vaio SVS 15.
This is on the Laptop:
and this on the TV:
Irauan Lage

Hi,
We can try to configure this setting: under Control Panel\Appearance and Personalization\Display
Please check on "Let me choose one scaling level for all my displays" option.
This setting determines whether the automatic DPI-scaling of Windows 8.1 is enabled or not. If the setting is unchecked, Windows will automatically select scaling values for each display the PC is connected to.
For detailed information about what is changed on Windows 8.1 DPI Scaling, you can refer to this article:
Windows 8.1 DPI Scaling Enhancements
http://blogs.windows.com/windows/b/extremewindows/archive/2013/07/15/windows-8-1-dpi-scaling-enhancements.aspx
Hope these could be helpful.
Kate Li
TechNet Community Support

Hp laserjet pro m1217nfw and remote desktop printing

hp laserjet pro m1217nfw and remote desktop printing, is there any issues with said function?

whats the problerm you are having??

Surface Pro 3, Remote Desktop, multiple monitors, Windows 8.1 DPI scaling issues

I have been evaluating Surface Pro 3 and once of the attributes is the display. Here is the description of the environment and the remote desktop display issue.
Surface Pro 3 (Windows 8.1 with latest firmware and Windows updates) has 12 inch built-in screen with native resolution 2160x1440. The Surface is docked and an external monitor (native resolution 1920x1080) is connected to the docking stations. The
display configuration doesn't allow for different scaling for each monitor, single scaling value is used for multiple monitors. This is an issue as the recommended scaling of 150% is optimal for small built-in screen of Surface but it is not optimal for
large screens of external monitors. Also this scaling is "inherited" by a remote desktop session which results in objects being too large on the remote desktop sessions or sometimes even blurry/fuzzy.
Can the blurriness/fuzziness of the remote desktop session be resolved?
Z

Hi Colin,
Thanks for the response. I installed the latest firmware and patches about a week ago and the scaling issue improved. It is not optimal yet as some graphical elements are still out of proportions but I do not want to spent more resources on this subject
anymore.
Best regards,
Zbysek
Z

Windows 2012 R2 Active Directory Domain Services and Remote Desktop services Role on the same server.

Findings:
Currently, Windows 2012 R2 AD DS role and RDS With Broker services can only seem to coexist properly in a new domain not an existing domain. Any attempt to add to an existing domain causes internal database user access denied issues and any attempt to
adjust rights and circumvent is dubious at best.
The escalation technician said it best. Out of 50 clients that want to do this, they end up not being able to help 5 right off the bat for whatever reason. As for the other 40 they might be able to help by running reports, adjusting rights and trying to add
the roles until it works. This can end up being a 20 day process. Basically they are playing whack-a-mole with user rights and permissions until something sticks.
We tried creating an OU where any other domain policies would not be inherited to see if that was the issue, a fresh install with different sequence of adding the Roles, no effect.
Given the errors I witnessed when running procmon and then trying to add the roles, the NT System and the Windows Internal database user had access denied issues on 100+ registry keys when trying to add the roles. After that the system is not behaving normally.
The errors displayed almost mirror the errors that would occur on Windows 2012 when those two roles would be added which of course is officially NOT supported on that system.
This blog needs serious revision:
http://blogs.msdn.com/b/rds/archive/2013/07/09/what-s-new-in-remote-desktop-services-for-windows-server-2012-r2.aspx
This is the excerpt from that blog: Single server RDS deployment including Active Directory. We now support running our RD Connection Broker role service on the same physical instance as an Active Directory Domain Controller. In addition, we published
guidelines for how RD Session Host could be used without the RD Connection Broker.
Microsoft Support was curteous and helpful and they were the ones who advised cutting our losses, which mirrored my hunch after seeing what was transpiring in the system. They refunded my money for the support call.
For me, it was an opportunity to find out if there was any way to configure Windows 2012 R2 in the Same manner that it was setup as Windows 2008 R2 and lay that to rest. The coexistence is poorly implemented. It is as if there was a reaction from all the deprecation
of bread and butter features such as shadowing in TS and the coexistence of AD DS and RDS to where those features were re-added haphazardly. (I have no complaints on shadowing on Windows 2012 R2 it works, just do not like having to go to server manager to
use it).
I opted for virtualizing the Domain controller to eliminate the incompatibility issues and that is what I will be doing from now on. I found free solutions for backing up and reporting for virtual machines as well as the suggested procedures for configruing
a Domain controller as a virtual machine on a Hyper-V environment and I will be sticking to those. Thus far the setup has been operational.
I am not allergic to virtualization, but for really small setups it adds additional time and considerations but if that is how it has to be done, so be it. Windows 2008 R2 days are numbered and since we can usually squeeze 5-7 years on quality server equipment,
buying a Windows 2008 R2 setup now is a borderline disservice in my opinion.
Hopefully someone finds this useful and saves some time.

Hi,
Thank you for posting in Windows Server Forum.
Do you need any other assistance?
Based on your description, you are describing your story of successfully implementing RDS server with AD role and more regarding all RDS related scenario. For shadowing feature, you can use with command also. Below is the syntax to shadow a session.
mstsc /v:<ServerName> /shadow:<SessionID>
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

MacBook with OS X and remote desktop to Windows server

I am curious if an apple MacBook running OS X 10.4 can be used as a remote desk top to access a Windows 2000 server. It is easy to do so with a Windows PC with Windows XP. However this necessitates carrying a Windows machine while travelling. I like the MacBook Pro I have and would like to use it for remote access. I do not want to install Windows on the MAC even though I can do it with my MacBook Pro.
Any thoughts? Or are there sittes addressing this issue?
Thanks in advance.
Raj

"I am curious if an apple MacBook running OS X 10.4 can be used as a remote desk top to access a Windows 2000 server."
Please search the discussions before posting. Questions regarding ARD controlling Windows computers have been asked and answered dozens of times.
Install VNC server software on the Windows server and control with ARD, or just use Microsoft's own Remote Desktop Connection for Mac.

OS 10.6.3 and Remote Desktop for windows server, PDF Printer problem

We are using Remote desktop for mac by windows in the office to work on a remote windows server, On the server we are using a business software (Mamut) for sale. In OS 10.5 we are using the PDF Printer to transfer PDF (invoice) from the business software (Mamut) 'Mamut is seeing the PDF printer as any other printer' to the desk top of your mac, so we can attach the PDF to a mail before we send it out to a customer, but in OS 10.6 the PDF printer is removed! So we need a different way of transfer the PDF from the windows server to the mac desk top.
So now I am wondering if any one has a suggestion on how to fix this! if not we can't upgrade to OS 10.6, and that would be a shame!

The thing is that in Mamut, we hit print, and because we us the PDF printer as Printer for Remote desk top, it pup up on the desk top of the mac, as a PDF. But in OS 10.6 there isn't any PDF printer to install, so then we have to make a PDF on the windows server and move it from the server to the mac, by mounting the HD from the Mac to the remote desk top, so it become edible in from the server. I think this is cumbersome.

Windows 8.1 and Remote Desktop

I realize this question or problem has been asked a lot. I figured I would just ask the question too. I have a new HP Pavilion desktop computer running (original) Windows 8. Windows 8 came pre-installed with this computer. I have
a problem trying to remote into this Windows 8 computer from a Vista computer. Since I was never able to get RD to work under Windows 8, I thought I would update to Windows 8.1. Nothing changed. I STILL can't remote into this computer even
with 8.1 installed. The computer is listed under Network and has an IP address.
On this computer, I have a local account and a Windows Live account. Under the firewall, I have enabled any remote settings and checked the Private and Public. Nothing.
Yes, I have RD checked and I have remote assistance checked too. The funny thing is that I don't have any options to set the level of security. It is blank. There is nothing there.
What am I missing here? I want to be able to remote into this computer.

Hi，
For this issue,I may need a few more information to understand the issue better.
1.Did you get any error messages?
2.Can you connect to other PC with Remote Desktop Connection?
3.Did Windows vista ping Windows 8.1 successfully?
First,please refer to the following article to narrow down this issue:
Remote Desktop Connection: frequently asked questions
http://windows.microsoft.com/en-gb/windows/remote-desktop-connection-faq#1TC=windows-8
Then,please temporarily disable Windows firewall and security software to test this issue.
Also,please check the event viewer to see if some error log appeared when the issue occurred.
Regards,
Kelvin hsu
TechNet Community Support

Windows 8.1 DPI scaling does not work with Windows 7 client ?

I have a Surface Pro with Windows 8.1 and a PC with Win7 SP1 both fully updated including optional updates (RDP8.1 client for Win7, verified in about box).
Still, when I connect to my Surface from my PC everything is enlarged.
My PC has two monitors: primary 1920x1080 and secondary 1680x1050. I've tried opening connection on each one of them as well as on both (multi monitor). I've also attempted to use windowed mode with lower resolutions.
Surface is set to default DPI settings (slider moved to Larger and "Let me choose one scaling" is unchecked). Also, when I'm connected via RDP I cannot move the slider ("Some display settings can't be changed from a remote session") though
I can click "Let me choose..." but that requires a sign-out. Another oddity is that my remote desktop client does not have a "Smart sizing" window menu item.

Hi,
When you are within a session you should be able to check the option Let me choose one scaling level for all displays, change the scaling, sign out, then when you reconnect it will have the new dpi setting applied. This is the expected method for a
Windows 7 client.
-TP

HP LaserJet Pro MFP M127fn and Remote Desktop Connection

So, my pc operates on Win7-64bit. I use Remote Desktop Connection to log in to the company server, running on MS Server 2008. I purchased the HP MFP M127fn today after confirming that it is compatible with both OS listed above. I successfully installed it directly to the server via usb cord - to make sure the correct drivers downloaded to the server. I was able to test-print and print from an app while physically connected to the server. I then disconnected the printer from the server and successfully connected it to my local pc. I can test-print and print from an app on my desktop. When connect to the server via RDC, it recognizes the MFP M127fn as my default printer, and sends a print job to my local pc. I can see the job in the server print queue, I can see the print job in queue on my desktop....it spools, then says it prints, however no actual print job ever materializes.
If I select to print to the MFP M127fn fax from the server, it will open the fax window on my desktop, allow me to enter a phone number, and will dial out and send the fax. So, that driver is functioning properly.
So, my question is this: If the printer and fax claim to be successfully installed, why do I not get the print job that is sent via the server and appears in my local print queue? I get no error, either on the server side or the local desktop. They both truly think the job has printed.....but no paper ever comes out.
Our company has used several other HP printers over the years with this same set-up and have never had a problem until now. The last one was also an HP MFP - the CM1312. So, I am now completely stumped by this. I called HP support and was routed through 4 different areas before I was told that no one had a clue what the problem might be. I then called the Easy-Tech desk at Staples, where I bought the printer, and was told that it was most-likely a hardware issue and I should return the printer to swap it out for another one. If nothing would print at all, I would agree it's hardware. But, as I can print locally, I'm more-inclined to think it's driver-related......any suggestions?

Hi,
The M127fn uses the PCLmS printing language which is a lightweight printing language, a such is not supported for RDP printing.
As a reference you may find the following socument about Citrix, Terminal Services and RDP Printing, as you may find listed the M127 is not supported for a such:
http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=4aa0-8465enw&404m=secure-erc
That is clearly not an harware issue, however I suggest returning the printer and replacing it with a different model which better feet such a task.
The M225dn as an example uses a PCL 6 print driver and should provide a better feet for RDP printing using HP UPD.
Regards,
Shlomi
Say thanks by clicking the Kudos thumb up in the post.
If my post resolve your problem please mark it as an Accepted Solution

Can 1 instance of Windows 8.1 ENTERPRISE host multiple Remote Desktop connections?

I am shopping for the components for building a machine with fair, high-performance hardware. I have Windows 8.1 Professional. I wanted to know if either Windows 8.1 Professional or Windows 8.1 Enterprise can support multiple remote connections
from users outside the local network. For example, my brother is based in San Diego, CA and has an underpowered laptop. Is there any way to make a remote connection over that much distance, from San Diego to Northern Virginia, from a RDP client running Windows
8.1 Professional to a RDP "server" Windows 8.1 Professional/Enterprise machine, and run a modern, single- or multiplayer- game over smoothly that connection? At the very least, is it possible to run common
apps (e.g. Microsoft Office 2013 IE 11, Adobe Acrobat XI) smoothly on a Windows 8.1 Pro RDP client connected to a Windows 8.1 RDP "server" located 2250+ miles away?
Would upgrading my installation from Professional to Enterprise improve the responsiveness and display quality for my remote users?
I know Windows Server R2 2012 has features specific for handling remote connections, but I am trying to keep a Windows 8.1 user experience. Still, if anyone can show some evidence that Windows Server 2012 R2 Remote Desktop Services (RDS) improves display
and responsiveness over long-distances for remote (RDS) connections, then I will shop for Windows Server 2012 R2 Standard instead. The huge drawback of Windows Server 2012 R2 Standard CALs is the enormous cost to enable 3-5
remote connections for family, non-commercial use.
Has anyone attempted to host long-distance remote access, non-commercially, for 3-5 connections? Has it worked well? What, in general, is required?
T. Webster

Hi,
It depends on the quality of the network connection to run the software smoothly throuth RDP. And I don't think the quality would be better if you upgrade to Windows 8.1 Enterprise.
Windows 8.1 allow only one session of RDP, the Remote Desktop Server in Windows other than the Windows Server edition has a limitation to allow only one concurrent user per session by default, i.e. if someone remotely connects to the computer over RDP then
whoever was logged in at that moment will be automatically logged off, even if that user is physically present at the computer. This is by design.
Regarding more information about RDP, please take a look at the following articles:
Remote Desktop app help
Remote Desktop Connection: frequently asked questions
Best regards
Michael Shao
TechNet Community Support

Access Anywhere VPN and Remote Desktop

I have a recently installed Win 2012 Essentials server. I have VPN, Remote Web Access, enabled. I can use Remote Web Access and login to see my remote desktops and drives, but VPN is not working. Both are enabled. I'm not able to
use the wizard to config but my firewall has 443 open. My clients say they can't see the server when disconnected from the local network.
The VPN connects but says it can access the server.
Not sure where to look.
Kevin

Hi Kevin,
Based on your description, it seems that Remote Web Access ran as normal. Would you please let me know whether
get any error message when configure Anywhere Access?
Please click Setting option in Dashboard. Navigate to Anywhere Access tab in Settings panel and click ‘Repair…’
button. Then check if find some relevant clues.
In addition, please refer to following article and check if can help you.
Manage VPN in Windows Server Essentials
Meanwhile, please follow the path: C:\ProgramData\Microsoft\Windows Server\Logs and check relevant log file
if find relevant clues.
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

VPN and Remote Desktop Connection

I have a standalone windows 2012 server that runs a domain with a few workstations. I have successfully configured a PPTP VPN and can connect using a Windows 7 computer at home. Once connected to the VPN, I can Remote Desktop to the server - but not any
other computers. The computer I'm trying to connect to runs Windows 7 and has remote desktop connections enabled.
Under the Access Details in the Remote Access Management the VPN connection is shown correctly first to the router (x.x.x.1) then the server (x.x.x.2) under Protocol 17 and Port 53. Then the server is shown again under Protocol 17 and Port 3389, which must
be the Remote Desktop connection. And then the workstation on the domain (x.x.x.20) also shows a connection with Protocol 17 and Port 3389. However, the remote desktop connection fails everytime. I'm not sure where the issue exists since it appears the server
is seeing and acknowledging the remote desktop connection. On my router I have PPTP passthrough enabled and port forward 3389 to the server.
I have attempted to use the workstations internal IP address as well as the computer name (workstation and workstation.domain.local) when connecting.
Thanks for your help.
I just noticed these three event errors on the destination remote machine. Not sure why it's trying to use L2TP?
Failed to apply IP Security on port VPN2-1 because of error: A certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.. No calls
will be accepted to this port.
A certificate could not be found. Connections that use the L2TP protocol over IPsec require the installation of a machine certificate, also known as a computer certificate. No L2TP calls will be accepted.
The Secure Socket Tunneling Protocol service either could not read the SHA256 certificate hash from the registry or the data is invalid. To be valid, the SHA256 certificate hash must be of type REG_BINARY and 32 bytes in length. SSTP might not be able to
retrieve the value from the registry due to some other system failure. The detailed error message is provided below. SSTP connections will not be accepted on this server. Correct the problem and try again.

Morning Trent,
I don't know if this is still an issue for you, did you get it solved?
If not, check on the server whether the user credentials that you're using to RDP to the workstation are actually authorised server-side. If that checks out, on the VPN connection you can specify a protocol to use. Specify the protocol that your VPN is configured
to use on the server.

Windows 8.1 DPI scaling and remote desktop issues

Similar Messages

Maybe you are looking for