Microsoft Remote Desktop Web Access Mac

-->

Dec 19, 2011 Those of you who don’t use MS Office suite for Mac, but would like to remotely access a Windows PC, you’ll be happy to know that Microsoft Remote Desktop Connection is available as a free, standalone download from Microsoft. Microsoft Remote Desktop Connection (MRDC) allows you to remotely access a windows system on your network. May 02, 2013 Remote Desktop can't connect to the remote computer for one of these reasons: 1) Remote access to the server is not enabled 2) The remote computer is turned-off 3) The remote computer is not available on the network. Make sure the remote computer is turned-on and connected on the network, and that remote access is enabled.

Applies To: Windows Server 2016 Essentials, Windows Server 2012 R2 Essentials, Windows Server 2012 Essentials

Remote Web Access in Windows Server Essentials, or in Windows Server 2012 R2 with the Windows Server Essentials Experience role installed, provides a streamlined, touch-friendly browser experience for accessing applications and data from virtually anywhere that you have an Internet connection and by using almost any device. To use the Remote Web Access functionality, you must first turn it on by using the Set Up Anywhere Access Wizard, and then set up your router and domain name.

In this topic

Turn on and configure Remote Web Access

The following topics will help you turn on and configure Remote Web Access:

Remote Web Access overview

When you are away from your office, you can open a web browser and access Remote Web Access from anywhere that has Internet access. In Remote Web Access, you can:

  • Access shared files and folders on the server.

  • Access your server and computers on the network. This means that you can access the desktop of a networked computer as if you were sitting in front of it at your office.

    Remote Web Access is not turned on by default. When you run the Set up Anywhere Access Wizard, the wizard attempts to set up your router and Internet connectivity. After Remote Web Access is turned on, you can set up a domain name for your server and customize Remote Web Access. You can also set up the router again if you change your router.

    Permission to access Remote Web Access is not automatically granted when you add a new user account. When you add a user account, you can choose to allow access to shared folders, the Media Library, computers, Home page links, and the server Dashboard. You can also specify that a user not be allowed to use Remote Web Access.

    The Remote Web Access setting is displayed for each user account on the USERS tab of the Windows Server Essentials Dashboard. To change the Remote Web Access setting, right-click the user account, and then click View the account properties.

Turn on Remote Web Access

You can turn on Remote Web Access by running the Set up Anywhere Access Wizard from the server Dashboard.

To turn on Remote Web Access

  1. Open the Dashboard.

  2. Click Settings, and then click the Anywhere Access tab.

  3. Click Configure. The Set Up Anywhere Access Wizard appears.

  4. On the Choose Anywhere Access features to enable page, select the Remote Web Access check box.

  5. Follow the instructions to complete the wizard.

Change your region

You must be a network administrator to change the region setting in Windows Server Essentials.

To change the region setting

  1. On a computer that is connected to Windows Server Essentials, open the Dashboard.

  2. Click Settings.

  3. On the General tab, click the drop-down list in the Country/Region location of server section.

  4. From the drop-down list, select the new region, and then click Apply to accept the new region setting.

Manage Remote Web Access permissions

When you add a user account in Windows Server Essentials, the new user is allowed by default to use Remote Web Access. If you chose not to allow Remote Web Access for a user account, and then find that the user needs to use Remote Web Access, you can update the user account's properties.

To manage Remote Web Access permissions for a user account

  1. Log on to the Dashboard, and then click Users.

  2. Click the user account that you want to manage, and then click View the account properties in the Tasks pane.

  3. In the Properties dialog box, click the Anywhere Access tab.

  4. On the Anywhere Access tab, select the Allow Remote Web Access and access to web services applications check box to allow a user to connect to the server using Remote Web Access.

  5. Click Apply, and then click OK.

    For more information, see Manage User Accounts.

Secure Remote Web Access

Windows Server Essentials uses a security certificate to help secure the information that is exchanged between the software and a web browser. When you install the Connector software on your computers, the security certificate for Windows Server Essentials is added to the trusted certificate list on your computers. The best way for users to access Remote Web Access when they are away from your office is to use a portable computer that has the Connector software installed on it.

Warning

Users who use Remote Web Access from public locations or other untrusted computers should ensure that they log off the website before leaving the computer unattended or when they are finished with their session.

