Microsoft Office Rdp Mac
Nov 27, 2017 Use the new Microsoft Remote Desktop app to connect to a remote PC or virtual apps and desktops made available by your administrator. The app helps you be productive no matter where you are. Configure your PC for remote access first by download the Remote Desktop assistant to your PC and let it do the work for you: https://aka.ms/rdsetup. Apr 19, 2018 navigate into Containers and set aside com.microsoft.rdc.macos and com.microsoft.rdc.mac (one of those is for v8, just pull them both aside). Go back to the User's Library and open the Group Containers folder. Set aside the folder UBF8T346G9.com.microsoft.rdc. Mar 10, 2020 Note. Starting with Version 16.21, Microsoft Teams will be installed by default for new installations if you're using the Office suite install package. For more information, see Microsoft Teams installations on a Mac.; For security reason, Microsoft has deprecated the use of SHA-1.
- Rdp Client Mac
- Rdp To Mac
- Microsoft Remote Desktop For Mac Download
- Best Rdp Client For Mac
- Rdp Mac To Windows
- Rdp Mac Client
Office for Mac that comes with an Office 365 subscription is updated on a regular basis to provide new features, security updates, and non-security updates. The following information is primarily intended for IT professionals that are deploying Office for Mac to the users in their organizations.
Nov 05, 1934 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. Install Office for Mac now Office 365 customers get the new Office for Mac first. You’ll have Office applications on your Mac or PC, apps on tablets and smartphones for when you're on the go, and Office Online on the web for everywhere in between. 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. . Starting with Windows 10 Fall Creators Update (1709), look for Remote Desktop under System in the Settings app instead of using the Remote Desktop Assistant. Microsoft Remote Desktop assistant allows you to configure your PC for remote access From your Windows PC, access the Microsoft Remote Desktop assistant to configure it for remote access from another device using the Remote Desktop.
Microsoft fingerprint reader mac os x. Note
- Starting with Version 16.21, Microsoft Teams will be installed by default for new installations if you're using the Office suite install package. For more information, see Microsoft Teams installations on a Mac.
- For security reason, Microsoft has deprecated the use of SHA-1. Learn more
- Starting with the 16.17 release in September 2018, this information also applies to Office 2019 for Mac, which is a version of Office for Mac that’s available as a one-time purchase from a retail store or through a volume licensing agreement.
- The update history information for version 16.16 and earlier also applies to Office 2016 for Mac, which is also a version of Office for Mac that’s available as a one-time purchase. Older versions up to and including 16.16 can be activated with an Office 2016 for Mac volume license. You can’t activate version 16.17 or later with an Office 2016 for Mac volume license. For information about Office 2016 for Mac releases from September onward, see Release notes for Office 2016 for Mac
- For information about the features, security updates, and non-security updates that are included in a given release of Office for Mac, see Release notes for Office for Mac.
- If you want early access to new releases, join the Office Insider program.
Most current packages for Office for Mac
The following table lists the most current packages for the Office suite and for the individual applications. The Office suite includes all the individual applications, such as Word, PowerPoint, and Excel. All packages are 64-bit only. The build date is listed in parentheses, in a YYMMDD format, after the version number. The install package is used if you don't have the application already installed, while the update package is used to update an existing installation.
To view release notes, see Release notes.
March 10, 2020
Version 16.35 (20030802)
Application | Download links | SHA-256 hash for install package |
---|---|---|
Office suite (with Teams) | Install package | 8E86CC3EDDB5D7AD0EBA34264C6017D8B3DB9BBC425106F8C5B1BBAC1C7966DA |
Office suite (without Teams) | Install package | DA6F028AB5A69FC48668A311A74231A9CDCDA1576D2EBB1C06E7A7DD53ED8510 |
Word | Install package Update package | 27BB4CAD84F7E15AA5E0AB48C18E620F08A4AA1AF05352847E8AA8924390005F |
Excel | Install package Update package | DFE5F4230DC3E4B85FF226E260580FBD5A85893DD17C6165721F92A03FDFDF91 |
PowerPoint | Install package Update package | 65292F7CDA8C53FB796332B84398F3A4528831CCED9E7E5614A778055F7683AF |
Outlook | Install package Update package | 92094986AE997694549E9FA54347663F4720B7842D6E5FF7525BBB4897EB5C94 |
OneNote | Update package | Not applicable |
Most current packages for other Mac programs from Microsoft
The following table provides information about the most current packages, including a download link, for other Mac programs from Microsoft that may be of interest to IT professionals. The build date is listed in parentheses, in a YYMMDD format, after the version number.
Note: Microsoft AutoUpdate (MAU) release information has moved to the MAU Release History page.
Program | Version | Package | More information | SHA-1/ SHA-256 hash |
---|---|---|---|---|
Skype for Business | 16.27.37 | Download | The latest version was released on June 23, 2019. Latest updates | ac33fbfa83e304e1ac3ba7365e8bf307b117ec954fd48902991356ee86f2e836 |
Remote Desktop | 10.3.1 | Download | This install package is 64-bit. What's new | a846cecda7391b4e67c37b4b30a0c49ebd3c80f4782a989c0b4f866cd6d09339 |
Intune Company Portal | 1.17 (52.1908008.000) [190823] | Download | What's new in Microsoft Intune | fec704b5194360a48365d0193a46135358c5f129fc2b1fb02acb902cd1f96de0 |
Microsoft SharePoint On-Premises Safari Browser Plugin for Office 2016 for Mac | 15.32.0 (170309) | Download | This install package is 64-bit. | f7f29202881a319fb249d15ab6125b5a1a94b303c649cbe3fafb37ecd4728ed8 |
Release history for Office for Mac
The following table provides release history information and download links for Office for Mac. The table is ordered by release date, with the most recent release date listed first. The build date is listed in parentheses, in a YYMMDD format, after the version number. All releases after August 22, 2016 are 64-bit only. All releases prior to August 22, 2016 are 32-bit only.
Note
Download links are only provided for the most recent releases.
Release date | Version | Install package | Update packages |
---|---|---|---|
March 10, 2020 | 16.35 (20030802) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
February 11, 2020 | 16.34 (20020900) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
January 14, 2020 | 16.33 (20011301) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
December 10, 2019 | 16.32 (19120802) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
November 12, 2019 | 16.31 (19111002) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
October 15, 2019 | 16.30 (19101301) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
September 18, 2019 | 16.29.1 (19091700) | Word, Excel, PowerPoint | |
September 10, 2019 | 16.29 (19090802) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
August 13, 2019 | 16.28 (19081202) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
July 16, 2019 | 16.27 (19071500) | Office suite (with Teams) Office suite (without Teams) | Word, Excel, PowerPoint, Outlook, OneNote |
June 11, 2019 | 16.26 (19060901) | ||
May 14, 2019 | 16.25 (19051201) | ||
April 16, 2019 | 16.24 (19041401) | ||
March 27, 2019 | 16.23.1 (19032603) | ||
March 12, 2019 | 16.23.0 (19030902) | ||
February 20, 2019 | 16.22 (19022000) | ||
January 24, 2019 | 16.21 (19011700) | ||
January 16, 2019 | 16.21 (19011500) | ||
December 11, 2018 | 16.20 (18120801) | ||
November 13, 2018 | 16.19 (18110915) | ||
October 16, 2018 | 16.18 (18101400) | ||
September 11, 2018 | 16.17 (18090901) | ||
August 14, 2018 | 16.16 (18081201) | ||
July 10, 2018 | 16.15 (18070902) | ||
June 13, 2018 | 16.14.1 (18061302) | ||
June 12, 2018 | 16.14.0 (18061000) | ||
May 24, 2018 | 16.13.1 (18052304) | ||
May 23, 2018 | 16.13.1 (18052203) | ||
May 15, 2018 | 16.13.0 (18051301) | ||
April 11, 2018 | 16.12.0 (18041000) | ||
March 19, 2018 | 16.11.1 (18031900) | ||
March 13, 2018 | 16.11.0 (18031100) | ||
February 13, 2018 | 16.10.0 (18021001) | ||
January 26, 2018 | 16.9.1 (18012504) | ||
January 18, 2018 | 16.9.0 (18011602) | ||
December 12, 2017 | 15.41.0 (17120500) | ||
November 14, 2017 | 15.40.0 (17110800) | ||
October 10, 2017 | 15.39.0 (17101000) | ||
September 12, 2017 | 15.38.0 (17090200) | ||
August 15, 2017 | 15.37.0 (17081500) | ||
July 21, 2017 | 15.36.1 (17072101) | ||
July 11, 2017 | 15.36.0 (17070200) | ||
June 16, 2017 | 15.35.0 (17061600) | ||
June 13, 2017 | 15.35.0 (17061000) | ||
May 16, 2017 | 15.34.0 (17051500) | ||
April 11, 2017 | 15.33.0 (17040900) | ||
March 14, 2017 | 15.32.0 (17030901) | ||
February 16, 2017 | 15.31.0 (17021600) | ||
January 11, 2017 | 15.30.0 (17010700) |
Applies To: Windows Server 2016, Windows Server 2019
When it comes to supported configurations for Remote Desktop Services environments, the largest concern tends to be version interoperability. Most environments include multiple versions of Windows Server - for example, you may have an existing Windows Server 2012 R2 RDS deployment but want to upgrade to Windows Server 2016 to take advantage of the new features (like support for OpenGLOpenCL, Discrete Device Assignment, or Storage Spaces Direct). The question then becomes, which RDS components can work with different versions and which need to be the same?
Rdp Client Mac
So with that in mind, here are basic guidelines for supported configurations of Remote Desktop Services in Windows Server.
Note
Make sure to review the system requirements for Windows Server 2016 and system requirements for Windows Server 2019.
Best practices
Use Windows Server 2019 for your Remote Desktop infrastructure (the Web Access, Gateway, Connection Broker, and license server). Windows Server 2019 is backward-compatible with these components, which means a Windows Server 2016 or Windows Server 2012 R2 RD Session Host can connect to a 2019 RD Connection Broker, but not the other way around.
For RD Session Hosts - all Session Hosts in a collection need to be at the same level, but you can have multiple collections. You can have a collection with Windows Server 2016 Session Hosts and one with Windows Server 2019 Session Hosts.
If you upgrade your RD Session Host to Windows Server 2019, also upgrade the license server. Remember that a 2019 license server can process CALs from all previous versions of Windows Server, down to Windows Server 2003.
Follow the upgrade order recommended in Upgrading your Remote Desktop Services environment.
If you are creating a highly available environment, all of your Connection Brokers need to be at the same OS level.
RD Connection Brokers
Windows Server 2016 removes the restriction for the number of Connection Brokers you can have in a deployment when using Remote Desktop Session Hosts (RDSH) and Remote Desktop Virtualization Hosts (RDVH) that also run Windows Server 2016. The following table shows which versions of RDS components work with the 2016 and 2012 R2 versions of the Connection Broker in a highly available deployment with three or more Connection Brokers.
3+ Connection Brokers in HA | RDSH or RDVH 2019 | RDSH or RDVH 2016 | RDSH or RDVH 2012 R2 |
---|---|---|---|
Windows Server 2019 Connection Broker | Supported | Supported | Supported |
Windows Server 2016 Connection Broker | N/A | Supported | Supported |
Windows Server 2012 R2 Connection Broker | N/A | N/A | Not Supported |
Support for graphics processing unit (GPU) acceleration
Remote Desktop Services support systems equipped with GPUs. Applications that require a GPU can be used over the remote connection. Additionally, GPU-accelerated rendering and encoding can be enabled for improved app performance and scalability.
Excel toolpak add in for mac. Remote Desktop Services Session Hosts and single-session client operating systems can take advantage of the physical or virtual GPUs presented to the operating system in many ways, including the Azure GPU optimized virtual machine sizes, GPUs available to the physical RDSH server, RemoteFX vGPUs (Only on Windows Server 2016), and GPUs presented to the VMs by supported hypervisors.
See Which graphics virtualization technology is right for you? for help figuring out what you need. For specific information about DDA, check out Plan for deploying Discrete Device Assignment.
GPU vendors may have a separate licensing scheme for RDSH scenarios or restrict GPU use on the server OS, verify the requirements with your favorite vendor.
GPUs presented by a non-Microsoft hypervisor or Cloud Platform must have drivers digitally-signed by WHQL and supplied by the GPU vendor.
Remote Desktop Session Host support for GPUs
The following table shows the scenarios supported by different versions of RDSH hosts.
Feature | Windows Server 2008 R2 | Windows Server 2012 R2 | Windows Server 2016 | Windows Server 2019 |
---|---|---|---|---|
Use of hardware GPU for all RDP sessions | No | Yes | Yes | Yes |
H.264/AVC hardware encoding (if suppported by the GPU) | No | No | Yes | Yes |
Load balancing between multiple GPUs presented to the OS | No | No | No | Yes |
H.264/AVC encoding optimizations for minimizing bandwidth usage | No | No | No | Yes |
H.264/AVC support for 4K resolution | No | No | No | Yes |
VDI support for GPUs
The following table shows support for GPU scenarios in the client OS.
Feature | Windows 7 SP1 | Windows 8.1 | Windows 10 |
---|---|---|---|
Use of hardware GPU for all RDP sessions | No | Yes | Yes |
H.264/AVC hardware encoding (if suppported by the GPU) | No | No | Windows 10 1703 and later |
Load balancing between multiple GPUs presented to the OS | No | No | Windows 10 1803 and later |
H.264/AVC encoding optimizations for minimizing bandwidth usage | No | No | Windows 10 1803 and later |
H.264/AVC support for 4K resolution | No | No | Windows 10 1803 and later |
RemoteFX 3D Video Adapter (vGPU) support
Remote Desktop Services supports RemoteFX vGPUs when VM is running as a Hyper-V guest on Windows Server 2012 R2 or Windows Server 2016. The following guest operating systems have RemoteFX vGPU support:
- Windows 7 SP1
- Windows 8.1
- Windows 10 1703 or later
- Windows Server 2016 in a single-session deployment only
- Windows Server 2019 in a single-session deployment only
Rdp To Mac
Discrete Device Assignment support
Remote Desktop Services supports Physical GPUs presented with Discrete Device Assignment from Windows Server 2016 or Windows Server 2019 Hyper-V hosts. See Plan for deploying Discrete Device Assignment for more details.
VDI deployment – supported guest OSes
Windows Server 2016 and Windows Server 2019 RD Virtualization Host servers support the following guest OSes:
- Windows 10 Enterprise
- Windows 8.1 Enterprise
- Windows 7 SP1 Enterprise
Note
- Remote Desktop Services doesn't support heterogeneous session collections. The OSes of all VMs in a collection must be the same version.
- You can have separate homogeneous collections with different guest OS versions on the same host.
- The Hyper-V host used to run VMs must be the same version as the Hyper-V host used to create the original VM templates.
Microsoft Remote Desktop For Mac Download
Single sign-on
Windows Server 2016 and Windows Server 2019 RDS supports two main SSO experiences:
- In-app (Remote Desktop application on Windows, iOS, Android, and Mac)
- Web SSO
Using the Remote Desktop application, you can store credentials either as part of the connection info (Mac) or as part of managed accounts (iOS, Android, Windows) securely through the mechanisms unique to each OS.
To connect to desktops and RemoteApps with SSO through the inbox Remote Desktop Connection client on Windows, you must connect to the RD Web page through Internet Explorer. The following configuration options are required on the server side. No other configurations are supported for Web SSO:
- RD Web set to Forms-Based Authentication (Default)
- RD Gateway set to Password Authentication (Default)
- RDS Deployment set to 'Use RD Gateway credentials for remote computers' (Default) in the RD Gateway properties
Note
Due to the required configuration options, Web SSO is not supported with smartcards. Users who login via smartcards might face multiple prompts to login.
Best Rdp Client For Mac
For more information about creating VDI deployment of Remote Desktop Services, check out Supported Windows 10 security configurations for Remote Desktop Services VDI.
Rdp Mac To Windows
Using Remote Desktop Services with application proxy services
Rdp Mac Client
You can use Remote Desktop Services, except for the web client, with Azure AD Application Proxy. Remote Desktop Services does not support using Web Application Proxy, which is included in Windows Server 2016 and earlier versions.