Mstsc Mac

Posted onby
-->Mstsc

Microsoft Remote Desktop Connection Client for Mac Version 2.1.0 (100825) Computer: computerName.school.edu /console. This is similar to PC syntax: C: Windows System32 mstsc.exe /v: computerName/admin.

Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2, Windows Server 2016

You can use the Remote Desktop client for Mac to work with Windows apps, resources, and desktops from your Mac computer. Use the following information to get started - and check out the FAQ if you have questions.

Note

  • Curious about the new releases for the macOS client? Check out What's new for Remote Desktop on Mac?
  • The Mac client runs on computers running macOS 10.10 and newer.
  • The information in this article applies primarily to the full version of the Mac client - the version available in the Mac AppStore. Test-drive new features by downloading our preview app here: beta client release notes.

Get the Remote Desktop client

Follow these steps to get started with Remote Desktop on your Mac:

  1. There’s no need to bother upgrading macOS when all you want to do is RDP to another computer. While the old Remote Desktop 8 (which is compatible with older macOS versions) is no longer available on the Mac App Store or direct from Microsoft, you can still download it direct from macsx 100% malware-free — just check out this article.
  2. This content applies to Windows Virtual Desktop with Azure Resource Manager Windows Virtual Desktop objects. If you're using Windows Virtual Desktop (classic) without Azure Resource Manager objects, see this article.
  1. Download the Microsoft Remote Desktop client from the Mac App Store.
  2. Set up your PC to accept remote connections. (If you skip this step, you can't connect to your PC.)
  3. Add a Remote Desktop connection or a remote resource. You use a connection to connect directly to a Windows PC and a remote resource to use a RemoteApp program, session-based desktop, or a virtual desktop published on-premises using RemoteApp and Desktop Connections. This feature is typically available in corporate environments.

Download Microsoft Remote Desktop Application

What about the Mac beta client?

We're testing new features on our preview channel on AppCenter. Want to check it out? Go to Microsoft Remote Desktop for Mac and select Download. You don't need to create an account or sign into AppCenter to download the beta client.

If you already have the client, you can check for updates to ensure you have the latest version. In the beta client, select Microsoft Remote Desktop Beta at the top, and then select Check for updates.

Add a workspace

Subscribe to the feed your admin gave you to get the list of managed resources available to you on your macOS device.

To subscribe to a feed:

  1. Select Add feed on the main page to connect to the service and retrieve your resources.
  2. Enter the feed URL. This can be a URL or email address:
    • This URL is usually a Windows Virtual Desktop URL. Which one you use depends on which version of Windows Virtual Desktop you're using.
      • For Windows Virtual Desktop (classic), use https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx.
      • For Windows Virtual Desktop, use https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery.
    • To use email, enter your email address. This tells the client to search for a URL associated with your email address if your admin configured the server that way.
  3. Select Subscribe.
  4. Sign in with your user account when prompted.

After you've signed in, you should see a list of available resources.

Once you've subscribed to a feed, the feed's content will update automatically on a regular basis. Resources may be added, changed, or removed based on changes made by your administrator.

Export and import connections

You can export a remote desktop connection definition and use it on a different device. Remote desktops are saved in separate RDP files.

To export an RDP file:

  1. In the Connection Center, right-click the remote desktop.
  2. Select Export.
  3. Browse to the location where you want to save the remote desktop RDP file.
  4. Select OK.

To import an RDP file:

  1. In the menu bar, select File > Import.
  2. Browse to the RDP file.
  3. Select Open.
Mstsc command mac

Add a remote resource

Remote resources are RemoteApp programs, session-based desktops, and virtual desktops published using RemoteApp and Desktop Connections.

  • The URL displays the link to the RD Web Access server that gives you access to RemoteApp and Desktop Connections.
  • The configured RemoteApp and Desktop Connections are listed.

To add a remote resource:

  1. In the Connection Center select +, and then select Add Remote Resources.
  2. Enter information for the remote resource:
    • Feed URL - The URL of the RD Web Access server. You can also enter your corporate email account in this field – this tells the client to search for the RD Web Access Server associated with your email address.
    • User name - The user name to use for the RD Web Access server you are connecting to.
    • Password - The password to use for the RD Web Access server you are connecting to.
  3. Select Save.

The remote resources will be displayed in the Connection Center.

Mstsc Mac

Connect to an RD Gateway to access internal assets

A Remote Desktop Gateway (RD Gateway) lets you connect to a remote computer on a corporate network from anywhere on the Internet. You can create and manage your gateways in the preferences of the app or while setting up a new desktop connection.

To set up a new gateway in preferences:

  1. In the Connection Center, select Preferences > Gateways.
  2. Select the + button at the bottom of the table Enter the following information:
    • Server name – The name of the computer you want to use as a gateway. This can be a Windows computer name, an Internet domain name, or an IP address. You can also add port information to the server name (for example: RDGateway:443 or 10.0.0.1:443).
    • User name - The user name and password to be used for the Remote Desktop gateway you are connecting to. You can also select Use connection credentials to use the same user name and password as those used for the remote desktop connection.

Manage your user accounts

When you connect to a desktop or remote resources, you can save the user accounts to select from again. You can manage your user accounts by using the Remote Desktop client.

To create a new user account:

  1. In the Connection Center, select Settings > Accounts.
  2. Select Add User Account.
  3. Enter the following information:
    • User Name - The name of the user to save for use with a remote connection. You can enter the user name in any of the following formats: user_name, domainuser_name, or [email protected]
    • Password - The password for the user you specified. Every user account that you want to save to use for remote connections needs to have a password associated with it.
    • Friendly Name - If you are using the same user account with different passwords, set a friendly name to distinguish those user accounts.
  4. Select Save, then select Settings.

Customize your display resolution

You can specify the display resolution for the remote desktop session.

  1. In the Connection Center, select Preferences.
  2. Select Resolution.
  3. Select +.
  4. Enter a resolution height and width, and then select OK.

To delete the resolution, select it, and then select -.

Displays have separate spaces

If you're running Mac OS X 10.9 and have disabled Displays have separate spaces in Mavericks (System Preferences > Mission Control), you need to configure this setting in the Remote Desktop client using the same option.

Drive redirection for remote resources

Drive redirection is supported for remote resources, so that you can save files created with a remote application locally to your Mac. The redirected folder is always your home directory displayed as a network drive in the remote session.

Note

In order to use this feature, the administrator needs to set the appropriate settings on the server.

Use a keyboard in a remote session

Mac keyboard layouts differ from the Windows keyboard layouts.

  • The Command key on the Mac keyboard equals the Windows key.
  • To perform actions that use the Command button on the Mac, you will need to use the control button in Windows (for example Copy = Ctrl+C).
  • The function keys can be activated in the session by pressing additionally the FN key (for example, FN+F1).
  • The Alt key to the right of the space bar on the Mac keyboard equals the Alt Gr/right Alt key in Windows.

By default, the remote session will use the same keyboard locale as the OS you're running the client on. (If your Mac is running an en-us OS, that will be used for the remote sessions as well.) If the OS keyboard locale is not used, check the keyboard setting on the remote PC and change it manually. See the Remote Desktop Client FAQ for more information about keyboards and locales.

Support for Remote Desktop gateway pluggable authentication and authorization

Windows Server 2012 R2 introduced support for a new authentication method, Remote Desktop Gateway pluggable authentication and authorization, which provides more flexibility for custom authentication routines. You can now try this authentication model with the Mac client.

Important

Custom authentication and authorization models before Windows 8.1 aren't supported, although the article above discusses them.

To learn more about this feature, check out https://aka.ms/paa-sample.

Tip

Questions and comments are always welcome. However, please do NOT post a request for troubleshooting help by using the comment feature at the end of this article. Instead, go to the Remote Desktop client forum and start a new thread. Have a feature suggestion? Tell us in the client user voice forum.

Mstsc.exe Mac

Hi, my name is Kim and I herd cats.. where cats in this case are High DPI issues. I've been working to get more information out there on DPI issues, like bribing the Product Group to write some awesome technical blogs about the fun of High DPI. (Ok - didn't have to bribe) getting public KB articles and other posts published and fielding questions from various groups on the status of many of the DPI problems. DPI and RDP is one that has come up often of late and I wanted write this to help people have the best possible experience with Windows 10, high resolution monitors and remote desktop connections.