Manage Remote Web Access and VPN users

You can use VPN to connect to Windows Server Essentials and access all your resources that are stored on the server. This is especially useful if you have a client computer that is set up with network accounts that can be used to connect to a hosted Windows Server Essentials server through a VPN connection. All the newly created user accounts on the hosted Windows Server Essentials server must use VPN to log on to the client computer for the first time.

To set VPN and Remote Web Access permissions for network users

  1. Open the Dashboard.

  2. On the navigation bar, click USERS.

  3. In the list of user accounts, select the user account that you want to grant permissions to access the desktop remotely.

  4. In the <User Account> Tasks pane, click Properties.

  5. In <User Account> Properties, click the Anywhere Access tab.

  6. On the Anywhere Access tab, do the following:

    1. To allow a user to connect to the server by using VPN, select the Allow Virtual Private Network (VPN) check box.

    2. To allow a user to connect to the server by using Remote Web Access, select the Allow Remote Web Access and access to web services applications check box.

  7. Click Apply, and then click OK.

Set up your router

When you configure your server for Remote Web Access, the Set Up Anywhere Access Wizard attempts to set up the router. If you change routers or change settings on the router, you must rerun the Set Up Your Router Wizard. For more information, see the following topics:

Set up your router

During this step, Windows Server Essentials attempts to automatically configure your router by using UPnP commands. To do this, your router must support UPnP standards, and the UPnP setting must be enabled on your router.

Note

Your network configuration should follow the supported network requirements for Windows Server Essentials. There should be only one router on your network.

If the router is not set up by the Set Up Your Domain Name Wizard, you must manually forward port 443. For information about how to set up port forwarding on your router, see Router Setup.

Replace a router

Replace the router according to the manufacturer's instructions, and then run the Set Up Your Router Wizard to configure the new router.

To set up your new router

  1. On the Windows Server Essentials Dashboard, click Settings.

  2. Click the Anywhere Access tab, and then in the Router section, click Set up. The Set Up Your Router Wizard starts.

  3. Follow the instructions in the wizard to finish setting up your new router.

Microsoft Remote Desktop App Mac

Network location defined

A network location is a collection of network settings that Windows applies when you connect to a network. The settings vary and can be customized based on the type of network that you use. The settings for a network location determine whether certain features (such as file and printer sharing, network discovery, and public folder sharing) are turned on or off. Network locations are useful when you need to connect to different networks.

As an example, you may own a laptop computer that you use at home and on the job. When you are in the office, you connect to the office network. However, when you come home, you use your laptop to access and play videos and music that is stored on the home server. When you connect to a new network and specify the location type, Windows assigns a network profile that is preset for that type of location. The next time you connect to that network, Windows recognizes the network and automatically assigns the correct settings. This adds a layer of security to help protect the information on your computer, and only the network features that you need for that location are turned on.

There are four kinds of network locations:

  • Home network Choose this network for home networks or when you know and trust the people and devices on the network. Computers on a home network can belong to a home group. Network discovery is turned on for home networks, which allows you to see other computers and devices on the network and allows other network users to see your computer.

  • Work network Choose this network for small office or other workplace networks. Network discovery, which allows you to see other computers and devices on a network and allows other network users to see your computer, is on by default, but you cannot create or join a home group.

  • Public network Choose this network for public places (such as coffee shops or airports). This location is designed to keep your computer from being visible to other computers and to help protect your computer from malicious software from the Internet. Home group is not available on public networks, and network discovery is turned off. You should also choose this option if you're connected directly to the Internet without using a router, or if you have a mobile broadband connection.

  • Domain Choose this network for domains such as those at enterprise workplaces. This type of network location is controlled by your network administrator, and it cannot be selected or changed.

Enable Remote Desktop Services ActiveX controls

The Remote Desktop Services ActiveX controls allows you to access your home or business computer, via the Internet, from another computer by using Remote Web Access.

To enable Remote Desktop Services ActiveX controls

  1. In Internet Explorer, click Tools, and then click Internet Options.

  2. On the Security tab, click Custom level.

  3. In the ActiveX controls and plug-ins section, do the following:

    1. Under Download signed ActiveX controls, click Prompt.

    2. Under Run ActiveX controls and plug-ins, click Enable.

  4. Click OK twice to accept the changes and close the dialog box.

