Microsoft Office 2013 Mac System Requirements
- Microsoft Office Mac Requirements
- Microsoft Office 2013 Mac System Requirements For Turbotax 2019
- Microsoft Office 2013
- Microsoft Office For Mac 2013 System Requirements
- Microsoft Office 2013 Mac System Requirements Free
- Microsoft Office Hardware Requirements
Applies to: Exchange Server 2013
Learn about the Exchange 2013 requirements that you need to know before you install Exchange 2013. For example, you'll learn about the hardware, network, and operating system requirements.
Microsoft To Do is free when you use your personal Microsoft Account, which means Microsoft To Do is available to all Office 365 and Personal customers as well. Both free and Office 365-subscribed personal Microsoft Accounts rely on Exchange Online servers, so the technical requirements detailed below are met by default. Jan 19, 2020 Microsoft Office 2013 Latest Crack + Torrent Version With Free Product Key s Free Download for Mac & Windows Microsoft Office 2013 Latest Crack removes toolbars and allows you to move to a tab in a document as in E-Reader. Videos are better supported You.
Before you install Microsoft Exchange Server 2013, we recommend that you review this topic to ensure that your network, hardware, software, clients, and other elements meet the requirements for Exchange 2013. In addition, make sure you understand the coexistence scenarios that are supported for Exchange 2013 and earlier versions of Exchange.
Supported coexistence scenarios
Microsoft Office Mac Requirements
The following table lists the scenarios in which coexistence between Exchange 2013 and earlier versions of Exchange is supported.
Coexistence of Exchange 2013 and earlier versions of Exchange Server
Microsoft Office 2013 Mac System Requirements For Turbotax 2019
| Exchange version | Exchange organization coexistence |
|---|---|
Exchange Server 2003 and earlier versions | Not supported |
Exchange 2007 | Supported with the following minimum versions of Exchange:
|
Exchange 2010 | Supported with the following minimum versions of Exchange:
|
Mixed Exchange 2010 and Exchange 2007 organization | Supported with the following minimum versions of Exchange:
|
Note 1: If you want to create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, you need to install Exchange 2007 SP3 Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
Note 2: If you want to create an EdgeSync Subscription between an Exchange 2010 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, you need to install Exchange 2010 SP3 Update Rollup 5 or later on the Exchange 2010 Hub Transport server.
Supported hybrid deployment scenarios
Exchange 2013 supports hybrid deployments with Office 365 tenants that have been upgraded to the latest version of Office 365. For more information about specific hybrid deployments, see Hybrid deployment prerequisites.
Network and directory servers
The following table lists the requirements for the network and the directory servers in your Exchange 2013 organization.
Network and directory server requirements for Exchange 2013
| Component | Requirement |
|---|---|
Schema master | By default, the schema master runs on the first Active Directory domain controller installed in a forest. The schema master must be running one of the following:
|
Global catalog server | In each Active Directory site where you plan to install Exchange 2013, you must have at least one global catalog server running one of the following:
For more information about global catalog servers, see What is the Global Catalog. |
Domain controller | In each Active Directory site where you plan to install Exchange 2013, you must have at least one writeable domain controller running one of the following:
|
Active Directory forest | Active Directory must be at Windows Server 2003 forest functionality mode or higher2. |
DNS namespace support | Exchange 2013 supports the following domain name system (DNS) namespaces:
For more information about DNS namespaces supported by Exchange, see Microsoft Knowledge Base article 2269838, Microsoft Exchange compatibility with Single Label Domains, Disjoined Namespaces, and Discontiguous Namespaces. |
IPv6 support | In Exchange 2013, IPv6 is supported only when IPv4 is also installed and enabled. If Exchange 2013 is deployed in this configuration, and the network supports IPv4 and IPv6, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses. For more information, see IPv6 support in Exchange 2013. |
1 Windows Server 2012 R2 is supported only with Exchange 2013 SP1 or later.
2 Windows Server 2012 R2 forest functionality mode is supported only with Exchange 2013 SP1 or later.
Directory server architecture
The use of 64-bit Active Directory domain controllers increases directory service performance for Exchange 2013.
Note
In multi-domain environments, on Windows Server 2008 domain controllers that have the Active Directory language locale set to Japanese, your servers might not receive some attributes that are stored on an object during inbound replication. For more information, see Microsoft Knowledge Base article 949189, A Windows Server 2008 domain controller that is configured with the Japanese language locale may not apply updates to attributes on an object during inbound replication.
Installing Exchange 2013 on directory servers
For security and performance reasons, we recommend that you install Exchange 2013 only on member servers and not on Active Directory directory servers. However, you can't run DCPromo on a computer running Exchange 2013. After Exchange 2013 is installed, changing its role from a member server to a directory server, or vice versa, isn't supported.
Hardware
The recommended hardware requirements for Exchange 2013 servers vary depending on a number of factors including the server roles that are installed and the anticipated load that will be placed on the servers.
For detailed information on how to properly size and configure your deployment, see Exchange 2013 Sizing and Configuration Recommendations.
For information about deploying Exchange in a virtualized environment, see Exchange 2013 virtualization.
Hardware requirements for Exchange 2013
| Component | Requirement | Notes |
|---|---|---|
Processor |
| See the 'Operating system' section later in this topic for supported operating systems. |
Memory | Varies depending on Exchange roles that are installed:
| None. |
Paging file size | The page file size minimum and maximum must be set to physical RAM plus 10 MB, to a maximum size of 32778MB if you're using more than 32GB of RAM. | For detailed pagefile recommendations, see the 'Pagefile' section in Exchange 2013 Sizing and Configuration Recommendations. |
Disk space |
| For detailed information on storage recommendations, see Exchange 2013 storage configuration options. |
Drive | DVD-ROM drive, local or network accessible | None. |
Screen resolution | 1024 x 768 pixels or higher | None. |
File format | Disk partitions formatted as NTFS file systems, which applies to the following partitions:
Disk partitions containing the following types of files can be formatted as ReFS:
| None. |
Operating system
The following table lists the supported operating systems for Exchange 2013.
Important
We don't support the installation of Exchange 2013 on a computer that's running in Windows Server Core mode. The computer must be running the full installation of Windows Server. If you want to install Exchange 2013 on a computer that's running in Windows Server Core mode, you must convert the server to a full installation of Windows Server by doing one of the following:
Windows Server 2008 R2: Reinstall Windows Server and select the Full Installation option.
Windows Server 2012 R2 or Windows Server 2012: Convert your Windows Server Core mode server to a full installation by running the following command.
Supported operating systems for Exchange 2013
| Component | Requirement |
|---|---|
Mailbox, Client Access, and Edge Transport server roles | One of the following:
|
Management tools | One of the following:
|
1 Windows Server 2012 R2 is supported only with Exchange 2013 SP1 or later.
2 Windows 8.1 is supported only with Exchange 2013 SP1 or later.
Supported Windows Management Framework versions for Exchange 2013
Exchange 2013 only supports the version of Windows Management Framework that's built into the release of Windows that you're installing Exchange on. Don't install versions of Windows Management Framework that are made available as stand-alone downloads on servers running Exchange.
.NET Framework
We strongly recommend that you use the latest version of .NET Framework that's supported by the release of Exchange you're installing.
| Exchange 2013 version | .NET Framework 4.8 | .NET Framework 4.7.2 | .NET Framework 4.7.1 | .NET Framework 4.6.2 |
|---|---|---|---|---|
| CU23 | X | X | ||
| CU21, CU22 | X | X | ||
| CU19, CU20 | X | X | ||
| CU16, CU17, CU18 | X | |||
| CU15 | X |
Note: For older versions, see Exchange Server supportability matrix
Supported clients
Microsoft Office 2013
Exchange 2013 supports the following versions of Outlook and Entourage for Mac:
Office 365 ProPlus
Outlook 2019
Outlook 2016
Outlook 2013
Outlook 2010
Outlook 2007
Entourage 2008 for Mac, Web Services Edition
Outlook for Mac for Office 365
Outlook for Mac 2011
For a list of Outlook releases that Exchange supports, see Outlook Updates.
Important
We strongly recommend that you install the latest available service packs and updates available so that your users receive the best possible experience when connecting to Exchange.
Outlook clients earlier than Outlook 2007 are not supported. Email clients on Mac operating systems that require DAV, such as Entourage 2008 for Mac RTM and Entourage 2004, are not supported.
Outlook Web App supports several browsers on a variety of operating systems and devices. For detailed information, see What's new for Outlook Web App in Exchange 2013.
-->This article describes the software and device requirements for running Office Add-ins.
Note
If you plan to publish your add-in to AppSource and make it available within the Office experience, make sure that you conform to the Commercial marketplace certification policies. For example, to pass validation, your add-in must work across all platforms that support the methods that you define (for more information, see section 1120.3 and the Office Add-in host and availability page).
For a high-level view of where Office Add-ins are currently supported, see Office Add-in host and platform availability.
Server requirements
To be able to install and run any Office Add-in, you first need to deploy the manifest and webpage files for the UI and code of your add-in to the appropriate server locations.
For all types of add-ins (content, Outlook, and task pane add-ins and add-in commands), you need to deploy your add-in's webpage files to a web server, or web hosting service, such as Microsoft Azure.
While not strictly required in all add-in scenarios, using an HTTPS endpoint for your add-in is strongly recommended. Add-ins that are not SSL-secured (HTTPS) generate unsecure content warnings and errors during use. If you plan to run your add-in in Office on the web or publish your add-in to AppSource, it must be SSL-secured. If your add-in accesses external data and services, it should be SSL-secured to protect data in transit. Self-signed certificates can be used for development and testing, so long as the certificate is trusted on the local machine.
Tip
When you develop and debug an add-in in Visual Studio, Visual Studio deploys and runs your add-in's webpage files locally with IIS Express, and doesn't require an additional web server.
For content and task pane add-ins, in the supported Office host applications - Excel, PowerPoint, Project, or Word - you also need an app catalog on SharePoint to upload the add-in's XML manifest file.
To test and run an Outlook add-in, the user's Outlook email account must reside on Exchange 2013 or later, which is available through Office 365, Exchange Online, or through an on-premises installation. The user or administrator installs manifest files for Outlook add-ins on that server.
Note
POP and IMAP email accounts in Outlook don't support Office Add-ins.
Client requirements: Windows desktop and tablet
The following software is required for developing an Office Add-in for the supported Office desktop clients or web clients that run on Windows-based desktop, laptop, or tablet devices:
For Windows x86 and x64 desktops, and tablets such as Surface Pro:
- The 32- or 64-bit version of Office 2013 or a later version, running on Windows 7 or a later version.
- Excel 2013, Outlook 2013, PowerPoint 2013, Project Professional 2013, Project 2013 SP1, Word 2013, or a later version of the Office client, if you are testing or running an Office Add-in specifically for one of these Office desktop clients. Office desktop clients can be installed on premises or via Click-to-Run on the client computer.
If you have a valid Office 365 subscription and you do not have access to the Office client, you can download and install the latest version of Office.
Internet Explorer 11 or Microsoft Edge (depending on the Windows and Office versions) must be installed but doesn't have to be the default browser. To support Office Add-ins, the Office client that acts as host uses browser components that are part of Internet Explorer 11 or Microsoft Edge. See Browsers used by Office Add-ins for more details.
Note
Internet Explorer's Enhanced Security Configuration (ESC) must be turned off for Office Web Add-ins to work. If you are using a Windows Server computer as your client when developing add-ins, note that ESC is turned on by default in Windows Server.
One of the following as the default browser: Internet Explorer 11, or the latest version of Microsoft Edge, Chrome, Firefox, or Safari (Mac OS).
An HTML and JavaScript editor such as Notepad, Visual Studio and the Microsoft Developer Tools, or a third-party web development tool.
Client requirements: OS X desktop
Outlook on Mac, which is distributed as part of Office 365, supports Outlook add-ins. Running Outlook add-ins in Outlook on Mac has the same requirements as Outlook on Mac itself: the operating system must be at least OS X v10.10 'Yosemite'. Because Outlook on Mac uses WebKit as a layout engine to render the add-in pages, there is no additional browser dependency.
The following are the minimum client versions of Office on Mac that support Office Add-ins.
- Word version 15.18 (160109)
- Excel version 15.19 (160206)
- PowerPoint version 15.24 (160614)
Client requirements: Browser support for Office web clients and SharePoint
Any browser that supports ECMAScript 5.1, HTML5, and CSS3, such as Internet Explorer 11, or the latest version of Microsoft Edge, Chrome, Firefox, or Safari (Mac OS).
Client requirements: non-Windows smartphone and tablet
Microsoft Office For Mac 2013 System Requirements
Specifically for Outlook running in a browser on smartphones and non-Windows tablet devices, the following software is required for testing and running Outlook add-ins.
| Host application | Device | Operating system | Exchange account | Mobile browser |
|---|---|---|---|---|
| Outlook on Android | Android tablets and smartphones | Android 4.4 KitKat later | On the latest update of Office 365 for business or Exchange Online | Native app for Android, browser not applicable |
| Outlook on iOS | iPad tablets, iPhone smartphones | iOS 11 or later | On the latest update of Office 365 for business or Exchange Online | Native app for iOS, browser not applicable |
| Outlook on the web | iPhone 4 or later, iPad 2 or later, iPod Touch 4 or later | iOS 5 or later | On Office 365, Exchange Online, or on premises on Exchange Server 2013 or later | Safari |
Microsoft Office 2013 Mac System Requirements Free
Note
The native apps OWA for Android, OWA for iPad, and OWA for iPhone have been deprecated and are no longer required or available for testing Outlook add-ins.