System Requirements For 2011 Mac Microsoft Office

System Requirements For 2011 Mac Microsoft Office 7,0/10 2809 votes

-->

System Requirements For 2011 Mac Microsoft Office 2016
Windows 10 Requirement
System Requirements For 2011 Mac Microsoft Office 2011 Updates

Microsoft Messenger 8 is included with both editions, and Microsoft Communicator for Mac 2011, which communicates with Microsoft Lync Server, is available only to volume licensing customers. Office 2011 requires an Intel Mac running Mac OS X 10.5.8 or later. 2016-6-28 Microsoft Office Communications Server 2007: RTM. Browser compatibility with Microsoft Dynamics CRM 2011 Notes. For more information about System Requirements, see the System Requirements and Required Components topic in the Microsoft Dynamics CRM 2011. For more details, see Exchange Server Supportability Matrix and System Requirements for Office server products. Finally, you should review the deployment tools you use in your organization, such as Microsoft Endpoint Configuration Manager. Most organizations deploy Office. The add-ins you'll see will depend on the app you're using and the kind of Office 365 subscription you have. Office for Mac doesn't currently support organization-based add-ins. Get a VBA add-in for Word or Excel for Mac.

Dynamics 365 for Outlook works the way that you do by providing a seamless combination of Dynamics 365 for Customer Engagement features in the familiar Outlook environment. This section lists software requirements for Dynamics 365 for Outlook and Dynamics 365 for Microsoft Office Outlook with Offline Access.

次の表に示したシステム要件は、Microsoft Office 365 ProPlus のほか、一般法人、教育、政府向けの各プランにも適用されます 1。また、メールのみやオンライン会議のみのプランなど、個別のサービス用の単体プランにも適用されます。. Microsoft Office contains Word, Excel, PowerPoint, and Outlook. Office 2016 is available via Microsoft Office 365. Office 2011 is still available to students, faculty, and staff via IUware. To use Office 2016 with Mac OS X, you must be running Mac OS X 10.10 (Yosemite) or later.

One of the following operating systems is required:

Windows 10 (64-bit and 32-bit versions)*
Windows 8.1 or Windows 8 (64-bit and 32-bit versions)
Windows 7 Service Pack 1 (64-bit and 32-bit versions) * Windows 7 does not support offline capabilities.
Windows Server 2012 and Windows Server 2012 R2 when running as a Remote Desktop Services application

*This feature is available only if your organization has updated to Dynamics CRM Online 2015 Update 1.1, Microsoft Dynamics CRM 2015 Update 0.2 or Dynamics 365 for Customer Engagement.

Microsoft Dynamics 365 for Outlook software feature prerequisites

The following software must be installed and running on the computer before you run Microsoft Dynamics CRM for Outlook Setup:

Web Browser. One of the following:

Internet Explorer 11
Internet Explorer 10

Important

Internet Explorer 9 or earlier versions are not supported for use with Dynamics 365 for Outlook.

You should add your Dynamics 365 (online), version 8.2 URL to Trusted sites in Internet Explorer. See Troubleshooting: Unblock required URLs.

Microsoft Office. One of the following: Microsoft word download.

Office 2016*
Office 2013
Office 2010
*This feature is available only if your organization has updated to Dynamics CRM Online 2015 Update 1.1, Microsoft Dynamics CRM 2015 Update 0.2 or Dynamics 365 for Customer Engagement.

Important

Dynamics 365 for Outlook isn’t supported with Office for Mac versions of Office Outlook.

System Requirements For 2011 Mac Microsoft Office 2016

To install and run the 64-bit version of Dynamics 365 for Outlook, a 64-bit version of Microsoft Office is required.

Before you run the Configuration Wizard to configure Dynamics 365 for Outlook, a Office Outlook profile must exist for the user. Therefore, Outlook must be run at least once to create the user's Outlook profile.

Both the web application and Dynamics 365 for Outlook require JavaScript enabled for certain features, such as Activity Feeds, dashboard areas, and the display of certain panes or menus. Although the web application displays error messages when JavaScript is disabled, Dynamics 365 for Outlook doesn’t. To verify if JavaScript is enabled in Internet Explorer, start Internet Explorer, on the Tools menu click or tap Internet options. On the Security tab, click or tap Internet, and then click or tap Custom level. In the Security Settings dialog box under Scripting, Active scripting must be set to Enable.

The Indexing Service (now known as the Windows Search Service, or WSS) is required by users who will set up and use Dynamics 365 for Outlook and its Help file in offline mode.

Dynamics 365 apps. One of the following editions of Dynamics 365 for Customer Engagement must be available so that Dynamics 365 for Outlook can connect to it:

On-premises editions of Dynamics 365 for Customer Engagement Server
Dynamics 365 for Customer Engagement

Additional Microsoft Dynamics 365 for Outlook software requirements

If needed, the following software will be installed by Microsoft Dynamics CRM for Outlook Setup:

SQL Server 2012 Express
Note
Installed from Dynamics 365 for Microsoft Office Outlook with Offline Access only.
Microsoft .NET Framework 4.6.2.
Microsoft Windows Installer 4.5.
Microsoft Visual C++ Redistributable.
Microsoft Report Viewer 2010.
Microsoft Application Error Reporting.
Windows Identity Foundation (WIF).
Azure AppFabric SDK V1.0.
Microsoft SQL Server Native Client.
Microsoft SQL Server Compact 4.0. Microsoft lifecam studio manual.
Reporting Services Microsoft ActiveX control. If not installed on the computer, the user will be prompted to install the software at first attempt to print a report. This installer package is named RSClientPrint.cab and can found on the SQL Server Reporting Services server at <drive>:Program filesMicrosoft SQL Server<MSSQL>Reporting ServicesReportServerbin.

