Install Remote Desktop For Mac Via Homebrew

-->

How do I install VNC® Viewer? Just run the installer on the device you want to control from and follow the instructions, or there's MSIs for remote deployment under Windows. If you don't have permission to install VNC® Viewer on desktop platforms, choose the standalone option. Advanced Mac users may appreciate using the Homebrew package manager, which greatly simplifies the process of installing command line software and tools on a Mac. For example, if you want to easily install favorite command line tools on a Mac like cask, htop, wget, nmap, tree, irssi, links, colordiff, or virtually any other familiar unix. Installing Remote Desktop 8 is a good workaround, as it can run on older versions of macOS. However unfortunately it is no longer available on the Mac App Store or from Microsoft. There are some software download sites that offer Remote Desktop 8, however they are likely to contain malware. Install using Homebrew. Homebrew is the preferred package manager for macOS. Install PowerShell via Direct Download; Install from binary archives. After installing PowerShell, you should install OpenSSL. OpenSSL is needed for PowerShell remoting and CIM operations. Installation of latest stable release via Homebrew on macOS 10.13 or higher. Use Microsoft Remote Desktop for Mac to connect to a remote PC or virtual apps and desktops made available by your admin. With Microsoft Remote Desktop, you can be productive no matter where you are. GET STARTED Configure your PC for remote access using the information at https://aka.ms/rdsetup.

PowerShell 7.0 or higher require macOS 10.13 and higher. All packages are available on our GitHubreleases page. After the package is installed, run pwsh from a terminal.

Note

PowerShell 7.1 is an in-place upgrade that removes PowerShell Core 6.x and 7.0.

The /usr/local/microsoft/powershell/6 folder is replaced by /usr/local/microsoft/powershell/7.

If you need to run and older version of PowerShell core side-by-side with PowerShell 7.1, installthe version you want using the binary archive method.

There are several ways to install PowerShell on macOS. Choose one of the following methods:

  • Install using Homebrew. Homebrew is the preferred package manager for macOS.
  • Install PowerShell via Direct Download
  • Install from binary archives.

After installing PowerShell, you should install OpenSSL. OpenSSL isneeded for PowerShell remoting and CIM operations.

Installation of latest stable release via Homebrew on macOS 10.13 or higher

If the brew command is not found, you need to install Homebrew followingtheir instructions.

Now, you can install PowerShell:

Finally, verify that your install is working properly:

When new versions of PowerShell are released, update Homebrew's formulae and upgrade PowerShell:

Note

The commands above can be called from within a PowerShell (pwsh) host,but then the PowerShell shell must be exited and restarted to complete the upgradeand refresh the values shown in $PSVersionTable.

Installation of latest preview release via Homebrew on macOS 10.13 or higher

After you've installed Homebrew, you can install PowerShell. First, install the Cask-Versionspackage that lets you install alternative versions of cask packages:

Now, you can install PowerShell:

Finally, verify that your install is working properly:

When new versions of PowerShell are released, update Homebrew's formulae and upgrade PowerShell:

Install Remote Desktop On Macbook

Note

The commands above can be called from within a PowerShell (pwsh) host,but then the PowerShell shell must be exited and restarted to complete the upgrade.and refresh the values shown in $PSVersionTable.

Installing PowerShell using the Homebrew tap method is also supported for stable and LTS versions.

You can now verify your install

When new versions of PowerShell are released, simply run the following command.

Note

Whether you use the cask or the tap method, when updating to a newer version of PowerShell, usethe same method you used to initially install PowerShell. If you use a different method, opening anew pwsh session will continue to use the older version of PowerShell.

If you do decide to use different methods, there are ways to correct the issue using theHomebrew link method.

Installation via Direct Download

Download the PKG package powershell-7.1.3-osx-x64.pkg from the releases page onto yourmacOS machine.

You can double-click the file and follow the prompts, or install it from the terminal:

Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIMoperations.

Install as a .NET Global tool

If you already have the .NET Core SDK installed, it's easy to install PowerShellas a .NET Global tool.

The dotnet tool installer adds ~/.dotnet/tools to your PATH environment variable. However, thecurrently running shell does not have the updated PATH. You should be able to start PowerShellfrom a new shell by typing pwsh.

Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIMoperations.

Binary Archives

PowerShell binary tar.gz archives are provided for the macOS platform to enable advanceddeployment scenarios. When you install using this method you must also manually install anydependencies.

Install OpenSSL. OpenSSL is needed for PowerShell remoting and CIMoperations.

Note

You can use this method to install any version of PowerShell including the latest:

  • Stable release: https://aka.ms/powershell-release?tag=stable
  • Preview release: https://aka.ms/powershell-release?tag=preview
  • LTS release: https://aka.ms/powershell-release?tag=lts

