Visual DPI doesn't match Desktop when using Remote Desktop
Open regedit and navigate to the registry key:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide
Right-click, select NEW -> DWORD (32 bit) Value
Type PreferExternalManifest and then press ENTER.
Right-click PreferExternalManifest, and then click Modify.
Enter Value Data 1 and select Decimal.
Click OK. Exit Registry Editor.
Next step is to make the manifest file, mstsc.exe.manifest. Copy the contents below and put it in Notepad or similar tool and save it to a file as %SystemRoot%\System32\mstsc.exe.manifest. Download of the file is also available, here. Important is that you save the file in the same directory as the Remote Desktop Client executable (mstsc.exe).
Related Articles
Bar Code Labor Ticket Entry not scanning correctly through Remote Desktop Session
Description: Barcode scanner is not scanning properly when using Remote Desktop Session (RDS) to access Bar Code Labor Ticket Entry but works fine outside Visual. Resolution: Issue was fixed by editing Remote Desktop Connection and setting Apply ...
Visual Rendering High DPI Issues
Close out of Visual right click on visual icon and select open file location Find VM.exe Right click and select Properties Select Change High DPI settings Select the checkbox under High DPI Scaling Override Select System (Enhanced) Click ok then ...
Use Single Sign On in Visual
If you get the above error when trying to log into Visual, create a shortcut pointing to VM.exe (or copy an existing shortcut to it). Right-click the shortcut and go to Properties, and at the end of the Target field, add a space and "-SYSADM" (no ...
Error while Launching Visual - "Cannot find specified protocol entry"
If the following error is encountered while trying to launch Visual, check if there are any ODBC connections with the same name as the database name specified for the Visual connection. ...
VELogon - INI settings - delete lines using Policy Profile folder
See attached for generic instructions for deleting lines from an INI file using the Policy Profile\VMFG folder in a VEScripts/VELogon environment.