(Resolved - My own stupidity) Remote Desktop 8.1.3 for iOS (iOS 8.0) - Connects to Black Screen

New version, new problems!
After finally solving my problems with connecting introduced in 8.1.0 for iOS, I have updated to 8.1.3 and have a new problem!
I am able to log in, but upon login, I am presented with a black screen instead of my desktop.  If I turn on the mouse pointer, the pointer shows up, but it does not control the remote computer.
Additionally, the iOS Remote Desktop Client is not "taking over" the remote computer... I am typing on the computer to write this, while my iPad's Remote Desktop app is supposedly "connected" to it.
Anyone else having this new issue?

Resolved - My own stupidity!  :-P
Garbage in, garbage out!  I have two computers connected to the same monitor...My 2nd computer was active on the monitor, hiding the fact that my primary computer (and remote desktop host computer) needed a restart!  I restarted, and the issue
was resolved!

Similar Messages

  • HT5306 I do not want to give remote access to anyone but myself as privacy is my friend.  Can this remote desktop software still be for me personally unless I allow access and for my MAC lap top only?  What if I do not update? compatibility issues with wh

    Hello:
    Thank you for the update for remote access for desktops.
    Personally, I do not want to give remote access to anyone but myself as privacy is my friend.  Can this remote desktop software still be for me personally unless I allow access and for my MAC lap top only?  What if I do not update? I do use this lap top in other countries.  compatibility issues with what?

    Apple Remote Desktop is off be default. It has to be enabled for some one to be able to remotely connect to the computer. And then, you still have to have a user name and password on the computer to remotely connect with.
    If you want to see if remote access has is enabled for Apple Remote Desktop; you can find the setting in, Apple Menu, System Prefrences, Sharing. If it's enabled, Remote Management or Screen Sharing will be checked.
    Beucase Apple Remote Desktop Agent is part of the Mac Operating System; even if your not using it, Apple Software Updates will from time to time offer updates for ARD Agent. Software Updates can some times be stacked ontop of each other; so chosing not to install an update, can mean other updates you may want may not be offered. At least until you install the updates those updates require. Also software updates can improve the security of your computer.

  • Remote Desktop 8.0.12 for Mac Typo

    Remote Desktop 8.0.12 for Mac has a typo in the "What's New" box that appears at startup. It reads "Fixed full screen issues in Yosemity," but should read "Fixed full screen issues in Yosemite." This should be fixed as
    soon as possible to preserve Microsoft's professionalism. 

    Hi Jolly,
    Thanks for shading your light, I will share with product group for further updation. 
    Regards.
    Dharmesh Solanki
    TechNet Community Support
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • HT203554 MacBook Pro (15-inch, Mid 2010) intermittent black screen or loss of video. Can I still get this problem resolve by Apple or I'm screwed because the MacBook Pro (15-inch, Mid 2010) intermittent black screen or loss of video Quality Program has en

    MacBook Pro (15-inch, Mid 2010) intermittent black screen or loss of video. Can I still get this problem resolve by Apple or I'm screwed because the MacBook Pro (15-inch, Mid 2010) intermittent black screen or loss of video Quality Program has ended?

    You can have Apple replace the logic board, but it will be at your expense.  The free replacement program has ended.
    As a band aid you may try the following:
    https://gfx.io/
    This will allow you to run on only the integrated GPU.
    Ciao.

  • Allow log on through Remote Desktop Services Group Policy for Domain Controllers

    Hello,
    We want to allow our Helpdesk Operators to be able to connect to Domain Controllers with the Remote Desktop Services. This is by default not allowed but according to many sites, it should be able to configure by using a Group Policy.
    We made a new Group Policy with the setting 'Allow log on through Remote Desktop Services' and 'Allow log on locally' (as an extra for testing) and applied Security Filtering to only use it for a specific Security Group. Our test user is a member of this
    security group and should be able to access the Domain Controllers now. However this isn't working.
    The error message we receive upon trying to connect:
    The connection was denied because the user account is not authorized for remote login.
    For troubleshooting, we also applied the Security Group for that setting in the Default Domain Controllers Policy but that doesn't seem to work either. We want to avoid customization on our Default Domain Controllers Policy but this was just a test case
    for solving our problem.
    What should we do to solve our problem?
    I hope to hear from you soon.
    Thanks in advance.

    Hi, I just found out what the problem was. This site helped me alot:
    http://blogs.technet.com/b/askperf/archive/2011/09/09/allow-logon-through-terminal-services-group-policy-and-remote-desktop-users-group.aspx
    In my case, I had the group added to the Allow Logon Through Remote Desktop Services but was not added to the Builtin\Remote Desktop Users group. After knowing this I made some changes to our situation and are now using the builtin\Remote Desktop Users group
    rather than a new self made Security Group. I also added the Remote Desktop Users to the Allow Logon Through Remote Desktop Service in the Default Domain Controllers Policy as this is not done by default. By default only the Domain Administrators are able
    to logon through remote desktop services.
    You do not need the 'Log on Locally' permission within the Group Policies.
    In short:
    Add the desired users/groups to the 'Builtin\Remote Desktop Users' security group.
    Add the 'Builtin\Remote Desktop Users' security group to the 'Allow Logon Through Remote Desktop Services' within the 'Default Domain Controllers Policy'.
    Thank you anyway for the fast reply.
    Have a nice day!

  • Remote Desktop Manager 50% off for SysAdmin week!

    It has not been posted here yet, but Devolutions are again offering 50% off a one-year licence of their excellent Remote Desktop Manager software. The offer is available at
    https://store.devolutions.net/promo/sysadminThis program is something I use on a daily basis in my job, and to be honest I would be completely lost without it now. Manage just about any server or environment you have from a single program - RDP, VNC, SSH/Telnet, Citix, Teamviewer, LogMeIn, Radmin, XWindow. It will even give you status pages for VMware, HyperV & XenServer environments - and even AWS! The best part, it also integrates with Spiceworks.
    Strong credential management and integration with popular services like KeePass and LastPass make it easy, and there is also automated VPN management (start connection, VPN opens & connects then the software opens the...
    This topic first appeared in the Spiceworks Community

    Thanks Jakub for "corflags" info.
    Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll [mstscax.dll]?
    Error message when making RDP connection:
    Could not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
    I was able to create new AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll assemblies from 64bit dll version and now it works with "AnyCPU":-)
    http://www.filedropper.com/axinteropmstsclib-mremoteng
    Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"
    so final .dll wasn't working.
    Adding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file.
    Hope it helps
    P.S. Sorry for possible technical misinterpretation, I am not programmer so creating new assemblies was trial-error process...

  • Remote Desktop 8.0.6 for Mac does not map keyboard key properly

    Remote Desktop for Mac 8.0.6 is incorrectly mapping the grave / tilde key on the keyboard to the backslash / pipe key.

    Hi,
    Please check if the system language on your Mac and the keyboard language on the remote PC are match.
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Remote Desktop Protocol v8.08 on IOS (IPAD) - constant disconnects since update to new version.

    I was having major issues with RDP 8.08 update on my IPAD in July 2014.  Connect to my remote Windows 7 desktop was successful, however, screen refresh peformance was very slow and disconnects occured often. Was referred to KB2570170 and applied
    the regedit change to add DisableLargeSendOffLoad = 1.  This however had no real affect.  It was suggested that I recycle my IPAD.  This did resolve the problem.  
    Should a recycle be performed more often ?

    Hi,
    Based on the description, it seems to be a network issue on iPad side. In addition, I think we do not need to recycle iPad more often.
    Best Regards.
    Jeremy Wu
    TechNet Community Support

  • Two critical regressions - Microsoft Remote Desktop 8.0.5 for OS X in Japanese environment

    When connecting from an OS X host to a Windows 7 box remotely via RDC, there are two critical regressions I've noticed.
    Prerequisites:
    OS X host with RDC 8.0.5 and JIS keyboard
    Windows 7 SP1, Japanese
    First issue: yen sign vs. backslash
    Upon connecting to the Windows 7 machine remotely, open a command prompt.
    On a Japanese machine with ShiftJIS (MS932) encoding, the backslash character is represented by a yen sign.
    RDC 8.0.5 is incorrectly sending U+00A5 (yen sign) whey typing the backslash key from the OS X JIS keyboard. RDC should be sending ShiftJIS character 5C (backslash) instead.
    Typing a directory path in the command prompt appears to work as the backslash is represented correctly, however the underlying character is incorrect and commands cannot be processed.
    Second issue: OS X keyboard IME on/off
    The OS X keyboard has two keys to activate/deactivate the Japanese input mode editor, to the left and right of the space bar.  These are both dead with RDC 8 and both keys send simple spaces (U+0020) to the remote host, which is useless and makes
    Japanese input impossible.

    Hi,
    Please make sure that the keyboard language and system language are set to Japanese both on Mac and Windows 7.
    However, if issue persists, you may have to use the On-screen Keyboard of Windows 7 as a workaround.
    Type without using the keyboard (On-Screen Keyboard)
    http://windows.microsoft.com/en-us/windows/type-without-keyboard#type-without-keyboard=windows-vista
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Remote Desktop and Licensing

    I wrote my own licensing scheme and I would like to know how to prevent multiple executions of my app. The licensing is on a per machine basis where it looks at the mac address of the computer to see if it's allowed to run. Because through remote desktop, the mac address for different users logged in simultaneously is always the same, I cannot prevent more than one user to run it at a time. I don't want complicated system session variables that have to be locked and unlocked, I just want to be able to detect, in the code, whether the user is connected to the machine through an rdp session or not. Thanks a lot.

    So surely there's some kind of MS command you can execute to see what users have logged in and how? You've already taken the problem space outside of Java by being bound to a specific OS's command, so I think you'll have to continue along that path, or find a different solution.

  • Remote Desktop Connection stop working after upgrade from 10.5.8 to 10.6.1

    I too could not connect to a W2K3 server with RDC 2.0.1 after upgrading from Mac OS X, 10.5.8 to 10.6/10.6.1. I have another Mac which is on 10.5.8 and connect fine with the same version of RDC 2.0.1 as well as other PC with Terminal Service Clients.
    There is no change on the server side. I have uninstalled and reinstalled RDC 2.0.1 several time and it did not resolve the issue. To rule out firewall/network, I tested with another remote desktop application called CoRD (for Mac) on the same laptop running SL 10.6.1 and it connected to the same W2K3 server fine.
    One thing that is worth mentioning (in my case), when it does not connect, RDC totally quit (not running anymore. Not minimize, no cannot connect error message, no little dot on the Dock for RDC, nothing) right after I put in the credential in. When looking at the log entries that are related to RDC in the Console application, I see the following
    machine 10.6.1. with RDC 2.0.1 (non-working)
    9/22/09 1:17:16 PM [0x0-0x3a03a].com.microsoft.rdc[468] objc[468]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . One of the two will be used. Which one is undefined.
    On the 10.5.8 machine with RDC 2.0.1 (working), I see the following entries
    9/22/09 1:13:23 PM [0x0-0x24f24f].com.microsoft.rdc[5502] objc[5502]: Class NLAssertionHandler is implemented in both /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/Netlib.framework/Versions/12/Netlib and /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL . Using implementation from /Applications/Remote Desktop Connection.app/Contents/MacOS/../Frameworks/RDCPAL.framework/Versions/12/RDCPAL .
    9/22/09 1:13:39 PM Remote Desktop Connection[5502] * _NSAutoreleaseNoPool(): Object 0x16a25c20 of class NSCFArray autoreleased with no pool in place - just leaking
    Stack: (0x9277af4f 0x92687432 0x93062bf5 0x926ce0fb 0x9723dff5 0x9268d52c 0x92fd447a 0x92fd4753 0x92fd4a48 0x930375da 0x530bac 0x4831a2 0x483750 0x483c0b 0x47a811 0x4796ac 0x485dad 0x47d475 0x5099dc 0x574c70 0x4ade03 0x4ae65d 0x4ae6f7 0x4ac8dd 0x53260c 0x534187 0x4ae76a 0x4ae7d0 0x4ae88e 0x493925 0x4ae13d 0x533b1a 0x53da6c 0x94a48057 0x934b3155 0x934b3012)
    Any help would be appreciated

    Doing some more troubleshooting after my post above as I saw a couple of entries referencing Stop Light keep popping up in the log of the Console. I removed Stoplight and Cocoa Gesture (for good meausre) and RDC 2.0.1 started working. I think it is Stop Light which causes RDC stop working, but I don't have to time right now to put Cocoa Gesture back to confirm that. I might if I have the time or post here if you have Stop Light installed as well and removing it resolved the RDC issue for you.

  • Mac Windows Remote Desktop Permission Denied

    OS X Yosemite v10.10
    Microsoft Remote Desktop Version 8.0.10 (Build 25189)
    Please respond with a fix.
    [2014-Nov-15 04:49:45] RDP (0): --- BEGIN INTERFACE LIST ---
    [2014-Nov-15 04:49:45] RDP (0): lo0 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): lo0 af=30 (AF_INET6) addr=::1 netmask=ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff
    [2014-Nov-15 04:49:45] RDP (0): lo0 af=2 (AF_INET) addr=127.0.0.1 netmask=255.0.0.0
    [2014-Nov-15 04:49:45] RDP (0): lo0 af=30 (AF_INET6) addr=fe80::1%lo0 netmask=ffff:ffff:ffff:ffff::
    [2014-Nov-15 04:49:45] RDP (0): lo0 af=2 (AF_INET) addr=127.94.0.2 netmask=
    [2014-Nov-15 04:49:45] RDP (0): lo0 af=2 (AF_INET) addr=127.94.0.1 netmask=
    [2014-Nov-15 04:49:45] RDP (0): gif0 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): stf0 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): en0 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): en0 af=30 (AF_INET6) addr=fe80::6203:8ff:fe9d:9c6e%en0 netmask=ffff:ffff:ffff:ffff::
    [2014-Nov-15 04:49:45] RDP (0): en0 af=2 (AF_INET) addr=192.168.1.23 netmask=255.255.255.0
    [2014-Nov-15 04:49:45] RDP (0): en1 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): en2 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): p2p0 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): awdl0 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): awdl0 af=30 (AF_INET6) addr=fe80::7c06:30ff:febb:b081%awdl0 netmask=ffff:ffff:ffff:ffff::
    [2014-Nov-15 04:49:45] RDP (0): bridge0 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): vmnet1 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): vmnet1 af=2 (AF_INET) addr=192.168.173.1 netmask=255.255.255.0
    [2014-Nov-15 04:49:45] RDP (0): vmnet8 af=18 addr= netmask=
    [2014-Nov-15 04:49:45] RDP (0): vmnet8 af=2 (AF_INET) addr=172.16.188.1 netmask=255.255.255.0
    [2014-Nov-15 04:49:45] RDP (0): --- END INTERFACE LIST ---
    [2014-Nov-15 04:49:45] RDP (0): correlation id: b4c9a4f5-7082-015d-ca07-b8aa6e330000
    [2014-Nov-15 04:49:45] RDP (0): Resolved '192.168.1.255' to '192.168.1.255' using NameResolveMethod_DNS(1)
    [2014-Nov-15 04:49:45] RDP (0): Exception caught: Exception in file '../../librdpclient/asiosocketendpoint.cpp' at line 589
    User Message : Permission denied
    [2014-Nov-15 04:49:45] RDP (0): Protocol state changed to: ProtocolConnectingNetwork(1)
    [2014-Nov-15 04:49:45] RDP (0): Protocol state changed to: ProtocolDisconnecting(7)
    [2014-Nov-15 04:49:45] RDP (0): Protocol state changed to: ProtocolDisconnected(8)
    [2014-Nov-15 04:49:45] RDP (0): ------ END ACTIVE CONNECTION ------

    Hi,
    Thank you for posting in Windows Server Forum.
    Please check whether having enough permission to access the server\remote system?
    Can he access remote session from other device? Does other users can login well?
    Because the error defines that he don’t have enough permission to perform this task. On Remote System\Server side kindly check whether he has added under “Remote Desktop Users” local group for accessing remote session. In addition please check following
    article.
    Why can’t I connect using Remote Desktop Connection?
    http://windows.microsoft.com/en-in/windows7/why-can-t-i-connect-using-remote-desktop-connection
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    TechNet Community Support

  • Cann't see outlook on remote desktop

    I an login to my work PC using microsoft remote desktop I installed on my mac but it doesn't recognize word, excel and outlook in my remote desktop window.

    This forum is for questions about Apple Remote Desktop, Apple's program for managing networked Macs. If you're using Microsoft's Remote Desktop Connection Client for Mac, you'll be most likely to get help in Microsoft's own forums.
    Regards.

  • Remote DeskTop Connection on iMac OS X (10.6.5)

    I am using RDC into work. I also have a need to use my system as do others in my home. We have 3 user accounts on the iMac and when I walk away I would like to log out of my account so others can use the system. Is there a way to do this keeping the RDC connected in the background?
    Thanks
    Steve

    If you are referring to Microsoft's Remote Desktop Connection Client for Mac, that's a different product. As such - this forum being specifically for Apple Remote Desktop, Apple's software for managing networked Macs - you might have more luck getting suggestions if you ask in Microsoft's own forums.
    Good luck.

  • Keyboard losing focus while in remote desktop session

    Hi,
    I have several Win7 computers that remote into a hosting company's server. Our users will log into the hosting company's servers via remote desktop. The issue that keeps coming back is that the keyboard will stop functioning after a user locks the computer
    then returns after a short period of time to continue working. The remote desktop session will remain working while the pc is locked. After unlocking the computer the keyboard will not work in the remote session. The mouse isn't affected by this and minimizing
    the session, the keyboard works fine on the local session. Sometimes you have to restore down then restore back or minimize the RDP session several times to get the keyboard to work inside the remote session. On a few occasions, ending the RDP session
    will cause the keyboard to work again. Anyone experienced this and have a resolution for this issue? This issue appears to be occurring more frequently and we have already recreated user profiles on the remote server but to no avail. Thank you for your help.

    Hi Nicholas,
    I have this issue aswell, and it has traveled with me over a switch if computers. So I suspect there is something with my user account/profile or similar. My colleague does not have the issue. 
    I also tried the hotfix but I received a message that the hotfix doesn't apply to this computer. The
    pc is a windows 7 Enterprise 64-bit. What can I do to resolve this?
    Any way to reset my Remote-desktop-cache or settings for my user account perhaps, start from scratch. 
    Best regards
    - Björn

Maybe you are looking for