Installing binary archives on macOS

Installing dependencies

OpenSSL is required for PowerShell remoting and CIM operations. You can install OpenSSL via MacPortsif needed.

Note

MacPorts and Homebrew can have problems when used to together on the same system. However,Homebrew does not have a package for OpenSSL 1.0. For more information, see theMacPorts FAQ.

  1. Install the Xcode command-line tools. The Xcode tools are required by MacPorts.

  2. Install MacPorts. If you need instructions, refer to theinstallation guide.

  3. Update MacPorts by running sudo port selfupdate.

  4. Upgrade MacPorts packages by running sudo port upgrade outdated.

  5. Install OpenSSL by running sudo port install openssl10.

  6. Link the libraries to make them available to PowerShell:

Uninstalling PowerShell

If you installed PowerShell with Homebrew, use the following command to uninstall:

If you installed PowerShell via direct download, PowerShell must be removed manually:

Install Remote Desktop For Mac Via Homebrew

To remove the additional PowerShell paths, refer to the paths section in this documentand remove the paths using sudo rm.

Note

This is not necessary if you installed with Homebrew.

Paths

  • $PSHOME is /usr/local/microsoft/powershell/7.1.3/
  • User profiles will be read from ~/.config/powershell/profile.ps1
  • Default profiles will be read from $PSHOME/profile.ps1
  • User modules will be read from ~/.local/share/powershell/Modules
  • Shared modules will be read from /usr/local/share/powershell/Modules
  • Default modules will be read from $PSHOME/Modules
  • PSReadline history will be recorded to ~/.local/share/powershell/PSReadLine/ConsoleHost_history.txt

The profiles respect PowerShell's per-host configuration. So the default host-specific profileexists at Microsoft.PowerShell_profile.ps1 in the same locations.

PowerShell respects the XDG Base Directory Specification on macOS.

Because macOS is a derivation of BSD, the prefix /usr/local is used instead of /opt. So,$PSHOME is /usr/local/microsoft/powershell/7.1.3/, and the symbolic link is placed at/usr/local/bin/pwsh.

Installation support

Microsoft supports the installation methods in this document. There may be other methods ofinstallation available from other sources. While those tools and methods may work, Microsoft cannotsupport those methods.

Additional Resources

Tutorial

Introduction

The command line interface is a non-graphical way to interact with your computer. Instead of clicking buttons with your mouse, you’ll type commands as text and receive text-based feedback. The command line, also known as a shell, lets you automate many tasks you do on your computer daily, and is an essential tool for software developers.

While the command line interface on macOS has a lot of the functionality you’d find in Linux and other Unix systems, it does not ship with a good package manager. A package manager is a collection of software tools that work to automate software installations, configurations, and upgrades. Package managers keep the software they install in a central location and can maintain all software packages on the system in formats that are commonly used.

Homebrew is a package manager for macOS which lets you install free and open-source software using your terminal. You’ll use Homebrew to install developer tools like Python, Ruby, Node.js, and more.

In this tutorial you’ll install and use Homebrew on your Mac.

Prerequisites

You will need a macOS computer running High Sierra or higher with administrative access and an internet connection.

Step 1 — Using the macOS Terminal

To access the command line interface on your Mac, you’ll use the Terminal application provided by macOS. Like any other application, you can find it by going into Finder, navigating to the Applications folder, and then into the Utilities folder. From here, double-click the Terminal application to open it up. Alternatively, you can use Spotlight by holding down the COMMAND key and pressing SPACE to find Terminal by typing it out in the box that appears.

To get more comfortable using the command line, take a look at An Introduction to the Linux Terminal. The command line interface on macOS is very similar, and the concepts in that tutorial are directly applicable.

Now that you have the Terminal running, let’s install some additional tools that Homebrew needs.

Step 2 — Installing Xcode’s Command Line Tools

Install remote desktop for mac via homebrew download

Xcode is an integrated development environment (IDE) that is comprised of software development tools for macOS. You won’t need Xcode to use Homebrew, but some of the software and components you’ll want to install will rely on Xcode’s Command Line Tools package.

Execute the following command in the Terminal to download and install these components:

You’ll be prompted to start the installation, and then prompted again to accept a software license. Then the tools will download and install automatically.

Install

You can now install Homebrew.

Step 3 — Installing and Setting Up Homebrew

To install Homebrew, you’ll download an installation script and then execute the script.

First, download the script to your local machine by typing the following command in your Terminal window:

The command uses curl to download the Homebrew installation script from Homebrew’s Git repository on GitHub.