Set up your domain name

After Remote Web Access is turned on, you can set up a domain name for your server that is running Windows Server Essentials. This is a necessary step if you plan to use Remote Web Access from a remote computer. For more information, see the following topics:

Domain names overview

A domain name uniquely identifies your server on the Internet. Domain names consist of at least two parts: a top level domain name (TLD) and a second level domain name. For example, in contoso.com, com is the TLD and contoso is the second level domain name.

While you are away from your office, you can use your domain name to access shared files on the server or computers on the network. You can also manage your server when you are away. For example, you register contoso.com for your server. When you are away from your office, you can open a web browser on your laptop and type contoso.com in the address text box to connect to the instance of Remote Web Access that you set up on Windows Server Essentials.

Understand Microsoft personalized domain names

A Microsoft personalized domain name includes the following features:

  • A custom domain name for Remote Web Access (for example, yourhostname.remotewebaccess.com). Your domain name is associated with your public IP address.

  • A DNS dynamic update protocol service so that Remote Web Access using your domain name will not be interrupted if your public IP address changes. Typically, Internet Service Providers (ISPs) for your organization's broadband connections provide dynamic public IP addresses that can change.

  • A trusted certificate associated with the domain name.

    To integrate a Microsoft personalized domain name with your server, you need a Microsoft account (formerly known as a Windows Live ID). If you do not have a Microsoft account, you can sign up for one at the Microsoft Hotmail website.

Important

Windows Live allows special characters in your Microsoft account password that the server does not support. If you use a Microsoft personalized domain, ensure that your Microsoft account password contains only characters that the server supports. The server does not support use of the characters $, /, ', and %.

Use a new or existing domain name

To automatically set up your domain name on a server running Windows Server Essentials, you must use a domain name service provider that is listed in the Set Up Your Domain Name Wizard. You may choose to get a new domain name or use an existing domain name. Do one of the following:

  • If you want to get a new domain name from one of the domain name service providers that are listed in the wizard, click I want to set up a new domain name.

  • If you have an existing domain name that you purchased from one of the supported domain name service providers, you can use the Set Up Your Domain Name Wizard to set up the domain name for your server. Click I want to use a domain name I already own, and then type the domain name in the Set Up Your Domain Name text box. You must provide the user name and password that you used to purchase the domain name.

  • If you have an existing domain name that you purchased from a domain name service provider that is not supported by Windows Server Essentials, and you want to use the Set Up Your Domain Name Wizard to set up the domain name for your server, you can transfer the domain name to one of the domain name service providers listed in the wizard. Click I want to use a domain name I already own, type the domain name in the Domain Name text box, and then follow the instructions on the domain name service provider's website to transfer the domain name.

Set up a domain name

When you turn on Remote Web Access, you can choose to set up the Internet domain name of the server.

To set up or manage an Internet domain name

  1. Open the Dashboard.

  2. Click Server settings, and then click the Anywhere Access tab.

  3. In the Domain name section, click Set up.

  4. Follow the instructions to complete the wizard. If you do not already own a domain name and certificate, the wizard helps you find a domain name provider to purchase a domain name and certificate, or you can get a personalized Microsoft domain name.

Choose a domain name service provider

You should choose a domain name service provider that supports the domain name extension that you want to use. The Set Up Your Domain Name Wizard includes a list of qualified providers that you can use with a link to each provider's website. Click the More Info link beside each provider's name to obtain information about the services and prices that are offered by the provider.

Note

Some domain name service providers serve broad international regions and others serve smaller markets. Because of this, some providers may not offer a website that is translated into your language of preference.

When you purchase your domain name, you might also consider purchasing the Domain Name System (DNS) dynamic update protocol service from your domain name service provider. DNS dynamic update protocol is a service that lets anyone on the Internet gain access to resources on a local network when the IP address of that network is constantly changing. Or you can purchase a static IP address from your Internet Service Provider (ISP) to assure that your IP address does not change.

Choose a domain name

Choose a name that uniquely identifies your business server. For example, if your business name is Contoso Ltd, you might choose Contoso to uniquely identify your home or business server on the Internet. If the domain name is not available, try another variation of that name, or perhaps something completely different.

