rm0.netlify.com

1. Office 365 Download On Mac
2. Microsoft Office 365 For Mac

In the desktop version of Office and in Office 365, if you are logged in using your Microsoft account, it will try to save the file to your OneDrive account by default. This is a new feature that started back in Office 2013 that aims to help you move your documents to the cloud, so that you can access them from anywhere and so that they are. Mar 19, 2020  Keep in touch and stay productive with Teams and Office 365, even when you're working remotely. How to set default save destination for “microsoft print to pdf”? Auto-create file names causing it to ask you for a filename. You can, however, edit the system registry to change the default 'Save As' location rather than the usual.

Note

Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. For more information about this change, read this blog post.

For a Microsoft Excel 2001 for Mac version of this article, see 259921.

Summary

This step-by-step article describes how to use the Microsoft Excel startup folders. Excel uses startup folders in two ways:

• To load Excel workbooks at startup.
• As a reference location for templates.

The actual startup folder locations vary, depending on which version of Excel you use.

Folders that Excel uses at startup

If you install Excel in the default location, Excel opens files from the following paths:

• In Microsoft Office Excel 2003, the path is C:Program FilesMicrosoft OfficeOffice11Xlstart

  In Microsoft Office Excel 2007, the path is C:Program FilesMicrosoft OfficeOffice12Xlstart

• C:Documents and SettingsUser_nameApplication DataMicrosoftExcelXLSTART

  In this path, User_name is your logon user name.

• The folder that is specified in the At startup, open all files in box.

  Note

  • To find the At startup, open all files in box in Excel 2003, click Options on the Toolsmenu, and then click the General tab.

  • To find the At startup, open all files in box in Excel 2007, click the Microsoft Office Button, click Excel Options, and then click Advanced. The At startup, open all files in box is under General.

Accepted file types during Excel startup

You typically use startup folders to load Excel templates and add-ins. You can also use startup folders to load workbooks. When you load the following types of files from a startup folder, the files have the important characteristics that are described in the following list.

Templates

If you save a workbook named Book.xlt, and then put it in a startup folder location, that workbook is the default workbook when you start Excel or open a new workbook.

Office 365 Download On Mac

To use additional templates, you must save them in the following folder:

C:Program FilesMicrosoft OfficeTemplates1033

Mac microsoft 2016 office auto updater. ApplicationSecurity updatesDownload link for update packageWord: Microsoft Word Information Disclosure Vulnerability: Microsoft Word Remote Code Execution VulnerabilityExcelPowerPointOutlookOneNoteOffice suiteDecember 2018 releaseRelease Date: December 11, 2018Version 16.16.5 (Build 18120801)This release provides the following updates. ApplicationSecurity updatesDownload link for update packageWordExcel: Microsoft Excel Remote Code Execution Vulnerability: Microsoft Excel Information Disclosure VulnerabilityPowerPoint: Microsoft PowerPoint Remote Code Execution VulnerabilityOutlookOneNoteOffice suiteNovember 2018 releaseRelease Date: November 13, 2018Version 16.16.4 (Build 18111001)This release provides the following updates.

To use the templates in Excel 2003, follow these steps:

1. On the Filemenu, click New.
2. In the New Workbook task pane, click On my computer under Templates.
3. In the Templates dialog box, double-click the template for the type of workbook that you want to create on the Spreadsheet Solutions tab.

To use the templates in Excel 2007, follow these steps:

1. Click the Microsoft Office Button, and then click New.
2. Under Templates, click Installed Templates.
3. Under Installed Templates, click the template that you want, and then click Create.

Add-ins

Add-ins (.xla files) that you put in a startup folder do not typically appear when you start Excel. The add-ins are loaded in memory. The add-ins run any auto macros.

You can use these add-ins by whatever method the add-in provides (for example, a command on a menu or a button on a toolbar).

Workbooks

Workbooks (.xls files) that you put in a startup folder are loaded and appear when you start Excel, unless the workbook is saved in a hidden state.

For example, the personal macro workbook Personal.xls is a global macro workbook that Excel typically loads from the XLStart folder in a hidden state.

Incorrect use of the alternative startup file location

When you use the alternative startup file location, you must specify a file path where there are recognizable file types (such as templates, add-ins, and workbooks).

If Excel finds unrecognizable file types in a startup folder, you may receive an error message. The most common error message is:

This file is not a recognizable format.

Use the default file location

In addition to the alternative startup file location, the default file location can be set by using the Default file location box on the General tab in the Options dialog box in Excel 2003.

The default file location differs from a startup folder. It can set the folder location that you want Excel to point to when you open or save a file by using the File menu.

Note

In Excel 2007, to see the default file location, follow these steps:

1. Click the Microsoft Office Button, and then click Excel Options.
2. Click Save.
3. The Default file location box is under Save workbooks.

Important

Microsoft Office 365 For Mac

Office 365 ProPlus is being renamed to Microsoft 365 Apps for enterprise. To learn more about this name change, read this blog post.

For details of when this change takes effect, and what actions admins might need to take, read this article.

The Office Customization Tool creates the configuration files that are used to deploy Office in large organizations. These configuration files give you more control over an Office installation: you can define which applications and languages are installed, how those applications should be updated, and application preferences. After creating the configuration files, you can use them with the Office Deployment Tool to deploy a customized version of Office.

Note

The Office Customization Tool is part of the deployment process for installing Office on hundreds or thousands of computers. To follow this process end-to-end, we recommend completing the assessment and planning phases for your Office deployment. If you're not an enterprise administrator and are looking to install Office 365 in your home or business, see Install Office with Office 365.

