Jan 07, 2008 System Requirements Details. Min Operating System. Apple MacOS X 10.4.9. Processor Speed. Min RAM Size. Min Hard Drive Space. Oct 20, 2010 Overview and Evaluation Office for Mac 2011 Administrator's Guide overview How Office for Mac 2011 delivers business value Compare Office 2008 for Mac with Office for Mac 2011 Office for Mac 2011 system requirements Online training for information workers About Microsoft Volume Licensing programs. 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 Office For Mac
- Microsoft Office 2008 For Mac System Requirements 2017
- Microsoft Office 2008 For Mac System Requirements 1
- Microsoft Office 2008 For Mac
- Microsoft Office 2008 For Mac System Requirements Mac
- Mac Software
- Ms Access For Mac
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?
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.
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
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 Office For Mac
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.
For more information about creating VDI deployment of Remote Desktop Services, check out Supported Windows 10 security configurations for Remote Desktop Services VDI.
Using Remote Desktop Services with application proxy services
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.
Although by definition a cloud offering is available to anyone with an Internet connection, there are a few other requirements that must be observed should you choose to use Microsoft Office 365. In particular, you must be located in a supported country and must have supported software and a high-speed Internet connection.
Geographic requirements of Office 365
Microsoft has released Office 365 to a specific set of initial countries and will roll it out to the rest of the world in the future. Following are the supported countries and the data center location that serves each country.
| United States Data Center | Singapore Data Center | Ireland Data Center |
|---|---|---|
| Canada | Australia | Austria |
| Costa Rica | Hong Kong | Belgium |
| Columbia | India | Cyprus |
| Mexico | Japan | Czech Republic |
| Peru | Malaysia | Denmark |
| Puerto Rico | New Zealand | Finland |
| Trinidad and Tobago | Singapore | France |
| United States | Germany | |
| Greece | ||
| Hungary | ||
| Ireland | ||
| Israel | ||
| Italy | ||
| Luxembourg | ||
| Netherlands | ||
| Norway | ||
| Poland | ||
| Portugal | ||
| Romania | ||
| Spain | ||
| Sweden | ||
| Switzerland | ||
| United Kingdom |
Software requirements of Office 365
Microsoft Office 2008 For Mac System Requirements 2017
To get the most out of Office 365, it is best to use Windows 7 with Office 2010 and the latest Internet Explorer browser. Doing this gives you the fully integrated experience. Office 365 does, however, support various software configurations.
| Operating Systems | Web Browsers | Office Clients |
|---|---|---|
| Windows XP SP3 | Internet Explorer 7 + | Office 2007 SP2 |
| Windows Vista SP2 | Firefox 3 + | Office 2010 |
| Windows 7 | Safari 4 + | Office 2008 for Mac |
| Mac OS X 10.5 (Leopard) | Chrome 3 + | Office 2011 for Mac |
| Mac OS X 10.6 (Snow Leopard) | Lync 2010 | |
| Windows Server 2003 | ||
| Windows Server 2008 |
Microsoft Office 2008 For Mac System Requirements 1
A key feature of Office 365 provides the ability for your business’s Active Directory instance to sync with your Office 365 account. To achieve this integration, however, your Active Directory domain must be a single forest.
Internet access requirements of Office 365
Microsoft Office 2008 For Mac
Because the Office 365 software lives in a Microsoft data center and is accessed over the Internet, having high-speed Internet access available on a regular basis is important.
For some of the components of Office 365, such as the Outlook Web App, high-speed Internet access is not required, but as a general rule, you want to make sure that your users have a pleasant experience and that equals a high-speed Internet connection when dealing with the cloud.
Microsoft Office 2008 For Mac System Requirements Mac
Because Office 365 can be accessed from any computer anywhere in the world with an Internet connection, you have no control over the network connectivity.
Mac Software
The good news, however, is that the types of things your users will do from on the road are check e-mail, edit documents in the browser, or download a quick document from the SharePoint site — tasks that work fine with slower connection speeds (with the exception of downloading documents).
Ms Access For Mac
Most users, however, understand that the speed of their Internet connection directly relates to the speed a document will download and will not blame the Office 365 service for a slow download.