The name you type can contain the following:

  • 63 characters maximum

  • Letters (English or your localized characters), numbers, or hyphens (-). The name must begin and end with a letter or a number.

Choose a domain name prefix

A domain name consists of hierarchical labels.

The top-level domain extension is the right-most label in the domain name. For example, in www.contoso.com, com is the top-level domain name extension.

The second-level domain name is the label next to the top-level domain name extension. The second-level domain name is often created based on the company name, products, or services. For example, in www.contoso.com, contoso is the second-level domain name and was chosen for the company name Contoso Pharmaceuticals. The second-level domain is sometimes referred to as the hostname, which has an IP address associated with it.

The domain name prefix identifies a subdomain. The subdomain name can be used to identify services, devices, or regions. For example, Contoso Pharmaceuticals wants to allow remote users to log on to Remote Web Access, but does not want the website to be available to the public, so they create a subdomain that allows only users with appropriate permissions to access the website. Contoso Pharmaceuticals sets up remote.contoso.com as the subdomain, and remote is the domain name prefix.

Tip

It is recommended that you use the default Remote as the prefix for your domain name.

Choose a domain name extension

When you choose a domain name for your Internet website, you also need to specify the domain name extension that you want to use. The extension is identified by the letters that follow the final period of any domain name. (The formal term for the extension is the top-level domain or TLD.)

There are two main types of domain extensions that you can use: generic and country-code.

Generic top-level domains

Generic domain extensions are three or more letters in length, and they are typically used by certain types of organizations.

Mac Microsoft Remote Desktop 12

Examples of generic top-level domains

Domain ExtensionDescription
.comTypically used by commercial organizations, but it can be used by anyone.
.netDesigned for businesses that offer network infrastructure services.
.orgOriginally used by non-profit agencies and other business that did not fall into another generic top-level domain category. Can be used by anyone.
.eduRestricted for use by educational organizations.

Country-code top-level domains

These domain extensions are two letters in length. They are designed to be used by organizations in the country or region that is associated with that code. Some country-code top-level domains are restricted for use by citizens of that country or region. Others are available for use by anyone.

Examples of country-code top-level domains

Domain ExtensionDescription
.caFor use by websites in Canada
.cnFor use by websites in China
.deFor use by websites in Germany
.co.ukFor use by websites in the United Kingdom

To view the complete list of top-level domains, see the Internet Assigned Numbers Authority website.

If a domain extension is not available to select in the Set Up Domain Name Wizard

When you run the Set Up Domain Name Wizard, the wizard looks at your system information to determine your country or region. The wizard then displays only those domain extensions that the participating providers in your area support. If the domain extension that you want does not appear in the list, you must choose a different domain extension to continue. Select an extension from the list that the wizard returned.

Update or upgrade your domain name service

You may need to update or upgrade your domain name service if you purchased a domain name, but did not purchase a certificate. You must have a certificate for your domain name from your domain name service provider.

Note

Work with your domain name service provider to determine the type of certificate that you need. The certificate can be one of the inexpensive certificates that are offered. However, you should review the documentation and features of higher level security certificates to determine if they better meet your business needs.

Export or import your certificate on your server

If you want to create a backup copy of a certificate or use it on another server, you must export the certificate. For information about exporting certificates, see Export a Certificate.

Set up a domain name manually

If you choose this option, the server does not monitor or maintain your domain name, and it does not alert you if there is a configuration issue. You might also consider this option if any of the following is true:

  • No partner domain name providers are listed for your country or region.

  • The partner domain providers listed do not support your domain name extension.

  • You have an existing domain name from a domain name provider that is not currently a partner, and you do not want to transfer that domain name to a Windows Server Essentials supported domain name provider.

  • The wizard does not list the domain name extension that you want to use, but the extension is available from a domain name provider that is not currently a partner.

    If you choose to set up your domain name manually, work with your domain name service provider to create an A Record for your domain.