Get started

To work with the service, go to Office Customization Tool and choose the products, languages, and application preferences you want to configure. For example, you can create a configuration file that downloads the 64-bit English version of Office 365 ProPlus, or you can create a file that installs the 64-bit English and German version of Office without Access and Publisher and with the EULA automatically accepted. When you're done, you export the configuration file, which you can then use with the Office Deployment Tool or another software distribution solution to deploy Office in your organization.

Note

If you use Microsoft Endpoint Configuration Manager (current branch) to deploy Office, we recommend using the Office 365 Installer wizard in the Configuration Manager console. That wizard includes a customized version of the Office Customization Tool. For more details, see Deploy Office 365 ProPlus with Microsoft Endpoint Configuration Manager (current branch).

Create a configuration file

Follow these steps to create a configuration file that can be used by the Office Deployment Tool or another software distribution solution to install Office.

Note

We recommend saving and managing your configuration files in the cloud. To do so, sign in to the Office 365 Client Configuration Service before you create your configuration file. For more details, see Save and manage configuration files in the cloud.

1. Go to Office Customization Tool.
2. In the Product and releases section, choose the architecture you want to deploy. Each configuration file can only deploy one architecture. For details on which architecture to choose, see Choose the 32-bit or 64-bit version of Office.
3. Choose the products and applications you want to deploy.
4. Choose the update channel you want to deploy. The update channel determines how frequently your client devices are updated with new features. For best practice recommendations, see Step 3 - Choose your update channels.
5. Choose which version you want to deploy. Unless you require a particular version, we recommend choosing the latest. For details on previous versions, see Update history for Office 365 ProPlus.
6. In the Language section, choose which languages to include. You can include multiple languages and you can select Match operating system to automatically install the same languages that are in use on the client device. For more details, see Overview of deploying languages in Office 365 ProPlus.
7. In the Installation section, choose whether to install the Office files directly from the cloud or from a local source on your network. For more details, see Choose how to deploy.
8. Choose whether to display the installation to your end users and whether to pin the Office icons to the taskbar. For more details on these options, see Display element and PinIconsToTaskBar property.
9. In the Update and upgrade section, choose whether to install updates directly from the cloud, from a local source on your network, or with Configuration Manager. If you want to update your client devices automatically, choose CDN and Automatically check for updates. For best practice recommendations, see Choose your update channels.
10. Choose whether to automatically remove all MSI-versions of Office, and whether to automatically install the same language as the removed MSI-version of Office. For more details, see Install the same languages as a previous MSI installation.
11. If you are deploying a volume-licensed version of Office, Visio, or Project, specify the appropriate license key in Licensing and activation settings. Note that Office 365 ProPlus is not volume licensed and does not require a KMS or MAK activation. For more details, see Overview of volume activation of Office.
12. In the General section, type your organization name and a description for this particular configuration. For example, you might want to use this file to install the 64-bit version of Office for your finance department.
13. Choose whether to automatically accept the EULA.
14. Choose whether to enabled shared computer activation. For more details, see Overview of shared computer activation for Office 365 ProPlus.
15. In the Application preferences section, choose what preferences to apply when deploying Office. You can search for a setting, filter the preferences by Office app, and learn more about each setting by clicking it and reviewing the detailed description.
16. Click Finish, review the configured settings in the right-hand pane, and then click Export.
17. Accept the terms in the license agreement, name the configuration file, and then click Export or, if you're saving the configuration file to the cloud, click Done.
18. You can now use the configuration file in your deployment workflow with the Office Deployment Tool or another software distribution solution.

Edit an existing configuration file

Follow these steps to import and edit an existing configuration file.

1. Go to Office Customization Tool.
2. Click Import, and then select the configuration file you want to edit.
3. Change the settings you want, and then export the updated file.

Save and manage configuration files in the cloud

You can now use the Office Customization Tool to create, save, and manage your deployment configuration files in the cloud. You can also refer to these cloud-based files directly when running the Office Deployment Tool.

To work with configuration files in the cloud, sign in to the Office 365 Client Configuration Service and go to the Device Configuration page. From that page, you can do the following:

• To create a new file, click Create, create a configuration file, and then click Done. The configuration file is automatically saved to the cloud as part of your tenant.
• To edit an existing file, click the name of the file, make your changes, and then click Done.
• To get a link to a configuration file, select the file, click Get Link, and then click Copy. You can use the link to refer to the configuration file when you use the Office Deployment Tool.

When running the Office Deployment Tool, you refer to the cloud-based configuration file by including the link in quotes. To deploy with the ODT, for example, use setup.exe /configure 'link'.

You can also copy, upload, or download configuration files from the Device Configuration page. For example, you can create a baseline configuration file and then create copies of that baseline for custom configurations.

Define application preferences

As part of the Office Customization Tool, you can define application preferences for supported products, including VBA macro notifications, default file locations, and default file formats. When you define these preferences, you can apply them as part of deploying Office or you can apply them to an existing installation of Office without changing any other deployment settings. For more details, see Apply application preferences and Apply application preferences to an existing installation of Office.

Notes

When creating a configuration file, the Office Customization Tool includes two attributes for the Configuration element: The ID attribute, which identifies the deployment method, and the Host attribute, which identifies the deployment options that have been selected. These attributes don't contain any personally identifiable information (PII), but Click-to-Run sends the attribute values to Microsoft so that we can better understand what configurations customers use and make customization even easier. Because of these insights, we recommend keeping the attributes. They are optional, however, and can be removed without affecting your deployment.