Microsoft Docs For Mac

Posted : admin On 03.04.2020

r7c.netlify.com › ▄ ▄ Microsoft Docs For Mac ▄ ▄

Use Microsoft Word for the best word processing and document creation. Find out how document collaboration and editing tools can help polish your Word docs.
The Windows 10 Home operating system offers built-in security and apps like Mail, Calendar, Photos, Microsoft Edge, and more to help keep you safe and productive.
Running other third-party endpoint protection products alongside Microsoft Defender ATP for Mac is likely to lead to performance problems and unpredictable side effects. If non-Microsoft endpoint protection is an absolute requirement in your environment, you can still safely take advantage of MDATP.
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.

Microsoft Word For Mac Document Recovery
Microsoft Docs Download
Microsoft Docs Machine Learning
Microsoft Docs For Mac Free

Office 2011 Mac - O365 MFA issues opening Word docs from SP Hi Team, I have had no issues opening and editing Office (Word/Excel) docs from SharePoint previously using Office2011 for Mac and saving to the O365 cloud location they were opened from.

The following tips and control equivalents should help you in your transition between a Mac and Windows (or WSL/Linux) development environment. For app development, the nearest equivalent to Xcode would be Visual Studio. There is also a version of Visual Studio for Mac, if you ever feel the need to go back. Choose from thousands of free Microsoft Office templates for every event or occasion. Jump start your school, work, or family project and save time with a professionally designed Word, Excel, PowerPoint template that’s a perfect fit.

-->

**适用于：****Office for Mac、Office 2019 for Mac、Office 2016 for MacApplies to:Office for Mac, Office 2019 for Mac, Office 2016 for Mac

作为管理员，你可以通过两种基本方式将 Office for Mac 部署到组织中的用户：There are two basic ways that you, as an admin, can deploy Office for Mac to users in your organization:

向用户提供安装程序包文件，并让他们自行安装 Office for MacProvide your users with the installer package file, and have them install Office for Mac for themselves
将安装程序包文件下载到本地网络，然后使用软件分发工具将 Office for Mac 部署到你的用户Download the installer package file to your local network, and then use your software distribution tools to deploy Office for Mac to your users

If you have an Office 365 plan, you can provide your users with instructions on how to download and install Office for Mac for themselves. To install Office for Mac, a user has to be administrator on the Mac or know an administrator account name and password.If you have an Office 365 plan, you can provide your users with instructions on how to download and install Office for Mac for themselves. To install Office for Mac, a user has to be administrator on the Mac or know an administrator account name and password.

But, if you deploy Office for Mac for your users, you have more control over the deployment, including which users get Office for Mac and when. To plan your deployment, review the following information.But, if you deploy Office for Mac for your users, you have more control over the deployment, including which users get Office for Mac and when. To plan your deployment, review the following information.

将 Office for Mac 下载到本地网络Download Office for Mac to your local network

The easiest way to download Office for Mac, and ensure you're always getting the most current version and build, is to download directly from the Office Content Delivery Network (CDN) on the internet. Here are the links to the installer packages for the Office suite, which contains all the applications:The easiest way to download Office for Mac, and ensure you're always getting the most current version and build, is to download directly from the Office Content Delivery Network (CDN) on the internet. Here are the links to the installer packages for the Office suite, which contains all the applications:

Office For Mac （适用于 office 365 计划）Office for Mac (for Office 365 plans)
Office 2019 for Mac（零售或批量许可版本）Office 2019 for Mac (for retail or volume licensed versions)
Office 2016 for Mac（零售或批量许可版本）Office 2016 for Mac (for retail or volume licensed versions)

备注

Get the Project Professional 2019 at Microsoft Store and compare products with the latest customer reviews and ratings. Download or ship for free. Project Plan 3 always gives you the latest version of Project. Project Professional has a perpetual license—once activated, the software will not expire. Project Plan 3 requires an active. Microsoft project for macbook. Microsoft Project and Microsoft Teams, the power of two. Use Project and Teams to empower collaboration and management of projects, including file sharing, chats, meetings, and more. Microsoft Project 2019 is the latest version of Project. Previous versions include Project 2016, Project 2013, Project 2010, and Project 2007. Project Online: A Microsoft Alternative On Mac. Project Online is your best Microsoft alternative. If you’ve used the version of Microsoft Office for Macbooks, you might’ve come across it already. The Project Online web app is designed by Microsoft, comes with Microsoft 365 for Mac. Dec 03, 2019 Unfortunately Microsoft Project, also known as MS Project, wasn’t designed for Mac computers, so it won’t work on any version of Mac OS. But there is a workaround that can solve your problem. It’s not complicated, and in fact, it’s easier to. Microsoft Project Student Download Version Limitations of MS Project free trial software. The Microsoft Project free trial 2016 software is a fully functional copy. The limitation is the trial period which is 180 days. However, by the time it expires, you.