Let’s walk through the flags that are associated with the curl command:

  • The -f or --fail flag tells the Terminal window to give no HTML document output on server errors.
  • The -s or --silent flag mutes curl so that it does not show the progress meter, and combined with the -S or --show-error flag it will ensure that curl shows an error message if it fails.
  • The -L or --location flag will tell curl to handle redirects. If the server reports that the requested page has moved to a different location, it’ll automatically execute the request again using the new location.
  • The -o switch specifies a local filename for the file.

Before running a script you’ve download from the Internet, you should review its contents so you know what the script will do. Use the less command to look at the installation script:

Once you’re comfortable with the contents of the script, execute the script with the bash command:

The installation script will explain what it will do and will prompt you to confirm that you want to do it. This lets you know exactly what Homebrew is going to do to your system before you let it proceed. It also ensures you have the prerequisites in place before it continues.

You’ll be prompted to enter your password during the process. However, when you type your password, your keystrokes will not display in the Terminal window. This is a security measure and is something you’ll see often when prompted for passwords on the command line. Even though you don’t see them, your keystrokes are being recorded by the system, so press the RETURN key once you’ve entered your password.

Press the letter y for “yes” whenever you are prompted to confirm the installation.

Once the installation process is complete, you will want to put the directory Homebrew uses to store its executables at the front of the PATH environment variable. This ensures that Homebrew installations will be called over the tools that macOS includes.

The file you’ll modify depends on which shell you’re using. If you’re using Bash, you’ll use the file ~/.bash_profile:

However, if you’re using ZSH, you’ll open the file ~/.zshrc.

Once the file opens up in the Terminal window, add the following lines to the end of the file:

The first line is a comment that will help you remember what this does if you open this file in the future.

To save your changes, hold down the CTRL key and the letter O, and when prompted, press the RETURN key. Then exit the editor by holding the CTRL key and pressing X. This will return you to your Terminal prompt.

To activate these changes, close and reopen your Terminal app. Alternatively, use the source command to load the file you modified.

If you modified .bash_profile, execute this command:

If you modified .zshrc, execute this command:

Once you have done this, the changes you have made to the PATH environment variable will take effect. They’ll be set correctly when you log in again in the future, as the configuration file for your shell is executed automatically when you open the Terminal app.

Now let’s verify that Homebrew is set up correctly. Execute this command:

If no updates are required at this time, you’ll see this in your Terminal:

Otherwise, you may get a warning to run another command such as brew update to ensure that your installation of Homebrew is up to date. Follow any on-screen instructions to fix your environment before moving on.

Step 4 — Installing, Upgrading, and Removing Packages

Now that Homebrew is installed, use it to download a package. The tree command lets you see a graphical directory tree and is available via Homebrew.

Install tree with the brew install command:

Homebrew will update its list of packages and then download and install the tree command:

Homebrew installs files to /usr/local by default, so they won’t interfere with future macOS updates. Verify that tree is installed by displaying the command’s location with the which command:

The output shows that tree is located in /usr/local/bin:

Run the tree command to see the version:

The version prints to the screen, indicating it’s installed:

Occasionally, you’ll want to upgrade an existing package. Use the brew upgrade command, followed by the package name:

You can run brew upgrade with no additional arguments to upgrade all programs and packages Homebrew manages.

When you install a new version, Homebrew keeps the older version around. After a while, you might want to reclaim disk space by removing these older copies. Run brew cleanup to remove all old versions of your Homebrew-managed software.

To remove a package you’re no longer using, use brew uninstall. To uninstall the tree command, execute this command:

The output shows that the package was removed:

You can use Homebrew to install desktop applications too.

Step 5 — Installing Desktop Applications

You’re not restricted to using Homebrew for command-line tools. Homebrew Cask lets you install desktop applications. This feature is included with Homebrew, so there’s nothing additional to install.

To use Homebrew to install Visual Studio Code, execute the following command:

The application will install:

You’ll find the application in your Applications folder, just as if you’d installed it manually.

To remove it, use brew cask uninstall:

Homebrew will remove the installed software:

It performs a backup first in case the removal fails, but once the program is fully uninstalled, the backup is removed as well.

Step 6 — Uninstalling Homebrew

If you no longer need Homebrew, you can use its uninstall script.

Download the uninstall script with curl:

As always, review the contents of the script with the less command to verify the script’s contents:

Once you’ve verified the script, execute the script with the --help flag to see the various options you can use:

The options display on the screen:

Use the -d flag to see what the script will do:

The script will list everything it will delete:

When you’re ready to remove everything, execute the script without any flags:

This removes Homebrew and any programs you’ve installed with it.

Conclusion

In this tutorial you installed and used Homebrew on your Mac. You can now use Homebrew to install command line tools, programming languages, and other utilities you’ll need for software development.

Homebrew has many packages you can install. Visit the official list to search for your favorite programs.