Tag Info

Hot answers tagged

2

Your path is probably longer than 2048. That is a published limit, and reducing your path below that will probably solve your problem. I'm not sure why RDP triggers it. My path is over 2048 when I first boot up, and it doesn't seem to matter... until I access the my workstation remotely using RDP.


2

There is no such thing as a generic text printer on OSX. OSX internally treats EVERY printer as postscript at the OS level. Then converts the postscript output to whatever language the printer needs (ZPLII in your case). So the Remote Desktop APP sees a "postscript" printer on OSX and communicates that to your Windows server. (Windows usually sees it as a ...


2

Solved it myself: Start --> Administrative Tools --> Remote Desktop Services --> Remote Desktop Session Host Configuration and then in the "remote control" tab selected "Use remote control with the following settings" and unmark the checkbox defaultly stating "Require user's permission". But on second thought, it's only advisable (if at all) when you ...


2

You will either need a router that allows forwarding to a different (internal) port than the port it's answering on, and set that internal port to the default RDP port (3389). (Related SU question: Port Forwarding on Router using same internal port number on different IP addresses) OR you need to change the port RDP listens on, on each machine. For that, ...


1

Unfortunately, RemoteApp does not support docking: https://support.microsoft.com/en-us/kb/954401/ - so this is not possible, not with a mouse / touch or a keyboard.


1

If I understand the question correctly this will get you what you want. This is PowerShell: $FireWall = New-Object -comObject HNetCfg.FwPolicy2 $EnableRules = $FireWall.rules | Where-Object {$_.LocalPorts -like "*3389*" -and $_.Profiles -eq "3"} ForEach ($Rule In $EnableRules){$Rule.Enabled = "True")} This will filter out the rules and grab the correct ...


1

Use rdp certificate authentication. @Scott Chamberlain described this http://superuser.com/a/750943/440206: Yes but you will need to install and configure your Remote Desktop Session host to use a Remote Desktop Gateway to do it. Once you are using a Remote Desktop Gateway you can set up Remote Desktop Connection Authorization Policies (RD ...


1

In the general case, no. In the specific case, it would depend on exactly what the artifact is. If you're talking about purely display corruption, most likely "No." But if the hardware is causing driver issues, "Maybe." As a diagnostic tool, this would be mostly-meaningless. "Mostly" because there IS the possibility of comparing known-bad screenshots ...


1

It sounds like this server is the member of a domain. You'll need to disable or modify the GPO that's causing this. There are a couple of ways you can go about this. Disable the GPO and change the configuration directly in terminal services. Configure the GPO with the desired setting. Disable the GPO Open gpedit.msc. Navigate to Computer ...


1

I've got the same issue too - unloading the Trend Micro OfficeScan on the CLIENT did indeed solve the issue. Now I'm stuck at how to allow RDP connections on 3389 and mstsc in my environment


1

Create a batch file with the following contents, named something like restore_console.bat: @echo off set LOG_FILENAME=%TEMP%\restore_console_log.txt echo Script executed at %TIME% > %LOG_FILENAME% echo qwinsta: >> %LOG_FILENAME% qwinsta >> %LOG_FILENAME% echo Checking for pending connection... >> %LOG_FILENAME% for /f %%i in ('qwinsta ...


1

The reason why it doesnt work, is that the virtual machine is using a generic virtual CD/DVD ROM driver. The actual hardware is abstracted from the VM and all it knows is that there is a CD/DVD ROM device is present. The reality is, there might not actually be hardware there. It could just be an .ISO or even another virtual drive. Does this mean it cant ...



Only top voted, non community-wiki answers of a minimum length are eligible