Installer and update packages for individual applications are also available on the Office CDN. For links to those, see Most current packages for Office for Mac.Installer and update packages for individual applications are also available on the Office CDN. For links to those, see Most current packages for Office for Mac.
The same installer package is used for Office for Mac and Office 2019 for Mac. How you activate the product determines whether you get the features for Office for Mac or the features for Office 2019 for Mac.The same installer package is used for Office for Mac and Office 2019 for Mac. How you activate the product determines whether you get the features for Office for Mac or the features for Office 2019 for Mac.
与 Office 2016 for Mac 不同的是，批量许可服务中心 (VLSC) 不提供 Office 2019 for Mac 的安装程序包。Unlike Office 2016 for Mac, the installer package for Office 2019 for Mac isn't available on the Volume Licensing Service Center (VLSC).

将 Office for Mac 部署到组织中的用户Deploy Office for Mac to users in your organization

Office for Mac uses the Apple Installer technology for installation. That means you can use the software distribution tools that you normally use to deploy software to Mac users. Some of the most common tools are Jamf Pro, Munki, and AutoPkg. You can also use Apple Remote Desktop and AppleScript.Office for Mac uses the Apple Installer technology for installation. That means you can use the software distribution tools that you normally use to deploy software to Mac users. Some of the most common tools are Jamf Pro, Munki, and AutoPkg. You can also use Apple Remote Desktop and AppleScript.

重要

There are changes in Office for Mac to improve security, including implementing Apple app sandboxing guidelines. These changes mean that you can't customize the app bundle before or after you deploy Office. Don't add, change, or remove files in an app bundle. For example, even if you don't need the French language resource files for Excel, don't delete them. This change prevents Excel from starting. Even though you can't customize app bundles, you can configure preferences for each app.There are changes in Office for Mac to improve security, including implementing Apple app sandboxing guidelines. These changes mean that you can't customize the app bundle before or after you deploy Office. Don't add, change, or remove files in an app bundle. For example, even if you don't need the French language resource files for Excel, don't delete them. This change prevents Excel from starting. Even though you can't customize app bundles, you can configure preferences for each app.

Office for Mac 的其他部署信息Additional deployment information for Office for Mac

无论您决定使用哪种部署方法，以下信息都可以帮助您规划 Office for Mac 部署。Whichever deployment method you decide to use, the following information can help you plan your Office for Mac deployment.

