Topics Map > Windows
Topics Map > Mac
Keyboard shortcuts for working in a remote desktop Windows Machine from your MacBook In this blog post, I am going to share with you how to get the missing keyboard keys that let you work in MS Windows via the remote desktop client under Mac OS X with the MacBook’s keyboard. Windows Remote Desktop for Mac uses Microsoft’s Remote Desktop Protocol, built into Windows 10, to display your Windows desktop on your macOS screen. You can run Windows apps, change settings, and share files and folders between your Mac and Windows devices. Im running Mac OS X Yosemite and just upgraded to Win10. I used to use the Remote Desktop Connection App but after the upgrade to Win10, I couldnt connect from my Mac. I installed Microsoft Remote Desktop and now I can connect to my Win 10 machine with no issues. Thanks for the quick fix! Microsoft RDP client for Mac does not currently support dual displays for Windows 7 Pro targets. Windows 7 Pro will support multiple monitors but only from the Windows mstsc.exe command line. You invoke the session using the mstsc command line using the /span option. You have to have two displays, locally, that are running at the same.
Sharing your screen remotely is a convenient way to access another computer as if you’re sitting in front of it. OS X and Windows have this ability built right into them, meaning you can easily share your Mac’s screen with Windows PCs, and vice versa.
Signum driver.
Connecting to Windows PC Clients from a Mac
To connect to a Windows PC, you must first turn on remote connections. Open the System Properties and click the “Remote” tab, then make sure “Allow remote connections to this computer” is enabled.
You also want to make sure you install the Microsoft Remote Desktop client on your Mac. It is available in the App Store.
Remote Desktop will be installed in your Mac’s Application’s folder. In our example, we’ve already set up a user profile, which is ready for action. Let’s take a moment, however, to click “Edit” and show you what’s involved.
Next to “Connection name” we give it a friendly name while the “PC name” is either the name we gave our target PC or its IP address.
We don’t worry about configuring a gateway because we’re connecting to our PC within our local network. Also, if you do not want to enter your user name and password every time you connect, you can add them to the “Credentials.” Not entering any credentials means that when you connect to your Windows machine, you will need to log into an account.
If you want to know what your PC’s name and/or IP address is, you need to check. Use the keyboard shortcut “Windows + R” and then type “cmd” to open a command prompt. In the command prompt, type “ipconfig” and hit “Return.” You want to use the IPv4 address it gives you.
If you can’t remember what you named your computer, you can find that information on the “System” control panel.
The rest of the Remote Desktop connection’s settings concern resolution, colors, and full screen options.
When you connect to a new client, you’ll likely see a Verify Certificate dialog. Click “Continue” to connect.
If you don’t want to see this warning dialog in the future, click “Show Certificate” and then check the “Always trust …” option as shown below.
To confirm changes to your certificate trust settings, you will need to enter your system password.
Remember, if you didn’t previously enter anything in the connection credentials, you will see the login screen when you first connect. Once you’ve successfully connected to your Windows PC from your Mac, your Windows desktop will appear.
As we mentioned, being able to connect to a Windows machine is a pleasant convenience. For example, your Windows PC may be a super beefy machine you use to do compiling or rendering. You can use remote desktop to check on a job’s progress or start tasks without actually being physically at the machine.
Connecting to a Mac from a Windows PC
Connecting to a Mac from a Windows PC is a little different. You’re not going to be able to use Remote Desktop, but that’s okay because there’s a free client called RealVNC viewer that does the trick nicely.
Just like with Windows, you first have to set up your Mac for screen sharing. Open the “Sharing” preference panel and check the box next to “Screen Sharing.”
Click “Computer Settings…” and make sure “VNC viewers may control screen with password” is checked. Then enter a simple password.
The VNC Viewer requires installation, but you don’t have to sign up for an account to use it.
Recall from the earlier screenshot that our Mac’s screen can be accessed at 192.168.0.118 or Matt-Air.local. If you’re unsure how to access your Mac, go back to your Sharing preferences and double-check the information on the Screen Sharing settings.
We enter “192.168.0.118” in our VNC client and leave the encryption as it is.
We return to our connection and click the “Connect” button. An authentication box will appear where you will need to enter the simple password you created in the Sharing preferences on your Mac.
When you connect to the target Mac, you will also need to log into a (presumably yours) user account, just like we had to do with Windows (if we didn’t supply our credentials).
Once logged in, your Mac desktop will now appear in the VNC Viewer window in the same state as you left it.
If you mouse to the top-middle of the window, you can spawn extra controls, which when you hover will give you a tooltip explaining what each one does.
You’ll find handy shortcuts to close and save the connection, as well as to change options, and a full-screen button so your shared desktop fills the screen.
On the Mac side of things, a Screen Sharing icon will appear in the menu bar. This lets you quickly and easily access the Screen Sharing preferences or disconnect clients.
It’s important to remember that sharing a computer screen is really only suited for short bits of work. If you were trying to remotely repair something or show another user how to do something, it’s ideal, but to get any meaningful work done, not so much. You will always experience a little bit of lag and stutter, and there’s not a whole lot you can do about that.
Like we said, however, it’s not intended for heavy-duty work. Keep in mind also, we’re only sharing our screens locally, which means that if you leave the house, say to go get coffee, and you realize you need to connect to a machine at home, you’ll need to know how to connect to it through your router.
REMOTEAPP
For remote desktop (terminal server) application hosting where the user is logging into a full desktop session, MAC users should have a good experience and there are Remote Desktop Connection Clients that can be downloaded for MACs, iphone, and ipad. (The Remote Desktop Connection Client is preloaded on all Windows machines and doesn’t require a download to use it). The Clients for MACs/Apple can be found here: https://www.RiptideHosting.com/blog/remote-desktop-connection-client-for-macs/
Windows 10 On Mac Pro
RemoteApp is an optional feature of Remote Desktop Services where users are not provided a desktop session but rather can only open a specified application. This feature doesn’t work well with MAC users in Windows 2008R2 due to the limitations below. It should work better in Windows 2012R2 for MAC users but only if using the RDweb login option. We have many MAC users using our Remote Desktop hosting although most are using full desktop sessions instead of RemoteApp. There are other options instead of RemoteApp as described toward the end of this post.
With RemoteApp, you can distribute a RDP file to a user (Windows 2008R2 only – “RDP distributable file” – this option is not available in Windows 2012R2) or you can set it up for users to access the specified program via a URL. The user can open the specified application but does not get a full desktop session to save/share files, etc.
- RD Web URL – When enabled, you can access the RD Web Access Web site at https://IPaddress/rdweb . In 2008R2, the website requires that the client browser has ActiveX enabled which basically limits usage to Internet Explorer and therefore excludes MAC users. (as noted here — https://technet.microsoft.com/en-us/library/cc731508.aspx). In 2012R2, the RD Web Access website no longer requires ActiveX and is supposed to work with many more browser options. However, Server 2012R2 does require that the Active Directory Domain Controller role be installed to use RemoteApp whereas it is not required in Windows 2008R2.
- Create RDP file via the RemoteApp Wizard to distribute to users. This works easily to create the file and other PC users should be able to open it easily. MAC users generally have issues when they try to open the file where the system doesn’t recognize it. Note: Windows Server 2012R2 no longer has this option to create the RemoteApp distributable file.
If you are going to use RemoteApp in 2008R2, contact us for additional instructions and tips that we can provide.
OTHER OPTIONS
Macbook Rdp To Windows 10 Download
- Launch a program automatically upon login. You can specify a program to run automatically upon login. You can do this by individual user (profile/properties tab), for all users in RD Session Host configuration and in Group Policy. See our post here: https://www.RiptideHosting.com/blog/how-to-launch-a-program-automatically-when-logging-into-remote-desktop-server/
Using Windows On Macbook Pro
- User full desktop sessions but configure group policies to limit access to certain things, remove icons, prevent access to drives, etc.