To create an A Record

  1. Decide on a host name, such as remote. This is the domain name prefix. The domain name prefix plus your domain name will define the URL to open your Remote Web Access logon page; for example, http://remote.contoso.com.

  2. In your domain name service providers configuration dashboard (usually on their webpage), create the A record for the host name that you decided on in Step 1. Ensure that the IP address that you specify in the A record is the IP address on the WAN side of your router (the Internet facing side). Consult your router documentation to find your WAN IP address.

  3. It is recommended that you contact your Internet Service Provider (ISP) to purchase a static IP address for your network. This ensures that the IP address does not change and that your DNS entry does not become outdated.

    If you do not have the option to obtain a static IP address from your ISP, you might also consider purchasing the Domain Name System (DNS) dynamic update protocol service from your domain name service provider or another service provider. DNS dynamic update protocol is a service that keeps the WAN IP address for your network up to date so that the IP address can be resolved to your domain name even if the IP address changes.

  4. Import a trusted certificate when the wizard prompts you. If you do not have a trusted certificate, you can obtain one from one of the supported domain name providers listed in the wizard or purchase one from the trusted provider of your choice. For more information about a trusted certificate, contact your domain name provider.

Find your domain name service provider

To find the domain name service provider for your domain name

  1. Open a web browser, and then type www.internic.com in the address bar to go to the Internic home page.

  2. On the Internic home page, click Whois.

  3. In the Whois box, type your domain name (for example contoso.com).

  4. Click the Domain option, and then click Submit.

  5. In the search results, the name of your domain name service provider is listed under Registrar.

Customize Remote Web Access

You can customize your Remote Web Access site by adding a personal logo or background image. You can also add links on the Home page so that this information is available to all of your users. For more information, see the following topics:

Customize Remote Web Access

You can customize Remote Web Access by changing the title of the website, changing the background image and logo, and adding links to other websites on the home page.

To customize Remote Web Access

  1. Open the Dashboard.

  2. Click Settings, and then click the Anywhere Access tab.

  3. In the Web site settings section, click Customize.

  4. When you finish customizing Remote Web Access, click OK. Test your changes on Remote Web Access.

Customize images for backgrounds and logos

This section provides information about the images that you can use to customize Remote Web Access.

Image size

Logo images

It is recommended that you use logo images that are 32x32 pixels. Larger images are shrunk to 32x32 and smaller images are stretched to 32x32, which could distort the image.

Desktop

Background images

While there is no size limit for background images, for best results, it is recommended that you use images that are approximately 800x500 pixels. The background image is placed in the center (horizontal and vertical) of the logon page. To help make the text on the logon page easy to read, the center of the background image should be light in color.

Image file types

The following image file types can be used to replace the default background and website logo:

  • Bitmap (*.bmp, *.dib, *.rle)

  • GIF (*.gif)

  • PNG (*.png)

  • JPG (*.jpg)

Repair Remote Web Access

The Repair Wizard helps you detect and resolve problems with your router or domain name. There are two ways to discover issues with Remote Web Access:

  • In Server Settings on the Dashboard, on the Anywhere Access tab, an icon is displayed with a red X along with a description of the issue.

  • An alert in the Alert Viewer.

Note

The Repair Wizard is not available until you turn on Remote Web Access. For information about turning on Remote Web Access, see Turn on Remote Web Access.

To repair Remote Web Access

  1. Log on to the Dashboard.

  2. Click Settings, and then click the Anywhere Access tab.

  3. Click Repair. The Repair Remote Web Access Wizard starts.

  4. Click Next. The wizard analyzes Remote Web Access, identifies the issue, and then attempts to repair the issue.

  5. If you receive an alert when the wizard finishes, you can click Retry to try to repair the issue again. If you continue to receive an alert, check the alert for additional information about the issue and troubleshooting steps.

Troubleshoot Remote Web Access

See also

-->

The Remote Desktop web client lets users access your organization's Remote Desktop infrastructure through a compatible web browser. They'll be able to interact with remote apps or desktops like they would with a local PC no matter where they are. Once you set up your Remote Desktop web client, all your users need to get started is the URL where they can access the client, their credentials, and a supported web browser.

Important

The web client does not currently support using Azure Application Proxy and does not support Web Application Proxy at all. See Using RDS with application proxy services for details.

What you'll need to set up the web client