What's new: Before you deploy, review the information about what's new for admins in Office for Mac. This includes information about system requirements, language support, and new features.What's new: Before you deploy, review the information about what's new for admins in Office for Mac. This includes information about system requirements, language support, and new features.
Side-by-side installation: You can't have Office 2016 for Mac and Office 2019 for Mac installed on the same computer. Also, you can't have Office for Mac (from an Office 365 plan) along with either Office 2016 for Mac or Office 2019 for Mac (both of which are one-time purchase versions) installed on the same computer.Side-by-side installation: You can't have Office 2016 for Mac and Office 2019 for Mac installed on the same computer. Also, you can't have Office for Mac (from an Office 365 plan) along with either Office 2016 for Mac or Office 2019 for Mac (both of which are one-time purchase versions) installed on the same computer.
Deploying individual apps: Installer package files for individual applications are available on the Office Content Delivery Network (CDN). For links to those, see Most current packages for Office for Mac.Deploying individual apps: Installer package files for individual applications are available on the Office Content Delivery Network (CDN). For links to those, see Most current packages for Office for Mac.
Activation: To use Office for Mac, it needs to be activated. Before you deploy, review the information about how activation works in Office for Mac.Activation: To use Office for Mac, it needs to be activated. Before you deploy, review the information about how activation works in Office for Mac.
Uninstalling: If you need to uninstall Office for Mac, you can follow these steps to completely remove Office for Mac. Unfortunately, there is no program to uninstall Office for Mac automatically.Uninstalling: If you need to uninstall Office for Mac, you can follow these steps to completely remove Office for Mac. Unfortunately, there is no program to uninstall Office for Mac automatically.
Office for Mac 2011: Support for Office for Mac 2011 ended on October 10, 2017. All of your Office for Mac 2011 apps will continue to function. But, you could expose yourself to serious and potentially harmful security risks. To completely remove Office for Mac 2011, follow these steps.Office for Mac 2011: Support for Office for Mac 2011 ended on October 10, 2017. All of your Office for Mac 2011 apps will continue to function. But, you could expose yourself to serious and potentially harmful security risks. To completely remove Office for Mac 2011, follow these steps.
Upgrading to Office 2019 for Mac: If you're a volume licensed customer, you can upgrade to Office 2019 for Mac without uninstalling Office 2016 for Mac. You just need to download the 2019 version of the Volume License (VL) Serializer from the Volume Licensing Service Center (VLSC) and deploy it to each computer running Office 2016 for Mac. If you need to go back to Office 2016 for Mac after you've upgraded, follow these steps.Upgrading to Office 2019 for Mac: If you're a volume licensed customer, you can upgrade to Office 2019 for Mac without uninstalling Office 2016 for Mac. You just need to download the 2019 version of the Volume License (VL) Serializer from the Volume Licensing Service Center (VLSC) and deploy it to each computer running Office 2016 for Mac. If you need to go back to Office 2016 for Mac after you've upgraded, follow these steps.
Version numbers Version numbers of 16.17 or higher for retail or volume licensed installs indicate you have Office 2019 for Mac.Version numbers Version numbers of 16.17 or higher for retail or volume licensed installs indicate you have Office 2019 for Mac.Office 2016 for Mac has version numbers of 16.16 or lower.Office 2016 for Mac has version numbers of 16.16 or lower.Since the 'major' version (16) hasn't changed between Office 2016 for Mac and Office 2019 for Mac, application settings, including policies, preferences, and preference domains are similar between the two versions.Since the 'major' version (16) hasn't changed between Office 2016 for Mac and Office 2019 for Mac, application settings, including policies, preferences, and preference domains are similar between the two versions.Also, add-ins and other extensibility solutions that are compatible with Office 2016 for Mac will most likely be compatible with Office 2019 for Mac or will require minimal testing.Also, add-ins and other extensibility solutions that are compatible with Office 2016 for Mac will most likely be compatible with Office 2019 for Mac or will require minimal testing.

Prerequisites

Ensure that the following prerequisites are met when composing shell scripts and assigning them to macOS devices.

Devices are running macOS 10.12 or later.
Devices are managed by Intune.
Shell scripts begin with #! and must be in a valid location such as #!/bin/sh or #!/usr/bin/env zsh.
Command-line interpreters for the applicable shells are installed.

Important considerations before using shell scripts

Shell scripts require that Microsoft Intune MDM Agent is successfully installed on the macOS device. For more information, see Microsoft Intune MDM Agent for macOS.
Shell scripts run in parallel on devices as separate processes.
Shell scripts that are run as the signed-in user will run for all currently signed-in user accounts on the device at the time of the run.
An end user is required to sign in to the device to execute scripts running as a signed-in user.
Root user privileges are required if the script requires making changes that a standard user account cannot.
Shell scripts will attempt to run more frequently than the chosen script frequency for certain conditions, such as if the disk is full, if the storage location is tampered with, if the local cache is deleted, or if the Mac device restarts.

Create and assign a shell script policy

Sign in to the Microsoft Endpoint Manager Admin Center.
Select Devices > macOS > Scripts > Add.
In Basics, enter the following properties, and select Next:
- Name: Enter a name for the shell script.
- Description: Enter a description for the shell script. This setting is optional, but recommended.
In Script settings, enter the following properties, and select Next:
- Upload script: Browse to the shell script. The script file must be less than 200 KB in size.
- Run script as signed-in user: Select Yes to run the script with the user's credentials on the device. Choose No (default) to run the script as the root user.
- Hide script notifications on devices: By default, script notifications are shown for each script that is run. End users see a IT is configuring your computer notification from Intune on macOS devices.
- Script frequency: Select how often the script is to be run. Choose Not configured (default) to run a script only once.
- Max number of times to retry if script fails: Select how many times the script should be run if it returns a non-zero exit code (zero meaning success). Choose Not configured (default) to not retry when a script fails.
In Scope tags, optionally add scope tags for the script, and select Next. You can use scope tags to determine who can see scripts in Intune. For full details about scope tags, see Use role-based access control and scope tags for distributed IT.
Select Assignments > Select groups to include. An existing list of Azure AD groups is shown. Select one or more device groups that include the users whose macOS devices are to receive the script. Choose Select. The groups you choose are shown in the list, and will receive your script policy.
Note
- Shell scripts in Intune can only be assigned to Azure AD device security groups. User group assignment is not supported in preview.
- Updating assignments for shell scripts also updates assignments for Microsoft Intune MDM Agent for macOS.
In Review + add, a summary is shown of the settings you configured. Select Add to save the script. When you select Add, the script policy is deployed to the groups you chose.

