Download Windows 10 With Office
Lorita Swartzwelder
Some Office 2019, Office 2016, and Office 2013 products come with a product key. If yours did, before installing Microsoft 365 for the first time, sign in with an existing or new Microsoft account and enter your product key at office.com/setup. Redeeming your key is what links your account with Microsoft 365 so you only have to do this once. Already did this? Select the tab below for the version you're trying to install.
If Microsoft 365 originally came pre-installed and you need to reinstall on it on the same device or a new device, you should already have a Microsoft account associated with your copy of Microsoft 365. This is the account you'll use to install Microsoft 365 following the steps below. If you need to uninstall Microsoft 365 first, see Uninstall Office from a PC or Uninstall Office for Mac.
In practical terms, what this means is that older Office versions might not be able to use all the latest functionality and features of Microsoft 365 services. In addition, over time, these older versions might encounter other unexpected performance or reliability issues while using Microsoft 365 services. That's because as we make improvements to Microsoft 365 services, we're not taking into account or testing with these older Office versions.
Therefore, to provide the best experience with using Microsoft 365 services, we strongly recommend that you move off older Office versions to versions supported for connecting to Microsoft 365 services.
Access email, store and share files, communicate with your coworkers or students, schedule meetings, track your to-do lists and more by integrating applications and downloading them on up to five devices.
Please be advised that Microsoft 365 add-ins may require you to create an account with that vendor. In these cases, be sure to set a unique and strong passphrase; do not reuse your Ohio State or other passwords. Enable multifactor authentication where available. More information is available from Ohio State's Information Security Control Requirements (ISCR) and Password Guidance from NIST.
If you have a disability and have trouble with any Microsoft 365 product, please reference the Microsoft Accessibility Disability Answer Desk where you can contact Windows and Office accessibility support through various methods.
Stanford University has a license agreement with Microsoft that provides several Microsoft products, including Office, to faculty and staff with full-service SUNet IDs. Office applications include Word, Excel, PowerPoint, OneNote, and Outlook (plus Access and Publisher for Windows users).
Our websites may use cookies to personalize and enhance your experience. By continuing without changing your cookie settings, you agree to this collection. For more information, please see our University Websites Privacy Notice.
Microsoft Office is an office suite for Microsoft Windows and Apple macOS operating systems. On Microsoft Windows, the suite includes Word, Excel, PowerPoint, Outlook, Access and Publisher. On macOS, the suite includes Word, Excel, PowerPoint, and Outlook.
Eligibility to download Microsoft Office on Columbia-owned devices is generally limited to University officers, support staff, faculty and specific graduate/professional students at CUIMC and CBS.
If you are not eligible, you will not be able to download the installer and will be redirected to a page with additional information. For more information, please visit our Microsoft Campus Agreement information page.
Office 365 works like you: everywhere.
There's no install required.
With Office 365 you can take advantage of the same Office tools you're used to using, from anywhere with an internet connection and a web browser.
Find training and certifications and discover resources that will assist you on your learning journey. Whether you are just starting or you are an experienced professional, our hands-on approach helps you arrive at your goals faster, with more confidence and at your own pace.
Boston University licenses a broad range of software through a Microsoft Enterprise Agreement (MSEA). Among other benefits, the agreement provides eligible employees with rights to use the most current and capable versions of Microsoft Windows and Office Suites on BU-owned PCs and Macs (Windows only for Intel-based Macs).
Adobe Acrobat PDFMaker (the Convert To Adobe PDF button in the PDFMaker toolbar/tab) is an add-in that creates PDF files from Microsoft Office applications. This feature installs with Acrobat Professional and Standard.
Before you begin troubleshooting, be sure that the version of Acrobat you are running is compatible with the version of Office you are running. For details, see Compatible web browsers and PDFMaker applications Acrobat, Reader.
If you can create a PDF file with the Adobe PDF printer or Acrobat Distiller, but not with Acrobat PDFMaker, the problem could be with an Acrobat PDFMaker feature. To determine if any of these features is the cause of your problem, disable them. Then, try to create a PDF file:
PDFMaker can conflict with other macros, such as virus checkers or fax software. If other troubleshooting tasks fail, or if PDFMaker has problems after installing a third-party macro, troubleshoot conflicts with other macros. Macros known to cause incompatibilities include Duden Korrektor Plus 2.0, ViaVoice 10 and earlier, Personal Translator 2002 Office Plus, OfficeReady Stuffit, Leuchter Informatic AG WordPlus, and GoldMine Link to Word.
To determine if PDFMaker is conflicting with another macro, delete or deactivate other macros one at a time (refer applicable link below). Then try again to convert a document to a PDF using PDFMaker. If the problem does not recur, contact the manufacturer of that macro.
If you do not resolve the issue, consider using your old global template (Normal.dot) instead of the new global template. To use your old Normal.dot template, rename the new Normal.dot template back to Normal.dot. If you continue to experience issues with PDFMaker after working with this document, contact Acrobat Support.
If your licensing agreement with Microsoft allows it, you can bring and deploy your Windows 10 or 11 desktop on your WorkSpaces. To do this, you must enable Bring Your Own License (BYOL) and provide a Windows 10 or 11 license that meets the requirements below. For more information about using Microsoft software on AWS, see Amazon Web Services and Microsoft.
To stay compliant with Microsoft licensing terms, AWS runs your BYOL WorkSpaces on hardware that is dedicated to you in the AWS Cloud. By bringing your own license, you can provide a consistent experience for your users. For more information, see WorkSpaces Pricing.
If you will be using non-GPU-enabled bundles (bundles other than Graphics.g4dn, GraphicsPro.g4dn, Graphics, and GraphicsPro), verify that you will use a minimum of 100 WorkSpaces per Region. These 100 WorkSpaces can be any mix of AlwaysOn and AutoStop WorkSpaces. Using a minimum of 100 WorkSpaces per Region is a requirement for running your WorkSpaces on dedicated hardware. Running your WorkSpaces on dedicated hardware is necessary to comply with Microsoft licensing requirements. The dedicated hardware is provisioned on the AWS side, so your VPC can stay on default tenancy.
The VM must be on a single volume with a maximum size of 70 GB and at least 10 GB of free space. If you're also planning to subscribe to Microsoft Office for your BYOL image, the VM must be on a single volume with a maximum size of 70 GB and at least 20 GB of free space. The DISK that the root volume is on cannot exceed 70GB.
For more information about using GPO to set the language for Office, see Customize language setup and settings for Office in the Microsoft documentation. Office 2016 and Office 2019 use the same GPO settings (labeled with Office 2016).
To work with GPOs, you must install the Active Directory administration tools. For information about using the Active Directory administration tools to work with GPOs, see Set up Active Directory Administration Tools for WorkSpaces.
Before you can configure Office 2016 or Office 2019 policy settings, you must download the administrative template files (.admx/.adml) for Office from the Microsoft Download Center. After you download the administrative template files, you must add the office16.admx and office16.adml files to the Central Store of the domain controller for your WorkSpaces directory. (The office16.admx and office16.adml files apply to both Office 2016 and Office 2019.) For more information about working with .admx and .adml files, see How to create and manage the Central Store for Group Policy Administrative Templates in Windows in the Microsoft documentation.
Office 2016 and Office 2019 use the same GPO settings (labeled with Office 2016). If you don't see Administrative Template Policy definitions (ADMX files) retrieved from the local computer under User Configuration, Policies, the office16.admx and office16.adml files aren't correctly installed on your domain controller.
For these settings, add a DWORD key value with the appropriate Office locale ID (LCID). For example, the LCID for English (US) is 1033. Because LCIDs are decimal values, you must set the Base option for the DWORD value to Decimal. For a list of the Office LCIDs, see Language identifiers and OptionState Id values in Office 2016 in the Microsoft documentation.
Migrate a WorkSpace - After you create a BYOL bundle with Office installed, you can use the WorkSpaces migration feature to migrate your existing BYOL WorkSpaces to the BYOL bundle that's subscribed to Office. For more information, see Migrate a WorkSpace.
Amazon WorkSpaces searches for and displays available IP address ranges as IPv4 Classless Inter-Domain Routing (CIDR) blocks, within the range that you specify. If you require a specific IP address range, you can edit the search range.
After you specify an IP address range, you cannot modify it. Make sure to specify an IP address range that doesn't conflict with the ranges used by your internal network. If you have any questions about which range to specify, contact your AWS account manager or sales representative, or contact the AWS Support Center before proceeding.
760c119bf3