I setup Microsoft's remote desktop client with my work PC using a mac. I have it setup and it is working perfectly but only on one monitor. I would like to set it up to use two monitors. Overview With the Microsoft Remote Desktop app, you can connect to a remote PC and your work resources from almost anywhere. Experience a rich Windows experience with RemoteFX in a Remote Desktop client designed to help you get your work done wherever you are. In a connection configured with the monitor-spanning feature, Remote Desktop displays the remote system in a window on one monitor but allows you to drag or span that window across multiple monitors. • Multi Monitor Support. Microsoft Remote Desktop (RDP) - Gateway Credentials. Use Thinstuff TSX Connection client. Use Thinstuff TSX for seamless mode. Enable super pan. Enabling super pan will take the entirety of your screen for the RDM session. Oct 15, 2014 Hi, I installed the Remote Desktop Client App from the Appstore on my OS X 10.8 Lion. There was a very nice Feature 'Use All Monitors'. Since I have installed the Update of the Application under OS X 10.9 Mavericks, the Feature was removed.

Nov 18, 2014 RDCMan manages multiple remote desktop connections Try. Remote Desktop Connection Manager 2.7. Users using Windows XP or Windows Server 2003 will need to obtain version 6 or newer of the Remote Desktop Connection client software. See the related downloads for more information.

