![]() We focus this guide on Windows 10, but the Chrome Remote Desktop app is also available for macOS and older versions of Windows and on Windows 11. Or you can always click the Stop Sharing button to terminate the remote session. Under the “Remote devices” section, click the device running Windows 10 Home to start a remote desktop.Īfter you complete the steps, the remote desktop session will start to continue working from home on another location.Īlso, you can click the arrow button on the middle right of the session to access settings, such as full-screen, scale, input controls, show dual-screens in the remote session, and disconnect the session. Sign in with the Google account you set up the remote desktop. Open the Chrome Remote Desktop page in Chrome. To start a remote desktop connection to a Windows 10 Home computer with Chrome, use these steps: Start remote desktop connection using Chrome Once you complete the steps, you’ll be able to access the computer (as long it’s turned on) from anywhere in the world using Google Chrome on another device whether you’re using the Home or Pro edition of Windows 10. (Optional) Choose a name for your Windows 10 Home computer.Ĭreate a six-digit PIN for remote desktop connection. ![]() This isn't perfect, you need to ensure your secondary user has the relevant access rights to the files and such that you may need to access, or you may have to adopt the awkward practice of leaving your secondary (or "dummy") user logged in when you leave the desk allowing you to use your primary ID over screen sharing, but it may help.Sign in with your Google account (if applicable).Ĭlick the Remote Access from the left pane. If you login with another user who is not already logged in at the hardware display, you get the following message and the ability to use the virtual display which results in being able to do whatever you like without changing the main screen and with no possibility of anyone being able to watch it.If your the user you try to login as is already logged in, then it will always switch to that user and use the hardware display.If no one is logged into the target machine, you will always get the Hardware display showing the normal login screen.Firstly, have another user to your normal one that has the relevant screen sharing options allowed, then login: To use the virtual display, here's what you need to do. This was an easy thing to use on 10.7 but it's been obfuscated rather on 10.8 and the menu item command to switch displays is gone. Anyone else out there manage to get this to work. here but its not working for some reason. Im trying to figure out how to set up my machine so that when I remote in the remote machines display will be hidden and not visible. Using normal screen sharing you have the option of using either the hardware display, or the virtual one. help Curtain Mode for Chrome Remote Desktop. OK, I cannot comment on using ARD, I don't have it, but this may be a suitable workaround, at least in the meantime. Either way, it seems like the solution should be the same. I'm not sure what I'm doing to trigger this situation, but I'm definitely not logging out. This will leave the Mac inaccessible to the Remote Desktop app and even a physical user of the computer, with the large lock icon still on the screen of the target Mac. Even if the screen is smashed, but the device. One way to reproduce this: Log in to the target Mac with Remote Desktop, initiate Curtain mode, and then after finishing whatever work was to be done, log out the user on the target Mac while still under Curtain mode. That will allow you to control the phone from computer with a mouse. My question: is there a way to successfully unlock a Mac that's stuck on the ARD lock screen, using ssh or otherwise? to tell all my running applications to gracefully quit, then I run shutdown -r now to reboot the machine. Eventually, I resort to using osascript -e. None of these things seem to unlock the screen. I've tried killing the ARDAgent process, the screen lock process (I can't recall the name), and anything else I can find with "ard" or "remote" in the process name. I usually try ssh-ing into the Mac from another machine and killing processes. Despite now being physically present in front of the Mac, I can't find a way to unlock the screen. (Latest ARD and OS X 10.8.2 on both machines.) When this happens, I come in to work the next day to find the big lock icon and message on my Mac's screen. ![]() Unfortunately, there's a bug of some kind that causes the remote Mac's screen to stay locked, even after I've disconnected from it. My work Mac's screen shows a big lock icon and a message while I'm remotely controlling it from my home Mac using Apple Remote Desktop (ARD). I use this when I connect to my work Mac from my home Mac. Apple Remote Desktop has a "curtain" feature that a remote client can use to lock the screen of the Mac that's being remotely controlled.
0 Comments
Leave a Reply. |