Note

Dynamics 365 for Outlook is not supported when remote Proxy Auto-Configuration (PAC) files are used.

Offline Support

The following operating systems are supported for offline mode.

Step 1 - Review infrastructure and requirements

Review the number and details of your client devices, including platform (Windows or Mac); operating systems; architectures (32-bit or 64-bit); required languages; and existing versions of Office, Visio, Project, and other Office applications.

As part of this review, make sure that your client devices meet or exceed the minimum system requirements for installing Office 365 ProPlus.

In addition, you should review the system requirements for your Office server workloads. For example, Exchange 2007 does not support Outlook 2016. For more details, see Exchange Server Supportability Matrix and System Requirements for Office server products.

Finally, you should review the deployment tools you use in your organization, such as Microsoft Endpoint Configuration Manager. Most organizations deploy Office with the deployment tools they already have in place. If your organization uses Configuration Manager, we recommend upgrading to the current branch and updating to the current release. For more details, see Which branch of Configuration Manager should I use?.

Step 2 - Review licensing and accounts

Make sure that all your users have Office 365 accounts and licenses, and that those licenses include Office 365 ProPlus. For details on how to manage accounts and licenses, see Overview of licensing and activation in Office 365 ProPlus, Manage user accounts and licenses with Office 365 PowerShell, and Subscriptions, licenses, accounts, and tenants for Microsoft's cloud offerings.

If you plan to install Visio or Project, make sure that you have the appropriate licenses and have identified the users who need them. For more details, see Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016.

Step 3 - Assess network capability

Review your network capability, including bandwidth and distribution of client devices, based on the following considerations:

Installation files for Office 365 ProPlus are at least 1.6 GB for the core files, plus at least 250 MB for each language deployed.
Client devices require Internet access to activate their Office 365 ProPlus subscription, and then must connect at least once every thirty days to verify their subscription.
The following ports and protocols must be open: Office 365 URLs and IP address ranges.
Office 365 updates vary in size, but you can review recent download sizes here. For details on the frequency and type of updates based on channel, see Overview of update channels for Office 365 ProPlus.
Updating client devices directly from the Office Content Delivery Network (CDN) can vastly reduce your administrative investment. To help decide whether this is appropriate for your organization, make sure to assess the connectivity between the Internet and your client devices, including those in remote sites. If you do manage updates from the Office CDN, updates are automatically deployed over a number of days to conserve your network bandwidth.

Step 4 - Assess application compatibility

Before deploying Office 365 ProPlus, you may want to test your business-critical VBA macros, third-party add-ins, and complex documents and spreadsheets to assess their compatibility with the new version of Office.

Note

The vast majority of add-ins, VBA macros, and complex documents and spreadsheets that work with Office 2010 or 2013 will work with Office 365 ProPlus as well.

To complete that assessment, do the following:

Discover and get readiness information about your VBA macros and add-ins by using the Readiness Toolkit. You can run the Readiness Toolkit on client devices across your entire organization. For more details, see Use the Readiness Toolkit to assess application compatibility for Office 365 ProPlus.
Use the reports to identify the readiness status of your add-ins and get recommendations about how to fix any VBA macro issues that were identified.
Working with your business groups, define a pilot group of representative users and client devices from across the organization. Those client devices should include the architectures in your organization (32-bit and 64-bit) and all the critical line-of-business applications, add-ins, and macros that you want to test with Office 365 ProPlus.
If you use the current version of Configuration Manager, you can use the Office 365 ProPlus Pilot and Health Dashboard to help you plan, pilot, and perform your Office 365 ProPlus deployment. For more information, see https://docs.microsoft.com/configmgr/sum/deploy-use/office-365-dashboard#bkmk_pilot.

As part of your Office deployment, you will deploy Office first to the targeted group from step 3, and then do an additional round of testing to ensure compatibility between Office 365 ProPlus and the add-ins and client devices in that group. After you have verified compatibility, you can deploy to the rest of your organization. That first group will then continue to be a pilot for testing future updates from Office ahead of the rest of your organization. For more details, see Plan your enterprise deployment of Office 365 ProPlus.

Review exit criteria

Before planning your deployment, make sure you've completed all the steps for assessing your environment and requirements.

Assessment	Reviewed?
Number of clients	Y/N
Client platform (Windows or Mac)	Y/N
Operating systems	Y/N
Architectures (32-bit and 64-bit)	Y/N
Required languages	Y/N
Existing versions of Office	Y/N
Existing versions of Project and Visio	Y/N
System requirements	Y/N
Existing deployment tools	Y/N
If using Configuration Manager, on current branch	Y/N
Office 365 licensing and accounts	Y/N
Network	Y/N
Run Readiness Toolkit	Y/N
Fix critical add-ins	Y/N
Define pilot group	Y/N

Windows 10 Requirement

Next step

System Requirements For 2011 Mac Microsoft Office 2011 Updates

Plan your deployment of Office 365 ProPlus.

6hc.netlify.app