Disclaimer - I know High DPI issues can be pretty complicated and ugly. But many DPI issues can be mitigated. This article isn't meant to address the difficulties in truly fixing DPI issues in code or discuss known bugs. It is meant to offer best practices to result in optimal performance for Remote Desktop sessions using Windows 10 1607 with multiple monitors.

For reference and for examples in this blog, I'm use a Surface Book with a Surface dock connected to a Dell 34' wide 4k monitor. I also connect to several remote systems, both Hyper-V VMs and physical systems. I'll stick with Surface Dock for simplicity and familiarity, but this applies to any high resolution devices and companion hardware.

Key points

  1. Always be up to date
    1. Third party apps
  2. Get to Baseline before making adjustments, registry hacks, judgements
    1. Logoff the device
    2. Setup hardware as you plan use it (connect all monitors, connect to the dock, etc)
    3. Logon

Definitions

  • Bad - I am keeping it generic here. DPI behavior can be any combination of large, small, fuzzy or crisp. The blogs go into more depth on general High DPI behavior:
  • Local system - the computer making the call
  • Remote system - the computer answering the call
  • Disconnect - Disconnect breaks the connection between the two systems. It does not logoff the remote session. Everything is left running.
  • Logoff - Shuts down all programs running on the system and ends the Winlogon session.

Tools I'm using

  1. Remote Desktop Connection MSTSC.exe (Win32)

User scenarios

One of the key considerations to avoid or mitigate DPI issues is knowing your scenarios. If you are considering buying a Surface Book, think of how you will be using the device. If it’s a sit-on-couch-binge-Netflix device/take notes in a meeting device, you won't notice any DPI issues. If you get a Surface Dock to go with it and have it docked, lid closed, most of the time, you won't see many DPI issues. But if you move around, dock/undock or connect to other systems via remote desktop protocol (RDP), or both, you'll probably run into Bad behavior.

The Bad behavior comes into play for two reasons. Hardware configuration(monitor) changes or the difference in resolution between the Surface and connected monitors is large. The latter can be addressed by using a monitor that matches or comes close to the resolution of the device. For example, my Surface Book does 3000x2000 and my external monitor does 3440x1440. When I connect to the dock, most applications look fine and will move between the monitors without noticeable burps. To combat the first issue, hardware changes, it is always best to logoff off, connect the dock, then logon and configure the displays as you want to use them. Key: You can return to this baseline at any time by logging off, docking, and logging on.

