-->
![Offline Offline](/uploads/1/2/6/5/126593997/417501378.png)
![Microsoft Remote Desktop Mac Offline Installer Microsoft Remote Desktop Mac Offline Installer](/uploads/1/2/6/5/126593997/120586851.jpg)
- Teamviewer
- Microsoft Remote Desktop Beta Mac
- Microsoft Remote Desktop Mac Offline Installer Windows 10
- Microsoft Remote Desktop Mac Offline Installer Windows 7
- Microsoft Remote Desktop On Mac
- Microsoft Remote Desktop App Mac
Applies to: Windows 10, Windows 10 IoT Enterprise, and Windows 7
Sep 04, 2016 Software update using Apple Remote Desktop Anyone has success doing Office update through Apple Remote Desktop while Office is running? I have read somewhere someone suggested Office needs to be closed during update through Apple Remote Desktop but I just want to know if it is possible to do it when Office is running. Remote Server Administration Tools cannot be installed on Windows RT, computers with an Advanced RISC Machine (ARM) architecture, or other system-on-chip devices. Remote Server Administration Tools for Windows 10 runs on both x86- and x64-based editions of the full release of Windows 10, Professional, Enterprise or Education editions. Microsoft Remote Desktop. Use the Microsoft Remote Desktop app to connect to a remote PC or virtual apps and desktops made available by your admin. The app helps you be productive no matter where you are. Getting Started Configure your PC for remote access first. Oct 19, 2013 To install Remote Desktop, the Mac App Store will download an installer package from Apple, install Remote Desktop, then delete the installer package as part of the post-installation clean-up. However, it is possible to make the App Store leave behind a copy. Microsoft Remote Desktop2.1.1. Microsoft Remote Desktop is one of the best remote desktop clients out there in the market. It now has a Mac version available as well. The Mac version helps users to connect their PC to their Mac and work seamlessly across the machines. The setup of this software is easy to do.
You can use the Remote Desktop client for Windows Desktop to access Windows apps and desktops remotely from a different Windows device.
Note
- This documentation is not for the Remote Desktop Connection (MSTSC) client that ships with Windows. It's for the new Remote Desktop (MSRDC) client.
- This client currently only supports accessing remote apps and desktops from Windows Virtual Desktop.
- Curious about the new releases for the Windows Desktop client? Check out What's new in the Windows Desktop client
Install the client
Choose the client that matches the version of Windows. The new Remote Desktop client (MSRDC) supports Windows 10, Windows 10 IoT Enterprise, and Windows 7 client devices.
You can install the client for the current user, which doesn't require admin rights, or your admin can install and configure the client so that all users on the device can access it.
Once you've installed the client, you can launch it from the Start menu by searching for Remote Desktop.
Update the client
You'll be notified whenever a new version of the client is available as long as your admin hasn't disabled notifications. The notification will appear in either the Connection Center or the Windows Action Center. To update your client, just select the notification.
You can also manually search for new updates for the client:
- From the Connection Center, tap the overflow menu (...) on the command bar at the top of the client.
- Select About from the drop-down menu.
- Tap Check for updates.
- If there's an update available, tap Install update to update the client.
Feeds
Get the list of managed resources you can access, such as apps and desktops, by subscribing to the feed your admin provided you. When you subscribe, the resources become available on your local PC. The Windows Desktop client currently supports resources published from Windows Virtual Desktop.
Subscribe to a feed
- From the main page of the client, also known as the Connection Center, tap Subscribe.
- Sign in with your user account when prompted.
- The resources will appear in the Connection Center grouped by Workspace.
You can launch resources with one of the following methods:
- Go to the Connection Center and double-click a resource to launch it.
- You can also go to the Start menu and look for a folder with the Workspace name or enter the resource name in the search bar.
Workspace details
After subscribing, you can view additional information about a Workspace on the Details panel:
- The name of the Workspace
- The URL and username used to subscribe
- The number of apps and desktops
- The date/time of the last update
- The status of the last update
Accessing the Details panel:
- From the Connection Center, tap the overflow menu (...) next to the Workspace.
- Select Details from the drop-down menu.
- The Details panel appears on the right side of the client.
After you've subscribed, the Workspace will update automatically on a regular basis. Resources may be added, changed, or removed based on changes made by your admin.
You can also manually look for updates to the resources when needed by selecting Update now from the Details panel.
Unsubscribe from a feed
This section will teach you how to unsubscribe from a feed. You can unsubscribe to either subscribe again with a different account or remove your resources from the system.
- From the Connection Center, tap the overflow menu (...) next to the Workspace.
- Select Unsubscribe from the drop-down menu.
- Review the dialog box and select Continue.
Managed desktops
Workspaces can contain multiple managed resources, including desktops. When accessing a managed desktop, you have access to all the apps installed by your admin.
Desktop settings
You can configure some of the settings for desktop resources to ensure the experience meets your needs. To access the list of available settings right-click on the desktop resource and select Settings.
The client will use the settings configured by your admin unless you turn off the Use default settings option. Doing so allows you to configure the following options:
- Use multiple displays switches the desktop session between using a single or multiple displays.
- Select the displays to use for the session specifies which local displays to use for the session. All selected displays must be adjacent to each other. This setting is automatically disabled when you use a single display.
- Start in full screen determines whether the session will launch in full-screen or windowed mode. This setting is automatically enabled when you use multiple displays.
- Update the resolution on resize makes the Remote Desktop resolution automatically update when you resize the session in windowed mode. When disabled, the session always remains at whichever resolution you specify in Resolution. This setting is automatically enabled when you use multiple displays.
- Resolution lets you specify the resolution of the remote desktop. The session will retain this resolution for its entire duration. This setting is automatically disabled if the resolution is set to update on resize.
- Change the size of the text and apps specifies the size of the content of the session. This setting only applies when connecting to Windows 8.1 and later or Windows Server 2012 R2 and later. This setting is automatically disabled if the resolution is set to update on resize.
- Fit session to window determines how the session is displayed when the resolution of the remote desktop differs from the size of the local window. When enabled, the session content will be resized to fit inside the window while preserving the aspect ratio of the session. When disabled, scrollbars or black areas will be shown when the resolution and window size don't match.
Provide feedback
Have a feature suggestion or want to report a problem? Tell us using the Feedback Hub. You can also access the Feedback Hub through the client:
- From the Connection Center, tap the Send feedback option on the command bar at the top of the client to open the Feedback Hub app.
- Enter the required information in the Summary and Details fields. When you're done, tap Next.
- Select whether it's a Problem or Suggestion.
- Check to see if the category is in Apps > Remote Desktop. If it is, tap Next.
- Review the existing feedback topics to see if someone else has reported the same problem. If not, select Make a new bug, then tap Next.
- On the next page, you can give us more information so we can help you solve the problem. You can write more detailed information, submit screenshots, and even create a recording of the problem to show us what happened. To make a recording, select Start recording, then do what you did up to the point where the problem happened. When you're done, return to the Feedback Hub and select Stop recording.
- When you're satisfied with the information, tap Submit.
- On the 'Thank you for your feedback!' page, tap Share my feedback to generate a link to your feedback that you can share with others as needed.
Access client logs
You might need the client logs when investigating a problem.
To retrieve the client logs:
- Ensure no sessions are active and the client process isn't running in the background by right-clicking on the Remote Desktop icon in the system tray and selecting Disconnect all sessions.
- Open File Explorer.
- Navigate to the %temp%DiagOutputDirRdClientAutoTrace folder.
We designed Visual Studio 2017 to work well in a variety of network and computer configurations. While we recommend that you try the Visual Studio web installer—which is a small file and allows you to stay current with all the latest fixes and features—we understand that you might not be able to.
We designed Visual Studio 2019 to work well in a variety of network and computer configurations. While we recommend that you try the Visual Studio web installer—which is a small file and allows you to stay current with all the latest fixes and features—we understand that you might not be able to.
For example, you might have an unreliable internet connection or one that has low bandwidth. If so, you have a few options: You can use the new 'Download all, then install' feature to download the files before you install, or you can use the command line to create a local cache of the files.
Note
Teamviewer
If you are an enterprise administrator who wants to perform a deployment of Visual Studio to a network of client workstations that are firewalled from the internet, see our Create a network installation of Visual Studio and Install certificates required for Visual Studio offline installation pages.
Use the 'Download all, then install' feature
New in version 15.8: After you download the web installer, select the new Download all, then install option from the Visual Studio Installer. Then, continue with your installation.
After you download the web installer, select the new Download all, then install option from the Visual Studio Installer. Then, continue with your installation.
We designed the 'Download all, then install' feature so that you can download Visual Studio as a single installation for the same computer on which you downloaded it. That way, you can safely disconnect from the web before you install Visual Studio.
Important
Do not use the 'Download all, then install' feature to create an offline cache that you intend to transfer to another computer. It's not designed to work that way.
If you want to create an offline cache to install Visual Studio on another computer, see the Use the command line to create a local cache section of this page for information about how to create a local cache, or the Create a network installation of Visual Studio page for information about how to create a network cache.
If you want to create an offline cache to install Visual Studio on another computer, see the Use the command line to create a local cache section of this page for information about how to create a local cache, or the Create a network installation of Visual Studio page for information about how to create a network cache.
Use the command line to create a local cache
After you download a small bootstrapper, use the command line to create a local cache. Then, use the local cache to install Visual Studio. (This process replaces the ISO files that were available for previous versions.)
Here's how.
Step 1 - Download the Visual Studio bootstrapper
You must have an internet connection to complete this step.
To get a bootstrapper for Visual Studio 2017, see the Visual Studio previous versions download page for details on how to do so.
Your setup executable—or to be more specific, the bootstrapper file—should match or be similar to one of the following.
Edition | Filename |
---|---|
Visual Studio Community | vs_community.exe |
Visual Studio Professional | vs_professional.exe |
Visual Studio Enterprise | vs_enterprise.exe |
Visual Studio Build Tools | vs_buildtools.exe |
Start by downloading the Visual Studio bootstrapper for your chosen edition of Visual Studio. Your setup file—or bootstrapper—will match or be similar to one of the following.
Edition | File |
---|---|
Visual Studio Community | vs_community.exe |
Visual Studio Professional | vs_professional.exe |
Visual Studio Enterprise | vs_enterprise.exe |
Visual Studio Build Tools | vs_buildtools.exe |
Tip
If you previously downloaded a bootstrapper file and want to verify its version, here's how. In Windows, open File Explorer, right-click the bootstrapper file, choose Properties, choose the Details tab, and then view the Product version number. To match that number to a release of Visual Studio, see the Visual Studio build numbers and release dates page.
![Offline Offline](/uploads/1/2/6/5/126593997/417501378.png)
Step 2 - Create a local install cache
You must have an internet connection to complete this step.
Important
If you install Visual Studio Community, you must activate it within 30 days of installation. This requires an internet connection.
Open a command prompt and use one of the commands from the following examples. The examples that are listed here assume that you're using the Community edition of Visual Studio; adjust the command as appropriate for your edition.
Tip
To prevent an error, make sure that your full installation path is less than 80 characters.
- For .NET web and .NET desktop development, run:
- For .NET desktop and Office development, run:
- For C++ desktop development, run:
- To create a complete local layout with all features (this will take a long time—we have lots of features!), run:
Note
A complete Visual Studio layout requires a minimum of 35 GB of disk space. For more information, see System requirements. And for information about how to create a layout with only the components you want to install, see Use command-line parameters to install Visual Studio.
Microsoft Remote Desktop Beta Mac
Note
A complete Visual Studio layout requires a minimum of 35 GB of disk space. For more information, see System requirements. And for information about how to create a layout with only the components you want to install, see Use command-line parameters to install Visual Studio.
If you want to install a language other than English, change
en-US
to a locale from the List of language locales. Then, use the list of the components and workloads available to further customize your installation cache.Step 3 - Install Visual Studio from the local cache
Tip
When you run from a local install cache, setup uses the local versions of each of these files. But if you select components during installation that aren't in the cache, setup attempts to download them from the internet.
Important
For offline installations, if you get an error message that says 'A product matching the following parameters cannot be found', make sure that you are using the
--noweb
switch with version 16.3.5 or later.To make sure that you install only the files that you've previously downloaded, use the same command-line options that you used to create the layout cache. For example, if you created a layout cache with the following command:
Microsoft Remote Desktop Mac Offline Installer Windows 10
Then use this command to run the installation:
Microsoft Remote Desktop Mac Offline Installer Windows 7
For more examples of how to use command-line parameters, see the Command-line parameter examples for Visual Studio installation page.
Note
If you get an error that a signature is invalid, you must install updated certificates. Open the Certificates folder in your offline cache. Double-click each of the certificate files, and then click through the Certificate Manager wizard. If you're asked for a password, leave it blank.
List of language locales
Microsoft Remote Desktop On Mac
Language-locale | Language |
---|---|
cs-CZ | Czech |
de-DE | German |
en-US | English |
es-ES | Spanish |
fr-FR | French |
it-IT | Italian |
ja-JP | Japanese |
ko-KR | Korean |
pl-PL | Polish |
pt-BR | Portuguese - Brazil |
ru-RU | Russian |
tr-TR | Turkish |
zh-CN | Chinese - Simplified |
zh-TW | Chinese - Traditional |
Get support
Sometimes, things can go wrong. If your Visual Studio installation fails, see Troubleshoot Visual Studio installation and upgrade issues for step-by-step guidance.
We also offer an installation chat (English only) support option for installation-related issues.
Here are a few more support options:
Microsoft Remote Desktop App Mac
![Microsoft Remote Desktop Mac Offline Installer Microsoft Remote Desktop Mac Offline Installer](/uploads/1/2/6/5/126593997/120586851.jpg)
- Report product issues to us via the Report a Problem tool that appears both in the Visual Studio Installer and in the Visual Studio IDE.
- Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.
- Use your GitHub account to talk to us and other Visual Studio developers in the Visual Studio conversation in the Gitter community.