Before getting started, keep the following things in mind:

  • Make sure your Remote Desktop deployment has an RD Gateway, an RD Connection Broker, and RD Web Access running on Windows Server 2016 or 2019.
  • Make sure your deployment is configured for per-user client access licenses (CALs) instead of per-device, otherwise all licenses will be consumed.
  • Install the Windows 10 KB4025334 update on the RD Gateway. Later cumulative updates may already contains this KB.
  • Make sure public trusted certificates are configured for the RD Gateway and RD Web Access roles.
  • Make sure that any computers your users will connect to are running one of the following OS versions:
    • Windows 10
    • Windows Server 2008R2 or later

Your users will see better performance connecting to Windows Server 2016 (or later) and Windows 10 (version 1611 or later).

Important

If you used the web client during the preview period and installed a version prior to 1.0.0, you must first uninstall the old client before moving to the new version. If you receive an error that says 'The web client was installed using an older version of RDWebClientManagement and must first be removed before deploying the new version,' follow these steps:

  1. Open an elevated PowerShell prompt.
  2. Run Uninstall-Module RDWebClientManagement to uninstall the new module.
  3. Close and reopen the elevated PowerShell prompt.
  4. Run Install-Module RDWebClientManagement -RequiredVersion <old version> to install the old module.
  5. Run Uninstall-RDWebClient to uninstall the old web client.
  6. Run Uninstall-Module RDWebClientManagement to uninstall the old module.
  7. Close and reopen the elevated PowerShell prompt.
  8. Proceed with the normal installation steps as follows.

How to publish the Remote Desktop web client

To install the web client for the first time, follow these steps:

  1. On the RD Connection Broker server, obtain the certificate used for Remote Desktop connections and export it as a .cer file. Copy the .cer file from the RD Connection Broker to the server running the RD Web role.

  2. On the RD Web Access server, open an elevated PowerShell prompt.

  3. On Windows Server 2016, update the PowerShellGet module since the inbox version doesn't support installing the web client management module. To update PowerShellGet, run the following cmdlet:

    Important

    You'll need to restart PowerShell before the update can take effect, otherwise the module may not work.

  4. Install the Remote Desktop web client management PowerShell module from the PowerShell gallery with this cmdlet:

  5. After that, run the following cmdlet to download the latest version of the Remote Desktop web client:

  6. Next, run this cmdlet with the bracketed value replaced with the path of the .cer file that you copied from the RD Broker:

  7. Finally, run this cmdlet to publish the Remote Desktop web client:

    Make sure you can access the web client at the web client URL with your server name, formatted as https://server_FQDN/RDWeb/webclient/index.html. It's important to use the server name that matches the RD Web Access public certificate in the URL (typically the server FQDN).

    Note

    When running the Publish-RDWebClientPackage cmdlet, you may see a warning that says per-device CALs are not supported, even if your deployment is configured for per-user CALs. If your deployment uses per-user CALs, you can ignore this warning. We display it to make sure you're aware of the configuration limitation.

  8. When you're ready for users to access the web client, just send them the web client URL you created.

Note

To see a list of all supported cmdlets for the RDWebClientManagement module, run the following cmdlet in PowerShell:

How to update the Remote Desktop web client