This is key. Winlogon starts when a user logs on. At that time, the existing hardware configuration is noted and DPI for that session is set. When applications are launched they use this information. When the hardware configuration changes mid-session, DPI is revised, but many applications are (currently) not aware enough to adjust. This is admittedly over-simplifying how it works, but the easiest way to think about it is that DPI is tied to the logon session. Key: If monitors change then create a new windows session = best experience.

Let's say you get a brand new Surface Book and Dock and 4k external monitor to connected to the dock - there's still some housekeeping to do (after you take time to enjoy the unboxing and new device smell - brand new keyboards are awesome and will never be that clean again!) Updates! Every release of Windows 10 has had DPI improvements. It's always best to be at the latest (currently its 1607. Which stands for year 2016, month 07. 1511 was November 2015, the first version, 1507 is July 2015 etc etc. This numbering convention will continue with future releases) Cumulative updates are also important. They typically do not introduce new features but they may provide bug fixes that improve behavior. Then, finally, hardware updates. Firmware updates for the Surface Book/Pro series will come down via Windows Updates. You will also need to check for updates to the Surface Dock. Key: always make sure you're troubleshooting new issues, not something that has already been fixed.

Remote desktop adds another layer of complexity to the situation. There are two RDP tools I'll compare here. First there is the Win32 app 'Remote Desktop Connection' or MSTSC.exe. This is an older application and does not scale well itself.

The second is Remote Desktop Preview App and is available in the Windows Store. There is both a normal and preview beta version. The one I'm working with here is the Preview version. Modern apps scale for free so this RDP client will always present itself as the right size.

Best RDP results with single monitors

Single monitor RDP scenarios are mostly unexciting when it comes to DPI issues so I'll keep it short.

Using MSTSC from a Surface Book to a remote system is not too problematic. The MSTSC client itself will behave on a single monitor. The behavior of the remote system will vary depending on the resolution of that system. You can control that in MSTSC settings under Display.

The same is true for the Remote Desktop Preview. Connections will be fine with little to no DPI issues. You can also control the display options for each session.

The only DPI issue in single monitor connections is more of an after-effect of an RDP session. Let's say you're working from home on the Surface Book and you RDP to your computer in the office. Everything looks great. When you're done you disconnect the RDP session instead of logging off the session.

The next day you go into the office and logon to that computer directly. The session is still active from yesterday, still thinking it is displaying to a 3000x2000 monitor. The display will be Bad especially if the monitor is much lower resolution. Logging off/on will fix it. Again, this is because the hardware configuration for that Windows session changed and cycling a logon will force the DPI to reset.

Best RDP results with multiple monitors

It gets a bit trickier when you have multiple monitors setup on your local system and use RDP.

To start:

  1. Know what monitor you want to use for the remote session.
  2. Know what monitor is marked as your main monitor.
  • I've found that I get the best results when I check “ Make this my Main Monitor” on the monitor I selected for #1

External Monitor

3. Use Microsoft Remote Desktop App Preview instead of MSTSC.exe

Once you have the above sorted out, make sure the configuration is lookin' good. This goes back to the Key Points above:

  • Always be up to date - Software and hardware
  • Get to Baseline - Log off, configure the hardware, logon

Next, fire up the connection to the remote machine. When you make that connection, remember you might be connecting to an existing session. Before making any judgements or adjustments to the display settings in the Remote Desktop app make sure to log off the remote session (not disconnect) and log back on. Once that is done both the local and remote sessions will be optimized for your current hardware configuration.

At this point, if the remote session view isn't quite your jam, make adjustments to the display settings options. Make sure to log off the remote session each time until it looks just right.

I typically match up the Windows Start button icons and taskbar items to make sure I'm close to good. You can see the MSTSC frame does not scale well, but the remote desktop can be adjusted to display very close to the local desktop.

Random Tidbits

Remote Desktop Preview App. This app is in beta and while some think that means buggy, it also means there is active worked being done to it. Since it's an app in the Store, it will update automagically.

And since it’s a modern app you can move it from monitor to monitor and it will adjust and scale on the fly.

Sliding a modern app from the 34' to the Surface Book, you will see there is a critical mass point where the app tips over to use the display settings on the Book. Top of the screen is my external monitor, bottom is the Surface Book. Captured with SnagIt