The script you created now appears in the list of scripts.

Monitor a shell script policy

You can monitor the run status of all assigned scripts for users and devices by choosing one of the following reports:

Scripts > select the script to monitor > Device status
Scripts > select the script to monitor > User status

Important

Irrespective of the selected Script frequency, the script run status is reported only the first time a script is run. Script run status is not updated on subsequent runs. However, updated scripts are treated as new scripts and will report the run status again.

Once a script runs, it returns one of the following statuses:

A script run status of Failed indicates that the script returned a non-zero exit code or the script is malformed.
A script run status of Success indicated that the script returned zero as the exit code.

Frequently asked questions

Why are assigned shell scripts not running on the device?

There could be several reasons:

The agent might need to check-in to receive new or updated scripts. This check-in process occurs every 8 hours and is different from the MDM check-in. Make sure that the device is awake and connected to a network for a successful agent check-in and wait for the agent to check-in.
The agent may not be installed. Check that the agent is installed at /Library/Intune/Microsoft Intune Agent.app on the macOS device.
The agent may not be in a healthy state. The agent will attempt to recover for 24 hours, remove itself and reinstall if shell scripts are still assigned.

Microsoft Docs Download

How frequently is script run status reported?

Script run status is reported to Microsoft Endpoint Manager Admin Console as soon as script run is complete. If a script is scheduled to run periodically at a set frequency, it only reports status the first time it runs.

When are shell scripts run again?

A script is run again only when the Max number of times to retry if script fails setting is configured and the script fails on run. If the Max number of times to retry if script fails is not configured and a script fails on run, it will not be run again and run status will be reported as failed.

What Intune role permissions are required for shell scripts?

Your assigned-intune role requires Device configurations permissions to delete, assign, create, update, or read shell scripts.

Microsoft Intune MDM Agent for macOS

Why is the agent required?

Microsoft Intune MDM Agent is necessary to be installed on managed macOS devices in order to enable advanced device management capabilities that are not supported by the native macOS operating system.

How is the agent installed?

The agent is automatically and silently installed on Intune-managed macOS devices that you assign at least one shell script to in Microsoft Endpoint Manager Admin Center. The agent is installed at /Library/Intune/Microsoft Intune Agent.app when applicable and doesn't appear in Finder > Applications on macOS devices. The agent appears as IntuneMdmAgent in Activity Monitor when running on macOS devices.

What does the agent do?

The agent silently authenticates with Intune services before checking in to receive assigned shell scripts for the macOS device.
The agent receives assigned shell scripts and runs the scripts based on the configured schedule, retry attempts, notification settings, and other settings set by the admin.
The agent checks for new or updated scripts with Intune services usually every 8 hours. This check-in process is independent of the MDM check-in.

How can I manually initiate an agent check-in from a Mac?

On a managed Mac that has the agent installed, open Terminal, run the sudo killall IntuneMdmAgent command to terminate the IntuneMdmAgent process. The IntuneMdmAgent process will restart immediately, which will initiate a check-in with Intune.

Alternatively, you can do the following:

Open Activity Monitor > View > select All processes.
Search for processes named IntuneMdmAgent.
Quit the process running for root user.

Note

The Check settings action in Company Portal and the Sync action for devices in Microsoft Endpoint Manager Admin Console initiates an MDM check-in and does not force an agent check-in.

When is the agent removed?

There are several conditions that can cause the agent to be removed from the device such as:

Shell scripts are no longer assigned to the device.
The macOS device is no longer managed.
The agent is in an irrecoverable state for more than 24 hours (device-awake time).

How to turn off usage data sent to Microsoft for shell scripts?

To turn off usage data sent to Microsoft from Intune MDM Agent, open Company Portal and select Menu > Preferences > uncheck 'allow Microsoft to collect usage data'. This will turn off usage data sent for both Intune MDM agent and Company Portal.

Microsoft Docs Machine Learning

Known issues

User group assignment: Shell scripts assigned to user groups doesn't apply to devices. User group assignment is currently not supported in preview. Use device group assignment to assign scripts.
Collect logs: 'Collect logs' action is visible. But when log collection is attempted, it shows 'an error occurred' and doesn't capture logs. Log collection is currently not supported in preview.
No script run status: In the unlikely event that a script is received on the device and the device goes offline before the run status is reported, the device will not report run status for the script in the admin console.
User status report: An empty report issue exists. In the Microsoft Endpoint Manager Admin Center, select Monitor. The user status shows an empty report.

r7c.netlify.com