When a new version of the Remote Desktop web client is available, follow these steps to update the deployment with the new client:

  1. Open an elevated PowerShell prompt on the RD Web Access server and run the following cmdlet to download the latest available version of the web client:

  2. Optionally, you can publish the client for testing before official release by running this cmdlet:

    The client should appear on the test URL that corresponds to your web client URL (for example, https://server_FQDN/RDWeb/webclient-test/index.html).

  3. Publish the client for users by running the following cmdlet:

    This will replace the client for all users when they relaunch the web page.

How to uninstall the Remote Desktop web client

To remove all traces of the web client, follow these steps:

  1. On the RD Web Access server, open an elevated PowerShell prompt.

  2. Unpublish the Test and Production clients, uninstall all local packages and remove the web client settings:

  3. Uninstall the Remote Desktop web client management PowerShell module:

How to install the Remote Desktop web client without an internet connection

Follow these steps to deploy the web client to an RD Web Access server that doesn't have an internet connection.

Note

Installing without an internet connection is available in version 1.0.1 and above of the RDWebClientManagement PowerShell module.

Note

You still need an admin PC with internet access to download the necessary files before transferring them to the offline server.

Microsoft

Note

The end-user PC needs an internet connection for now. This will be addressed in a future release of the client to provide a complete offline scenario.

From a device with internet access

  1. Open a PowerShell prompt.

  2. Import the Remote Desktop web client management PowerShell module from the PowerShell gallery:

    Although this 1 month Microsoft Office 2016 free trial offer to you is free, Microsoft will try to make you pay for it after the 1-month free trial expires. That is why they collect all your payment details which could be either a credit or debit card, PayPal or your bank details. The trial gives you access to all the features of Office 365 Home. It includes: Always up-to-date versions of Word, Excel, PowerPoint, Outlook, Publisher, and Access as well as access to additional OneNote features (features vary). Share with your entire family – for up to 6 people. Office for Mac with Office 365, gives you power and flexibility to get things done virtually from anywhere. Find the right Office for you. Microsoft office for mac trial free download - Microsoft Office 2011, Microsoft Office 2008 update, Microsoft Office 2016 Preview, and many more programs. Microsoft Virtual PC for Mac 7.0.3. For example, if you had a trial of Office 365 Personal, you can’t sign up for a trial of Office 365 Home. However, one year after your trial or paid subscription ends, you can sign up for a new trial. Microsoft office for mac for free trial download.

  3. Download the latest version of the Remote Desktop web client for installation on a different device:

  4. Download the latest version of the RDWebClientManagement PowerShell module:

  5. Copy the content of 'C:WebClient' to the RD Web Access server.

From the RD Web Access server

Follow the instructions under How to publish the Remote Desktop web client, replacing steps 4 and 5 with the following.

  1. You have two options to retrieve the latest web client management PowerShell module:

    • Import the Remote Desktop web client management PowerShell module:
    • Copy the downloaded RDWebClientManagement folder to one of the local PowerShell module folders listed under $env:psmodulePath, or add the path to the folder with the downloaded files to the $env:psmodulePath.

  2. Deploy the latest version of the Remote Desktop web client from the local folder (replace with the appropriate zip file):

Connecting to RD Broker without RD Gateway in Windows Server 2019

This section describes how to enable a web client connection to an RD Broker without an RD Gateway in Windows Server 2019.

Setting up the RD Broker server

Follow these steps if there is no certificate bound to the RD Broker server

  1. Open Server Manager > Remote Desktop Services.

  2. In Deployment Overview section, select the Tasks dropdown menu.

  3. Select Edit Deployment Properties, a new window titled Deployment Properties will open.

  4. In the Deployment Properties window, select Certificates in the left menu.

  5. In the list of Certificate Levels, select RD Connection Broker - Enable Single Sign On. You have two options: (1) create a new certificate or (2) an existing certificate.

Microsoft Remote Desktop 10 Mac

Follow these steps if there is a certificate previously bound to the RD Broker server

  1. Open the certificate bound to the Broker and copy the Thumbprint value.

  2. To bind this certificate to the secure port 3392, open an elevated PowerShell window and run the following command, replacing '< thumbprint >' with the value copied from the previous step:

    Note

    To check if the certificate has been bound correctly, run the following command:

    In the list of SSL Certificate bindings, ensure that the correct certificate is bound to port 3392.

  3. Open the Windows Registry (regedit) and nagivate to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp and locate the key WebSocketURI. The value must be set to https://+:3392/rdp/.

Setting up the RD Session Host

Follow these steps if the RD Session Host server is different from the RD Broker server:

  1. Create a certificate for the RD Session Host machine, open it and copy the Thumbprint value.

  2. To bind this certificate to the secure port 3392, open an elevated PowerShell window and run the following command, replacing '< thumbprint >' with the value copied from the previous step:

    Note

    To check if the certificate has been bound correctly, run the following command:

    In the list of SSL Certificate bindings, ensure that the correct certificate is bound to port 3392.

  3. Open the Windows Registry (regedit) and nagivate to HKLMSYSTEMCurrentControlSetControlTerminal ServerWinStationsRDP-Tcp and locate the key WebSocketURI. The value must be set to https://+:3392/rdp/.

General Observations

  • Ensure that both the RD Session Host and RD Broker server are running Windows Server 2019.

  • Ensure that public trusted certificates are configured for both the RD Session Host and RD Broker server.

    Note

    If both the RD Session Host and the RD Broker server share the same machine, set the RD Broker server certificate only. If the RD Session Host and RD Broker server use different machines, both must be configured with unique certificates.

  • The Subject Alternative Name (SAN) for each certificate must be set to the machine's Fully Qualified Domain Name (FQDN). The Common Name (CN) must match the SAN for each certificate.

Mac Microsoft Remote Desktop Client

How to pre-configure settings for Remote Desktop web client users

This section will tell you how to use PowerShell to configure settings for your Remote Desktop web client deployment. These PowerShell cmdlets control a user's ability to change settings based on your organization's security concerns or intended workflow. The following settings are all located in the Settings side panel of the web client.

Suppress telemetry

By default, users may choose to enable or disable collection of telemetry data that is sent to Microsoft. For information about the telemetry data Microsoft collects, please refer to our Privacy Statement via the link in the About side panel.

As an administrator, you can choose to suppress telemetry collection for your deployment using the following PowerShell cmdlet:

By default, the user may select to enable or disable telemetry. A boolean value $false will match the default client behavior. A boolean value $true disables telemetry and restricts the user from enabling telemetry.

Remote resource launch method

Note

This setting currently only works with the RDS web client, not the Windows Virtual Desktop web client.

By default, users may choose to launch remote resources (1) in the browser or (2) by downloading an .rdp file to handle with another client installed on their machine. As an administrator, you can choose to restrict the remote resource launch method for your deployment with the following Powershell command:

By default, the user may select either launch method. A boolean value $true will force the user to launch resources in the browser. A boolean value $false will force the user to launch resources by downloading an .rdp file to handle with a locally installed RDP client.

Reset RDWebClientDeploymentSetting configurations to default

To reset a deployment-level web client setting to the default configuration, run the following PowerShell cmdlet and use the -name parameter to specify the setting you want to reset:

Troubleshooting

If a user reports any of the following issues when opening the web client for the first time, the following sections will tell you what to do to fix them.

What to do if the user's browser shows a security warning when they try to access the web client

The RD Web Access role might not be using a trusted certificate. Make sure the RD Web Access role is configured with a publicly trusted certificate.

If that doesn't work, your server name in the web client URL might not match the name provided by the RD Web certificate. Make sure your URL uses the FQDN of the server hosting the RD Web role.

What to do if the user can't connect to a resource with the web client even though they can see the items under All Resources

If the user reports that they can't connect with the web client even though they can see the resources listed, check the following things:

Microsoft Remote Desktop 8 For Mac

  • Is the RD Gateway role properly configured to use a trusted public certificate?
  • Does the RD Gateway server have the required updates installed? Make sure that your server has the KB4025334 update installed.

If the user gets an 'unexpected server authentication certificate was received' error message when they try to connect, then the message will show the certificate's thumbprint. Search the RD Broker server's certificate manager using that thumbprint to find the right certificate. Verify that the certificate is configured to be used for the RD Broker role in the Remote Desktop deployment properties page. After making sure the certificate hasn't expired, copy the certificate in .cer file format to the RD Web Access server and run the following command on the RD Web Access server with the bracketed value replaced by the certificate's file path:

Microsoft Remote Desktop Web Access Mac Download

Diagnose issues with the console log

Microsoft Remote Desktop Web Access Mac Torrent

If you can't solve the issue based on the troubleshooting instructions in this article, you can try to diagnose the source of the problem yourself by watching the console log in the browser. The web client provides a method for recording the browser console log activity while using the web client to help diagnose issues.

Microsoft Remote Desktop Web Access Mac 10

  • Select the ellipsis in the upper-right corner and navigate to the About page in the dropdown menu.
  • Under Capture support information select the Start recording button.
  • Perform the operation(s) in the web client that produced the issue you are trying to diagnose.
  • Navigate to the About page and select Stop recording.
  • Your browser will automatically download a .txt file titled RD Console Logs.txt. This file will contain the full console log activity generated while reproducing the target issue.

The console may also be accessed directly through your browser. The console is generally located under the developer tools. For example, you can access the log in Microsoft Edge by pressing the F12 key, or by selecting the ellipsis, then navigating to More tools > Developer Tools.

Get help with the web client

If you've encountered an issue that can't be solved by the information in this article, you can report it on Tech Community. You can also request or vote for new features at our suggestion box.

Comments are closed.