During the move: Bridging the app between 2 screens may be messy depending on which screen it is using for display settings. Here's a shot of the Remote Desktop Preview moving to the larger screen. The App still is using the Surface Book's settings, as you can see the Start Button and the Remote Desktop frame are right-sized, while the taskbar on the larger screen seems tiny. One the App is completely on the larger screen it will then adjust to look great there.

You can also resize the window as needed. Note: I have seen the remote session screen get stuck while resizing. This is not a feature, but part of the wonderful Beta-ness.

Larger Remote session

The app saves desktop connections (MSTSC does this too, but I like the options in the App better) This means you can create multiple connections to the same remote machine. Each connection can be setup to have unique display (and more) settings. For example: I'm working from hotel, no extra monitors or dock and I connect remotely to my office. I can setup that RDP connection and save it as Computer-Solo and I set the display settings to 'Choose for me'. But when I work from home I have multiple monitors, a better connection and I work mainly on my external monitor. I save this connection as Computer-Multimon.

Check point endpoint security client for mac os x. Simplify endpoint security management with unified policies, centralized reporting and actionable forensics Check Point Endpoint Policy Management gives security administrators the power to enforce, manage, report and educate users with one console.

Summary

I love long blogs posts as much as I love DPI issues. (sorry!) But devil is in the details when it comes to conquering Bad behavior. I can't stress some items enough. Various hardware/software configurations can make it difficult to clearly identify exactly what specific pains people are feeling. I've reviewed a majority of DPI support cases that have come in on Windows 10 since launch and know it's hard to address all the Bad behavior.

But every Windows 10 release is a step forward. Skype for Business and Office 2016 updates have be released and Modern/UWP apps scale for free.

  • There is no one 'Just fix it' button for DPI issue. (We'd all love a magic Fix it!)
  • Always check for the latest software/hardware versions and updates.
  • Always check to see if the issue is there at Baseline - monitors setup as needed, new logon session.
  • Use the new Remote Desktop Preview (beta) app
  • If you make registry changes to effect DPI behavior - don’t forget about them. Those changes do come with caveats. Roll registry changes back to default settings if you notice odd behavior and test DPI performance without them.
  • If you do find an issue, check Windows Feedback app to see if someone has reported it, if so, vote it up! If not - describe exactly how to reproduce the behavior, hardware configuration, screenshots help! More Feedback votes = Higher priority!

DPI reference links:

macOS
66,712

Easily connect to remote Windows PCs

With Remote Desktop Connection Client 2, you can quickly, simply and securely connect to Windows-based PCs to access Windows-based files, applications, devices, and networks from your Mac.

One Mac, unlimited Windows

New Multiple Session Support gives Mac users simultaneous access to multiple Windows-based PCs or to a network server that hosts remote applications and files. Since it works with Vista and is a Universal application, Remote Desktop Connection Client 2 is compatible with the latest technologies on Windows and Mac platforms.

A more Mac-like experience

A redesigned user interface makes this application more customizable. Create your own keyboard shortcuts; and even access and change preferences during active sessions.

Print everything off your Mac

Access and print from Windows applications to any printer that can be configured from your Intel- or PowerPC-based Macs.

Get fast updates and easy help

Microsoft Error Reporting Tool and Microsoft AutoUpdate are included so you can anonymously submit data on software related issues and get software updates as soon as they are available. Remote Desktop Connection Client 2 also takes advantage of the new Helpviewer and improved help topics for quick access to fresh online product help from within the application.

Reduce security breaches

Mstsc Command Mac

Network Level Authentication (NLA) is a new authentication method in Windows Vista that offers security enhancements that can help to protect the remote computer from hackers and malicious software. It completes user authentication before you establish a full Remote Desktop Connection. Please see Windows Help for more details on network level authentication.

What's New:

Microsoft Remote Desktop Connection Client For Mac Multiple Monitors

  • You can download version 10.2.9 and update to 10.2.11 if you don't want to go through the Appstore.

Remote Desktop Connection Mac Download