diff --git a/.gitignore b/.gitignore index acaea0eab..3eac81834 100644 --- a/.gitignore +++ b/.gitignore @@ -1,7 +1,7 @@ -log/ -obj/ -_site/ -.optemp/ -_themes*/ - +log/ +obj/ +_site/ +.optemp/ +_themes*/ + .openpublishing.buildcore.ps1 \ No newline at end of file diff --git a/.openpublishing.build.ps1 b/.openpublishing.build.ps1 index aadef7620..93bdf62f2 100644 --- a/.openpublishing.build.ps1 +++ b/.openpublishing.build.ps1 @@ -1,17 +1,17 @@ -param( - [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1", - [string]$parameters -) -# Main -$errorActionPreference = 'Stop' - -# Step-1: Download buildcore script to local -echo "download build core script to local with source url: $buildCorePowershellUrl" -$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition -$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1" -Invoke-WebRequest $buildCorePowershellUrl -OutFile "$buildCorePowershellDestination" - -# Step-2: Run build core -echo "run build core script with parameters: $parameters" -& "$buildCorePowershellDestination" "$parameters" -exit $LASTEXITCODE +param( + [string]$buildCorePowershellUrl = "https://opbuildstorageprod.blob.core.windows.net/opps1container/.openpublishing.buildcore.ps1", + [string]$parameters +) +# Main +$errorActionPreference = 'Stop' + +# Step-1: Download buildcore script to local +echo "download build core script to local with source url: $buildCorePowershellUrl" +$repositoryRoot = Split-Path -Parent $MyInvocation.MyCommand.Definition +$buildCorePowershellDestination = "$repositoryRoot\.openpublishing.buildcore.ps1" +Invoke-WebRequest $buildCorePowershellUrl -OutFile "$buildCorePowershellDestination" + +# Step-2: Run build core +echo "run build core script with parameters: $parameters" +& "$buildCorePowershellDestination" "$parameters" +exit $LASTEXITCODE diff --git a/.openpublishing.publish.config.json b/.openpublishing.publish.config.json index 769506ca3..b2f864bd8 100644 --- a/.openpublishing.publish.config.json +++ b/.openpublishing.publish.config.json @@ -1,36 +1,36 @@ -{ - "need_generate_pdf": false, - "need_generate_intellisense": false, - "docsets_to_publish": [ - { - "docset_name": "OfficeDocs-OfficeProPlus", - "build_source_folder": "DeployOffice", - "build_output_subfolder": "OfficeDocs-OfficeProPlus", - "locale": "en-us", - "monikers": [], - "moniker_ranges": [], - "open_to_public_contributors": false, - "type_mapping": { - "Conceptual": "Content", - "ManagedReference": "Content", - "RestApi": "Content" - }, - "build_entry_point": "docs", - "template_folder": "_themes", - "version": 0 - } - ], - "notification_subscribers": [], - "branches_to_filter": [], - "skip_source_output_uploading": false, - "need_preview_pull_request": false, - "dependent_repositories": [ - { - "path_to_root": "_themes", - "url": "https://github.com/Microsoft/templates.docs.msft", - "branch": "master", - "branch_mapping": {} - } - ], - "need_generate_pdf_url_template": false +{ + "need_generate_pdf": false, + "need_generate_intellisense": false, + "docsets_to_publish": [ + { + "docset_name": "OfficeDocs-OfficeProPlus", + "build_source_folder": "DeployOffice", + "build_output_subfolder": "OfficeDocs-OfficeProPlus", + "locale": "en-us", + "monikers": [], + "moniker_ranges": [], + "open_to_public_contributors": false, + "type_mapping": { + "Conceptual": "Content", + "ManagedReference": "Content", + "RestApi": "Content" + }, + "build_entry_point": "docs", + "template_folder": "_themes", + "version": 0 + } + ], + "notification_subscribers": [], + "branches_to_filter": [], + "skip_source_output_uploading": false, + "need_preview_pull_request": false, + "dependent_repositories": [ + { + "path_to_root": "_themes", + "url": "https://github.com/Microsoft/templates.docs.msft", + "branch": "master", + "branch_mapping": {} + } + ], + "need_generate_pdf_url_template": false } \ No newline at end of file diff --git a/DeployOffice/Deploy_O365ProPlus.md b/DeployOffice/Deploy_O365ProPlus.md new file mode 100644 index 000000000..45e6c268d --- /dev/null +++ b/DeployOffice/Deploy_O365ProPlus.md @@ -0,0 +1,98 @@ + + + +# [nav-overview](articles/.md) +## [Deployment guide](articles/deployment-guide-for-office-365-proplus.md) +## [What's new](articles/what-s-new-deploying-office-365-proplus-in-the-enterprise.md) +## [About Office 365 ProPlus](articles/about-office-365-proplus-in-the-enterprise.md) +# [nav-deploy](articles/.md) +## [Choose how to deploy](articles/choose-how-to-deploy-office-365-proplus.md) +## [From a local source](articles/deploy-office-365-proplus-from-a-local-source.md) +## [With Configuration Manager](articles/deploy-office-365-proplus-with-system-center-configuration-manager.md) +## [From the cloud](articles/deploy-office-365-proplus-from-the-cloud.md) +# [nav-manage-updates](articles/.md) +## [Upcoming changes](articles/overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md) +## [Update channels](articles/overview-of-update-channels-for-office-365-proplus.md) +## [Manage updates with Configuration Manager](articles/manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md) +## [Change management](articles/change-management-for-office-365-clients.md) +## [Version and build numbers](articles/version-and-build-numbers-of-update-channel-releases.md) +## [Update process](articles/overview-of-the-update-process-for-office-365-proplus.md) +## [Choose how to manage updates](articles/choose-how-to-manage-updates-to-office-365-proplus.md) +## [Configure update settings](articles/configure-update-settings-for-office-365-proplus.md) +# [nav-best-practices](articles/.md) +## [Best practices guide](articles/best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md) +## [Assess](articles/best-practices-for-assessing-your-infrastructure.md) +### [Best practices for assessment - reference materials](articles/best-practices-for-assessmentreference-materials.md) +### [Focus areas for assessment](articles/best-practices-focus-areas-for-assessment.md) +## [Plan](articles/best-practices-for-planning-your-deployment-of-office-365-proplus.md) +### [Best practices for planning - reference materials](articles/best-practices-for-planningreference-materials.md) +## [Deploy](articles/best-practices-for-deploying-office-365-proplus.md) +## [Manage updates](articles/best-practices-for-managing-updates-in-office-365-proplus.md) +## [Recommended deployment scenarios](articles/best-practices-recommended-deployment-scenarios.md) +### [Enterprise managed scenario](articles/best-practices-enterprise-managed-scenario.md) +#### [Assessment for enterprise managed](articles/best-practices-assessment-for-enterprise-managed.md) +#### [Planning for enterprise managed](articles/best-practices-planning-for-enterprise-managed.md) +#### [Deployment for enterprise managed](articles/best-practices-deployment-for-enterprise-managed.md) +##### [Download XML files for enterprise managed](articles/best-practices-download-xml-files-for-enterprise-managed.md) +##### [Install XML files for enterprise managed](articles/best-practices-install-xml-files-for-enterprise-managed.md) +##### [Uninstall XML files for enterprise managed](articles/best-practices-uninstall-xml-files-for-enterprise-managed.md) +##### [Configuration Manager for enterprise managed](articles/best-practices-system-center-configuration-manager-configuration-for-enterprise.md) +##### [Office 2016 Mac client install for enterprise managed](articles/best-practices-office-2016-mac-client-install-for-enterprise-managed.md) +#### [Management for enterprise managed](articles/best-practices-management-for-enterprise-managed.md) +### [Locally managed scenario](articles/best-practices-locally-managed-scenario.md) +#### [Assessment for locally managed](articles/best-practices-assessment-for-locally-managed.md) +#### [Planning for locally managed](articles/best-practices-planning-for-locally-managed.md) +#### [Deployment for locally managed](articles/best-practices-deployment-for-locally-managed.md) +##### [Download XML files for locally managed](articles/best-practices-download-xml-files-for-locally-managed.md) +##### [Install XML files for locally managed](articles/best-practices-install-xml-files-for-locally-managed.md) +##### [Uninstall XML files for locally managed](articles/best-practices-uninstall-xml-files-for-locally-managed.md) +##### [Distributed File System configuration for locally managed](articles/best-practices-distributed-file-system-configuration-for-locally-managed.md) +##### [Office 2016 Mac client install for locally managed](articles/best-practices-office-2016-mac-client-install-for-locally-managed.md) +#### [Management for locally managed](articles/best-practices-management-for-locally-managed.md) +### [Cloud managed scenario](articles/best-practices-cloud-managed-scenario.md) +#### [Assessment for cloud managed](articles/best-practices-assessment-for-cloud-managed.md) +#### [Planning for cloud managed](articles/best-practices-planning-for-cloud-managed.md) +#### [Deployment for cloud managed](articles/best-practices-deployment-for-cloud-managed.md) +##### [Download XML files for cloud managed](articles/best-practices-download-xml-files-for-cloud-managed.md) +##### [Install XML files for cloud managed](articles/best-practices-install-xml-files-for-cloud-managed.md) +##### [Uninstall XML files for cloud managed](articles/best-practices-uninstall-xml-files-for-cloud-managed.md) +##### [Office Content Delivery Network configuration for cloud managed](articles/best-practices-office-content-delivery-network-configuration-for-cloud-managed.md) +##### [Office 2016 Mac client install for cloud managed](articles/best-practices-office-2016-mac-client-install-for-cloud-managed.md) +#### [Management for cloud managed](articles/best-practices-management-for-cloud-managed.md) +### [Deployment scenarios](articles/best-practices-deployment-scenarios.md) +## [Deployment resources](articles/best-practices-deployment-resources.md) +### [Sample configuration files for downloading Office 365 ProPlus](articles/best-practices-sample-configuration-files-for-downloading-office-365-proplus.md) +### [Sample configuration files for installing Office 365 ProPlus](articles/best-practices-sample-configuration-files-for-installing-office-365-proplus.md) +### [Installing Office 365 ProPlus from CDN or DFS](articles/best-practices-for-installing-office-365-proplus-from-cdn-or-dfs.md) +#### [Step by step installation using CDN](articles/best-practices-step-by-step-installation-using-cdn.md) +#### [Step by step installation using DFS](articles/best-practices-step-by-step-installation-using-dfs.md) +### [Group Policy implementation](articles/best-practices-for-implementing-group-policy.md) +### [OffScrub](articles/best-practices-for-using-offscrub.md) +### [Office Telemetry](articles/best-practices-for-office-telemetry.md) +### [Deploying Office 2016 to Mac clients](articles/best-practices-for-deploying-office-2016-to-mac-clients.md) +### [Common debugging steps](articles/best-practices-common-debugging-steps.md) +## [Managing channels](articles/best-practices-for-managing-channels.md) +## [Managing reference material](articles/best-practices-managing-reference-material.md) +### [Update channels](articles/best-practices-update-channels.md) +### [Channel management](articles/best-practices-channel-management.md) +### [Links for administration education](articles/best-practices-links-for-administration-education.md) +### [Links for helpdesk and end user training](articles/best-practices-links-for-helpdesk-and-end-user-training.md) +## [Group policy](articles/best-practices-for-group-policy.md) +# [nav-reference](articles/.md) +## [Overview](articles/reference-articles-for-deploying-office-365-proplus.md) +## [Office 2016 Deployment Tool](articles/overview-of-the-office-2016-deployment-tool.md) +## [Configuration options for the Office 2016 Deployment Tool](articles/configuration-options-for-the-office-2016-deployment-tool.md) +## [Proofing Tools for Office 365 ProPlus](articles/proofing-tools-for-office-365-proplus.md) +## [Deploy with Remote Desktop Services](articles/deploy-office-365-proplus-by-using-remote-desktop-services.md) +## [Deploy as part of an operating system image](articles/deploy-office-365-proplus-as-part-of-an-operating-system-image.md) +## [Overview: Deploying languages in Office 365 ProPlus](articles/overview-deploying-languages-in-office-365-proplus.md) +## [Overview of shared computer activation for Office 365 ProPlus](articles/overview-of-shared-computer-activation-for-office-365-proplus.md) +## [Overview of licensing and activation in Office 365 ProPlus](articles/overview-of-licensing-and-activation-in-office-365-proplus.md) +## [Licensing and activation data sent to Office 365 by Office 365 ProPlus](articles/licensing-and-activation-data-sent-to-office-365-by-office-365-proplus.md) +## [Troubleshoot issues with shared computer activation for Office 365 ProPlus](articles/troubleshoot-issues-with-shared-computer-activation-for-office-365-proplus.md) +# [nav-upgrade](articles/.md) +## [Overview of upgrade to 2016](articles/overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md) +## [Plan your upgrade from 2013 to 2016](articles/plan-your-upgrade-from-office-365-proplus-2013-to-2016.md) +## [Configure updates to prepare for upgrade](articles/configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md) +## [Upgrade from ProPlus 2013 to 2016](articles/upgrade-from-office-365-proplus-2013-to-2016.md) + diff --git a/DeployOffice/Deploy_O365ProPlus_Errors_Found.csv b/DeployOffice/Deploy_O365ProPlus_Errors_Found.csv new file mode 100644 index 000000000..8045a3aa6 --- /dev/null +++ b/DeployOffice/Deploy_O365ProPlus_Errors_Found.csv @@ -0,0 +1,86 @@ +Error Type,Topic Guid,Message +Error,,Checking for list in tables in file: message:System.Collections.ArrayList +Error,,CHecking Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content in md file: message:System.Collections.ArrayList +Error,,Checking for missing tables headers in file: message:System.Collections.ArrayList +Error,,Running transform:ConceptualTransform.xslt on file: message:System.Collections.ArrayList +Error,,Running github process on file: message:System.Collections.ArrayList +Warning,091876a8-22ee-4685-bb88-adb9de85175a,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:setup.exe /configure <configurationXMLfilename>.xml in md file:091876a8-22ee-4685-bb88-adb9de85175a.md total found:0 +Warning,091876a8-22ee-4685-bb88-adb9de85175a,Missing tables headers in file:091876a8-22ee-4685-bb88-adb9de85175a.md +Warning,13aa8058-b524-4c73-930b-0802b2617ab4,Missing tables headers in file:13aa8058-b524-4c73-930b-0802b2617ab4.md +Warning,16cf763b-78a4-43dc-b05f-3efade197c0d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

<Display Level="None" AcceptEULA="True" />

in md file:16cf763b-78a4-43dc-b05f-3efade197c0d.md total found:0 +Warning,16cf763b-78a4-43dc-b05f-3efade197c0d,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:<No installed product keys detected> in md file:16cf763b-78a4-43dc-b05f-3efade197c0d.md total found:0 +Warning,190f41e4-064d-486b-9c95-db08f973687c,Found a an ul list inside a table in html file:190f41e4-064d-486b-9c95-db08f973687c.xml +Warning,190f41e4-064d-486b-9c95-db08f973687c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Release dates and build numbers that are italicized and enclosed in "< >" are subject to change.

in md file:190f41e4-064d-486b-9c95-db08f973687c.md total found:0 +Warning,1ee534fd-56dd-40fc-a463-470e8d636f09,Found a an ul list inside a table in html file:1ee534fd-56dd-40fc-a463-470e8d636f09.xml +Warning,2124a0dc-3f85-478c-a3da-c0b332b82095,Missing tables headers in file:2124a0dc-3f85-478c-a3da-c0b332b82095.md +Warning,278cea26-4657-45c1-aede-5365daa2f63c,Missing tables headers in file:278cea26-4657-45c1-aede-5365daa2f63c.md +Warning,29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line: setup.exe /configure <installXMLfilename>.xml in md file:29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f.md total found:0 +Warning,29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:setup.exe /configure <installXMLfilename>.xml in md file:29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f.md total found:0 +Warning,29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:setup.exe /configure <configurationXMLfilename>.xml in md file:29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f.md total found:0 +Warning,29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:setup.exe /configure <configurationXMLfilename>.xml in md file:29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f.md total found:0 +Warning,29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:setup.exe /configure <configurationXMLfilename>.xml in md file:29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f.md total found:0 +Warning,29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:setup.exe /configure <configurationXMLfilename>.xml in md file:29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f.md total found:0 +Warning,29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f,Missing tables headers in file:29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f.md +Warning,2f560823-aa43-4003-8f79-2750d3944060,Missing tables headers in file:2f560823-aa43-4003-8f79-2750d3944060.md +Warning,328bc4dc-79ab-4082-a897-25ebe4fc44a9,Missing tables headers in file:328bc4dc-79ab-4082-a897-25ebe4fc44a9.md +Warning,3a3b98be-c33e-4ed5-8403-9cf71eccb904,Missing tables headers in file:3a3b98be-c33e-4ed5-8403-9cf71eccb904.md +Warning,3c108fee-b271-4cb0-8b16-a134faf9f70c,Missing tables headers in file:3c108fee-b271-4cb0-8b16-a134faf9f70c.md +Warning,42a703ac-618c-4cb1-bc29-3014de45692b,Found nested table in md file:42a703ac-618c-4cb1-bc29-3014de45692b.md +Warning,42a703ac-618c-4cb1-bc29-3014de45692b,Fixing missing end table tag in file:42a703ac-618c-4cb1-bc29-3014de45692b.md +Warning,42a703ac-618c-4cb1-bc29-3014de45692b,Found invalid tables saving file:42a703ac-618c-4cb1-bc29-3014de45692b.md +Warning,5af6bb88-a92e-4fb0-ae1b-f11929fdf275,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

< 25 traveling users- some who are offsite for extended periods

in md file:5af6bb88-a92e-4fb0-ae1b-f11929fdf275.md total found:0 +Warning,5b5f4aab-7100-4e14-b3d6-218d0a267765,Missing tables headers in file:5b5f4aab-7100-4e14-b3d6-218d0a267765.md +Warning,5ce548ce-7a28-4ce4-a87f-ab4413bdcb40,Found a an ul list inside a table in html file:5ce548ce-7a28-4ce4-a87f-ab4413bdcb40.xml +Warning,5ebd1288-69ed-4425-a9cf-6253d6027005,Missing tables headers in file:5ebd1288-69ed-4425-a9cf-6253d6027005.md +Warning,68113166-4e85-45da-8963-ad65d3031ade,Missing tables headers in file:68113166-4e85-45da-8963-ad65d3031ade.md +Warning,733ff07f-8137-46e6-9904-70f59d716f6f,Found a an ul list inside a table in html file:733ff07f-8137-46e6-9904-70f59d716f6f.xml +Warning,78b33779-9356-4cdf-9d2c-08350ef05cca,Found a an ul list inside a table in html file:78b33779-9356-4cdf-9d2c-08350ef05cca.xml +Warning,80b82132-22c2-4628-84b4-fbbd6598aaba,Found a an ul list inside a table in html file:80b82132-22c2-4628-84b4-fbbd6598aaba.xml +Warning,80b82132-22c2-4628-84b4-fbbd6598aaba,Missing tables headers in file:80b82132-22c2-4628-84b4-fbbd6598aaba.md +Warning,80faf817-9559-459d-8e9c-e062b29fe9a3,Found a an ul list inside a table in html file:80faf817-9559-459d-8e9c-e062b29fe9a3.xml +Warning,80faf817-9559-459d-8e9c-e062b29fe9a3,Missing tables headers in file:80faf817-9559-459d-8e9c-e062b29fe9a3.md +Warning,8d86741d-51da-4b73-91bb-506579494bd3,Missing tables headers in file:8d86741d-51da-4b73-91bb-506579494bd3.md +Warning,8efa2040-4259-42e7-8087-f589adcc4190,Missing tables headers in file:8efa2040-4259-42e7-8087-f589adcc4190.md +Warning,98799ea9-3b93-46b4-b399-b9fcab3e1d80,Missing tables headers in file:98799ea9-3b93-46b4-b399-b9fcab3e1d80.md +Warning,9976a65c-2e66-4781-b830-02db03b1cdba,Missing tables headers in file:9976a65c-2e66-4781-b830-02db03b1cdba.md +Warning,99aa9fba-e188-4ca0-ac0a-2c82d6ed5242,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

< 1%

in md file:99aa9fba-e188-4ca0-ac0a-2c82d6ed5242.md total found:0 +Warning,99aa9fba-e188-4ca0-ac0a-2c82d6ed5242,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

< 10%

in md file:99aa9fba-e188-4ca0-ac0a-2c82d6ed5242.md total found:0 +Warning,99aa9fba-e188-4ca0-ac0a-2c82d6ed5242,Missing tables headers in file:99aa9fba-e188-4ca0-ac0a-2c82d6ed5242.md +Warning,9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd,Found a an ul list inside a table in html file:9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd.xml +Warning,9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd,Missing tables headers in file:9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd.md +Warning,9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd,Fixing missing end table tag in file:9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd.md +Warning,9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd,Fixing missing end table tag in file:9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd.md +Warning,9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd,Found invalid tables saving file:9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd.md +Warning,a073ea21-62ed-40ef-8405-fd287f7d0b11,Found a an ul list inside a table in html file:a073ea21-62ed-40ef-8405-fd287f7d0b11.xml +Warning,a2cf0c03-0c1d-4753-ac05-00aab2644f9d,Missing tables headers in file:a2cf0c03-0c1d-4753-ac05-00aab2644f9d.md +Warning,a7e61b05-c07c-4a14-9888-3ea61b30f2fc,Missing tables headers in file:a7e61b05-c07c-4a14-9888-3ea61b30f2fc.md +Warning,a7fcdebf-97e5-4551-84f8-f2cb993c16da,Missing tables headers in file:a7fcdebf-97e5-4551-84f8-f2cb993c16da.md +Warning,ac3e0d61-fd10-4caa-9b88-be55d1ef39bb,Missing tables headers in file:ac3e0d61-fd10-4caa-9b88-be55d1ef39bb.md +Warning,ae942449-1fca-4484-898b-a933ea23def7,Found a an ul list inside a table in html file:ae942449-1fca-4484-898b-a933ea23def7.xml +Warning,aef0e8b7-b36c-488d-a392-21720c139063,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

< 100 travelling users- some who are offsite for extended periods

in md file:aef0e8b7-b36c-488d-a392-21720c139063.md total found:0 +Warning,aef0e8b7-b36c-488d-a392-21720c139063,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

Remote Desktop Services and Citrix farm with < 500 users

in md file:aef0e8b7-b36c-488d-a392-21720c139063.md total found:0 +Warning,be130915-09ab-4303-b436-ae7b84266e28,Missing tables headers in file:be130915-09ab-4303-b436-ae7b84266e28.md +Warning,c3aeb487-d45f-4079-8c35-7558a45b876c,Found < > tag Bug 1235997:Support Request: MD conversion issue: not escaped tags causing missing content line:

PRODUCT NOTICE Your shared computer license expires on <date> and we're having trouble renewing it.

in md file:c3aeb487-d45f-4079-8c35-7558a45b876c.md total found:0 +Warning,c5aa7b52-77a0-464d-a295-5ee8e9a08f61,Missing tables headers in file:c5aa7b52-77a0-464d-a295-5ee8e9a08f61.md +Warning,c9ce5ffa-bfc7-4207-a6c0-c24fa9ae9db2,Missing tables headers in file:c9ce5ffa-bfc7-4207-a6c0-c24fa9ae9db2.md +Warning,d3879f0d-766c-469c-9440-0a9a2a905ca8,Found nested table in md file:d3879f0d-766c-469c-9440-0a9a2a905ca8.md +Warning,d66205f9-cf21-43df-bb19-af18cf0048bb,Missing tables headers in file:d66205f9-cf21-43df-bb19-af18cf0048bb.md +Warning,df4dba28-cc45-41a0-9b23-a1535523ab8c,Missing tables headers in file:df4dba28-cc45-41a0-9b23-a1535523ab8c.md +Warning,e9a8dd9f-732c-4c51-907b-59152acda975,Missing tables headers in file:e9a8dd9f-732c-4c51-907b-59152acda975.md +Warning,f4899394-87f3-425c-9902-ddd65eaaac97,Missing tables headers in file:f4899394-87f3-425c-9902-ddd65eaaac97.md + + +Warning,82691bd7-a3d5-47ca-8d8a-0ee43ec2c01f,Topic title:use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016-and-project-2016 bigger then max length:80 new topic titile name:use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016 +Warning,9b0b48f2-1937-4b10-8274-1ccdb2f5d019,Topic title:use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-office-365-proplus bigger then max length:80 new topic titile name:use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off +Warning,a7e61b05-c07c-4a14-9888-3ea61b30f2fc,Topic title:best-practices-system-center-configuration-manager-configuration-for-enterprise-managed bigger then max length:80 new topic titile name:best-practices-system-center-configuration-manager-configuration-for-enterprise- +Warning,1ee534fd-56dd-40fc-a463-470e8d636f09,Topic title:configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office-2016-version bigger then max length:80 new topic titile name:configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office +Warning,N/A,Sql Query:use [DDCMS_MOD_IW] SELECT tkw.[topicGuid] as topicGuid,kwf.[keyword] as f1Keyword + FROM [TopicKeywordsF] tkw join [dbo].[KeywordsF] kwf on tkw.[kwdGuid] = kwf.[kwdGuid] + join [dbo].[Topics] topics on topics.[topicGuid] = tkw.[topicGuid] + join [dbo].[Projects] pro on pro.[projectGuid] = topics.[homeProjectGuid] + where pro.[projectName] = 'Deploy_O365ProPlus' retuned no rows for project:Deploy_O365ProPlus server:ocpubcms for database:DDCMS_MOD_IW +Warning,N/A,Sql Query:use [DDCMS_MOD_IW] SELECT tkw.[topicGuid] as topicGuid,kwf.[keyword] as f1Keyword + FROM [TopicKeywordsF] tkw join [dbo].[KeywordsF] kwf on tkw.[kwdGuid] = kwf.[kwdGuid] + join [dbo].[Topics] topics on topics.[topicGuid] = tkw.[topicGuid] + join [dbo].[Projects] pro on pro.[projectGuid] = topics.[homeProjectGuid] + where pro.[projectName] = 'Deploy_O365ProPlus' retuned no rows for project:Deploy_O365ProPlus server:ocpubcms for database:DDCMS_MOD_IW diff --git a/DeployOffice/Deploy_O365ProPlus_Friendly_Name_Mapping.csv b/DeployOffice/Deploy_O365ProPlus_Friendly_Name_Mapping.csv new file mode 100644 index 000000000..ff7472f1a --- /dev/null +++ b/DeployOffice/Deploy_O365ProPlus_Friendly_Name_Mapping.csv @@ -0,0 +1,101 @@ +VBA Project,GUID,Friendly name +Deploy_O365ProPlus,a2cf0c03-0c1d-4753-ac05-00aab2644f9d,best-practices-deployment-for-locally-managed +Deploy_O365ProPlus,d4e4f2f7-35c8-4e2b-bf55-01807bd83235,nav-reference +Deploy_O365ProPlus,836f882c-8ff6-4f19-8b24-0212e0111c94,overview-of-shared-computer-activation-for-office-365-proplus +Deploy_O365ProPlus,9976a65c-2e66-4781-b830-02db03b1cdba,best-practices-for-deploying-office-2016-to-mac-clients +Deploy_O365ProPlus,13aa8058-b524-4c73-930b-0802b2617ab4,best-practices-sample-configuration-files-for-installing-office-365-proplus +Deploy_O365ProPlus,78b33779-9356-4cdf-9d2c-08350ef05cca,overview-of-the-upcoming-changes-to-office-365-proplus-update-management +Deploy_O365ProPlus,d3879f0d-766c-469c-9440-0a9a2a905ca8,configuration-options-for-the-office-2016-deployment-tool +Deploy_O365ProPlus,82691bd7-a3d5-47ca-8d8a-0ee43ec2c01f,use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016 +Deploy_O365ProPlus,bf1d87b1-3398-45e7-86cc-109995f3af76,best-practices-office-2016-mac-client-install-for-enterprise-managed +Deploy_O365ProPlus,9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd,change-management-for-office-365-clients +Deploy_O365ProPlus,bb5b62d9-1168-47e9-9d54-15a958acfcca,overview-of-the-office-2016-deployment-tool +Deploy_O365ProPlus,83ede0c2-474d-4b11-8723-1984d5279a4c,end-user-update-notifications-for-office-365-proplus +Deploy_O365ProPlus,9b0b48f2-1937-4b10-8274-1ccdb2f5d019,use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off +Deploy_O365ProPlus,aef0e8b7-b36c-488d-a392-21720c139063,best-practices-assessment-for-locally-managed +Deploy_O365ProPlus,5b5f4aab-7100-4e14-b3d6-218d0a267765,best-practices-download-xml-files-for-locally-managed +Deploy_O365ProPlus,328bc4dc-79ab-4082-a897-25ebe4fc44a9,best-practices-download-xml-files-for-cloud-managed +Deploy_O365ProPlus,d239ef5d-34d7-486f-a8e4-26eeec4e0a80,best-practices-cloud-managed-scenario +Deploy_O365ProPlus,2f560823-aa43-4003-8f79-2750d3944060,best-practices-deployment-for-enterprise-managed +Deploy_O365ProPlus,af9d7621-8c2c-4181-84b4-27778b1e7920,deploy-office-365-proplus-by-using-remote-desktop-services +Deploy_O365ProPlus,e486afce-ad31-4889-87a4-28796751bb86,choose-how-to-manage-updates-to-office-365-proplus +Deploy_O365ProPlus,99aa9fba-e188-4ca0-ac0a-2c82d6ed5242,best-practices-for-managing-channels +Deploy_O365ProPlus,42a703ac-618c-4cb1-bc29-3014de45692b,delay-receiving-feature-updates-from-deferred-channel-for-office-365-proplus +Deploy_O365ProPlus,ead29f67-69fa-4a79-88fc-3056ac3f2b6f,nav-overview +Deploy_O365ProPlus,7c80254b-cc14-441c-8500-333d32c71949,best-practices-for-managing-updates-in-office-365-proplus +Deploy_O365ProPlus,1096c33e-a6f2-44c8-9821-3cba07ec5750,overview-of-licensing-and-activation-in-office-365-proplus +Deploy_O365ProPlus,a7e61b05-c07c-4a14-9888-3ea61b30f2fc,best-practices-system-center-configuration-manager-configuration-for-enterprise +Deploy_O365ProPlus,16cf763b-78a4-43dc-b05f-3efade197c0d,deploy-office-365-proplus-as-part-of-an-operating-system-image +Deploy_O365ProPlus,3afa6514-2df3-4c52-a746-40a6ea4feeaa,best-practices-management-for-enterprise-managed +Deploy_O365ProPlus,1ee534fd-56dd-40fc-a463-470e8d636f09,configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office +Deploy_O365ProPlus,394f54fb-01ba-4be4-8606-4bce1ac39a31,best-practices-assessment-for-enterprise-managed +Deploy_O365ProPlus,8d86741d-51da-4b73-91bb-506579494bd3,best-practices-uninstall-xml-files-for-enterprise-managed +Deploy_O365ProPlus,1eca17f1-64f4-48ad-93ab-51f48aff70f4,best-practices-focus-areas-for-assessment +Deploy_O365ProPlus,278cea26-4657-45c1-aede-5365daa2f63c,best-practices-links-for-administration-education +Deploy_O365ProPlus,b4a17328-fcfe-40bf-9202-58d7cbf1cede,manage-updates-to-office-365-proplus-with-system-center-configuration-manager +Deploy_O365ProPlus,e9a8dd9f-732c-4c51-907b-59152acda975,best-practices-planning-for-cloud-managed +Deploy_O365ProPlus,7b5e0fde-11ff-4cd1-aceb-59f4ba77ff49,best-practices-office-2016-mac-client-install-for-locally-managed +Deploy_O365ProPlus,a6ada180-3f19-43b3-9291-5ec3cef88b2f,best-practices-deployment-resources +Deploy_O365ProPlus,c5aa7b52-77a0-464d-a295-5ee8e9a08f61,best-practices-office-content-delivery-network-configuration-for-cloud-managed +Deploy_O365ProPlus,5ebd1288-69ed-4425-a9cf-6253d6027005,best-practices-step-by-step-installation-using-dfs +Deploy_O365ProPlus,553200ea-c3d6-462f-a281-6399ebcca2be,nav-best-practices +Deploy_O365ProPlus,0a185e67-2b81-4c97-8c45-65984d8a9d9b,best-practices-update-channels +Deploy_O365ProPlus,07cf6be3-b6c7-435d-a1a7-6febe2cc3fd7,best-practices-for-using-offscrub +Deploy_O365ProPlus,733ff07f-8137-46e6-9904-70f59d716f6f,plan-your-upgrade-from-office-365-proplus-2013-to-2016 +Deploy_O365ProPlus,570c7fb3-d7a5-49cd-8cbf-7300ea656328,best-practices-for-office-telemetry +Deploy_O365ProPlus,4d9d796b-4291-4e0c-bd75-751b434eeb01,best-practices-deployment-scenarios +Deploy_O365ProPlus,c3aeb487-d45f-4079-8c35-7558a45b876c,troubleshoot-issues-with-shared-computer-activation-for-office-365-proplus +Deploy_O365ProPlus,41edd1c2-6d00-4855-9119-75f1d2f095af,nav-manage-updates +Deploy_O365ProPlus,6a135401-541b-458e-88ee-77cdf2cdd1c8,best-practices-managing-reference-material +Deploy_O365ProPlus,fb1e26ac-9818-424f-b319-78817eb6650b,nav-upgrade +Deploy_O365ProPlus,e270bbe0-5156-4587-871b-7b923b199743,what-s-new-deploying-office-365-proplus-in-the-enterprise +Deploy_O365ProPlus,9ccf0f13-28ff-4975-9bd2-7e4ea2fefef4,overview-of-update-channels-for-office-365-proplus +Deploy_O365ProPlus,ae2bcbfa-2c03-4f4d-b951-8352f079e3d0,best-practices-management-for-locally-managed +Deploy_O365ProPlus,742fd8e2-8931-416a-8120-8ee982a6c825,best-practices-for-planningreference-materials +Deploy_O365ProPlus,f5062b95-6346-4e25-a2a3-91667aa7650e,nav-deploy +Deploy_O365ProPlus,48c953de-270e-4809-bd7d-93431159a047,best-practices-locally-managed-scenario +Deploy_O365ProPlus,3a3b98be-c33e-4ed5-8403-9cf71eccb904,best-practices-install-xml-files-for-locally-managed +Deploy_O365ProPlus,3c108fee-b271-4cb0-8b16-a134faf9f70c,best-practices-deployment-for-cloud-managed +Deploy_O365ProPlus,df4dba28-cc45-41a0-9b23-a1535523ab8c,best-practices-for-planning-your-deployment-of-office-365-proplus +Deploy_O365ProPlus,b18a9110-0d14-46ec-af54-a22793ef6b38,deploy-office-365-proplus-from-the-cloud +Deploy_O365ProPlus,e0deafc7-4646-49ea-9882-a2ad8b47a7e4,best-practices-for-group-policy +Deploy_O365ProPlus,8e5133dc-6bd5-46e8-a39c-a544d8c7bcdd,best-practices-office-2016-mac-client-install-for-cloud-managed +Deploy_O365ProPlus,9f11214c-911d-4e3c-9993-a566f12b1a68,about-office-365-proplus-in-the-enterprise +Deploy_O365ProPlus,f8a53994-d9e5-46db-aa90-a704bcca2473,best-practices-for-deploying-office-365-proplus +Deploy_O365ProPlus,31a384ca-650c-4265-b76c-a87b414fd8b8,best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise +Deploy_O365ProPlus,ae942449-1fca-4484-898b-a933ea23def7,version-and-build-numbers-of-update-channel-releases +Deploy_O365ProPlus,e471ef30-2a09-4767-a172-aa74e1dc4686,choose-how-to-deploy-office-365-proplus +Deploy_O365ProPlus,5ce548ce-7a28-4ce4-a87f-ab4413bdcb40,upgrade-from-office-365-proplus-2013-to-2016 +Deploy_O365ProPlus,68113166-4e85-45da-8963-ad65d3031ade,best-practices-install-xml-files-for-cloud-managed +Deploy_O365ProPlus,091876a8-22ee-4685-bb88-adb9de85175a,best-practices-channel-management +Deploy_O365ProPlus,be130915-09ab-4303-b436-ae7b84266e28,best-practices-install-xml-files-for-enterprise-managed +Deploy_O365ProPlus,d66205f9-cf21-43df-bb19-af18cf0048bb,best-practices-uninstall-xml-files-for-locally-managed +Deploy_O365ProPlus,36b7ec08-9f97-4d76-a600-b9e424005792,best-practices-enterprise-managed-scenario +Deploy_O365ProPlus,98799ea9-3b93-46b4-b399-b9fcab3e1d80,best-practices-planning-for-enterprise-managed +Deploy_O365ProPlus,ac3e0d61-fd10-4caa-9b88-be55d1ef39bb,best-practices-planning-for-locally-managed +Deploy_O365ProPlus,2124a0dc-3f85-478c-a3da-c0b332b82095,best-practices-distributed-file-system-configuration-for-locally-managed +Deploy_O365ProPlus,c9ce5ffa-bfc7-4207-a6c0-c24fa9ae9db2,best-practices-uninstall-xml-files-for-cloud-managed +Deploy_O365ProPlus,f7d07a88-35c3-48f5-b30e-c842f2d911a5,licensing-and-activation-data-sent-to-office-365-by-office-365-proplus +Deploy_O365ProPlus,29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f,best-practices-step-by-step-installation-using-cdn +Deploy_O365ProPlus,484b129d-9220-409e-bf0c-d0057653f793,best-practices-for-implementing-group-policy +Deploy_O365ProPlus,f3986751-46f7-4e61-b71b-d509736132a6,reference-preferred-gpo-baseline +Deploy_O365ProPlus,190f41e4-064d-486b-9c95-db08f973687c,download-sizes-approximate-for-channel-updates-to-office-365-proplus +Deploy_O365ProPlus,6df5de04-6b8e-48af-aede-dceaefacc278,reference-articles-for-deploying-office-365-proplus +Deploy_O365ProPlus,f4899394-87f3-425c-9902-ddd65eaaac97,best-practices-for-assessing-your-infrastructure +Deploy_O365ProPlus,4d4ff951-ee72-4763-806a-deeb384a369b,best-practices-recommended-deployment-scenarios +Deploy_O365ProPlus,80faf817-9559-459d-8e9c-e062b29fe9a3,best-practices-links-for-helpdesk-and-end-user-training +Deploy_O365ProPlus,21c562f2-2e54-452d-8ef5-e39c236bfaf1,proofing-tools-for-office-365-proplus +Deploy_O365ProPlus,7655b5cb-89ae-4a08-9621-e5af1b77cfe1,overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version +Deploy_O365ProPlus,35d4cb3b-4cc9-4bc9-9f20-eaf3c50f8331,deploy-office-365-proplus-from-a-local-source +Deploy_O365ProPlus,5af6bb88-a92e-4fb0-ae1b-f11929fdf275,best-practices-assessment-for-cloud-managed +Deploy_O365ProPlus,a7fcdebf-97e5-4551-84f8-f2cb993c16da,best-practices-download-xml-files-for-enterprise-managed +Deploy_O365ProPlus,f99f8cd0-e648-4834-8f45-f5637351899d,deployment-guide-for-office-365-proplus +Deploy_O365ProPlus,8efa2040-4259-42e7-8087-f589adcc4190,best-practices-sample-configuration-files-for-downloading-office-365-proplus +Deploy_O365ProPlus,6467979c-3430-45c2-a28f-f9ac995731a5,overview-deploying-languages-in-office-365-proplus +Deploy_O365ProPlus,936cda26-41f9-45b5-a1f9-f9e1f485d23b,overview-of-the-update-process-for-office-365-proplus +Deploy_O365ProPlus,80b82132-22c2-4628-84b4-fbbd6598aaba,best-practices-for-installing-office-365-proplus-from-cdn-or-dfs +Deploy_O365ProPlus,a7f2fec4-75cb-49de-8e03-fc8e7a4691b5,best-practices-management-for-cloud-managed +Deploy_O365ProPlus,b584fcff-d64d-426a-b20f-fc93707cf46c,best-practices-common-debugging-steps +Deploy_O365ProPlus,a073ea21-62ed-40ef-8405-fd287f7d0b11,configure-update-settings-for-office-365-proplus +Deploy_O365ProPlus,f9bb5ed7-8d41-40fb-9804-fecfba7e5d6d,best-practices-for-assessmentreference-materials +Deploy_O365ProPlus,4dd6a023-0a5d-4dc9-9bad-ff70e01840b8,deploy-office-365-proplus-with-system-center-configuration-manager diff --git a/DeployOffice/TOC.md b/DeployOffice/TOC.md index 06913f7ae..b7decba9d 100644 --- a/DeployOffice/TOC.md +++ b/DeployOffice/TOC.md @@ -1 +1,96 @@ -# [Index](index.md) \ No newline at end of file +# DeployOffice Test Table of Contents +## [About Office 365 ProPlus in the enterprise](about-office-365-proplus-in-the-enterprise.md) +## [Best practices Assessment for cloud managed](best-practices-assessment-for-cloud-managed.md) +## [Best practices Assessment for enterprise managed](best-practices-assessment-for-enterprise-managed.md) +## [Best practices Assessment for locally managed](best-practices-assessment-for-locally-managed.md) +## [Best practices Channel management](best-practices-channel-management.md) +## [Best practices Cloud managed scenario](best-practices-cloud-managed-scenario.md) +## [Best practices Common debugging steps](best-practices-common-debugging-steps.md) +## [Best practices Deployment for cloud managed](best-practices-deployment-for-cloud-managed.md) +## [Best practices Deployment for enterprise managed](best-practices-deployment-for-enterprise-managed.md) +## [Best practices Deployment for locally managed](best-practices-deployment-for-locally-managed.md) +## [Best practices Deployment resources](best-practices-deployment-resources.md) +## [Best Practices Deployment scenarios](best-practices-deployment-scenarios.md) +## [Best practices Distributed File System configuration for locally managed](best-practices-distributed-file-system-configuration-for-locally-managed.md) +## [Best practices Download XML files for cloud managed](best-practices-download-xml-files-for-cloud-managed.md) +## [Best practices Download XML files for enterprise managed](best-practices-download-xml-files-for-enterprise-managed.md) +## [Best practices Download XML files for locally managed](best-practices-download-xml-files-for-locally-managed.md) +## [Best practices Enterprise managed scenario](best-practices-enterprise-managed-scenario.md) +## [Best practices Focus areas for assessment](best-practices-focus-areas-for-assessment.md) +## [Best practices for assessing your infrastructure](best-practices-for-assessing-your-infrastructure.md) +## [Best practices for assessment - reference materials](best-practices-for-assessmentreference-materials.md) +## [Best practices for deploying Office 2016 to Mac clients](best-practices-for-deploying-office-2016-to-mac-clients.md) +## [Best practices for deploying Office 365 ProPlus](best-practices-for-deploying-office-365-proplus.md) +## [Best practices for group policy](best-practices-for-group-policy.md) +## [Best practices for implementing group policy](best-practices-for-implementing-group-policy.md) +## [Best practices for installing Office 365 ProPlus from CDN or DFS](best-practices-for-installing-office-365-proplus-from-cdn-or-dfs.md) +## [Best practices for managing channels](best-practices-for-managing-channels.md) +## [Best practices for managing updates in Office 365 ProPlus](best-practices-for-managing-updates-in-office-365-proplus.md) +## [Best practices for Office Telemetry](best-practices-for-office-telemetry.md) +## [Best practices for planning your deployment of Office 365 ProPlus](best-practices-for-planning-your-deployment-of-office-365-proplus.md) +## [Best practices for planning - reference materials](best-practices-for-planningreference-materials.md) +## [Best practices for using OffScrub](best-practices-for-using-offscrub.md) +## [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md) +## [Best practices Install XML files for cloud managed](best-practices-install-xml-files-for-cloud-managed.md) +## [Best practices Install XML files for enterprise managed](best-practices-install-xml-files-for-enterprise-managed.md) +## [Best practices Install XML files for locally managed](best-practices-install-xml-files-for-locally-managed.md) +## [Best practices Links for administration education](best-practices-links-for-administration-education.md) +## [Best practices Links for helpdesk and end user training](best-practices-links-for-helpdesk-and-end-user-training.md) +## [Best practices Locally managed scenario](best-practices-locally-managed-scenario.md) +## [Best practices Management for cloud managed](best-practices-management-for-cloud-managed.md) +## [Best practices Management for enterprise managed](best-practices-management-for-enterprise-managed.md) +## [Best practices Management for locally managed](best-practices-management-for-locally-managed.md) +## [Best practices Managing reference material](best-practices-managing-reference-material.md) +## [Best practices Office 2016 Mac client install for cloud managed](best-practices-office-2016-mac-client-install-for-cloud-managed.md) +## [Best practices Office 2016 Mac client install for enterprise managed](best-practices-office-2016-mac-client-install-for-enterprise-managed.md) +## [Best practices Office 2016 Mac client install for locally managed](best-practices-office-2016-mac-client-install-for-locally-managed.md) +## [Best practices Office Content Delivery Network configuration for cloud managed](best-practices-office-content-delivery-network-configuration-for-cloud-managed.md) +## [Best practices Planning for cloud managed](best-practices-planning-for-cloud-managed.md) +## [Best practices Planning for enterprise managed](best-practices-planning-for-enterprise-managed.md) +## [Best practices Planning for locally managed](best-practices-planning-for-locally-managed.md) +## [Best practices Recommended deployment scenarios](best-practices-recommended-deployment-scenarios.md) +## [Best practices Sample configuration files for downloading Office 365 ProPlus](best-practices-sample-configuration-files-for-downloading-office-365-proplus.md) +## [Best practices Sample configuration files for installing Office 365 ProPlus](best-practices-sample-configuration-files-for-installing-office-365-proplus.md) +## [Best practices Step by step installation using CDN](best-practices-step-by-step-installation-using-cdn.md) +## [Best practices Step by step installation using DFS](best-practices-step-by-step-installation-using-dfs.md) +## [Best practices System Center Configuration Manager configuration for enterprise managed](best-practices-system-center-configuration-manager-configuration-for-enterprise.md) +## [Best practices Uninstall XML files for cloud managed](best-practices-uninstall-xml-files-for-cloud-managed.md) +## [Best practices Uninstall XML files for enterprise managed](best-practices-uninstall-xml-files-for-enterprise-managed.md) +## [Best practices Uninstall XML files for locally managed](best-practices-uninstall-xml-files-for-locally-managed.md) +## [Best practices Update channels](best-practices-update-channels.md) +## [Change management for Office 365 clients](change-management-for-office-365-clients.md) +## [Choose how to deploy Office 365 ProPlus](choose-how-to-deploy-office-365-proplus.md) +## [Choose how to manage updates to Office 365 ProPlus](choose-how-to-manage-updates-to-office-365-proplus.md) +## [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) +## [Configure update settings for Office 365 ProPlus](configure-update-settings-for-office-365-proplus.md) +## [Configure updates of Office 365 ProPlus to prepare for the upgrade to the Office 2016 version](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md) +## [Delay receiving feature updates from Deferred Channel for Office 365 ProPlus](delay-receiving-feature-updates-from-deferred-channel-for-office-365-proplus.md) +## [Deploy Office 365 ProPlus as part of an operating system image](deploy-office-365-proplus-as-part-of-an-operating-system-image.md) +## [Deploy Office 365 ProPlus by using Remote Desktop Services](deploy-office-365-proplus-by-using-remote-desktop-services.md) +## [Deploy Office 365 ProPlus from a local source](deploy-office-365-proplus-from-a-local-source.md) +## [Deploy Office 365 ProPlus from the cloud](deploy-office-365-proplus-from-the-cloud.md) +## [Deploy Office 365 ProPlus with System Center Configuration Manager](deploy-office-365-proplus-with-system-center-configuration-manager.md) +## [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) +## [[nav-overview](articles/.md)](Deploy_O365ProPlus.md) +## [Download sizes (approximate) for channel updates to Office 365 ProPlus](download-sizes-approximate-for-channel-updates-to-office-365-proplus.md) +## [End-user update notifications for Office 365 ProPlus](end-user-update-notifications-for-office-365-proplus.md) +## [Welcome to OfficeDocs-OfficeProPlus!](index.md) +## [Licensing and activation data sent to Office 365 by Office 365 ProPlus](licensing-and-activation-data-sent-to-office-365-by-office-365-proplus.md) +## [Manage updates to Office 365 ProPlus with System Center Configuration Manager](manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md) +## [Overview Deploying languages in Office 365 ProPlus](overview-deploying-languages-in-office-365-proplus.md) +## [Overview of licensing and activation in Office 365 ProPlus](overview-of-licensing-and-activation-in-office-365-proplus.md) +## [Overview of shared computer activation for Office 365 ProPlus](overview-of-shared-computer-activation-for-office-365-proplus.md) +## [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md) +## [Overview of the upcoming changes to Office 365 ProPlus update management](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md) +## [Overview of the update process for Office 365 ProPlus](overview-of-the-update-process-for-office-365-proplus.md) +## [Overview of the upgrade of Office 365 ProPlus to the Office 2016 version](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md) +## [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) +## [Plan your upgrade from Office 365 ProPlus 2013 to 2016](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md) +## [Proofing Tools for Office 365 ProPlus](proofing-tools-for-office-365-proplus.md) +## [Reference articles for deploying Office 365 ProPlus](reference-articles-for-deploying-office-365-proplus.md) +## [Troubleshoot issues with shared computer activation for Office 365 ProPlus](troubleshoot-issues-with-shared-computer-activation-for-office-365-proplus.md) +## [Upgrade from Office 365 ProPlus 2013 to 2016](upgrade-from-office-365-proplus-2013-to-2016.md) +## [Use the Office Compatibility Toolkit to assess application compatibility for Office 365 ProPlus](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md) +## [Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016](use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016.md) +## [Version and build numbers of update channel releases](version-and-build-numbers-of-update-channel-releases.md) +## [What's new Deploying Office 365 ProPlus in the enterprise](what-s-new-deploying-office-365-proplus-in-the-enterprise.md) diff --git a/DeployOffice/about-office-365-proplus-in-the-enterprise.md b/DeployOffice/about-office-365-proplus-in-the-enterprise.md new file mode 100644 index 000000000..902991b94 --- /dev/null +++ b/DeployOffice/about-office-365-proplus-in-the-enterprise.md @@ -0,0 +1,131 @@ +--- +title: About Office 365 ProPlus in the enterprise +ms.prod: OFFICE365 +ms.assetid: 9f11214c-911d-4e3c-9993-a566f12b1a68 +--- + + +# About Office 365 ProPlus in the enterprise + +Office 365 ProPlus is a version of Office that's available through Office 365. It includes the applications that you're familiar with, including Access, Excel, OneNote, Outlook, PowerPoint, Publisher, Skype for Business, and Word. You can use these applications to connect with Office 365 services such as SharePoint Online, Exchange Online, and Skype for Business Online. + + + + + +> [!NOTE] +> Office 365 ProPlus is available as a standalone offering, or as part of other Office 365 plans, such as Office 365 Enterprise E3. > Project and Visio aren't included with Office 365 ProPlus, but are available from other Office 365 plans. > For more information about Office 365 plans, see [https://products.office.com](https://products.office.com) and the [Office 365 Service Descriptions](https://go.microsoft.com/fwlink/p/?LinkID=303961). + + + + + +## Office 365 ProPlus is similar to other versions of Office + + +Office 365 ProPlus is similar to other versions of Office that you can deploy to your users. Here are some important similarities: + + + + +- Office 365 ProPlus is a full version of Office. The in-product environment, such as the ribbon, will be familiar to Office users. + + +- Its system requirements (for example, memory, hard disk space, and operating system) are similar to other current versions of Office. For more information, see [System requirements for Office](https://products.office.com/office-system-requirements). + + +- Like other versions of Office, Office 365 ProPlus is available in a 32-bit and a 64-bit version. To decide which version is right for your environment, carefully review [Choose the 64-bit or 32-bit version of Office](http://technet.microsoft.com/library/2dee7807-8f95-4d0c-b5fe-6c6f49b8d261%28Office.14%29.aspx) before you deploy. + + +- When you deploy Office 365 ProPlus, it's installed on the user's local computer. Office 365 ProPlus is not a web-based version of Office. It runs locally on the user's computer. Users don't need to be connected to the Internet all the time to use it. + + +- You can use many of the same tools to deploy and configure Office 365 ProPlus that you're already using to deploy Office. For example, you can use System Center Configuration Manager to deploy Office 365 ProPlus. For more information, see [Choose how to deploy Office 365 ProPlus](choose-how-to-deploy-office-365-proplus.md). + + +- In addition, you can use many of the same Group Policy settings that you use with other versions of Office to configure and enforce Office 365 ProPlus program settings. + + + +## What's different about Office 365 ProPlus? + + +Even though Office 365 ProPlus is a lot like other versions of Office, there are differences, including for [Deployment differences](about-office-365-proplus-in-the-enterprise.md#BKMK_Deployment) and [Licensing differences](about-office-365-proplus-in-the-enterprise.md#BKMK_Licensing). + + + +The most significant difference is that Office 365 ProPlus is updated regularly, as often as monthly, with new features, unlike non-subscription versions of Office. For a list of new features, see [What's new and improved in Office 2016 for Office 365](http://technet.microsoft.com/library/95c8d81d-08ba-42c1-914f-bca4603e1426%28Office.14%29.aspx). + + + + +### Deployment differences + + + +- By default, Office 365 ProPlus installs as one package. This means that all Office programs are installed on the user's computer. But, you can configure the deployment to [Exclude or remove Office 365 ProPlus products from client computers](overview-of-the-office-2016-deployment-tool.md#BKMK_excludeorremove), such as Access. + + +- Because Office 365 ProPlus uses a different installation technology, called Click-to-Run, there's a different way to apply software updates, such as security updates. By default, Office 365 ProPlus is configured to automatically install updates from the Office Content Delivery Network (CDN) on the Internet. But, you can configure Office 365 ProPlus to install updates from a location within your own network or you can [Manage updates to Office 365 ProPlus with System Center Configuration Manager](manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md). + + +- Office 365 ProPlus also provides the ability to control how often users receive feature updates. For example, users can get new features to Office 365 ProPlus as soon as they are available. Or, if you have line-of-business applications, add-ins, or macros that you want to test with the new features, you can provide users with new features less frequently. For more information, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md). + + +- Office 365 provides a web-based portal where users can install Office 365 ProPlus themselves. Keep in mind that users have to be local administrators on their computers to install Office 365 ProPlus. If users aren't local administrators, you'll have to install Office 365 ProPlus for them. Also, if you don't want your users to install from the portal, you can prevent that. For more information, see [Choose how to deploy Office 365 ProPlus](choose-how-to-deploy-office-365-proplus.md). + + + +### Licensing differences + + + +- Users can install Office 365 ProPlus on up to five different computers with a single Office 365 license. For example, a user can have Office 365 ProPlus installed on a computer in the office, on a laptop to use when traveling, and on a home computer. Users can also install on up to 5 tablets and 5 phones. + + +- Office 365 ProPlus is offered as a subscription. If you cancel your subscription, Office 365 ProPlus goes into reduced functionality mode. In reduced functionality mode, users can open and view existing Office files, but users can't use most of the other features of Office 365 ProPlus. For more information, see [Overview of licensing and activation in Office 365 ProPlus](overview-of-licensing-and-activation-in-office-365-proplus.md). + + +- To use Office 365 ProPlus, a user must have an Office 365 account and have been assigned a license. If the user's license or account is removed, the user's installations of Office 365 ProPlus go into reduced functionality mode. + + +- Even though users don't need to be connected to the Internet all the time to use Office 365 ProPlus, users must connect to the Internet at least once every 30 days. This is so that the status of their Office 365 subscriptions can be checked. If users don't connect within 30 days, Office 365 ProPlus goes into reduced functionality mode. After users connect to the Internet and their subscription status is verified, all the features of Office 365 ProPlus are available again. + + + +## More information about Office 365 ProPlus + + + +- You can use Office 365 ProPlus with supported versions of Exchange Server or SharePoint Server that are installed on-premises in your organization. Or, if they're part of your Office 365 plan, you can use Office 365 ProPlus with Exchange Online and SharePoint Online. + + +- Users can store the files they create with Office 365 ProPlus on their local computers or elsewhere on your network, such as a SharePoint site. Office 365 also provides cloud-based file storage options, + + +- Office 365 ProPlus isn't the same as [Office Online](https://go.microsoft.com/fwlink/p/?LinkID=303963). Office Online lets users open Word, Excel, PowerPoint, or OneNote documents in a web browser. Office Online is included with all Office 365 plans. + + +- Read the [Office 365 Service Descriptions](https://go.microsoft.com/fwlink/p/?LinkID=303961) to learn more about what's included in Office 365. + + + +## See also + + + +#### Other Resources + + + + + + [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) + + + + [Compare enterprise plans for Office 365](https://products.office.com/en-us/business/compare-more-office-365-for-business-plans) + + + + [Purchase Office 365 ProPlus](https://go.microsoft.com/fwlink/p/?LinkID=329114) diff --git a/DeployOffice/best-practices-assessment-for-cloud-managed.md b/DeployOffice/best-practices-assessment-for-cloud-managed.md new file mode 100644 index 000000000..d08f108a2 --- /dev/null +++ b/DeployOffice/best-practices-assessment-for-cloud-managed.md @@ -0,0 +1,112 @@ +--- +title: Best practices Assessment for cloud managed +ms.prod: OFFICE365 +ms.assetid: 5af6bb88-a92e-4fb0-ae1b-f11929fdf275 +--- + + +# Best practices: Assessment for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *The Best Practices for Office 365 ProPlus Deployment has been created by a team of subject matter experts from the Office 365 Product Group, Office 365 Product Marketing Group, and delivery experts from Microsoft Services. The recommendations include application discovery, deployment, channel management, and reporting. For a list of all the best practices articles, see [Best practices: Recommended deployment scenarios](best-practices-recommended-deployment-scenarios.md).* +The goal for *Cloud Managed* is to modernize their existing Office implementation by migrating to Office 365 ProPlus using Office Content Delivery Network (CDN). Users productivity should not be impacted due to the migration, and 32-Bit Office users will receive Office 365 ProPlus 32-bit. + + + + + +## Assessment results + + +### Size and distribution + + +- 500+ employees + + +- 1 supported language + + +- US-based company + + +- < 25 traveling users, some who are offsite for extended periods + + +- Sites are small offices + + + +### IT infrastructure + + +- Windows 10 Pro 64-bit + + +- ~5 Mac users whos have local administrator rights + + +- Mac clients are not managed by client management software + + +- All systems have EN-US language pack installed with additional languages per region or pulled by the user + + +- Desktops, notebooks, and shared devices for shift workers + + +- Network bandwidth is sufficient for daily business + + +- Windows clients are not managed through client management software + + +- Office 365 ProPlus will be made available through the Office 365 portal + + +- Users have local administrative rights on their machines + + +- Network is a distributed layout with a small number of high-bandwidth internet interconnection points + + + +### Application landscape + + +- Office 2010 Volume License (MSI) 32-bit + + +- Some pilot users may have Office Professional Plus 2013 (MSI) 32-bit, as well as Project and Visio 2013 (MSI) 32-bit + + +- Project 2010 and Visio 2010 (MSI) 32-bit that will be moved to Project and Visio 2013 (MSI) 32-bit + + + +### Cloud infrastructure + + +- Office 365 tenant with Azure AD Connect + + +- On-Premises Active Directory Federation Services with Single Sign-on (SSO) + + +- Exchange Online deployed in production + + +- SharePoint Online deployed in production + + +- OneDrive deployed + + +- Self-service including installations are not blocked in the portal + + + diff --git a/DeployOffice/best-practices-assessment-for-enterprise-managed.md b/DeployOffice/best-practices-assessment-for-enterprise-managed.md new file mode 100644 index 000000000..8fdc2c6e1 --- /dev/null +++ b/DeployOffice/best-practices-assessment-for-enterprise-managed.md @@ -0,0 +1,112 @@ +--- +title: Best practices Assessment for enterprise managed +ms.prod: OFFICE365 +ms.assetid: 394f54fb-01ba-4be4-8606-4bce1ac39a31 +--- + + +# Best practices: Assessment for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Enterprise Managed* success criteria is to deploy Office 365 ProPlus in a like-for-like fashion. Users should get the application set they had before, including Project and Visio, and their existing languages. 32-bit users should be kept on 32-bit, and 64-bit users should receive the appropriate 64- bit version. All InfoPath-based LOB applications must continue to work. Everything should work as before, with a minimal user impact and management overhead. +## Assessment results + + +### Size and distribution + + +- 20,000+ employees + + +- 17 supported languages + + +- Worldwide across the Americas, EMEA and APAC regions + + +- 1,000s of travelling users, most of whom are offsite for extended periods + + +- Sites are ranging from small offices up to a larger campus + + + +### IT infrastructure + + +- Windows 7 64-bit + + +- Small pockets of Mac users, ~500 total, managed by a third party Mac software distribution tool + + +- All systems have en-us language pack installed, with additional languages per region or pulled by the user + + +- Desktops, notebooks, and shared devices for shift workers + + +- Remote Desktop Services and Citrix farm with 1,000s of users + + +- Static and dynamic Virtual Desktop Infrastructure (VDI) for a smaller user group + + +- Network bandwidth is sufficient for daily business + + +- Windows clients managed by System Center Configuration Manager + + +- High bandwidth deployments (such as a 1 GB Office package) require pre -caching and staged deployment + + +- Users do not have administrative rights on their machines + + +- Network is a distributed layout with a small number of high-bandwidth internet interconnection points + + + +### Application landscape + + +- Office 2010 Volume License (MSI) 32-bit + + +- Groups of users who use Project 2010 and Visio 2010 (MSI) 32-bit + + +- Finance department uses Office 2010 64-bit for working with large data sets + + +- Small pockets still run Office/Visio/Project 2007 (MSI) 32-bit + + +- OneDrive is in the evaluation phase and should not be deployed until signed off on + + +- Due to legacy Line-of-Business (LOB) applications, InfoPath is required + + + +### Cloud infrastructure + + +- Office 365 tenant with Azure AD Connect + + +- On-Premises Active Directory Federation Services with Single Sign-on (SSO) + + +- Exchange Online deployed in production + + +- Self-service installations are blocked in the portal + + + diff --git a/DeployOffice/best-practices-assessment-for-locally-managed.md b/DeployOffice/best-practices-assessment-for-locally-managed.md new file mode 100644 index 000000000..2b2e80fe7 --- /dev/null +++ b/DeployOffice/best-practices-assessment-for-locally-managed.md @@ -0,0 +1,97 @@ +--- +title: Best practices Assessment for locally managed +ms.prod: OFFICE365 +ms.assetid: aef0e8b7-b36c-488d-a392-21720c139063 +--- + + +# Best practices: Assessment for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Locally Managed* success criteria is to deploy Office 365 ProPlus in a like-for-like fashion, replacing the previous version of Office. Users should get the application set they had before, including Visio and Project, and the existing languages. InfoPath-based LOB applications must continue to work, with minimal user impact and management overhead. *Locally Managed* only supports 32-bit Office so all users will remain on 32-bit Office. +## Assessments results + + +### Size and distribution + + +- 5000 employees + + +- 3 supported languages + + +- Canada, USA, and Germany + + +- < 100 travelling users, some who are offsite for extended periods + + +- Sites are a main office in each country, limited small offices throughout each country + + + +### IT infrastructure + + +- Windows 7 64-bit + + +- Small group of Mac users, ~25 who users have local administrator rights + + +- Mac clients are not managed by client management software + + +- All systems have en-us language pack installed with additional languages in CanAm region or pulled by the user + + +- Remote Desktop Services and Citrix farm with < 500 users + + +- Network bandwidth is sufficient for daily business + + +- Users do not have administrative rights on their machines + + +- Network is a distributed layout with a small number of high-bandwidth internet interconnection points + + + +### Application landscape + + +- Office 2010 Volume License (MSI) 32-bit + + +- Groups of users using Project 2010 and Visio 2010 32-bit + + +- All applications other than Access being deployed + + +- Due to legacy Line-of-Business (LOB) applications, InfoPath is required + + + +### Cloud infrastructure + + +- Office 365 tenant with Azure AD Connect + + +- On-Premises Active Directory Federation Services with Single Sign-on (SSO) + + +- Exchange Online deployed in production + + +- Self-service including installations are not blocked in the portal + + + diff --git a/DeployOffice/best-practices-channel-management.md b/DeployOffice/best-practices-channel-management.md new file mode 100644 index 000000000..a3c8fbe36 --- /dev/null +++ b/DeployOffice/best-practices-channel-management.md @@ -0,0 +1,152 @@ +--- +title: Best practices Channel management +ms.prod: OFFICE365 +ms.assetid: 091876a8-22ee-4685-bb88-adb9de85175a +--- + + +# Best practices: Channel management + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +There are two common ways for organizations to apply updates to Office UNRESOLVED_TOKEN_VAL(365) ProPlus: +- Automatically from the Internet + + +- Automatically from an on-premises location, such as a network share, DFS, or by using a software distribution tool such as System Center Configuration Manager + + +When choosing how to manage updates, you should plan to use your existing software deployment and management tools and processes, such as a DFS system or System Center Configuration Manager. IT admins should also use the Office Deployment Tool configuration settings either via the install XML or Group Policy to configure and control the Office UNRESOLVED_TOKEN_VAL(365) ProPlus client update settings. Proper planning should be included for the unlikely cases that a user requests to switch their update channel cadence, as well as the event that a user or channel membership group needs their Office UNRESOLVED_TOKEN_VAL(365) ProPlus build reverted back to a previously known good version. +## Switching channels + +Switching Channels is not advised unless required because it is a100% file delta install. If the channel you are switching to is 1.2 GB, then a complete 1.2 GB of network bandwidth is consumed if installing locally (700-800 MB if using Office CDN). There is no need to uninstall and then re-install; however, the network impact is the same as a new install. + + + + +> [!NOTE] +> If the source files are hosted on premises, changing the Update Channel Group Policy object has no impact on the channel switch. The Update Channel Group Policy object can only be used if you are using the Office CDN for the source location. + + + + + +## Rollback + +There are two supported methods to perform a rollback or downgrade: + + + + +- Run the ODT setup.exe in configure mode with a new install XML using the "version: element. + + +- Call OfficeC2Rclient.exe update engine and perform a command line rollback using the "updatetoversion" element. + + +If a rollback is required, one of the following two solutions is recommended: + + + + +### Re-Run ODT Setup.exe with new Install XML + +To perform a rollback, re-run the ODT setup.exe in configure mode and push out a new install XML file that includes the build version specified in the install XML to rollback to. When using this method, the client must have access to the appropriate build source files; therefore, you should either have the client install the specified version from the Office CDN, or use the _UpdatePath_ element to point to a local source that contains the appropriate Office UNRESOLVED_TOKEN_VAL(365) ProPlus build source files. + + + +It is important to note that if the customer is patching from an on premises source location, the new install XML re-run with a specified version must contain an _UpdatePath_ that specifies the network location of that specified build. If the specified build version cannot be found, the rollback will fail. + + + + **Steps for re-running the ODT Setup.exe with new Install XML to rollback** + + + + +1. Identify the version of Office365 ProPlus (version numbers can be found at [Version and build numbers of update channel releases for Office 365 clients](https://technet.microsoft.com/en-us/library/mt592918.aspx)). + + +2. Copy ODT setup.exe and the new install XML file to the appropriate source distribution location to be deployed to the client machines. + + +3. From an elevated command prompt with administrator privileges, run **setup.exe /configure .xml**. + + > [!NOTE] + > If users are not local administrators on the machine, a software distribution tool or script that runs with elevated privileges must be used +4. After the above the command has completed, verify the version of Office 365 ProPlus is at the desired version. + + Open an Office 365 ProPlus Application >> **File >> Office Account >> Verify Office 365 ProPlus version Utilize OfficeC2RClient.exe** + + + +### Use OfficeC2RClient.exe + +By specifying a previous Office 365 ProPlus build version in the command line, the OfficeC2RClient.exe will roll back the Office UNRESOLVED_TOKEN_VAL(365) ProPlus client to that specified build. The OfficeC2RClient.exe takes into account the _UpdatePath_ location that is set either by the ODT or Group Policy, and will look to that location for the source files for the specified build version in the command line. The OfficeC2RClient.exe feature can be automated by using a batch file and script, or by leveraging an empty System Center Configuration Manager package to call the OfficeC2RClient.exe with the appropriate elements and specified variables. + + + +To use the OfficeC2RClient.exe, see [How to revert to an earlier version of Office 2013 or Office 2016 Click-to-Run](https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-click-to-run). + + + +The following table represents additional command line switches that you can include: + + + + +|||| +|:-----|:-----|:-----| +|**Variable**
|**Values**
|**Description**
| +|UpdatePromptUser
|True, False (Default: False)
|Specifies whether a user will see the "Office updates are available" dialog box before applying updates.
| +|ForceAppShutdown
|True, False (Default: False)
|Specifies whether a user is given the option to postpone the update. If set to "True", Office applications will shut down immediately when the update process begins.
| +|DisplayLevel
|True, False (Default: True)
|Specifies whether or not a user will see a user interface during the updates. If set to "False," all update user interface will be hidden, including any errors that are encountered during the update.
| +|UpdateToVersion
|16.0.XXXX.XXXX (Default: Install latest released build)
|Specifies the version of Office 365 ProPlus to update to, which can be used to install a newer or older version than the current Office 365 ProPlus build that is installed.
| + + **Steps for using OfficeC2RClient.exe to rollback** + + + + +1. Identify the version of Office365 ProPlus (version numbers can be found at [Version and build numbers of update channel releases for Office 365 clients](https://technet.microsoft.com/en-us/library/mt592918.aspx)). + + +2. From an elevated command prompt with administrator privileges, run the following command: + + ``` + +"%Program Files%\\Common Files\\Microsoft Shared\\ClicktoRun\\OfficeC2RClient.exe" /update user updatepromptuser=false forceappshutdown=true displaylevel=true updatetoversion=16.0.xxxx.xxxx + ``` + + + > [!NOTE] + > Be sure to note that **forceappshutdown=true** in the command line because updates cannot occur unless all off the applications are shut down. The **updatetoversion** is the specified version that the client will be rolling back to. Additionally, ensure that the specified **updatetoversion** correlates to the current channel membership that the client is on.> If users are not local administrators on the machine, a software distribution tool or script that runs with elevated privileges must be used. +3. After the above the command has completed, verify that the version of Office365 ProPlus is at the desired version. + + Open an Office 365 ProPlus Application >> **File >> Office Account >> Verify Office 365 ProPlus version Utilize OfficeC2RClient.exe** + + + +## Channel management references + +The following links provide detailed information about channel management: + + + + +- [Configure update settings for Office 365 ProPlus](https://technet.microsoft.com/en-us/library/dn761708.aspx) + + +- [Manage updates to Office 365 ProPlus with System Center Configuration Manager](https://technet.microsoft.com/en-us/library/mt628083.aspx) + + +- [Change management for Office 365 clients](https://technet.microsoft.com/en-us/library/mt584223.aspx) + + +- [How to revert to an earlier version of Office 2013 or Office 2016 Click-to-Run](https://support.microsoft.com/en-us/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-click-to-run) + + + diff --git a/DeployOffice/best-practices-cloud-managed-scenario.md b/DeployOffice/best-practices-cloud-managed-scenario.md new file mode 100644 index 000000000..5c9dc01b6 --- /dev/null +++ b/DeployOffice/best-practices-cloud-managed-scenario.md @@ -0,0 +1,42 @@ +--- +title: Best practices Cloud managed scenario +ms.prod: OFFICE365 +ms.assetid: d239ef5d-34d7-486f-a8e4-26eeec4e0a80 +--- + + +# Best practices: Cloud managed scenario + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Cloud Managed represents generally small businesses who are generally located out of a small centralized office in a single country; however, they might have smaller remote offices throughout the country. The work force leverages the newest productivity devices and software on the market, because having a smaller organization allows for more rapid adoption of new technology. They have a small IT team that manages the entire organizational IT environment technologies such as Active Directory Domain Services (AD DS), Azure Active Directory Password Sync, GPO, etc. The IT team does not use software distribution tools to manage client software, and no Distributed File System (DFS) exists. Network shares are leveraged for installing software, and users have administrative privileges on their client devices. The IT team provides batch files or scripts for end users to automate deployments. +## + + ** [Best practices: Assessment for cloud managed](best-practices-assessment-for-cloud-managed.md)** Assessment results and success criteria for deploying Office 365 ProPlus. + + + + ** [Best practices: Planning for cloud managed](best-practices-planning-for-cloud-managed.md)** Creating a deployment plan is key when you migrate to Office 365 ProPlus. + + + + ** [Best practices: Deployment for cloud managed](best-practices-deployment-for-cloud-managed.md)** Common management tasks after deploying Office 365 ProPlus. + + + + ** [Best practices: Management for cloud managed](best-practices-management-for-cloud-managed.md)** Common management tasks after deploying Office 365 ProPlus. + + + + + + + + + + + + diff --git a/DeployOffice/best-practices-common-debugging-steps.md b/DeployOffice/best-practices-common-debugging-steps.md new file mode 100644 index 000000000..ae46f78dc --- /dev/null +++ b/DeployOffice/best-practices-common-debugging-steps.md @@ -0,0 +1,42 @@ +--- +title: Best practices Common debugging steps +ms.prod: OFFICE365 +ms.assetid: b584fcff-d64d-426a-b20f-fc93707cf46c +--- + + +# Best practices: Common debugging steps + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +The following steps are common issues that can occur when you deploy and manage Office UNRESOLVED_TOKEN_VAL(365) ProPlus: +1. Use a network scanning utility such as Process Monitor, Wireshark, or Fiddler to see if throughput or connections are being blocked: + + - OfficeC2RClient.exe + + + - OLicenseHeartbeat.exe + + +2. Does the system account running the processes have proxy access? + + +3. Are the appropriate network and firewall rules open for Office 365 traffic? + + +4. Make sure that you are using the latest version of the [Office Deployment Tool](https://www.microsoft.com/en-us/download/details.aspx?id=49117) (updated regularly). + + +5. Make sure that your XML syntax is correct by using the [GitHub XML script editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + +6. Check for new GPOs in the [Office 2016 Administrative Template files](https://www.microsoft.com/en-us/download/details.aspx?id=49030) (updated regularly). + + +7. Does the account that is being used to install Office UNRESOLVED_TOKEN_VAL(365) ProPlus have administrative privileges? + + + diff --git a/DeployOffice/best-practices-deployment-for-cloud-managed.md b/DeployOffice/best-practices-deployment-for-cloud-managed.md new file mode 100644 index 000000000..36ec95f83 --- /dev/null +++ b/DeployOffice/best-practices-deployment-for-cloud-managed.md @@ -0,0 +1,150 @@ +--- +title: Best practices Deployment for cloud managed +ms.prod: OFFICE365 +ms.assetid: 3c108fee-b271-4cb0-8b16-a134faf9f70c +--- + + +# Best practices: Deployment for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Now that *Cloud Managed* has been through Assessment and Planning, it is time to deploy the software. +## Configure the deployment files for redistribution + +Download the latest version of the [Office Deployment Tool (ODT)](https://www.microsoft.com/en-us/download/details.aspx?id=49117) and create and configure the install XML files to download and install the Office 365 ProPlus source files. *Cloud Managed* created multiple XML files to configure and install Office 365 ProPlus. + + + + [GitHub](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl) was leveraged to edit the XML files. + + + +The following XML files must be created: + + + + +||| +|:-----|:-----| +|**XML file**
|**Languages**
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit
|English
| +|Office 365 ProPlus - Deferred Channel - Desktops - VDI - 32-bit
|English
| +|Office 365 ProPlus - First Release Deferred Channel - Desktops - 32-bit
|English
| + +For examples, see [Best practices: Download XML files for cloud managed](best-practices-download-xml-files-for-cloud-managed.md). + + + + +## Configure the Office Scrub tool to remove all previous versions of Office + +Because *Cloud Managed* has multiple versions of Office, two versions of the Office Scrub tool must be obtained from Premier support. The first version removes Office 2007 and 2010 MSI versions, while the second version removes Office 2013 MSI, 2013 C2R, and 2016 MSI or C2R. + + + +The application will be run via a script. Because there are multiple versions of the tool, each command must be performed separately. + + + +The following sequence will be run: + + + + +- Office 2010 Removal + + +- Office 2013 MSI Core Suite Removal (leave Project and Visio 2013 on machine) + + +User data will be persisted and Project and Visio will be left intact. A quick repair on Project and Visio will likely be required. + + + +For examples, see [Best practices: Install XML files for cloud managed](best-practices-install-xml-files-for-cloud-managed.md). + + + + +## Create the batch install wrapper to automate the OffScrub and Office 365 ProPlus install or removal + + *Cloud Managed* can use a batch file that is stored in a UNC path to initiate the Office 365 ProPlus installation from the Office CDN, or to uninstall an existing Office 365 ProPlus installation. + + + +A sample Office 365 ProPlus batch file task order is: + + + + +- Run Office Scrub + + - Remove all Office 2010 (MSI) components + + + - Remove Office 2013 (MSI) Core suite applications (leave any 2013 Project and Visio MSI instances intact) + + + - Leave user data in place + + +- Install Office 365 ProPlus with proper channel, architecture, and languages + + +The following batch files or scripts should be created: + + + + +- OffScrub + Office 365 ProPlus Deferred Channel install + + +- OffScrub + Office 365 ProPlus First Release for Deferred Channel Office 365 ProPlus install + + +- Office 365 ProPlus uninstall + + +Add the following line to a to a batch file ( **Office365_DC_Configuration.cmd** ). This batch line will dynamically determine the script directory and find setup.exe and install XML. Note that this does not check whether the script is performed with elevated rights, but Cloud Managed users are local administrators on their client devices. + + + + + + +``` + +"%~dp0Setup.exe" /configure "%~dp0install.xml" +``` + +An additional batch file ( **Office365_Removal.cmd** ) to uninstall can be created with the following batch line: + + + + + + +``` +"%~dp0Setup.exe" /configure "%~dp0removal.xml" +``` + +For detailed guidance, see [Best practices: Office Content Delivery Network configuration for cloud managed](best-practices-office-content-delivery-network-configuration-for-cloud-managed.md). + + + + +## Configure Office 2016 for Mac for distribution + + *Cloud Managed* has a limited Mac environment and will utilize the Office 365 portal for deployments. Users should be provided instructions on how to install Office 2016 for Mac from the Office 365 portal. Users will need to provide their machine administrator credentials in order to install Office 2016 for Mac. + + + +For detailed guidance, see [Best practices: Office 2016 Mac client install for cloud managed](best-practices-office-2016-mac-client-install-for-cloud-managed.md). + + + + diff --git a/DeployOffice/best-practices-deployment-for-enterprise-managed.md b/DeployOffice/best-practices-deployment-for-enterprise-managed.md new file mode 100644 index 000000000..ae1a8a2d3 --- /dev/null +++ b/DeployOffice/best-practices-deployment-for-enterprise-managed.md @@ -0,0 +1,127 @@ +--- +title: Best practices Deployment for enterprise managed +ms.prod: OFFICE365 +ms.assetid: 2f560823-aa43-4003-8f79-2750d3944060 +--- + + +# Best practices: Deployment for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Now that *Enterprise Managed* has gone through Assessment and Planning, it is time to deploy the software. +## Download the Office 365 ProPlus files for redistribution + + *Enterprise Managed* will download the latest version of the [Office Deployment Tool (ODT)](https://www.microsoft.com/en-us/download/details.aspx?id=49117) and use the ODT setup.exe in download mode, in combination with the download XML files, to download the latest Office 365 client source files. The downloaded source files must be for 32-bit Deferred and First Release for Deferred Channel builds, Project Pro, Visio Pro, 64-bit Deferred Channel builds, and all supported languages for the Office 365 clients. + + + +The specific downloads are listed in the following table: + + + + +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - Deferred Channel - 32-bit
|English, French, Spanish, Portuguese, Chinese (Simplified), Chinese, Indonesian, Japanese, Korean, Malay, Thai, Czech, Danish , Dutch, Finnish, German, Greek
| +|Visio Pro Volume Licensed (VL) - Deferred Channel - 32-bit
|English
| +|Project Pro Volume Licensed (VL) - Deferred Channel - 32-bit
|English
| +|Office 365 ProPlus - Deferred Channel - 64-bit
|English
| +|Office 365 ProPlus, Project Pro (VL), and Visio Pro (VL) - First Release for Deferred Channel - 32-bit
|English
| + +For examples, see [Best practices: Download XML files for enterprise managed](best-practices-download-xml-files-for-enterprise-managed.md). + + + + +## Configure the deployment files + + *Enterprise Managed* will edit the XML files for the deployment. *Enterprise Managed* made several install XML files, that together with the Office 365 client source files that were previously downloaded, configure and install Office 365 ProPlus. + + + + +> [!NOTE] +> Use [GitHub](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl) to edit the XML files. + + + + +The following XML files must be created: + + + + +|||| +|:-----|:-----|:-----| +|**XML file**
|**Languages**
|**Exclusions/additions**
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - North America Region
|English, French, Spanish
|Exclude OneDrive for Business
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - LATAM Region
|Spanish, Portuguese, English
|Exclude OneDrive for Business
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - AsiaPAC Region
|Chinese (Simplified), Chinese, Indonesian, Japanese, Korean, Malay, Thai, English
|Exclude OneDrive for Business
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - EU Region
|Czech, Danish, Dutch, Finnish, German, Greek, English, French
|Exclude OneDrive for Business
| +|Project Pro Volume Licensed (VL) - Deferred Channel - Desktops - 32-bit
|English
|| +|Visio Pro Volume Licensed (VL) - Deferred Channel - Desktops - 32-bit
|English
|| +|Individual languages - Deferred Channel - Desktops 32-bit
|English, French, Spanish, Portuguese, Chinese (Simplified), Chinese, Indonesian, Japanese, Korean, Malay, Thai, Czech, Danish, Dutch, Finnish, German, Greek
|| +|Office 365 ProPlus - Deferred Channel - VDI - 32-bit - All regions
|English, French, Spanish, Portuguese, Chinese (Simplified), Chinese, Indonesian, Japanese, Korean, Malay, Thai, Czech, Danish, Dutch, Finnish, German, Greek
|Shared computer activation
Exclude OneDrive for Business
| +|Office 365 ProPlus - Deferred Channel - Desktops - 64-bit
|English
|Exclude OneDrive for Business
| +|Office 365 ProPlus - First Release for Deferred Channel - Desktops - 32-bit
|English
|Exclude OneDrive for Business
| +|Project Pro (VL)- First Release for Deferred Channel - Desktops - 32-bit
|English
|| +|Visio Pro (VL) - First Release for Deferred Channel - Desktops - 32-bit
|English
|| + +For examples, see [Best practices: Install XML files for enterprise managed](best-practices-install-xml-files-for-enterprise-managed.md). + + + + +## Configure OffScrub to remove all previous versions of Office + + *Enterprise Managed* must obtain two different versions of the Office Scrub tool from Premier support. The first version removes Office 2007 and 2010 MSI versions, and the second version removes Office 2013 MSI, 2013 C2R, 2016 MSI and 2016 C2R. OffScrub will be run several times via task sequence; because there are multiple versions of the tool, each command must be performed separately. + + + +The following sequence will be run: + + + + +- Office 2007 Removal + + +- Office 2010 Removal + + +User data will persist. All instances of Project and Visio will be removed with the accompanying version of the Office suite. + + + +For examples, see [Best practices: Uninstall XML files for enterprise managed](best-practices-uninstall-xml-files-for-enterprise-managed.md). + + + + +## Integrate the individual packages into System Center Configuration Manager for distribution + +System Center Configuration Manager can deploy to machines with elevated privilege and logging. Although the Office 365 ProPlus package does not use normal KB patch updates, *Enterprise Managed* will use System Center Configuration Manager for continual maintenance of Office 365 ProPlus because their System Center Configuration Manager version allows for integration of Office Builds into the management tool (System Center Configuration Manager 1602 or greater). + + + +For detailed guidance, see [Best practices: System Center Configuration Manager configuration for enterprise managed](best-practices-system-center-configuration-manager-configuration-for-enterprise.md). + + + + +## Configure Office 2016 for Mac for distribution + + *Enterprise Managed* has existing enterprise Mac software distribution that is different than System Center Configuration Manager. Additionally, the Office Deployment Tool is only for the Windows versions of Office 365 ProPlus. Therefore, the deployment process is slightly different for Mac clients. *Enterprise Managed* will use their existing Mac software distribution tool to manage their Mac deployments. + + + +For detailed guidance, see [Best practices: Office 2016 Mac client install for enterprise managed](best-practices-office-2016-mac-client-install-for-enterprise-managed.md). + + + + diff --git a/DeployOffice/best-practices-deployment-for-locally-managed.md b/DeployOffice/best-practices-deployment-for-locally-managed.md new file mode 100644 index 000000000..a3c071683 --- /dev/null +++ b/DeployOffice/best-practices-deployment-for-locally-managed.md @@ -0,0 +1,246 @@ +--- +title: Best practices Deployment for locally managed +ms.prod: OFFICE365 +ms.assetid: a2cf0c03-0c1d-4753-ac05-00aab2644f9d +--- + + +# Best practices: Deployment for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Now that *Locally Managed* has been through Assessment and Planning, it is time to deploy the software. +## Create a folder structure in Distributed File System + +Use the existing Distributed File System (DFS) and scripts to let users install from a network share without requiring administrative privileges on the local machines. *Locally Managed* should have a similar folder structure within the DFS to host Office 365 client related content, and users must have read permissions to the share. + + + + +||| +|:-----|:-----| +|**Folder path**
|**Purpose**
| +|\\\\Server\\Share\\O365
|This is the parent folder that will be used for storing all Office 365 ProPlus related items.
| +|\\\\Server\\Share\\O365\\FRDC
|Use this folder to store the most current Office 365 ProPlus First Release for Deferred Channel build that pre-production users will receive.
| +|\\\\Server\\Share\\O365\\DC
|Use this folder to store the most current Office 365 ProPlus Deferred Channel build that production users will receive. Production channel should be Deferred Channel.
| +|\\\\Server\\Share\\O365\\Archive
|Use this folder to host N-1 previously known good builds in case a rollback or downgrade is needed.
| +|\\\\Server\\Share\\O365\\OffScrub
|Use this folder to host the OffScrub scripts to remove previous versions of Office.
| + +The following image is an example of the folder structure that *Locally Managed* should create: + + + + + + + +![Locally managed folder structure for Office 365](images/0532b11b-c2ea-4e73-8fe5-52526cefac35.png) + + + + + + + + + + + + +## Download the Office 365 ProPlus files for redistribution + +Download the latest version of the [Office Deployment Tool (ODT)](https://www.microsoft.com/en-us/download/details.aspx?id=49117) and put it in the **\\\\Server\\Share\\O365** network location. Then, create and configure the download XML file to download the Office 365 ProPlus source files. Run ODT setup.exe in download mode and the download XML to retrieve the latest Office 365 ProPlus source files. The downloaded source files must be for 32-bit Deferred and First Release for Deferred Channel builds, Project Pro, Visio Pro, and all supported languages for the Office 365 clients. + + + +The specific download packages are as follows: + + + + +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - Deferred Channel - 32-bit
|English, French, German
| +|Visio Pro - Deferred Channel - 32-bit
|English
| +|Project Pro - Deferred Channel - 32-bit
|English
| +|Office 365 ProPlus, Project Pro, and Visio Pro - First Release for Deferred Channel - 32-bit
|English
| + +The Deferred Channel download XML should be placed in the corresponding ** \\\\Server\\Share\\O365\\DC** network location The First Release for Deferred Channel download XML should be placed in the corresponding **\\\\Server\\Share\\O365\\FRDC** network location. Both the Deferred Channel and First Release for Deferred Channel download XMLs should download the source bits into their corresponding channel folders in DFS. + + + +For examples, see [Best practices: Download XML files for locally managed](best-practices-download-xml-files-for-locally-managed.md). + + + + +## Configure the deployment files + +The next step is to edit the install XML files for the deployment. *Locally Managed* created multiple XML files, that together with the downloaded Office 365 ProPlus files, will configure and install Office 365 ProPlus. + + + + [GitHub](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl) was leveraged to edit the XML files. + + + +The following XML files must be created: + + + + +|||| +|:-----|:-----|:-----| +|**XML file**
|**Languages**
|**Exclusions/additions**
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - CanAm Region
|English, French
|Exclude Access
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - Germany
|German
|Exclude Access
| +|Office 365 ProPlus - Deferred Channel - VDI - 32-bit - All regions
|English, French, German
|Shared Activation
Exclude Access
| +|Project Pro - Deferred Channel - Desktops - 32-bit
|English
|| +|Visio Pro - Deferred Channel - Desktops - 32-bit
|English
|| +|Individual languages - Deferred Channel - Desktops 32-bit
|English, French, German
|| +|Office 365 ProPlus, Project Pro, and Visio Pro - First Release Deferred Channel - Desktops - 32-bit
|English
|Exclude Access
| + +The Deferred Channel install XML should be placed in the corresponding \\ **\\Server\\Share\\O365\\DC** network location . The First Release for Deferred Channel install XML should be placed in the corresponding **\\\\Server\\Share\\O365\\FRDC** network location. + + + +For examples, see [Best practices: Install XML files for locally managed](best-practices-install-xml-files-for-locally-managed.md). + + + + +## Configure the Office Scrub tool to remove all previous versions of Office + + *Locally Managed* has only one preexisting version of Office in the environment, Office 2010 (MSI), so only the version of the OffScrub tool that removes Office 2007 and 2010 MSI versions must be obtained from Premier support. The OffScrub script should be stored in the **\\\\Server\\Share\\O365\\OffScrub** network location. The application will be run via a batch file or script. It is automated and the user will not need elevated privilege. + + + +The following sequence will be run: + + + + +- Office 2010 (MSI) Full Suite Removal + + +User data will be persisted and all instances of Project and Visio will be removed with the accompanying version of the Office suite. + + + +For examples, see [Best practices: Uninstall XML files for locally managed](best-practices-uninstall-xml-files-for-locally-managed.md). + + + + +## Create the batch install wrapper to automate the OffScrub and Office 365 ProPlus install or removal + + *Locally Managed* should use batch files or scripts stored in the previously created folder structure. The script or batch file will run with elevated privileges, so users only need read permissions to the share that hosts the batch file or script, OffScrub script, ODT setup.exe, install XML files, and Office 365 source files. + + + +A sample Office 365 ProPlus batch file task order is as follows: + + + + +- Run OffScrub + + - Remove all Office 2010 (MSI) components + + + - Remove Office 2013 Core Suite components (leave Project and Visio 2013) + + + - Leave user data in place + + +- Install InfoPath 2013 (MSI) + + +- Install Office 365 ProPlus with proper channel, architecture, and languages + + +The Project and Visio batch file task orders should be as follows: + + + + +- Install Project or Visio with proper channel, architecture, and languages + + +The following batch files or scripts should be created: + + + + +- OffScrub + Office 365 ProPlus Deferred Channel install + + +- Project Pro Deferred Channel install + + +- Visio Pro Deferred Channel install + + +- OffScrub + Office 365 ProPlus First Release for Deferred Channel install + + +- Project Pro First Release for Deferred Channel install + + +- Visio Pro First Release for Deferred Channel install + + +- Office 365 ProPlus uninstall + + +- Individual language installations + + + *Locally Managed* must advertise separate batch files for Deferred Channel and First Release for Deferred Channel users. Users should only be able to perform the script that automates the Office 365 ProPlus configuration that is designed for them: no pre-production or FRDC users should see the DC or production script. Therefore, the DC automation scripts should be stored in its respective folder location ( **\\\\Server\\Share\\O365\\DC** ), and the FRDC automation scripts should be stored in its respective folder location ( **\\\\Server\\Share\\O365\\FRDC** ). *Locally Managed* users should be instructed to go to the designated folder and run the appropriate Office script based on their end user role (production or pre-production), or Group Policy should copy the appropriate batch file to the user's desktop to run. + + + +Add the following line to a to a batch file (for example, **Office365_DC_Configuration.cmd** ). This line will dynamically determine the script directory and find setup.exe and install XML. Note that this command does not check whether the script is performed with elevated rights, so *Locally Managed* must make sure that elevated rights are applied. A similar batch line can be leverage for OffScrub. + + + + + + +``` + +"%~dp0Setup.exe" /configure "%~dp0install.xml" +``` + +You can create an additional batch file (for example, **Office365_Removal.cmd** ) to uninstall and leverage the following batch line: + + + + + + +``` +"%~dp0Setup.exe" /configure "%~dp0removal.xml" +``` + +For detailed guidance, see [Best practices: Distributed File System configuration for locally managed](best-practices-distributed-file-system-configuration-for-locally-managed.md). + + + + +## Configure Office 2016 for Mac for distribution + + *Locally Managed* has a small Mac environment and does not have Mac software distribution tools, but still wants to have control over their Mac clients. Therefore, it is recommended that they use a network share deployment. + + + +For detailed guidance, see [Best practices: Office 2016 Mac client install for locally managed](best-practices-office-2016-mac-client-install-for-locally-managed.md). + + + + diff --git a/DeployOffice/best-practices-deployment-resources.md b/DeployOffice/best-practices-deployment-resources.md new file mode 100644 index 000000000..1e18ef62c --- /dev/null +++ b/DeployOffice/best-practices-deployment-resources.md @@ -0,0 +1,15 @@ +--- +title: Best practices Deployment resources +ms.prod: OFFICE365 +ms.assetid: a6ada180-3f19-43b3-9291-5ec3cef88b2f +--- + + +# Best practices: Deployment resources + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Key deployment resources for the implementing the best practice recommendations. ** [Best practices: Sample configuration files for downloading Office 365 ProPlus](best-practices-sample-configuration-files-for-downloading-office-365-proplus.md)** Common examples of the configuration file used by the Office 2016 Deployment Tool to download Office 365 ProPlus. ** [Best practices: Sample configuration files for installing Office 365 ProPlus](best-practices-sample-configuration-files-for-installing-office-365-proplus.md)** Common examples of the configuration file used by the Office 2016 Deployment Tool to install Office 365 ProPlus. ** [Best practices for installing Office 365 ProPlus from CDN or DFS](best-practices-for-installing-office-365-proplus-from-cdn-or-dfs.md)** Details the different architecture components. For step-by-step instructions, see [Best practices: Step by step installation using CDN](best-practices-step-by-step-installation-using-cdn.md) and [Best practices: Step by step installation using DFS](best-practices-step-by-step-installation-using-dfs.md). ** [Best practices for implementing group policy](best-practices-for-implementing-group-policy.md)** Links to the administrative templates for Office 2016. ** [Best practices for using OffScrub](best-practices-for-using-offscrub.md)** The Office Scrub tool (OffScrub) is the best way to remove a previous version of Office. ** [Best practices for Office Telemetry](best-practices-for-office-telemetry.md)** Office Telemetry is the new compatibility monitoring framework that replaces the previous Office 2010 compatibility tools/ ** [Best practices for deploying Office 2016 to Mac clients](best-practices-for-deploying-office-2016-to-mac-clients.md)** The system requirements and deployment information for Office 2016 for Mac. ** [Best practices: Common debugging steps](best-practices-common-debugging-steps.md)** Fixes for common issues that can occur when deploying and managing Office 365 ProPlus. diff --git a/DeployOffice/best-practices-deployment-scenarios.md b/DeployOffice/best-practices-deployment-scenarios.md new file mode 100644 index 000000000..87a451b75 --- /dev/null +++ b/DeployOffice/best-practices-deployment-scenarios.md @@ -0,0 +1,85 @@ +--- +title: Best Practices Deployment scenarios +ms.prod: OFFICE365 +ms.assetid: 4d9d796b-4291-4e0c-bd75-751b434eeb01 +--- + + +# Best Practices: Deployment scenarios + [![Help for Office 365 IT Pros](images/0d973495-46cc-42dc-a26e-87933e8b0a6b.png) + + + +](http://technet.microsoft.com/library/6e18d402-f35e-415a-83b1-56620d4074ff%28Office.14%29.aspx) *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* +## The Enterprise Managed scenario + + +The Enterprise Managed scenario represents large to very large organizations, with tens of thousands of employees who are distributed globally. Enterprise Managed scenarios use software management tools such as System Center Configuration Manager to manage end user client devices and software. Users are not local administrators on their machines. The IT department in the Enterprise Managed scenario typically controls and automates the technologies. + + + + + + + +![Enterprise Managed deployment](images/180d081a-aad7-40f9-bb18-ff65ff166530.png) + + + + + + + + + + + + +## The Locally Managed scenario + + +The Locally Managed scenario represents medium to large organizations that range up to ten thousand employees. There may be multiple sites in different countries or continents, but locally managed is not considered to be distributed globally. Locally Managed does not have software distribution tools to manage client software, but instead uses a Distributed File System and network shares to host deployment packages for end users. Locally Managed leverages batch files or scripts that run with elevated privileges so the deployment is automated for end users, who are generally not local administrators on their machines. + + + + + + + +![Locally Managed deployment](images/067af377-022d-4a4b-aa04-993669398ebc.png) + + + + + + + + + + + + +## The Cloud Managed scenario + + +The Cloud Managed scenario represents small businesses that typically range in the hundreds of employees, and are generally located out of one country or a single office. Cloud Managed does not have software distribution tools to manage client software, but instead uses network shares to host deployment packages for end users. Cloud Managed uses batch files or scripts so the deployment is automated for end users, but because users have local administrator rights, some software installation is left up to the end user. + + + + + + + +![Cloud Managed deployment](images/f1468c2b-b347-4f55-b6b7-0fa9e23a7e97.png) + + + + + + + + + + + + diff --git a/DeployOffice/best-practices-distributed-file-system-configuration-for-locally-managed.md b/DeployOffice/best-practices-distributed-file-system-configuration-for-locally-managed.md new file mode 100644 index 000000000..6fe5e99c4 --- /dev/null +++ b/DeployOffice/best-practices-distributed-file-system-configuration-for-locally-managed.md @@ -0,0 +1,92 @@ +--- +title: Best practices Distributed File System configuration for locally managed +ms.prod: OFFICE365 +ms.assetid: 2124a0dc-3f85-478c-a3da-c0b332b82095 +--- + + +# Best practices: Distributed File System configuration for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Locally Managed* will use their Distributed File System (DFS) and batch files or scripts to deploy the Office 365 ProPlus packages. The scripts are set to install silently because multiple steps are being performed. +The Office 365 ProPlus configuration script does the following: + + + + + +- Run OffScrub + + - Remove all Office 2010 MSI components if found + + + - Leave user data in place + + +- Install InfoPath 2013 MSI + + +- Install Office 365 ProPlus with proper channel, architecture, and languages from DFS + + + +## OffScrub + +The following table includes the OffScrub Command lines that *Locally Managed* uses for the batch file or script sequence to remove the previous version of Office 2010 (MSI): + + + + +||| +|:-----|:-----| +|**Context for program**
|**Command line**
| +|Office 2010 Removal
|Command prompt cscript Offscrub2010.vbs clientall /bypass 1 /log c:\\temp /nocancel /q
| + + +## Batch file + + *Locally Managed* will use batch files or scripts to complete the Office 365 client configurations. The batch files must run with elevated privileges because their users are not local admins on their machines. *Locally Managed* must do one of the following: + + + + +- Create a batch file shortcut that runs with elevated privileges, and paste the shortcuts into the appropriate **\\\\Server\\Share\\O365\\DC** and **\\\\Server\\Share\\O365\\FRDC** folders. + + +- In the batch file or script, include a parameter that will launch command prompt with elevated privileges when it is run by an end user without local administrator rights on the machine. + + + *Locally Managed* can then either instruct users to the correct batch file or script to run in the DFS network location, or use Group Policy to manually deploy the batch file to the user's desktop. + + + +The following image shows an example of the Office Source location for *Locally Managed* 32-bit Deferred Channel. It includes the ODT setup.exe, Office 365 client download and configuration XML files, individual language pack installation XML files, Office 365 client source files, and batch files to install or uninstall the Office 365 client software and language packs. A similar example should also exist in the FRDC folder. + + + + + + + +![Deferred Channel source files](images/4b0df8e6-dda2-4159-b7bf-7b7f24aa8285.png) + + + +The following table shows example batch files or scripts: + + + + +|||| +|:-----|:-----|:-----| +|**Context**
|**Batch file**
|**Performs**
| +|Office 365 ProPlus DC Desktop 32-bit
|Office365ProPlus_DC_CanAm_Configuration
|Uninstalls Office 2010 using OffScrub tool and installs Office 365 ProPlus 32-bit Deferred Channel with CanAm 2 languages
| +|Office 365 ProPlus DC VDI 32-bit
|Office365ProPlus_VDI_DC_Configuration
|Uninstalls Office 2010 using OffScrub tool, installs Office 365 ProPlus 32-bit Deferred Channel with 3 languages, and enables Shared Computer Activation
| +|Visio Pro DC Desktop 32-bit
|Visio_DC_Configuration
|Installs Visio Pro 32-bit Deferred Channel with 1 language
| +|French Language Pack DC 32-bit
|Install_French_LP_DC
|Installs French language pack 32-bit DC to existing Office 365 clients
| + + diff --git a/DeployOffice/best-practices-download-xml-files-for-cloud-managed.md b/DeployOffice/best-practices-download-xml-files-for-cloud-managed.md new file mode 100644 index 000000000..3fc8dc34d --- /dev/null +++ b/DeployOffice/best-practices-download-xml-files-for-cloud-managed.md @@ -0,0 +1,91 @@ +--- +title: Best practices Download XML files for cloud managed +ms.prod: OFFICE365 +ms.assetid: 328bc4dc-79ab-4082-a897-25ebe4fc44a9 +--- + + +# Best practices: Download XML files for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Cloud Managed* deployments will rely on Office CDN as a content source and therefore will not create download XML files. However, in the case that they decide at a future date to host the content in an on premises source location, the following download XML files could be used. + *Cloud Managed* would need download XMLs for the following packages: + + + + + +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus Deferred Channel 32-Bit
|1 language
| +|Office 365 ProPlus First Release for Deferred Channel 32-bit
|1 language
| + + *Cloud Managed* expects Current Channel users to self-provision and self-manage. All applications will be included during the install. +## Example download XML files + +The following are the Cloud Managed example download XML files to download Office 365 client source files. + + + + +### Office 365 ProPlus - Deferred Channel - 32-bit + + +``` + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded
| +|Channel="Deferred"
|The channel build of Office 365 ProPlus being downloaded
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being downloaded
| +|Language ID="en-us"
|The language being downloaded for Office 365 ProPlus
| + + +### Office 365 ProPlus - First Release for Deferred Channel - 32-bit + + +``` + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded
| +|Channel="FirstReleaseDeferred"
|The channel build of Office 365 ProPlus being downloaded
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being downloaded
| +|Language ID="en-us"
|The language being downloaded for Office 365 ProPlus
| + + diff --git a/DeployOffice/best-practices-download-xml-files-for-enterprise-managed.md b/DeployOffice/best-practices-download-xml-files-for-enterprise-managed.md new file mode 100644 index 000000000..6a17f9a9a --- /dev/null +++ b/DeployOffice/best-practices-download-xml-files-for-enterprise-managed.md @@ -0,0 +1,152 @@ +--- +title: Best practices Download XML files for enterprise managed +ms.prod: OFFICE365 +ms.assetid: a7fcdebf-97e5-4551-84f8-f2cb993c16da +--- + + +# Best practices: Download XML files for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Enterprise Managed* needs download XMLs for the following packages: +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - Deferred Channel - 32-bit
|17 languages
| +|Project Pro (VL) - Deferred Channel - 32-bit
|1 language
| +|Visio Pro (VL) - Deferred Channel - 32-bit
|1 language
| +|Office 365 ProPlus - Deferred Channel - 64-bit
|1 language
| +|Office 365 ProPlus, Project Pro (VL), and Visio Pro (VL) - First Release for Deferred Channel - 32-bit
|1 language
| + + *Enterprise Managed* expects Current Channel users to self-provision and self-manage, and will be removing the OneDrive for Business application at time of deployment for all users. +## Example download XML files + +The following are the Enterprise Managed example download XML files for downloading Office 365 client source files. + + + + +### Office 365 ProPlus, Project Pro (VL), and Visio Pro (VL) - Deferred Channel - 32-bit + + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded
| +|Channel="Deferred"
|The channel build of Office 365 ProPlus being downloaded
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being downloaded
| +|Language ID="ii-cc"
|The languages being downloaded for Office 365 ProPlus
| +|Product ID="ProjectProXVolume"
|SKU of Project Pro being downloaded
| +|Language ID="en-us"
|The language being downloaded for Project Pro
| +|Product ID="VisioProXVolume"
|SKU of Visio Pro being downloaded
| +|Language ID="en-us"
|The language being downloaded for Visio Pro
| + + +### Office 365 ProPlus - Deferred Channel - 64-bit + + +``` + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="64"
|The architecture of Office being downloaded
| +|Channel="Deferred"
|The channel build of Office 365 ProPlus being downloaded
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being downloaded
| +|Language ID="en-us"
|The language being downloaded for Office 365 ProPlus
| + + +### Office 365 ProPlus, Project Pro (VL), and Visio Pro (VL) - First Release for Deferred Channel - 32-bit + + +``` + + + + + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded
| +|Channel="FirstReleaseDeferred"
|The channel build of Office 365 ProPlus being downloaded
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being downloaded
| +|Language ID="en-us"
|The language being downloaded for Office 365 ProPlus
| +|Product ID="ProjectProXVolume"
|SKU of Project Pro being downloaded
| +|Language ID="en-us"
|The language being downloaded for Project Pro
| +|Product ID="VisioProXVolume"
|SKU of Visio Pro being downloaded
| +|Language ID="en-us"
|The language being downloaded for Visio Pro
| + + diff --git a/DeployOffice/best-practices-download-xml-files-for-locally-managed.md b/DeployOffice/best-practices-download-xml-files-for-locally-managed.md new file mode 100644 index 000000000..dd0946f79 --- /dev/null +++ b/DeployOffice/best-practices-download-xml-files-for-locally-managed.md @@ -0,0 +1,109 @@ +--- +title: Best practices Download XML files for locally managed +ms.prod: OFFICE365 +ms.assetid: 5b5f4aab-7100-4e14-b3d6-218d0a267765 +--- + + +# Best practices: Download XML files for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Locally Managed* must download XML files for the following packages: +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - Deferred Channel - 32-Bit
|3 languages
| +|Project Pro - Deferred Channel - 32-bit
|1 language
| +|Visio Pro - Deferred Channel - 32-bit
|1 language
| +|Office 365 ProPlus, Project Pro, and Visio Pro - First Release for Deferred Channel - 32-bit
|1 language
| + + *Locally Managed* expects Current Channel users to self-provision and self-manage. +## Example download XML files + +The following are the *Locally Managed* example download XML files to download Office 365 client source files. + + + + +### Office 365 ProPlus, Project Pro, and Visio Pro - Deferred Channel - 32-bit + + +``` + + + + + + + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded
| +|Channel="Deferred"
|The channel build of Office 365 ProPlus being downloaded
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being downloaded
| +|Language ID="ii-cc"
|The languages being downloaded for Office 365 ProPlus
| +|Product ID="ProjectProRetail"
|SKU of Project Pro being downloaded
| +|Language ID="en-us"
|The language being downloaded for Project Pro
| +|Product ID="VisioProRetail"
|SKU of Visio Pro being downloaded
| +|Language ID="en-us"
|The language being downloaded for Visio Pro
| + + +### Office 365 ProPlus, Project Pro, and Visio Pro - First Release Deferred Channel - 32-bit + + +``` + + + + + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded
| +|Channel="FirstReleaseDeferred"
|The channel build of Office 365 ProPlus being downloaded
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being downloaded
| +|Language ID="en-us"
|The language being downloaded for Office 365 ProPlus
| +|Product ID="ProjectProRetail"
|SKU of Project Pro being downloaded
| +|Language ID="en-us"
|The language being downloaded for Project Pro
| +|Product ID="VisioProRetail"
|SKU of Visio Pro being downloaded
| +|Language ID="en-us"
|The language being downloaded for Visio Pro
| + + diff --git a/DeployOffice/best-practices-enterprise-managed-scenario.md b/DeployOffice/best-practices-enterprise-managed-scenario.md new file mode 100644 index 000000000..0e57eb289 --- /dev/null +++ b/DeployOffice/best-practices-enterprise-managed-scenario.md @@ -0,0 +1,42 @@ +--- +title: Best practices Enterprise managed scenario +ms.prod: OFFICE365 +ms.assetid: 36b7ec08-9f97-4d76-a600-b9e424005792 +--- + + +# Best practices: Enterprise managed scenario + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Enterprise Managed represents large to very large organizations, in which the work force is leveraging nearly every single technology that exists, ranging from desktops to notebooks to tablets, software distribution tools, and virtual environments like Remote Desktop Services and Virtual Desktop Infrastructure. The IT department manages the client software using software management tools such as System Center Configuration Manager, and has dedicated teams that administer the company's Active Directory components such as Active Directory Domain Services (AD DS), Active Directory Federation Services (AD FS), and Group Policy. +## + + ** [Best practices: Assessment for enterprise managed](best-practices-assessment-for-enterprise-managed.md)** Assessment results and success criteria for deploying Office 365 ProPlus. + + + + ** [Best practices: Planning for enterprise managed](best-practices-planning-for-enterprise-managed.md)** Creating a deployment plan is key when you migrate to Office 365 ProPlus. + + + + ** [Best practices: Deployment for enterprise managed](best-practices-deployment-for-enterprise-managed.md)** Guidance on how to deploy Office 365 ProPlus in the enterprise-managed scenario. + + + + ** [Best practices: Management for enterprise managed](best-practices-management-for-enterprise-managed.md)** Common management tasks after deploying Office 365 ProPlus. + + + + + + + + + + + + diff --git a/DeployOffice/best-practices-focus-areas-for-assessment.md b/DeployOffice/best-practices-focus-areas-for-assessment.md new file mode 100644 index 000000000..2ea008f05 --- /dev/null +++ b/DeployOffice/best-practices-focus-areas-for-assessment.md @@ -0,0 +1,199 @@ +--- +title: Best practices Focus areas for assessment +ms.prod: OFFICE365 +ms.assetid: 1eca17f1-64f4-48ad-93ab-51f48aff70f4 +--- + + +# Best practices: Focus areas for assessment + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +This article describes the assessment focus areas for your Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment. +## Size and distribution + + +- Number of devices targeted for the deployment. + + +- List of countries and regions to cover. + + +- List of languages supported by central IT department. + + +- Estimated number of the following: + + - Travelling users + + + - Travelling users + + + - Employees sharing a device (e.g. shift and factory floor workers) + + + +## IT infrastructure + + +- Operating Systems (OS) supported by central IT department, if multiple (for example, Windows 7 x86 and x64). + + +- Number of devices per OS type. + + +- Number and type of Bring Your Own Device (BYOD)s. + + +- Number of mobile and fixed devices. + + +- Do all devices have a common base language (e.g. en-us)? + + +- Do users have administrative rights on their machines? + + +- Number of the following: + + - Remote Desktops Service servers + + + - Remote Desktops Service farms + + + - Remote Desktops Service users + + + - Static VDI clients + + + - Dynamic VDI clients + + +- How is software currently distributed? System Center Configuration Manager (which version, how many sites)? + + +- How are clients and users managed? Active Directory Domain Service? + + +- Are all devices and users located in the same Directory Service or spread across several forests (e.g. one per region)? + + +- List of sites and number of targeted devices per site. + + +- If planning to leverage on premises Exchange servers + + - Is it at least Exchange 2010? + + + - Is Autodiscover enabled? + + +- If planning to leverage on premises Lync or Skype for Business Servers, is it at least Lync 2010? + + + +## Network infrastructure + + +- From a software deployment perspective, which sites: + + - Are well connected to the internal software distribution solution (e.g. System Center Configuration Manager)? + + + - Are moderately well connected to the internal software distribution solution> + + + - Are poorly connected to the internal software distribution solution? + + +- Which sites are well connected to the internet? + + +- Can the network handle the impact of the deployment and management scenarios selected? + + + +## Application landscape + + +- Which versions and editions of Office are currently deployed? + + +- Is there a mix in CPU architecture (Office 32-bit and 64-bit in production)? + + +- How many installations of Project exist? Which version(s) and editions? + + +- How many installations of Visio exist? Which version(s) and editions? + + +- Is InfoPath used in production? + + +- Is there a need to exclude applications from the deployment (for example, Access)? + + +- Should end users be able to add applications if they were excluded to the base install (for example, Access)? + + +- Is Office currently configured and managed by Group Policy settings? + + +- How many Group Policy objects exist to configure the client? Are there any subsets for specific user groups? + + +- What are the number of Office languages packs deployed per region? + + +- Which applications are out of scope (for example, Publisher or OneDrive)? + + +- Are there any known dependencies on legacy, end of life, or discontinued products (for example, Access 97)? + + +- Is there a known group of users which test new releases and updated first (e.g. Application Owners, QA group, Pilot group)? + + + +## Cloud infrastructure + + +- Is the Office 365 tenant configured and ready for production? + + +- Are the user licenses available in the tenant? Which SKU was purchased? + + +- Is identity already setup up? Which flavor (Cloud IDs, Synchronized IDs or Federated IDs)? + + +- If you are using Federated IDs, which identity provider is used (for example, Active Directory Federation Services)? + + +- Is the identity synchronization set up and working? + + +- Are all users accounts already synchronized to the tenant? + + +- Do the user accounts have the necessary Office 365 ProPlus license assigned? + + +- Is the self-service Office 365 ProPlus installation from the Office 365 portal blocked today? + + +- Are all URLs and IPs listed required for Office 365 whitelisted in the web proxies? + + +- Is the cloud infrastructure signed off by the security and compliance department? + + + diff --git a/DeployOffice/best-practices-for-assessing-your-infrastructure.md b/DeployOffice/best-practices-for-assessing-your-infrastructure.md new file mode 100644 index 000000000..8b9fe0ebd --- /dev/null +++ b/DeployOffice/best-practices-for-assessing-your-infrastructure.md @@ -0,0 +1,96 @@ +--- +title: Best practices for assessing your infrastructure +ms.prod: OFFICE365 +ms.assetid: f4899394-87f3-425c-9902-ddd65eaaac97 +--- + + +# Best practices for assessing your infrastructure + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Deploying Office UNRESOLVED_TOKEN_VAL(365) ProPlus requires the same level of planning as any large-scale Office client deployment. The focus of the Best Practices for Office UNRESOLVED_TOKEN_VAL(365) ProPlus focuses on key actives that are specific to deploying Office UNRESOLVED_TOKEN_VAL(365) ProPlus. +This topic covers key infrastructure assessment components and application compatibility discovery processes, as well as tools to aide with understanding the scope and remediation needs for Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + + + +For Office UNRESOLVED_TOKEN_VAL(365) ProPlus, there are two key areas that the assessment should focus on; these are understanding the infrastructure and environment, and application compatibility for legacy Office client products. It is important when preparing for the Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment that you understand the current state of the environment and the differences between Office UNRESOLVED_TOKEN_VAL(365) ProPlus and legacy MSI based clients. +## Environment assessment + +The assessment phase incorporates planning and requirements gathering. + + + +For Office UNRESOLVED_TOKEN_VAL(365) ProPlus specifically, the following list describes key areas for assessment: + + + + +- Understand the Office UNRESOLVED_TOKEN_VAL(365) components that are already being used in the environment, and determine any settings or configurations that are needed to enable and support Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + +- Understand the software distribution solutions that are currently being used. + + +- Assess network bandwidth capabilities to determine the best distribution method for first installation and update management. + + +- Understand the current versions of client software in the environment. + + +- Understand the Office applications that are required by the customer for each segment of users. + + + +## Application compatibility assessment + +The second area to focus on when planning an Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment is application compatibility. The common application compatibility issues when moving to a new version of Office are VBA, macros, third party add-ins, and complex documents. Many customers have a difficult time collecting the relevant data in their environment, as well as defining what components are business critical and which components are used by individuals. + + + +To simplify these activities, the following four-phase approach helps to identify the components that must be remediated prior to migrating to Office UNRESOLVED_TOKEN_VAL(365) ProPlus. The process involves leveraging the business users and the Telemetry Dashboard. + + + + +||| +|:-----|:-----| +|**Phase**
|**Description**
| +|Discover the components
|Discover what is being used, by whom, and how often. This helps determine what to test for compatibility with the new version of Office. Documents and solutions that are used frequently and by large numbers of users are good candidates for testing.
| +|Rationalize the business-critical components
|Partner with business groups to identify what's critical to the business. The discovery data can help jumpstart and guide this discussion. The goal is to identify the business-critical documents and solutions that must be ready on the first day of the Office deployment.
| +|Validate the solution
|Start a pilot deployment where users test required documents and solutions by using Office. This is called user acceptance testing. Troubleshoot any issues that occur for documents and solutions that must be ready on the first day of deployment.
| +|Manage the components for future validation of critical components
|Deploy Office and monitor documents and solutions. Watch for trends in Office performance and behavior as updated Office solutions are deployed. Use your Help Desk resources to troubleshoot issues as they occur for non-business-critical documents and solutions.
| + +For specific guidance on each phase of the application compatibility framework, see [Assess Office compatibility with other versions of Office](https://technet.microsoft.com/en-us/library/ee819096%28v=office.16%29.aspx). + + + +For specific guidance on the Telemetry Dashboard installation and usage, see [Best practices for Office Telemetry](best-practices-for-office-telemetry.md). + + + + +## Call to action + + +- Review the suggested questionnaire for the different focus areas. See [Best practices: Focus areas for assessment](best-practices-focus-areas-for-assessment.md). + + +- Identify the appropriate contact for each area and discuss the questions with them. + + +- Note down all responses and use them as the foundation for your planning. + + + +## Related Topics + + [Best practices for assessment - reference materials](best-practices-for-assessmentreference-materials.md) + + + + diff --git a/DeployOffice/best-practices-for-assessmentreference-materials.md b/DeployOffice/best-practices-for-assessmentreference-materials.md new file mode 100644 index 000000000..fb14ca9a5 --- /dev/null +++ b/DeployOffice/best-practices-for-assessmentreference-materials.md @@ -0,0 +1,87 @@ +--- +title: Best practices for assessment - reference materials +ms.prod: OFFICE365 +ms.assetid: f9bb5ed7-8d41-40fb-9804-fecfba7e5d6d +--- + + +# Best practices for assessment - reference materials + [![Help for Office 365 IT Pros](images/0d973495-46cc-42dc-a26e-87933e8b0a6b.png) + + + +](http://technet.microsoft.com/library/6e18d402-f35e-415a-83b1-56620d4074ff%28Office.14%29.aspx) *The Best Practices for Office 365 ProPlus Deployment has been created by a team of subject matter experts from the Office 365 Product Group, Office 365 Product Marketing Group, and delivery experts from Microsoft Services. The recommendations include application discovery, deployment, channel management, and reporting. For a list of all the best practices articles, see [Best practices: Recommended deployment scenarios](best-practices-recommended-deployment-scenarios.md).* +The following articles provide deeper technical information on specific areas of the assessment phase that are not covered in depth in the customer scenarios. + + + + + +## Frequently asked questions + + +### What is Office Click-to-Run? What are the differences between Office 365 ProPlus and previous versions of Office? + + [Overview of Click-to-Run](https://technet.microsoft.com/en-us/library/jj219427.aspx) + + + + [Changes in Office 2016 for Windows](https://technet.microsoft.com/en-us/library/mt715497%28v=office.16%29.aspx) + + + + +### Does it still use KMS/MAK to activate? Does it require Internet connection? + +Office UNRESOLVED_TOKEN_VAL(365)ProPlus uses the Office Licensing Service (OLS) to activate. It requires an Internet connection to the OLS at least once every 30 days. + + + + [Overview of licensing and activation in Office 365 ProPlus](https://technet.microsoft.com/en-us/library/gg982959.aspx) + + + + [Licensing and activation data sent to Office 365 by Office 365 ProPlus](https://technet.microsoft.com/en-us/library/dn308544.aspx) + + + + +### How does activation work for Office 2016 for Mac? + + [Overview of activation for Office 2016 for Mac](https://technet.microsoft.com/en-us/library/mt346043%28v=office.16%29.aspx) + + + + +### What are the Office 365 ProPlus and Office 2016 for Mac system requirements? + + [System requirements for Office](https://products.office.com/en-US/office-system-requirements) + + + + +### Can I still leverage my existing deployment tools and processes? + + [Determine the deployment method to use for Office 365 ProPlus](https://technet.microsoft.com/en-us/library/gg998766.aspx) + + + + [Deployment options for admins for Office 2016 for Mac](https://technet.microsoft.com/en-us/library/jj984157%28v=office.16%29.aspx) + + + + +### How can I assess if my current add-ins, macros, and complex documents will work in Office 365 ProPlus? + +Office Telemetry is a compatibility monitoring framework to help reduce the time and risks of an Office upgrade. See [Best practices for Office Telemetry](best-practices-for-office-telemetry.md). + + + + +### I'm currently running Office 365 ProPlus 2013. How does the upgrade process work to upgrade to the Office 2016 suite? + + [Overview of the upgrade of Office 365 ProPlus to the Office 2016 version](https://technet.microsoft.com/EN-US/library/mt656689.aspx) + + + + diff --git a/DeployOffice/best-practices-for-deploying-office-2016-to-mac-clients.md b/DeployOffice/best-practices-for-deploying-office-2016-to-mac-clients.md new file mode 100644 index 000000000..de6ae584f --- /dev/null +++ b/DeployOffice/best-practices-for-deploying-office-2016-to-mac-clients.md @@ -0,0 +1,69 @@ +--- +title: Best practices for deploying Office 2016 to Mac clients +ms.prod: OFFICE365 +ms.assetid: 9976a65c-2e66-4781-b830-02db03b1cdba +--- + + +# Best practices for deploying Office 2016 to Mac clients + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +This article defines the system requirements and deployment information for Office 2016 for Mac. +## System requirements + +The following table lists the standard system Office System Requirements. However, system requirements are subject to change. Therefore, see [System requirements for Office](https://products.office.com/en-US/office-system-requirements) for the most current Office system requirements. + + + + +||| +|:-----|:-----| +|**Component**
|**Requirement**
| +|Operating system
|Mac: At least Mac OS X 10.10
| +|Computer and processor
|Mac: Intel Processor
| +|Memory
|Mac: 4 GB of RAM
| +|Disk space
|Mac: 6 gigabytes (GB) available, HFS + hard disk format
| +|Display
|Mac: 1280 x 800
| +|Browsers
|Current or immediate previous versions of Internet Explorer
Current version of Safari, Chrome, Firefox, or Microsoft Edge
| +|.Net
|PC: .NET 3.5 required, some features may require .NET 4.0, 4.5, or 4.6 CLR to also be installed
| + + +## Office 2016 for Mac references + +The following links provide detailed information about Office 2016 for Mac deployments: + + + + +- [What's new for admins in Office 2016 for Mac](https://technet.microsoft.com/en-us/library/mt346044%28v=office.16%29.aspx) + + +- [Overview of activation for Office 2016 for Mac](https://technet.microsoft.com/en-us/library/mt346043%28v=office.16%29.aspx) + + +- [Deployment options for admins for Office 2016 for Mac](https://technet.microsoft.com/en-us/library/jj984157%28v=office.16%29.aspx) + + +- [Deploy preferences for Office 2016 for Mac](https://technet.microsoft.com/en-us/library/jj984220%28v=office.16%29.aspx) + + +- [Deploy updates for Office 2016 for Mac](https://technet.microsoft.com/en-us/library/jj984187%28v=office.16%29.aspx) + + +- [Office 2016 for Mac upgrade to 64-bit](https://technet.microsoft.com/en-us/library/mt762139%28v=office.16%29.aspx) + + +- [Download and install or reinstall Office 365 or Office 2016 on your PC or Mac](https://support.office.com/en-us/article/Download-and-install-or-reinstall-Office-365-or-Office-2016-on-your-PC-or-Mac-4414eaaf-0478-48be-9c42-23adc4716658?ui=en-US&rs=en-US&ad=US) + + +- [What to try if you can't install Office 2016 for Mac](https://support.office.com/en-us/article/What-to-try-if-you-can-t-install-Office-2016-for-Mac-5efba2b4-b1e6-4e5f-bf3c-6ab945d03dea?ui=en-US&rs=en-US&ad=US) + + +- [Troubleshoot Office 2011 for Mac issues by completely uninstalling before you reinstall](https://support.office.com/en-us/article/Troubleshoot-Office-2011-for-Mac-issues-by-completely-uninstalling-before-you-reinstall-ba8d8d13-0015-4eea-b60b-7719c2cedd17?ui=en-US&rs=en-US&ad=US&fromAR=1) + + + diff --git a/DeployOffice/best-practices-for-deploying-office-365-proplus.md b/DeployOffice/best-practices-for-deploying-office-365-proplus.md new file mode 100644 index 000000000..d8466dac3 --- /dev/null +++ b/DeployOffice/best-practices-for-deploying-office-365-proplus.md @@ -0,0 +1,209 @@ +--- +title: Best practices for deploying Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: f8a53994-d9e5-46db-aa90-a704bcca2473 +--- + + +# Best practices for deploying Office 365 ProPlus + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +When planning for and implementing a modern Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment, it is critical to understand the available deployment options. This article covers the preferred deployment options and provides high level descriptions of the architecture components. +## Deployment options + +The three common deployment options for delivering Office 365 ProPlus to customer's end user devices are: + + + + +- [The Enterprise Managed scenario](best-practices-deployment-scenarios.md#Enterprise) uses software distribution tools to deploy Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + +- [The Locally Managed scenario](best-practices-deployment-scenarios.md#Local) uses on-premises file distribution systems to deploy Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + +- [The Cloud Managed scenario](best-practices-deployment-scenarios.md#Cloud) uses the Office Content Delivery Network (CDN) to deploy Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + +For additional information on these customer scenarios, see the [Best Practices: Deployment scenarios](best-practices-deployment-scenarios.md). + + + +The following is a high level overview of the general deployment components and tools that are used in an Office 365 ProPlus deployment. + + + + +## Client distribution and update maintenance infrastructure overview + +In general, the modern Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment solution includes functionality to deploy, maintain, and update clients from both an on premise infrastructure, and from an off premise Office Content Delivery Network (CDN) infrastructure. The on premise and off premise deployment infrastructures provide IT administrators flexibility to manage the initial deployment and maintenance of the Office client for different connectivity and end user segments of their environment. + + + +The following image shows a high level overview of the on premises and off premises deployment infrastructure components for Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + + + + + + +![High level overview deploy Office 365](images/bebd7cb7-2bec-42e4-ae5e-ecc6817d9484.jpg) + + + +The deployment solution is comprised of two main source file distribution locations: + + + + +- **Off premises distribution (A)** - distribution from the Office Content Delivery Network (CDN). + + +- **On premises distribution (B)** - distribution from local file shares, software distribution systems, or distributed file systems. + + +The following supporting processes contribute to the overall deployment solution: + + + + +- **Office Deployment Tool** - Tool used to customize and configure Office UNRESOLVED_TOKEN_VAL(365) ProPlus distribution packages. + + +- **Deployment Package** - components required to install Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + +- **Office Build Maintenance** - For each channel release, a proper patching protocol must be established. + + +- **Network Bandwidth** - It is recommended to use maintenance windows to distribute Office builds to mitigate network bandwidth impact. + + +- **Security Management** - Group Policy settings (GP) are recommended for managing Office UNRESOLVED_TOKEN_VAL(365) ProPlus first run and user experience, as well as to manage incompatible Office Add-Ins + + + +## Overview of key infrastructure components + + +### Source file distribution locations + +There are two preferred source file distribution locations when deploying and managing Office UNRESOLVED_TOKEN_VAL(365) ProPlus. When planning and building an Office UNRESOLVED_TOKEN_VAL(365) deployment solution, it is recommended to understand the distribution locations and benefits of each location. Each source file location has benefits, and most deployment solutions will leverage both locations to provide the IT administrators with flexibility to use the best location based on the connectivity and delivery requirements of the end user segments in the environment. + + + + **Off Premises distribution using the Office CDN** + + + +While it is not common for an enterprise to use the Office UNRESOLVED_TOKEN_VAL(365) portal for the initial Office UNRESOLVED_TOKEN_VAL(365) ProPlus client install, there are scenarios where you should use the Office CDN as the "SourcePath" location in theOffice UNRESOLVED_TOKEN_VAL(365) ProPlus client deployment package. Leveraging the Office CDN as a "SourcePath" allows the IT department to manage the deployment through a controlled deployment process, and then leverage the Office CDN for the source file locations. This method allows the customer's IT department to have direct control over when end users will receive the new Office client, allows the IT department to configure what applications will be installed on the end user's client device, and takes advantage of Microsoft's file replication and distribution capabilities on the Office CDN. + + + +The IT managed deployment method using the Office CDN provides enterprises with the flexibility to support remote users and smaller branch offices with minimal corporate connectivity to deploy, update, and patch the end users devices. For an in depth overview of the Office UNRESOLVED_TOKEN_VAL(365) CDN, see [Content delivery networks](https://support.office.com/en-us/article/Content-delivery-networks-0140f704-6614-49bb-aa6c-89b75dcd7f1f?ui=en-US&rs=en-US&ad=US). + + + + **On Premises distribution locations** + + + +A majority of enterprise customers already have tools and processes in place for managing software and file distribution, such as System Center Configuration Manager, distributed file system (DFS) solutions, or other software distribution systems. If you have already invested in software distribution solutions, it is preferred to leverage these systems for the Office UNRESOLVED_TOKEN_VAL(365) ProPlus client. By leveraging existing infrastructures, you can lower the education ramp for users by not having to invest in training for a new system as part of the overall deployment. + + + + +### Office Deployment Tool + +The Office Deployment Tool downloads and installs Office UNRESOLVED_TOKEN_VAL(365) clients. You can download the most recent version of the [Office 2016 Deployment Tool](https://www.microsoft.com/en-us/download/details.aspx?id=49117) from the Microsoft Download Center. It is highly recommended for customers to frequently check for a newer version of the Office Deployment Tool, as it might contain updates. + + + +For detailed information on the Office Deployment Tool, see [Best practices: Office Deployment Tool](http://technet.microsoft.com/library/948e3efd-c45b-41e2-80c4-7fccb4dac043.aspx). + + + +Perform the following steps to extract the executable together with a sample configuration XML: + + + + +1. Download the [Office 2016 Deployment Tool](https://www.microsoft.com/en-us/download/details.aspx?id=49117). + + +2. Double-click **officedeploymenttool.exe**. + + +3. Accept the Microsoft Software License Terms. + + +4. Select a destination folder (for example, **C:\\ODT** ), and click **OK** to continue. + + +5. Click ** OK** to finish. + + +You now have a folder structure that looks similar to the following screenshot: + + + + + + + +![ODT folder structure](images/ea7f0c80-3f3d-405b-add1-0707677a828e.png) + + + + + + + + + + + + +### Deploy by using software distribution tools + +This section covers the general steps for deploying Office UNRESOLVED_TOKEN_VAL(365) ProPlus by using existing software distribution tools. For specific instructions and prescribed guidance for software distribution tools, see [Best practices: System Center Configuration Manager configuration for enterprise managed](best-practices-system-center-configuration-manager-configuration-for-enterprise.md). + + + +Deploying Office UNRESOLVED_TOKEN_VAL(365) ProPlus with an existing software distribution tool is the recommended solution for a majority of enterprise customers because it is already in use for other software distribution, and the infrastructure required to distribute the Office 365 ProPlus client already exists. The follow steps are the generalized recommended steps for a successful deployment. + + + + +1. Prepare the Office UNRESOLVED_TOKEN_VAL(365) ProPlus Installation Files. + + +2. Create an application in the software distribution system. + + +3. Create a deployment type for the application. + + +4. Distribute the application to distribution points. + + +5. Deploy the application to the appropriate device collection. + + +A critical change in deploying with software distribution tools is that in the configuration XMLs, the SourcePath attribute must be removed because software distribution tools typically copy the installation files to a different named subfolder on each computer, and the SourcePath cannot be specified for every computer. When the SourcePath isn't specified or left out, the Office Deployment Tool automatically looks for the Office UNRESOLVED_TOKEN_VAL(365) ProPlus installation files in the same folder in which the Office Deployment Tool is located. + + + + +## Group Policy settings + +See [Best practices for implementing group policy](best-practices-for-implementing-group-policy.md) for instructions on how to deploy the desired Group Policy settings into production. + + + + diff --git a/DeployOffice/best-practices-for-group-policy.md b/DeployOffice/best-practices-for-group-policy.md new file mode 100644 index 000000000..61b576a40 --- /dev/null +++ b/DeployOffice/best-practices-for-group-policy.md @@ -0,0 +1,127 @@ +--- +title: Best practices for group policy +ms.prod: OFFICE365 +ms.assetid: e0deafc7-4646-49ea-9882-a2ad8b47a7e4 +--- + + +# Best practices for group policy + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + +## Policy settings added with Office 2013 + + +- Default UI Theme + + +- Disable Outlook Update Notifications + + +- Enable Retrieval of Remote Certificate Authority Information + + +- Hide the Office Store button in Outlook + + +- Hide Update Notification + + +- Show OneDrive Sign In + + +- Target Version + + +- Update Deadline + + +- Update Path + + +- Updates to existing IE Security settings + + + +## Policy settings added with Office 2016 + + +- Age out the locally cached copies of server document versions that are more than *n* days old + + +- Block macros from running in Office files from the Internet + + +- Conversion Service Options + + +- Disable Real Time Coauthoring for Word + + +- Do not promote InfoPath forms properties into Outlook properties + + +- Document Information Panel Beaconing UI + + +- Enable DLP on application boot + + +- Hide built-in shape style presets + + +- Office 365 Client Management + + +- Office document cache location + + +- Offline Mode for Document Information Panel + + +- PowerPoint Designer Options + + +- Prevent personal Microsoft accounts from using MAPI + + +- Prioritize BITS + + +- Publish to Docs.com + + +- Send personal information + + +- Set the minimum operating system for verifying agile VBA signatures + + +- Trust legacy VBA signatures + + +- Turn off audio recording for screen recording + + +- Update Branch + + + +## Overview of all Office 2016 Group Policy settings + +The **office2016grouppolicyandoctsettings.xlsx** spreadsheet contains all of the Office 2016 Group Policy settings. + + + + +> [!NOTE] +> Microsoft provides updates to the Office 2016 Group Policy settings. You should periodically check for new releases of the Office 2016 Administrative Template files at [Download the Administrative Templates for Office 2016](https://www.microsoft.com/en-us/download/details.aspx?id=49030). + + + + + diff --git a/DeployOffice/best-practices-for-implementing-group-policy.md b/DeployOffice/best-practices-for-implementing-group-policy.md new file mode 100644 index 000000000..2940e106e --- /dev/null +++ b/DeployOffice/best-practices-for-implementing-group-policy.md @@ -0,0 +1,26 @@ +--- +title: Best practices for implementing group policy +ms.prod: OFFICE365 +ms.assetid: 484b129d-9220-409e-bf0c-d0057653f793 +--- + + +# Best practices for implementing group policy + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + **Implement the best practices GPOs** +1. Import the Office 2016 Administrative Templates into AD DS: + + - [Download the Administrative Templates for Office 2016](https://www.microsoft.com/en-us/download/details.aspx?id=49030) + + + - Extract the content and import it into your central store for Group Policy settings on a domain controller (see [Managing Group Policy ADMX Files Step-by-Step Guide](https://technet.microsoft.com/en-us/library/cc709647%28v=ws.10%29.aspx)). + + + + + diff --git a/DeployOffice/best-practices-for-installing-office-365-proplus-from-cdn-or-dfs.md b/DeployOffice/best-practices-for-installing-office-365-proplus-from-cdn-or-dfs.md new file mode 100644 index 000000000..d41b2939d --- /dev/null +++ b/DeployOffice/best-practices-for-installing-office-365-proplus-from-cdn-or-dfs.md @@ -0,0 +1,258 @@ +--- +title: Best practices for installing Office 365 ProPlus from CDN or DFS +ms.prod: OFFICE365 +ms.assetid: 80b82132-22c2-4628-84b4-fbbd6598aaba +--- + + +# Best practices for installing Office 365 ProPlus from CDN or DFS + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +When planning for and implementing a Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment, it is critical to understand the available deployment options. This article covers the high level description of the different architecture components that are used in the CDN and DFS client deployment processes. +## Platform architecture + +Office UNRESOLVED_TOKEN_VAL(365) ProPlus is available in both 32-bit and 64-bit editions. You should understand the advantages and disadvantages before selecting a specific architecture. + + + +The following table details the advantages and disadvantages of selecting 64-bit Office: + + + + +||| +|:-----|:-----| +|**Advantages**
|**Disadvantages**
| +|64-bit can address more memory than 32-bit.
|Native 64-bit Office UNRESOLVED_TOKEN_VAL(365) ProPlus cannot be installed on computers that have 32-bit Office applications and third- party add-ins installed.
| +|Excel 2016 can load much larger workbooks. Excel 2016 made updates to use 64-bit memory addressing to move beyond the 4 gigabytes (GB) addressable memory boundary that limits 32-bit applications. (Must be on version 1602 and current channel. The update for Deferred Channel is expected to release in Oct 2016.)
|Macros and add-ins might need to be re-written to work in an 64-bit environment.
| +|Some tools, like Power Query, are supported in 64-bit environments only.
|Some applications may not render graphics correctly.
| + + +> [!NOTE] +> For detailed guidance, see [64-bit editions of Office 2013](https://technet.microsoft.com/en-us/library/ee681792%28v=office.15%29.aspx). + + + + +It is recommended that 32-bit is used for both 32-bit and 64-bit operating systems if users in your organization depend on existing extensions to Office, such as Microsoft ActiveX® controls, third-party add-ins, in-house solutions built on previous versions of Office, or 32-bit versions of programs that interface directly with Office. + + + +If some users in your organization are Excel expert users who work with Excel spreadsheets that are larger than 4 GB, they can install the 64-bit edition of Office 365 ProPlus. In addition, if you have in-house solution developers, we recommend that those developers have access to the 64-bit edition of Office UNRESOLVED_TOKEN_VAL(365) ProPlus so that they can test and update your in-house solutions in the 64-bit edition of Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + + + +### Click-to-Run technology + +Click-to-Run is a Microsoft streaming and virtualization technology that reduces the time that is required to install Office and helps you run multiple versions of Office on the same computer. The streaming technology lets you download and begin to use an Office product before the whole product is installed on the computer. + + + +The virtualization technology provides an isolated environment for Office to run on your computer. This isolated environment provides a separate location for the Office product files and settings to be stored so that they don't change other applications that are already installed on the computer. This lets you run the latest version of Office side -by-side with an earlier version of Office that is already installed on the computer. + + + + +> [!NOTE] +> The earlier version of Office that is already installed on the computer must be one of the following versions of Office: Office 2010, Office 2007, or Office 2003. Microsoft only tests the N-1 for side by side compatibility.> The versions of Office that you install must be the same edition. For example, both installations of Office are the 32 -bit edition. + + + + +Even though the Office product runs in a self-contained environment, the Office product can interact with the other applications that are installed on the computer. Macros, in-document automation, and cross-Office product interoperability will work. Click-to-Run is designed to allow locally-installed add-ins and dependent applications to work with it. However, some add-ins or other integration points with Office might behave differently or might not work when you are using Click-to-Run. + + + +Click-to-Run is used to install and update Office products. These streaming and virtualization capabilities are based on technologies include in Microsoft Application Virtualization (App-V). + + + + +### Installation process + +Click-to-Run uses a multi-process framework to do the following tasks: + + + + +- Start an installation and perform core Click-to-Run tasks such as streaming and application start. + + +- Maintain state for the virtualized package. + + +- Initiate integration tasks. + + +- Monitor for updates. + + +- Provide an interface into the Click-to-Run platform. + + +Applications and processes use this interface to query for state and to communicate information. + + + + + + + +![Click-to-Run deploy process](images/532c35a1-c16e-41f1-8c45-b9e00f0d04f9.png) + + + +A single executable program contains the logic that is required to initiate Click-to-Run streaming and application start processes. It includes all the components that are required to stream Click-to-Run packages. + + + +Streaming of Office, a core component of the Click-to-Run infrastructure, allows for parts of the product to be prioritized, grouped into blocks, and delivered over time while the applications run. The streaming process is controlled by the streaming engine. + + + +The streaming engine manages downloads of items in the streaming queue, prioritizes incoming streaming requests, determines whether to display streaming user interface, and publishes the downloaded information to the native file system. The streaming engine also maintains a streaming queue, a prioritized list of all the Office sources and components that are to be downloaded to the local cache to complete the installation or to fulfill on-demand requests that are generated by an application's runtime. Every Click-to-Run package has a default streaming queue prioritization at first. This prioritization can change dynamically in response to application use before the product is fully cached locally. + + + + +## Feature selection + +Due to the nature of Click-to-Run deployment, customizations and feature selections at the application level are not possible. This is unlike Office MSI versions, where the Office Customization Tool (OCT) can be used to generate customized .msp files for use at install time. + + + + +## Customization + +After the Office configuration decisions have been made, an approach must be defined to apply these settings to the Office installation. Customization of Office deployment can be broken into two key approaches: + + + + +- During deployment + + +- Post deployment + + + +### Deployment customization + +The Office UNRESOLVED_TOKEN_VAL(365) ProPlus installation architecture offers only one method to perform customization during deployment: using an XML definition file. + + + + **Setup customization file (XML)** + + + +The XML file configures the way that Setup will interact with user and how Office 365 ProPlus is installed and maintained. + + + +You can specify the following options in the XML file: + + + + +- Languages to install. + + +- Platform architecture to install (32-bit or 64-bit). + + +- License activation feature. + + +- Installation logs usage. + + +- Display information. + + +- Update settings. + + + **Multiple language deployment** + + + +When configuring the deployment of multiple languages, it is important to consider the approach the deployment of these languages. By default, Setup installs only the language version that match elements that are defined in the XML customization file. + + + +You can install more than one language on a single computer without using more than one license. The first language that is defined in the XML configuration file is the default language. Each language size is between 150 -250 MB. + + + + +## Prepare to deploy + +The MSI version of Office allows for the Office Customization Tool (OCT) to customize Office installation. The OCT tool cannot be leveraged for Office UNRESOLVED_TOKEN_VAL(365) ProPlus. Instead, customization is accomplished by using Group Policy. + + + + +- Review and record the customization settings in the legacy version of Office. + + +- Download the [Office 2016 Administrative Template files](https://www.microsoft.com/en-us/download/details.aspx?id=49030). + + +- Choose the 32 or 64-bit template files. + + +- Compare the recorded customization settings with the Office 2016 Administrative Template Excel spreadsheet for Office UNRESOLVED_TOKEN_VAL(365) ProPlus Customization. + + +- Import the Office 2016 Administrative Template Files into Active Directory and configure the appropriate Group Policy settings. See [Managing Group Policy ADMX Files Step-by-Step Guide](https://msdn.microsoft.com/en-us/library/bb530196.aspx). + + +The Office 2016 Administrative Template files are updated with new settings to control the look and feel of Office UNRESOLVED_TOKEN_VAL(365) ProPlus + + + + +### Languages + +It is a preferred practice that Office UNRESOLVED_TOKEN_VAL(365) ProPlus languages are installed during the initial installation. Additionally, languages can be deployed post installation. You can review the supported languages for Office UNRESOLVED_TOKEN_VAL(365) ProPlus at [Language identifiers](https://technet.microsoft.com/en-us/library/f5fee727-df49-4ef7-b073-dd6c08dfecfa). + + + + +### Office applications + +The following applications are included with Office 365 ProPlus: [Office 365 ProPlus](https://products.office.com/en-us/business/office-365-proplus-business-software). Although InfoPath is not included in Office 365 ProPlus, it is available for Office 365 ProPlus subscribers. The download for InfoPath 2013 for Office 365 ProPlus Subscription is located [here](https://www.microsoft.com/en-us/download/details.aspx?id=48734). + + + + +- Review the applications. + + +- Decide which applications to deploy. + + + +## Visio and Project 2016 + +Visio 2016 and Project 2016 are not included with Office UNRESOLVED_TOKEN_VAL(365) ProPlus, and require a separate license. You can install the volume licensed versions of Project and Visio 2016, with the requirements are located at [Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016](https://technet.microsoft.com/library/mt703272.aspx). The installations leverage C2R technology, but activate by using a traditional MAK/KMS system. + + + + +## Side by side or removal of legacy Office + + +- Side by Side - It is a preferred practice that the legacy versions of Office are removed during the installation of Office ProPlus. Side by side should be only be used for limited testing during the pilot deployment. + + +- Removal of Legacy Office -The preferred practice for the removal of legacy versions of Office is to utilize OffScrub for the specific version Office. OffScrub is fully supported by Premier and should be contacted to obtain the required versions. + + + diff --git a/DeployOffice/best-practices-for-managing-channels.md b/DeployOffice/best-practices-for-managing-channels.md new file mode 100644 index 000000000..5a02b4d58 --- /dev/null +++ b/DeployOffice/best-practices-for-managing-channels.md @@ -0,0 +1,189 @@ +--- +title: Best practices for managing channels +ms.prod: OFFICE365 +ms.assetid: 99aa9fba-e188-4ca0-ac0a-2c82d6ed5242 +--- + + +# Best practices for managing channels + +> [!IMPORTANT] +> On April 20, we announced changes to better align the Office 365 ProPlus and Windows 10 update models. In that [blog post](https://go.microsoft.com/fwlink/p/?linkid=846981), we highlighted changes to the release cadence and the support duration of feature updates for Office 365 ProPlus. As part of these changes, Office 365 ProPlus is also changing the names of its update channels. > For more information about these changes, see [Overview of the upcoming changes to Office 365 ProPlus update management](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md). > As most of these changes take effect in September 2017, this content will be updated in the next few months. + + + + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* +This article describes recommended channel membership roles and best practices for channel management. + + + + + +## Channel membership roles + +Customers appreciate the value of constantly getting new features with Office UNRESOLVED_TOKEN_VAL(365) ProPlus; however, there is a concern about how often the product updates and how to have adequate time to validate the new features so that they don't break existing business processes. Additional time is also needed to train the help desk and end users before the feature is enabled through the production environment. Customers have done this previously with software and patches they release by first releasing it to a QA group that represents a population sample of all business groups and apps. After the QA group has the software/patch and has not reported any adverse effects in 1 -2 weeks, the IT team then starts the production roll out to the entire organization. + + + +This process can now be achieved by leveraging the different Office UNRESOLVED_TOKEN_VAL(365) client channel builds so that the QA group has the features for at least 4 months before the rest of the enterprise receives those features. + + + +To have appropriate channel representation across the environment, we recommend you use the following diagram. Each group can have Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployed and managed by using the Office Content Delivery Network (CDN), an on premises source location, or a mix between the Office CDN and an on premises source location. Additionally, pilot and pre-production groups should have instructions on how to immediately report abnormalities or issues, so they can be addressed before they are released in the Deferred Channel build. + + + + + + + +![Channel rings](images/42c08d42-6ff1-4729-ae7a-b4011a499989.png) + + + + +|||||| +|:-----|:-----|:-----|:-----|:-----| +|**Ring**
|**Channel**
|**Client population**
|**Primary function**
|**Roles**
| +|Pilot deployment
|Current
|< 1%
|Evaluate new features and functionality before release across all available channels.
|Developers, testers, application/add-in owners, IT and O365 champions, Office project team members, training and communication leads.
| +|Pre-production deployment
|First Release for Deferred Channel
|< 10%
|Business group feature and functionality validation, provide direct feedback to IT and Office admins.
|Developers, testers, training and communication leads, business group champions, and designated end users from each business group.
| +|Production deployment
|Deferred
|~89%
|End user production.
|All end users not in the pilot or pre-production groups.
| + + +## Manage updates overview + +This section describes how to implement an automated process to publish Office UNRESOLVED_TOKEN_VAL(365) ProPlus builds. By default, each client is set to pull from the Office CDN using the Deferred Channel update channel method. The client will check the specified update path location and if there is no new version, it will remain as is. If there is a newer version, the client will perform a delta binary to calculate the difference between itself and the update location's build, compress the data, and then start the transmission to update. Office will use Background Intelligent Transfer Service (BITS) to control bandwidth if downloading from the Office CDN; BITS is not applied if downloading from an SMB file share. The client does not need administrative privileges to update. Office checks for updates regularly via a scheduled task and can be seen in Task Scheduler. + + + + +## Channel management + + +When updating directly from the Office CDN, channel management is managed by the cloud service. This means that based on the channel membership, the Office client gets the appropriate build of Office. + + + +The Office update engine cannot distinguish between the channels; it is driven by build numbers. If you control patching on premises, we highly recommend that you review the following sections, because the Office client is missing the proper channel management control from the Office CDN. There is no channel awareness by the Office client when the update source is managed on premises. This means that the update engine picks up the latest available build that is advertised through the v32.cab file. When managing patching on premises withOffice UNRESOLVED_TOKEN_VAL(365) ProPlus 2016, careful consideration, planning, and organization is required to make sure that Office clients receive the correct channel builds. + + + + +### Manage updates through the Office CDN + +The following steps are recommended for a fully automated testing and deployment process using the Office CDN for patching: + + + + +1. Identify and configure a pilot group to use Current Channel. + + +2. Identify and configure a pre-production or QA group to use First Release for Deferred Channel. + + +3. Configure all other clients to be in the production group to use Deferred Channel. + + +4. Configure all groups to receive updates directly from the Office CDN. + + +5. When a new build is released for the various channels, the update mechanism automatically downloads the latest build by using a scheduled task. + + +6. Have pilot and pre-production groups use Office as usual, with instructions to immediately report any issues or concerns. + + + +### Manage updates on premises + +If your organization does not have the network capacity to adopt updates directly from the Office CDN, the builds can instead be hosted in an on premises source location. + + + + +> [!NOTE] +> After the builds are hosted on premises, the Office client is missing the proper channel management control and the update engine will pick up the latest available build rather than the associated channel membership. + + + + +Due to the availability dates of the builds, we recommend that you check for build updates several times per month. An automated task can be created to check the Office CDN to see if there is a newer build available in a specific channel. If so, the automated task can download the build source files to a specified location. An administrator can then take the newly download source files and distribute them out to the appropriate channel membership groups. + + + + +### Switch update channels + +If you switch update channels, you should carefully plan to account for the full delta change. Switching Channels is not advised because it is a 100% file delta install. If the channel you are switching to is 1.2 GB, then a complete 1.2 GB of network bandwidth is consumed if installing locally (700-800 GB if using Office CDN). There is no need to uninstall and then re-install; however, the network impact is the same as a new install. The task of switching update channels should use the existing deployment infrastructure. + + + +For step by step guidance on switching update channels, see [Best practices: Channel management](best-practices-channel-management.md). + + + + +## Out-of-Band build for Deferred Channel + + +Microsoft might release an out-of-band build outside of the estimated release timeline for Deferred Channel. In these cases, it is recommended that the deployment administrators evaluate the out-of-band build and whether to deploy or skip the out of band build. + + + +If it is deemed critical for deployment, follow the same deployment procedures that were previously stated and process it as usual. Otherwise, skip the out-of-band build and deploy the released out of band Patch Tuesday build. + + + + +## Rollback or downgrade strategy + + +A rollback or downgrade strategy should be planned in the unlikely event that a new Office 365 ProPlus build causes a disruption in service. The update engine can perform a downgrade, but the engine must be instructed to rollback by specifying a previous build number to rollback to. If the target version is not specified, the Office 365 ProPlus client cannot complete a downgrade. + + + +Similar to update scenarios, the rollback should take the client channel membership into account. The downgrade should respect the current channel membership of the client, and a target build version correlating to that current channel membership should be specified to maintain channel membership. If the target version specified is of a different channel than the channel that the client is currently on, the downgrade will succeed and a full delta will be performed in downgrading to the different channel. + + + +For guidance on how to perform a rollback using the OfficeC2RClient.exe update engine, see [Best practices: Channel management](best-practices-channel-management.md). + + + + +## Group Policy management + + +Customers should incorporate the [Office 2016 Administrative Template files (ADMX/ADML)](https://www.microsoft.com/en-us/download/details.aspx?id=49030) to configure update settings for Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + + + +> [!NOTE] +> When using Group Policy settings to manage Office UNRESOLVED_TOKEN_VAL(365) ProPlus, the Group Policy settings take precedence over any configuration settings that are set by the install XML and Office Deployment Tool. Therefore, it is recommended that you use Group Policy settings as additional enforcement to settings that are specified via the install XML and Office Deployment Tool + + + + +You can use the following Group Policy objects to manage Office 365 ProPlus: + + + + +||| +|:-----|:-----| +|**Update setting**
|**Group Policy setting**
| +|Set updates to occur automatically
|Enable automatic updates
| +|Specify a location to look for updates
|Update path
| +|Specify the version of Office UNRESOLVED_TOKEN_VAL(365) ProPlus to update to
|Target version
| +|Set a deadline, by which time updates must be applied
|Update deadline
| +|Hide update notifications from users
|Hide update notifications
| +|Hide the option to enable or disable Office automatic updates
|Hide options to enable or disable updates
| + +For more information on managing updates by using Group Policy, or to manage Office 365 ProPlus update settings using the Office Deployment Tool configuration options, see [Configure update settings for Office 365 ProPlus](https://technet.microsoft.com/en-us/library/dn761708.aspx). + + + + diff --git a/DeployOffice/best-practices-for-managing-updates-in-office-365-proplus.md b/DeployOffice/best-practices-for-managing-updates-in-office-365-proplus.md new file mode 100644 index 000000000..a1f91f327 --- /dev/null +++ b/DeployOffice/best-practices-for-managing-updates-in-office-365-proplus.md @@ -0,0 +1,67 @@ +--- +title: Best practices for managing updates in Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 7c80254b-cc14-441c-8500-333d32c71949 +--- + + +# Best practices for managing updates in Office 365 ProPlus + +> [!IMPORTANT] +> On April 20, we announced changes to better align the Office 365 ProPlus and Windows 10 update models. In that [blog post](https://go.microsoft.com/fwlink/p/?linkid=846981), we highlighted changes to the release cadence and the support duration of feature updates for Office 365 ProPlus. As part of these changes, Office 365 ProPlus is also changing the names of its update channels. > For more information about these changes, see [Overview of the upcoming changes to Office 365 ProPlus update management](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md). > As most of these changes take effect in September 2017, this content will be updated in the next few months. + + + + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* +Because Office UNRESOLVED_TOKEN_VAL(365) ProPlus is an Evergreen product, it is important to consider ongoing management after Office UNRESOLVED_TOKEN_VAL(365) ProPlus is deployed. This article provides a high level overview of the components that are involved with Office UNRESOLVED_TOKEN_VAL(365) ProPlus management. + + + + + +## IT managed and unmanaged deployment scenarios + +In general, the Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment solution includes functionality to deploy, maintain, and update clients from both an on premise infrastructure and off premise Office Content Delivery Network (CDN) infrastructure. The on premise and off premise deployment infrastructures give IT administrators flexibility to manage the initial deployment and maintenance of the Office client for different connectivity and end user segments of the environment. + + + +For more information on deployment scenarios and channel management, see [Best practices for managing channels](best-practices-for-managing-channels.md). + + + + +## Patching and update channels with Office 365 ProPlus + +With the 2016 release of Office UNRESOLVED_TOKEN_VAL(365) ProPlus, Microsoft introduces the concept of update channels. Update channels give IT admins control over when new features will be rolled out to end users. It allows IT admins more time to validate critical business applications with new features, and lets IT admins manage communications and training needs of their end users . A majority of enterprise customers will use the Deferred Channel for their general end user population; however, IT admins should also use other channels for their pilot and pre-production user groups to create validation, communications, and training processes to ease feature roll outs to their end users. + + + +Each device in the customer's environment can be a member of a specified channel, which controls feature adoption and code stability. To balance the speed of adoption, running a stable environment, and preparing for updates and product changes, it is recommended to leverage all channels and segment the customer end user base by purpose and function. By segmenting the work force and having multiple groups, customer's IT admins have more flexibility and control. For detailed information on the Office UNRESOLVED_TOKEN_VAL(365) update channels, see [Best practices: Update channels](best-practices-update-channels.md). + + + +The following image shows how new features and non-security updates are propagated from Current Channel to First Release for Deferred Channel to Deferred Channel. + + + + + + + +![Office 365 release cadence](images/99a17880-4029-44e9-b478-be4058c30f92.png) + + + +See also [Best practices for managing channels](best-practices-for-managing-channels.md) + + + + +## Ongoing Office 365 ProPlus management and maintenance + +In addition to checking for new Office 365 ProPlus build releases, you should periodically check for newer builds of the 2016 Office Deployment Tool and Office 2016 Administrative Template files. New releases of these items can include new features or capabilities to help IT admins manage Office 365 ProPlus deployments. It is recommended that you have a process in place to make sure that the Office Deployment Tool and Office 2016 Administrative Template files that are being used are the latest available versions from Microsoft. + + + + diff --git a/DeployOffice/best-practices-for-office-telemetry.md b/DeployOffice/best-practices-for-office-telemetry.md new file mode 100644 index 000000000..2a60fd8eb --- /dev/null +++ b/DeployOffice/best-practices-for-office-telemetry.md @@ -0,0 +1,73 @@ +--- +title: Best practices for Office Telemetry +ms.prod: OFFICE365 +ms.assetid: 570c7fb3-d7a5-49cd-8cbf-7300ea656328 +--- + + +# Best practices for Office Telemetry + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Office Telemetry is the new compatibility monitoring framework that replaces the previous Office 2010 compatibility tools and helps minimize the time and risks of an Office upgrade. When an Office document or solution is loaded, used, closed, or raises an error in certain Office applications, the application adds a record about the event to a local data store. The record is then uploaded to the Office Telemetry database, where it is used together with the Telemetry Dashboard for IT admins to get a complete view of the Office Telemetry data that is being collected in the organization. +## Office Telemetry dashboard overview + +Telemetry Dashboard is an Excel workbook that is configured to connect to a telemetry database, and comes installed together with Office versions starting with Office 2013. The Telemetry Dashboard also allows IT admins to use pre-built reports or create custom reports that can help with critical applications. + + + +The Telemetry Dashboard should be used in conjunction with interviewing and working with key business stakeholders to identify the critical business applications that must be validated prior to deploying Office 365 ProPlus in the environment. It should not replace working with business groups; instead, it should assist with identifying how often users access specific components and the number of users for those particular components. + + + + +## Office Telemetry reference + +The following links provide additional details on Telemetry Dashboard components and recommended configuration options to assist you with application compatibility assessment: + + + + +- [Assess Office compatibility with other versions of Office](https://technet.microsoft.com/en-us/library/ee819096%28v=office.16%29.aspx) + + +- [Telemetry Dashboard topology, sizing, and bandwidth planning](https://technet.microsoft.com/en-us/library/jj822978%28v=office.16%29.aspx) + + +- [Office Telemetry tools and components](https://technet.microsoft.com/en-us/library/jj822978%28v=office.16%29.aspx) + + +- [Update Office Telemetry components for Office 2016](https://technet.microsoft.com/en-us/library/dn627517%28v=office.16%29.aspx) + + +- [Deploy Telemetry Dashboard](https://technet.microsoft.com/en-us/library/jj219431%28v=office.16%29.aspx) + + +- [Data that the telemetry agent collects in Office](https://technet.microsoft.com/en-us/library/mt599629%28v=office.16%29.aspx) + + +- [Document and solution types monitored by telemetry in Office](https://technet.microsoft.com/en-us/library/mt599633%28v=office.16%29.aspx) + + +- [Monitor Office compatibility and deployments by using Telemetry Dashboard](https://technet.microsoft.com/en-us/library/jj980533%28v=office.16%29.aspx) + + +- [Manage the privacy of data monitored by telemetry in Office](https://technet.microsoft.com/en-us/library/jj591589%28v=office.16%29.aspx) + + +- [Manage add-ins by using Telemetry Dashboard in Office](https://technet.microsoft.com/en-us/library/mt599631%28v=office.16%29.aspx) + + +- [Let's manage add-ins using Telemetry Dashboard](https://blogs.technet.microsoft.com/office_resource_kit/2012/09/17/lets-manage-add-ins-using-telemetry-dashboard/) + + +- [Telemetry Dashboard worksheet reference](https://technet.microsoft.com/en-us/library/jj980532%28v=office.16%29.aspx) + + +- [Custom reporting and database schema reference for Telemetry Dashboard](https://technet.microsoft.com/en-us/library/dn169565%28v=office.16%29.aspx) + + + diff --git a/DeployOffice/best-practices-for-planning-your-deployment-of-office-365-proplus.md b/DeployOffice/best-practices-for-planning-your-deployment-of-office-365-proplus.md new file mode 100644 index 000000000..c003cd11d --- /dev/null +++ b/DeployOffice/best-practices-for-planning-your-deployment-of-office-365-proplus.md @@ -0,0 +1,202 @@ +--- +title: Best practices for planning your deployment of Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: df4dba28-cc45-41a0-9b23-a1535523ab8c +--- + + +# Best practices for planning your deployment of Office 365 ProPlus + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Creating a deployment plan is a key component when migrating to Office UNRESOLVED_TOKEN_VAL(365) ProPlus. Planning is based on discovered assessment items, including constraints and how to implement Office UNRESOLVED_TOKEN_VAL(365) ProPlus to meet the goals of the project. +The following items should be considered when creating an Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment plan. + + + + + +## Source locations + +When planning for the Office source locations, it is recommended for the customer to use the existing tools and processes. Office UNRESOLVED_TOKEN_VAL(365) ProPlus can be deployed and updated directly from the Office Content Delivery Network (CDN), System Center Configuration Manager, or an internal share such as a network share or Distributed File System (DFS). + + + +For more information on deployment source locations, see [Best practices for deploying Office 365 ProPlus](best-practices-for-deploying-office-365-proplus.md). + + + + +## Channel membership + +To establish a build validation process within the organization, Microsoft recommends the following channel membership guidance: + + + + +- 1% get Current Channel + + +- 10% get First Release for Deferred Channel + + +- 89% get Deferred Channel + + +For specific guidance on channel membership and management, see [Best practices for managing channels](best-practices-for-managing-channels.md). + + + + +## Base client packaging + +Because Office UNRESOLVED_TOKEN_VAL(365) ProPlus is a customizable package, you should determine what application sets each business group should get. Applications that are initially excluded can be added back in later; specific applications can be removed after Office UNRESOLVED_TOKEN_VAL(365) ProPlus has already been installed. If an application isto be excluded from the Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment, you should create a plan to restore or replace the application. + + + + +## Architecture + +Planning should be completed to identify the deployment scenarios and use cases for the 64-bit architecture version of Office UNRESOLVED_TOKEN_VAL(365) ProPlus. The deployment plan should include how existing Office 64-bit users will be transitioned to the new Office UNRESOLVED_TOKEN_VAL(365) ProPlus client. + + + + +## Deployment configurations + +Appropriate planning must be done to create all of the required install XMLs for the various end user deployment scenarios in the organization. The install XMLs should also include the option to install individually supported language packs for users who need a language that was not part of the original Office UNRESOLVED_TOKEN_VAL(365) ProPlus installation. + + + + +## Shared computing + +Because Office UNRESOLVED_TOKEN_VAL(365) ProPlus has a specific Shared Computer Activation mode, the deployment plan should include how shared workstations and VDI environments will receive the correct installation package, as well as how they will be managed. + + + + +## Side by side + +While Office UNRESOLVED_TOKEN_VAL(365) ProPlus supports generally an N-1 coexistence scenario with previous versions of Office, careful consideration and planning must be completed for any side by side scenarios. If Office side by side is going to be used in the environment, the deployment plan should contain an estimated time line of when users will transition off of the legacy Office applications and rely solely on Office UNRESOLVED_TOKEN_VAL(365) ProPlus. Although Office side by side is generally supported by Microsoft, it is not recommend as a long term solution for end users. + + + +For more information on coexistence planning for side by side, InfoPath, and Project and Visio deployments, see [Best practices for planning - reference materials](best-practices-for-planningreference-materials.md). + + + + +## Infopath + +Because InfoPath is no longer part of the Office 2016 suite, a separate standalone installation of InfoPath 2013 must be configured and deployed. InfoPath will no longer be a part of the Office suite moving forward; plan accordingly. + + + + +## Project and Visio + +There are multiple versions of Project and Visio that are supported to run alongside with Office UNRESOLVED_TOKEN_VAL(365) ProPlus. Customers can leverage their existing Project and Visio MSI versions, or leverage the Click-to-Run (C2R) versions that support traditional volume licensing and Office UNRESOLVED_TOKEN_VAL(365) licensing models. The deployment plan should also include how users will request a Project or Visio install, and whether or not the process will be automated. + + + + +## Office Scrub Tool (OffScrub) + +You should use OffScrub to remove the legacy versions of Office prior to installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus, including the 2013 version of Office 365 ProPlus. The deployment plan should include how the OffScrub tool will be used and integrated into the task sequence or deployment script. + + + +For more information on the OffScrub tool, see [Best practices for using OffScrub](best-practices-for-using-offscrub.md). + + + + +## Office 2016 for Mac + +When planning for Office 2016 for Mac, existing Mac distribution methods and solutions should be considered. + + + +For more information about Office 2016 for Mac deployments, see [Best practices for deploying Office 2016 to Mac clients](best-practices-for-deploying-office-2016-to-mac-clients.md). + + + + +## Licensing + +When planning an Office UNRESOLVED_TOKEN_VAL(365) ProPlus deployment, careful considerations and planning should be done to ensure all users are assigned the appropriate Office UNRESOLVED_TOKEN_VAL(365) license that includes Office UNRESOLVED_TOKEN_VAL(365) ProPlus prior to the deployment. + + + + +## Network + +Office UNRESOLVED_TOKEN_VAL(365) ProPlus requires the following ports and protocols to be open: [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US). + + + +It requires a reliable connection to the Office CDN during both the deployment and management phases. Therefore, adequate planning should make sure that the network can support the deployment and management methodologies. + + + +For more network considerations, see [Best practices for planning - reference materials](best-practices-for-planningreference-materials.md). + + + + +## Skipping builds and rollbacks + +When Office UNRESOLVED_TOKEN_VAL(365) ProPlus updates to the next available version, it uses binary delta compression. However, when you skip a build or roll back, full file delta replication is used, which uses more bandwidth. You can switch from channel to channel; however, this is a 100% file download and should be avoided unless absolutely required. It is important to plan for the unlikely scenarios that a build will be skipped, or that a rollback to a previous version must be completed. Both scenarios have an impact on the network, so careful considerations should be made on when the actions can be performed to minimize end user impact. + + + +The following table provides examples (the actual numbers vary from build to build): + + + + +|||||| +|:-----|:-----|:-----|:-----|:-----| +|**Explanation**
|**Current build**
|**Next build**
|**Compression type**
|**Size**
| +|Update to next current build
|2060
|2062
|Binary Delta
|~134 MB
| +|Roll back large jump
|2060
|1078
|File Delta
|~677 MB
| +|Changing Channel
|Deferred
|Current
|100% File Delta
|~1,000 MB
| + +For more information about performing a rollback, see [Best practices: Channel management](best-practices-channel-management.md). + + + + +## Group Policy settings + +Office offers about 3,000 group policy settings to allow a granular control of security, privacy, and user experience. In most cases, only a subset of these are needed to adjust the configuration to the needs, requirements, and intended user experience of an organization. It is important to include other departments that are responsible for IT security, data protection, and privacy early to get a sign-off of the GPOs before the actual deployment happens. + + + + +### Call to action + + +- Review [Best practices for group policy](best-practices-for-group-policy.md) with more than 250 proven, commonly set policies for users and computers. Check the listed additional settings. + + +- Adjust the settings to fit your needs and requirements. + + +- Get a Resultant Set of Policy (RSOP) of today's policies and review them. Identify settings not covered in the Best Practices for Office UNRESOLVED_TOKEN_VAL(365) ProPlus, and consider adding them if the setting is still needed. + + +- Check which settings where introduced in Office 2013 and Office 2016 and consider adding them to your list of settings. + + +- Identify which entity in your organization must sign off security and privacy related settings, present them and get a sign-off. + + +- Get a sign off and hand the settings over to the team that administers the group Policy Settings. The Best Practices settings can easily be imported into your environment. + + + diff --git a/DeployOffice/best-practices-for-planningreference-materials.md b/DeployOffice/best-practices-for-planningreference-materials.md new file mode 100644 index 000000000..f421cb1e7 --- /dev/null +++ b/DeployOffice/best-practices-for-planningreference-materials.md @@ -0,0 +1,101 @@ +--- +title: Best practices for planning - reference materials +ms.prod: OFFICE365 +ms.assetid: 742fd8e2-8931-416a-8120-8ee982a6c825 +--- + + +# Best practices for planning - reference materials + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +The following articles provide deeper technical information on specific areas of the planning phase that are not covered in depth in the customer scenarios. +## Frequently asked questions + + +### What are Office 365 ProPlus related items I should plan for in my network impact? + + [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US&fromAR=1) + + + + [Network requests in Office 365 ProPlus](https://support.office.com/en-us/article/Network-requests-in-Office-365-ProPlus-eb73fcd1-ca88-4d02-a74b-2dd3a9f3364d?ui=en-US&rs=en-US&ad=US) + + + + +### How can I measure the network impact that Office 365 ProPlus builds have? + + [How big was this month's Office ProPlus update?](https://blogs.technet.microsoft.com/odsupport/2016/08/16/how-big-was-this-months-office-proplus-update/) + + + + +### How should I plan for my coexistence scenarios, such as preexisting versions of Office, Project, and Visio? + + [Supported scenarios for installing different versions of Office, Visio, and Project on the same computer](https://technet.microsoft.com/library/mt712177%28v=office.16%29.aspx) + + + + +### What's new to help me plan and manage an Office 365 ProPlus deployment? + + [What's new to help admins deploy and manage Office 365 ProPlus](https://technet.microsoft.com/en-us/library/mt422980.aspx) + + + + +### What's new to help me plan and manage an Office 2016 for Mac deployment? + + [What's new for admins in Office 2016 for Mac](https://technet.microsoft.com/en-us/library/mt346044%28v=office.16%29.aspx) + + + + +### How can I plan for a multi-language deployment of Office 365 ProPlus? + + [Plan for multilanguage deployment of Click-to-Run-based Office installations](https://technet.microsoft.com/en-us/library/dn186220.aspx) + + + + +### What are the language packs and proofing tools available for Office 365 ProPlus? + + [Language identifiers and OptionState Id values in Office 2016](https://technet.microsoft.com/en-us/library/cc179219%28v=office.16%29.aspx) + + + + [Do I need a language pack, Language Accessory Pack (LAP), or a Language Interface Pack (LIP)?](https://support.office.com/en-us/article/Do-I-need-a-language-pack-Language-Accessory-Pack-LAP-or-a-Language-Interface-Pack-LIP-4548ec6b-6d0e-40aa-8780-7bbee9554e04?ui=en-US&rs=en-US&ad=US&fromAR=1) + + + + [Companion proofing languages for Office 2016](https://technet.microsoft.com/en-us/library/ee942198%28v=office.16%29.aspx) + + + + [Language Accessory Pack for Office 2016](https://support.office.com/en-us/article/Language-Accessory-Pack-for-Office-2016-82ee1236-0f9a-45ee-9c72-05b026ee809f?ui=en-US&rs=en-US&ad=US&fromAR=1) + + + + +### I have shared workstations and/or a VDI environment. How does Office 365 ProPlus support shared devices? + + [Overview of shared computer activation for Office 365 ProPlus](https://technet.microsoft.com/en-us/library/dn782860.aspx) + + + + +### I'm currently running Office 365 ProPlus 2013. What planning needs to be done to upgrade to the Office 2016 suite? + + [Prepare to upgrade Office 365 ProPlus to the Office 2016 version](https://technet.microsoft.com/EN-US/library/mt422981.aspx) + + + + [Configure updates of Office 365 ProPlus to prepare for the upgrade to the Office 2016 version](https://technet.microsoft.com/EN-US/library/mt656688.aspx) + + + + diff --git a/DeployOffice/best-practices-for-using-offscrub.md b/DeployOffice/best-practices-for-using-offscrub.md new file mode 100644 index 000000000..da56215d7 --- /dev/null +++ b/DeployOffice/best-practices-for-using-offscrub.md @@ -0,0 +1,68 @@ +--- +title: Best practices for using OffScrub +ms.prod: OFFICE365 +ms.assetid: 07cf6be3-b6c7-435d-a1a7-6febe2cc3fd7 +--- + + +# Best practices for using OffScrub + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +The Office Scrub tool (OffScrub) is the best way to remove a previous version of Office. OffScrub has a better success rate of removing Office than traditional methods. It will call the setup.exe and msiexec.exe to remove the previous bits. It is best equipped to deal with machine or software corruption, and completely removes the Office app shortcuts for the previous Office versions. It is recommended to use OffScrub in almost every situation of migrating from previous versions of Office. OffScrub is supported by Premier, whom you should contact to obtain the latest version for your specific Office deployment. +Reasons for OffScrub to be used with legacy Office to Office 2016 C2R migrations: + + + + + +- If Office source bits or the cache is missing or unhealthy, the legacy product does not uninstall. + + +- Guarantees a clean uninstall. + + +- Does not touch the User Hive. + + +- Has verbose logging. + + +- Removes legacy addon products such a Visio Viewer, etc. + + +- Can remove Project and Visio and Office in one command. + + +- Removes non-standard company approved Office Applications. This applies to companies that allow users to install and leverage non-corporate products + + +Reasons for OffScrub to be used with Office 2013 CR2 to Office 2016 C2R migrations: +- Office 2013 Icons on task bar are not removed. + + +- Shortcut Icons are not removed. + + +- Upgrade process doesn't always do a clean uninstall. Removal of the bits with Offscrub typically ensures a clean uninstall. + + +- Quicker than native process. + + +- Does not touch the User Hive + + +- Has verbose logging. + + +- Can remove Project and Visio and Office in one command. + + +- Removes legacy addon products such a Visio Viewer, etc. + + + diff --git a/DeployOffice/best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md b/DeployOffice/best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md new file mode 100644 index 000000000..1d0d5d33c --- /dev/null +++ b/DeployOffice/best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md @@ -0,0 +1,56 @@ +--- +title: Best practices guide for deploying Office 365 ProPlus in the enterprise +ms.prod: OFFICE365 +ms.assetid: 31a384ca-650c-4265-b76c-a87b414fd8b8 +--- + + +# Best practices guide for deploying Office 365 ProPlus in the enterprise + +The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. The guide is recommended for IT Pros who are familiar with running enterprise-level software deployment projects. + + + + + +## Best Practices for deploying Office 365 ProPlus + + ** [Best practices for assessing your infrastructure](best-practices-for-assessing-your-infrastructure.md)** Key infrastructure assessment components and app compatibility discovery processes. + + + + ** [Best practices for planning your deployment of Office 365 ProPlus](best-practices-for-planning-your-deployment-of-office-365-proplus.md)** What to consider when creating a deployment plan. + + + + ** [Best practices for deploying Office 365 ProPlus](best-practices-for-deploying-office-365-proplus.md)** The preferred deployment options and high-level descriptions of the architecture components. + + + + ** [Best practices for managing updates in Office 365 ProPlus](best-practices-for-managing-updates-in-office-365-proplus.md)** Details on channel management in Office 365 ProPlus. + + + + ** [Best practices: Recommended deployment scenarios](best-practices-recommended-deployment-scenarios.md)** The three preferred deployment options for delivering Office 365 ProPlus to client devices. + + + + ** [Best practices for implementing group policy](best-practices-for-implementing-group-policy.md)** The recommended Group Policy settings for deploying Office 365 ProPlus. + + + + +## See also + + +#### Other Resources + + + + + + [Best practices: Recommended deployment scenarios](best-practices-recommended-deployment-scenarios.md) + + + + [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) diff --git a/DeployOffice/best-practices-install-xml-files-for-cloud-managed.md b/DeployOffice/best-practices-install-xml-files-for-cloud-managed.md new file mode 100644 index 000000000..479db966a --- /dev/null +++ b/DeployOffice/best-practices-install-xml-files-for-cloud-managed.md @@ -0,0 +1,131 @@ +--- +title: Best practices Install XML files for cloud managed +ms.prod: OFFICE365 +ms.assetid: 68113166-4e85-45da-8963-ad65d3031ade +--- + + +# Best practices: Install XML files for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Cloud Managed* needs install XML files for the following packages: +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit
|1 language
| +|Office 365 ProPlus - Deferred Channel - Shared Computers - 32-bit
|1 language
| +|Office 365 ProPlus - First Release Deferred Channel - Desktops - 32-bit
|1 language
| + + *Cloud Managed* expects Current Channel users to self-provision and self-manage. All applications will be included in the install. +## Example install XML files + +The following are the *Cloud Managed* example install XML files for configuring and installing Office 365 clients. + + + + +### Office 365 ProPlus - Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + + +``` + + **XML install file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - Deferred Channel - Desktops - Shared Computer Activation - 32-bit + + +``` + + + + + + + + + + + + +``` + + **XML install file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|SharedComputerLicensing Value="1"
|Places Office 365 ProPlus into Shared Computer Activation mode
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - First Release for Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + + +``` + + **XML install file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + diff --git a/DeployOffice/best-practices-install-xml-files-for-enterprise-managed.md b/DeployOffice/best-practices-install-xml-files-for-enterprise-managed.md new file mode 100644 index 000000000..ea1178b9a --- /dev/null +++ b/DeployOffice/best-practices-install-xml-files-for-enterprise-managed.md @@ -0,0 +1,477 @@ +--- +title: Best practices Install XML files for enterprise managed +ms.prod: OFFICE365 +ms.assetid: be130915-09ab-4303-b436-ae7b84266e28 +--- + + +# Best practices: Install XML files for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Enterprise Managed* needs install XML files for the following packages: +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - North America Region
|3 languages
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - LATAM Region
|3 languages
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - AsiaPAC Region
|8 languages
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - EU Region
|8 languages
| +|Project Pro (VL) - Deferred Channel - Desktops - 32-bit
|1 language
| +|Project Pro (VL) - Deferred Channel - Desktops - 32-bit
|1 language
| +|Office 365 ProPlus - Deferred Channel - VDI/Shared Computers - 32-bit - All regions
|17 languages
| +|Individual languages - Deferred Channel - Desktops 32-bit
|17 languages
| +|Office 365 ProPlus - Deferred Channel - Desktops - 64-bit
|1 language
| +|Office 365 ProPlus - First Release Deferred Channel - Desktops - 32-bit
|1 language
| +|Project Pro (VL)- First Release for Deferred Channel - Desktops - 32-bit
|1 language
| +|Visio Pro (VL) - First Release for Deferred Channel - Desktops - 32-bit
|1 language
| + + *Enterprise Managed* expects Current Channel users to self-provision and self-manage. OneDrive for Business will be excluded from the installation in all cases. +## Example install XML files + +The following are the *Enterprise Managed* example install XML files for configuring and installing Office 365 clients. + + + + +### Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - North America Region + + +``` + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|Language ID="ii-cc"
|The additional languages being installed for Office 365 ProPlus
| +|ExcludeApp ID="Groove"
|Excludes OneDrive from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - LATAM Region + + +``` + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|Language ID="ii-cc"
|The additional languages being installed for Office 365 ProPlus
| +|ExcludeApp ID="Groove"
|Excludes OneDrive from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - AsiaPAC Region + + +``` + +Configuration> + + + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="zh-cn"
|The default language being installed for Office 365 ProPlus
| +|Language ID="ii-cc"
|The additional languages being installed for Office 365 ProPlus
| +|ExcludeApp ID="Groove"
|Excludes OneDrive from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - EU region + + +``` + + + + + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="cs-cz"
|The default language being installed for Office 365 ProPlus
| +|Language ID="ii-cc"
|The additional languages being installed for Office 365 ProPlus
| +|ExcludeApp ID="Groove"
|Excludes OneDrive from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Project Pro (VL) - Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="ProjectProXVolume"
|SKU of Office 365 Project Pro being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 Project Pro
| +|Display Level="None"
|Hides the UI when installing Office 365 Project Pro
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Visio Pro (VL) - Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="VisioProXVolume"
|SKU of Office 365 Visio Pro being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 Visio Pro
| +|Display Level="None"
|Hides the UI when installing Office 365 Visio Pro
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - Deferred Channel - VDI/Shared Computer Activation - 32-bit + + +``` + + + + + + + + + + + + + + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|Language ID="ii-cc"
|The additional languages being installed for Office 365 ProPlus
| +|ExcludeApp ID="Groove"
|Excludes OneDrive from Office 365 ProPlus installation
| +|SharedComputerLicensing Value="1"
|Places Office 365 ProPlus into Shared Computer Activation mode
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Individual languages Deferred Channel - Desktops 32-bit + + +``` + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="LanguagePack"
|SKU of language pack being installed
| +|Language ID="es-es"
|The default language being installed for Office 365 ProPlus
| + + +### Office 365 ProPlus - Deferred Channel - Desktops - 64-Bit + + +``` + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="64"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|ExcludeApp ID="Groove"
|Excludes OneDrive from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - First Release for Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|ExcludeApp ID="Groove"
|Excludes OneDrive from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Project Pro (VL) - First Release for Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="ProjectProXVolume"
|SKU of Project Pro (VL) being installed
| +|Language ID="en-us"
|The default language being installed for Project Pro (VL)
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Project to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Visio Pro - First Release for Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="VisioProXVolume"
|SKU of Visio Pro (VL) being installed
| +|Language ID="en-us"
|The default language being installed for Visio Pro (VL)
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Visio to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + diff --git a/DeployOffice/best-practices-install-xml-files-for-locally-managed.md b/DeployOffice/best-practices-install-xml-files-for-locally-managed.md new file mode 100644 index 000000000..382317ae7 --- /dev/null +++ b/DeployOffice/best-practices-install-xml-files-for-locally-managed.md @@ -0,0 +1,334 @@ +--- +title: Best practices Install XML files for locally managed +ms.prod: OFFICE365 +ms.assetid: 3a3b98be-c33e-4ed5-8403-9cf71eccb904 +--- + + +# Best practices: Install XML files for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Locally Managed* needs install XML files for: the following packages: +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - CanAm Region
|2 languages
| +|Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - Germany
|1 language
| +|Project Pro - Deferred Channel - Desktops - 32-bit
|1 language
| +|Visio Pro - Deferred Channel - Desktops - 32-bit
|1 language
| +|Project Pro (VL) - Deferred Channel - Desktops - 32-bit
|1 language
| +|Project Pro (VL) - Deferred Channel - Desktops - 32-bit
|1 language
| +|Office 365 ProPlus - Deferred Channel - VDI/Shared Computers - 32-bit - All regions
|17 languages
| +|Individual languages - Deferred Channel - Desktops 32-bit
|3 languages
| +|Office 365 ProPlus - First Release Deferred Channel - Desktops - 32-bit
|1 language
| +|Project Pro (VL)- First Release for Deferred Channel - Desktops - 32-bit
|1 language
| +|Visio Pro (VL) - First Release for Deferred Channel - Desktops - 32-bit
|1 language
| + + *Locally Managed* expects Current Channel users to self-provision and self-manage. Access will be excluded from the installation in all cases. +## Example install XML files + +The following are the *Locally Managed* example install XML files for configuring and installing Office 365 clients. + + + + +### Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - CanAm Region + + +``` + + + + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|Language ID="fr-fr"
|The additional language being installed for Office 365 ProPlus
| +|ExcludeApp ID="Access"
|Excludes Access from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - Deferred Channel - Desktops - 32-bit - Germany + + +``` + + + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being installed
| +|Language ID="de-de"
|The default language being installed for Office 365 ProPlus
| +|ExcludeApp ID="Access"
|Excludes Access from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Project Pro - Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="ProjectProRetail"
|SKU of Office Project Pro being installed
| +|Language ID="en-us"
|The default language being installed for Project Pro
| +|Display Level="None"
|Hides the UI when installing Project Pro
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Visio Pro - Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="VisioProRetail"
|SKU of Office Visio Pro being installed
| +|Language ID="en-us"
|The default language being installed for Visio Pro
| +|Display Level="None"
|Hides the UI when installing Visio Pro
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Office 365 ProPlus - Deferred Channel - VDI/Shared Computer Activation - 32-bit + + +``` + + + + + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetaill"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|Language ID="ii-cc"
|The additional languages being installed for Office 365 ProPlus
| +|ExcludeApp ID="Access"
|Excludes Access from Office 365 ProPlus installation
| +|SharedComputerLicensing Value="1"
|Places Office 365 ProPlus into Shared Computer Activation mode
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Individual languages - Deferred Channel - Desktops 32-bit + + +``` + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="LanguagePack"
|SKU of language pack being installed
| +|Language ID="de-de"
|The language being installed for Office 365 ProPlus
| + + +### Office 365 ProPlus - First Release for Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="O365ProPlusRetaill"
|SKU of Office 365 ProPlus being installed
| +|Language ID="en-us"
|The default language being installed for Office 365 ProPlus
| +|ExcludeApp ID="Access"
|Excludes Access from Office 365 ProPlus installation
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the install of Office to shut down. Data loss may occur.
| +|Display Level="None"
|Hides the UI when installing Office 365 ProPlus
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Project Pro - First Release for Deferred Channel - Desktops - 32-bit + + +``` + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="ProjectProRetail"
|SKU of Office 365 Project Pro being installed
| +|Language ID="en-us"
|The default language being installed for Project Pro
| +|Display Level="None"
|Hides the UI when installing Project Pro
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + +### Visio Pro - First Release for Deferred Channel - Desktops 32-bit + + +``` + + + + + + + + + + +``` + + **XML download file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being installed
| +|Product ID="VisioProRetail"
|SKU of Office 365 Visio Pro being installed
| +|Language ID="en-us"
|The default language being installed for Visio Pro
| +|Display Level="None"
|Hides the UI when installing Visio Pro
| +|AcceptEULA="TRUE"
|Accept the License Agreement
| + + diff --git a/DeployOffice/best-practices-links-for-administration-education.md b/DeployOffice/best-practices-links-for-administration-education.md new file mode 100644 index 000000000..e133641b7 --- /dev/null +++ b/DeployOffice/best-practices-links-for-administration-education.md @@ -0,0 +1,28 @@ +--- +title: Best practices Links for administration education +ms.prod: OFFICE365 +ms.assetid: 278cea26-4657-45c1-aede-5365daa2f63c +--- + + +# Best practices: Links for administration education + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +The following table lists helpful videos for administrators who are new to Office UNRESOLVED_TOKEN_VAL(365) ProPlus: +||| +|:-----|:-----| +|**Title**
|**Location**
| +|Office UNRESOLVED_TOKEN_VAL(365) ProPlus Upgrade
(for Office 2013 to Office 2016)
| [https://mva.microsoft.com/en-US/training-courses/office-365-proplus-upgrade-14776?l=Zo4fEFjzB_6000115881](https://mva.microsoft.com/en-US/training-courses/office-365-proplus-upgrade-14776?l=Zo4fEFjzB_6000115881)
| +|Office UNRESOLVED_TOKEN_VAL(365) ProPlus Deployment Deep Dive
| [https://mva.microsoft.com/en-US/training-courses/office-365-proplus-deployment-deep-dive-14066](https://mva.microsoft.com/en-US/training-courses/office-365-proplus-deployment-deep-dive-14066)
| +|What really happens when there is a Service Outage
| [https://mva.microsoft.com/en-US/training-courses/what-really-happens-when-there-is-an-office-365-service-incident-and-whats-my-role-14085](https://mva.microsoft.com/en-US/training-courses/what-really-happens-when-there-is-an-office-365-service-incident-and-whats-my-role-14085)
| +|Tools and Tips for Administrating Office UNRESOLVED_TOKEN_VAL(365)
| [https://mva.microsoft.com/en-US/training-courses/tools-and-tips-for-administering-office-365-14083](https://mva.microsoft.com/en-US/training-courses/tools-and-tips-for-administering-office-365-14083)
| +|Office UNRESOLVED_TOKEN_VAL(365) ProPlus What's New in 2016 and Beyond
| [https://mva.microsoft.com/en-US/training-courses/office-365-proplus-whats-new-in-2016-and-beyond-14065?l=6k9rJAomB_9800115881](https://mva.microsoft.com/en-US/training-courses/office-365-proplus-whats-new-in-2016-and-beyond-14065?l=6k9rJAomB_9800115881)
| +|Managing Change in Office UNRESOLVED_TOKEN_VAL(365) Rapid Release World
| [https://mva.microsoft.com/en-US/training-courses/managing-change-in-an-office-365-rapid-release-world-14061?l=SaT0W4nmB_1400115881](https://mva.microsoft.com/en-US/training-courses/managing-change-in-an-office-365-rapid-release-world-14061?l=SaT0W4nmB_1400115881)
| +|Deploying Office UNRESOLVED_TOKEN_VAL(365) ProPlus
| [https://mva.microsoft.com/en-US/training-courses/deploying-office-365-proplus-9013](https://mva.microsoft.com/en-US/training-courses/deploying-office-365-proplus-9013)
| +|Solving Office UNRESOLVED_TOKEN_VAL(365) Client Deployment Scenarios
| [https://mva.microsoft.com/en-US/training-courses/solving-office-365-client-deployment-scenarios-9086?l=suttZBf4_2304984382](https://mva.microsoft.com/en-US/training-courses/solving-office-365-client-deployment-scenarios-9086?l=suttZBf4_2304984382)
| + + diff --git a/DeployOffice/best-practices-links-for-helpdesk-and-end-user-training.md b/DeployOffice/best-practices-links-for-helpdesk-and-end-user-training.md new file mode 100644 index 000000000..031723c25 --- /dev/null +++ b/DeployOffice/best-practices-links-for-helpdesk-and-end-user-training.md @@ -0,0 +1,160 @@ +--- +title: Best practices Links for helpdesk and end user training +ms.prod: OFFICE365 +ms.assetid: 80faf817-9559-459d-8e9c-e062b29fe9a3 +--- + + +# Best practices: Links for helpdesk and end user training + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +The following table lists helpful resources for end users who are new to Office UNRESOLVED_TOKEN_VAL(365) ProPlus. +||||| +|:-----|:-----|:-----|:-----| +|**Product**
|**Title**
|**Format**
|**Location**
| +|Outlook 2016 on Windows
|Learn to Setup first Outlook Account
|Video
| [https://support.office.com/en-us/article/Set-up-your-email-b44563f6-74ca-476d-aa0e-9b9ad0074d82?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Set-up-your-email-b44563f6-74ca-476d-aa0e-9b9ad0074d82?ui=en-US&rs=en-US&ad=US)
| +|Outlook 2016 on Windows
|Compose and Send Email
|Video
| [https://support.office.com/en-us/article/Video-Create-and-send-email-400d4d45-8e2d-46a2-8cb5-ddabf12489ed?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Create-and-send-email-400d4d45-8e2d-46a2-8cb5-ddabf12489ed?ui=en-US&rs=en-US&ad=US)
| +|Outlook 2016 on Windows
|Stop Sending attachments: Sharing with email
|Video
| [https://support.office.com/en-us/article/Stop-sending-attachments-Sharing-with-email-234b9758-3fc7-4883-b086-83ddc03cebc8?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Stop-sending-attachments-Sharing-with-email-234b9758-3fc7-4883-b086-83ddc03cebc8?ui=en-US&rs=en-US&ad=US)
| +|Outlook 2016 on Windows
|View Unread Emails
|Video
| [https://support.office.com/en-us/article/Video-View-email-9aa2285c-acee-41eb-89fc-b0630af0a886?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-View-email-9aa2285c-acee-41eb-89fc-b0630af0a886?ui=en-US&rs=en-US&ad=US)
| +|Outlook 2016 on Windows
|Reply to or forward an email message
|Video
| [https://support.office.com/en-us/article/Video-Reply-to-or-forward-email-72255538-5bcb-4be6-bede-c28014a5c951?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Reply-to-or-forward-email-72255538-5bcb-4be6-bede-c28014a5c951?ui=en-US&rs=en-US&ad=US)
| +|Outlook 2016 on Windows
|Search and Filter Email
|Video
| [https://support.office.com/en-us/article/Video-Search-and-filter-email-3e32b06d-a2d9-4a66-922f-78b77c41b97f?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Search-and-filter-email-3e32b06d-a2d9-4a66-922f-78b77c41b97f?ui=en-US&rs=en-US&ad=US)
| +|Outlook 2016 on Windows
|Add signatures to emails
|Video
| [https://support.office.com/en-us/article/Video-Add-signatures-to-emails-31fb24f9-e698-4789-b92a-f0e777f774ca?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Add-signatures-to-emails-31fb24f9-e698-4789-b92a-f0e777f774ca?ui=en-US&rs=en-US&ad=US)
| +|Outlook 2016 on Windows
|Outlook Quick Start Guide
|PDF
| [http://download.microsoft.com/download/5/E/7/5E7E239F-B465-4D39-888F-8A5CCEF7A8AD/OUTLOOK%202016%20QUICK%20START%20GUIDE.PDF](http://download.microsoft.com/download/5/E/7/5E7E239F-B465-4D39-888F-8A5CCEF7A8AD/OUTLOOK%202016%20QUICK%20START%20GUIDE.PDF)
| +|Outlook 2016 on Mac OS
|Outlook 2016 for Mac Basics
|PowerPoint
| [https://docs.com/OfficeTraining/6434/outlook-for-mac-2016-basics-training](https://docs.com/OfficeTraining/6434/outlook-for-mac-2016-basics-training)
Add an email account
Attach things to email
Create an email signature
Set up Automatic replies
Add email contacts
Work with your calendar
Work with tasks
| +|Outlook 2016 on Mac OS
|Office 2016 for Mac Quick Start Guides
|PDF
| [https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8](https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8)
| +|Outlook 2016 on Mac OS
|Use VoiceOver in Outlook 2106
|Article
| [https://support.office.com/en-us/article/Use-VoiceOver-in-Outlook-2016-for-Mac-13e59ff3-6da3-4d59-88d8-885a5dc9e90d](https://support.office.com/en-us/article/Use-VoiceOver-in-Outlook-2016-for-Mac-13e59ff3-6da3-4d59-88d8-885a5dc9e90d)
| +|Outlook 2016 on Mac OS
|Where is my Outbox
|Article
| [https://support.office.com/en-us/article/Where-s-my-Outbox-in-Outlook-2016-for-Mac-5018fdd3-26b9-4fa0-b111-b656cdb5afae?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Where-s-my-Outbox-in-Outlook-2016-for-Mac-5018fdd3-26b9-4fa0-b111-b656cdb5afae?ui=en-US&rs=en-US&ad=US)
| +|Outlook 2016 on Mac OS
|Share your calendar
|Article
| [https://support.office.com/en-us/article/Share-your-calendar-in-Outlook-2016-for-Mac-1534a3e9-b6d1-420f-88ae-89abb17ad57e?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Share-your-calendar-in-Outlook-2016-for-Mac-1534a3e9-b6d1-420f-88ae-89abb17ad57e?ui=en-US&rs=en-US&ad=US)
| +|Outlook on the Web
|Welcome to Outlook.com
|Article
| [https://support.office.com/en-us/article/Welcome-to-Outlook-com-28bac523-cc12-4b52-b13c-4436cd181edc?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Welcome-to-Outlook-com-28bac523-cc12-4b52-b13c-4436cd181edc?ui=en-US&rs=en-US&ad=US)
| +|Outlook on the Web
|Using email in Outlook on the web and Outlook.com
|Article
| [https://support.office.com/en-us/article/Using-email-in-Outlook-on-the-web-and-Outlook-com-a5806e13-2fdc-4b79-a7d6-940a54c48121?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Using-email-in-Outlook-on-the-web-and-Outlook-com-a5806e13-2fdc-4b79-a7d6-940a54c48121?ui=en-US&rs=en-US&ad=US)
Create and send a new message
Spell-check an email
Reply, reply all, or forward an email message
Create a new email folder
Search for a piece of mail
Work with draft messages
Archive old email messages
Delete email or recover deleted items
Sign Out of Outlook
| +|Outlook on Android
|Get the app
|Link
| [https://play.google.com/store/apps/details?id=com.microsoft.office.outlook](https://play.google.com/store/apps/details?id=com.microsoft.office.outlook)
| +|Outlook on Android
|Setup email on an Android phone or tablet
|Article
| [https://support.office.com/en-us/article/Set-up-email-in-the-Outlook-for-Android-app-886db551-8dfa-4fd5-b835-f8e532091872?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Set-up-email-in-the-Outlook-for-Android-app-886db551-8dfa-4fd5-b835-f8e532091872?ui=en-US&rs=en-US&ad=US)
| +|Outlook on iOS
|Get the app
|Link
| [https://itunes.apple.com/app/id951937596](https://itunes.apple.com/app/id951937596)
| +|Outlook on iOS
|Set up email in Outlook for iOS mobile app
|Article
| [https://support.office.com/en-us/article/Set-up-email-in-Outlook-for-iOS-mobile-app-b2de2161-cc1d-49ef-9ef9-81acd1c8e234?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Set-up-email-in-Outlook-for-iOS-mobile-app-b2de2161-cc1d-49ef-9ef9-81acd1c8e234?ui=en-US&rs=en-US&ad=US)
| +|Outlook on Windows Phone
|Setup email on Windows Phone
|Article
| [https://support.office.com/en-us/article/Set-up-email-on-Windows-Phone-181a112a-be92-49ca-ade5-399264b3d417](https://support.office.com/en-us/article/Set-up-email-on-Windows-Phone-181a112a-be92-49ca-ade5-399264b3d417)
| +|Word 2016 on Windows
|Explore the document gallery
|Article
| [https://support.office.com/en-us/article/Explore-Word-2016-eb385404-cb97-4b41-b2aa-1c18d05cd383?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Explore-Word-2016-eb385404-cb97-4b41-b2aa-1c18d05cd383?ui=en-US&rs=en-US&ad=US)
| +|Word 2016 on Windows
|Create a document in Word 2016
|Video
| [https://support.office.com/en-us/article/Create-a-document-in-Word-2016-f01a7977-3942-4daa-b651-23cc06a0054b?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Create-a-document-in-Word-2016-f01a7977-3942-4daa-b651-23cc06a0054b?ui=en-US&rs=en-US&ad=US)
| +|Word 2016 on Windows
|Format a document in Word 2016
|Video
| [https://support.office.com/en-us/article/Format-a-document-in-Word-2016-780772c6-9506-4081-afd1-aff9aab19f5f?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Format-a-document-in-Word-2016-780772c6-9506-4081-afd1-aff9aab19f5f?ui=en-US&rs=en-US&ad=US)
| +|Word 2016 on Windows
|Insert Items in a Word 2106 document
|Video
| [https://support.office.com/en-us/article/Insert-items-in-a-Word-2016-document-5c967406-a472-498b-a2e3-cdd5f0d5c50a?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Insert-items-in-a-Word-2016-document-5c967406-a472-498b-a2e3-cdd5f0d5c50a?ui=en-US&rs=en-US&ad=US)
| +|Word 2016 on Windows
|Add headers and footers and change page numbers in Word 2016
|Video
| [https://support.office.com/en-us/article/Add-headers-and-footers-and-change-page-numbers-in-Word-2016-f4875508-bb0c-498d-a79b-540160a7a85f?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Add-headers-and-footers-and-change-page-numbers-in-Word-2016-f4875508-bb0c-498d-a79b-540160a7a85f?ui=en-US&rs=en-US&ad=US)
| +|Word 2016 on Windows
|Save a document in Word 2016
|Article
| [https://support.office.com/en-us/article/Save-a-document-in-Word-2016-78c23f64-2791-4137-903d-ab0bb7a9007a?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Save-a-document-in-Word-2016-78c23f64-2791-4137-903d-ab0bb7a9007a?ui=en-US&rs=en-US&ad=US)
| +|Word 2016 on Windows
|Word 2016 Quick Start Guide
|PDF
| [https://support.office.com/en-us/article/Office-2016-Quick-Starts-25f909da-3e76-443d-94f4-6cdf7dedc51e?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Office-2016-Quick-Starts-25f909da-3e76-443d-94f4-6cdf7dedc51e?ui=en-US&rs=en-US&ad=US)
| +|Word 2016 on Mac OS
|Word 2016 for Mac training
|PowerPoint
| [https://docs.com/OfficeTraining/1025/word-2016-for-mac-basics](https://docs.com/OfficeTraining/1025/word-2016-for-mac-basics)
| +|Word 2016 on Mac OS
|Word 2016 for Mac Quick Start Guide
|PDF
| [https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8](https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8)
| +|Word 2016 on Mac OS
|Word 2016 Mac Common Scenarios
|Article
| [https://support.office.com/en-us/article/Word-2016-for-Mac-Help-c3292414-89c0-46e5-82a7-d55a1720f3bd](https://support.office.com/en-us/article/Word-2016-for-Mac-Help-c3292414-89c0-46e5-82a7-d55a1720f3bd)
| +|Word on Android
|Getting Started with Word for Android Tablet
|Video
| [https://support.office.com/en-us/article/Video-Getting-started-with-Word-for-Android-tablet-1aaaa121-99a7-426d-af6a-ee1611002dca](https://support.office.com/en-us/article/Video-Getting-started-with-Word-for-Android-tablet-1aaaa121-99a7-426d-af6a-ee1611002dca)
| +|Word on Android
|Android Touch Guide
|Article
| [https://support.office.com/en-us/article/Word-for-Android-touch-guide-32b15209-5934-4b0e-a1c4-585cb70ac3fa](https://support.office.com/en-us/article/Word-for-Android-touch-guide-32b15209-5934-4b0e-a1c4-585cb70ac3fa)
| +|Word on iOS
|Log in to Office for the Ipad
|Video
| [https://support.office.com/en-us/article/Video-Log-in-to-Office-for-iPad-726ab177-888c-4f2e-a0d9-8fb5c5ef3a36?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Log-in-to-Office-for-iPad-726ab177-888c-4f2e-a0d9-8fb5c5ef3a36?ui=en-US&rs=en-US&ad=US)
| +|Word on iOS
|Open Files from the Cloud
|Video
| [https://support.office.com/en-us/article/Video-Open-files-from-the-cloud-in-Word-for-iPad-ac034c0b-26c3-475a-a462-a391e0fa0bf1?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Open-files-from-the-cloud-in-Word-for-iPad-ac034c0b-26c3-475a-a462-a391e0fa0bf1?ui=en-US&rs=en-US&ad=US)
| +|Word on iOS
|Open Email Attachments
|Video
| [https://support.office.com/en-us/article/Video-Open-email-attachments-in-Word-for-iPad-db02998d-76ba-414b-857e-85574718049b?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Open-email-attachments-in-Word-for-iPad-db02998d-76ba-414b-857e-85574718049b?ui=en-US&rs=en-US&ad=US)
| +|Word on iOS
|How saving works in Word for the iPad
|Video
| [https://support.office.com/en-us/article/Video-How-saving-works-in-Word-for-iPad-57fb4f11-86f4-4177-af51-e4155789453f?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-How-saving-works-in-Word-for-iPad-57fb4f11-86f4-4177-af51-e4155789453f?ui=en-US&rs=en-US&ad=US)
| +|Word on iOS
|Type in Word for the IPad
|Video
| [https://support.office.com/en-us/article/Video-Type-in-Word-for-iPad-b54b8e59-52d0-4cbd-895e-4564346d43bc?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Type-in-Word-for-iPad-b54b8e59-52d0-4cbd-895e-4564346d43bc?ui=en-US&rs=en-US&ad=US)
| +|Word on iOS
|Select stuff in Word for the iPad
|Video
| [https://support.office.com/en-us/article/Video-Select-stuff-in-Word-for-iPad-5a809aa6-aeda-4660-9732-e0e4740eb849?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Select-stuff-in-Word-for-iPad-5a809aa6-aeda-4660-9732-e0e4740eb849?ui=en-US&rs=en-US&ad=US)
| +|Word on iOS
|How to print in Word for iPad
|Video
| [https://support.office.com/en-us/article/Video-How-to-print-in-Word-for-iPad-ce4ce819-126f-4fa0-a2dc-725252a602dd?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-How-to-print-in-Word-for-iPad-ce4ce819-126f-4fa0-a2dc-725252a602dd?ui=en-US&rs=en-US&ad=US)
| +|Word on iOS
|Word for iPhone touch guide
|Article
| [https://support.office.com/en-us/article/Word-for-iPhone-touch-guide-0a154e7f-14ee-46f1-a4c2-07c2017151b6](https://support.office.com/en-us/article/Word-for-iPhone-touch-guide-0a154e7f-14ee-46f1-a4c2-07c2017151b6)
| +|Word on Windows Phone
|Use Word Mobile for Windows Phone
|Article
| [https://support.office.com/en-us/article/Use-Word-Mobile-for-Windows-Phone-3fe718ee-e8a6-40b0-8420-b3520c25c411](https://support.office.com/en-us/article/Use-Word-Mobile-for-Windows-Phone-3fe718ee-e8a6-40b0-8420-b3520c25c411)
| +|Excel 2016 on Windows
|What is Excel?
|Video
| [https://support.office.com/en-us/article/Video-What-is-Excel-842fb550-07cb-42d1-9a9f-c55789efed57?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-What-is-Excel-842fb550-07cb-42d1-9a9f-c55789efed57?ui=en-US&rs=en-US&ad=US)
| +|Excel 2016 on Windows
|Create a workbook
|Video
| [https://support.office.com/en-us/article/Video-Create-a-workbook-82e9eab2-2e4e-463a-baa5-669b6c8ac543?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Create-a-workbook-82e9eab2-2e4e-463a-baa5-669b6c8ac543?ui=en-US&rs=en-US&ad=US)
| +|Excel 2016 on Windows
|Add and enter data
|Video
| [https://support.office.com/en-us/article/Video-Add-and-edit-data-2661a56a-196c-49c0-9dc3-ca785df9df9b?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Add-and-edit-data-2661a56a-196c-49c0-9dc3-ca785df9df9b?ui=en-US&rs=en-US&ad=US)
| +|Excel 2016 on Windows
|Create charts
|Video
| [https://support.office.com/en-us/article/Video-Create-charts-231c42d2-5e58-40e1-99f0-cbe618cfee1d?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Create-charts-231c42d2-5e58-40e1-99f0-cbe618cfee1d?ui=en-US&rs=en-US&ad=US)
| +|Excel 2016 on Windows
|Save your workbook
|Article
| [https://support.office.com/en-us/article/Save-your-workbook-90838b70-f005-4e52-bb45-0ce1f2786821?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Save-your-workbook-90838b70-f005-4e52-bb45-0ce1f2786821?ui=en-US&rs=en-US&ad=US)
| +|Excel 2016 on Windows
|Excel Quick start Guide
|PDF
| [https://support.office.com/en-us/article/Office-2016-Quick-Starts-25f909da-3e76-443d-94f4-6cdf7dedc51e?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Office-2016-Quick-Starts-25f909da-3e76-443d-94f4-6cdf7dedc51e?ui=en-US&rs=en-US&ad=US)
| +|Excel 2016 on Mac OS
|Excel 2016 for Mac Basics
|Article
| [https://docs.com/OfficeTraining/5255/excel-2016-for-mac-basics](https://docs.com/OfficeTraining/5255/excel-2016-for-mac-basics)
Learn your way around
Create a workbook
Save a workbook
| +|Excel 2016 on Mac OS
|What's new in Office 2016 for Mac?
|Video (monthly updates)
| [https://support.office.com/en-us/article/What-s-new-and-improved-in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/What-s-new-and-improved-in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?ui=en-US&rs=en-US&ad=US)
| +|Excel 2016 on Mac OS
|Excel 2016 Quick Start Guide
|PDF
| [https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8](https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8)
| +|Excel 2016 on Mac OS
|Excel 2016 Mac Common Scenarios
|Article
| [https://support.office.com/en-us/article/Excel-2016-for-Mac-Help-2010f16b-aec0-4da7-b381-9cc1b9b47745](https://support.office.com/en-us/article/Excel-2016-for-Mac-Help-2010f16b-aec0-4da7-b381-9cc1b9b47745)
| +|Excel on Android (Tablet)
|Excel for Android Tablets Help
|Article
| [https://support.office.com/en-us/article/Excel-for-Android-Tablets-Help-5f089a58-dfa5-4cdb-b93b-55deb638a469?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Excel-for-Android-Tablets-Help-5f089a58-dfa5-4cdb-b93b-55deb638a469?ui=en-US&rs=en-US&ad=US)
| +|Excel on Android (Tablet)
|Getting started with Excel for Android tablet
|Video
| [https://support.office.com/en-us/article/Video-Getting-started-with-Excel-for-Android-tablet-c5d5c135-0bc1-4aea-9b54-95a518dd0c11](https://support.office.com/en-us/article/Video-Getting-started-with-Excel-for-Android-tablet-c5d5c135-0bc1-4aea-9b54-95a518dd0c11)
| +|Excel on Android (Tablet)
|Log in to Office for Android
|Video
| [https://support.office.com/en-us/article/Video-Log-in-to-Office-for-Android-tablet-cb14504a-417f-4f64-b9c8-235e85621e8c?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Log-in-to-Office-for-Android-tablet-cb14504a-417f-4f64-b9c8-235e85621e8c?ui=en-US&rs=en-US&ad=US)
| +|Excel on Android (Tablet)
|Get Started with Excel Spreadsheet for Android Tablet
|Video
| [https://support.office.com/en-us/article/Video-Getting-started-with-Excel-for-Android-tablet-c5d5c135-0bc1-4aea-9b54-95a518dd0c11](https://support.office.com/en-us/article/Video-Getting-started-with-Excel-for-Android-tablet-c5d5c135-0bc1-4aea-9b54-95a518dd0c11)
| +|Excel on Android (Tablet)
|Excel for Android Touch Guide
|Article
| [https://support.office.com/en-us/article/Excel-for-Android-touch-guide-aef977da-6adf-4724-b054-8ca4bb1d7afb](https://support.office.com/en-us/article/Excel-for-Android-touch-guide-aef977da-6adf-4724-b054-8ca4bb1d7afb)
| +|Excel on iOS
|Training Videos for Excel on iPad
|Video
| [https://support.office.com/en-us/article/Training-videos-for-Excel-for-iPad-8c2fb984-de3c-4988-a32d-d549b6c91810](https://support.office.com/en-us/article/Training-videos-for-Excel-for-iPad-8c2fb984-de3c-4988-a32d-d549b6c91810)
Log in to Office for the iPad
Open Files from the cloud
Open an email attachment
How saving works in Excel for iPad
Type in Excel for the iPad
Select stuff in the Excel for iPad
Print in Excel for the iPad
| +|Excel on iOS
|Type in Excel for iPad
|Video
| [https://support.office.com/en-us/article/Video-Type-in-Excel-for-iPad-1ebd2af3-40a3-4cfc-bfeb-bc62d9d37a77](https://support.office.com/en-us/article/Video-Type-in-Excel-for-iPad-1ebd2af3-40a3-4cfc-bfeb-bc62d9d37a77)
| +|Excel on iOS
|Excel for iPhone Help
|Article
| [https://support.office.com/en-us/article/Excel-for-iPhone-help-b367819b-05b4-4a56-ab1c-678da62e1fd3](https://support.office.com/en-us/article/Excel-for-iPhone-help-b367819b-05b4-4a56-ab1c-678da62e1fd3)
| +|Excel on iOS
|Excel for iPhone Touch Guide
|Article
| [https://support.office.com/en-us/article/Excel-for-iPhone-Touch-Guide-5b175ec6-5cde-48d9-a13f-226680953278](https://support.office.com/en-us/article/Excel-for-iPhone-Touch-Guide-5b175ec6-5cde-48d9-a13f-226680953278)
| +|Excel on Windows Phone
|Use Excel for Windows Phone
|Article
| [https://support.office.com/en-us/article/Use-Excel-Mobile-for-Windows-Phone-a39cc086-5230-46c5-bac5-8964bbc453f1](https://support.office.com/en-us/article/Use-Excel-Mobile-for-Windows-Phone-a39cc086-5230-46c5-bac5-8964bbc453f1)
| +|PowerPoint 2016 on Windows
|Explore PowerPoint 2016
|Video
| [https://support.office.com/en-us/article/Video-Explore-PowerPoint-2016-74d69873-993c-4618-87c9-98aa3adf11cf?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Explore-PowerPoint-2016-74d69873-993c-4618-87c9-98aa3adf11cf?ui=en-US&rs=en-US&ad=US)
| +|PowerPoint 2016 on Windows
|Insert Stuff into your presentation
|Video
| [https://support.office.com/en-us/article/Video-Insert-stuff-into-your-presentation-313b6793-bc76-4f43-bd69-a511dcd83bd3?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Insert-stuff-into-your-presentation-313b6793-bc76-4f43-bd69-a511dcd83bd3?ui=en-US&rs=en-US&ad=US)
| +|PowerPoint 2016 on Windows
|Save and share your presentation
|Video
| [https://support.office.com/en-us/article/Video-Save-and-share-your-presentation-b40d547f-a07d-48d2-bc60-ef3fb653ac22?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Save-and-share-your-presentation-b40d547f-a07d-48d2-bc60-ef3fb653ac22?ui=en-US&rs=en-US&ad=US)
| +|PowerPoint 2016 on Windows
|Presenting with PowerPoint
|Video
| [https://support.office.com/en-us/article/Video-Presenting-with-PowerPoint-edb122e7-2ef2-4361-a078-708c3b84022a?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-Presenting-with-PowerPoint-edb122e7-2ef2-4361-a078-708c3b84022a?ui=en-US&rs=en-US&ad=US)
| +|PowerPoint 2016 on Windows
|PowerPoint Quick start Guide
|PDF
| [https://support.office.com/en-us/article/Office-2016-Quick-Starts-25f909da-3e76-443d-94f4-6cdf7dedc51e?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Office-2016-Quick-Starts-25f909da-3e76-443d-94f4-6cdf7dedc51e?ui=en-US&rs=en-US&ad=US)
| +|PowerPoint on Mac OS
|PowerPoint 2016 for Mac Basics
|PowerPoint
| [https://docs.com/OfficeTraining/2082/powerpoint-2016-for-mac-basics](https://docs.com/OfficeTraining/2082/powerpoint-2016-for-mac-basics)
Getting Started
Add slides
Add content
Format content
Apply a different theme
Apply a different slide layout
Save your presentation
| +|PowerPoint on Mac OS
|What's new in Office 2016 for Mac
|Video (updated monthly)
| [https://support.office.com/en-us/article/What-s-new-and-improved-in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/What-s-new-and-improved-in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?ui=en-US&rs=en-US&ad=US)
| +|PowerPoint on Mac OS
|PowerPoint 2016 Mac Quick Start Guides
|PDF
| [https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8](https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8)
| +|PowerPoint on Mac OS
|PowerPoint 2016 for Mac Help
|Article
| [https://support.office.com/en-us/article/PowerPoint-2016-for-Mac-Help-89809457-4470-4f79-a4d6-835cd366f7d7](https://support.office.com/en-us/article/PowerPoint-2016-for-Mac-Help-89809457-4470-4f79-a4d6-835cd366f7d7)
| +|PowerPoint on Android
|PowerPoint for Android touch guide
|Article
| [https://support.office.com/en-us/article/PowerPoint-for-Android-touch-guide-7f2b68df-608f-428b-958b-5a165fb109ce](https://support.office.com/en-us/article/PowerPoint-for-Android-touch-guide-7f2b68df-608f-428b-958b-5a165fb109ce)
| +|PowerPoint on Android
|Getting Started with PowerPoint for Android Tablet
|Video
| [https://support.office.com/en-us/article/Video-Getting-started-with-PowerPoint-for-Android-tablet-1ca4c589-217b-4762-ae20-d1877555b8c1](https://support.office.com/en-us/article/Video-Getting-started-with-PowerPoint-for-Android-tablet-1ca4c589-217b-4762-ae20-d1877555b8c1)
| +|PowerPoint on Android
|Use an external keyboard with PowerPoint for Android
|Article
| [https://support.office.com/en-us/article/Use-an-external-keyboard-with-PowerPoint-for-Android-8f4abc4e-afb2-4eb7-be9f-73b7f928b336](https://support.office.com/en-us/article/Use-an-external-keyboard-with-PowerPoint-for-Android-8f4abc4e-afb2-4eb7-be9f-73b7f928b336)
| +|PowerPoint on iOS
|Training videos for PowerPoint for the iPad
|Video
| [https://support.office.com/en-us/article/Training-videos-for-PowerPoint-for-iPad-d59b27f6-28cb-47f3-ab85-f3de1e7bbf87](https://support.office.com/en-us/article/Training-videos-for-PowerPoint-for-iPad-d59b27f6-28cb-47f3-ab85-f3de1e7bbf87)
Log in to Office for iPad
Open a file from the cloud
Open email attachments
How saving works in PowerPoint for iPad
Type in PowerPoint for iPad
Select stuff in PowerPoint for iPad
How to print in PowerPoint for the iPad
Run a Slideshow in PowerPoint for iPad
Projecting your slideshow to a screen
| +|PowerPoint on iOS
|PowerPoint for iPhone Help
|Article
| [https://support.office.com/en-us/article/PowerPoint-for-iPhone-Help-754fcb37-783b-4e8a-afca-edb900221b8b](https://support.office.com/en-us/article/PowerPoint-for-iPhone-Help-754fcb37-783b-4e8a-afca-edb900221b8b)
| +|PowerPoint on iOS
|PowerPoint for iPad touch Guide
|Article
| [https://support.office.com/en-us/article/PowerPoint-for-iPad-touch-guide-bbc7cfc1-6fb0-4579-a19a-de7b4ff10478](https://support.office.com/en-us/article/PowerPoint-for-iPad-touch-guide-bbc7cfc1-6fb0-4579-a19a-de7b4ff10478)
| +|PowerPoint on Windows Phone
|Use PowerPoint for Windows Phone
|Article
| [https://support.office.com/en-us/article/Use-PowerPoint-Mobile-for-Windows-Phone-da9ff3b1-0278-454b-8796-e75ce3ce5738](https://support.office.com/en-us/article/Use-PowerPoint-Mobile-for-Windows-Phone-da9ff3b1-0278-454b-8796-e75ce3ce5738)
| +|OneNote for Windows
|What is OneNote?
|Video
| [https://support.office.com/en-us/article/What-is-OneNote-be6cc6cc-3ca7-4f46-8876-5000f013c563?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/What-is-OneNote-be6cc6cc-3ca7-4f46-8876-5000f013c563?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Use OneNote in the Cloud
|Article
| [https://support.office.com/en-us/article/Use-OneNote-in-the-cloud-54fcce99-65b6-4501-ab96-27c30a176139?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Use-OneNote-in-the-cloud-54fcce99-65b6-4501-ab96-27c30a176139?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Getting Started with OneNote and notebooks
|Article
| [https://support.office.com/en-us/article/Get-started-with-OneNote-and-notebooks-4beb2128-51d9-4531-a4e0-078f605bbfea?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Get-started-with-OneNote-and-notebooks-4beb2128-51d9-4531-a4e0-078f605bbfea?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Add section and pages
|Article
| [https://support.office.com/en-us/article/Add-sections-and-pages-b041747d-f29c-4cd3-a52e-f835ee315660?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Add-sections-and-pages-b041747d-f29c-4cd3-a52e-f835ee315660?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Maximize your pages
|Article
| [https://support.office.com/en-us/article/Maximize-your-pages-d57f386d-38de-4bd9-91bc-6820a3988bed?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Maximize-your-pages-d57f386d-38de-4bd9-91bc-6820a3988bed?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Take Notes
|Article
| [https://support.office.com/en-us/article/Take-notes-2f9f2dac-57ce-4836-ba8e-fdbf525a52ab?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Take-notes-2f9f2dac-57ce-4836-ba8e-fdbf525a52ab?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Create a Quick Note
|Article
| [https://support.office.com/en-us/article/Create-a-Quick-Note-d7c202c5-c8e5-4a47-8645-a7ba29c26baa?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Create-a-Quick-Note-d7c202c5-c8e5-4a47-8645-a7ba29c26baa?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Clip from the web
|Article
| [https://support.office.com/en-us/article/Clip-from-the-Web-b503dc7e-f320-4d7a-8546-1fb31123c308](https://support.office.com/en-us/article/Clip-from-the-Web-b503dc7e-f320-4d7a-8546-1fb31123c308)
| +|OneNote for Windows
|Record audio
|Article
| [https://support.office.com/en-us/article/Record-audio-d69dcbfe-1fd7-4930-9564-bbd83099e2c4?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Record-audio-d69dcbfe-1fd7-4930-9564-bbd83099e2c4?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Capture the screen
|Article
| [https://support.office.com/en-us/article/Capture-the-screen-c763fc05-7bd8-4020-aebb-e0b054149d94?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Capture-the-screen-c763fc05-7bd8-4020-aebb-e0b054149d94?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Insert a picture
|Article
| [https://support.office.com/en-us/article/Insert-a-picture-56292764-e25d-4712-91e6-f51c6a22453e?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Insert-a-picture-56292764-e25d-4712-91e6-f51c6a22453e?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Copy text from an image
|Article
| [https://support.office.com/en-us/article/Copy-text-from-an-image-0ab3ecd7-57e5-4372-a5bd-e684cb52c150?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Copy-text-from-an-image-0ab3ecd7-57e5-4372-a5bd-e684cb52c150?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Insert a link
|Article
| [https://support.office.com/en-us/article/Insert-a-link-c505156d-148f-4160-8b00-27a6cb501d1d?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Insert-a-link-c505156d-148f-4160-8b00-27a6cb501d1d?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Create a table
|Article
| [https://support.office.com/en-us/article/Create-a-table-211cf0fe-2116-4af8-92e8-608161494d66?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Create-a-table-211cf0fe-2116-4af8-92e8-608161494d66?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Sort a Table
|Article
| [https://support.office.com/en-us/article/Sort-a-table-03f6e2c8-6482-470e-9670-343fa18a8d48?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Sort-a-table-03f6e2c8-6482-470e-9670-343fa18a8d48?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Convert a table to Excel
|Article
| [https://support.office.com/en-us/article/Convert-a-table-to-Excel-a24c39e2-32b6-4366-ad21-537e2a1675e8?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Convert-a-table-to-Excel-a24c39e2-32b6-4366-ad21-537e2a1675e8?ui=en-US&rs=en-US&ad=US)
| +|OneNote for Windows
|Quick Start Guide for OneNote
|PDF
| [https://support.office.com/en-us/article/Office-2016-Quick-Starts-25f909da-3e76-443d-94f4-6cdf7dedc51e?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Office-2016-Quick-Starts-25f909da-3e76-443d-94f4-6cdf7dedc51e?ui=en-US&rs=en-US&ad=US)
| +|OneNote on Mac OS
|OneNote 2016 for Mac Basics
|PowerPoint
| [https://docs.com/OfficeTraining/1862/onenote-2016-for-mac-basics-training?c=3AM3U6](https://docs.com/OfficeTraining/1862/onenote-2016-for-mac-basics-training?c=3AM3U6)
What is OneNote?
Use OneNote in the cloud
Get started with OneNote and notebooks
Add section and pages
Maximize your pages
Take notes
Record audio
Capture the screen
Insert pictures
Copy text from images
Insert links
Create tables
| +|OneNote on Mac OS
|What's new in Office 2016 for Mac?
|Article
| [https://support.office.com/en-us/article/What-s-new-and-improved-in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/What-s-new-and-improved-in-Office-2016-for-Mac-44d5a464-3051-41b0-b44e-c6cee569f545?ui=en-US&rs=en-US&ad=US)
| +|OneNote on Mac OS
|OneNote Quick Start Guide
|PDF
| [https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8](https://support.office.com/en-us/article/Office-2016-for-Mac-Quick-Start-Guides-5bccb480-0e5b-4b51-b072-66d3793ccad8)
| +|OneNote on Mac OS
|Get started with OneNote 2016 for Mac
|Article
| [https://support.office.com/en-us/article/Get-started-with-OneNote-2016-for-Mac-d6bec487-285f-426e-be9d-58cb49eb1979](https://support.office.com/en-us/article/Get-started-with-OneNote-2016-for-Mac-d6bec487-285f-426e-be9d-58cb49eb1979)
OneNote Quick Start Guide
Watch a video about OneNote
Learn basic tasks in OneNote
Look up OneNote keyboard shortcuts
Check for OneNote updates
Enable Accessibility options in OneNote
Download OneNote for your iPhone and iPad
| +|OneNote on Mac OS
|Frequently Asked Questions about OneNote 2016 for Mac
|Article
| [https://support.office.com/en-us/article/Frequently-Asked-Questions-about-OneNote-2016-for-Mac-bf9bcd6a-b8ce-4d18-a11f-ed1f596df3ed](https://support.office.com/en-us/article/Frequently-Asked-Questions-about-OneNote-2016-for-Mac-bf9bcd6a-b8ce-4d18-a11f-ed1f596df3ed)
| +|OneNote on iOS
|How does OneNote for iPad work?
|Article
| [https://support.office.com/en-us/article/How-does-OneNote-for-iPad-work-808e6fc6-5ee8-4095-ae4c-b6ca8b9451a9](https://support.office.com/en-us/article/How-does-OneNote-for-iPad-work-808e6fc6-5ee8-4095-ae4c-b6ca8b9451a9)
| +|OneNote on iOS
|Common Scenarios
|Article
| [https://support.office.com/en-us/article/Microsoft-OneNote-Help-f44e5bcd-5203-4553-9de4-0c56e6500825?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Microsoft-OneNote-Help-f44e5bcd-5203-4553-9de4-0c56e6500825?ui=en-US&rs=en-US&ad=US)
| +|OneNote on iOS
|Sync the OneNote notebooks on your Mac or PC with your iPad or iPhone
|Article
| [https://support.office.com/en-us/article/Sync-the-OneNote-notebooks-on-your-Mac-or-PC-with-your-iPad-or-iPhone-7c1a5793-0e3a-4847-97d1-de66099e78dd?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Sync-the-OneNote-notebooks-on-your-Mac-or-PC-with-your-iPad-or-iPhone-7c1a5793-0e3a-4847-97d1-de66099e78dd?ui=en-US&rs=en-US&ad=US)
| +|OneNote on iOS
|Share content from other apps with OneNote for iPhone
|Article
| [https://support.office.com/en-us/article/Share-content-from-other-apps-with-OneNote-for-iPhone-or-iPad-f21123c3-2b5f-4fc6-bc75-62fecd284824?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Share-content-from-other-apps-with-OneNote-for-iPhone-or-iPad-f21123c3-2b5f-4fc6-bc75-62fecd284824?ui=en-US&rs=en-US&ad=US)
| +|OneNote on Windows Phone
|Use OneNote Mobile for Windows Phone
|Article
| [https://support.office.com/en-us/article/Use-OneNote-on-a-Windows-Phone-203dd6b0-240b-46bf-b65c-1f0834bc697a?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Use-OneNote-on-a-Windows-Phone-203dd6b0-240b-46bf-b65c-1f0834bc697a?ui=en-US&rs=en-US&ad=US)
| +|OneDrive Business for Windows
|What is OneDrive for Business
|Video
| [https://support.office.com/en-us/article/What-is-OneDrive-for-Business-187f90af-056f-47c0-9656-cc0ddca7fdc2](https://support.office.com/en-us/article/What-is-OneDrive-for-Business-187f90af-056f-47c0-9656-cc0ddca7fdc2)
| +|OneDrive Business for Windows
|Store, Share and sync files for OneDrive for Business
|Article
| [https://support.office.com/en-us/article/Store-sync-and-share-your-work-files-OneDrive-for-Business-301817f6-9705-4525-ba3d-79082029b195](https://support.office.com/en-us/article/Store-sync-and-share-your-work-files-OneDrive-for-Business-301817f6-9705-4525-ba3d-79082029b195)
Dragging and dropping files to OneDrive for Business
[https://support.office.com/en-us/article/Dragging-and-dropping-files-to-OneDrive-for-Business-e2e0c53e-8707-4b9d-aa0d-d3cfcb792b72](https://support.office.com/en-us/article/Dragging-and-dropping-files-to-OneDrive-for-Business-e2e0c53e-8707-4b9d-aa0d-d3cfcb792b72)
Seeing your files from other devices
[https://support.office.com/en-us/article/Seeing-your-files-from-other-devices-fe48cf1e-d23c-4bb5-b274-f04e3d46539a](https://support.office.com/en-us/article/Seeing-your-files-from-other-devices-fe48cf1e-d23c-4bb5-b274-f04e3d46539a)
Saving and opening files
[https://support.office.com/en-us/article/Saving-and-opening-files-f3c50490-e402-44cd-81f1-d559fdc715fb](https://support.office.com/en-us/article/Saving-and-opening-files-f3c50490-e402-44cd-81f1-d559fdc715fb)
Syncing your files with your computer
[https://support.office.com/en-us/article/Syncing-your-files-with-your-computer-31e11d42-c3e4-443a-a5dd-9186bb6fdf3c](https://support.office.com/en-us/article/Syncing-your-files-with-your-computer-31e11d42-c3e4-443a-a5dd-9186bb6fdf3c)
Managing your files in OneDrive for Business
[https://support.office.com/en-us/article/Managing-your-files-in-OneDrive-for-Business-1c53e2c1-950e-46fa-8611-e07efcfb0565](https://support.office.com/en-us/article/Managing-your-files-in-OneDrive-for-Business-1c53e2c1-950e-46fa-8611-e07efcfb0565)
Sharing files with others
[https://support.office.com/en-us/article/Sharing-files-with-others-1441ccff-7d1d-4105-bf62-84b720149a28](https://support.office.com/en-us/article/Sharing-files-with-others-1441ccff-7d1d-4105-bf62-84b720149a28)
| +|OneDrive Business on Android phone or tablet
|Use OneDrive for Android
|Article
| [https://support.office.com/en-us/article/Use-OneDrive-for-Android-eee1d31c-792d-41d4-8132-f9621b39eb36?ui=en-US&amp;rs=en-US&amp;ad=US](https://support.office.com/en-us/article/Use-OneDrive-for-Android-eee1d31c-792d-41d4-8132-f9621b39eb36?ui=en-US&amp;rs=en-US&amp;ad=US)
| +|OneDrive Business for IPhone or iPad
|Working with your files on your iPhone or iPad
|Article
| [https://support.office.com/en-us/article/Use-OneDrive-on-iOS-08d5c5b2-ccc6-40eb-a244-fe3597a3c247?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Use-OneDrive-on-iOS-08d5c5b2-ccc6-40eb-a244-fe3597a3c247?ui=en-US&rs=en-US&ad=US)
| +|OneDrive Business for Windows Phone
|Use OneDrive for Business on your Windows phone
|Article
| [https://support.office.com/en-us/article/Use-OneDrive-for-Business-on-your-Windows-phone-6b0e1e05-2b8c-48fa-8820-7f25e2290fca?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Use-OneDrive-for-Business-on-your-Windows-phone-6b0e1e05-2b8c-48fa-8820-7f25e2290fca?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Introducing Skype for Business
|Video
| [https://support.office.com/en-us/article/Introducing-Skype-for-Business-e705627e-8e94-4bae-ac8b-4ccea5a9c4c0?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Introducing-Skype-for-Business-e705627e-8e94-4bae-ac8b-4ccea5a9c4c0?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Explore Skype for Business
|Video
| [https://support.office.com/en-us/article/Explore-Skype-for-Business-8b7aecb2-bdf0-436b-894f-31af502e912b?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Explore-Skype-for-Business-8b7aecb2-bdf0-436b-894f-31af502e912b?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Add a contact
|Video
| [https://support.office.com/en-us/article/Add-a-contact-f3f993dd-3cd8-49cb-a68c-6764ba23db4a?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Add-a-contact-f3f993dd-3cd8-49cb-a68c-6764ba23db4a?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Check a contact's presence and IM them
|Video
| [https://support.office.com/en-us/article/Check-a-contact-s-presence-and-IM-them-9d0b09c3-8e5e-4db3-8077-263a2b120fe8?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Check-a-contact-s-presence-and-IM-them-9d0b09c3-8e5e-4db3-8077-263a2b120fe8?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Change your picture
|Article
| [https://support.office.com/en-us/article/Change-your-picture-772fcd80-55a7-4196-bff7-1e3f172c8eb2?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Change-your-picture-772fcd80-55a7-4196-bff7-1e3f172c8eb2?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|See what's new in Skype for Business
|Article
| [https://support.office.com/en-us/article/See-what-s-new-in-Skype-for-Business-aba02d7e-c801-4a82-bccd-e7207240f612?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/See-what-s-new-in-Skype-for-Business-aba02d7e-c801-4a82-bccd-e7207240f612?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|What is Skype for Business
|Video
| [https://support.office.com/en-us/article/Video-What-is-Skype-for-Business-3a21eca4-434d-41f1-ab06-3d4a268573b7?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Video-What-is-Skype-for-Business-3a21eca4-434d-41f1-ab06-3d4a268573b7?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Make and receive a video call using Skype for Business
|Article
| [https://support.office.com/en-us/article/Make-and-receive-a-video-call-using-Skype-for-Business-abf62493-670f-4b0d-b2cf-fe03b49caf42?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Make-and-receive-a-video-call-using-Skype-for-Business-abf62493-670f-4b0d-b2cf-fe03b49caf42?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Use your desk phone to make a Skype for Business call
|Article
| [https://support.office.com/en-us/article/Use-your-desk-phone-to-make-a-Skype-for-Business-call-6a316c11-a05e-460c-b969-32ff0ad848e6?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Use-your-desk-phone-to-make-a-Skype-for-Business-call-6a316c11-a05e-460c-b969-32ff0ad848e6?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Set up a Skype for Business meeting in Outlook
|Video
| [https://support.office.com/en-us/article/Set-up-a-Skype-for-Business-meeting-in-Outlook-b8305620-d16e-4667-989d-4a977aad6556](https://support.office.com/en-us/article/Set-up-a-Skype-for-Business-meeting-in-Outlook-b8305620-d16e-4667-989d-4a977aad6556)
| +|Skype for Business for Windows
|Join a Skype for Business Meeting
|Video
| [https://support.office.com/en-us/article/Join-a-Skype-for-Business-meeting-3862be6d-758a-4064-a016-67c0febf3cd5](https://support.office.com/en-us/article/Join-a-Skype-for-Business-meeting-3862be6d-758a-4064-a016-67c0febf3cd5)
| +|Skype for Business for Windows
|Calling into a meeting on your mobile or other phone
|Article
| [https://support.office.com/en-us/article/Call-into-a-Skype-for-Business-meeting-on-your-mobile-or-other-phone-9fc51fc3-f201-49b1-b2d3-97fe6f9da238?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Call-into-a-Skype-for-Business-meeting-on-your-mobile-or-other-phone-9fc51fc3-f201-49b1-b2d3-97fe6f9da238?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business for Windows
|Setup an audio device for Skype for Business
|Video
| [https://support.office.com/en-us/article/Set-up-an-audio-device-for-Skype-for-Business-2533d929-9814-4349-8ae4-fca29246e2ff?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Set-up-an-audio-device-for-Skype-for-Business-2533d929-9814-4349-8ae4-fca29246e2ff?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business on Windows Phone
|Skype for Business is now on Windows Phone
|Article
| [https://support.office.com/en-us/article/Skype-for-Business-is-now-on-Windows-Phone-6f48a22d-b064-4f2f-beab-25b4744af5c4](https://support.office.com/en-us/article/Skype-for-Business-is-now-on-Windows-Phone-6f48a22d-b064-4f2f-beab-25b4744af5c4)
| +||Quick Start Guides about Skype for Business
|Article
| [https://support.office.com/en-us/article/Quick-Start-Guides-about-Skype-for-Business-bbb1dd15-3858-4081-9c28-8379020af66d?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Quick-Start-Guides-about-Skype-for-Business-bbb1dd15-3858-4081-9c28-8379020af66d?ui=en-US&rs=en-US&ad=US)
| +|Skype for Business on iOS
|Skype for Business is now on iOS
|Article
| [https://support.office.com/en-us/article/Skype-for-Business-is-now-on-iOS-1a2cf653-955b-4329-b289-db7a67d32bfd](https://support.office.com/en-us/article/Skype-for-Business-is-now-on-iOS-1a2cf653-955b-4329-b289-db7a67d32bfd)
| +|Skype for Business on Android
|Skype for Business is now on Android
|Article
| [https://support.office.com/en-us/article/Skype-for-Business-is-now-on-Android-59aacea2-cf3c-44c8-976a-9fd9353ba770](https://support.office.com/en-us/article/Skype-for-Business-is-now-on-Android-59aacea2-cf3c-44c8-976a-9fd9353ba770)
| +||What is Skype Meeting Broadcast?
|Article
| [https://support.office.com/en-us/article/What-is-a-Skype-Meeting-Broadcast-c472c76b-21f1-4e4b-ab58-329a6c33757d?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/What-is-a-Skype-Meeting-Broadcast-c472c76b-21f1-4e4b-ab58-329a6c33757d?ui=en-US&rs=en-US&ad=US)
| +||Schedule a Skype Meeting Broadcast Event
|Article
| [https://support.office.com/en-us/article/Schedule-a-Skype-Meeting-Broadcast-c3995bc9-4d32-4f75-a004-3bc5c477e553?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Schedule-a-Skype-Meeting-Broadcast-c3995bc9-4d32-4f75-a004-3bc5c477e553?ui=en-US&rs=en-US&ad=US)
| +||Manage a Skype Meeting Broadcast Event
|Article
| [https://support.office.com/en-us/article/Manage-a-Skype-Meeting-Broadcast-event-c7b98cbe-d168-4cf4-b87f-867707b25811](https://support.office.com/en-us/article/Manage-a-Skype-Meeting-Broadcast-event-c7b98cbe-d168-4cf4-b87f-867707b25811)
| +|Publisher 2016
|Basic Tasks in Publisher
|Article
| [https://support.office.com/en-us/article/Basic-tasks-in-Publisher-0e5ed249-1927-433f-a35c-63beb8216fcf?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Basic-tasks-in-Publisher-0e5ed249-1927-433f-a35c-63beb8216fcf?ui=en-US&rs=en-US&ad=US)
| +|Publisher 2016
|Make the Switch to Publisher
|Video
| [https://support.office.com/en-us/article/Make-the-switch-to-Publisher-2013-bb151ab4-fc6f-48a7-932e-778da48aa7a4](https://support.office.com/en-us/article/Make-the-switch-to-Publisher-2013-bb151ab4-fc6f-48a7-932e-778da48aa7a4)
| +|Publisher 2016
|Publisher Quick Start Guide
|PDF
| [https://support.office.com/en-us/article/Publisher-2013-Quick-Start-Guide-ea8023fe-5d0c-48e2-9401-b9d9b386dad8](https://support.office.com/en-us/article/Publisher-2013-Quick-Start-Guide-ea8023fe-5d0c-48e2-9401-b9d9b386dad8)
| +|Access 2016
|Basic Tasks for an Access desktop database
|Article
| [https://support.office.com/en-us/article/Basic-tasks-for-an-Access-desktop-database-5ddb8595-497c-4366-8327-ae79d2abdc9c?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Basic-tasks-for-an-Access-desktop-database-5ddb8595-497c-4366-8327-ae79d2abdc9c?ui=en-US&rs=en-US&ad=US)
Choose a template
Create a database from scratch
Add a table
Copy and paste data
Import or link to data
Organize data with the Table Analyzer
| +|Access 2016
|Introduction to tables
|Article
| [https://support.office.com/en-us/article/Introduction-to-tables-78ff21ea-2f76-4fb0-8af6-c318d1ee0ea7](https://support.office.com/en-us/article/Introduction-to-tables-78ff21ea-2f76-4fb0-8af6-c318d1ee0ea7)
| +|Access 2016
|Introduction to queries
|Article
| [https://support.office.com/en-US/article/Introduction-to-queries-2DADBA46-37F9-4CD6-828A-46502A66C250](https://support.office.com/en-US/article/Introduction-to-queries-2DADBA46-37F9-4CD6-828A-46502A66C250)
| +|Access 2016
|Create an Access form
|Article
| [https://support.office.com/en-us/article/Create-a-form-in-Access-5d550a3d-92e1-4f38-9772-7e7e21e80c6b?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Create-a-form-in-Access-5d550a3d-92e1-4f38-9772-7e7e21e80c6b?ui=en-US&rs=en-US&ad=US)
| +|Access 2016
|Introduction to reports in Access
|Article
| [https://support.office.com/en-us/article/Introduction-to-reports-in-Access-e0869f59-7536-4d19-8e05-7158dcd3681c](https://support.office.com/en-us/article/Introduction-to-reports-in-Access-e0869f59-7536-4d19-8e05-7158dcd3681c)
| +|Access 2016
|Protect your data with backup and restore process
|Article
| [https://support.office.com/en-us/article/Protect-your-data-with-backup-and-restore-processes-96539a81-5984-4d56-99ca-ee81f8d6356c](https://support.office.com/en-us/article/Protect-your-data-with-backup-and-restore-processes-96539a81-5984-4d56-99ca-ee81f8d6356c)
| +|Access 2016
|Access Quick Start Guide
|PDF
| [https://support.office.com/en-us/article/Access-2013-Quick-Start-Guide-aa404d26-ce42-4dd2-ac5e-51f9f39f7275](https://support.office.com/en-us/article/Access-2013-Quick-Start-Guide-aa404d26-ce42-4dd2-ac5e-51f9f39f7275)
| +|Office Mobile
|Office Mobile Quick Start Guides
|PDF
| [https://support.office.com/en-us/article/Office-Mobile-Quick-Start-Guides-c957c048-00fa-4793-8b40-4f564f9d58c6?ui=en-US&rs=en-US&ad=US](https://support.office.com/en-us/article/Office-Mobile-Quick-Start-Guides-c957c048-00fa-4793-8b40-4f564f9d58c6?ui=en-US&rs=en-US&ad=US)
Word Mobile
Excel Mobile
PowerPoint Mobile
OneNote Mobile
| + + diff --git a/DeployOffice/best-practices-locally-managed-scenario.md b/DeployOffice/best-practices-locally-managed-scenario.md new file mode 100644 index 000000000..9b7c28a9b --- /dev/null +++ b/DeployOffice/best-practices-locally-managed-scenario.md @@ -0,0 +1,42 @@ +--- +title: Best practices Locally managed scenario +ms.prod: OFFICE365 +ms.assetid: 48c953de-270e-4809-bd7d-93431159a047 +--- + + +# Best practices: Locally managed scenario + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Locally Managed represents medium to large organizations that may have offices in multiple countries, but are not considered to be globally distributed. Employees are generally located out of a centralized office in the country, with limited small offices. The work force is primarily leveraging newer productivity software, including some VDI, but the IT department does not have software distribution tools to manage client software. IT Administrators leverage a Distributed File System (DFS) and network shares to host installation packages that end users install, and utilize custom scripts and batch files for automated deployments for end users because the users do not have local admin rights. They do not have dedicated IT teams to specific products, and instead leverages shared teams that manage multiple technologies of the IT environment such as Active Directory Domain Services (AD DS), Active Directory Federation Services (AD FS), and Group Policy. +## + + ** [Best practices: Assessment for locally managed](best-practices-assessment-for-locally-managed.md)** Assessment results and success criteria for deploying Office 365 ProPlus. + + + + ** [Best practices: Planning for locally managed](best-practices-planning-for-locally-managed.md)** Creating a deployment plan is key when you migrate to Office 365 ProPlus. + + + + ** [Best practices: Deployment for locally managed](best-practices-deployment-for-locally-managed.md)** Guidance on how to deploy Office 365 ProPlus in the locally managed scenario. + + + + ** [Best practices: Management for locally managed](best-practices-management-for-locally-managed.md)** Common management tasks after deploying Office 365 ProPlus. + + + + + + + + + + + + diff --git a/DeployOffice/best-practices-management-for-cloud-managed.md b/DeployOffice/best-practices-management-for-cloud-managed.md new file mode 100644 index 000000000..e24521e90 --- /dev/null +++ b/DeployOffice/best-practices-management-for-cloud-managed.md @@ -0,0 +1,106 @@ +--- +title: Best practices Management for cloud managed +ms.prod: OFFICE365 +ms.assetid: a7f2fec4-75cb-49de-8e03-fc8e7a4691b5 +--- + + +# Best practices: Management for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Cloud Managed* wants to apply GPO management to their Office 365 ProPlus systems. They want to test specific scenarios that they are likely to encounter. +The items are: + + + + + +- Configure infrastructure + + +- License users + + +- Roll back a build + + +- Switch channels + + +- Configure policy + + - Group Policy for desktops + + + - Group Policy for OneDrive for Business + + + +## Configure infrastructure + +Office 365 is a cloud service; therefore, it requires Internet access. If you manage by URL, then updates are less frequent and typically only needed when new products or features are released. However, if you manage by IP address range, then changes occur more often. The following page should be referenced and subscribed to in an RSS feed: [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US). + + + + +## License users + +See [Assign licenses to user accounts with Office 365 PowerShell](https://technet.microsoft.com/en-us/library/dn771770.aspx). + + + + +## Roll back a build + + *Cloud Managed* can use a script that is hosted in a network share to perform a client rollback. For step by step guidance on performing a rollback using the **OfficeC2RClient.exe** update engine, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + +## Switch channels + +To change a user's channel membership, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + +## Configure policy + +We highly recommend that you periodically check for new GPO templates. As new Office features are rolled out, GPOs are often updated and new Office management GPOs are released. + + + + [Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool](https://www.microsoft.com/en-us/download/details.aspx?id=49030). + + + + +### Additional Group Policy for VDI + +An additional GPO should be considered for Outlook and Cached Mode for shared workstations. *Cloud Managed* has set the value to 5 days. + + + + +### Group Policy for OneDrive + +See [Administrative settings for the OneDrive for Business Next Generation Synch Client](https://support.office.com/en-us/article/Administrative-settings-for-the-new-OneDrive-sync-client-0ecb2cf5-8882-42b3-a6e9-be6bda30899c?ui=en-US&rs=en-US&ad=US). + + + + +## Cloud Managed Mac Client Updates + +Similar to Office 365 ProPlus, Microsoft provides new builds that contain application updates. This means that individual security or feature updates cannot be downloaded or installed. However, with a locally managed deployment, admins can select which applications to apply updates to. Office 2016 for Mac has a program named Microsoft AutoUpdate to automatically check for updates daily. Microsoft AutoUpdate can be configured to daily, weekly, monthly, or manually depending on preferences. + + + +Because *Cloud Managed* has a very limited Mac population, they should configure Microsoft AutoUpdate to download updates automatically to users' computers, and then have the users manually install the updates. + + + + diff --git a/DeployOffice/best-practices-management-for-enterprise-managed.md b/DeployOffice/best-practices-management-for-enterprise-managed.md new file mode 100644 index 000000000..f5547b030 --- /dev/null +++ b/DeployOffice/best-practices-management-for-enterprise-managed.md @@ -0,0 +1,193 @@ +--- +title: Best practices Management for enterprise managed +ms.prod: OFFICE365 +ms.assetid: 3afa6514-2df3-4c52-a746-40a6ea4feeaa +--- + + +# Best practices: Management for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Enterprise Managed* wants to apply GPO management to their Office 365 ProPlus systems and to test specific scenarios that they are likely to encounter. +The items are: + + + + + +- Configure infrastructure + + +- License users + + +- Add languages + + +- Remove languages + + +- Add OneDrive + + +- Roll back a build + + +- Switch channels + + +- Configure policy + + - Group Policy for desktops + + + - Additional Group Policy objects for VDI + + + - Group Policy for OneDrive for Business + + + +## Configure infrastructure and maintain network, ports, and protocols + +Office 365 is a cloud service; therefore, it requires Internet access. If you manage by URL, then updates are less frequent and typically only needed when new products or features are released. However, if you manage by IP address range, then changes occur more often. The following page should be referenced and subscribed to in an RSS feed: [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US). + + + + +## License users + +See [Assign licenses to user accounts with Office 365 PowerShell](https://technet.microsoft.com/en-us/library/dn771770.aspx). + + + + +## Add languages + +The **ProductID="LanguagePack"** element lets you add languages to an existing Office 365 client install without needing to know its existing configuration settings. + + + + +``` + + + + + + + + +``` + + +## Remove languages + +The **remove** element lets you remove a language from an existing Office 365 client install. + + + + +``` + + + + + + + + +``` + +OR + + + + + + +``` + + + + + + + + +``` + + +## Add OneDrive + +By removing the application exclude statement from the install XML file, it will include the application when it is re-run. + + + + +``` + + + + + + + + +``` + + +## Roll back a build + + *Enterprise Managed* can leverage their existing software distribution tool, System Center Configuration Manager, to perform a client rollback. For step-by-step guidance on performing a rollback using the OfficeC2RClient.exe update engine, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + +## Switch channels + +To change a user's channel membership, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + +## Configure policy + +We highly recommend that you periodically check for new GPO templates. As new Office features are rolled out, GPOs are often updated and new Office management GPOs are released. + + + + [Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool](https://www.microsoft.com/en-us/download/details.aspx?id=49030). + + + + +### Additional Group Policy for VDI + +An additional GPO should be considered for Outlook and Cached Mode for VDI. *Enterprise Managed* has set the value to 3 days. + + + + +### Group Policy for OneDrive + +See [Administrative settings for the OneDrive for Business Next Generation Synch Client](https://support.office.com/en-us/article/Administrative-settings-for-the-new-OneDrive-sync-client-0ecb2cf5-8882-42b3-a6e9-be6bda30899c?ui=en-US&rs=en-US&ad=US). + + + + +## Enterprise Managed Mac Client Updates + +Similar to Office 365 ProPlus, Microsoft provides new builds that contain application updates. This means that individual security or feature updates cannot be downloaded or installed. However, with a locally managed deployment, admins can select which applications to apply updates to. Office 2016 for Mac has a program named Microsoft AutoUpdate to automatically check for updates daily. Microsoft AutoUpdate can be configured to daily, weekly, monthly, or manually depending on preferences. + + + +Because *Enterprise Managed* has an existing Mac software distribution tool, Microsoft AutoUpdate should be configured to manually download the updates to the local network. They can then use the existing software distribution tool to deploy the updates to the Mac clients. + + + + diff --git a/DeployOffice/best-practices-management-for-locally-managed.md b/DeployOffice/best-practices-management-for-locally-managed.md new file mode 100644 index 000000000..d2b634483 --- /dev/null +++ b/DeployOffice/best-practices-management-for-locally-managed.md @@ -0,0 +1,193 @@ +--- +title: Best practices Management for locally managed +ms.prod: OFFICE365 +ms.assetid: ae2bcbfa-2c03-4f4d-b951-8352f079e3d0 +--- + + +# Best practices: Management for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Locally Managed* wants to apply some GPO management to their Office 365 ProPlus systems, as well as to test specific scenarios they are likely to encounter. +The items are: + + + + + +- Configure infrastructure + + +- License users + + +- Add languages + + +- Remove languages + + +- Add Access + + +- Roll back a build + + +- Switch channels + + +- Configure policy + + - Group Policy for desktops + + + - Additional Group Policy objects for VDI + + + - Group Policy for OneDrive for Business + + + +## Configure infrastructure and maintain network, ports, and protocols + +Office 365 is a cloud service; therefore, it requires Internet access. If you manage by URL, then updates are less frequent and typically only needed when new products or features are released. However, if you manage by IP address range, then changes occur more often. The following page should be referenced and subscribed to in an RSS feed: [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2?ui=en-US&rs=en-US&ad=US). + + + + +## License users + +See [Assign licenses to user accounts with Office 365 PowerShell](https://technet.microsoft.com/en-us/library/dn771770.aspx). + + + + +## Add languages + +The **ProductID="LanguagePack"** element lets you add languages to an existing Office 365 client install without needing to know its existing configuration settings. + + + + +``` + + + + + + + + +``` + + +## Remove languages + +The **remove** element lets you remove a language from an existing Office 365 client install. + + + + +``` + + + + + + + + +``` + +OR + + + + + + +``` + + + + + + + + +``` + + +## Add Access + +By removing the exclude statement from an application, it will include the application when re-run. If the newly run install XML file differs from the previous file used to install, the latest configuration settings are applied. + + + + +``` + + + + + + + + +``` + + +## Roll back a build + + *Locally Managed* can leverage a batch file or script that is hosted in their existing DFS structure to perform a client rollback. For step-by-step guidance on performing a rollback using the **OfficeC2RClient.exe** update engine, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + +## Switch channels + +To change a user's channel membership, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + +## Configure policy + +We highly recommend that you periodically check for new GPO templates. As new Office features are rolled out, GPOs are often updated and new Office management GPOs are released. + + + + [Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool](https://www.microsoft.com/en-us/download/details.aspx?id=49030). + + + + +### Additional Group Policy for VDI + +Additional GPO should be considered around Outlook and Cached Mode for shared computing. *Locally Managed* has set the value to 3 days. + + + + +### Group Policy for OneDrive + +See [Administrative settings for the OneDrive for Business Next Generation Synch Client](https://support.office.com/en-us/article/Administrative-settings-for-the-new-OneDrive-sync-client-0ecb2cf5-8882-42b3-a6e9-be6bda30899c?ui=en-US&rs=en-US&ad=US). + + + + +## Locally Managed Mac Client Updates + +Similar to Office 365 ProPlus, Microsoft provides new builds that contain application updates. This means that individual security or feature updates cannot be downloaded or installed. However, with a locally managed deployment, admins can select which applications to apply updates to. Office 2016 for Mac has a program named Microsoft AutoUpdate to automatically check for updates daily. Microsoft AutoUpdate can be configured to daily, weekly, monthly, or manually depending on preferences. + + + +Because *Locally Managed* has a small Mac population and no Mac software distribution tool, they should configure Microsoft AutoUpdate to download updates automatically to users' computers, and then have the users manually install the updates. + + + + diff --git a/DeployOffice/best-practices-managing-reference-material.md b/DeployOffice/best-practices-managing-reference-material.md new file mode 100644 index 000000000..c941301e6 --- /dev/null +++ b/DeployOffice/best-practices-managing-reference-material.md @@ -0,0 +1,89 @@ +--- +title: Best practices Managing reference material +ms.prod: OFFICE365 +ms.assetid: 6a135401-541b-458e-88ee-77cdf2cdd1c8 +--- + + +# Best practices: Managing reference material + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +The following articles provide deeper technical information on specific areas of the Manage phase that are not covered in depth in the customer scenarios. +## Frequently asked questions + + +### How does Office 365 ProPlus update? Does it leverage WSUS like previous Office versions did? How does it detect that updates are available? + + [Overview of the update process for Office 365 ProPlus](https://technet.microsoft.com/en-us/library/dn761709.aspx) + + + + +### How are update settings applied, and how are they managed? Can I use Group Policy to manage Office 365 ProPlus updates? + + [Choose how to apply updates to Office 365 ProPlus](https://technet.microsoft.com/en-us/library/dn761707.aspx) + + + + [Configure update settings for Office 365 ProPlus](https://technet.microsoft.com/en-us/library/dn761708.aspx) + + + + +### What update notifications will users see? + + [Reference: End-user update notifications for Office 365 ProPlus](https://technet.microsoft.com/en-us/library/dn761706.aspx) + + + + +### Can I switch update channels if needed? + + [Best practices: Channel management](best-practices-channel-management.md) + + + + +### How do I rollback to a previous build of Office 365 ProPlus if needed? + + [Best practices: Channel management](best-practices-channel-management.md) + + + + +### How do I implement Office 2016 ADMX and ADML files? + + [Managing Group Policy ADMX Files Step-by-Step Guide](https://technet.microsoft.com/en-us/library/cc709647%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396) + + + + +### How can I use System Center Configuration Manager 1602+ to manage Office 365 ProPlus updates? + + [Manage updates to Office 365 ProPlus with System Center Configuration Manager](https://technet.microsoft.com/en-us/library/mt628083.aspx) + + + + +### What change management should I be aware of with Office 365 ProPlus? + + [Change management for Office 365 clients](https://technet.microsoft.com/en-us/library/mt584223.aspx) + + + + +### What training or resources can I provide my IT teams, help desks, and end users to prepare for Office 365 ProPlus? + + [Best practices: Links for administration education](best-practices-links-for-administration-education.md) + + + + [Best practices: Links for helpdesk and end user training](best-practices-links-for-helpdesk-and-end-user-training.md) + + + + diff --git a/DeployOffice/best-practices-office-2016-mac-client-install-for-cloud-managed.md b/DeployOffice/best-practices-office-2016-mac-client-install-for-cloud-managed.md new file mode 100644 index 000000000..42af0e02b --- /dev/null +++ b/DeployOffice/best-practices-office-2016-mac-client-install-for-cloud-managed.md @@ -0,0 +1,26 @@ +--- +title: Best practices Office 2016 Mac client install for cloud managed +ms.prod: OFFICE365 +ms.assetid: 8e5133dc-6bd5-46e8-a39c-a544d8c7bcdd +--- + + +# Best practices: Office 2016 Mac client install for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +This article describes how *Cloud Managed* should design and deploy Office 2016 for Mac. Because they have a very limited Mac population, users should self-manage and self-service from the Office 365 portal. +## Office 365 portal deployment + +In a deployment situation where the user is downloading Office 2016 for Mac from the Office 365 software Portal, the following guidance is recommended: [Download and install or reinstall Office 365 or Office 2016 on your PC or Mac](https://support.office.com/en-us/article/Download-and-install-or-reinstall-Office-365-or-Office-2016-on-your-PC-or-Mac-4414eaaf-0478-48be-9c42-23adc4716658?ui=en-US&rs=en-US&ad=US). If Office installation fails, see [What to try if you can't install Office 2016 for Mac](https://support.office.com/en-us/article/What-to-try-if-you-can-t-install-Office-2016-for-Mac-5efba2b4-b1e6-4e5f-bf3c-6ab945d03dea?ui=en-US&rs=en-US&ad=US). + + + +For a user to install Office 2016 for Mac from the Office 365 portal, the user must have administrative privileges on their client device. + + + + diff --git a/DeployOffice/best-practices-office-2016-mac-client-install-for-enterprise-managed.md b/DeployOffice/best-practices-office-2016-mac-client-install-for-enterprise-managed.md new file mode 100644 index 000000000..059612dc7 --- /dev/null +++ b/DeployOffice/best-practices-office-2016-mac-client-install-for-enterprise-managed.md @@ -0,0 +1,51 @@ +--- +title: Best practices Office 2016 Mac client install for enterprise managed +ms.prod: OFFICE365 +ms.assetid: bf1d87b1-3398-45e7-86cc-109995f3af76 +--- + + +# Best practices: Office 2016 Mac client install for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +This article describes how *Enterprise Managed* designed and deployed Office 2016 for Mac. They will utilize their existing Mac software distribution tool to manage the Office 2016 for Mac deployment. Users are blocked from downloading Office 2016 for Mac from the Office 365 portal. +## Mac software distribution tool + +Because Office 2016 for Mac uses the Apple Installer technology for installation, *Enterprise Managed* can utilize their existing Mac software distribution tool such as Apple Remote Desktop or Casper JAMF Software Suite. Administrators control the software deployment and have centralized control over the deployment to monitor the Mac clients to see when they have received the software. For Enterprise Managed to deploy via their Mac software distribution tool, an Office 365 administrator should download the MPKG files from the Office 365 portal and create the deployment package. + + + + +> [!NOTE] +> Not all third-party Mac software distribution solutions support automatic account configuration. + + + + +For more information on deployment options for Office 2016 for Mac, see [Office 2016 for Mac Clients](http://www.deployoffice.com/preferred-practices/). + + + + +## Deployment preferences + +For guidance on deploying preferences to end users, see [Office 2016 for Mac Clients](http://www.deployoffice.com/preferred-practices/). + + + +Deployment preferences can overwrite the existing user preference settings. To remove Office for Mac 2011, [Troubleshoot Office 2011 for Mac issues by completely uninstalling before you reinstall](https://support.office.com/en-us/article/Troubleshoot-Office-2011-for-Mac-issues-by-completely-uninstalling-before-you-reinstall-ba8d8d13-0015-4eea-b60b-7719c2cedd17?ui=en-US&rs=en-US&ad=US&fromAR=1). + + + + +## Deployment languages + +All of the [supported languages](https://support.office.com/en-us/article/Supported-languages-in-Office-2016-for-Mac-26d30382-9fba-45dd-bf55-02ab03e2a7ec?ui=en-US&rs=en-US&ad=US) in Office 2016 for Mac are included and installed as part of the installer package .pkg file. Because there are no separate installer package files for each language, admins cannot choose which language to deploy to users. The language is selected during the installation based on the System Preferences settings. If none of the language settings are supported by Office, Office will install in English. + + + + diff --git a/DeployOffice/best-practices-office-2016-mac-client-install-for-locally-managed.md b/DeployOffice/best-practices-office-2016-mac-client-install-for-locally-managed.md new file mode 100644 index 000000000..a5ecb3e87 --- /dev/null +++ b/DeployOffice/best-practices-office-2016-mac-client-install-for-locally-managed.md @@ -0,0 +1,60 @@ +--- +title: Best practices Office 2016 Mac client install for locally managed +ms.prod: OFFICE365 +ms.assetid: 7b5e0fde-11ff-4cd1-aceb-59f4ba77ff49 +--- + + +# Best practices: Office 2016 Mac client install for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +This article describes how *Locally Managed* should design and deploy Office 2016 for Mac. Because they do not have a sizeable Mac population or Mac software distribution tools, the deployment should be managed from a local network share. +## Download Office 2016 for Mac to the local network + +Administrators can download the MPKG files from the Office 365 Portal Software Page and place the installation image in a network share. This strategy is useful for small scaled deployments and allows the user to control the installation of Office. Only users who are approved to install Office 2016 for Mac should have access to the network share. + + + + +1. Sign in to the Office 365 portal as an Office 365 administrator. + + +2. Go to the [Office 365 admin center](https://support.office.com/en-us/article/About-the-old-Office-365-admin-center-58537702-d421-4d02-8141-e128e3703547?ui=en-US&rs=en-US&ad=US) and select **Service Settings > User software**. + + +3. Under **Software for Mac**, expand **Office for Mac** and then click **Download** to begin downloading the installer package file. The installer package file is named **Microsoft_Office_2016_Installer.pkg**. + + +4. Put the **Microsoft_Office_2016_Installer.pkg** file in the network location. + + +5. Provide Mac end users with installation instructions + + +For more information on deployment options for Office 2016 for Mac, see [Office 2016 for Mac Clients](http://www.deployoffice.com/preferred-practices/). + + + + +## Deployment preferences + +For guidance on deploying preferences to end users, see [Office 2016 for Mac Clients](http://www.deployoffice.com/preferred-practices/). + + + +Deployment preferences can overwrite the existing user preference settings. To remove Office for Mac 2011, [Troubleshoot Office 2011 for Mac issues by completely uninstalling before you reinstall](https://support.office.com/en-us/article/Troubleshoot-Office-2011-for-Mac-issues-by-completely-uninstalling-before-you-reinstall-ba8d8d13-0015-4eea-b60b-7719c2cedd17?ui=en-US&rs=en-US&ad=US&fromAR=1). + + + + +## Deployment languages + +All of the [supported languages](https://support.office.com/en-us/article/Supported-languages-in-Office-2016-for-Mac-26d30382-9fba-45dd-bf55-02ab03e2a7ec?ui=en-US&rs=en-US&ad=US) in Office 2016 for Mac are included and installed as part of the installer package .pkg file. Because there are no separate installer package files for each language, admins cannot choose which language to deploy to users. The language is selected during the installation based on the System Preferences settings. If none of the language settings are supported by Office, Office will install in English. + + + + diff --git a/DeployOffice/best-practices-office-content-delivery-network-configuration-for-cloud-managed.md b/DeployOffice/best-practices-office-content-delivery-network-configuration-for-cloud-managed.md new file mode 100644 index 000000000..f9ddb1248 --- /dev/null +++ b/DeployOffice/best-practices-office-content-delivery-network-configuration-for-cloud-managed.md @@ -0,0 +1,75 @@ +--- +title: Best practices Office Content Delivery Network configuration for cloud managed +ms.prod: OFFICE365 +ms.assetid: c5aa7b52-77a0-464d-a295-5ee8e9a08f61 +--- + + +# Best practices: Office Content Delivery Network configuration for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Cloud Managed* will use the Office Content Delivery Network (CDN) for the source files to deploy the Office 365 ProPlus packages. However, they will utilize automation scripts for OffScrub and to initiate the Office 365 ProPlus deployment. +The Office 365 configuration script does the following: + + + + + +- Run OffScrub + + - Remove all Office 2010 MSI components if found + + + - Remove Office 2013 MSI core suite if found, but leave 2013 Project and Visio intact if previously installed + + + - Leave user data in place + + +- Install Office 365 ProPlus with proper channel, architecture, and languages from Office CDN + + + +## OffScrub + +The following table includes the OffScrub Command lines that *Cloud Managed* used for the script sequence to remove previous versions of Office: + + + + +||| +|:-----|:-----| +|**Context for program**
|**Command line**
| +|Office 2010 Removal
|Command prompt cscript Offscrub2010.vbs clientall /bypass 1 /log c:\\temp /nocancel /q
| +|Office 2013 MSI Removal
|Command prompt cscript OffScrub2013.vbs ProPlus /bypass 1 /log c:\\temp /nocancel /q
| + + +## Office source location + + *Cloud Managed* will utilize scripts to complete the Office 365 client configurations. The following is an example of the Office source location for Cloud Managed 32-bit Deferred Channel. It includes the ODT setup.exe, Office 365 client install XML files, and corresponding batch files. + + + + + + + +![Cloud managed source locations](images/82dbed0c-d6d1-42fc-bb05-2556189be01b.jpg) + + + +An example batch file for the package is as follows: + + + + +||| +|:-----|:-----| +|**Context for program**
|**Command line**
| +|Deferred Channel 32-bit
|Setup.exe /configure Install_ProPlus_DC_.xml
| + + diff --git a/DeployOffice/best-practices-planning-for-cloud-managed.md b/DeployOffice/best-practices-planning-for-cloud-managed.md new file mode 100644 index 000000000..a0522ee20 --- /dev/null +++ b/DeployOffice/best-practices-planning-for-cloud-managed.md @@ -0,0 +1,207 @@ +--- +title: Best practices Planning for cloud managed +ms.prod: OFFICE365 +ms.assetid: e9a8dd9f-732c-4c51-907b-59152acda975 +--- + + +# Best practices: Planning for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Creating a deployment plan is a key component when migrating to Office 365 ProPlus. Planning is based on discovered assessment items, including constraints and how to implement Office 365 ProPlus to meet the goals of the project. +## Planning source locations + +Office 365 ProPlus can be deployed and updated directly from the Office Content Delivery Network (CDN), System Center Configuration Manager, or a network share or Distributed File System (DFS). Because Cloud Managed does not use client management software or have a DFS in place, they will leverage the Office 365 self-service portal to install Office 365 ProPlus for remote users, and leverage the CDN for non-traveling or on-premises users. The following planning is focused on the assets that were discovered during the assessment phase. + + + + +## Channel membership + + *Cloud Managed* understands the following Microsoft guidance: + + + + +- 1% get Current Channel + + +- 10% get First Release for Deferred Channel + + +- 89% get Deferred Channel + + +Using existing groups, ~50 users will be on First Release Deferred Channel, and ~440 users will get Deferred Channel. There are ~10 developer, technology owner, or business lead roles that will self-install and self-manage from Office CDN with Current Channel. These Current Channel users will receive features ahead of FRDC and DC. + + + +For more information about channel membership and management, see [Managing Channels for Office 365 ProPlus](http://www.deployoffice.com/preferred-practices/). + + + + +## Base client packaging + +The IT department at *Cloud Managed* has limited history of deploying MSI-based Office using Office Customization Tool, with only one previous deployment configured. A business requirement is for shared computers to be covered as part of the deployment. Cloud Managed will create deployment packages consisting of the install XML file and ODT setup.exe, host it internally using UNC shares, and create deployment scripts to deploy Office 365 ProPlus. + + + + +## Download the source files + +When using the Office CDN, Cloud Managed is not downloading source files to an on-premises location for redistribution. However, they will still leverage the [Office 2016 Deployment Tool](https://www.microsoft.com/en-us/download/details.aspx?id=49117) to create an install package and language pack for customization and distribution. + + + +For more information about the Office Deployment Tool, see [Office Deployment Tool](http://www.deployoffice.com/preferred-practices/). + + + + +## Configure deployments + + *Cloud Managed* uses [Github Office 365 ProPlus - Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + +The install XML files are relatively simple and can be made by following the [XML properties that are published on Technet](https://technet.microsoft.com/en-us/library/jj219426.aspx). However, because *Cloud Managed* manages multiple download and install XML files, *Cloud Managed* uses a web-based tool for accuracy and efficiency. + + + + *Cloud Managed* will need install XML files for the following: + + + + +- 32-bit Office 365 ProPlus Deferred Channel and supported language + + +- 32-bit Office 365 ProPlus First Release for Deferred Channel and supported language + + +It is not difficult to manage multiple install XML files because they are less than 4 kilobytes each. + + + + +## Shared computing + +The shared computing property value needs to be set properly for each of the shared computing scenarios that were discovered during Assessment. + + + + +``` + + +``` + +The following table describes how the setting will be applied to each of the shared computer activation deployment scenarios: + + + + +||| +|:-----|:-----| +|**Client type**
|**XML value**
| +|Standard desktop
|0
| +|Shared workstation
|1
| + + +## Languages + + *Cloud Managed* will use the Office CDN and languages will be downloaded directly from the Office CDN and installed using the Office Deployment Tool. If they decided to allow users to install additional languages, users can leverage a self-service language pack install because they have local administrator rights on the clients. + + + + +## Remove/restore applications + + *Cloud Managed* is not planning to exclude any applications during the Office 365 ProPlus deployment. + + + + +## Customizations (GPO) + + *Cloud Managed* will leverage the [Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool for Group Policy](https://www.microsoft.com/en-us/download/details.aspx?id=49030) *. Cloud Managed* has reviewed existing Group Policy settings and identified any preexisting Group Policy settings to use with Office 365 ProPlus. At this time, [OneDrive is a separate GPO template download](https://support.office.com/en-us/article/Administrative-settings-for-the-new-OneDrive-sync-client-0ecb2cf5-8882-42b3-a6e9-be6bda30899c?ui=en-US&rs=en-US&ad=US) and should be reviewed to determine if any Group Policy settings are required. + + + + +## Side by side + + *Cloud Managed* will install Office 365 ProPlus side by side with existing Office installations that have Project and Visio. The plan of record is to remove any previous versions of Office 2010 and 2013 (MSI), Project 2010 (MSI), and Visio 2010 (MSI), and to keep user data intact (dictionary, mail file, signature, etc.). If a user already has a 2013 Project or Visio (MSI) install on their machine, it will be left installed during the OffScrub process, but a quick repair will be run after the Office 365 ProPlus installation completes in order for the Project and Visio versions to function properly. If a user runs into Macro or Add-in errors, they will then attempt to remediate the issue by using a side by side scenario. + + + + +## Project and Visio + + *Cloud Managed* has a small number of 2010 Project and Visio (MSI) deployments that they will migrate to 2013 Project and Visio (MSI). 2013 Project and Visio (MSI) will run in side by side with Office 365 ProPlus in a supported N-1 scenario. *Cloud Managed* should run a quick repair on any Project and Visio MSI installs after Office 365 ProPlus has been installed. + + + + +## Office Scrub Tool (OffScrub) + +Cloud Managed will use OffScrub to ensure that all previous installations of Office 2010 (MSI), including Project and Visio 2010 installations, and all previous installations of Office 2013 (MSI), excluding Project and Visio 2013, are properly removed before Office 365 ProPlus is installed. + + + +For more information on the OffScrub tool, see [Offscrub](http://www.deployoffice.com/preferred-practices/). + + + + +## Architecture + + *Cloud Managed* determined that only the 32-bit version of the Office 365 clients will be deployed. *Cloud Managed* has no use cases for 64-bit applications. + + + + +## Office 2016 for Mac + + *Cloud Managed* will not use client management software to deploy Office 2016 for Mac for their ~5 Mac users. Instead, they will use the Office 365 portal for users who need Office 2016 for Mac. Users will be prompted for their machine administrator credentials to install Office 2016 for Mac. + + + + +## Licensing + + *Cloud Managed* has already synced their users and the Exchange Online users already have E3 licenses. *Cloud Managed* uses PowerShell and on premises AD DS attributes to determine and assign the Office 365 Licenses, but also does some manual license assignment and management via the Office 365 admin portal. + + + + +> [!NOTE] +> Licensing is done by using custom PowerShell; the AD DS is just a reference point for the PowerShell licensing script. + + + + + +## Network + + *Cloud Managed* will bypass proxy services for all Office 365 ProPlus URLs. Therefore, the ability to activate or authenticate to Office 365 and maintain the subscription will not be blocked. Since they will be relying on users to update from the CDN, all Office 365 ProPlus URLs must be open. + + + + +## Staying current versus skipping builds and rollbacks + + *Cloud Managed* is planning on staying current because they understand that it is the most network optimized solution. However, they have created a script stored in a network location that contains the necessary items to perform a rollback to a previously known good version. Administrators would need to provide the appropriate version number in the script to rollback to, and they will utilize the Office CDN for the rollback. + + + +For more information about performing a rollback, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + diff --git a/DeployOffice/best-practices-planning-for-enterprise-managed.md b/DeployOffice/best-practices-planning-for-enterprise-managed.md new file mode 100644 index 000000000..bc2d4b82b --- /dev/null +++ b/DeployOffice/best-practices-planning-for-enterprise-managed.md @@ -0,0 +1,282 @@ +--- +title: Best practices Planning for enterprise managed +ms.prod: OFFICE365 +ms.assetid: 98799ea9-3b93-46b4-b399-b9fcab3e1d80 +--- + + +# Best practices: Planning for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Creating a deployment plan is key when you migrate to Office 365 ProPlus. Planning is based on discovered assessment items, including constraints, and how to implement Office 365 ProPlus to meet the goals of the project. +## Planning source locations + +You can deploy and update Office 365 ProPlus directly from the Office Content Delivery Network (CDN), System Center Configuration Manager, or an internal share such as UNC shares or a Distributed File System (DFS). Because * Enterprise Managed* has System Center Configuration Manager implemented in the environment, they can leverage System Center Configuration Manager for the initial deployment. System Center Configuration Manager has update 1606 or greater; therefore, they can manage Office updates natively in System Center Configuration Manager, as well as ongoing Office 365 channel and build management. + + + +The following planning is focused around deployment of items that are discovered in Assessment by using System Center Configuration Manager. + + + + +## Channel membership + + *Enterprise Managed* uses the following Microsoft channel membership guidance: + + + + +- 1% get Current Channel + + +- 10% get First Release for Deferred Channel + + +- 89% get Deferred Channel + + +Because * Enterprise Managed* already has System Center Configuration Manager Collections for QA and Production Groups, they can leverage the existing System Center Configuration Manager collections: these are very close to the Microsoft recommendations. Using the existing collections, approximately 1,500 users will get First Release for Deferred Channel (FRDC), and approximately 18,471 users will get Deferred Channel (DC). Approximately 25 development, technology owner, or business lead roles will self-install and self-manage from CDN with Current Channel. These Current Channel users will receive features ahead of FRDC and DC. + + + +For more information about channel membership and management, see [Best practices: Management for enterprise managed](best-practices-management-for-enterprise-managed.md). + + + + +## Base client packaging + +The packaging and deployment team at *Enterprise Managed* has a rich history of deploying MSI -based Office by leveraging the Office Customization Tool. Many MSI-based files significantly customize how Office looks and feels. + + + + *Enterprise Managed* only implements changes that adhere to security polices. Office 365 ProPlus is initially configured without OneDrive for Business at deployment time; it will be added later. There is also a business requirement that all shared computer scenarios are covered properly, as they make up a sizable user population. Distribution will continue to leverage the existing System Center Configuration Manager infrastructure to deploy the Office 365 clients with the elevated privileges that are required for Office installation. + + + + +## Download the source files + +The [Office 2016 Deployment Tool](https://www.microsoft.com/en-us/download/details.aspx?id=49117) downloads the source media that is required to create an install package and language pack(s) for customization and distribution. *Enterprise Managed* will create a download an XML file that the Office Deployment Tool setup.exe uses to download the Office 365 client source files. + + + +For more information about the Office Deployment Tool, see [Best practices: Deployment for enterprise managed](best-practices-deployment-for-enterprise-managed.md). + + + + +## Configure deployments + + *Enterprise Managed* uses [Github Office 365 ProPlus - Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + +The install XML files are relatively simple and can be made by following the [XML properties that are published on Technet](https://technet.microsoft.com/en-us/library/jj219426.aspx). However, because *Enterprise Managed* manages multiple download and install XML files, *Enterprise Managed* uses a web-based tool for accuracy and efficiency. + + + + *Enterprise Managed* needs install XML files for the following: + + + + +- 32-bit Office 365 ProPlus Deferred Channel in each region and appropriate supported regional languages + + +- 32-bit Project Pro (VL) Deferred Channel and supported language + + +- 32-bit Visio Pro (VL) Deferred Channel and supported language + + +- 64-bit Deferred Channel and appropriate supported language + + +- 32-bit Office 365 ProPlus First Release for Deferred Channel and supported language + + +- 32-bit Project Pro (VL) First Release for Deferred Channel and supported language + + +- 32-bit Visio Pro (VL) First Release for Deferred Channel and supported language + + +Having multiple XML files is not difficult to manage because each is less than 4 kilobytes, and they make up the System Center Configuration Manager programs attributes for the package. + + + + +## Shared computing + +The shared computing property value needs to be set properly for each of the shared computing scenarios discovered during Assessment. + + + + +``` + + +``` + +The following table explains how the settings will be applied to each of the shared computer activation deployment scenarios that Assessment identified: + + + + +||| +|:-----|:-----| +|**Client type**
|**XML value**
| +|Standard desktop
|0
| +|RDS
|1
| +|Non-Persistent VDI
|1
| +|Persistent VDI
|0
| +|Shared workstation
|1
| + + +## Languages + +Languages are downloaded and installed by using the Office Deployment Tool. System Center Configuration Manager packages will be broken up by regions, where each region will have its own set of languages that accompany the Office 365 ProPlus files. *Enterprise Managed* has adds each language to the self-service catalog for users to install post-Office deployment. Because the language packs are about 200 MB each, and self-service of languages outside the region is an occurrence that happens rarely, all languages are not replicated to all regions. The default language is the one that is most commonly used in that region, together with instructions on how to change the default language. For the self-service languages, such as a user in the LATAM region who wants to add German, the ** Product ID=" LanguagePack"** element in the Office Deployment Tool is used. + + + +The following table shows each region and corresponding languages and identifiers: + + + + +||||| +|:-----|:-----|:-----|:-----| +|**Region**
|**Languages**
|**Geographic area**
|**Language ID**
| +|North America
|English
French
Spanish
|United States
Canada
Mexico
|EN-US
FR-FR
ES-ES
| +|LATAM
|Spanish
Portuguese
English
|South America
Brazil
|ES-ES
PT-BR
EN-US
| +|AsiaPAC
|Chinese (Simplified)
Chinese
Indonesian
Japanese
Korean
Malay
Thai
English
|People's Republic of China
Taiwan
Indonesia
Japan
Korea
Malaysia
Thailand
|ZH-CN
ZH-TW
ID-ID
JA-JP
KO-KR
MS-MY
TH-TH
EN-US
| +|EU
|Czech
Danish
Dutch
Finnish
German
Greek
French
English
|Czech Republic
Denmark
Netherlands
Finland
Germany
Greece
France
|CS-CZ
DA-DK
NL-NL
FI-FI
DE-DE
EL-GR
FR-FR
EN-US
| + + +## Remove/restore applications + +OneDrive for Business is excluded from the Office 365 ProPlus suite at time of deployment, but Enterprise Managed can add it later after it has been signed off on and approved for deployment. Although they could use AppLocker in GPO to lock the .EXE, users would still see the icon; therefore, they have decided to use the **ExcludeApp** element in the install XML file. + + + + +## Customizations (GPO) + + *Enterprise Managed* will leverage the [Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool for Group Policy](https://www.microsoft.com/en-us/download/details.aspx?id=49030) *Enterprise Managed* has reviewed existing Group Policy settings and identified any preexisting Group Policy settings to use with Office 365 ProPlus. [OneDrive is a separate GPO template download](https://support.office.com/en-us/article/Administrative-settings-for-the-new-OneDrive-sync-client-0ecb2cf5-8882-42b3-a6e9-be6bda30899c?ui=en-US&rs=en-US&ad=US) that is not leveraged until *Enterprise Managed* approves and adds OneDrive for Business into the Office 365 ProPlus deployment package. + + + +A sample set of the Preferred Practices policies and GPO backups can be found here. + + + + +## Side by side + + *Enterprise Managed* will avoid running side by side versions, especially where Project and Visio are concerned. The plan of record is to use the Office Scrub tool (OffScrub) to remove any previous versions of Office (2007, 2010, or 2013), but leave the user data intact (such as the dictionary, mail file, signature, etc.). If the user requests Project or Visio, they can be pre-approved by role (such as project manager) or by manager approval. This is not an automated process. If a user runs into macro or add-in issues, *Enterprise Managed* will remediate the issue via the help desk first. If escalated further, Enterprise Managed can do a side by side or a Published App model for legacy versions of Office. Side by side scenarios are determined on a case by case basis. + + + + +## Infopath + + *Enterprise Managed* will download the 2013 MSI version of InfoPath from the portal or Microsoft download center and distribute it as part of the payload of Office. *Enterprise Managed* understands that this product is the last version that will be made, and is working on removing InfoPath forms from their environment. It is being deployed with Office in parallel to finding an InfoPath replacement. + + + + +## Project and Visio + + *Enterprise Managed* has different versions and users of Project and Visio that they do not want to run side by side. Additionally, *Enterprise Managed* are transitioning from MSI-based Project and Visio software to the Click-to-Run (C2R) based versions. *Enterprise Managed* will continue to leverage their existing KMS/MAK servers for activation of Project and Visio, but the applications will be deployed by using an install XML file and Office Deployment Tool. + + + +For more information about deploying the C2R volume licensed editions of Project and Visio, see [Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016](https://technet.microsoft.com/library/mt703272.aspx). + + + + +## Office scrub tool (OffScrub) + + *Enterprise Managed* will use OffScrub to ensure that all previous Office versions, including Project and Visio installations, are properly removed before Office 365 ProPlus is installed. + + + +For more information on the OffScrub tool, please see [Offscrub](http://www.deployoffice.com/preferred-practices/). + + + + +## Architecture + + *Enterprise Managed* determined that only the finance and accounting departments need to run 64-bit Office. Therefore, there will be a single deployment channel (Deferred) for 64-bit to reduce the storage and complexity of maintaining multiple channels, builds, and levels of architecture. + + + + +## Office 2016 for Mac + + *Enterprise Managed* will leverage their existing Mac enterprise software management tool to install and manage Office 2016 for Mac deployments for the ~500 Mac users. An Office 365 administrator will download the **Microsoft_Office_2016_Installer.pkg** from the Office 365 portal and use the software distribution tool to distribute and manage it. Users will be blocked from installing Office 2016 for Mac from the Office 365 software portal. + + + + +## Licensing + + *Enterprise Managed* has already synced all of their users, and the Exchange Online users already using E3/E5 licenses. They utilize PowerShell and on-premises AD DS attributes to determine and assign the Office 365 Licenses. The majority of users are E3, with the exception being Enterprise Voice E5 users, which are well defined. The remaining E1 users are temporary employees that are in a very locked down OU, and are easy to manage with AD DS attributes. + + + + +> [!NOTE] +> Licensing is done by using custom PowerShell; the AD DS is just a reference point for the PowerShell licensing script. + + + + + +## Network + + *Enterprise Managed* will bypass proxy services for all Office 365 ProPlus URLs. Therefore, the ability to activate and authenticate to Office 365 and maintain the subscription is not blocked. 99% of the organization users will get the Office content from System Center Configuration Manager, but System Center Configuration Manager must get the content from the Office CDN. + + + +The following table shows the planning estimates for monthly downloads from CDN to System Center Configuration Manager: + + + + +|||| +|:-----|:-----|:-----| +|**Name**
|**Approximate size**
|**Approximate frequency**
| +|32-bit Deferred Channel
|~1024 MB
|Monthly
| +|64-bit Deferred Channel
|~1024 MB
|Monthly
| +|32-bit First Release Deferred Channel
|~1024 MB
|Every 2 weeks (for estimation purposes)
| +|17 Languages
|17*~200 MB = ~3,400 MB
|Monthly
| + +Download from Internet to System Center Configuration Manager each month: ~7.4 GB. + + + +Largest regional distribution point update each month (1 channel, 1 architecture and 8 languages): 2.6 GB. + + + + +## Staying current versus skipping builds and rollbacks + + *Enterprise Managed* is planning on staying current because it is the most network-optimized solution. However, they have created an empty package in System Center Configuration Manager that contains the necessary items to perform a rollback to a previously known good version. An administrator must provide the appropriate source files and version number to which to rollback the clients. + + + +For more information about performing a rollback, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + diff --git a/DeployOffice/best-practices-planning-for-locally-managed.md b/DeployOffice/best-practices-planning-for-locally-managed.md new file mode 100644 index 000000000..e5000e555 --- /dev/null +++ b/DeployOffice/best-practices-planning-for-locally-managed.md @@ -0,0 +1,263 @@ +--- +title: Best practices Planning for locally managed +ms.prod: OFFICE365 +ms.assetid: ac3e0d61-fd10-4caa-9b88-be55d1ef39bb +--- + + +# Best practices: Planning for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +Creating a deployment plan is a key component when migrating to Office 365 ProPlus. Planning is based on discovered assessment items, including constraints and how to implement Office 365 ProPlus to meet the goals of the project. +## Planning source locations + +Office 365 ProPlus can be deployed and updated directly from the Office Content Delivery Network (CDN), System Center Configuration Manager, or through an internal share such as a network share or Distributed File System (DFS). Because *Locally Managed* has a DFS implementation, *Locally Managed* will leverage DFS to deploy the initial Office deployment, as well as ongoing build management. The following planning is focused around deployment of items that were discovered in Assessment via DFS. + + + + +## Channel membership + + *Locally Managed* will incorporate the following Microsoft channel membership guidance: + + + + +- 1% get Current Channel + + +- 10% get First Release for Deferred Channel + + +- 89% get Deferred Channel + + + *Locally Managed* estimates that there may be ~20 developer, technology owner, or business lead roles that will self-install and self-manage from CDN with Current Channel (to have the features before anyone one else). These Current Channel users will receive features ahead of FRDC and DC. The existing QA collection of ~500 users will also be utilized to receive First Release for Deferred Channel. These FRDC users should represent all business groups, so that each build has been validated throughout the organization. + + + +For more information about channel membership and management, see [Managing Channels for Office 365 ProPlus](http://www.deployoffice.com/preferred-practices/). + + + + +## Base client packaging + +The packaging and deployment team at *Locally Managed* has a moderate history of deploying MSI-based (MSI) Office leveraging the Office Customization Tool with Office 2010. Many of the MSI-based files significantly customize how Office looks and feels. *Locally Managed* will only implement changes that adhere to their security polices to minimize any customizations to look and feel. Office 365 ProPlus will be configured without Access at deployment time, because it is not required by the organization. There is also a business requirement for the shared computer scenarios to be covered properly. Office 365 ProPlus distribution will leverage the DFS infrastructure and batch files to deploy the Office 365 client with elevated privileges that are required for installation. + + + + +## Download the source files + +The Office 2016 Deployment Tool will be used to download the source media required to create an install package and language pack(s) for customization and distribution. *Locally Managed* will create a download XML file that Office Deployment Tool setup.exe uses to download the Office 365 client source files. + + + +For more information about the Office Deployment Tool, see [Office Deployment Tool](http://www.deployoffice.com/preferred-practices/). + + + + +## Configure deployments + + *Locally Managed* uses [ Github Office 365 ProPlus - Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + +The install XML files are relatively simple and can be made by following the [XML properties that are published on Technet](https://technet.microsoft.com/en-us/library/jj219426.aspx). However, because *Locally Managed* manages multiple download and install XML files, *Locally Managed* uses a web-based tool for accuracy and efficiency. + + + + *Locally Managed* will need install XML files for the following: + + + + +- 32-bit Office 365 ProPlus Deferred Channel in both regions and appropriate supported regional languages + + +- 32-bit Project Pro Deferred Channel and supported language + + +- 32-bit Visio Pro Deferred Channel and supported language + + +- 32-bit Office 365 ProPlus First Release for Deferred Channel and supported language + + +- 32-bit Project Pro First Release for Deferred Channel and supported language + + +- 32-bit Visio Pro First Release for Deferred Channel and supported language + + +It is not difficult to manage multiple install XML files because they are less than 4 kilobytes each. + + + + +## Shared computing + +The shared computing property value must be set properly for each of the shared computing scenarios that were discovered during assessment. + + + + +``` + + +``` + +The following table explains how the setting is applied to each of the shared computer activation deployment scenarios that were identified during Assessment: + + + + +||| +|:-----|:-----| +|**Client type**
|**XML value**
| +|Standard desktop
|0
| +|RDS
|1
| +|Random access workstation
|1
| + + +## Languages + +Languages will be downloaded and installed using the Office Deployment Tool. *Locally Managed* will add a self-service installation for all three supported languages because they will not be installing the same languages in the CanAm and Germany regions. For the self-service languages, such as a user in the CanAm region wanting to add German, the plan is to use the **Product ID="LanguagePack"** element in the Office Deployment Tool. + + + +The default language is the one that is most commonly used in a region. The following table lists each region and the corresponding languages and identifiers. + + + + +||||| +|:-----|:-----|:-----|:-----| +|**Region**
|**Languages**
|**Geographic area**
|**Language ID**
| +|CanAm
|English
French
|United States
Canada
|EN-US
FR-FR
| +|Germany
|German
|Germany
|DE-DE
| + + +## Remove/restore applications + +Access will be excluded from the Office 365 ProPlus suite at time of deployment, but *Locally Managed* can add it later should business requirements change. *Locally Managed* could use AppLocker in GPO to lock the .exe, but users would still see the icon; therefore, a better approach is to use the **ExcludeApp** element in the install XML file. + + + + +## Customizations (GPO) + + *Locally Managed* will leverage the [Office 2016 Administrative Template files (ADMX/ADML) and Office Customization Tool for Group Policy](https://www.microsoft.com/en-us/download/details.aspx?id=49030) *Locally Managed* has reviewed existing Group Policy settings and identified any preexisting Group Policy settings to use with Office 365 ProPlus. [OneDrive is a separate GPO template download](https://support.office.com/en-us/article/Administrative-settings-for-the-new-OneDrive-sync-client-0ecb2cf5-8882-42b3-a6e9-be6bda30899c?ui=en-US&rs=en-US&ad=US) that is not leveraged until *Locally Managed* approves and adds OneDrive for Business into the Office 365 ProPlus deployment package. + + + +A sample set of the Preferred Practices policies and GPO backups can be found here. + + + + +## Side by side + + *Locally Managed* reviewed their assessment data and decided to avoid running side by side. The plan of record is to use the Office Scrub tool (OffScrub) to remove the previous version of Office 2010 (MSI), but leave the user data intact (dictionary, mail file, signature, etc.). If the user requests Project or Visio back, they can be pre-approved by role (such as project manager) or managed approval to be licensed and allowed to get the Office 365 Project or Visio Pro version installed. If a user runs into macro or add-in issues, they will attempt to remediate the issue via the IT helpdesk first. If escalated further, *Locally Managed* will do side by side for the legacy version of Office. This will be determined on a case by case basis. + + + + +## Infopath + + *Locally Managed* will download the 2013 MSI version of InfoPath from the portal or [Microsoft download center](https://www.microsoft.com/en-us/download/details.aspx?id=48734) and distribute it as part of the payload of office. *Locally Managed* understands that this product is the last version that will be made, and is working on removing InfoPath forms from their environment. It is being deployed with Office in parallel to finding an InfoPath replacement. + + + + +## Project and Visio + + *Locally Managed* has a moderate number of Project and Visio 2010 installs that they do not want to run side by side. They will be transitioning from machine installs of the software to adding the licenses to their Office 365 tenant to cover Click-to-Run versions of Project and Visio. This way, the license will follow the user and always be the current version of Office, Project, and Visio. This will require less administrative effort and management from the IT team. + + + + +## Office Scrub Tool (OffScrub) + + *Locally Managed* will use OffScrub to ensure that all previous installations of Office 2010 (MSI), including Project and Visio 2010 installations, are properly removed before Office 365 ProPlus is installed. + + + +For more information on the OffScrub tool, see [Offscrub](http://www.deployoffice.com/preferred-practices/). + + + + +## Architecture + + *Locally Managed* determined that only the 32-bit version of the Office 365 clients will be deployed. Locally Managed has no use cases for 64-bit applications. + + + + +## Office 2016 for Mac + +Because *Locally Managed* has a small population of ~25 existing Office for Mac users, they will leverage a network share for Office 2016 for Mac deployments. An Office 365 administrator will download the **Microsoft_Office_2016_Installer.pkg** from the Office 365 portal, and users will install Office 2016 for Mac from the network location. Users will be prompted for their machine administrator credentials to install Office 2016 for Mac. + + + + +## Licensing + + *Locally Managed* has already synced all of their users, and the Exchange Online users already use E3 licenses. *Locally Managed* uses PowerShell and on premises AD DS attributes to determine and assign the Office 365 Licenses. Nearly all users are assigned the E3 license SKU. + + + + +> [!NOTE] +> Licensing is done by using custom PowerShell; the AD DS is just a reference point for the PowerShell licensing script. + + + + + +## Network + + *Locally Managed* will bypass proxy services for all Office 365 ProPlus URLs. Therefore, the ability to activate or authenticate to Office 365 and maintain the subscription will not be blocked. Because they will be relying on users to update from the CDN, all Office 365 ProPlus URLs must be open. + + + + +|||| +|:-----|:-----|:-----| +|**Name**
|**Approximate size**
|**Approximate frequency**
| +|32-bit Deferred Channel
|~1024 MB
|Monthly
| +|3 Languages
|3 *~200MB = ~600 MB
|Monthly
| +|32-bit First Release Deferred Channel
|~1024 MB
|Every 2 weeks (for estimation purposes)
| +|1 Language
|~200 MB
|Every 2 weeks (for estimation purposes)
| + +Deferred Channel download from Office CDN to DFS each month: ~ 1.6 GB. + + + +First Release for Deferred Channel download from Office CDN to DFS each month: ~2.4 GB. + + + +Total download from Office CDN to DFS each month: ~4 GB. + + + + +## Staying current versus skipping builds and rollbacks + + *Locally Managed* is planning on staying current because they understand that it is the most network optimized solution. However, they have created a script stored in the DFS that contains the necessary items to perform a rollback to a previously known good version. An administrator would need to download the appropriate source files to rollback to, and insert the appropriate version number in the script to rollback to. + + + +For more information about performing a rollback, see [Channel management](http://www.deployoffice.com/preferred-practices/). + + + + diff --git a/DeployOffice/best-practices-recommended-deployment-scenarios.md b/DeployOffice/best-practices-recommended-deployment-scenarios.md new file mode 100644 index 000000000..1c55dba54 --- /dev/null +++ b/DeployOffice/best-practices-recommended-deployment-scenarios.md @@ -0,0 +1,85 @@ +--- +title: Best practices Recommended deployment scenarios +ms.prod: OFFICE365 +ms.assetid: 4d4ff951-ee72-4763-806a-deeb384a369b +--- + + +# Best practices: Recommended deployment scenarios + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +The following are example customers that are an amalgam of the most common customer scenarios that we encounter. If the example customer does not match your environment exactly, that is okay because between all three of the customer examples, we should cover most of the of the situations any customer could face. +We have named these customer scenarios Enterprise Managed, Locally Managed, and Cloud Managed, based on the primary distribution and update management solution that each scenario leverages. + + + + + +## Call to action + +Please review the three scenarios and decide which one best fits your current environment. Lead with this scenario and feel free to add portions from the other two scenarios. For example, your environment might be very similar to the *Enterprise Managed* scenario, except that you leverage an older MSI version of Project/Visio and allow Mac users to configure their own software. You would follow all of the guidance from *Enterprise Managed* except when it comes to Project/Visio and Mac clients, and then check *Locally Managed* and *Cloud Managed* to see which scenario best fits your Project/Visio and Mac client usage. We recommend that you identifywhich scenario is most similar to your current environment and then mix and match components from the other scenarios to build out a complete assessment and deployment plan. + + + + +## The Enterprise Managed scenario + + *Enterprise Managed* represents large to very large organizations, . in which the work force is leveraging nearly every single technology that exists, ranging from desktops to notebooks to tablets, software distribution tools, and virtual environments like Remote Desktop Services and Virtual Desktop Infrastructure. The IT department manages the client software using software management tools such as System Center Configuration Manager, and has dedicated teams that administer the company's Active Directory components such as Active Directory Domain Services (AD DS), Active Directory Federation Services (AD FS), Group Policy, etc. + + + + + + + +![Enterprise Managed deployment](images/180d081a-aad7-40f9-bb18-ff65ff166530.png) + + + +If this scenario represents your organization, see [Best practices: Enterprise managed scenario](best-practices-enterprise-managed-scenario.md). + + + + +## The Locally Managed scenario + + *Locally Managed* represents medium to large organizations that may have offices in multiple countries, but are not considered to be globally distributed. Employees are generally located out of a centralized office in the country, with limited small offices. The work force is primarily leveraging newer productivity software, including some VDI, but the IT department does not have software distribution tools to manage client software. IT Administrators leverage a Distributed File System (DFS) and network shares to host installation packages that end users install, and utilize custom scripts and batch files for automated deployments for end users because the users do not have local admin rights. They do not have dedicated IT teams to specific products, and instead leverages shared teams that manage multiple technologies of the IT environment such as Active Directory Domain Services (AD DS), Active Directory Federation Services (AD FS), Group Policy, etc. + + + + + + + +![Locally Managed deployment](images/067af377-022d-4a4b-aa04-993669398ebc.png) + + + +If this scenario represents your organization, see [Best practices: Locally managed scenario](best-practices-locally-managed-scenario.md). + + + + +## The Cloud Managed scenario + + *Cloud Managed* represents generally small businesses who are generally located out of a small centralized office in a single country; however, they might have smaller remote offices throughout the country. The work force leverages the newest productivity devices and software on the market, because having a smaller organization allows for more rapid adoption of new technology. They have a small IT team that manages the entire organizational IT environment technologies such as Active Directory Domain Services (AD DS), Azure Active Directory Password Sync, GPO, etc. The IT team does not use software distribution tools to manage client software, and no Distributed File System (DFS) exists. Network shares are leveraged for installing software, and users have administrative privileges on their client devices. The IT team provides batch files or scripts for end users to automate deployments. + + + + + + + +![Cloud Managed deployment](images/f1468c2b-b347-4f55-b6b7-0fa9e23a7e97.png) + + + +If this scenario represents your organization, see [Best practices: Cloud managed scenario](best-practices-cloud-managed-scenario.md). + + + + diff --git a/DeployOffice/best-practices-sample-configuration-files-for-downloading-office-365-proplus.md b/DeployOffice/best-practices-sample-configuration-files-for-downloading-office-365-proplus.md new file mode 100644 index 000000000..2da7beb43 --- /dev/null +++ b/DeployOffice/best-practices-sample-configuration-files-for-downloading-office-365-proplus.md @@ -0,0 +1,221 @@ +--- +title: Best practices Sample configuration files for downloading Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 8efa2040-4259-42e7-8087-f589adcc4190 +--- + + +# Best practices: Sample configuration files for downloading Office 365 ProPlus + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +This article includes some common XML configuration files for using the Office 2016 Deployment Tool to download Office UNRESOLVED_TOKEN_VAL(365) ProPlus source files. +## Sample Download File with all Office Applications - Deferred Channel + + +``` + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Channel="Deferred"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| + + +## Sample Download File with all Office Applications in 64-bit - Current Channel + + +``` + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="64"
|The architecture of Office being downloaded.
| +|Channel="Current"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| + + +## Sample Download File with all Office Applications with English and Spanish - Deferred Channel + + +``` + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Channel="Deferred"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Language ID="es-es"
|The additional language being downloaded for Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| + + +## Sample Download File with all Applications including Visio and Project 2016 Click to Run - Deferred Channel + + +``` + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Channel="Deferred"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Product ID="VisioProRetail"
|Visio 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus. Note: Visio 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus must be on the same update channel as Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Language ID="en-us"
|The default language being downloaded for Visio 2016 Click to Run.
| +|Product ID="ProjectProRetail"
|Project 2016Office UNRESOLVED_TOKEN_VAL(365) ProPlus. Note: Project 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus must be on the same update channel as Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Language ID="en-us"
|The default language being downloaded for Project 2016 Click to Run.
| + + +## Sample Download File with all Applications including Visio and Project 2016 Click to Run with English and Spanish - Deferred Channel + + +``` + + + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Channel="Deferred"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Language ID="es-es"
|The additional language being downloaded for Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Product ID="VisioProRetail"
|Visio 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus. Note: Visio 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus must be on the same update channel as Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Language ID="en-us"
|The default language being downloaded for Visio 2016 Click to Run.
| +|Language ID="es-es"
|The additional language being downloaded for Visio 2016 Click to Run.
| +|Product ID="ProjectProRetail"
|Project 2016Office UNRESOLVED_TOKEN_VAL(365) ProPlus. Note: Project 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus must be on the same update channel as Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Language ID="en-us"
|The default language being downloaded for Project 2016 Click to Run.
| +|Language ID="es-es"
|The additional language being downloaded for Project 2016 Click to Run.
| + + +## Sample Download File with all Applications including Visio (VL) and Project (VL) 2016 Click to Run - Deferred Channel + + +``` + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Channel="Deferred"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Product ID="VisioProXVolume"
|Visio 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus volume licensed. Note: Visio 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus must be on the same update channel as Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Language ID="en-us"
|The default language being downloaded for Visio 2016 Click to Run.
| +|Product ID="ProjectProXVolumel"
|Project 2016Office UNRESOLVED_TOKEN_VAL(365) ProPlus volume licensed. Note: Project 2016 Office UNRESOLVED_TOKEN_VAL(365) ProPlus must be on the same update channel as Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Language ID="en-us"
|The default language being downloaded for Project 2016 Click to Run.
| + + diff --git a/DeployOffice/best-practices-sample-configuration-files-for-installing-office-365-proplus.md b/DeployOffice/best-practices-sample-configuration-files-for-installing-office-365-proplus.md new file mode 100644 index 000000000..08c2a85c3 --- /dev/null +++ b/DeployOffice/best-practices-sample-configuration-files-for-installing-office-365-proplus.md @@ -0,0 +1,250 @@ +--- +title: Best practices Sample configuration files for installing Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 13aa8058-b524-4c73-930b-0802b2617ab4 +--- + + +# Best practices: Sample configuration files for installing Office 365 ProPlus + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + This article contains some common example XML files to configure and install Office UNRESOLVED_TOKEN_VAL(365) ProPlus. +## Sample configuration with all Office applications with updates enabled from CDN, interface display, license agreement + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Updates Enabled="TRUE"
|Updates are enabled to automatically download from CDN.
| +|Display Level="Full"
|Full UI when installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|AcceptEULA="TRUE"
|Accept the license agreement.
| + + +## Sample configuration with all Office applications with SourcePath, updates enabled from internal source, interface display, license agreement + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Updates Enabled="TRUE"
|Updates are enabled.
| +|UpdatePath="\\\\Server\\Share\\Updates"
|Updates to install from \\\\Server\\Share\\Updates.
| +|Display Level="Full"
|Full UI when installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|AcceptEULA="TRUE"
|Accept the license agreement.
| + + +## Sample configuration with Word excluded with SourcePath, updates enabled from internal source, interface display, license agreement, logging + + +``` + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|ExcludeApp ID="Word"
|Excludes Word from being installed.
| +|Updates Enabled="TRUE"
|Updates are enabled.
| +|UpdatePath="\\\\Server\\Share\\Updates"
|Updates to install from \\\\Server\\Share\\Updates.
| +|Display Level="Full"
|Full UI when installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|AcceptEULA="TRUE"
|Accept the license agreement.
| +|Logging Level="Standard"
|Logging is enabled.
| +|Path="%temp%"
|Log is written to %temp%.
| + + +## Sample configuration with all applications including Visio and Project 2016 Click to Run with SourcePath, updates enabled from internal source, no interface display, license agreement + + +``` + + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Product ID="ProjectProRetail"
|SKU of Project being installed.
| +|Language ID="en-us"
|The default language being installed for Project 2016 Click to Run.
| +|Product ID="VisioProRetail"
|SKU of Visio being installed.
| +|Language ID="en-us"
|The default language being installed for Visio 2016 Click to Run.
| +|Updates Enabled="TRUE"
|Updates are enabled.
| +|UpdatePath="\\\\Server\\Share\\Updates"
|Updates to install from \\\\Server\\Share\\Updates.
| +|Display Level="NONE"
|No UI when installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus, Project, and Visio
| +|AcceptEULA="TRUE"
|Accept the license agreement.
| + + +## Sample configuration with all applications including Visio (VL) and Project (VL) 2016 Click to Run with SourcePath, updates enabled from internal source, no interface display, license agreement + + +``` + + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Product ID="ProjectProXVolume"
|SKU of Project being installed (volume licensed).
| +|Language ID="en-us"
|The default language being installed for Project 2016 Click to Run.
| +|Product ID="VisioProXVolume"
|SKU of Visio being installed (volume licensed).
| +|Language ID="en-us"
|The default language being installed for Visio 2016 Click to Run.
| +|Updates Enabled="TRUE"
|Updates are enabled.
| +|UpdatePath="\\\\Server\\Share\\Updates"
|Updates to install from \\\\Server\\Share\\Updates.
| +|Display Level="NONE"
|No UI when installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus, Project, and Visio
| +|AcceptEULA="TRUE"
|Accept the license agreement.
| + + +## Sample Configuration with all applications including Visio and Project 2016 Click to Run with SourcePath, updates disabled from internal source, interface display, license agreement, logging + + +``` + + + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Product ID="ProjectProRetail"
|SKU of Project being installed.
| +|Language ID="en-us"
|The default language being installed for Project 2016 Click to Run.
| +|Product ID="VisioProRetail"
|SKU of Visio being installed.
| +|Language ID="en-us"
|The default language being installed for Visio 2016 Click to Run.
| +|Updates Enabled="FALSE"
|Updates are disabled.
| +|UpdatePath="\\\\Server\\Share\\Updates"
|Updates to install from \\\\Server\\Share\\Updates.
| +|Display Level="Full"
|Full UI when installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus, Project, and Visio
| +|AcceptEULA="TRUE"
|Accept the license agreement.
| +|Logging Level="Standard"
|Logging is enabled.
| +|Path="%temp%"
|Log is written to %temp%.
| + + diff --git a/DeployOffice/best-practices-step-by-step-installation-using-cdn.md b/DeployOffice/best-practices-step-by-step-installation-using-cdn.md new file mode 100644 index 000000000..de7de155b --- /dev/null +++ b/DeployOffice/best-practices-step-by-step-installation-using-cdn.md @@ -0,0 +1,430 @@ +--- +title: Best practices Step by step installation using CDN +ms.prod: OFFICE365 +ms.assetid: 29873de8-6c2f-4f6d-aa1a-ca6f4a28a46f +--- + + +# Best practices: Step by step installation using CDN + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +This article discusses how to install and manage Office UNRESOLVED_TOKEN_VAL(365) ProPlus by leveraging the Content Delivery Network (CDN). It also provides a high level description of the different architecture components. +## Deploy Office 365 ProPlus + + +### Create XML file for installation + +The XML file for installation will specify the following items: + + + + +- Product and languages + + +- Level of interface to display + + +- Logging options + + +- Product updates behavior + + +The parameters and settings for the XML file can be found at [Reference: Configuration options for the Office Deployment Tool](https://technet.microsoft.com/en-us/library/jj219426.aspx). The parameters for Project and Visio 2016 volume licensing can be found at [Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016](https://technet.microsoft.com/library/mt703272.aspx). A graphical UI for creating the XML file can be found at the Office GitHub Repository [Office Click-To-Run Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + + +### Create OffScrub.vbs configuration file + +An OffScrub configuration command must be created to automate the removal of Office. + + + + +1. From Premier, obtain the appropriate version of OffScrub for the Office version to remove. + + +2. From an elevated command prompt with administrative privileges, run the following command to get the SKU IDs of the Office products installed: + + ``` + +cscript .vbs /preview /log + ``` + + + Example: + + + + ``` + cscript Offscrub10.vbs /preview /log c:\\temp + ``` + +3. Review the out offscrub /preview command and look for the following line: + + ``` + Found registered product(s): PRJSTDR,PROPLUSR,VISIOR + ``` + + + Example output: + + ![Deploy Office 365 example output](images/1d4828f2-26a1-4b0e-a3d9-f35c901b831f.PNG) + + + The products found in the above example are Project 2010 Standard, Office ProPlus 2010 and Visio 2010. + + +4. Run the following command from an elevated command prompt with administrative privileges to remove all Office 2010 client products: + + ``` + +cscript OffScrub10.vbs clientall /bypass 1 /log c:\\temp /nocancel /q + ``` + + + **Sample Offscrub10.vbs removing Office 2010 and keeping Visio 2010 and Project 2010** + + + + ``` + cscript OffScrub10.vbs PROPLUSR /bypass 1 /log c:\\temp /nocancel /q + ``` + + + **Sample Offscrub10.vbs removing Office 2010 removing Visio 2010 and keeping Project 2010** + + + + ``` + cscript OffScrub10.vbs PROPLUSR, VISIOR /bypass 1 /log c:\\temp /nocancel /q + ``` + + +### Install Office365 ProPlus and remove legacy version of Office + + **Install Office 365 ProPlus and remove legacy version of Office - non-shared workstation** + + + + +1. Make sure that the update channel has been set in the Office 2016 Group Policy object. + + +2. Copy OffScrub, the ODT, and the install XML file to a local directory on the workstations. + + +3. From an elevated command prompt with administrator privileges, run the OffScrub.vbs with the appropriate command line switches. + + +4. Review the OffScrub exit codes that are contained in the script. + + > [!NOTE] + > Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes. +5. From an elevated command prompt with administrator privileges, run ** setup.exe /configure .xml**. + + +6. Review the installation log. + + +7. Reboot the workstation to cleanup any files that were not cleared from the registry during the OffScrub process. + + + **Install Office 365 ProPlus and remove legacy version of Office - shared workstation** + + + + +1. Ensure the update channel has been set in the Office 2016 Group Policy object. + + +2. Copy OffScrub, the ODT, and the install XML file to a local directory on the workstations. + + +3. From an elevated command prompt with administrator privileges, run the OffScrub.vbs with the appropriate command line switches. + + +4. Review the OffScrub exit codes that are contained in the script. + + > [!NOTE] + > Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes. +5. From an elevated command prompt with administrator privileges, run **setup.exe /configure .xml**. + + +6. Review the installation log. + + +7. Reboot the workstation to cleanup any files that were not cleared from the registry during the OffScrub process. + + + +## Post-deployment tasks + + +### Remove an application from Office 365 ProPlus + +You can remove a program from the Office Suite post-deployment by using an XML configuration file. + + + +The parameters and settings for the XML file can be found at [Reference: Configuration options for the Office Deployment Tool](https://technet.microsoft.com/en-us/library/jj219426.aspx). A graphical UI for creating the XML file can be found at the Office GitHub Repository [Office Click-To-Run Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + + **Sample Configuration File for Removing Word Post Install - Deferred Channel** + + + + + + +``` + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|ExcludeApp ID="Word"
|Remove Word from deployed Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Updates Channel = "Deferred"
|The Update Channel for Office UNRESOLVED_TOKEN_VAL(365) ProPlus. This parameter should match the Channel build being installed. If it does the product will switch to the channel defined.
Example: The channel being installed is Current Channel and the Updates Channel is set to Deferred. When the client updates, Office 365 ProPlus will update to Deferred channel, which might or might not contain all the features/non-security updates that the Current Channel does.
| +|Enabled="TRUE"
|Updates are enabled.
| +|Property Name="FORCEAPPSHUTDOWN" Value="TRUE"
|Force the Office UNRESOLVED_TOKEN_VAL(365) ProPlus apps to shutdown. This should be set to True. If the applications are not closed, installation can fail.
| +|Logging Level="Standard" Path="c:\\office install"
|Logging level and location of log file.
| +|Display Level="Full"
|Full UI when installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|AcceptEULA="TRUE"
|Accept the license agreement.
| + + **Steps to remove an application post-deployment** + + + + +1. Copy ODT and the configuration XML file to a local directory on the workstations. + + +2. From an elevated command prompt with administrator privileges, run **setup.exe /configure .xml**. + + +3. Review the installation log. + + + +### Add an application to Office 365 ProPlus + +You can add a program to the Office 365 ProPlus suite post-deployment by using an XML install file. + + + +The parameters and settings for the XML file can be found at [Reference: Configuration options for the Office Deployment Tool](https://technet.microsoft.com/en-us/library/jj219426.aspx). A graphical UI for creating the XML file can be found at the Office GitHub Repository [Office Click-To-Run Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + + **Sample Configuration File Adding Word to an Already Deployed Office 365 ProPlus - Deferred Channel** + + + + + + +``` + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Updates Channel = "Deferred"
|The Update Channel for Office UNRESOLVED_TOKEN_VAL(365) ProPlus. This parameter should match the Channel build being installed. If it does the product will switch to the channel defined.
Example: The channel being installed is Current Channel and the Updates Channel is set to Deferred. When the client updates, Office 365 ProPlus will update to Deferred channel, which might or might not contain all the features/non-security updates that the Current Channel does.
| +|Enabled="TRUE"
|Updates are enabled.
| +|Property Name="FORCEAPPSHUTDOWN" Value="TRUE"
|Force the Office UNRESOLVED_TOKEN_VAL(365) ProPlus apps to shutdown. This should be set to True. If the applications are not closed, installation can fail.
| +|Logging Level="Standard" Path="c:\\office install"
|Logging level and location of log file.
| +|Display Level="Full"
|Full UI when installing Office UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|AcceptEULA="TRUE"
|Accept the license agreement.
| + + **Steps to add an application post-deployment** + + + + +1. Copy ODT and the XML configuration file to a local directory on the workstations. + + +2. From an elevated command prompt with administrator privileges, run **setup.exe /configure .xml**. + + +3. Review the installation log. + + + +### Add a language post-deployment + +You can add an additional language to Office UNRESOLVED_TOKEN_VAL(365) ProPlus post-deployment. + + + +If the Office UNRESOLVED_TOKEN_VAL(365) ProPlus is on Current Channel greater than update 2062, use the newest ODT and XML install file that identifies the language to be installed. If Office UNRESOLVED_TOKEN_VAL(365) ProPlus is not using the above requirements, a full XML configuration must be used. + + + + **Sample XML Add Spanish to Post Deployment - Current Channel** + + + + + + +``` + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Channel="Current"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being installed.
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="LanguagePack"
|Language Pack
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Updates Channel = "Deferred"
|The Update Channel for Office UNRESOLVED_TOKEN_VAL(365) ProPlus. This parameter should match the Channel build being installed. If it does the product will switch to the channel defined.
Example: The channel being installed is Current Channel and the Updates Channel is set to Deferred. When the client updates, Office 365 ProPlus will update to Deferred channel, which might or might not contain all the features/non-security updates that the Current Channel does.
| +|Property Name="FORCEAPPSHUTDOWN" Value="TRUE"
|Force the Office UNRESOLVED_TOKEN_VAL(365) ProPlus apps to shutdown. This should be set to True. If the applications are not closed, installation can fail.
| + + **Steps to add a language post-deployment - Current Channel and Non-Current Channel** + + + + +1. Copy ODT and the configuration XML file to a local directory on the workstations. + + +2. From an elevated command prompt with administrator privileges, run **setup.exe /configure .xml**. + + +3. Review the installation log. + + + +### Change from non-shared workstation to shared workstation + +To change from a non-shared workstation to shared workstation, you must redeploy a configuration XML. + + + + **Sample Configuration File with all Applications Shared Computer Activation - Deferred Channel** + + + + + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Channel="Deferred"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being installed.
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="O365ProPlusRetail"
|SKU of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being downloaded
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| +|Updates Channel = "Deferred"
|The Update Channel for Office UNRESOLVED_TOKEN_VAL(365) ProPlus. This parameter should match the Channel build being installed. If it does the product will switch to the channel defined.
Example: The channel being installed is Current Channel and the Updates Channel is set to Deferred. When the client updates, Office 365 ProPlus will update to Deferred channel, which might or might not contain all the features/non-security updates that the Current Channel does.
| +|Enabled="TRUE"
|Updates are enabled.
| +|Property Name="SharedComputer Licensing" Value="1"
|Shared Computer Licensing is enabled
| + + **Steps to change from non-shared to shared workstation post-deployment** + + + + +1. Copy ODT and the configuration XML file to a local directory on the workstations to be deployed. + + +2. From an elevated command prompt with administrator privileges, run **setup.exe /configure .xml**. + + +3. Review the installation log. + + + +## Change update channels + +It is a preferred practice to change the update channel by changing it in the Office 2016 Group Policy object if required. The changing of channels will result in a 100% delta change to the product. For more information on switching channels, see [Best practices: Channel management](best-practices-channel-management.md). + + + + +## Rollback or downgrade strategy + +In the unlikely scenario that the pilot or production group deems that the newly updated build is not suitable for use, a rollback or downgrade can be completed in order to get the group back on a previously known good or approved build of Office 365 ProPlus. For more information on rollbacks, see [Best practices: Channel management](best-practices-channel-management.md). + + + + diff --git a/DeployOffice/best-practices-step-by-step-installation-using-dfs.md b/DeployOffice/best-practices-step-by-step-installation-using-dfs.md new file mode 100644 index 000000000..7d0bc4bec --- /dev/null +++ b/DeployOffice/best-practices-step-by-step-installation-using-dfs.md @@ -0,0 +1,316 @@ +--- +title: Best practices Step by step installation using DFS +ms.prod: OFFICE365 +ms.assetid: 5ebd1288-69ed-4425-a9cf-6253d6027005 +--- + + +# Best practices: Step by step installation using DFS + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + +This article describes how to install and manage Office UNRESOLVED_TOKEN_VAL(365) ProPlus by leveraging an existing Distributed File System (DFS). It also provides a high level description of the architecture components. +## Deploy Office365 ProPlus from DFS + + +### Create DFS folder structure + +Create the following folder structure in the network shares: + + + + +||| +|:-----|:-----| +|**Folder path**
|**Purpose**
| +|**\\\\Server\\Share\\O365**
|This is the parent folder to store all Office UNRESOLVED_TOKEN_VAL(365) ProPlus related items.
| +|**\\\\Server\\Share\\O365\\CC**
|Use this folder to store the most current Office UNRESOLVED_TOKEN_VAL(365) ProPlus Current Channel build that pilot users will receive.
| +|**\\\\Server\\Share\\O365\\FRDC**
|Use this folder to store the most current Office UNRESOLVED_TOKEN_VAL(365) ProPlus First Release for Deferred Channel build that pre-production users will receive.
| +|**\\\\Server\\Share\\O365\\DC**
|Use this folder to store the most current Office UNRESOLVED_TOKEN_VAL(365) ProPlus Deferred Channel build that production users will receive. Production channel should be Deferred Channel.
| +|**\\\\Server\\Share\\O365\\Archive\\%channel%**
|Use this folder to host N-1 previously known good builds in case a rollback or downgrade is needed.
| + + +### Download Office365 ProPlus builds + +The downloads will contain the Office UNRESOLVED_TOKEN_VAL(365) ProPlus build for the most up -to-date channel release. Specify all products and languages that will be deployed. + + + +The parameters and settings for the XML file can be found at [Reference: Configuration options for the Office Deployment Tool](https://technet.microsoft.com/en-us/library/jj219426.aspx). The parameters for Project and Visio 2016 volume licensing can be found at [Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016](https://technet.microsoft.com/library/mt703272.aspx). A graphical UI for creating the XML file can be found at the Office GitHub Repository [Office Click-To-Run Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + + **Download Current Channel build** + + + + +1. Download latest Current Channel build. For an example XML, see [Best practices: Sample configuration files for downloading Office 365 ProPlus](best-practices-sample-configuration-files-for-downloading-office-365-proplus.md). + + +2. Save the configuration file as **GetLatestCCBuild.xml**. + + +3. Confirm that Office Deployment Tool (setup.exe) is in **\\\\Server\\Share\\O365**. + + +4. Copy **GetLatestCCBuild.xml** to **\\\\Server\\Share\\O365\\CC**. + + +5. From an elevated command prompt with administrator privileges, run **\\\\Server\\Share\\O365\\Setup.exe /Download \\\\Server\\Share \\O365\\CC\\GetLatestCCBuild.xml**. + + +6. After it is run, Office Deployment Tool will download the latest Office UNRESOLVED_TOKEN_VAL(365) ProPlus Current Channel build into ** \\\\Server\\Share\\O365\\CC**. + + + **Download first release for Deferred Channel build** + + + + +1. Download latest First Release Deferred Channel build. For an example XML, see [Best practices: Sample configuration files for downloading Office 365 ProPlus](best-practices-sample-configuration-files-for-downloading-office-365-proplus.md) + + +2. Save the configuration file as **GetLatestFRDCBuild.xml**. + + +3. Confirm that Office Deployment Tool (setup.exe) is in **\\\\Server\\Share\\O365**. + + +4. Copy **GetLatestFRDCBuild.xml** to **\\\\Server\\Share\\O365\\FRDC**. + + +5. From an elevated command prompt with administrator privileges, run **\\\\Server\\Share\\O365\\Setup.exe /Download \\\\Server\\Share\\O365\\FRDC\\GetLatestFRDCBuild.xml**. + + +6. After it is run, Office Deployment Tool will download the latest Office UNRESOLVED_TOKEN_VAL(365) ProPlus First Release Deferred Channel build into ** \\\\Server\\Share\\O365\\FRDC**. + + + **Download Deferred Channel build** + + + + +1. Download latest Deferred Channel build. For an example XML, see [Best practices: Sample configuration files for downloading Office 365 ProPlus](best-practices-sample-configuration-files-for-downloading-office-365-proplus.md). + + +2. Save the configuration file as **GetLatestDCBuild.xml**. + + +3. Confirm that Office Deployment Tool (setup.exe) is in **\\\\Server\\Share\\O365**. + + +4. Copy **GetLatestDCBuild.xml** to ** \\\\Server\\Share\\O365\\DC**. + + +5. From an elevated command prompt with administrator privileges, run \\ **\\Server\\Share\\O365\\Setup.exe /Download \\\\Server\\Share\\O365\\DC\\GetLatestDCBuild.xml**. + + +6. After it is run, Office Deployment Tool will download the latest Office UNRESOLVED_TOKEN_VAL(365) ProPlus Deferred Channel build into **\\\\Server\\Share\\O365\\DC**. + + + +## Install Office365 ProPlus and remove legacy version of Office + + **Install Office 365 ProPlus and remove legacy version of Office - Current Channel build** + + + + +1. Copy OffScrub to the workstations to be deployed. + + +2. From an elevated command prompt with administrator privileges, run the **OffScrub.vbs** with the appropriate command line switches. + + +3. Review the OffScrub exit codes that are contained within the script **Offscrub.vbs**. + + > [!NOTE] + > Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes. +4. From an elevated command prompt with administrator privileges, run **\\\\Server\\Share\\O365\\Setup.exe /Configure \\\\Server\\Share\\O365\\CC\\CC_configuration.xml**. + + +5. Review the installation log. + + +6. Reboot the workstation to cleanup any files that were not cleared from the registry during the OffScrub process. + + + **Install Office 365 ProPlus and remove legacy version of Office - First Release for Deferred Channel build** + + + + +1. Copy OffScrub to the workstations to be deployed. + + +2. From an elevated command prompt with administrator privileges, run the **OffScrub.vbs** with the appropriate command line switches. + + +3. Review the OffScrub exit codes that are contained within the script **Offscrub.vbs**. + + > [!NOTE] + > Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes. +4. From an elevated command prompt with administrator privileges, run **\\\\Server\\Share\\O365\\Setup.exe /Configure \\\\Server\\Share\\O365\\FRDC\\FRDC_configuration.xml.xml**. + + +5. Review the installation log. + + +6. Reboot the workstation to cleanup any files that were not cleared from the registry during the OffScrub process. + + + **Install Office 365 ProPlus and remove legacy version of Office - Deferred Channel build** + + + + +1. Copy OffScrub to the workstations to be deployed. + + +2. From an elevated command prompt with administrator privileges, run the **OffScrub.vbs** with the appropriate command line switches. + + +3. Review the OffScrub exit codes that are contained within the script **Offscrub.vbs**. + + > [!NOTE] + > Each version of OffScrub will have the same or similar Error/Success codes. Review each script for respective codes. +4. From an elevated command prompt with administrator privileges, run **\\\\Server\\Share\\O365\\Setup.exe /Configure \\\\Server\\Share\\O365\\DC\\DC_configuration.xml.xml**. + + +5. Review the installation log. + + +6. Reboot the workstation to cleanup any files that were not cleared from the registry during the OffScrub process. + + + +## Post-deployment tasks + + +### Remove an application from Office ProPlus 365 + +You can remove a program from the Office Suite post deployment by using an XML configuration file. + + + +The parameters and settings for the XML file can be found at [Reference: Configuration options for the Office Deployment Tool](https://technet.microsoft.com/en-us/library/jj219426.aspx). A graphical UI for creating the XML file can be found at the Office GitHub Repository [Office Click-To-Run Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + + +1. Configure an XML file to exclude an application. For an example XML file, see [Best practices: Sample configuration files for downloading Office 365 ProPlus](best-practices-sample-configuration-files-for-downloading-office-365-proplus.md). + + +2. Save the configuration file as ** DCExcludeword_configuration.xml**. + + +3. Confirm that Office Deployment Tool (setup.exe) is in **\\\\Server\\Share\\O365**. + + +4. Copy **DCExcludeword_configuration.xml** to **\\\\Server\\Share\\O365\\DC**. + + +5. From an elevated command prompt with administrator privileges, run **\\\\Server\\Share\\O365\\Setup.exe /Configure \\\\Server\\Share\\O365\\DC\\DCExcludeword_configuration.xml**. + + + +### Add an application to Office ProPlus 365 + +You can add a program to the Office Suite post deployment by using an XML configuration file. + + + +The parameters and settings for the XML file can be found at [Reference: Configuration options for the Office Deployment Tool](https://technet.microsoft.com/en-us/library/jj219426.aspx). A graphical UI for creating the XML file can be found at the Office GitHub Repository [Office Click-To-Run Configuration XML Editor](http://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.mdl). + + + + +1. Configure an XML file by removing any excluded applications. + + +2. Save the configuration file as **DC_configuration.xml**. + + +3. Confirm that Office Deployment Tool (setup.exe) is in **\\\\Server\\Share\\O365**. + + +4. Copy **DC_configuration.xml** to ** \\\\Server\\Share\\O365\\DC**. + + +5. From an elevated command prompt with administrator privileges, run **\\\\Server\\Share\\O365\\Setup.exe /Configure \\\\Server\\Share\\O365\\DC\\DC_configuration.xml**. + + + +### Add a language + +You can add an additional language to Office UNRESOLVED_TOKEN_VAL(365) ProPlus. + + + +If the Office UNRESOLVED_TOKEN_VAL(365) ProPlus is on Current Channel greater than update 2062, use the newest ODT and XML install file that identifies the language to be installed. If Office UNRESOLVED_TOKEN_VAL(365) ProPlus is not using the above requirements, a full XML configuration must be used. + + + + **Sample XML Add Spanish to Post Deployment - Deferred Channel** + + + + + + +``` + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Channel="Deferred"
|The channel build of Office UNRESOLVED_TOKEN_VAL(365) ProPlus being installed.
| +|OfficeClientEdition="32"
|The architecture of Office being downloaded.
| +|Product ID="LanguagePack"
|Language Pack
| +|Language ID="en-us"
|The default language forOffice UNRESOLVED_TOKEN_VAL(365) ProPlus.
| + + +1. Save the configuration file as **DCLanguage_configuration.xml**. + + +2. Confirm that Office Deployment Tool (setup.exe) is in **\\\\Server\\Share\\O365**. + + +3. Copy **DCLangauge_configuration.xml** to **\\\\Server\\Share\\O365\\DC**. + + +4. From an elevated command prompt with administrator privileges, run **\\\\Server\\Share\\O365\\Setup.exe /Configure \\\\Server\\Share\\O365\\DC\\DCLanguage_configuration.xml**. + + + +## Change update channels + +It is a preferred practice to change the update channel by changing it in the Office 2016 Group Policy object if required. The changing of channels will result in a 100% delta change to the product. For more information on switching channels, see [Best practices: Channel management](best-practices-channel-management.md). + + + + +## Rollback or downgrade strategy + +In the unlikely scenario that the pilot or production group deems that the newly updated build is not suitable for use, a rollback or downgrade can be completed in order to get the group back on a previously known good or approved build of Office 365 ProPlus. For more information on rollbacks, see [Best practices: Channel management](best-practices-channel-management.md). + + + + diff --git a/DeployOffice/best-practices-system-center-configuration-manager-configuration-for-enterprise.md b/DeployOffice/best-practices-system-center-configuration-manager-configuration-for-enterprise.md new file mode 100644 index 000000000..25b0bdbc9 --- /dev/null +++ b/DeployOffice/best-practices-system-center-configuration-manager-configuration-for-enterprise.md @@ -0,0 +1,112 @@ +--- +title: Best practices System Center Configuration Manager configuration for enterprise managed +ms.prod: OFFICE365 +ms.assetid: a7e61b05-c07c-4a14-9888-3ea61b30f2fc +--- + + +# Best practices: System Center Configuration Manager configuration for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Enterprise Managed* will use their existing enterprise software deployment and management tool, System Center Configuration Manager, to deploy Office 365 client packages. The packages are set to install silently because task sequences are used to configure and install a stack of products. +The task sequence does the following: + + + + + +- Run OffScrub + + - Remove all Office 2007 components if found + + + - Remove all Office 2010 components if found + + + - Leave user data in place + + +- Install InfoPath 2013 MSI + + +- Install Office 365 ProPlus with proper channel, architecture, and languages from System Center Configuration Manager + + + +## OffScrub + +The following table includes the OffScrub command lines that Enterprise Managed used to remove previous versions of Office: + + + + +||| +|:-----|:-----| +|**Context for program**
|**Command line**
| +|Office 2007 Removal
|Command prompt cscript Offscrub2007.vbs clientall /bypass 1 /log c:\\temp /nocancel /q
| +|Office 2010 Removal
|Command prompt cscript Offscrub2010.vbs clientall /bypass 1 /log c:\\temp /nocancel /q
| +|Office 2013 MSI Removal
|Command prompt cscript OffScrub_O15msi clientall /bypass 1 /log c:\\temp /nocancel /q
| + + +## Office source location + +The following image shows an example of the Office source location for Enterprise Managed 32-bit Deferred Channel. The ODT setup.exe is next to the downloaded Office 365 client source files and install XML files. This allows for the file paths to always be relative; therefore, a source path is not needed for the install XML. This is recommended for System Center Configuration Manager deployments because you don't need to be concerned about the names of the distribution points of local CCMCache. + + + + + + + +![Office 365 online source location](images/495a5ea5-a10e-409a-8761-8862959c340a.png) + + + +The previous image is an example of an Office 365 ProPlus System Center Configuration Manager 32-bit Deferred Channel package: the ODT setup.exe, all of the install XML files, and all of the Office 365 client bits. + + + +Examples of the programs for the package are as follows: + + + + +||| +|:-----|:-----| +|**Context for program**
|**Command line**
| +|Deferred Channel 32-bit with Shared Computing Activation
|Setup.exe /configure Install_ProPlus_DC_VDI.xml
| +|Deferred Channel 32-bit for Desktop - North America
|Setup.exe /configure Install_ProPlus_DC_NA.xml
| +|Deferred Channel 32-bit for Desktop - LATAM
|Setup.exe /configure Install_ProPlus_DC_LATAM.xml
| +|Deferred Channel 32-bit Project Pro (VL)
|Setup.exe /configure Install_Project_DC.xml
| + +Individual languages are added as software programs and placed in the software catalog for users that want additional languages to self-provision. The install XMLs leverage the **Product ID="LanguagePack"** element. + + + + +||| +|:-----|:-----| +|**Context for program**
|**Command line**
| +|Greek
|Setup.exe /configure Install_Greek_LAP_DC.xml
| +|Spanish
|Setup.exe /configure Install_Spanish_LAP_DC.xml
| +|Malay
|Setup.exe /configure Install_Malay_LAP_DC.xml
| + + +## System Center Configuration Manager step-by-step configuration + +Reference the following links to configure System Center Configuration Manager to deploy and managed Office 365 ProPlus: + + + + +- [Deploy Office 365 ProPlus by using System Center Configuration Manager](https://technet.microsoft.com/en-us/library/dn708063.aspx) + + +- [Manage updates to Office 365 ProPlus with System Center Configuration Manager](https://technet.microsoft.com/en-us/library/mt628083.aspx) + + + diff --git a/DeployOffice/best-practices-uninstall-xml-files-for-cloud-managed.md b/DeployOffice/best-practices-uninstall-xml-files-for-cloud-managed.md new file mode 100644 index 000000000..38eab6874 --- /dev/null +++ b/DeployOffice/best-practices-uninstall-xml-files-for-cloud-managed.md @@ -0,0 +1,51 @@ +--- +title: Best practices Uninstall XML files for cloud managed +ms.prod: OFFICE365 +ms.assetid: c9ce5ffa-bfc7-4207-a6c0-c24fa9ae9db2 +--- + + +# Best practices: Uninstall XML files for cloud managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Cloud Managed* needs an uninstall XML file for the following package: +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus
|1 language
| + + +## Office 365 ProPlus + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being removed
| +|Language ID="en-us"
|The language being removed from Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Office to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Office 365 ProPlus
| + + diff --git a/DeployOffice/best-practices-uninstall-xml-files-for-enterprise-managed.md b/DeployOffice/best-practices-uninstall-xml-files-for-enterprise-managed.md new file mode 100644 index 000000000..a14257134 --- /dev/null +++ b/DeployOffice/best-practices-uninstall-xml-files-for-enterprise-managed.md @@ -0,0 +1,227 @@ +--- +title: Best practices Uninstall XML files for enterprise managed +ms.prod: OFFICE365 +ms.assetid: 8d86741d-51da-4b73-91bb-506579494bd3 +--- + + +# Best practices: Uninstall XML files for enterprise managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Enterprise Managed* needs uninstall XML files for the following packages: +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - North America Region
|3 languages
| +|Office 365 ProPlus - LATAM Region
|2 languages
| +|Office 365 ProPlus - AsiaPAC Region
|7 languages
| +|Office 365 ProPlus - EU Region
|6 languages
| +|Project Pro (VL)
|1 language
| +|Visio Pro (VL)
|1 language
| + + +## Example uninstall XML files + +The following are the *Enterprise Managed* example uninstall XML files to remove Office 365 clients. + + + + +### Office 365 ProPlus - North America Region + + +``` + +Configuration> + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being removed
| +|Language ID="ii-cc"
|The languages being removed from Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Office to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Office 365 ProPlus
| + + +### Office 365 ProPlus - LATAM Region + + +``` + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being removed
| +|Language ID="ii-cc"
|The languages being removed from Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Office to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Office 365 ProPlus
| + + +### Office 365 ProPlus - AsiaPac Region + + +``` + + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being removed
| +|Language ID="ii-cc"
|The languages being removed from Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Office to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Office 365 ProPlus
| + + +### Office 365 ProPlus - EU Region + + +``` + + + + + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being removed
| +|Language ID="ii-cc"
|The languages being removed from Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Office to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Office 365 ProPlus
| + + +### Project Pro (VL) + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="ProjectProXVolume"
|SKU of Office 365 ProPlus being removed
| +|Language ID="en-us"
|The language being removed from Project Pro (VL)
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Project Pro (VL) to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Project Pro (VL)
| + + +### Visio Pro (VL) + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="VisioProXVolume"
|SKU of Visio Pro (VL) being removed
| +|Language ID="en-us"
|The language being removed from Visio Pro (VL)
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Visio Pro (VL) to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Visio Pro (VL)
| + + diff --git a/DeployOffice/best-practices-uninstall-xml-files-for-locally-managed.md b/DeployOffice/best-practices-uninstall-xml-files-for-locally-managed.md new file mode 100644 index 000000000..70e5df8a2 --- /dev/null +++ b/DeployOffice/best-practices-uninstall-xml-files-for-locally-managed.md @@ -0,0 +1,154 @@ +--- +title: Best practices Uninstall XML files for locally managed +ms.prod: OFFICE365 +ms.assetid: d66205f9-cf21-43df-bb19-af18cf0048bb +--- + + +# Best practices: Uninstall XML files for locally managed + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* + + + + + *Locally Managed* needs uninstall XML files for the following packages: +||| +|:-----|:-----| +|**Package**
|**Languages**
| +|Office 365 ProPlus - CanAm Region
|2 languages
| +|Office 365 ProPlus - Germany
|1 language
| +|Project Pro
|1 language
| +|Visio Pro
|1 language
| +|Project Pro (VL)
|1 language
| +|Visio Pro (VL)
|1 language
| + + +## Example uninstall XML files + +The following are the *Locally Managed* example uninstall XML files for removing Office 365 clients. + + + + +### Office 365 ProPlus - CanAm Region + + +``` + + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being removed
| +|Language ID="ii-cc"
|The languages being removed from Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Office to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Office 365 ProPlus
| + + +## Office 365 ProPlus - Germany + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="O365ProPlusRetail"
|SKU of Office 365 ProPlus being removed
| +|Language ID="de-de"
|The language being removed from Office 365 ProPlus
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Office to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Office 365 ProPlus
| + + +## Project Pro + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="ProjectProRetail"
|SKU of Project Pro being removed
| +|Language ID="en-es"
|The language being removed from Project Pro
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Project Pro to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Project Pro
| + + +## Visio Pro + + +``` + + + + + + + + + + +``` + + **XML configuration file breakdown** + + + + +||| +|:-----|:-----| +|**Component**
|**Explanation**
| +|Product ID="VisioProRetail"
|SKU of Visio Pro being removed
| +|Language ID="en-es"
|The language being removed from Visio Pro
| +|FORCEAPPSHUTDOWN Value ="True"
|Forces any Office apps that are blocking the uninstall of Visio Pro to shut down. Data loss may occur.
| +|Display Level="None"
|No UI when removing Visio Pro
| + + diff --git a/DeployOffice/best-practices-update-channels.md b/DeployOffice/best-practices-update-channels.md new file mode 100644 index 000000000..9c4bf5723 --- /dev/null +++ b/DeployOffice/best-practices-update-channels.md @@ -0,0 +1,78 @@ +--- +title: Best practices Update channels +ms.prod: OFFICE365 +ms.assetid: 0a185e67-2b81-4c97-8c45-65984d8a9d9b +--- + + +# Best practices: Update channels + +> [!IMPORTANT] +> On April 20, we announced changes to better align the Office 365 ProPlus and Windows 10 update models. In that [blog post](https://go.microsoft.com/fwlink/p/?linkid=846981), we highlighted changes to the release cadence and the support duration of feature updates for Office 365 ProPlus. As part of these changes, Office 365 ProPlus is also changing the names of its update channels. > For more information about these changes, see [Overview of the upcoming changes to Office 365 ProPlus update management](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md). > As most of these changes take effect in September 2017, this content will be updated in the next few months. + + + + + *The Best Practices Guide includes deployment recommendations and real-world examples from the Office 365 Product Group and delivery experts from Microsoft Services. For a list of all the articles, see [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md).* +With the 2016 release of Office UNRESOLVED_TOKEN_VAL(365) ProPlus, Microsoft introduced the concept of update channels to allow IT admins to have more control over new feature rollouts and business application validation. IT admins should leverage all channels to create validation, communications, and training processes. Preexisting QA or validation groups should be used. + + + + +Security updates are released every month for each production update channel in support. The Deferred Channel builds are released on the second Tuesday of a month (Patch Tuesday), while the First Release for Deferred Channel and Current Channel builds are quality-driven rather than date-driven, and can vary from the patch Tuesday release cadence. The following sections should be reviewed in order for the customer to understand each update channel. +## Current Channel (CC) + +Current Channel for Office UNRESOLVED_TOKEN_VAL(365) ProPlus provides monthly releases that contain new or updated features, security updates, and non-security updates, such as updates that provide stability or performance improvements for Office. Not every Current Channel release contains all of these features and updates. A Current Channel release is supported only until the next Current Channel release is available; no new security updates are provided for previous Current Channel releases. + + + +Leveraging Current Channel is ideal for users and/or organizations that want to provide users with the newest Office features as soon as they are available, and are not concerned about testing these features before deploying to production. Current Channel is released at quality-driven intervals rather than date-driven intervals. Current Channel is ideal for users in a customer's pilot group that are evaluating new features and functionality prior to rolling the features out to the broad user community. + + + + +## First Release for Deferred Channel (FRDC) + +First Release for Deferred Channel for Office UNRESOLVED_TOKEN_VAL(365) ProPlus provides monthly releases that can contain new or updated features, security updates, and non-security updates, such as updates that provide stability or performance improvements for Office. It is intended to give pre-production users and compatibility testers a chance to adequately test the upcoming Deferred Channel release to identify possible issues that may need to be fixed with line-of-business applications, add-ins, and/or macros. First Release for Deferred Channel is a fully supported version of Office UNRESOLVED_TOKEN_VAL(365) ProPlus. When using the Deferred Channel for production users, it is strongly recommended to have approximately 10% of the overall end user population on First Release for Deferred Channel to do ample testing in preparing for the next Deferred Channel release. + + + + +## Deferred Channel (DC) + +Deferred Channel for Office UNRESOLVED_TOKEN_VAL(365) ProPlus provides releases every four months that can contain new features, security updates, and non- security updates, such as updates that provide stability or performance improvements for Office. Subsequent Deferred Channel builds, released monthly for three months after the primary Deferred Channel release, contains security updates only. Deferred Channel might not have all of the new features that are included in the most recent Current Channel. After it is released, no new features are added to the Deferred Channel and it will only receive monthly security updates. A Deferred Channel release is supported for eight months, but after the eight-month period no new security updates are provided. There will always be two Deferred Channel releases available. + + + +Deferred Channel is recommended for users and/or organizations that do not want to deploy the latest features of Office without adequate testing. Deferred Channel is also ideal for users and/or organizations that have a significant number of line-of-business applications, add-ins, and/or macros that need to be tested with each release. + + + + +> [!NOTE] +> Deferred Channel is the default update branch for Office UNRESOLVED_TOKEN_VAL(365) ProPlus 2016. + + + + + +## Update channel references + +The following links provide detailed information about update channels: + + + + +- [Overview of update channels for Office 365 ProPlus](https://technet.microsoft.com/en-us/library/mt455210.aspx) + + +- [Version and build numbers of update channel releases for Office 365 clients](https://technet.microsoft.com/en-us/library/mt592918.aspx) + + +- [Office 365 client update channel releases](https://technet.microsoft.com/en-us/office/mt465751) + + +- [What's new and improved in Office 2016 for Office 365](https://support.office.com/en-us/article/What-s-new-and-improved-in-Office-2016-for-Office-365-95c8d81d-08ba-42c1-914f-bca4603e1426?ui=en-US&rs=en-US&ad=US) + + + diff --git a/DeployOffice/change-management-for-office-365-clients.md b/DeployOffice/change-management-for-office-365-clients.md new file mode 100644 index 000000000..5fa9a7b3b --- /dev/null +++ b/DeployOffice/change-management-for-office-365-clients.md @@ -0,0 +1,715 @@ +--- +title: Change management for Office 365 clients +ms.prod: OFFICE365 +ms.assetid: 9d9fc2d3-23e1-4309-8ae6-12ef5b6a8dcd +--- + + + +# Change management for Office 365 clients + +> [!IMPORTANT] +> On April 20, we announced changes to better align the Office 365 ProPlus and Windows 10 update models. In that [blog post](https://go.microsoft.com/fwlink/p/?linkid=846981), we highlighted changes to the release cadence and the support duration of feature updates for Office 365 ProPlus. As part of these changes, Office 365 ProPlus is also changing the names of its update channels. > For more information about these changes, see [Overview of the upcoming changes to Office 365 ProPlus update management](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md). > As most of these changes take effect in September 2017, this content will be updated in the next few months. + + + + +The client applications that are included with Office 365 are now being released regularly with updates that provide new features and functionality together with security and other updates. Windows 10 has also adopted the new servicing model and is also releasing new functionality regularly. As an IT Professional, you need to understand this new servicing model and how you can manage the releases while your organization takes advantage of the new functionality. +This article gives you an overview of the new servicing model, and helps you understand the release channels and cadence, and how to effectively manage releases of the Office 365 client applications for your organization. + + + + +In this article: +- [A New Update Strategy: The Servicing Model](change-management-for-office-365-clients.md#ServicingModel) + + +- [Release Options](change-management-for-office-365-clients.md#Branches) + + +- [Release Cadences](change-management-for-office-365-clients.md#Cadence) + + +- [Types of Changes](change-management-for-office-365-clients.md#Changes) + + +- [Roles and Responsibilities](change-management-for-office-365-clients.md#Roles) + + +- [Manage Update Deployments](change-management-for-office-365-clients.md#Manage) + + +Download this information as a model poster in [Visio](https://go.microsoft.com/fwlink/?LinkId=626680) or [PDF](https://go.microsoft.com/fwlink/?LinkId=626681) format. + + + +![Servicing model poster](images/f0f92823-29ae-443e-af36-d913c6ba6486.png) + + + +For an overview, watch the following video. + + + +![Your browser does not support video. Install Microsoft Silverlight, Adobe Flash Player, or Internet Explorer 9.](images/MSN_Video_Widget.gif) + + + + + + + + + + + + +## A New Update Strategy: The Servicing Model + + +Both Windows 10 and Office 365 have adopted the servicing model for client updates. This means that new features, non-security updates, and security updates are released regularly, so your users can have the latest functionality and improvements. The servicing model also includes time for enterprise organizations to test and validate releases before adopting them. + + + + +### What is the Servicing Model? + +In a traditional development model it can take months of planning, development, and testing before a large release is ready. Traditional deployments take enterprises years to plan, evaluate test, pilot, and deploy and then maintain the entire environment. + + + +The following illustration shows a traditional release model: + + + + + + + +![Traditional release model](images/37437b6c-5325-4739-ac6a-0dca404329ca.png) + + + +The following illustration shows a traditional deployment model: + + + + + + + +![Traditional deployment model](images/45ce18de-b51b-4bda-8189-c593883ddd80.png) + + + +In a servicing model, new features and innovations can be developed and released in a quick cadence, so that customers are always seeing improvements. Because development has changed, so does the deployment process for an enterprise organization. Quicker release of features mean that you can evaluate, pilot, and deploy different sets of features at the same time. + + + +The following illustration shows releases in a servicing world: + + + + + + + +![Releases in a servicing world](images/64f9e1cf-db58-43bc-945a-9dc643eb6596.png) + + + +The following illustration shows deployment in a servicing world: + + + + + + + +![Deployment in a servicing world](images/03839cb7-6e68-4697-9eb4-194c7edba3c4.png) + + + + + + + + + + + + +### What's in it for Enterprise Organizations? + +You want up-to-date features, but you also want the control and support you need to run your business. With the variety of release programs for Windows 10 and Office 365, you can evaluate new features, pilot them with specific groups in your organization, and then deploy them widely to your organization. You can also keep specialty systems on a long-term build for control. + + + +Use the update option that's right for your devices and your business needs. We recommend the following: + + + + +||||| +|:-----|:-----|:-----|:-----| +|**Device type**
|![Phones and tablets](images/7686c89d-eff0-4ab2-8b28-5eed68967351.png)|![Laptops and desktops](images/99e17d65-144f-442b-9181-9090ec421e48.png)|![Specialty systems](images/4b7f1d61-6020-4781-b5a4-d5f87ee03bc3.png)| +|**Update option**
|iOS or Android devices receive regular updates from their respective app stores. Devices running the Office Universal apps automatically receive regular updates from the Microsoft store.
For Windows 10 devices, use Current Branch to get regular updates with the latest features.
|Use Current Branch (Windows) and Current Channel (Office 365) to get regular updates with the latest features.
Have custom add-ins? Choose Current Branch for Business (Windows) and Deferred Channel (Office 365) so you have time to test.
|Use Windows 10 Long Term Servicing Branch and Office Professional Plus 2016 client installs (using MSI files) for control.
| + + +#### Focus on your business, not managing the software. + +The following table explains ways you can focus on your business, not managing the software, with the Office 365 client applications. + + + + +||| +|:-----|:-----| +|**Stay up to date**
|Regular updates mean your users' phones, tablets, and desktops stay up to date with the latest fixes.
| +|**Mix and match programs**
|Follow your business needs - not all systems need to follow the same deployment model. You can even use different models for Windows and Office on the same devices.
| +|**Save on management**
|Allow automatic updates to the fully tested Current Branch for Business (Windows) and Deferred Channel (Office 365) instead of managing the software packages yourself.
| +|**Stay in the loop**
|See what's coming in the next releases and find out what security updates have been included by reviewing communications from Microsoft.
| +|**Manage risk**
|Use Current Branch for Business (Windows) and Deferred Channel or First Release for Deferred Channel (Office 365) to test critical line-of-business applications that must remain up and running.
| +|**Save on development**
|First, check the marketplace - others may have a solution that works. If you need custom development, use best practices to ensure add-ins work after updates.
| + + +## Release Options + + +You need to understand the different release options for Windows 10 and the Office 365 client applications so you can choose the right options for your business. You decide what works and choose the combinations of releases to support for your organization. This section provides an overview and helps you choose. + + + + +### Summary of Release Options + +Use the following table to choose the right release option for your business needs: + + + + + +|** ![Up to date innovation](images/c43eb782-f0b4-4592-a07c-4d2c01a68966.png)
Up to date innovation**|** ![Have time to evaluate](images/84c2cca8-ef2e-4fd9-8294-4232f3f012c9.png)
Have time to evaluate**|** ![Security always](images/21459b91-f971-416c-8cfe-0a85c2769520.png)
Security, always**| +|:-----|:-----|:-----| +|Get the latest features right away. Choose Current Branch (Windows 10) and Current Channel (Office 365).
| Test with your existing systems. Choose these releases:
Windows 10: Current Branch for Business
Office 365: Deferred Channel and First Release for Deferred Channel
|You'll always get the latest security updates, no waiting, whichever program you choose.
| + + +### Default channels for client applications + +Office 365 includes different sets of client applications. Office 365 Business includes the core Office applications (Word, Excel, PowerPoint, Microsoft Outlook, OneNote, and Publisher), and Office 365 ProPlus includes the core applications plus Skype for Business and Access. Project Online Desktop Client and Visio Pro for Office 365 also follow this release model. + + + +The following illustration shows these sets of client applications. + + + + + + + +![Default channels for client applications](images/bc32bed2-b7be-4652-93d0-4f0f90b97e8e.png) + + + +By default, the client applications for Office 365 are set to these channel releases: + + + + +- **Office 365 Business, Project Online Desktop Client, and Visio Pro for Office 365** are set to use Current Channel. + + +- **Office 365 ProPlus** is set to use Deferred Channel. + + +But you can determine which channel is used for your client applications, according to your business needs. + + + +For more information about the channels for Office 365 client applications, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md). + + + + +### Which Release Option? + +This table shows the release options for Windows 10 and Office 365 clients. + + + + + +|**Release Options**|**Available for Office 365 client?**|**Available for Windows 10?**| +|:-----|:-----|:-----| +|**Windows Insider Preview Branch** lets you preview features and give feedback.
|No
|Yes
| +|**Current Branch** gives your users the latest released features. It's great for your mobile users who bring their own devices, your sales force out in the field, and for test systems or pilot programs.
|No
|Yes
| +|**Current Channel** gives your users the latest released features. It's great for your mobile users who bring their own devices, your sales force out in the field, and for test systems or pilot programs.
|Yes
|No
| +|**First Release for Deferred Channel** gives you time to check out the features and test your customizations or processes.
|Yes
|No
| +|**Current Branch for Business** gives you a couple of months lead-time before you get the latest version. It's best for desktops and laptops in the office. Enjoy new features, and the fact that millions of users have tested and validate them.
|No
|Yes
| +|**Deferred Channel** gives you a couple of months lead-time before you get the latest version. It's best for desktops and laptops in the office. Enjoy new features, and the fact that millions of users have tested and validate them.
|Yes
|No
| +|**Office Professional Plus 2016 client installs (using MSI files)** is good for scenarios where maximum control is required and the device has limited internet access.
|No
|No
| +|**Long Term Servicing Branch** is best for scenarios where control over the operating system deployment is of prime importance.
|No
|Yes
| + +The release options at the top of the table provides the freshest features, those at the bottom provide the most administrative control. Freshness indicates rapid access to new features and the ability to provide feedback to Microsoft. You'll sacrifice features for extra control - use the most controlled options for specialty systems, like factory floors, air traffic control, or emergency room devices. Current Branch for Business (Windows) and Deferred Channel (Office 365) offer a balance between new features and control. + + + + +## Release Cadences + + +It is important to keep both Windows and your Office clients up to date. Office 365 and Windows 10 are working to align release cadences to make this easier. Both will have regular security updates and will have new features releasing 2 or 3 times per year. There is also a long-term service branch available for Windows 10 for specialty devices. + + + + +### Windows 10 Release Cadence + +Windows 10 has four types of release branches: + + + + +- **Windows Insider Preview** Join the [Windows Insider](https://insider.windows.com/) program to evaluate and provide feedback on pre-release features, and perform application compatibility validation testing. New features are released frequently. + + +- **Current Branch** After new features have been tested through the Windows Insider program, they are released along with bug fixes and security patches as the Current Branch. A new Current Branch is released a few times a year. + + +- **Current Branch for Business** The features from Current Branch are rolled into the Current Branch for Business a few times a year. Microsoft supports a Current Branch for Business release for at least 8 months. + + +- **Long Term Servicing Branch** This branch provides a supported OS platform for 10 years. Enterprises can choose to move to a new release or stay where they are at and skip to the next one. Long Term Servicing Branches are infrequently used for specialty devices. Use Office Professional Plus 2016 clients with these devices. + + +The following illustration shows the relationships between these releases for Windows 10. + + + + + + + +![Windows 10 release cadence](images/42471221-f1a5-4bd6-9d7e-5f24a3049330.png) + + + +Read [Windows 10 servicing options for updates and upgrades](https://go.microsoft.com/fwlink/?LinkId=626683) for more information. + + + + +### Office 365 Client Release Cadence + +Office 365 clients have the following types of releases: + + + + +- **Current Channel** New features, security updates, and fixes can be released to the Current Channel every month. This is the default release schedule for Office 365 Business clients. + + +- **First Release for Deferred Channel** You can validate this release for four months before it becomes a Deferred Channel release. New features are included only at the beginning of a release. This channel is refreshed with non-security updates and security updates every month. + + +- **Deferred Channel** The First Release for Deferred Channel is rolled up and released as the Deferred Channel every 4 months. No new features are added until the next Deferred Channel, although security updates will continue to be released. Each Deferred Channel is supported for an additional 4 months, at which point users must move to the next release. This is the default release schedule for Office 365 ProPlus clients. + + +The following illustration shows the relationships between these releases for Office 365 ProPlus. + + + + + + + +![Office 365 release cadence](images/99a17880-4029-44e9-b478-be4058c30f92.png) + + + + + + + + + + + + +### Office Mobile Apps + +Office Mobile Apps for iOS and Android have regular releases available through their respective app stores. Office Universal Apps for Windows have regular releases available through the Microsoft Store. + + + + +### Office Professional Plus 2016 client installs + +Security updates are made available for the Office clients that you install by using .MSI files as part of the Office Volume Licensing program. New features are not delivered outside of full product releases. Recommended for devices on the Long Term Servicing Branch of Windows 10. + + + + +### Deployment tools + +The following table lists the deployment tools that can be used for Windows 10 and the Office 365 client applications: + + + + + +|**Tool**|**Supported for Windows 10?**|**Supported for Office 365 clients?**| +|:-----|:-----|:-----| +|Windows Update for Business
|Yes
|No
| +|Windows Server Update Services
|Yes
|No
| +|System Center Configuration Manager
|Yes
|Yes
| +|Microsoft InTune
|Yes
|Yes
| +|3rd party software deployment tools
|Yes
|Yes
| + + +## Types of Changes + + +There are several types of changes that are made to Office 365 on a regular basis. The communication channels for those changes, and the actions that you might have to take for them will vary, depending on the type of change. + + + +This section explains the types of changes you can expect, when to expect changes, and what you need to do to be prepared for changes in Office 365. + + + + +### Types of Changes for the Office 365 Service and Client Applications + +Not all changes have the same impact on your users or require action. Some are planned and some unplanned by their nature (non-security updates and security updates aren't usually planned in advance). Depending on the type of change, the communication channel also varies. The following table lists the types of changes you can expect for the Office 365 service and client applications. + + + + + +||** ![Functionality](images/920badf4-7064-49b3-bc49-e61a033c4415.png)
Functionality**|** ![Non-security updates](images/88099880-fe32-4da5-9724-d9e11ff51d62.png)
Non-security updates**|** ![Security always](images/21459b91-f971-416c-8cfe-0a85c2769520.png)
Security**| +|:-----|:-----|:-----|:-----| +|**Type of change**
| Feature updates
New features or applications
Deprecated features
| Client hotfixes for issues
| Security patches
| +|**Advance notice?**
|30 days notice for changes that require action
|No, these are included in the monthly build for all channels
|No, these are included in the monthly build for all channels
| +|**Communication channel**
| Message Center
[Office 365 Roadmap](https://go.microsoft.com/fwlink/?LinkID=529454)
[Office Blog](https://go.microsoft.com/fwlink/?LinkId=626089)
[Office 365 Network](https://go.microsoft.com/fwlink/?LinkID=525063) in Yammer
| TechNet [Office 365 client update channel releases](https://go.microsoft.com/fwlink/?LinkID=626090) page
| Security bulletin
| +|**Requires tenant admin action?**
|Sometimes
|Rarely
|Rarely
| +|**What kind of action?**
| Change settings
Communicate changes to users
Validate customizations
| Change admin settings
|| +|**Requires testing?**
|Rarely - check business critical Add-ins
|Sometimes - testing the fix against processes or customizations
|Rarely
| +|**Examples of changes**
| Feature updates: PowerPoint - simpler process for embedding videos
New features or applications: Skype for Business
| Hotfixes based on customer reported bugs
|| + + +### Guidelines for managing change when using Office Add-ins: + + +- We recommend that customers use Current Channel to get the latest updates. If you have Office customizations or Add-ins deployed, you can use the Deferred Channel, which delays updates to Office until you have had the change to test and fix your customizations. To test and fix your customizations before updates are applied to Deferred Channel, use First Release for Deferred Channel. Use the Office Telemetry Dashboard to check Add-ins for compatibility. For more information, see [Compatibility and telemetry in Office](https://go.microsoft.com/fwlink/?LinkId=626610). + + +- If your developers built the Office Add-in, we suggest they update the code and redeploy the custom Office Add-in. + + +- If you built your customization using VBA, VSTO, or COM, consider rebuilding your customization as an Office Add-in, or check the Office Store to see if there is a 3rd-party Add-in that provides similar functionality. + + +- Consider decommissioning Office Add-in that are no longer used or have low utilization. + + +More information about [Office Add-ins](https://go.microsoft.com/fwlink/?LinkID=626869). + + + + +### Tips for Testing + +For functionality changes, you should test against your add-ins and other customizations to see if you need to update them. Use these tips for testing: + + + + +- Don't wait - have a pilot team use the Current Channel builds to start evaluating new features. Use the First Release for Deferred Channel if you need a longer lead time for testing. + + +- Use an Azure virtual environment to test against your customizations or processes. + + +- Align your work with the release schedule - schedule testing passes monthly. + + + +## Roles and Responsibilities + + +Responsibility for managing change is shared between Microsoft and you as the admin of your Office 365 tenancy. The balance of responsibility is different for an online service than it is for an on-premises server or client. + + + +Understand the roles both Microsoft and you need to play before, during, and after a change occurs to the service. + + + +Review what's included in each release on the [Office 365 client update channel releases](https://go.microsoft.com/fwlink/?LinkId=626090) page on TechNet. + + + + +### Balance of Responsibility + +In a service offering, the balance of responsibility for things such as hardware maintenance and security updates shifts to the service provider (Microsoft) instead of the customer (you). However, you still need to ensure that custom software continues to function as expected when updates are rolled out. + + + +For on-premises products, your organization takes on most of the responsibility for managing change. + + + +Your responsibility for change management is based on the type of service. The following chart summarizes the balance of responsibility for both Microsoft and the customer for online services and on-premises software. + + + + + +||**Office 365 service**|**Office 365 clients**|**On-premises clients and servers**| +|:-----|:-----|:-----|:-----| +|**Responsibility**
|**Microsoft's**
|**The Customers'**
|**Microsoft's**
|**The Customers'**
|**Microsoft's**
|**The Customers'**
| +|Provide new functionality
|X
||X
||X
|X
| +|Test new features for quality assurance
|X
||X
|X
|X
|X
| +|Communicate about new features
|X
|X
|X
|X
|X
|X
| +|Integrate custom software
|X
|X
|X
|X
||X
| +|Apply security updates
|X
|||X
||X
| +|Maintain system software
|X
|||X
||X
| +|Maintain hardware
|X
|||X
||X
| + + +### Microsoft's Role and Your Role + +Microsoft and you both play a role in managing change for Office 365 before, during, and after a change. + + + + +#### Before a change + +Microsoft's role + + + + +- Set expectations for service changes. + + +- Notify customers 30 days in advance for changes that require administrator action. + + +- Publish majority of new features and updates on the [Office 365 Roadmap](https://go.microsoft.com/fwlink/?LinkID=529454). + + +Customer's role + + + + +- Understand what to expect for changes and communications. + + +- Read Message Center, [Office 365 Roadmap](https://go.microsoft.com/fwlink/?LinkID=529454) and [Office Blog](https://go.microsoft.com/fwlink/?LinkId=626089) regularly. + + +- Set up pilot teams to preview new functionality using Current Channel. + + +- Review and update internal change management processes. + + +- Understand the Office 365 system requirements and check compliance. + + + +#### During a change + +Microsoft's role + + + + +- Roll change out to customers. + + +- Specifically for Office 365 clients: release a new Current Channel each month and new security and non-security updates for Deferred Channel. + + +- Monitor telemetry and support escalations for any unexpected issues. + + +Customer's role + + + + +- Check Message Center and review the additional information link. + + +- Take any action required (if applicable) and test any add-ins. + + +- If using an internal share for updates, download the latest builds and upload to your share. + + +- If a break/fix scenario is experienced, create a Support Request. + + + +#### After a change + +Microsoft's role + + + + +- Listen to customer feedback to improve rollout of future changes. + + +- Listen to feedback from the [Office 365 Network](https://go.microsoft.com/fwlink/?LinkID=525063) in Yammer and admin feedback tool. + + +- Update [Office 365 Roadmap](https://go.microsoft.com/fwlink/?LinkID=529454) statuses and add new features. + + +Customer's role + + + + +- Work with people in your organization to adopt the change (get help on the [Office 365 Success Center](http://go.microsoft.com/fwlink/?LinkID=523734)). + + +- Review change management processes and bottlenecks for opportunities to streamline, and use more Microsoft resources. + + +- Provide general feedback in the [Office 365 Network](https://go.microsoft.com/fwlink/?LinkID=525063) in Yammer and specific feedback in the admin feedback tool. + + +- Train users to provide app specific feedback using the Smile button in Office apps. + + + +## Manage Update Deployments + + +You choose when and how updates are deployed to your organization by configuring: + + + + +- **Which channel to use.** This controls how often updates are available. + + +- **Which update method to use (automatic or manual).** This controls how your client computers get the updates. + + + +### How to Apply Updates + +You can decide how updates are deployed to your users' computers. You can allow the client computers to automatically receive updates over the Internet or from an on-premises location. Alternatively, you might want to have more control by packaging the updates yourself and manually delivering them to client computers over your network. + + + + +#### Methods for applying Office updates to client computers + +The following table explains three methods you can use to apply Office updates to client computers. + + + + + +|**Automatic**|**Manual**| +|:-----|:-----| +|**From the Internet**
|**From an on-premises location**
|**From an on-premises location**
| +|Microsoft makes an updated build available on the Internet. The client computers automatically install the updates when they are available.
|An administrator downloads the updated build to an on-premises location. The client computers automatically install the updates when they are available.
|An administrator downloads the updated build to an on-premises location. The administrator uses scripts or software distribution tools to push the updated build to the client computers.
| + +The following illustration shows these methods: + + + + + + + +![Apply Office updates to clients](images/c8774868-5fc5-4f07-890a-8ae777d5d44d.png) + + + + + + + + + + + + +#### Do you need to control the delivery of updates? + +To decide which method to use, consider the following scenarios: + + + + +- Customizations + + - **Allow automatic updates for...**Users or computers that are primarily for productivity and don't use customizations or integrated solutions. + + Recommended Channel: 
Current Channel + + + - **Use manual delivery of updates for...**Users or computers that rely on customizations or integrated solutions that work with the Office 365 clients. + + Recommended Channel: 
Deferred Channel. Validate by using First Release for Deferred Channel. + + +- Managed or un-managed computers? + + - **Allow automatic updates from the Internet for...**Consumers and small businesses without an IT department. + + + - **Deploy from an on-premises location when...**You want to control when updates are pushed out to your organization's computers. + + + +### How to configure channels and update methods + +Use the following methods to configure which channels are used by which client computers and how those clients computers are updated: + + + + +- Office Deployment Tool + + +- Group Policy - for centralized administration of domain-joined computers. + + + +## See also + + + +#### Other Resources + + + + + + [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) + + + + [Windows 10 servicing options for updates and upgrades](https://go.microsoft.com/fwlink/?LinkId=626683) + + + + [Microsoft cloud IT architecture resources](https://go.microsoft.com/fwlink/?LinkId=690243) + + + + [Office 365 client update channel releases](https://go.microsoft.com/fwlink/?LinkId=626090) diff --git a/DeployOffice/choose-how-to-deploy-office-365-proplus.md b/DeployOffice/choose-how-to-deploy-office-365-proplus.md new file mode 100644 index 000000000..34b5e9a76 --- /dev/null +++ b/DeployOffice/choose-how-to-deploy-office-365-proplus.md @@ -0,0 +1,104 @@ +--- +title: Choose how to deploy Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: e471ef30-2a09-4767-a172-aa74e1dc4686 +--- + + +# Choose how to deploy Office 365 ProPlus + +## + + ** [Deploy with System Center Configuration Manager](https://docs.microsoft.com/en-us/sccm/sum/deploy-use/manage-office-365-proplus-updates)** How to deploy Office 365 ProPlus with Configuration Manager version 1702. For how to deploy with earlier versions , see [Deploy Office 365 ProPlus with System Center Configuration Manager](deploy-office-365-proplus-with-system-center-configuration-manager.md) + + + + ** [Deploy Office 365 ProPlus from a local source](deploy-office-365-proplus-from-a-local-source.md)** Step-by-step instructions for deploying Office 365 ProPlus from a shared folder on your network with the Office 2016 Deployment Tool. + + + + + + + + ** [Deploy Office 365 ProPlus from the cloud](deploy-office-365-proplus-from-the-cloud.md)** Step-by-step instructions for deploying Office 365 ProPlus from the Office CDN with the Office 2016 Deployment Tool. + + + + + + + + + + + + +## How to choose + +There are two basic ways that you can deploy Office 365 ProPlus in your organization: + + + + +- Have users install Office 365 ProPlus directly from the Office 365 portal. For more details on this method, see [Set up Office 365 for business](http://technet.microsoft.com/library/6a3a29a0-e616-4713-99d1-15eda62d04fa%28Office.14%29.aspx). + + +- Download the Office 365 ProPlus software to your local network and then deploy it to your users from a local share using the Office 2016 Deployment Tool, System Center Configuration Manager, or another software distribution tool. + + + + + + +![Office 365 deployment methods](images/3d236c2a-304c-44b3-9a73-d0fa8cc48437.jpg) + + + +Which deployment method you use depends on what's most important for your organization. For example, to install from the Office 365 portal requires the least amount of administrative setup, but gives you less control over the deployment. + + + +If you want more control over your deployment, download the Office 365 ProPlus software to an on-premises location, such as a local network share. You can then control the following: + + + + +- Which individual Office programs are installed. + + +- Where on the network Office 365 ProPlus is installed from. + + +- How Office 365 ProPlus is updated after it is installed. + + +- Which computers Office 365 ProPlus is installed on. + + +- Which users, if any, get the 64-bit version of Office 365 ProPlus. + + +- Which languages are available to install. + + +Also, by downloading Office 365 ProPlus to your local network, you can use many of the same tools that you already use to deploy and configure other versions of Office, including System Center Configuration Manager. + + + +Whichever deployment method you use, Office 365 ProPlus is installed and runs locally on the user's computer. Office 365 ProPlus is not a web-based version of Office. Users don't have to be connected to the Internet all the time to use it. + + + + +## Related Topics + + [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) + + + + [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md) + + + + diff --git a/DeployOffice/choose-how-to-manage-updates-to-office-365-proplus.md b/DeployOffice/choose-how-to-manage-updates-to-office-365-proplus.md new file mode 100644 index 000000000..9eac79c21 --- /dev/null +++ b/DeployOffice/choose-how-to-manage-updates-to-office-365-proplus.md @@ -0,0 +1,118 @@ +--- +title: Choose how to manage updates to Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: e486afce-ad31-4889-87a4-28796751bb86 +--- + + +# Choose how to manage updates to Office 365 ProPlus + + **Summary:** Compares different ways to update Office 365 ProPlus, including automatically from the Internet or from an on-premises location. + + + + +There are three ways that admins typically apply updates for Office 365 ProPlus: +- Automatically from the Internet + + +- Automatically from an on-premises location + + +- By installing an updated version of Office 365 ProPlus + + +Which way is right for your organization depends on how much administrative effort you want to expend and how much control that you want to have over the update process.In most cases, you use the Office Deployment Tool or Group Policy to [configure the appropriate update settings](configure-update-settings-for-office-365-proplus.md). +> [!IMPORTANT] +> Because individual updates aren't available for Office 365 ProPlus, you can't use Windows Update, Windows Server Update Services (WSUS), or System Center Configuration Manager to download and apply individual updates to Office 365 ProPlus. + + + + + +## Apply updates automatically from the Internet to Office 365 ProPlus + + +This is the default setting for Office 365 ProPlus. For example, if your users install Office 365 ProPlus themselves from the Office 365 portal, Office 365 ProPlus is configured to get updates automatically from the Internet. No additional user or administrative configuration is needed. + + + +Even if you use the Office Deployment Tool to deploy Office 365 ProPlus to your users, you can configure updates to be applied automatically from the Internet. + + + +This option might be a good choice for your organization if you have users who travel or work remotely and don't connect to the corporate network regularly. It's also the choice that requires the least amount of administrative effort. But, this option gives you the least amount of control over the update process. + + + + +## Apply updates automatically from an on-premises location to Office 365 ProPlus + + +You can configure Office 365 ProPlus to get updates automatically from a location on your network, such as a network share. You can configure the update location by using the Office Deployment Tool or Group Policy. + + + +This is a good option if you want more control over the version of Office 365 ProPlus that users have installed. For example, even if the June version of Office 365 ProPlus is available, you might want your users to continue using the May version. You might want to do this because you want to test to make sure that your line-of-business applications work with the June version. + + + + +> [!TIP] +> For an example of how to set up a group to test updates, [read this blog post about how to manage updates for Office 365 ProPlus](https://go.microsoft.com/fwlink/p/?LinkID=507547). + + + + +You'll have to use the Office Deployment Tool to [download updated versions of Office 365 ProPlus from the Internet](overview-of-the-office-2016-deployment-tool.md) to your local network. After it's downloaded, you can place the updated version on a network share that is close to the users. + + + + +## Apply updates by installing an updated version of Office 365 ProPlus + + +Instead of using automatic updates, you can deploy an updated version of Office 365 ProPlus to your users by using the Office Deployment Tool. You can use the Office Deployment Tool together with software distribution tools, such as System Center Configuration Manager or Microsoft Intune. + + + +This option is useful if you want to control which version of Office 365 ProPlus users have, and you want to control which users get updated and when they get updated. This option provides the most control, but also requires the most administrative effort. + + + +This option re-installs Office 365 ProPlus, but only new or changed files are downloaded to the user's computer. + + + +If you decide to use this option, you'll disable automatic updates. You can [control that setting](configure-update-settings-for-office-365-proplus.md) by using either the Office Deployment Tool or Group Policy. + + + + +## See also + + + +#### Other Resources + + + + + + [Choose how to deploy Office 365 ProPlus](choose-how-to-deploy-office-365-proplus.md) + + + + [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md) + + + + [Overview of the update process for Office 365 ProPlus](overview-of-the-update-process-for-office-365-proplus.md) + + + + [Configure update settings for Office 365 ProPlus](configure-update-settings-for-office-365-proplus.md) + + + + [End-user update notifications for Office 365 ProPlus](end-user-update-notifications-for-office-365-proplus.md) diff --git a/DeployOffice/configuration-options-for-the-office-2016-deployment-tool.md b/DeployOffice/configuration-options-for-the-office-2016-deployment-tool.md new file mode 100644 index 000000000..12095aca8 --- /dev/null +++ b/DeployOffice/configuration-options-for-the-office-2016-deployment-tool.md @@ -0,0 +1,278 @@ +--- +title: Configuration options for the Office 2016 Deployment Tool +ms.prod: OFFICE365 +ms.assetid: d3879f0d-766c-469c-9440-0a9a2a905ca8 +--- + + +# Configuration options for the Office 2016 Deployment Tool + +With the Office Deployment Tool (ODT), you can download and deploy Office 365 ProPlus to your client computers. The ODT gives you more control over an Office installation: you can define which products and languages are installed, how those products should be updated, and whether or not to display the install experience to your users. This article covers all the available options in the tool. To learn how to use the tool itself, see [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md). + + + + + +## Example of a standard configuration file + +The ODT consists of two files: setup.exe and configuration.xml. To work with the tool, you edit the configuration file to define what options you want, and then run setup.exe from the command line. For example, you can edit the configuration file to download the 32-bit English edition of Office, or you can edit the file to install the 32-bit English edition of Office with the EULA automatically accepted and without Publisher. + + + +When creating the configuration file, we recommend starting with an example file and updating it with the appropriate options for your environment. You can start by copying and pasting the example below into a text file and saving it with a name of your choosing. Use the file to modify the XML elements and attributes and use the reference table in this article to learn more details about each of the elements and attributes. + + + +This configuration file includes the most-commonly used elements and attributes, and can be used to download and install Office on a client computer + + + + + + +``` + + + + + + + + + + + + + + + + +``` + + + +|**Value**|**Description**| +|:-----|:-----| +|SourcePath="\\\\Server\\Share"
|Office will be downloaded to "\\\\server\\share" on your network and deployed using installation files at that location.
| +|OfficeClientEdition="32"
|Downloads and installs the 32-bit edition of Office
| +|Channel="Deferred"
|After installation, Office will be updated using the Deferred channel.
| +|Product ID="O365ProPlusRetail"
|Downloads and installs Office 365 ProPlus.
| +|Language ID="en-us"
Language ID="ja-jp"
|Downloads and installs English and Japanese versions of Office.
| +|Updates Enabled="TRUE" UpdatePath="\\\\Server\\Share"
|After installation, Office checks for updates at "\\\\server\\share" on your network.
| +|Display Level="None" AcceptEULA="TRUE"
|When installing Office, no user interface is displayed.
| +|Logging Level="Standard" Path="%temp%"
|Log files are stored in the %temp% folder.
| + + +## Configuration options for the Office Deployment Tool + +The following options apply to running the ODT in download, configure, or packager mode. + + + + + +|**Name**|**Description**|**Example**| +|:-----|:-----|:-----| +|**Add** element
|Defines the products and languages to download or install
| +``` + + + + + + + + + + +``` + +| +|**SourcePath** attribute (part of Add element)
|Defines the location of the Office installation files. If the ODT is run in download mode, defines where to save the files.
Optional. If not included, the ODT will look for installation files in the same folder as the tool, and then use the Office Content Delivery Network (CDN). If not included and the ODT is run in download mode, the Office installation files are downloaded to the same folder as the tool.
| `SourcePath="\\\\server\\share\\"`
`SourcePath="c:\\preload\\office"`
| +|**Version** attribute (part of Add element)
|Optional. The default is the latest available version of Office is used.
| `Version="16.0.6741.2056"`
| +|**OfficeClientEdition** attribute (part of Add element)
|Defines whether the 32-bit or 64-bit edition of Office 365 ProPlus is downloaded or installed.
Required.
| `OfficeClientEdition="32"`
`OfficeClientEdition="64"`
| +|**Channel** attribute (part of Add element)
|Defines which channel to use for updating Office after it is installed.
Optional. The default is **Deferred** for Office 365 ProPlus and **Current** for Visio Pro for Office 365 and Project Online Desktop Client.
For more information about update channels, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md).
| `Channel="Current"`
`Channel="Deferred"`
`Channel="FirstReleaseDeferred"`
`Channel="FirstReleaseCurrent"`
| +|**DownloadPath** attribute (part of Add element)
|Defines where the installation files are downloaded from. Most commonly used to distribute specific languages and products for Office from a central location on your network to another location.
To use this setting, run the ODT in download mode.
Optional. If not included, the files are downloaded from the Office CDN.
| `DownloadPath="\\\\serverb\\share\\"`
| +|**ForceUpgrade** attribute (part of Add element)
|When set to True, ForceUpgrade automatically upgrades from Office 365 ProPlus 2013 to Office 365 ProPlus 2016 without asking for input from the user. This attribute is often used alongside the Display element to hide the user interface during installation.
Optional. Default is **False**.
| `ForceUpgrade="FALSE` `"`
`ForceUpgrade="TRUE"`
| +|**Product** element
|Defines which products to download or install.
If you define multiple products, the products are installed in the order in the configuration file. The first product determines the context for the Microsoft Office First Run Experience.
You can use the Product element to add language packs to existing installations of Office 365 ProPlus. For more details on how, including an example configuration file, see [Add languages to existing installations of Office 365 ProPlus](overview-of-the-office-2016-deployment-tool.md#BKMK_updatelanguages).
| +``` + + + + + + + + +``` + +| +|**ID** attribute (part of Product element)
|Defines the ID of the product to download or install.
Required.
|Office 365 Product IDs:
`ID="O365ProPlusRetail"`
`ID="VisioProRetail"`
`ID="ProjectProRetail"`
For a list of all supported product IDs, see [Product IDs that are supported by the Office Deployment Tool for Click-to-Run](https://go.microsoft.com/fwlink/p/?LinkID=301891)
| +|**Language** element
|Defines which languages to download or install. To install the same language as the client's operating system, use "MatchOS" as the ID.
If you define multiple languages, the first language in the configuration file determines the Shell UI culture, including shortcuts, right-click context menus, and tooltips.
If you decide that you want to change the Shell UI language after an initial installation, you have to uninstall and reinstall Office.
| +``` + + + + +``` + +| +|**ID** attribute (part of Language element)
|Defines the ID of the language to download or install.
Required.
| `ID="en-us"`
`ID="ja-jp"`
`ID="MatchOS"`
For a list of all languages, see [Language identifiers](https://technet.microsoft.com/EN-US/library/cc179219%28v=office.16%29.aspx).
| +|**Display** element
|Defines what the user sees when Office is installed.
| +``` + + +``` + +| +|**Level** attribute (part of Display element)
|If **Level** is set to **None**, Office is installed with no user interface: no progress bars, completion screens, error messages, or other user interface are displayed.
If **Level** is set to **Full**, Office is installed with the normal installation experience.
Optional. Default is **Full**.
| `Level="None"`
`Level="Full"`
| +|**AcceptEULA** attribute (part of Display element)
|If **AcceptEULA** is set to **TRUE**, the user does not see a Microsoft Software License Terms dialog box.
If this attribute is set to **FALSE** or is not included, the user may see a Microsoft Software License Terms dialog box.
We recommend that administrators set **AcceptEULA** to **TRUE**.
This setting only applies if you install with the user's account. If you use System Center Configuration Manager or other software distribution tool that uses the SYSTEM account to install, then the setting is not applied.
Optional. Default is **FALSE**.
| `AcceptEULA="TRUE"`
`AcceptEULA="FALSE"`
| +|**ExcludeApp** element
|Defines which Office 365 ProPlus products should not be installed.
| +``` + + + + + + + + +``` + +| +|**ID** attribute (part of ExcludeApp element)
|Defines the ID of the product that should not be installed.
Required.
| `ID="Access"`
`ID="Excel"`
`ID="Groove"`
`ID="Lync"`
`ID="OneDrive"`
`ID="OneNote"`
`ID="Outlook"`
`ID="PowerPoint"`
`ID="Publisher"`
`ID="Word"`
For OneDrive for Business, use **Groove**. For Skype for Business, use **Lync**.
| +|**Logging** element
|Defines options for ODT logging
| +``` + + + +``` + +| +|**Level** attribute (part of Logging element)
|Turns logging on or off.
Optional. Default is **Standard**
| `Level="Off"`
`Level="Standard"`
| +|**Path** attribute (part of Logging element)
|Defines the location of the log files.
Optional. Default is **%temp%**.
| `Path="%temp%"`
`Path="\\\\server\\share\\userlogs\\"`
| +|**Property** element
|Defines certain Office behaviors and properties.
| +``` + + + + +``` + +| +|**Name** attribute (part of Property element)
|Defines the specific property whose value you want to set.
Required.
|| +|**Value** attribute (part of Property element)
|Defines the value of the named property.
|| +|**AUTOACTIVATE** property (part of Property element)
|Because Office 365 ProPlus is set to activate automatically, you should not set this property for Office 365 ProPlus products.
For other products, you can set **AUTOACTIVATE** to **1** to have the product activate automatically.
Optional. Default is **0**.
| +``` + + +``` + + +``` + + +``` + +| +|**FORCEAPPSHUTDOWN** property (part of Property element)
|When set to **TRUE**, forces any apps that are blocking the install of Office to shut down. Data loss may occur.
Optional. Default is **FALSE**.
| +``` + + + +``` + +| +|**PACKAGEGUID** property (part of Property element)
|By default, App-V packages created by the ODT share the same App-V Package ID. Administrators can use **PACKAGEGUID** to specify a different Package ID.
This allows you to publish multiple App-V packages of Officee to an App-V Management Server. But, this doesn't enable you to deploy more than one Office App-V package to a single computer.
You can use the ODT to create App-V packages for Office 365 ProPlus. Creating packages for the volume-licensed versions of Office Professional Plus or Office Standard is not supported.
Optional.
| +``` + + +``` + +The Package ID must follow the format of the example and can only use these characters:
0, 1, 2, 3, 4, 5, 6, 7, 8, 9, A, B, C, D, E, F
If you use any other characters, the App-V package is created with the default Package ID.
| +|**SharedComputerLicensing** property (part of Property element)
|**SharedComputerLicensing** to 1 if you deploy Office 365 ProPlus to shared computers by using Remote Desktop Services.
For more information, see [Overview of shared computer activation for Office 365 ProPlus](overview-of-shared-computer-activation-for-office-365-proplus.md).
Optional. Default value is **0**.
| +``` + + +``` + + +``` + + +``` + +| +|**PinIconsToTaskBar** property (part of Property element)
|Defines whether shortcut icons for Office products are added to the Windows taskbar in Windows 7, 8, and 8.1.
If you install Office using a system account, which is common when deploying with System Center Configuration ManagerS, the icons will not be pinned even if this property is set to True.
Optional. The default value is **True**.
| +``` + + +``` + + +``` + + +``` + +| +|**Remove** element
|Defines which products and languages to remove from a previous installation of Office 365 ProPlus.
To remove an installed language, you must provide both the product and the language, as in the example. For more information, see [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md).
| +``` + + + + + + +``` + +| +|**All** attribute (part of Remove element)
|If set to TRUE, all Office 365 ProPlus products and languages will be removed.
Optional. The default value is **FALSE**.
| `All="FALSE"`
`All="TRUE"`
| +|**Updates** element
|Defines how Office is updated after it's installed
| +``` + + +``` + +| +|**Enabled** attribute (part of Updates element)
|If set to **TRUE**, Office will check for updates. If set to **FALSE**, Office won't check for updates.
Optional. The default value is **TRUE**.
| `Enabled="TRUE"`
`Enabled="FALSE"`
| +|**UpdatePath** attribute (part of Updates element)
|Defines where the updates for Office come from.
If UpdatePath is not set or is set to empty (""), the location is set to the Office Content Delivery Network (CDN).
**UpdatePath** can specify a network, local, or HTTP path of a source for Office installation files. Environment variables can be used for network or local paths.
If you use Group Policy with the [Office 2016](https://www.microsoft.com/download/details.aspx?id=49030) Administrative Template files (ADMX/ADML), you can set **UpdatePath** by using the **Update Path** policy setting. You can find this policy setting under Computer Configuration\\Administrative Templates\\Microsoft Office 2016 (Machine)\\Updates.
Optional.
| `UpdatePath="\\\\server\\share\\"`
`UpdatePath="C:\\Preload\\Office"`
`UpdatePath="http://internalApps/Office/"`
| +|**TargetVersion** attribute (part of Updates element)
|Defines which version Office updates to.
If **TargetVersion** is not set or is set to empty (""), Office updates to the most recent version from the specified update path.
If **TargetVersion** is set to a specific build number, Office attempts to update to that version..
If you use Group Policy with the or [Office 2016](https://www.microsoft.com/download/details.aspx?id=49030) Administrative Template files (ADMX/ADML), you can set **TargetVersion** by using the **Target Version** policy setting. You can find this policy setting under Computer Configuration\\Administrative Templates\\Microsoft Office 2016 (Machine)\\Updates.
Optional.
| `TargetVersion="15.1.2.3"`
`TargetVersion="""`
| +|**Deadline** attribute (part of Updates element)
|Defines a deadline by which updates must be applied. The deadline is specified in Coordinated Universal Time (UTC).
You can use **Deadline** with **Target Version** to make sure that Office is updated to a particular version by a particular date. We recommend that you set the deadline at least a week in the future to allow users time to install the updates.
Prior to the deadline, users receive multiple reminders to install the updates. If Office isn't updated by the deadline, users see a notification that the updates will be applied in 15 minutes. This gives users the opportunity to save the Office documents that they are working on and to close any Office programs that are open. If users don't close the Office programs, the programs are closed automatically when the 15 minutes are up, which might result in data loss. After the Office programs are closed, the updates are applied automatically.
The deadline only applies to one set of updates. If you want to use a deadline to make sure that Office is always up-to-date, you must change the deadline every time that a new update for Office is available.
To use this attribute, Office must be running at least Service Pack 1 (version 15.0.4569.1507).
If you use Group Policy with the [Office 2016](https://www.microsoft.com/download/details.aspx?id=49030) Administrative Template files (ADMX/ADML), you can set **Deadline** by using the **Update Deadline** policy setting. You can find this policy setting under Computer Configuration\\Administrative Templates\\Microsoft Office 2016 (Machine)\\Updates.
Optional.
| `Deadline="05/16/2014 18:30"`
| +|**Channel** attribute (part of Updates element)
|Defines which channel to use for updating Office after it is installed. Note that there are two channel attributes: the channel for the Add element is used to specify an update channel while installing Office, and the channel for the Update element is used to change the channel for an existing installation of Office.
For more information about update channels, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md).
If you use Group Policy with the [Office 2016 Administrative Template files (ADMX/ADML)](https://go.microsoft.com/fwlink/p/?LinkID=626001), you can set **Channel** by using the **Update Channel** policy setting. You can find this policy setting under Computer Configuration\\Administrative Templates\\Microsoft Office 2016 (Machine)\\Updates. If enabled, this Group Policy setting takes precedence over the **Channel** value set by using the Office Deployment Tool.
Optional. The default is **Deferred** for Office 365 ProPlus and **Current** for Visio Pro for Office 365 and Project Online Desktop Client.
| `Channel="Current"`
`Channel="Deferred"`
`Channel="FirstReleaseDeferred"`
`Channel="FirstReleaseCurrent"`
| + + +## Related Topics + + [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md) + + + + [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) + + + + [Language identifiers](https://technet.microsoft.com/EN-US/library/cc179219%28v=office.16%29.aspx) + + + + diff --git a/DeployOffice/configure-update-settings-for-office-365-proplus.md b/DeployOffice/configure-update-settings-for-office-365-proplus.md new file mode 100644 index 000000000..2c417b0ae --- /dev/null +++ b/DeployOffice/configure-update-settings-for-office-365-proplus.md @@ -0,0 +1,115 @@ +--- +title: Configure update settings for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: a073ea21-62ed-40ef-8405-fd287f7d0b11 +--- + + +# Configure update settings for Office 365 ProPlus + + **Summary:** Explains how admins can use the Office Deployment Tool or Group Policy to configure update settings for Office 365 ProPlus. + + + + +There are two ways that you can configure update settings for Office 365 ProPlus in your organization: +- Office Deployment Tool + + +- Group Policy + + +Here are the update settings that you can configure by using the Office Deployment Tool or Group Policy. + +|**Update setting**|**Office Deployment Tool setting**|**Group Policy setting**| +|:-----|:-----|:-----| +|Set updates to occur automatically
|Enabled
|Enable automatic updates
| +|Specify a location to look for updates
|UpdatePath
|Update path
| +|Specify the version of Office 365 ProPlus to update to
|TargetVersion
|Target version
| +|Set a deadline by when updates have to be applied
|Deadline
|Update deadline
| +|Hide update notifications from users
|You can't configure this by using the Office Deployment Tool.
|Hide update notifications
| +|Hide the option to enable or disable Office automatic updates
|You can't configure this by using the Office Deployment Tool.
|Hide options to enable or disable updates
| + +By default, updates for Office 365 ProPlus are downloaded automatically from the Internet and applied in the background, without any user or administrator intervention. You can use these update settings to change that behavior and make other changes about how Office 365 ProPlus is updated.In most cases, you'll use either the Office Deployment Tool or Group Policy, not both, to configure update settings. If you do use both to configure a setting, the Group Policy setting overrides the setting configured by the Office Deployment Tool. +## Use the Office Deployment Tool to configure update settings for Office 365 ProPlus + + +Users can install Office 365 ProPlus themselves from the Office 365 portal, but using the Office Deployment Tool to deploy Office 365 ProPlus to your users gives you more control over the installation. This includes controlling how Office 365 ProPlus is updated. + + + +The settings that the Office Deployment Tool uses to install and update Office 365 ProPlus are contained in a configuration.xml file. This file is a text file that can be edited in Notepad. There is a [list of settings](configuration-options-for-the-office-2016-deployment-tool.md) that you can specify, including settings for configuring updates. + + + +For example, if you want Office 365 ProPlus to get updates automatically from a network share called _\\\\server\\updates_, you'd include the following line in your configuration.xml file: + + + + + + +``` + + +``` + +The update settings in the configuration.xml file are applied to Office 365 ProPlus when you use the Office Deployment Tool to deploy Office 365 ProPlus. If you decide to change these settings, you must update your configuration.xml file, and then run the Office Deployment Tool again. + + + + +## Use Group Policy to configure update settings for Office 365 ProPlus + + +If you have Windows Server and Active Directory Domain Services (AD DS) deployed in your organization, you can configure update settings for Office 365 ProPlus by using Group Policy. To do this, download the most current [Office 2016 Administrative Template files (ADMX/ADML)](https://www.microsoft.com/download/details.aspx?id=49030), which include the policy settings for Office 365 ProPlus. + + + + +> [!IMPORTANT] +> You must be running at least version 15.0.4605.1003 of Office 365 ProPlus, which was released in April 2014, to use the following policy settings:> Hide update notifications> Target version> Update deadline> Update path> To determine which version of Office 365 ProPlus is installed on a user's computer, go to **File > Account** in any Office program. The version is listed under the **Office Updates** section. + + + + +After you copy the Administrative Template files to AD DS, you'll find the update policy settings under Computer Configuration\\Policies\\Administrative Templates\\Microsoft Office 2016 (Machine)\\Updates in the Group Policy Management Console. You'll also find a description of how to configure each policy setting. + + + + + + + +![Group Policy settings updates](images/86a9781c-0e91-4e5d-b334-7a0d07d85466.jpg) + + + +If you decide to make a change later, update the Group Policy setting by using the Group Policy Management Console. The updated policy settings are automatically applied to Office 365 ProPlus, through the normal Group Policy update process. + + + +Group Policy settings can be used regardless of whether users install Office 365 ProPlus themselves from the Office 365 portal, or if you deploy Office 365 ProPlus to your users by using the Office Deployment Tool. + + + + +## See also + + + +#### Other Resources + + + + + + [Overview of the update process for Office 365 ProPlus](overview-of-the-update-process-for-office-365-proplus.md) + + + + [Choose how to manage updates to Office 365 ProPlus](choose-how-to-manage-updates-to-office-365-proplus.md) + + + + [End-user update notifications for Office 365 ProPlus](end-user-update-notifications-for-office-365-proplus.md) diff --git a/DeployOffice/configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md b/DeployOffice/configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md new file mode 100644 index 000000000..8aa8f9471 --- /dev/null +++ b/DeployOffice/configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md @@ -0,0 +1,192 @@ +--- +title: Configure updates of Office 365 ProPlus to prepare for the upgrade to the Office 2016 version +ms.prod: OFFICE365 +ms.assetid: 1ee534fd-56dd-40fc-a463-470e8d636f09 +--- + + +# Configure updates of Office 365 ProPlus to prepare for the upgrade to the Office 2016 version + + **Summary:** Help admins configure updates for Office 365 ProPlus to prepare for the upgrade to the Office 2016 version. + + + + +If you deployed the Office 2013 version of Office 365 ProPlus to the users in your organization, then you need to be aware of an upgrade coming from Microsoft. This will upgrade the Office apps, such as Word and Excel, from the Office 2013 version to the Office 2016 version. For information on the schedule for this upgrade, [review these key dates](upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Key). +> [!IMPORTANT] +> Support for the Office 2013 version of Office 365 ProPlus ended on February 28, 2017. For more information, see Microsoft Knowledge Base (KB) article [3199744.](https://support.microsoft.com/kb/3199744) + + + + +Not every Office 2013 installation is a candidate for this upgrade. Only Office 2013 installations that meet [certain criteria](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md#BKMK_Criteria) receive an upgrade notification from Microsoft. The first check is to see how Office is configured to get updates. As shown in the following table, only Office installations that are configured to get updates automatically from the Office Content Delivery Network (CDN) on the Internet are considered for this upgrade. + +|**Update configuration**|**Considered for upgrade**| +|:-----|:-----| +|Automatically from the Office Content Delivery Network (CDN) on the Internet
|Yes
| +|Automatically from a location other than the CDN, such as an internal network share
|No
| +|Automatic updates disabled
|No
| + +To determine if your Office installation could get upgraded, you first need to [determine if Office is configured to get updates from the CDN](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md#BKMK_DetermineCDN). If Office is configured to get updates from the CDN and you don't want Office to be upgraded, then you'll want to make a configuration change, such as the following: +- [Configure Office to get updates from a location other than the CDN](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md#BKMK_ConfigureNotCDN) + + +- [Prevent the upgrade but still get updates from the CDN](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md#BKMK_PreventAuto) + + +- [Disable updates entirely](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md#BKMK_Disable) + + +The upgrade isn't automatic. The user has to choose **Update Office** from within an Office app, such as Word, to begin the upgrade. For more information about the upgrade, [read this overview](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md). +> [!NOTE] +> This information also applies to Visio Pro for Office 365 and Project Online Desktop Client. It also applies to Office 365 Business, which is the version of Office that comes with some Office 365 plans, such as Business Premium. + + + + + +## Determine if Office is configured to get updates from the CDN + + +You can determine where Office gets updates from by using Registry Editor to view the registry on the computer where Office is installed. There are three places in the registry that you need to check, as listed in the following table. + + + + + +|**Registry key**|**Value**|**Description**| +|:-----|:-----|:-----| +|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office\\15.0\\ClickToRun\\Configuration
|UpdateUrl
| If this value appears in the registry, and it points to a location on your network, such as a network share, then Office isn't configured to get updates from the CDN.
But, you also need to check for the updatepath value in the registry.
| +|HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Office\\15.0\\Common\\OfficeUpdate
|updatepath
| If this value appears in the registry, and it points to a location on your network, such as a network share, then Office isn't configured to get updates from the CDN.
But, if the value appears in the registry, and the **Data** column is blank, then Office is configured to get updates from the CDN.
This location in the registry is used by Group Policy to store the configuration of the **Update Path** policy setting.
The setting of the updatepath value takes precedence over the setting of UpdateURL.
| +|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office\\15.0\\ClickToRun\\Configuration
|CDNBaseURL
| If the UpdateURL and the updatepath values don't appear in the registry, then Office is configured to get updates from the CDN.
In the **Data** column, you should see an address that begins with http://officecdn.microsoft.com
| + +This assumes that Office is configured to get updates automatically. You can check this in the following places in the registry: + + + + +- Under the HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office\\15.0\\ClickToRun\\Configuration key, the UpdatesEnabled value is set to TRUE. + + +- Under the HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Office\\15.0\\Common\\OfficeUpdate key, the enableautomaticupdates value is set to 1. + + +The enableautomaticupdates value appears in the registry if you use Group Policy and enable the **Enable automatic updates** policy setting. The setting of the enableautomaticupdates value takes precedence over the setting of the UpdatesEnabled value. + + + + +## Configure Office to get updates from a location other than the CDN + + +If you want to control when Office is upgraded, we recommend that you configure Office to get updates from a location on your internal network, such as a network share, instead of the CDN. You can configure this by using one of the following methods: + + + + +- Use Group Policy and enable the **Update path** policy setting. When you enable the policy setting, you need to provide a location, such as a network share. You can find this policy setting under Computer Configuration\\Policies\\Administrative Templates\\Microsoft Office 2013 (Machine)\\Updates in the Group Policy Management Console. + + +- Use the Office Deployment Tool and include the following line in the configuration.xml file: + + ``` + + + ``` + + + Replace _\\\\Server\\Share_ with the location on your network. Then, run the Office Deployment Tool in /configure mode on each computer that has Office installed. Be sure that you're using the [Office 2013 version of the Office Deployment Tool](https://go.microsoft.com/fwlink/p/?linkid=282642). + + +After you do this, use the Office 2013 version of the Office Deployment Tool to download updates for Office 2013 to your local network until you upgrade to Office 2016. + + + + +## Prevent the upgrade but still get updates from the CDN + + +There is another option. You can continue to have Office get updates from the CDN, but prevent Office from receiving this upgrade. + + + + +> [!IMPORTANT] +> Support for the Office 2013 version of Office 365 ProPlus ends on February 28, 2017. Therefore, we recommend that you upgrade to the Office 2016 version of Office 365 ProPlus as soon as possible. For more information, see Microsoft Knowledge Base (KB) article [3199744](https://support.microsoft.com/kb/3199744). + + + + +You can continue to get updates from the CDN, but prevent this upgrade, by using one of the following methods: + + + + +- Use Group Policy and disable the **Enable Automatic Upgrade** policy setting. You can find this policy setting under Computer Configuration\\Policies\\Administrative Templates\\Microsoft Office 2013 (Machine)\\Updates in the Group Policy Management Console. + + +- In the registry, under the HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Office\\15.0\\Common\\OfficeUpdate key, add a DWORD value named enableautomaticupgrade. Set the **Value data** to 0. + + +- Use the Office Deployment Tool and include the following line in the configuration.xml file: + + ``` + + ``` + + + Then, run the Office Deployment Tool in /configure mode on each computer that has Office installed. Be sure that you're using the [Office 2013 version of the Office Deployment Tool](https://go.microsoft.com/fwlink/p/?linkid=282642). + + + +## Disable updates entirely + + +To prevent this upgrade, you can also disable updates entirely, but in most cases this isn't recommended. That's because it means you won't be getting security updates of Office. + + + +If you plan to upgrade and update Office by using by using enterprise software deployment software, such as System Center Configuration Manager, you might want to disable automatic updates. You can disable automatic updates by using one of the following methods: + + + + +- Use Group Policy and disable the **Enable automatic updates** policy setting. You can find this policy setting under Computer Configuration\\Policies\\Administrative Templates\\Microsoft Office 2013 (Machine)\\Updates in the Group Policy Management Console. + + + + +- Use the Office Deployment Tool and include the following line in the configuration.xml file: + + ``` + + ``` + + + Then, run the Office Deployment Tool in /configure mode on each computer that has Office installed. Be sure that you're using the [Office 2013 version of the Office Deployment Tool](https://go.microsoft.com/fwlink/p/?linkid=282642). + + + +## See also + + + +#### Other Resources + + + + + + [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) + + + + [Plan your upgrade from Office 365 ProPlus 2013 to 2016](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md) + + + + [Upgrade from Office 365 ProPlus 2013 to 2016](upgrade-from-office-365-proplus-2013-to-2016.md) + + + + [Overview of the upgrade of Office 365 ProPlus to the Office 2016 version](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md) diff --git a/DeployOffice/delay-receiving-feature-updates-from-deferred-channel-for-office-365-proplus.md b/DeployOffice/delay-receiving-feature-updates-from-deferred-channel-for-office-365-proplus.md new file mode 100644 index 000000000..4ad8195eb --- /dev/null +++ b/DeployOffice/delay-receiving-feature-updates-from-deferred-channel-for-office-365-proplus.md @@ -0,0 +1,113 @@ +--- +title: Delay receiving feature updates from Deferred Channel for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 42a703ac-618c-4cb1-bc29-3014de45692b +--- + + + +# Delay receiving feature updates from Deferred Channel for Office 365 ProPlus + +Office 365 clients that get updates from [Deferred Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_CBB), such as Office 365 ProPlus, receive new features for the Office 2016 apps every four months — in February, June, and October. If Office is configured to receive updates automatically from the Office Content Delivery Network (CDN), then you get these feature updates from Deferred Channel automatically. + + + + + +> [!IMPORTANT] +> The release cadence for Deferred Channel is changing. The next feature update for Deferred Channel is scheduled for September 2017, instead of October. After that, Deferred Channel will get new features every January and July. For more information, see [Overview of the upcoming changes to Office 365 ProPlus update management](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md). + + + + + +If you have a specific business need to delay receiving these feature updates from Deferred Channel, you can configure Office to not receive these feature updates, but still receive the most current security updates. + + + + +For example, if you're currently using Version 1609 of Deferred Channel, which was released in February 2017, you can continue using it and getting security updates for it until September 2017. But, as of June 13, 2017, there's another version available from Deferred Channel, Version 1701, which provides new features. Version 1701 is the default version for Deferred Channel. If you don't specify which version you want, you get updated to Version 1701. Therefore, if you want to continue getting updates for Version 1609 of Deferred Channel, you have to specify that's the version you want. This will require you to perform some manual steps every month. +## Delay receiving feature updates from Deferred Channel when using the Office Content Delivery Network (CDN) + +To continue to get security updates for Version 1609 from the Office CDN, you need to do the following: + + + + +- Configure Office to get the latest build of Version 1609 of Deferred Channel from the Office CDN. As of June 13, 2017, the latest build is 7369.2139. + + +- On the second Tuesday of the following months - for example, on July 11, 2017 - refer to [this table](version-and-build-numbers-of-update-channel-releases.md#BKMK_ByVersion) to determine the latest build number for Version 1609. The second Tuesday of each month is when Microsoft releases a new build with security updates for Deferred Channel. + + +- Once you have the latest build number, re-configure Office to get this latest build of Version 1609 of Deferred Channel. + + +To configure Office to update to a specific version, you can use either Group Policy or the Office Deployment Tool. Once the target version is set, Office attempts to update to that version the next time it looks for updates. + + + +The following table provides information about the relevant Group Policy and Office Deployment Tool settings. The table also includes the registry value that is set when you use Group Policy or the Office Deployment Tool. + + + + + +|**Configuration tool**|**Setting**|**Registry value and key**|**Additional information**| +|:-----|:-----|:-----|:-----| +|Group Policy
|Target Version
|Value: updatetargetversion
Key: HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Office\\16.0\\Common\\OfficeUpdate
|You can find this policy setting under Computer Configuration\\Administrative Templates\\Microsoft Office 2016 (Machine)\\Updates.
If you use the Group Policy setting, its setting takes precedence over the setting configured by the Office Deployment Tool.
| +|Office Deployment Tool
|TargetVersion
|Value: updatetoversion
Key: HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office\\ClickToRun\\Configuration
|You configure this attribute in the Updates element in the configuration.xml file.
Your xml file should look something like the following example.
``` ```If you use the Office Deployment Tool, you need to re-run setup.exe, with your configuration.xml file, on each computer in order to update this setting.
| + +On the second Tuesday of each month, until September 2017, you need to update the Group Policy setting or the configuration.xml with the latest build number for Version 1609 of Deferred Channel. For example, for June 2017, you specify the target version as 16.0.7369.2139. + + + + +> [!NOTE] +> Another possibility is to run the following command from an elevated command prompt: > C:\\Program Files\\Common Files\\Microsoft Shared\\ClickToRun\\OfficeC2RClient.exe /update user updatetoversion="16.0.7369.2139"> When you run this command, Office looks at the configured update location, such as the Office CDN, and tries to update to the specified version. This update happens immediately, instead of waiting for the next time Office is scheduled to look for updates, which could be in a few days. + + + + + +## Delay receiving feature updates from Deferred Channel when using an internal network location + +If you don't want to get updates from the Office CDN, you can use Group Policy or the Office Deployment Tool to specify the location for Office to look for updates. For example, every month you can use the Office Deployment Tool to download the latest build of Version 1609 of Deferred Channel to a file share on your local network. Then, you can use Group Policy or the Office Deployment Tool to configure Office to look at that file share for updates. For more information, see [Configure update settings for Office 365 ProPlus](configure-update-settings-for-office-365-proplus.md). + + + +To download the latest build with the Office Deployment Tool, you need to configure both the Version and the Channel attributes in the Add element of the configuration.xml file. + + + + +## See also + + +#### Other Resources + + + + + + [Version and build numbers of update channel releases](version-and-build-numbers-of-update-channel-releases.md) + + + + [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) + + + + [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) + + + + [Office 365 client update channel releases](https://technet.microsoft.com/office/mt465751) + + + + [Download the Office Deployment Tool (Office 2016 version)](http://go.microsoft.com/fwlink/p/?LinkID=626065) + + + + [Download the Office 2016 Administrative Template files (ADMX/ADML) for Group Policy](https://www.microsoft.com/download/details.aspx?id=49030) diff --git a/DeployOffice/deploy-office-365-proplus-as-part-of-an-operating-system-image.md b/DeployOffice/deploy-office-365-proplus-as-part-of-an-operating-system-image.md new file mode 100644 index 000000000..dd867e285 --- /dev/null +++ b/DeployOffice/deploy-office-365-proplus-as-part-of-an-operating-system-image.md @@ -0,0 +1,166 @@ +--- +title: Deploy Office 365 ProPlus as part of an operating system image +ms.prod: OFFICE365 +ms.assetid: 16cf763b-78a4-43dc-b05f-3efade197c0d +--- + + +# Deploy Office 365 ProPlus as part of an operating system image + +You can include [Office 365 ProPlus](about-office-365-proplus-in-the-enterprise.md) as part of an operating system image that you deploy to users in your organization. You just need to make sure you don't activate Office 365 ProPlus when you create the image. That's because you need your users to activate their Office 365 ProPlus installations by signing in with their accounts. + + + + +Here are the basic steps of how to include Office 365 ProPlus when you create and deploy an operating system image. +## + + + +### Step 1: Install and configure the operating system for the image + + +To start, install and configure the operating system on a test computer. There are several free tools from Microsoft to help you do this, such as [Windows Assessment and Deployment Kit (Windows ADK)](https://go.microsoft.com/fwlink/p/?LinkID=312996) and [Microsoft Deployment Toolkit (MDT)](https://go.microsoft.com/fwlink/p/?LinkID=268150). + + + + +### Step 2: Install Office 365 ProPlus for the image by using the Office Deployment Tool + + +To install Office 365 ProPlus on the test computer, first download the Office 2016 version of the Office Deployment Tool from the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkID=626065). + + + +Then, use the [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md) to download the Office 365 ProPlus software to your local network. You also use the Office Deployment Tool to install Office 365 ProPlus on to the test computer. + + + +Remember, you don't want to activate Office 365 ProPlus when you do the installation. + + + +To prevent Office 365 ProPlus from trying to automatically activate during the installation, perform a silent installation. To do this, in the [configuration.xml file](configuration-options-for-the-office-2016-deployment-tool.md) that the Office Deployment Tool uses, include the following line: + + + + + + + +When you set **Level** to **None**, you don't see any user interface elements during the installation. You won't see anything that shows the progress of the installation and you won't see any error messages. + + + + +> [!IMPORTANT] +> Don't sign in to the Office 365 portal to install Office 365 ProPlus from the **software** page. If you do, activation occurs automatically.> Also, don't save the setup file from the Office 365 portal to the test computer. Even if you run the setup file, which will have a file name similar to Setup.X86.en-us_O365ProPlusRetail_d079c594-698d-4370-9174-7c00f76abf00_TX_PR_.exe, from the test computer, activation occurs automatically. + + + + +After the installation is complete, don't open any Office programs. If you open an Office program, you are prompted to sign-in and activate. Even if you don't sign in and you close the **Activate Office** dialog box, a temporary product key is installed. You don't want any kind of Office 365 ProPlus product key installed in your operating system image. + + + +If you accidentally open an Office program, you'll have to uninstall Office 365 ProPlus, restart the computer, and then install Office 365 ProPlus again. + + + + +### Step 3: Install and configure other programs for the operating system image + + +Next, install other programs that you want to include as part of the operating system image. This includes Office add-ins you want to provide to your users. + + + +Remember not to open any Office programs. After you have created the image, you can test on another computer that Office and the add-ins work correctly. + + + + +### Step 4: Check that an Office 365 ProPlus product key is not installed in the image + + +Before you save the image, you should check to make sure that no product key for Office 365 ProPlus is installed. To do this, use the ospp.vbs script. This script is installed on the computer when Office 365 ProPlus is installed. + + + +For example, at a command prompt, run the following command: + + + + cscript.exe "%programfiles%\\Microsoft Office\\Office15\\ospp.vbs" /dstatus + + + +You should see ****, as shown in the following screen shot. + + + + + + + +![No installed product key detected](images/aa1e234d-c2d1-471f-bf7f-9b11adc8b4b4.jpg) + + + +The location of the ospp.vbs script depends on whether you install the 32-bit or 64-bit version of Office 365 ProPlus and whether you install on a 32-bit or 64 bit version of the operating system. The following table lists the possible locations of the ospp.vbs script. + + + + + +|**Version of Office 365 ProPlus**|**Version of operating system**|**Location of ospp.vbs file**| +|:-----|:-----|:-----| +|32-bit
|32-bit
|%programfiles%\\Microsoft Office\\Office15\\
| +|32-bit
|64-bit
|%programfiles(x86)%\\Microsoft Office\\Office15\\
| +|64-bit
|64-bit
|%programfiles%\\Microsoft Office\\Office15\\
| + + +### Step 5: Save the operating system image + + +You can use Windows ADK or MDT 2012 to save the operating system image file that you'll deploy to your users. You can also use [System Center Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkID=312997). + + + + +### Step 6: Test that the operating system image works + + +Deploy the operating system image to another test computer. Then, open the Office programs to make sure they are set up as you want. If you have a test user account for your Office 365 subscription, you can test that activation works. + + + +After you finish your tests, don't save an image of the test computer. + + + + +### Step 7: Deploy the operating system image to your users + + +After you test your operating system image, you can deploy it to your users. There are many ways that you can deploy the image to computers in your organization. For example, you can use Windows ADK, MDT 2012, Configuration Manager, scripts, or other enterprise software deployment tools. + + + +Users are prompted to activate Office 365 ProPlus when they open their first Office program, as seen in the following screen shot. + + + + + + + +![Activate Office](images/9cb7eef4-0ce6-428a-8f96-890e5237d17a.png) + + + +As long as the computer is connected to the Internet, the user just needs to sign in when prompted, and then activation occurs automatically. + + + + diff --git a/DeployOffice/deploy-office-365-proplus-by-using-remote-desktop-services.md b/DeployOffice/deploy-office-365-proplus-by-using-remote-desktop-services.md new file mode 100644 index 000000000..82de19e08 --- /dev/null +++ b/DeployOffice/deploy-office-365-proplus-by-using-remote-desktop-services.md @@ -0,0 +1,175 @@ +--- +title: Deploy Office 365 ProPlus by using Remote Desktop Services +ms.prod: OFFICE365 +ms.assetid: af9d7621-8c2c-4181-84b4-27778b1e7920 +--- + + +# Deploy Office 365 ProPlus by using Remote Desktop Services + +If you use Remote Desktop Services (RDS) to provide shared computers to users in your organization, you can install Office 365 ProPlus on those computers. But, you have to use the Office Deployment Tool and enable [shared computer activation](overview-of-shared-computer-activation-for-office-365-proplus.md) to do the installation. + + + + +The following are two common RDS scenarios: +- Install Office 365 ProPlus on an RDS server. + + +- Install Office 365 ProPlus on a shared virtual machine. + + + +## What you need to get started + + +The following is a list of prerequisites that you need to deploy Office 365 ProPlus with RDS: + + + + +- An [Office 365 plan](https://go.microsoft.com/fwlink/p/?LinkId=510587) that includes Office 365 ProPlus. Also, make sure that you [Assign or remove licenses for Office 365 for business](http://technet.microsoft.com/library/997596b5-4173-4627-b915-36abac6786dc%28Office.14%29.aspx) for Office 365 ProPlus. + + > [!NOTE] + > You also can use RDS to deploy Visio Pro for Office 365 or Project Online Desktop Client, if you have a subscription plan that includes those products. +- The Office 2016 version of the Office Deployment Tool, which is available on the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkID=626065). You can download the Office 365 ProPlus software to your local network by using the [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md). + + +- Any supported version of Office 365 ProPlus. + + +- A supported version of RDS, which includes any of the following: + + - Windows Server 2008 R2 + + + - Windows Server 2012 + + + - Windows Server 2012 R2 + + + - Windows Server 2016 + + +- Reliable connectivity between the shared computer and the Internet. + + This is required because the shared computer must be able to contact the Office Licensing Service on the Internet to obtain a license for each user who uses Office 365 ProPlus on the computer and then activate Office 365 ProPlus. Internet connectivity is also needed to renew the license, which occurs every few days. + + +- A separate user account for each user who logs on to the shared computer. + + +- A server that supports [Hyper-V](https://go.microsoft.com/fwlink/p/?LinkId=510585) if you're deploying Office 365 ProPlus on a shared virtual machine. + + + +## Install Office 365 ProPlus on an RDS server + + +In this scenario, you install Office 365 ProPlus on a computer configured as a Remote Desktop Session Host server. This enables multiple users to connect remotely to this computer. The users can each run Office 365 ProPlus programs, such as Word or Excel, at the same time. + + + +Here are the basic steps of how to install Office 365 ProPlus on an RDS server: + + + + +1. Install and configure Windows Server. + + +2. Install and configure the Remote Desktop Session Host role service. + + For example, [follow these steps to install RD Session Host](https://go.microsoft.com/fwlink/p/?LinkId=510582) on Windows Server 2008 R2. + + For users to be able to connect remotely to the server to use Office 365 ProPlus, their accounts must be members of the Remote Desktop Users group on the RD Session Host server. + + +3. [Create a configuration.xml file](configuration-options-for-the-office-2016-deployment-tool.md) that includes the following lines: + + ``` + + + + + ``` + + + You set the display level to "None" to do a silent installation of Office 365 ProPlus. This prevents Office 365 ProPlus from trying to activate during the installation. This also means that you won't see any user interface elements during the installation, such as the progress of the installation or error messages. + + You use the SharedComputerLicensing setting to enable [shared computer activation](overview-of-shared-computer-activation-for-office-365-proplus.md), which is required to use Office 365 ProPlus on a shared computer. + + +4. Use the [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md) and the configuration.xml file to install Office 365 ProPlus on the RD Session Host server. + + +At this point, users can connect to the RD Session Host server and use Office 365 ProPlus. Users can connect to the server by using Remote Desktop Connection, which is available in Windows, or by using other [Remote Desktop clients](https://go.microsoft.com/fwlink/p/?LinkId=510586). + + + + +## Install Office 365 ProPlus on a shared virtual machine + + +In this scenario, you install Office 365 ProPlus as part of an operating system image, such as one running Windows 8.1. Then, you use RDS and Hyper-V to create a group of virtual machines based on that image. These virtual machines can be shared by multiple users. In RDS, this is known as either a virtual desktop pool or a pooled virtual desktop collection, depending on which version of RDS that you're using. + + + + +> [!NOTE] +> You can also use RDS to assign a virtual machine to a specific user. RDS calls that a personal virtual desktop. In that scenario, you don't use shared computer activation, because the virtual machine isn't shared among multiple users. + + + + +Here are the basic steps of how to configure RDS to deploy Office 365 ProPlus on a shared virtual machine: + + + + +1. Create the operating system image: + + - Follow the instructions to [deploy Office 365 ProPlus as part of an operating system image](deploy-office-365-proplus-as-part-of-an-operating-system-image.md). In Step 2 of the instructions, make sure that your configuration.xml file also includes the following line to enable shared computer activation: + + ``` + + + ``` + + - You also need to [make some RDS-specific changes on the virtual machine](https://go.microsoft.com/fwlink/p/?LinkId=510584), such as enabling Remote Desktop. + + +2. Install and configure Windows Server. + + +3. Install and configure RDS. + + For example, [follow these steps to deploy a virtual desktop pool](https://go.microsoft.com/fwlink/p/?LinkId=510583) on Windows Server 2008 R2. + + +After you've completed all the RDS configuration steps, users can connect to any of the virtual machines and run Office 365 ProPlus. + + + + +## Related Topics + + + [Overview of shared computer activation for Office 365 ProPlus](overview-of-shared-computer-activation-for-office-365-proplus.md) + + + + [Troubleshoot issues with shared computer activation for Office 365 ProPlus](troubleshoot-issues-with-shared-computer-activation-for-office-365-proplus.md) + + + + [Remote Desktop Services in Windows Server 2008 R2](https://go.microsoft.com/fwlink/p/?LinkID=268148) + + + + [Remote Desktop Services Overview (Windows Server 2012 and Windows Server 2012 R2)](https://go.microsoft.com/fwlink/p/?LinkID=268149) + + + + diff --git a/DeployOffice/deploy-office-365-proplus-from-a-local-source.md b/DeployOffice/deploy-office-365-proplus-from-a-local-source.md new file mode 100644 index 000000000..5e2798950 --- /dev/null +++ b/DeployOffice/deploy-office-365-proplus-from-a-local-source.md @@ -0,0 +1,318 @@ +--- +title: Deploy Office 365 ProPlus from a local source +ms.prod: OFFICE365 +ms.assetid: 35d4cb3b-4cc9-4bc9-9f20-eaf3c50f8331 +--- + + +# Deploy Office 365 ProPlus from a local source + +This article gives step-by-step instructions for how to use the Office 2016 Deployment Tool (ODT) to deploy Office 365 ProPlus to client computers from a shared folder on your network. As part of this deployment, we will install multiple languages, use two update channels for Office, and exclude an Office application. + + + + +The steps in this article can apply to a variety of environments, but we'll base our examples on the following infrastructure and requirements: +- Users have local admin privileges on their client computers + + +- Office 365 ProPlus will be deployed in English and Japanese + + +- Most clients will receive updates to Office from Deferred Channel + + +- A small set of pilot clients will receive earlier updates from First Release for Deferred Channel + + +- Office will be installed without Publisher on all clients + + +- Office will install silently on all clients + + +- After install, all updates to Office will come directly from the Office Content Delivery Network (CDN) + + +Based on these requirements, we'll create two deployment groups: group one will receives updates from Deferred Channel and group two will receive updates from First Release for Deferred Channel: + +|**Group**|**Requirements**| +|:-----|:-----| +|Group 1: Deferred
|Office 365 ProPlus in English and Japanese, no Publisher, silent installation, and updates come from the Office CDN. Updates to Office come from Deferred channel, which is the default choice.
| +|Group 2: First Release for Deferred
|Same as above, except updates to Office come from First Release for Deferred Channel.
| + +Each group will need a unique set of Office installation files: one that comes from the most recent release of Deferred Channel, and one that comes from the most recent release of the First Release for Deferred Channel. To download and deploy these different releases of Office to our two groups, we'll create two configuration files, which are used to define which versions of Office to download and deploy. Each of the configuration files downloads and deploys a different build of Office: one from Deferred Channel and one from First Release for Deferred Channel. For more details on the update channels, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md).This article includes recommendations on how to deploy Office 365 ProPlus and why we make those recommendations. We can't cover all possible situations, of course, so we've aimed for a common scenario that can be used as a template for your own deployment. Where appropriate, we link to reference articles for further customizing your Office deployment, such as adding more languages +## Create shared folders for Office installation files and updates + +Because we're deploying Office 365 ProPlus from a local source, we have to create folders to store the Office installation files. We'll create one parent folder and two child folders, one for the version of Office from Deferred Channel and one for the version of Office from First Release for Deferred Channel. This structure is similar to the Office CDN structure. + + + + **Step 1: Create the following folders:** + + + + + +|**Folder Path**|**Purpose**| +|:-----|:-----| +|\\\\Server\\Share\\O365
|Stores the Office Deployment Tool and the configuration files that define how to download and deploy Office
| +|\\\\Server\\Share\\O365\\DC
|Stores the Office 365 ProPlus installation files from Deferred Channel
| +| [\\\\Server\\Share\\O365\\FRDC](file://\\\\Server\\Share\\O365\\FRDC)
|Stores the Office 365 ProPlus installation files from First Release for Deferred Channel
| + +These folders will include all the Office installation files we need to deploy. You can create whatever structure works for your organization, of course, but we'll refer to this setup in our examples. + + + + **Step 2: Assign Read permissions for your users** + + + +Installing Office from a shared folder requires only that the user have Read permission for that folder, so we'll assign Read permission to everyone. For details about how to create shared folders and assign permissions, see [Shared Folders](http://go.microsoft.com/fwlink/p/?LinkId=184710) + + + + +> [!NOTE] +> In our example, we have just one shared folder on the network, but many organizations make the Office installation files available from multiple locations. Using multiple locations can help improve availability and minimize the effect on network bandwidth. For example, if some of your users are located in a branch office, you can create a shared folder in the branch office. Those users can then install Office from the local network. You can use the Distributed File System (DFS) role service in Windows Server to create a network share that is replicated to multiple locations. For more information, see [DFS Management](https://technet.microsoft.com/library/cc732006.aspx). + + + + + +## Download the installation files for Office 365 ProPlus + +We'll use the Office 2016 Deployment Tool (ODT) to download the installation files for Office from the Office Content Delivery Network (CDN). The deployment tool is run from the command line and uses a configuration file to determine what settings to apply when downloading or deploying Office. + + + + **Step 1: Download the Office 2016 Deployment Tool** + + + +Download the Office 2016 Deployment Tool from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=49117) to \\\\Server\\Share\\O365 (or the folder you created above). If you've already downloaded the ODT, make sure you have the latest version. + + + +After downloading the file, run the self-extracting executable file, which contains the Office 2016 Deployment Tool executable (setup.exe) and a sample configuration file (configuration.xml). + + + + **Step 2: Create a configuration file for group 1** + + + +To download and deploy Office 365 ProPlus for group 1, we'll create a configuration file that defines the appropriate settings for the Office 2016 Deployment Tool. + + + +Using a text editor, copy and paste the following into a text file and save it as **config-group1-DC.xml** in the **\\\\Server\\Share\\O365** folder. + + + + + + +``` + + + + + + + + + + + + + +``` + +This configuration file is used to download Office installation files and then deploy them to the group 1 users. Here's more detail on how the XML settings define what to download and what to install: + + + + + +|**Value**|**Description**| +|:-----|:-----| +|SourcePath="\\\\Server\\Share\\O365\\DC"
|Office will be downloaded to and then installed from **\\\\server\\share\\O365\\DC** on our network.
| +|OfficeClientEdition="32"
|Downloads and installs the 32-bit edition of Office
| +|Channel="Deferred"
|Downloads and installs the Office installation files from Deferred Channel
| +|Product ID="O365ProPlusRetail"
|Downloads and installs Office 365 ProPlus
| +|Language ID="en-us"
Language ID="ja-jp"
|Downloads and installs English and Japanese versions of Office
| +|ExcludeApp ID="Publisher"
|When installing Office, Publisher will be excluded
| +|Updates Enabled="TRUE"
|After installation, Office will check for updates
| +|UpdatePath=""
|After installation, updates for Office will come from the Office CDN
| +|Channel="Deferred"
|After installation, updates to Office will come from Deferred Channel
| +|Display Level="None"
|Installs Office silently, without displaying the user interface.
| +|AcceptEULA="TRUE"
|When installing Office, accepts the Microsoft Software License Terms automatically
| + +Note that the Office installation files and Office updates will come from Deferred Channel. For more details on the most recent version of Office based on the different update channels, see [Office 365 client update channel releases](https://technet.microsoft.com/en-us/office/mt465751.aspx). + + + + **Step 3: Create a configuration file for group 2** + + + +Using a text editor, copy and paste the following into a text file and save it as **config-group2-FRDC.xml** in the \\\\Server\\Share\\O365 folder. + + + + + + +``` + + + + + + + + + + + + + +``` + +This configuration file is used to download Office installation files and then deploy them to the group 2 users. The settings are exactly the same as the first configuration file, except the source path points to a different folder (FRDC), and the installation channel and update channel are both set to First Release for Deferred. + + + + **Step 4: Customize the configuration files for your environment** + + + +To change the options from our example, you can edit the XML elements and attributes in the configuration files. For example, if you want to add a third language, you can insert an additional language element with the appropriate ID. You can also create additional configuration files for other groups you want to deploy to, such as a group that needs to receive updates from a different channel. + + + +For more information about the configuration options, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md). + + + + **Step 5: Run the ODT executable in download mode for group 1** + + + +From a command prompt, run the ODT executable in download mode and with a reference to the configuration file for group 1: + + + + `\\\\server\\share\\O365\\setup.exe /download \\\\server\\share\\O365\\config-group1-DC.xml` + + + +The files should begin downloading immediately. After running the command, go to **\\\\server\\share\\O365\\DC** (or the download location you defined in the configuration file) and look for an Office folder with the appropriate files in it. + + + +If you run into problems, make sure you have the newest version of the ODT and make sure your configuration file and command reference the correct location. You can also troubleshoot issues by reviewing the log file in the %temp% directory. + + + + **Step 6: Run the ODT executable in download mode for group 2** + + + +From a command prompt, run the ODT executable in download mode and with a reference to the configuration file for group 2: + + + + `\\\\server\\share\\O365\\setup.exe /download \\\\server\\share\\O365\\config-group2-FRDC.xml` + + + +The files should begin downloading immediately. After running the command, go to **\\\\server\\share\\O365\\FRDC** (or the download location you defined in the configuration file) and look for an Office folder with the appropriate files in it. + + + + +## Deploying Office 365 ProPlus + +To deploy Office, we'll provide two commands that users can run from their client computers. The first command installs Office for client computers in group 1 and the second for group 2. The commands run the ODT in configure mode and with a reference to the appropriate configuration file, which defines which version of Office to install on the client computer. + + + +Users who run these commands must have local admin privileges on their computer and must have read permissions to the share ( **\\\\server\\share\\O365**, in our case). + + + + **Step 1: Run the commands for group 1** + + + +From the client computers for group 1, run the following command from a command prompt with admin privileges: + + + + `\\\\Server\\Share\\O365\\setup.exe /configure \\\\Server\\Share\\O365\\config-group1-DC.xml` + + + + **Step 2: Run the commands for group 2** + + + +From the client computers for group 2, run the following command from a command prompt with admin privileges: + + + + `\\\\Server\\Share\\O365\\setup.exe /configure \\\\Server\\Share\\O365\\config-group2-FRDC.xml` + + + +This command is the same as group 1, except that it references the configuration file for group 2. + + + + +> [!NOTE] +> Most organizations will use this command as part of a batch file, script, or other process that automates the deployment. In those cases, you can run the script under elevated permissions, so the users will not need to have admin privileges on their computers. + + + + + **Step 3: Verify that installation was successful** + + + +After running the command, the Office installation should start immediately. If you run into problems, make sure you have the newest version of the ODT and make sure your configuration file and command reference the correct location. You can also troubleshoot issues by reviewing the log file in the %temp% and %windir%\\temp directories. + + + + +## Related Topics + + [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) + + + + [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md) + + + + [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) + + + + [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md) + + + + diff --git a/DeployOffice/deploy-office-365-proplus-from-the-cloud.md b/DeployOffice/deploy-office-365-proplus-from-the-cloud.md new file mode 100644 index 000000000..d99919049 --- /dev/null +++ b/DeployOffice/deploy-office-365-proplus-from-the-cloud.md @@ -0,0 +1,233 @@ +--- +title: Deploy Office 365 ProPlus from the cloud +ms.prod: OFFICE365 +ms.assetid: b18a9110-0d14-46ec-af54-a22793ef6b38 +--- + + +# Deploy Office 365 ProPlus from the cloud + +This article gives step-by-step instructions for how to deploy Office 365 ProPlus to client computers from the Office Content Delivery Network (CDN) by using the Office 2016 Deployment Tool (ODT). The article is intended for administrators in enterprise environments working with hundreds or thousands of computers. If you want to install Office on a single device or small number of devices, we recommend reviewing [Download and install or reinstall Office 365 or Office 2016 on your PC or Mac](http://technet.microsoft.com/library/4414eaaf-0478-48be-9c42-23adc4716658%28Office.14%29.aspx) or [Use the Office 2016 offline installer](http://technet.microsoft.com/library/f0a85fe7-118f-41cb-a791-d59cef96ad1c%28Office.14%29.aspx). + + + + +The steps in this article can apply to a variety of environments, but we'll base our examples on the following infrastructure and requirements: +- Office will be installed and receive updates from the Office CDN + + +- Office 365 ProPlus will be deployed in English and in the 32-bit edition only + + +- Most clients will receive updates to Office from Deferred Channel + + +- A small set of pilot clients will receive earlier updates from First Release for Deferred Channel + + +- Office will install silently on all clients + + +- Users have local admin privileges on their client computers + + +Based on these requirements, we'll create two deployment groups: group 1 will receives updates from Deferred Channel and group 2 will receive updates from First Release for Deferred Channel. + +|**Group**|**Requirements**| +|:-----|:-----| +|Group 1: Deferred
|Office 365 ProPlus in English, silent installation, and installation and updates come from the Office CDN. Updates to Office come from Deferred channel, which is the default choice.
| +|Group 2: First Release for Deferred
|Same as above, except updates to Office come from First Release for Deferred Channel.
| + +Each group will need a unique configuration file, which is used to define which versions of Office to deploy. Each configuration file deploys a different build of Office: one from Deferred Channel and one from First Release for Deferred Channel. For more details on the update channels, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md). +## Download the Office 2016 Deployment Tool and create the configuration files + +We'll use the Office 2016 Deployment Tool (ODT) to deploy Office from the Office CDN. The deployment tool is run from the command line and uses a configuration file to determine what settings to apply when deploying Office. + + + + **Step 1: Create a shared folder** + + + +Create the shared folder **\\\\Server\\Share\\O365** and assign read permissions for your users. + + + +You can create whatever structure works for your organization, of course, but we'll refer to this setup in our examples. For details about how to create shared folders and assign permissions, see [Shared Folders](https://technet.microsoft.com/library/cc770406.aspx). + + + + **Step 2: Download the Office 2016 Deployment Tool** + + + +Download the Office 2016 Deployment Tool from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=49117) to \\\\Server\\Share\\O365. If you've already downloaded the ODT, make sure you have the latest version. + + + +After downloading the file, run the self-extracting executable file, which contains the Office 2016 Deployment Tool executable (setup.exe) and a sample configuration file (configuration.xml). + + + + **Step 3: Create a configuration file for group 1** + + + +To download and deploy Office 365 ProPlus for group 1, we'll create a configuration file that defines the appropriate settings for the Office 2016 Deployment Tool. + + + +Using a text editor, copy and paste the following into a text file and save it as **config-group1-DC.xml** in the \\\\server\\share\\O365 folder. + + + + + + +``` + + + + + + + + + + +``` + +This configuration file is used to deploy Office to the group 1 users. Here's more detail on how the XML settings define what to install: + + + + + +|**Value**|**Description**| +|:-----|:-----| +|OfficeClientEdition="32"
|Installs the 32-bit edition of Office
| +|Channel="Deferred"
|Installs the Office installation files from Deferred Channel
| +|Product ID="O365ProPlusRetail"
|Installs Office 365 ProPlus
| +|Language ID="en-us"
|Installs English version of Office
| +|Display Level="None"
|Installs Office silently, without displaying the user interface.
| +|AcceptEULA="TRUE"
|When installing Office, accepts the Microsoft Software License Terms automatically
| + +Note that the Office installation files and Office updates will come from Deferred Channel. For more details on the most recent version of Office based on the different update channels, see [Office 365 client update channel releases](https://technet.microsoft.com/en-us/office/mt465751.aspx). + + + + **Step 4: Create a configuration file for group 2** + + + +Using a text editor, copy and paste the following into a text file and save it as **config-group2-FRDC.xml** in the \\\\Server\\Share\\O365 folder. + + + + + + +``` + + + + + + + + + + +``` + +This configuration file is used deploy Office to the group 2 users. The settings are exactly the same as the first configuration file, except the installation channel and update channel are both set to First Release for Deferred. + + + + **Step 5: Customize the configuration files for your environment** + + + +To change the options from our example, you can edit the XML elements and attributes in the configuration files. For example, if you want to add a second language, you can insert an additional language element with the appropriate ID. You can also create additional configuration files for other groups you want to deploy to, such as a group that needs to receive updates from a different channel or a group that needs the 64-bit edition of Office. + + + +For more information about the configuration options, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md). + + + + +## Deploying Office 365 ProPlus + +To deploy Office, we'll provide two commands that users can run from their client computers. The first command installs Office for client computers in group 1 and the second for group 2. The commands run the ODT in configure mode and with a reference to the appropriate configuration file, which defines which version of Office to install on the client computer. + + + +Users who run these commands must have local admin privileges on their computer and must have read permissions to the share (\\\\server\\share\\O365, in our case). + + + +Most organizations will use this command as part of a batch file, script, or other process that automates the deployment. In those cases, you can run the script under elevated permissions, so the users will not need to have admin privileges on their computers. + + + + **Step 1: Run the commands for group 1** + + + +From the client computers for group 1, run the following command from a command prompt with admin privileges: + + + + `\\\\Server\\Share\\O365\\setup.exe /configure \\\\Server\\Share\\O365\\config-group1-DC.xml` + + + + **Step 2: Run the commands for group 2** + + + +From the client computers for group 2, run the following command from a command prompt with admin privileges: + + + + `\\\\Server\\Share\\O365\\setup.exe /configure \\\\Server\\Share\\O365\\config-group2-FRDC.xml` + + + +This command is the same as group 1, except that it references the configuration file for group 2. + + + + **Step 3: Verify that installation was successful** + + + +After running the command, the Office installation should start immediately. If you run into problems, make sure you have the newest version of the ODT and make sure your configuration file and command reference the correct location. You can also troubleshoot issues by reviewing the log file in the %temp% and %windir%\\temp directories. + + + + +## Related Topics + + [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) + + + + [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md) + + + + [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) + + + + [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md) + + + + diff --git a/DeployOffice/deploy-office-365-proplus-with-system-center-configuration-manager.md b/DeployOffice/deploy-office-365-proplus-with-system-center-configuration-manager.md new file mode 100644 index 000000000..f7df24ed6 --- /dev/null +++ b/DeployOffice/deploy-office-365-proplus-with-system-center-configuration-manager.md @@ -0,0 +1,296 @@ +--- +title: Deploy Office 365 ProPlus with System Center Configuration Manager +ms.prod: OFFICE365 +ms.assetid: 4dd6a023-0a5d-4dc9-9bad-ff70e01840b8 +--- + + +# Deploy Office 365 ProPlus with System Center Configuration Manager + +This article applies to System Center 2012 R2 Configuration Manager. For information on how to deploy Office 365 ProPlus with Configuration Manager version 1702, see [Manage Office 365 ProPlus with Configuration Manager](https://docs.microsoft.com/en-us/sccm/sum/deploy-use/manage-office-365-proplus-updates). + + + + +If you use System Center Configuration Manager to deploy software, such as Office, to users and computers in your organization, you can also use that existing Configuration Manager environment to deploy Office 365 ProPlus. By using Configuration Manager, you can control which users and computers get Office 365 ProPlus, where they get the installation files from, and when the Office 365 ProPlus installation occurs. +For example, you can control network bandwidth usage by placing the Office 365 ProPlus installation files on a distribution point within your organization's network, instead of having users install Office 365 ProPlus directly from the Internet. Keep in mind, however, that even if you're installing Office 365 ProPlus from a location within your network, the computer where Office 365 ProPlus is installed still needs access to the Internet to be able to [active Office 365 ProPlus](overview-of-licensing-and-activation-in-office-365-proplus.md#BKMK_ActivatingO365PP). + + + + +The steps that follow are for System Center 2012 R2 Configuration Manager, but you can also deploy Office 365 ProPlus by using System Center 2012 Configuration Manager or Configuration Manager 2007 R2. +## Prepare the Office 365 ProPlus installation files to be deployed by Configuration Manager + + +To get started, download the Office 2016 version of the Office Deployment Tool from the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkID=626065) to a shared folder on your organization's network. Then, use the Office Deployment Tool to [download the Office 365 ProPlus installation files](overview-of-the-office-2016-deployment-tool.md#BKMK_downloadinstallationfiles) from the Internet to the same shared folder. + + + +Next, edit the configuration.xml, and [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) for how you want to install Office 365 ProPlus. The following example shows a configuration.xml that you can use to install the 32-bit, English version of Office 365 ProPlus. + + + + + + +``` + + + + + + + + + +``` + +It's important that you don't include the SourcePath attribute in the Add section of your configuration.xml file. That's because Configuration Manager copies the installation files for an application into a folder under the Configuration Manager client cache folder, and the name of that subfolder is different for each computer. Because the folder name is different for each computer, you can't specify a SourcePath that will work for every computer that you're deploying Office 365 ProPlus to. Instead, leave out the SourcePath attribute. When a SourcePath isn't specified, the Office Deployment Tool automatically looks for the Office 365 ProPlus installation files in the same folder that the Office Deployment Tool is located. That's why we're including the Office Deployment Tool, the configuration.xml, and the Office 365 ProPlus installation files together in the same shared folder. + + + + + + + +![Office 365 installation file folder](images/b556bbf7-f881-4d34-98fb-b96de5d6e0ec.png) + + + + + + + + + + + + +## Create an application for Office 365 ProPlus in Configuration Manager + + +The next step is to [create an application](https://go.microsoft.com/fwlink/p/?LinkId=535035) in Configuration Manager. An application contains the files and information that Configuration Manager needs to deploy software to a user's computer. + + + + **To create an application** + + + + +1. In the Configuration Manager console, choose **Software Library** > **Application Management** > **Applications**. + + +2. On the **Home** tab, in the **Create** group, choose ** Create Application**. + + +3. On the **General** page of the Create Application Wizard, select **Manually specify the application information**, and then choose **Next**. + + +4. On the **General information** page, enter a name for the application, enter any optional information, and then choose **Next.** + + +5. On the **Application Catalog** page, provide the information that's appropriate for your environment, and then choose **Next**. + + +6. On the **Deployment Types** page, choose **Next**. We'll add a deployment type later. + + +7. On the **Summary** page, review the settings you've chosen, and then choose **Next** to create the application. + + +8. After the application is created, on the **Completion** page, choose **Close**. + + + +## Create a deployment type for the Office 365 ProPlus application in Configuration Manager + + +An application in Configuration Manager must contain at least one [deployment type](https://go.microsoft.com/fwlink/p/?LinkId=535030). The deployment type contains the installation files for a software package as well as rules that specify when and how the software is deployed. + + + +For the Office 365 ProPlus application, the deployment type includes the following: + + + + +- The path of the shared folder that contains the Office Deployment Tool, your configuration.xml file, and the Office 365 ProPlus installation files that you downloaded from the Internet. For example, \\\\server1\\share1. + + +- The command line that gets the Office Deployment Tool to start the installation of Office 365 ProPlus. + + +- A [detection method](https://go.microsoft.com/fwlink/p/?LinkId=535032), which Configuration Manager uses to determine if Office 365 ProPlus is already installed on the user's computer. + + + **To create a deployment type** + + + + +1. In the Configuration Manager console, choose **Software Library** > **Application Management** > **Applications**. + + +2. Select the Office 365 ProPlus application, and then on the **Home** tab, in the **Application** group, choose ** Create Deployment Type**. + + +3. On the **General** page of the Create Deployment Type Wizard, in the **Type** list, select **Script Installer**, and then choose **Next**. + + +4. On the **General Information** page, enter a name for the deployment type, enter any optional information, and then choose **Next.** + + +5. On the **Content** page, do the following: + + - In the **Content location** box, enter the network share where you put the Office Deployment Tool, your configuration.xml file, and the Office 365 ProPlus installation files that you downloaded from the Internet. + + + - In the **Installation program** box, enter the following text: setup.exe /configure configuration.xml + + + + After you enter this information, choose **Next**. + + +6. On the **Detection Method** page, choose **Add Clause**. + + +7. In the **Detection Rule** dialog box, do the following: + + - In the **Setting Type** list, select **Registry**. + + + - In the **Hive** list, select **HKEY_LOCAL_MACHINE**. + + + - In the **Key** box, enter the following text: Software\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\O365ProPlusRetail - en-us + + + - Select the **Use (Default) registry key value for detection** check box. + + + + ![Detection rule](images/c6565ea7-2326-490e-8e1f-c2daaa928193.png) + + + After you enter this information, choose **OK**, and then on the **Detection Method** page, choose **Next**. + + +8. On the **User Experience** page, in the **Installation behavior** list, select **Install for system**, and then choose **Next**. + + +9. If you want to specify any requirements or dependencies for the deployment type, choose **Next** to go through those pages in the wizard. Otherwise, choose **Summary**. + + +10. On the **Summary** page, review the settings you've chosen, choose **Next**, and then choose **Close.** + + + +## Distribute the Office 365 ProPlus application to distribution points in Configuration Manager + + +After you create the Office 365 ProPlus application and configure its deployment type, the next step is to copy all the files needed by the application to the appropriate [distribution points](https://go.microsoft.com/fwlink/p/?LinkId=535033) in your Configuration Manager environment. + + + + **To distribute the application to distribution points** + + + + +1. In the Configuration Manager console, choose **Software Library** > **Application Management** > **Applications**. + + +2. Select the Office 365 ProPlus application, and then on the **Home** tab, in the **Deployment** group, choose ** Distribute Content**. + + +3. On the **General** page of the Distribute Content Wizard, choose **Next**, and then on the **Content** page, choose **Next**. + + +4. On the **Content Destination** page, choose **Add** > **Distribution Point**, select the appropriate distribution points, and then choose **OK**. Then, select **Next**. + + +5. On the **Summary** page, review the settings you've chosen, and then choose **Next**. + + +6. On the **Confirmation** page, check that the content was successfully assigned to the distribution points, and then choose **Close**. + + +7. To monitor the distribution, go to **Monitoring** > **Distribution Status** > **Content Status**. + + +8. Select the application, and then view the **Completion Statistics**. + + ![Completion Statistics](images/2023e38c-7c9d-4981-a336-ca676b81e430.png) + + + + + + +## Deploy the Office 365 ProPlus application in Configuration Manager + + +After the files for the Office 365 ProPlus application are copied to the appropriate distribution points, the next step is to [deploy the application](https://go.microsoft.com/fwlink/p/?LinkId=535036). When you deploy the application, you specify which computers or users get the application and when. + + + + **To deploy the application** + + + + +1. In the Configuration Manager console, choose **Software Library** > **Application Management** > **Applications**. + + +2. Select the Office 365 ProPlus application, and then on the **Home** tab, in the **Deployment** group, choose **Deploy**. + + +3. On the **General** page of the Deploy Software Wizard, choose **Browse** for the **Collection** box, and then select which computers or users that you want to deploy Office 365 ProPlus to. After you've made your selection, choose **OK**, and then choose **Next**. + + +4. On the **Content** page, choose **Next** because we've already specified the distribution points for the application. + + +5. On the **Deployment Settings** page, in the **Purpose** list, select **Required**. + + +6. If you want to specify a schedule, configure the user experience, or create an alert, choose **Next** to go through those pages in the wizard. Otherwise, choose **Summary**. + + +7. On the **Summary** page, review the settings you've chosen, and then choose **Next**. + + +8. On the **Confirmation** page, check that the application was successfully deployed, and then choose **Close**. + + +After you deploy the application, a targeted computer becomes aware of the deployed application during the computer's next client policy polling cycle, which is once every sixty minutes by default. Then, the computer downloads the installation files for the application from a distribution point into the Configuration Manager client cache. The installation of Office 365 ProPlus takes place from the client cache and no additional files are downloaded from the network or from the Internet. + + + + + + + +![Office installation status](images/3804d212-3bbc-4768-a90a-864fa69b1dfb.png) + + + + + + + + + + + + +## Related Topics + + + [Application Management in Configuration Manager](https://go.microsoft.com/fwlink/p/?LinkId=535034) + + + + diff --git a/DeployOffice/deployment-guide-for-office-365-proplus.md b/DeployOffice/deployment-guide-for-office-365-proplus.md new file mode 100644 index 000000000..40b45d69c --- /dev/null +++ b/DeployOffice/deployment-guide-for-office-365-proplus.md @@ -0,0 +1,34 @@ +--- +title: Deployment guide for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: f99f8cd0-e648-4834-8f45-f5637351899d +--- + + +# Deployment guide for Office 365 ProPlus + + This guide helps IT Pros plan, deploy, and manage Office 365 ProPlus in their enterprise environments. + + + + + +## Featured + + ** [Overview of the upcoming changes to Office 365 ProPlus update management](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md)** Learn about the changes being made to update channels, along with a schedule of key upcoming dates. + + + + ** [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md)** Recommended guidance and real-world examples about deploying and managing Office 365 ProPlus. + + + + ** [Microsoft FastTrack for Office](http://fasttrack.microsoft.com/office)** FastTrack guides you through the most common deployment configurations. + + + + + + + +Learn about deployment options, how to deploy from a local source, and how to use System Center Configuration Manager to deploy Office 365 ProPlus. [Choose how to deploy Office 365 ProPlus](choose-how-to-deploy-office-365-proplus.md) [Deploy Office 365 ProPlus from the cloud](deploy-office-365-proplus-from-the-cloud.md) [Deploy Office 365 ProPlus from a local source](deploy-office-365-proplus-from-a-local-source.md) [Deploy with Configuration Manager (version 1702)](https://docs.microsoft.com/en-us/sccm/sum/deploy-use/manage-office-365-proplus-updates) [Deploy Office 365 ProPlus with System Center Configuration Manager](deploy-office-365-proplus-with-system-center-configuration-manager.md)Learn about the different update channels available for Office 365 ProPlus and how to use Configuration Manager to manage updates. [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) [Manage updates to Office 365 ProPlus with System Center Configuration Manager](manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md) [Change management for Office 365 clients](change-management-for-office-365-clients.md) [Version and build numbers of update channel releases](version-and-build-numbers-of-update-channel-releases.md)Review the recommended guidance and real-world examples from Microsoft about how to deploy and manage Office 365 ProPlus. [Best practices for assessing your infrastructure](best-practices-for-assessing-your-infrastructure.md) [Best practices for planning your deployment of Office 365 ProPlus](best-practices-for-planning-your-deployment-of-office-365-proplus.md) [Best practices for deploying Office 365 ProPlus](best-practices-for-deploying-office-365-proplus.md) [Best practices for managing updates in Office 365 ProPlus](best-practices-for-managing-updates-in-office-365-proplus.md) [Best practices: Recommended deployment scenarios](best-practices-recommended-deployment-scenarios.md)Learn about the Office Deployment Tool (ODT), other deployment options, and activation. [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md) [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) [Overview: Deploying languages in Office 365 ProPlus](overview-deploying-languages-in-office-365-proplus.md) [Deploy Office 365 ProPlus by using Remote Desktop Services](deploy-office-365-proplus-by-using-remote-desktop-services.md) [Deploy Office 365 ProPlus as part of an operating system image](deploy-office-365-proplus-as-part-of-an-operating-system-image.md) [Overview of licensing and activation in Office 365 ProPlus](overview-of-licensing-and-activation-in-office-365-proplus.md) [Overview of shared computer activation for Office 365 ProPlus](overview-of-shared-computer-activation-for-office-365-proplus.md) diff --git a/DeployOffice/docfx.json b/DeployOffice/docfx.json index 0b1277eb5..857d43902 100644 --- a/DeployOffice/docfx.json +++ b/DeployOffice/docfx.json @@ -1,37 +1,37 @@ -{ - "build": { - "content": [ - { - "files": [ - "**/*.md" - ], - "exclude": [ - "**/obj/**", - "**/includes/**", - "README.md", - "LICENSE", - "LICENSE-CODE", - "ThirdPartyNotices" - ] - } - ], - "resource": [ - { - "files": [ - "**/*.png", - "**/*.jpg" - ], - "exclude": [ - "**/obj/**", - "**/includes/**" - ] - } - ], - "overwrite": [], - "externalReference": [], - "globalMetadata": {}, - "fileMetadata": {}, - "template": [], - "dest": "OfficeDocs-OfficeProPlus" - } +{ + "build": { + "content": [ + { + "files": [ + "**/*.md" + ], + "exclude": [ + "**/obj/**", + "**/includes/**", + "README.md", + "LICENSE", + "LICENSE-CODE", + "ThirdPartyNotices" + ] + } + ], + "resource": [ + { + "files": [ + "**/*.png", + "**/*.jpg" + ], + "exclude": [ + "**/obj/**", + "**/includes/**" + ] + } + ], + "overwrite": [], + "externalReference": [], + "globalMetadata": {}, + "fileMetadata": {}, + "template": [], + "dest": "OfficeDocs-OfficeProPlus" + } } \ No newline at end of file diff --git a/DeployOffice/download-sizes-approximate-for-channel-updates-to-office-365-proplus.md b/DeployOffice/download-sizes-approximate-for-channel-updates-to-office-365-proplus.md new file mode 100644 index 000000000..15e1be5f6 --- /dev/null +++ b/DeployOffice/download-sizes-approximate-for-channel-updates-to-office-365-proplus.md @@ -0,0 +1,648 @@ +--- +title: Download sizes (approximate) for channel updates to Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 190f41e4-064d-486b-9c95-db08f973687c +--- + + +# Download sizes (approximate) for channel updates to Office 365 ProPlus + + **Last updated:** August 8, 2017 + + + + +The following tables show, by release date and update channel, the approximate download size when updating a recent previous release of Office 365 ProPlus to the most current release. +We're providing this information in advance of the actual release date to help enterprise customers plan network bandwidth utilization for these upcoming channel updates. Because we're providing this information in advance, some information might change by the time the actual release comes out. + + + + +Our goal is to provide update size information a week in advance of a release, but there are times when the information isn't available that far in advance. Releases for Deferred Channel and First Release for Deferred Channel are scheduled for the second Tuesday of each month. Current Channel releases are not on a set schedule. +> [!IMPORTANT] +> The approximate download size listed in the tables only applies to the en-us, x86 version of Office 365 ProPlus.> Download sizes are approximate. Actual download sizes might vary, possibly by as much as 50 mb.> Release dates and build numbers that are italicized and enclosed in "< >" are subject to change.> Only the most recent previous releases are listed in the tables. If you're updating from an older release, your download size will be larger.> If you're switching to a different channel, for example from First Release for Deferred Channel to Deferred Channel, your update size will be considerably larger than what's listed in the table. It could entail a full download, which would be at least 1 GB. + + + + +For information about the features, security updates, and non-security updates that are included in a given release, see [Office 365 client update channel releases](https://go.microsoft.com/fwlink/p/?linkid=841891). +## Release date: August 8, 2017 + + + +### First Release for Deferred Channel + +The most current release is Version 1705 (Build 8201.2171). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1705 (Build 8201.2158)
|July 27, 2017
|82
| +|Version 1705 (Build 8201.2136)
|July 13, 2017
|73
| +|Version 1705 (Build 8201.2102)
|June 13, 2017
|110
| + + + + + + +## Release date: August 7, 2017 + + + +### Current Channel + +The most current release is Version 1707 (Build 8326.2070). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1707 (Build 8326.2062)
|July 31, 2017
|49
| +|Version 1707 (Build 8326.2059)
|July 28, 2017
|226
| +|Version 1707 (Build 8326.2058)
|July 27, 2017
|230
| +|Version 1706 (Build 8229.2103)
|July 19, 2017
|118
| +|Version 1706 (Build 8229.2086)
|July 13, 2017
|130
| + + +## Release date: July 31, 2017 + + + +### Current Channel + +The most current release is Version 1707 (Build 8326.2062). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1707 (Build 8326.2059)
|July 28, 2017
|51
| +|Version 1707 (Build 8326.2058)
|July 27, 2017
|178
| +|Version 1706 (Build 8229.2103)
|July 19, 2017
|118
| +|Version 1706 (Build 8229.2086)
|July 13, 2017
|130
| + + +## Release date: July 28, 2017 + + + +### Current Channel + +The most current release is Version 1707 (Build 8326.2059). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1707 (Build 8326.2058)
|July 27, 2017
|176
| +|Version 1706 (Build 8229.2103)
|July 19, 2017
|119
| +|Version 1706 (Build 8229.2086)
|July 13, 2017
|129
| + + +## Release date: July 27, 2017 + + + +### Current Channel + +The most current release is Version 1707 (Build 8326.2058). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1706 (Build 8229.2103)
|July 19, 2017
|117
| +|Version 1706 (Build 8229.2086)
|July 13, 2017
|147
| +|Version 1706 (Build 8229.2073)
|June 28, 2017
|312
| + + +### Deferred Channel + +The most current release is Version 1701 (Build 7766.2099). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1701 (Build 7766.2096)
|July 13, 2017
|135
| +|Version 1701 (Build 7766.2092)
|June 13, 2017
|164
| + + +### First Release for Deferred Channel + +The most current release is Version 1705 (Build 8201.2158). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1705 (Build 8201.2136)
|July 13, 2017
|70
| +|Version 1705 (Build 8201.2102)
|June 13, 2017
|120
| + + + + + + +## Release date: July 19, 2017 + + + +### Current Channel + +The most current release is Version 1706 (Build 8229.2103). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1706 (Build 8229.2086)
|July 13, 2017
|70
| +|Version 1706 (Build 8229.2073)
|June 28, 2017
|236
| +|Version 1705 (Build 8201.2102)
|June 13, 2017
|171
| + + +## Release date: July 13, 2017 + + + +### Current Channel + +The most current release is Version 1706 (Build 8229.2086). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1706 (Build 8229.2073)
|June 28, 2017
|62
| +|Version 1705 (Build 8201.2102)
|June 13, 2017
|168
| +|Version 1705 (Build 8201.2075)
|June 7, 2017
|345
| +|Version 1704 (Build 8067.2157)
|June 1, 2017
|648
| +|Version 1704 (Build 8067.2115)
|May 18, 2017
|187
| + + +### Deferred Channel + +The most current release is Version 1701 (Build 7766.2096). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1701 (Build 7766.2092)
|June 13, 2017
|221
| +|Version 1609 (Build 7369.2130)
|May 9, 2017
|284
| + + +### First Release for Deferred Channel + +The most current release is Version 1705 (Build 8201.2136). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1705 (Build 8201.2102)
|June 13, 2017
|85
| +|Version 1701 (Build 7766.2084)
|May 9, 2017
|321
| + + + + + + +## Release date: June 28, 2017 + + + +### Current Channel + +The most current release is Version 1706 (Build 8229.2073). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1705 (Build 8201.2102)
|June 13, 2017
|168
| +|Version 1705 (Build 8201.2075)
|June 7, 2017
|344
| +|Version 1704 (Build 8067.2157)
|June 1, 2017
|648
| +|Version 1704 (Build 8067.2115)
|May 18, 2017
|190
| + + +## Release date: June 13, 2017 + + + +### Current Channel + +The most current release is Version 1705 (Build 8201.2102). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1705 (Build 8201.2075)
|June 7, 2017
|53
| +|Version 1704 (Build 8067.2157)
|June 1, 2017
|608
| +|Version 1704 (Build 8067.2115)
|May 18, 2017
|160
| + + +### Deferred Channel + +The most current release is Version 1701 (Build 7766.2092). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1609 (Build 7369.2130)
|May 9, 2017
|248
| +|Version 1609 (Build 7369.2127)
|April 11, 2017
|294
| + + +### First Release for Deferred Channel + +The most current release is Version 1705 (Build 8201.2102). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1701 (Build 7766.2084)
|May 9, 2017
|278
| +|Version 1701 (Build 7766.2076)
|April 11, 2017
|279
| + + + + + + +## Release date: June 7, 2017 + + + +### Current Channel + +The most current release is Version 1705 (Build 8201.2075). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1704 (Build 8067.2157)
|June 1, 2017
|625
| +|Version 1704 (Build 8067.2115)
|May 18, 2017
|344
| +|Version 1703 (Build 7967.2161)
|May 9, 2017
|258
| + + +## Release date: June 1, 2017 + + + +### Current Channel + +The most current release is Version 1704 (Build 8067.2157). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1704 (Build 8067.2115)
|May 18, 2017
|315
| +|Version 1703 (Build 7967.2161)
|May 9, 2017
|223
| + + +## Release date: May 18, 2017 + + + +### Current Channel + +The most current release is Version 1704 (Build 8067.2115). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1703 (Build 7967.2161)
|May 9, 2017
|187
| +|Version 1703 (Build 7967.2139)
|April 21, 2017
|213
| + + +## Release date: May 9, 2017 + + + +### Current Channel + +The most current release is Version 1703 (Build 7967.2161). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1703 (Build 7967.2139)
|April 21, 2017
|79
| +|Version 1702 (Build 7870.2038)
|April 11, 2017
|136
| +|Version 1702 (Build 7870.2031)
|March 27, 2017
|165
| +|Version 1702 (Build 7870.2024)
|March 14, 2017
|289
| + + +### Deferred Channel + +The most current release is Version 1609 (Build 7369.2130). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1609 (Build 7369.2127)
|April 11, 2017
|110
| +|Version 1609 (Build 7369.2120)
|March 14, 2017
|131
| + + +### First Release for Deferred Channel + +The most current release is Version 1701 (Build 7766.2084). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1701 (Build 7766.2076)
|April 11, 2017
|93
| +|Version 1701 (Build 7766.2071)
|March 14, 2017
|89
| + + + + + + +## Release date: April 21, 2017 + + + +### Current Channel + +The most current release is Version 1703 (Build 7967.2139). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1702 (Build 7870.2038)
|April 11, 2017
|137
| +|Version 1702 (Build 7870.2031)
|March 27, 2017
|168
| +|Version 1702 (Build 7870.2024)
|March 14, 2017
|289
| +|Version 1702 (Build 7870.2020)
|March 9, 2017
|392
| + + +## Release date: April 11, 2017 + + + +### Current Channel + +The most current release is Version 1702 (Build 7870.2038). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1702 (Build 7870.2031)
|March 27, 2017
|63
| +|Version 1702 (Build 7870.2024)
|March 14, 2017
|200
| +|Version 1702 (Build 7870.2020)
|March 9, 2017
|322
| +|Version 1701 (Build 7766.2060)
|February 23, 2017
|197
| + + +### Deferred Channel + +The most current release is Version 1609 (Build 7369.2127). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1609 (Build 7369.2120)
|March 14, 2017
|109
| +|Version 1609 (Build 7369.2118)
|February 22, 2017
|176
| + + +### First Release for Deferred Channel + +The most current release is Version 1701 (Build 7766.2076). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1701 (Build 7766.2071)
|March 14, 2017
|96
| +|Version 1701 (Build 7766.2060)
|February 22, 2017
|108
| + + + + + + +## Release date: March 27, 2017 + + + +### Current Channel + +The most current release is Version 1702 (Build 7870.2031). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1702 (Build 7870.2024)
|March 14, 2017
|50
| +|Version 1702 (Build 7870.2020)
|March 9, 2017
|300
| +|Version 1701 (Build 7766.2060)
|February 23, 2017
|200
| +|Version 1612 (Build 7668.2074)
|January 31, 2017
|550
| +|Version 1612 (Build 7668.2066)
|January 25, 2017
|550
| + + +## Release date: March 14, 2017 + + + +### Current Channel + +The most current release is Version 1702 (Build 7870.2024). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1702 (Build 7870.2020)
|March 9, 2017
|125
| +|Version 1701 (Build 7766.2060)
|February 23, 2017
|200
| +|Version 1612 (Build 7668.2074)
|January 31, 2017
|550
| +|Version 1612 (Build 7668.2066)
|January 25, 2017
|550
| +|Version 1611 (Build 7571.2109)
|January 4, 2017
|225
| + + +### Deferred Channel + +The most current release is Version 1609 (Build 7369.2120). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1609 (Build 7369.2118)
|February 22, 2017
|200
| +|Version 1605 (Build 6965.2117)
|January 10, 2017
|350
| + + +### First Release for Deferred Channel + +The most current release is Version 1701 (Build 7766.2071). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1701 (Build 7766.2060)
|February 22, 2017
|150
| +|Version 1609 (Build 7369.2102)
|January 10, 2017
|250
| + + + + + + +## Release date: March 9, 2017 + + + +### Current Channel + +The most current release is Version 1702 (Build 7870.2020). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1701 (Build 7766.2060)
|February 23, 2017
|175
| +|Version 1612 (Build 7668.2074)
|January 31, 2017
|550
| +|Version 1612 (Build 7668.2066)
|January 25, 2017
|525
| +|Version 1611 (Build 7571.2109)
|January 4, 2017
|250
| + + +## Release date: February 23, 2017 + + + +### Current Channel + +The most current release is Version 1701 (Build 7766.2060). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1612 (Build 7668.2074)
|January 31, 2017
|100
| +|Version 1612 (Build 7668.2066)
|January 25, 2017
|150
| +|Version 1611 (Build 7571.2109)
|January 4, 2017
|175
| + + +## Release date: February 22, 2017 + + + +### Deferred Channel + +The most current release is Version 1609 (Build 7369.2118). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1605 (Build 6965.2117)
|January 10, 2017
|375
| +|Version 1605 (Build 6965.2115)
|December 13, 2016
|375
| + + +### First Release for Deferred Channel + +The most current release is Version 1701 (Build 7766.2060). + + + + + +|**Release upgrading from**|**Release date**|**Approximate download size (in MB)**| +|:-----|:-----|:-----| +|Version 1609 (Build 7369.2102)
|January 10, 2017
|275
| +|Version 1609 (Build 7369.2095)
|December 13, 2016
|275
| + + + + + + +## See also + + + +#### Other Resources + + + + + + [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) + + + + [Version and build numbers of update channel releases](version-and-build-numbers-of-update-channel-releases.md) diff --git a/DeployOffice/end-user-update-notifications-for-office-365-proplus.md b/DeployOffice/end-user-update-notifications-for-office-365-proplus.md new file mode 100644 index 000000000..cae71822e --- /dev/null +++ b/DeployOffice/end-user-update-notifications-for-office-365-proplus.md @@ -0,0 +1,146 @@ +--- +title: End-user update notifications for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 83ede0c2-474d-4b11-8723-1984d5279a4c +--- + + +# End-user update notifications for Office 365 ProPlus + +You probably don't want users in your organization to notice when security and other updates are applied to Office 365 ProPlus on their computers. In most cases, they won't notice as the updates are installed automatically in the background. But, you should be aware that there are times when users see notifications that updates are available or need to be applied. + + + + +Updates can only be applied when Office programs aren't running. Therefore, notifications usually appear because the user is working in an Office program, such as Microsoft Outlook, and hasn't closed it in several days. +## Notifications your users see when updates can't be applied for several days to Office 365 ProPlus + + +After updates are downloaded to the computer that is running Office 365 ProPlus, Office attempts to apply the updates. If, after four days, the updates still aren't applied, a message appears in the notification area in Windows, telling the user that updates are available. + + + + + + + +![Office updates are available](images/a5ed310f-432c-49de-a810-38962b552531.jpg) + + + +The message disappears in a few seconds, but the Office icon stays visible in the notification area. If the user clicks the message, Office tries to apply the updates. If any Office programs are currently being used, they must be closed. + + + +If, after six days, the updates still aren't applied, a message appears in any newly opened Office document, reminding the user that updates are available. + + + + + + + +![Updates are available, but are blocked by one or more apps.](images/93bc2d5b-4955-4369-bf3b-5beb0b3ff705.jpg) + + + +Users can choose **Update now** to apply the updates. The user is then prompted to close all open Office programs. After the updates are applied, the message disappears. + + + +Users also see notifications if they go to **File > Account** in an Office program. The **Office Updates** section turns yellow if updates are ready to be applied. + + + + + + + +![Office updates are available](images/574a065f-f666-481f-b2f7-5cc56d7c97f9.jpg) + + + +If you don't want your users to see these types of notifications, you can [use Group Policy to hide the notifications](configure-update-settings-for-office-365-proplus.md). + + + + +## Notifications your users see when you set an update deadline for Office 365 ProPlus + + +To make sure that your users apply updates to Office 365 ProPlus, you can [configure a deadline](configure-update-settings-for-office-365-proplus.md). The deadline specifies a date and time by when the updates must be applied. If the updates aren't applied by the deadline, Office automatically closes any open Office programs and applies the updates. + + + +Users are given notifications leading up to the deadline. For example, within seventy-two hours of the deadline, users see a message, in any newly opened Office document, that updates are blocked. + + + + + + + +![Office updates 72 hour deadline](images/f69d4bed-ab4d-43ac-ae5d-01ac31653cb9.jpg) + + + +The next reminder users see is twelve hours before the deadline. They'll see a message in the notification area in Windows, reminding them that updates are ready to be applied. + + + + + + + +![Office updates 12 hour deadline notification](images/6c315397-3f15-4c9f-86b1-5132c28dbc7e.jpg) + + + +This message appears every two hours. It'll also be shown 60 minutes, 30 minutes, 15 minutes, and 5 minutes before the deadline. + + + +If the deadline arrives and the updates still aren't applied, users see a dialog box that warns them that they have 15 minutes before the updates are applied. + + + + + + + +![Office updates 15 minute deadline notification](images/1016ec10-5e8a-4280-896a-4e1026304a63.jpg) + + + +This gives users fifteen minutes to save and close any work. When the countdown reaches 00:00, any open Office programs are closed, and the updates are applied. + + + + + +> [!NOTE] +> The **Hide update notifications** Group Policy setting doesn't hide notifications related to deadlines. + + + + + +## See also + + + +#### Other Resources + + + + + + [Overview of the update process for Office 365 ProPlus](overview-of-the-update-process-for-office-365-proplus.md) + + + + [Choose how to manage updates to Office 365 ProPlus](choose-how-to-manage-updates-to-office-365-proplus.md) + + + + [Configure update settings for Office 365 ProPlus](configure-update-settings-for-office-365-proplus.md) diff --git a/DeployOffice/images/00a4d1a9-4c89-4534-93ed-affb3f47dde7.png b/DeployOffice/images/00a4d1a9-4c89-4534-93ed-affb3f47dde7.png new file mode 100644 index 000000000..00b249609 Binary files /dev/null and b/DeployOffice/images/00a4d1a9-4c89-4534-93ed-affb3f47dde7.png differ diff --git a/DeployOffice/images/03839cb7-6e68-4697-9eb4-194c7edba3c4.png b/DeployOffice/images/03839cb7-6e68-4697-9eb4-194c7edba3c4.png new file mode 100644 index 000000000..024935d81 Binary files /dev/null and b/DeployOffice/images/03839cb7-6e68-4697-9eb4-194c7edba3c4.png differ diff --git a/DeployOffice/images/0532b11b-c2ea-4e73-8fe5-52526cefac35.png b/DeployOffice/images/0532b11b-c2ea-4e73-8fe5-52526cefac35.png new file mode 100644 index 000000000..854a800c4 Binary files /dev/null and b/DeployOffice/images/0532b11b-c2ea-4e73-8fe5-52526cefac35.png differ diff --git a/DeployOffice/images/067af377-022d-4a4b-aa04-993669398ebc.png b/DeployOffice/images/067af377-022d-4a4b-aa04-993669398ebc.png new file mode 100644 index 000000000..0bbd682bf Binary files /dev/null and b/DeployOffice/images/067af377-022d-4a4b-aa04-993669398ebc.png differ diff --git a/DeployOffice/images/0d973495-46cc-42dc-a26e-87933e8b0a6b.png b/DeployOffice/images/0d973495-46cc-42dc-a26e-87933e8b0a6b.png new file mode 100644 index 000000000..34551d999 Binary files /dev/null and b/DeployOffice/images/0d973495-46cc-42dc-a26e-87933e8b0a6b.png differ diff --git a/DeployOffice/images/1016ec10-5e8a-4280-896a-4e1026304a63.jpg b/DeployOffice/images/1016ec10-5e8a-4280-896a-4e1026304a63.jpg new file mode 100644 index 000000000..14b45af11 Binary files /dev/null and b/DeployOffice/images/1016ec10-5e8a-4280-896a-4e1026304a63.jpg differ diff --git a/DeployOffice/images/1166f881-87da-4667-a4bd-e92c23859de2.png b/DeployOffice/images/1166f881-87da-4667-a4bd-e92c23859de2.png new file mode 100644 index 000000000..421556d64 Binary files /dev/null and b/DeployOffice/images/1166f881-87da-4667-a4bd-e92c23859de2.png differ diff --git a/DeployOffice/images/15b018fe-c12e-4d78-9287-bc95d5e14cac.png b/DeployOffice/images/15b018fe-c12e-4d78-9287-bc95d5e14cac.png new file mode 100644 index 000000000..b77e22d6d Binary files /dev/null and b/DeployOffice/images/15b018fe-c12e-4d78-9287-bc95d5e14cac.png differ diff --git a/DeployOffice/images/15f0ae22-60d6-4484-838a-08b5e1312988.jpg b/DeployOffice/images/15f0ae22-60d6-4484-838a-08b5e1312988.jpg new file mode 100644 index 000000000..81278c4da Binary files /dev/null and b/DeployOffice/images/15f0ae22-60d6-4484-838a-08b5e1312988.jpg differ diff --git a/DeployOffice/images/16fae804-8d79-43db-8902-2adbbc6e0c9e.png b/DeployOffice/images/16fae804-8d79-43db-8902-2adbbc6e0c9e.png new file mode 100644 index 000000000..a63842c4b Binary files /dev/null and b/DeployOffice/images/16fae804-8d79-43db-8902-2adbbc6e0c9e.png differ diff --git a/DeployOffice/images/180d081a-aad7-40f9-bb18-ff65ff166530.png b/DeployOffice/images/180d081a-aad7-40f9-bb18-ff65ff166530.png new file mode 100644 index 000000000..f26d51fbf Binary files /dev/null and b/DeployOffice/images/180d081a-aad7-40f9-bb18-ff65ff166530.png differ diff --git a/DeployOffice/images/1d4828f2-26a1-4b0e-a3d9-f35c901b831f.PNG b/DeployOffice/images/1d4828f2-26a1-4b0e-a3d9-f35c901b831f.PNG new file mode 100644 index 000000000..7cb9f0008 Binary files /dev/null and b/DeployOffice/images/1d4828f2-26a1-4b0e-a3d9-f35c901b831f.PNG differ diff --git a/DeployOffice/images/2023e38c-7c9d-4981-a336-ca676b81e430.png b/DeployOffice/images/2023e38c-7c9d-4981-a336-ca676b81e430.png new file mode 100644 index 000000000..ccd4af4aa Binary files /dev/null and b/DeployOffice/images/2023e38c-7c9d-4981-a336-ca676b81e430.png differ diff --git a/DeployOffice/images/21459b91-f971-416c-8cfe-0a85c2769520.png b/DeployOffice/images/21459b91-f971-416c-8cfe-0a85c2769520.png new file mode 100644 index 000000000..269ab5cef Binary files /dev/null and b/DeployOffice/images/21459b91-f971-416c-8cfe-0a85c2769520.png differ diff --git a/DeployOffice/images/2a4e0cfb-828b-4881-9db9-468a2b597b7d.jpg b/DeployOffice/images/2a4e0cfb-828b-4881-9db9-468a2b597b7d.jpg new file mode 100644 index 000000000..2ab4b81e0 Binary files /dev/null and b/DeployOffice/images/2a4e0cfb-828b-4881-9db9-468a2b597b7d.jpg differ diff --git a/DeployOffice/images/37437b6c-5325-4739-ac6a-0dca404329ca.png b/DeployOffice/images/37437b6c-5325-4739-ac6a-0dca404329ca.png new file mode 100644 index 000000000..b5bde3d45 Binary files /dev/null and b/DeployOffice/images/37437b6c-5325-4739-ac6a-0dca404329ca.png differ diff --git a/DeployOffice/images/3804d212-3bbc-4768-a90a-864fa69b1dfb.png b/DeployOffice/images/3804d212-3bbc-4768-a90a-864fa69b1dfb.png new file mode 100644 index 000000000..5938de81e Binary files /dev/null and b/DeployOffice/images/3804d212-3bbc-4768-a90a-864fa69b1dfb.png differ diff --git a/DeployOffice/images/3d236c2a-304c-44b3-9a73-d0fa8cc48437.jpg b/DeployOffice/images/3d236c2a-304c-44b3-9a73-d0fa8cc48437.jpg new file mode 100644 index 000000000..ad7de5bcf Binary files /dev/null and b/DeployOffice/images/3d236c2a-304c-44b3-9a73-d0fa8cc48437.jpg differ diff --git a/DeployOffice/images/42471221-f1a5-4bd6-9d7e-5f24a3049330.png b/DeployOffice/images/42471221-f1a5-4bd6-9d7e-5f24a3049330.png new file mode 100644 index 000000000..0120ad9bc Binary files /dev/null and b/DeployOffice/images/42471221-f1a5-4bd6-9d7e-5f24a3049330.png differ diff --git a/DeployOffice/images/42c08d42-6ff1-4729-ae7a-b4011a499989.png b/DeployOffice/images/42c08d42-6ff1-4729-ae7a-b4011a499989.png new file mode 100644 index 000000000..3868a1ee5 Binary files /dev/null and b/DeployOffice/images/42c08d42-6ff1-4729-ae7a-b4011a499989.png differ diff --git a/DeployOffice/images/45ce18de-b51b-4bda-8189-c593883ddd80.png b/DeployOffice/images/45ce18de-b51b-4bda-8189-c593883ddd80.png new file mode 100644 index 000000000..b129c061f Binary files /dev/null and b/DeployOffice/images/45ce18de-b51b-4bda-8189-c593883ddd80.png differ diff --git a/DeployOffice/images/495a5ea5-a10e-409a-8761-8862959c340a.png b/DeployOffice/images/495a5ea5-a10e-409a-8761-8862959c340a.png new file mode 100644 index 000000000..ca3276dab Binary files /dev/null and b/DeployOffice/images/495a5ea5-a10e-409a-8761-8862959c340a.png differ diff --git a/DeployOffice/images/4b0df8e6-dda2-4159-b7bf-7b7f24aa8285.png b/DeployOffice/images/4b0df8e6-dda2-4159-b7bf-7b7f24aa8285.png new file mode 100644 index 000000000..122402338 Binary files /dev/null and b/DeployOffice/images/4b0df8e6-dda2-4159-b7bf-7b7f24aa8285.png differ diff --git a/DeployOffice/images/4b7f1d61-6020-4781-b5a4-d5f87ee03bc3.png b/DeployOffice/images/4b7f1d61-6020-4781-b5a4-d5f87ee03bc3.png new file mode 100644 index 000000000..bfa9486a5 Binary files /dev/null and b/DeployOffice/images/4b7f1d61-6020-4781-b5a4-d5f87ee03bc3.png differ diff --git a/DeployOffice/images/4bab7afd-4ffa-4775-bc8b-86767198d140.png b/DeployOffice/images/4bab7afd-4ffa-4775-bc8b-86767198d140.png new file mode 100644 index 000000000..847835c1a Binary files /dev/null and b/DeployOffice/images/4bab7afd-4ffa-4775-bc8b-86767198d140.png differ diff --git a/DeployOffice/images/4e25a9fc-1844-4204-9b9d-40603ca1a091.png b/DeployOffice/images/4e25a9fc-1844-4204-9b9d-40603ca1a091.png new file mode 100644 index 000000000..847835c1a Binary files /dev/null and b/DeployOffice/images/4e25a9fc-1844-4204-9b9d-40603ca1a091.png differ diff --git a/DeployOffice/images/532c35a1-c16e-41f1-8c45-b9e00f0d04f9.png b/DeployOffice/images/532c35a1-c16e-41f1-8c45-b9e00f0d04f9.png new file mode 100644 index 000000000..43269c93f Binary files /dev/null and b/DeployOffice/images/532c35a1-c16e-41f1-8c45-b9e00f0d04f9.png differ diff --git a/DeployOffice/images/574a065f-f666-481f-b2f7-5cc56d7c97f9.jpg b/DeployOffice/images/574a065f-f666-481f-b2f7-5cc56d7c97f9.jpg new file mode 100644 index 000000000..250117d2b Binary files /dev/null and b/DeployOffice/images/574a065f-f666-481f-b2f7-5cc56d7c97f9.jpg differ diff --git a/DeployOffice/images/64f9e1cf-db58-43bc-945a-9dc643eb6596.png b/DeployOffice/images/64f9e1cf-db58-43bc-945a-9dc643eb6596.png new file mode 100644 index 000000000..8cab8aeb4 Binary files /dev/null and b/DeployOffice/images/64f9e1cf-db58-43bc-945a-9dc643eb6596.png differ diff --git a/DeployOffice/images/67637fc5-35cc-4118-acc1-e68fe1155512.png b/DeployOffice/images/67637fc5-35cc-4118-acc1-e68fe1155512.png new file mode 100644 index 000000000..cd615272f Binary files /dev/null and b/DeployOffice/images/67637fc5-35cc-4118-acc1-e68fe1155512.png differ diff --git a/DeployOffice/images/6769367a-3c03-4ada-94d4-6c75228aabb2.png b/DeployOffice/images/6769367a-3c03-4ada-94d4-6c75228aabb2.png new file mode 100644 index 000000000..2f0218fdb Binary files /dev/null and b/DeployOffice/images/6769367a-3c03-4ada-94d4-6c75228aabb2.png differ diff --git a/DeployOffice/images/6c315397-3f15-4c9f-86b1-5132c28dbc7e.jpg b/DeployOffice/images/6c315397-3f15-4c9f-86b1-5132c28dbc7e.jpg new file mode 100644 index 000000000..3f4f92a43 Binary files /dev/null and b/DeployOffice/images/6c315397-3f15-4c9f-86b1-5132c28dbc7e.jpg differ diff --git a/DeployOffice/images/7686c89d-eff0-4ab2-8b28-5eed68967351.png b/DeployOffice/images/7686c89d-eff0-4ab2-8b28-5eed68967351.png new file mode 100644 index 000000000..cc62d40f5 Binary files /dev/null and b/DeployOffice/images/7686c89d-eff0-4ab2-8b28-5eed68967351.png differ diff --git a/DeployOffice/images/78aa59b0-8772-4ba2-8094-bfeb65602ab7.png b/DeployOffice/images/78aa59b0-8772-4ba2-8094-bfeb65602ab7.png new file mode 100644 index 000000000..fb3b008d2 Binary files /dev/null and b/DeployOffice/images/78aa59b0-8772-4ba2-8094-bfeb65602ab7.png differ diff --git a/DeployOffice/images/82dbed0c-d6d1-42fc-bb05-2556189be01b.jpg b/DeployOffice/images/82dbed0c-d6d1-42fc-bb05-2556189be01b.jpg new file mode 100644 index 000000000..50986fdc9 Binary files /dev/null and b/DeployOffice/images/82dbed0c-d6d1-42fc-bb05-2556189be01b.jpg differ diff --git a/DeployOffice/images/84c2cca8-ef2e-4fd9-8294-4232f3f012c9.png b/DeployOffice/images/84c2cca8-ef2e-4fd9-8294-4232f3f012c9.png new file mode 100644 index 000000000..1573ba563 Binary files /dev/null and b/DeployOffice/images/84c2cca8-ef2e-4fd9-8294-4232f3f012c9.png differ diff --git a/DeployOffice/images/86a9781c-0e91-4e5d-b334-7a0d07d85466.jpg b/DeployOffice/images/86a9781c-0e91-4e5d-b334-7a0d07d85466.jpg new file mode 100644 index 000000000..920255c63 Binary files /dev/null and b/DeployOffice/images/86a9781c-0e91-4e5d-b334-7a0d07d85466.jpg differ diff --git a/DeployOffice/images/88099880-fe32-4da5-9724-d9e11ff51d62.png b/DeployOffice/images/88099880-fe32-4da5-9724-d9e11ff51d62.png new file mode 100644 index 000000000..f564be3ed Binary files /dev/null and b/DeployOffice/images/88099880-fe32-4da5-9724-d9e11ff51d62.png differ diff --git a/DeployOffice/images/920badf4-7064-49b3-bc49-e61a033c4415.png b/DeployOffice/images/920badf4-7064-49b3-bc49-e61a033c4415.png new file mode 100644 index 000000000..27804a1c5 Binary files /dev/null and b/DeployOffice/images/920badf4-7064-49b3-bc49-e61a033c4415.png differ diff --git a/DeployOffice/images/93bc2d5b-4955-4369-bf3b-5beb0b3ff705.jpg b/DeployOffice/images/93bc2d5b-4955-4369-bf3b-5beb0b3ff705.jpg new file mode 100644 index 000000000..48e539596 Binary files /dev/null and b/DeployOffice/images/93bc2d5b-4955-4369-bf3b-5beb0b3ff705.jpg differ diff --git a/DeployOffice/images/99a17880-4029-44e9-b478-be4058c30f92.png b/DeployOffice/images/99a17880-4029-44e9-b478-be4058c30f92.png new file mode 100644 index 000000000..2f0218fdb Binary files /dev/null and b/DeployOffice/images/99a17880-4029-44e9-b478-be4058c30f92.png differ diff --git a/DeployOffice/images/99e17d65-144f-442b-9181-9090ec421e48.png b/DeployOffice/images/99e17d65-144f-442b-9181-9090ec421e48.png new file mode 100644 index 000000000..0cf02bc9a Binary files /dev/null and b/DeployOffice/images/99e17d65-144f-442b-9181-9090ec421e48.png differ diff --git a/DeployOffice/images/9cb7eef4-0ce6-428a-8f96-890e5237d17a.png b/DeployOffice/images/9cb7eef4-0ce6-428a-8f96-890e5237d17a.png new file mode 100644 index 000000000..bc0a39d49 Binary files /dev/null and b/DeployOffice/images/9cb7eef4-0ce6-428a-8f96-890e5237d17a.png differ diff --git a/DeployOffice/images/CFW.gif b/DeployOffice/images/CFW.gif new file mode 100644 index 000000000..27097e54c Binary files /dev/null and b/DeployOffice/images/CFW.gif differ diff --git a/DeployOffice/images/Caution.gif b/DeployOffice/images/Caution.gif new file mode 100644 index 000000000..0f24145a1 Binary files /dev/null and b/DeployOffice/images/Caution.gif differ diff --git a/DeployOffice/images/GitHub-Mark-64px.png b/DeployOffice/images/GitHub-Mark-64px.png new file mode 100644 index 000000000..182a1a3f7 Binary files /dev/null and b/DeployOffice/images/GitHub-Mark-64px.png differ diff --git a/DeployOffice/images/LastChild.gif b/DeployOffice/images/LastChild.gif new file mode 100644 index 000000000..0b9af7e88 Binary files /dev/null and b/DeployOffice/images/LastChild.gif differ diff --git a/DeployOffice/images/MSN_Video_Widget.gif b/DeployOffice/images/MSN_Video_Widget.gif new file mode 100644 index 000000000..852a7daa9 Binary files /dev/null and b/DeployOffice/images/MSN_Video_Widget.gif differ diff --git a/DeployOffice/images/Octocat.png b/DeployOffice/images/Octocat.png new file mode 100644 index 000000000..4cd60c933 Binary files /dev/null and b/DeployOffice/images/Octocat.png differ diff --git a/DeployOffice/images/a5ed310f-432c-49de-a810-38962b552531.jpg b/DeployOffice/images/a5ed310f-432c-49de-a810-38962b552531.jpg new file mode 100644 index 000000000..e8ec903cd Binary files /dev/null and b/DeployOffice/images/a5ed310f-432c-49de-a810-38962b552531.jpg differ diff --git a/DeployOffice/images/aa1e234d-c2d1-471f-bf7f-9b11adc8b4b4.jpg b/DeployOffice/images/aa1e234d-c2d1-471f-bf7f-9b11adc8b4b4.jpg new file mode 100644 index 000000000..bafdb3722 Binary files /dev/null and b/DeployOffice/images/aa1e234d-c2d1-471f-bf7f-9b11adc8b4b4.jpg differ diff --git a/DeployOffice/images/adm.gif b/DeployOffice/images/adm.gif new file mode 100644 index 000000000..9855be65e Binary files /dev/null and b/DeployOffice/images/adm.gif differ diff --git a/DeployOffice/images/adm_arch.gif b/DeployOffice/images/adm_arch.gif new file mode 100644 index 000000000..6308c86dd Binary files /dev/null and b/DeployOffice/images/adm_arch.gif differ diff --git a/DeployOffice/images/adm_dev.gif b/DeployOffice/images/adm_dev.gif new file mode 100644 index 000000000..bb0f95f57 Binary files /dev/null and b/DeployOffice/images/adm_dev.gif differ diff --git a/DeployOffice/images/adm_dev_arch.gif b/DeployOffice/images/adm_dev_arch.gif new file mode 100644 index 000000000..b2c79227c Binary files /dev/null and b/DeployOffice/images/adm_dev_arch.gif differ diff --git a/DeployOffice/images/alert_caution.gif b/DeployOffice/images/alert_caution.gif new file mode 100644 index 000000000..331b50bda Binary files /dev/null and b/DeployOffice/images/alert_caution.gif differ diff --git a/DeployOffice/images/alert_note.gif b/DeployOffice/images/alert_note.gif new file mode 100644 index 000000000..57bf20c91 Binary files /dev/null and b/DeployOffice/images/alert_note.gif differ diff --git a/DeployOffice/images/alert_security.gif b/DeployOffice/images/alert_security.gif new file mode 100644 index 000000000..e70b29eaa Binary files /dev/null and b/DeployOffice/images/alert_security.gif differ diff --git a/DeployOffice/images/arch.gif b/DeployOffice/images/arch.gif new file mode 100644 index 000000000..79e25d200 Binary files /dev/null and b/DeployOffice/images/arch.gif differ diff --git a/DeployOffice/images/b556bbf7-f881-4d34-98fb-b96de5d6e0ec.png b/DeployOffice/images/b556bbf7-f881-4d34-98fb-b96de5d6e0ec.png new file mode 100644 index 000000000..301b5a82e Binary files /dev/null and b/DeployOffice/images/b556bbf7-f881-4d34-98fb-b96de5d6e0ec.png differ diff --git a/DeployOffice/images/bc32bed2-b7be-4652-93d0-4f0f90b97e8e.png b/DeployOffice/images/bc32bed2-b7be-4652-93d0-4f0f90b97e8e.png new file mode 100644 index 000000000..68fffc175 Binary files /dev/null and b/DeployOffice/images/bc32bed2-b7be-4652-93d0-4f0f90b97e8e.png differ diff --git a/DeployOffice/images/bebd7cb7-2bec-42e4-ae5e-ecc6817d9484.jpg b/DeployOffice/images/bebd7cb7-2bec-42e4-ae5e-ecc6817d9484.jpg new file mode 100644 index 000000000..4af0be2c3 Binary files /dev/null and b/DeployOffice/images/bebd7cb7-2bec-42e4-ae5e-ecc6817d9484.jpg differ diff --git a/DeployOffice/images/big_adm.gif b/DeployOffice/images/big_adm.gif new file mode 100644 index 000000000..9855be65e Binary files /dev/null and b/DeployOffice/images/big_adm.gif differ diff --git a/DeployOffice/images/big_arch.gif b/DeployOffice/images/big_arch.gif new file mode 100644 index 000000000..9f0ae0316 Binary files /dev/null and b/DeployOffice/images/big_arch.gif differ diff --git a/DeployOffice/images/big_dev.gif b/DeployOffice/images/big_dev.gif new file mode 100644 index 000000000..0a22ad2c2 Binary files /dev/null and b/DeployOffice/images/big_dev.gif differ diff --git a/DeployOffice/images/big_kw.gif b/DeployOffice/images/big_kw.gif new file mode 100644 index 000000000..bdbc65a04 Binary files /dev/null and b/DeployOffice/images/big_kw.gif differ diff --git a/DeployOffice/images/box.gif b/DeployOffice/images/box.gif new file mode 100644 index 000000000..a0e0ca91e Binary files /dev/null and b/DeployOffice/images/box.gif differ diff --git a/DeployOffice/images/bullet.gif b/DeployOffice/images/bullet.gif new file mode 100644 index 000000000..bd7f9d235 Binary files /dev/null and b/DeployOffice/images/bullet.gif differ diff --git a/DeployOffice/images/c43eb782-f0b4-4592-a07c-4d2c01a68966.png b/DeployOffice/images/c43eb782-f0b4-4592-a07c-4d2c01a68966.png new file mode 100644 index 000000000..476c7fc71 Binary files /dev/null and b/DeployOffice/images/c43eb782-f0b4-4592-a07c-4d2c01a68966.png differ diff --git a/DeployOffice/images/c6565ea7-2326-490e-8e1f-c2daaa928193.png b/DeployOffice/images/c6565ea7-2326-490e-8e1f-c2daaa928193.png new file mode 100644 index 000000000..65f6ae7bd Binary files /dev/null and b/DeployOffice/images/c6565ea7-2326-490e-8e1f-c2daaa928193.png differ diff --git a/DeployOffice/images/c830ebad-a255-4e32-8d7a-af5a687dc107.png b/DeployOffice/images/c830ebad-a255-4e32-8d7a-af5a687dc107.png new file mode 100644 index 000000000..6a7ad2705 Binary files /dev/null and b/DeployOffice/images/c830ebad-a255-4e32-8d7a-af5a687dc107.png differ diff --git a/DeployOffice/images/c8774868-5fc5-4f07-890a-8ae777d5d44d.png b/DeployOffice/images/c8774868-5fc5-4f07-890a-8ae777d5d44d.png new file mode 100644 index 000000000..019f155d6 Binary files /dev/null and b/DeployOffice/images/c8774868-5fc5-4f07-890a-8ae777d5d44d.png differ diff --git a/DeployOffice/images/collall.gif b/DeployOffice/images/collall.gif new file mode 100644 index 000000000..66a6f1162 Binary files /dev/null and b/DeployOffice/images/collall.gif differ diff --git a/DeployOffice/images/collapse.gif b/DeployOffice/images/collapse.gif new file mode 100644 index 000000000..d57c04677 Binary files /dev/null and b/DeployOffice/images/collapse.gif differ diff --git a/DeployOffice/images/collapse_all.gif b/DeployOffice/images/collapse_all.gif new file mode 100644 index 000000000..b38b9903b Binary files /dev/null and b/DeployOffice/images/collapse_all.gif differ diff --git a/DeployOffice/images/copycode.gif b/DeployOffice/images/copycode.gif new file mode 100644 index 000000000..167816266 Binary files /dev/null and b/DeployOffice/images/copycode.gif differ diff --git a/DeployOffice/images/copycodeHighlight.gif b/DeployOffice/images/copycodeHighlight.gif new file mode 100644 index 000000000..be87230ff Binary files /dev/null and b/DeployOffice/images/copycodeHighlight.gif differ diff --git a/DeployOffice/images/dev.gif b/DeployOffice/images/dev.gif new file mode 100644 index 000000000..07684fded Binary files /dev/null and b/DeployOffice/images/dev.gif differ diff --git a/DeployOffice/images/dev_arch.gif b/DeployOffice/images/dev_arch.gif new file mode 100644 index 000000000..dc74755b7 Binary files /dev/null and b/DeployOffice/images/dev_arch.gif differ diff --git a/DeployOffice/images/dropdown.gif b/DeployOffice/images/dropdown.gif new file mode 100644 index 000000000..f5590a0a5 Binary files /dev/null and b/DeployOffice/images/dropdown.gif differ diff --git a/DeployOffice/images/dropdownHover.gif b/DeployOffice/images/dropdownHover.gif new file mode 100644 index 000000000..c7061b566 Binary files /dev/null and b/DeployOffice/images/dropdownHover.gif differ diff --git a/DeployOffice/images/drpdown.gif b/DeployOffice/images/drpdown.gif new file mode 100644 index 000000000..9d3bbb6e7 Binary files /dev/null and b/DeployOffice/images/drpdown.gif differ diff --git a/DeployOffice/images/drpdown_orange.gif b/DeployOffice/images/drpdown_orange.gif new file mode 100644 index 000000000..cf50c2014 Binary files /dev/null and b/DeployOffice/images/drpdown_orange.gif differ diff --git a/DeployOffice/images/drpdown_orange_up.gif b/DeployOffice/images/drpdown_orange_up.gif new file mode 100644 index 000000000..a173df1e6 Binary files /dev/null and b/DeployOffice/images/drpdown_orange_up.gif differ diff --git a/DeployOffice/images/drpup.gif b/DeployOffice/images/drpup.gif new file mode 100644 index 000000000..de7719859 Binary files /dev/null and b/DeployOffice/images/drpup.gif differ diff --git a/DeployOffice/images/e01c8a45-1814-4bfe-bb7e-c0176f393031.png b/DeployOffice/images/e01c8a45-1814-4bfe-bb7e-c0176f393031.png new file mode 100644 index 000000000..421556d64 Binary files /dev/null and b/DeployOffice/images/e01c8a45-1814-4bfe-bb7e-c0176f393031.png differ diff --git a/DeployOffice/images/ea7f0c80-3f3d-405b-add1-0707677a828e.png b/DeployOffice/images/ea7f0c80-3f3d-405b-add1-0707677a828e.png new file mode 100644 index 000000000..74dd6daad Binary files /dev/null and b/DeployOffice/images/ea7f0c80-3f3d-405b-add1-0707677a828e.png differ diff --git a/DeployOffice/images/exp.gif b/DeployOffice/images/exp.gif new file mode 100644 index 000000000..023b837ea Binary files /dev/null and b/DeployOffice/images/exp.gif differ diff --git a/DeployOffice/images/expall.gif b/DeployOffice/images/expall.gif new file mode 100644 index 000000000..1a91b1273 Binary files /dev/null and b/DeployOffice/images/expall.gif differ diff --git a/DeployOffice/images/expand_all.gif b/DeployOffice/images/expand_all.gif new file mode 100644 index 000000000..c7061b566 Binary files /dev/null and b/DeployOffice/images/expand_all.gif differ diff --git a/DeployOffice/images/f0f92823-29ae-443e-af36-d913c6ba6486.png b/DeployOffice/images/f0f92823-29ae-443e-af36-d913c6ba6486.png new file mode 100644 index 000000000..efa1810bf Binary files /dev/null and b/DeployOffice/images/f0f92823-29ae-443e-af36-d913c6ba6486.png differ diff --git a/DeployOffice/images/f1468c2b-b347-4f55-b6b7-0fa9e23a7e97.png b/DeployOffice/images/f1468c2b-b347-4f55-b6b7-0fa9e23a7e97.png new file mode 100644 index 000000000..1892ddff5 Binary files /dev/null and b/DeployOffice/images/f1468c2b-b347-4f55-b6b7-0fa9e23a7e97.png differ diff --git a/DeployOffice/images/f29ab2ab-6699-41b4-8fbb-232f66137426.png b/DeployOffice/images/f29ab2ab-6699-41b4-8fbb-232f66137426.png new file mode 100644 index 000000000..499d02aa7 Binary files /dev/null and b/DeployOffice/images/f29ab2ab-6699-41b4-8fbb-232f66137426.png differ diff --git a/DeployOffice/images/f69d4bed-ab4d-43ac-ae5d-01ac31653cb9.jpg b/DeployOffice/images/f69d4bed-ab4d-43ac-ae5d-01ac31653cb9.jpg new file mode 100644 index 000000000..e112e35eb Binary files /dev/null and b/DeployOffice/images/f69d4bed-ab4d-43ac-ae5d-01ac31653cb9.jpg differ diff --git a/DeployOffice/images/f8bb9b93-f25d-44ff-b46e-a9e163704663.png b/DeployOffice/images/f8bb9b93-f25d-44ff-b46e-a9e163704663.png new file mode 100644 index 000000000..93d17c15e Binary files /dev/null and b/DeployOffice/images/f8bb9b93-f25d-44ff-b46e-a9e163704663.png differ diff --git a/DeployOffice/images/filter1a.gif b/DeployOffice/images/filter1a.gif new file mode 100644 index 000000000..8a2f9b58a Binary files /dev/null and b/DeployOffice/images/filter1a.gif differ diff --git a/DeployOffice/images/filter1c.gif b/DeployOffice/images/filter1c.gif new file mode 100644 index 000000000..49de223fd Binary files /dev/null and b/DeployOffice/images/filter1c.gif differ diff --git a/DeployOffice/images/footer.gif b/DeployOffice/images/footer.gif new file mode 100644 index 000000000..16bfa5e6d Binary files /dev/null and b/DeployOffice/images/footer.gif differ diff --git a/DeployOffice/images/gradient.gif b/DeployOffice/images/gradient.gif new file mode 100644 index 000000000..017976241 Binary files /dev/null and b/DeployOffice/images/gradient.gif differ diff --git a/DeployOffice/images/greencheck.gif b/DeployOffice/images/greencheck.gif new file mode 100644 index 000000000..4ba17510d Binary files /dev/null and b/DeployOffice/images/greencheck.gif differ diff --git a/DeployOffice/images/greychck.gif b/DeployOffice/images/greychck.gif new file mode 100644 index 000000000..adb8fa1e6 Binary files /dev/null and b/DeployOffice/images/greychck.gif differ diff --git a/DeployOffice/images/header_prev_next.jpg b/DeployOffice/images/header_prev_next.jpg new file mode 100644 index 000000000..2f53424cd Binary files /dev/null and b/DeployOffice/images/header_prev_next.jpg differ diff --git a/DeployOffice/images/header_sql_tutorial_blank.jpg b/DeployOffice/images/header_sql_tutorial_blank.jpg new file mode 100644 index 000000000..aca05662a Binary files /dev/null and b/DeployOffice/images/header_sql_tutorial_blank.jpg differ diff --git a/DeployOffice/images/header_sql_tutorial_logo.GIF b/DeployOffice/images/header_sql_tutorial_logo.GIF new file mode 100644 index 000000000..e0b0bcc5f Binary files /dev/null and b/DeployOffice/images/header_sql_tutorial_logo.GIF differ diff --git a/DeployOffice/images/kw.gif b/DeployOffice/images/kw.gif new file mode 100644 index 000000000..9f0ae0316 Binary files /dev/null and b/DeployOffice/images/kw.gif differ diff --git a/DeployOffice/images/kw_adm.gif b/DeployOffice/images/kw_adm.gif new file mode 100644 index 000000000..5114e8900 Binary files /dev/null and b/DeployOffice/images/kw_adm.gif differ diff --git a/DeployOffice/images/kw_adm_arch.gif b/DeployOffice/images/kw_adm_arch.gif new file mode 100644 index 000000000..9adfaac45 Binary files /dev/null and b/DeployOffice/images/kw_adm_arch.gif differ diff --git a/DeployOffice/images/kw_adm_dev.gif b/DeployOffice/images/kw_adm_dev.gif new file mode 100644 index 000000000..46f6eea3b Binary files /dev/null and b/DeployOffice/images/kw_adm_dev.gif differ diff --git a/DeployOffice/images/kw_adm_dev_arch.gif b/DeployOffice/images/kw_adm_dev_arch.gif new file mode 100644 index 000000000..358f2fa16 Binary files /dev/null and b/DeployOffice/images/kw_adm_dev_arch.gif differ diff --git a/DeployOffice/images/kw_arch.gif b/DeployOffice/images/kw_arch.gif new file mode 100644 index 000000000..fec3452ea Binary files /dev/null and b/DeployOffice/images/kw_arch.gif differ diff --git a/DeployOffice/images/kw_dev.gif b/DeployOffice/images/kw_dev.gif new file mode 100644 index 000000000..d9d6f64ba Binary files /dev/null and b/DeployOffice/images/kw_dev.gif differ diff --git a/DeployOffice/images/kw_dev_arch.gif b/DeployOffice/images/kw_dev_arch.gif new file mode 100644 index 000000000..e784bd6f2 Binary files /dev/null and b/DeployOffice/images/kw_dev_arch.gif differ diff --git a/DeployOffice/images/load.gif b/DeployOffice/images/load.gif new file mode 100644 index 000000000..5035e4f9c Binary files /dev/null and b/DeployOffice/images/load.gif differ diff --git a/DeployOffice/images/load_hover.gif b/DeployOffice/images/load_hover.gif new file mode 100644 index 000000000..c7740c189 Binary files /dev/null and b/DeployOffice/images/load_hover.gif differ diff --git a/DeployOffice/images/note.gif b/DeployOffice/images/note.gif new file mode 100644 index 000000000..54c6ae65b Binary files /dev/null and b/DeployOffice/images/note.gif differ diff --git a/DeployOffice/images/pencil.GIF b/DeployOffice/images/pencil.GIF new file mode 100644 index 000000000..000dcb42a Binary files /dev/null and b/DeployOffice/images/pencil.GIF differ diff --git a/DeployOffice/images/privclass.gif b/DeployOffice/images/privclass.gif new file mode 100644 index 000000000..083c53429 Binary files /dev/null and b/DeployOffice/images/privclass.gif differ diff --git a/DeployOffice/images/privdelegate.gif b/DeployOffice/images/privdelegate.gif new file mode 100644 index 000000000..d3aa8a65e Binary files /dev/null and b/DeployOffice/images/privdelegate.gif differ diff --git a/DeployOffice/images/privdelicate.gif b/DeployOffice/images/privdelicate.gif new file mode 100644 index 000000000..0abc063f7 Binary files /dev/null and b/DeployOffice/images/privdelicate.gif differ diff --git a/DeployOffice/images/privenum.gif b/DeployOffice/images/privenum.gif new file mode 100644 index 000000000..0db234987 Binary files /dev/null and b/DeployOffice/images/privenum.gif differ diff --git a/DeployOffice/images/privenumeration.gif b/DeployOffice/images/privenumeration.gif new file mode 100644 index 000000000..0db234987 Binary files /dev/null and b/DeployOffice/images/privenumeration.gif differ diff --git a/DeployOffice/images/privevent.gif b/DeployOffice/images/privevent.gif new file mode 100644 index 000000000..621e71f47 Binary files /dev/null and b/DeployOffice/images/privevent.gif differ diff --git a/DeployOffice/images/privextension.gif b/DeployOffice/images/privextension.gif new file mode 100644 index 000000000..949ddf066 Binary files /dev/null and b/DeployOffice/images/privextension.gif differ diff --git a/DeployOffice/images/privfield.gif b/DeployOffice/images/privfield.gif new file mode 100644 index 000000000..14120522a Binary files /dev/null and b/DeployOffice/images/privfield.gif differ diff --git a/DeployOffice/images/privinterface.gif b/DeployOffice/images/privinterface.gif new file mode 100644 index 000000000..dddf1a703 Binary files /dev/null and b/DeployOffice/images/privinterface.gif differ diff --git a/DeployOffice/images/privmethod.gif b/DeployOffice/images/privmethod.gif new file mode 100644 index 000000000..ef9baa465 Binary files /dev/null and b/DeployOffice/images/privmethod.gif differ diff --git a/DeployOffice/images/privproperty.gif b/DeployOffice/images/privproperty.gif new file mode 100644 index 000000000..8062b4a72 Binary files /dev/null and b/DeployOffice/images/privproperty.gif differ diff --git a/DeployOffice/images/privstructure.gif b/DeployOffice/images/privstructure.gif new file mode 100644 index 000000000..a2e5f8241 Binary files /dev/null and b/DeployOffice/images/privstructure.gif differ diff --git a/DeployOffice/images/protclass.gif b/DeployOffice/images/protclass.gif new file mode 100644 index 000000000..02944723a Binary files /dev/null and b/DeployOffice/images/protclass.gif differ diff --git a/DeployOffice/images/protdelegate.gif b/DeployOffice/images/protdelegate.gif new file mode 100644 index 000000000..9047a1e32 Binary files /dev/null and b/DeployOffice/images/protdelegate.gif differ diff --git a/DeployOffice/images/protdeligate.gif b/DeployOffice/images/protdeligate.gif new file mode 100644 index 000000000..9047a1e32 Binary files /dev/null and b/DeployOffice/images/protdeligate.gif differ diff --git a/DeployOffice/images/protenum.gif b/DeployOffice/images/protenum.gif new file mode 100644 index 000000000..9ba37e350 Binary files /dev/null and b/DeployOffice/images/protenum.gif differ diff --git a/DeployOffice/images/protenumeration.gif b/DeployOffice/images/protenumeration.gif new file mode 100644 index 000000000..cc96bb635 Binary files /dev/null and b/DeployOffice/images/protenumeration.gif differ diff --git a/DeployOffice/images/protevent.gif b/DeployOffice/images/protevent.gif new file mode 100644 index 000000000..061d0f86f Binary files /dev/null and b/DeployOffice/images/protevent.gif differ diff --git a/DeployOffice/images/protextension.gif b/DeployOffice/images/protextension.gif new file mode 100644 index 000000000..38199bea2 Binary files /dev/null and b/DeployOffice/images/protextension.gif differ diff --git a/DeployOffice/images/protfield.gif b/DeployOffice/images/protfield.gif new file mode 100644 index 000000000..3dd0310ac Binary files /dev/null and b/DeployOffice/images/protfield.gif differ diff --git a/DeployOffice/images/protinterface.gif b/DeployOffice/images/protinterface.gif new file mode 100644 index 000000000..522e7953a Binary files /dev/null and b/DeployOffice/images/protinterface.gif differ diff --git a/DeployOffice/images/protmethod.gif b/DeployOffice/images/protmethod.gif new file mode 100644 index 000000000..2b3467229 Binary files /dev/null and b/DeployOffice/images/protmethod.gif differ diff --git a/DeployOffice/images/protoperator.gif b/DeployOffice/images/protoperator.gif new file mode 100644 index 000000000..cd9e638ec Binary files /dev/null and b/DeployOffice/images/protoperator.gif differ diff --git a/DeployOffice/images/protproperty.gif b/DeployOffice/images/protproperty.gif new file mode 100644 index 000000000..0f41ac3aa Binary files /dev/null and b/DeployOffice/images/protproperty.gif differ diff --git a/DeployOffice/images/protstructure.gif b/DeployOffice/images/protstructure.gif new file mode 100644 index 000000000..af356a1db Binary files /dev/null and b/DeployOffice/images/protstructure.gif differ diff --git a/DeployOffice/images/pubclass.gif b/DeployOffice/images/pubclass.gif new file mode 100644 index 000000000..dac8a7668 Binary files /dev/null and b/DeployOffice/images/pubclass.gif differ diff --git a/DeployOffice/images/pubdelegate.gif b/DeployOffice/images/pubdelegate.gif new file mode 100644 index 000000000..e336e5cca Binary files /dev/null and b/DeployOffice/images/pubdelegate.gif differ diff --git a/DeployOffice/images/pubenum.gif b/DeployOffice/images/pubenum.gif new file mode 100644 index 000000000..a6cb355ff Binary files /dev/null and b/DeployOffice/images/pubenum.gif differ diff --git a/DeployOffice/images/pubenumeration.gif b/DeployOffice/images/pubenumeration.gif new file mode 100644 index 000000000..a6cb355ff Binary files /dev/null and b/DeployOffice/images/pubenumeration.gif differ diff --git a/DeployOffice/images/pubevent.gif b/DeployOffice/images/pubevent.gif new file mode 100644 index 000000000..cc77aa8f3 Binary files /dev/null and b/DeployOffice/images/pubevent.gif differ diff --git a/DeployOffice/images/pubextension.gif b/DeployOffice/images/pubextension.gif new file mode 100644 index 000000000..b7e83d87d Binary files /dev/null and b/DeployOffice/images/pubextension.gif differ diff --git a/DeployOffice/images/pubfield.gif b/DeployOffice/images/pubfield.gif new file mode 100644 index 000000000..590fbfc60 Binary files /dev/null and b/DeployOffice/images/pubfield.gif differ diff --git a/DeployOffice/images/pubinterface.gif b/DeployOffice/images/pubinterface.gif new file mode 100644 index 000000000..1a0038413 Binary files /dev/null and b/DeployOffice/images/pubinterface.gif differ diff --git a/DeployOffice/images/pubmethod.gif b/DeployOffice/images/pubmethod.gif new file mode 100644 index 000000000..4e61c9ff1 Binary files /dev/null and b/DeployOffice/images/pubmethod.gif differ diff --git a/DeployOffice/images/puboperator.gif b/DeployOffice/images/puboperator.gif new file mode 100644 index 000000000..ebc8d6a3e Binary files /dev/null and b/DeployOffice/images/puboperator.gif differ diff --git a/DeployOffice/images/pubproperty.gif b/DeployOffice/images/pubproperty.gif new file mode 100644 index 000000000..074b71a23 Binary files /dev/null and b/DeployOffice/images/pubproperty.gif differ diff --git a/DeployOffice/images/pubstructure.gif b/DeployOffice/images/pubstructure.gif new file mode 100644 index 000000000..6210d3633 Binary files /dev/null and b/DeployOffice/images/pubstructure.gif differ diff --git a/DeployOffice/images/requirements1a.gif b/DeployOffice/images/requirements1a.gif new file mode 100644 index 000000000..3b0879389 Binary files /dev/null and b/DeployOffice/images/requirements1a.gif differ diff --git a/DeployOffice/images/requirements1c.gif b/DeployOffice/images/requirements1c.gif new file mode 100644 index 000000000..d62bda3b5 Binary files /dev/null and b/DeployOffice/images/requirements1c.gif differ diff --git a/DeployOffice/images/save.gif b/DeployOffice/images/save.gif new file mode 100644 index 000000000..0c8224348 Binary files /dev/null and b/DeployOffice/images/save.gif differ diff --git a/DeployOffice/images/save_hover.gif b/DeployOffice/images/save_hover.gif new file mode 100644 index 000000000..7b62e923d Binary files /dev/null and b/DeployOffice/images/save_hover.gif differ diff --git a/DeployOffice/images/security.gif b/DeployOffice/images/security.gif new file mode 100644 index 000000000..b663dbea0 Binary files /dev/null and b/DeployOffice/images/security.gif differ diff --git a/DeployOffice/images/seealso1a.gif b/DeployOffice/images/seealso1a.gif new file mode 100644 index 000000000..7a01e1de8 Binary files /dev/null and b/DeployOffice/images/seealso1a.gif differ diff --git a/DeployOffice/images/seealso1c.gif b/DeployOffice/images/seealso1c.gif new file mode 100644 index 000000000..84f79e71f Binary files /dev/null and b/DeployOffice/images/seealso1c.gif differ diff --git a/DeployOffice/images/static.gif b/DeployOffice/images/static.gif new file mode 100644 index 000000000..d3309435b Binary files /dev/null and b/DeployOffice/images/static.gif differ diff --git a/DeployOffice/images/xna.gif b/DeployOffice/images/xna.gif new file mode 100644 index 000000000..9e6a9d4bd Binary files /dev/null and b/DeployOffice/images/xna.gif differ diff --git a/DeployOffice/licensing-and-activation-data-sent-to-office-365-by-office-365-proplus.md b/DeployOffice/licensing-and-activation-data-sent-to-office-365-by-office-365-proplus.md new file mode 100644 index 000000000..c51380a5b --- /dev/null +++ b/DeployOffice/licensing-and-activation-data-sent-to-office-365-by-office-365-proplus.md @@ -0,0 +1,91 @@ +--- +title: Licensing and activation data sent to Office 365 by Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: f7d07a88-35c3-48f5-b30e-c842f2d911a5 +--- + + +# Licensing and activation data sent to Office 365 by Office 365 ProPlus + + **Summary:** Describes what data Office 365 ProPlus sends to Office 365 services for licensing and activation purposes. + + + + +Computers that have Office 365 ProPlus installed occasionally need to send data to Office 365. This data helps Office 365 do the following: +- Register the computer and activate Office 365 ProPlus + + +- Check the status of the Office 365 subscription + + +- Manage product keys for Office 365 ProPlus + + +This article shows the data that is sent to Office 365 for each of these tasks, and which URLs it is sent to. +## Registering the computer and activating Office 365 ProPlus + + +During the installation and activation process, Office 365 ProPlus connects to the Office Licensing Service, and sends the following data: + + + + +**** + + +|**Data**|**Description**|**Purpose**| +|:-----|:-----|:-----| +|OrgId user identity
|The OrgId ticket generated when the user signs in to Office 365.
|Used to authenticate the call with the Office Licensing Service. The user signs in to their subscription account to retrieve a license for Office 365.
| +|Machine Key
|The serial number of the Office 365 ProPlus product key for the computer.
|Used to uniquely identify the Office 365 ProPlus product key used by the computer.
| +|Machine Name
|The friendly name of the computer, as set by the user in the operating system. For example, if the full name of a computer is "computer1.contoso.com," only "computer1" is sent to Office 365.
|This value is needed so users can identify which computers they have activated Office 365 ProPlus on when they sign in to the Office 365 portal. On the software page, they see a list of their computers and can manage their Office 365 ProPlus installations.
| +|Machine ID
|The hardware ID of the computer.
|Used to uniquely identify that computer.
| + + +## Checking the status of the Office 365 subscription + + +Once Office 365 ProPlus is installed and activated, a process runs once a day to connect to the Office Licensing Service. The purpose is to check whether the Office 365 subscription is still active or if it has changed in any way. The connection needs to succeed at least once a month for Office 365 ProPlus to remain fully functional. + + + +Office 365 ProPlus connects to the Office Licensing Service, and sends the following data: + + + + +**** + + +|**Data**|**Description**|**Purpose**| +|:-----|:-----|:-----| +|Machine Key
|The serial number of the Office 365 ProPlus product key for the computer.
|Used to uniquely identify the Office 365 ProPlus product key used by the computer.
| + + +## Managing product keys for Office 365 ProPlus + + +Office 365 ProPlus uses a standard Microsoft technology called Activation & Validation Service to activate and validate keys. Since Office 365 product keys need to be renewed every month, communication with the Activation & Validation Service is necessary on a monthly basis. + + + +For a description of the data sent, see the Activation section of the [Windows 8 and Windows Server 2012 Privacy Statement](https://go.microsoft.com/fwlink/p/?LinkId=313210) + + + + +## See also + + + +#### Other Resources + + + + + + [Overview of licensing and activation in Office 365 ProPlus](overview-of-licensing-and-activation-in-office-365-proplus.md) + + + + [Office 365 URLs and IP address ranges](https://go.microsoft.com/fwlink/p/?linkid=389789) diff --git a/DeployOffice/manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md b/DeployOffice/manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md new file mode 100644 index 000000000..c49f2d180 --- /dev/null +++ b/DeployOffice/manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md @@ -0,0 +1,174 @@ +--- +title: Manage updates to Office 365 ProPlus with System Center Configuration Manager +ms.prod: OFFICE365 +ms.assetid: b4a17328-fcfe-40bf-9202-58d7cbf1cede +--- + + +# Manage updates to Office 365 ProPlus with System Center Configuration Manager + +System Center Configuration Manager has the ability to manage Office 365 client updates by using the Software Update management workflow. You can use Configuration Manager to update Office 365 ProPlus, Visio Pro for Office 365, Project Online Desktop Client, and Office 365 Business. + + + + +When Microsoft publishes a new Office 365 client update to the Office Content Delivery Network (CDN), Microsoft simultaneously publishes an [update package](manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md#BKMK_Package) to Windows Server Update Services (WSUS). Then, Configuration Manager synchronizes the Office 365 client update from the WSUS catalog to the site server. Configuration Manager can then download the update and distribute it to distribution points selected by the administrator. The Configuration Manager desktop client then tells the Office client where to get the update and when to start the update installation process. +Here's an overview of the steps to enable Configuration Manager to manage Office 365 client updates: + + + + + +1. [Review the requirements](manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md#BKMK_Reqs) + + +2. [Enable Configuration Manager to receive Office 365 client package notifications](manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md#BKMK_EnableCM) + + +3. [Enable Office 365 clients to receive updates from Configuration Manager](manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md#BKMK_EnableClient) + + +After you perform these steps, you can use the software update management capabilities of Configuration Manager to deploy the updates. For more information, see [Manage software updates in System Center Configuration Manager](https://technet.microsoft.com/library/mt613209.aspx). +## Requirements for using Configuration Manager to manage Office 365 client updates + + +To enable Configuration Manager to manage Office 365 client updates, you need the following: + + + + +- System Center Configuration Manager, update 1602 or later + + +- An Office 365 client - Office 365 ProPlus, Visio Pro for Office 365, Project Online Desktop Client, or Office 365 Business + + +- Supported channel version for Office 365 client. For more details, see [Version and build numbers of update channel releases](version-and-build-numbers-of-update-channel-releases.md) + + +- Windows Server Update Services (WSUS) 4.0 + + You can't use WSUS by itself to deploy these updates. You need to use WSUS in conjunction with Configuration Manager + + +- On the computers that have the Office 365 client installed, the [Office COM object is enabled](manage-updates-to-office-365-proplus-with-system-center-configuration-manager.md#BKMK_EnableClient). + + + +## Enable Configuration Manager to receive Office 365 client package notifications + + +To start, you need to configure Configuration Manager to receive notifications when Office 365 client update packages are available. To do that, use the following steps: + + + + +1. In the Configuration Manager console, choose **Site Configuration** > **Sites**, and then select your site server. + + +2. On the **Home** tab, in the **Settings** group, choose **Configure Site Components**, and then choose **Software Update Point**. + + +3. In the **Software Update Point Component Properties** dialog box, do the following: + + - On the **Products** tab, under **Office**, select **Office 365 Client**. + + + - On the **Classifications** tab, select **Updates**. + + + + You can have other check boxes selected in the **Products** and **Classifications** tabs. But, **Office 365 Client** and **Updates** need to be selected for Configuration Manager to receive notifications when Office 365 client update packages are available. + + +4. Next, synchronize software updates. If you don't do that, you won't see the updates in the console and the updates won't be available to deploy. For more information about how to synchronize software updates, see [Introduction to software updates in System Center Configuration Manager](https://docs.microsoft.com/en-us/sccm/sum/understand/software-updates-introduction). + + + +## Enable Office 365 clients to receive updates from Configuration Manager + + +For Configuration Manager to be able to manage Office 365 client updates, an Office COM object needs to be enabled on the computer where Office is installed. The Office COM object takes commands from Configuration Manager to download and install client updates. + + + +You can enable the Office COM object by using the Office Deployment Tool or by using Group Policy. + + + + +### Use Office Deployment Tool to enable Office 365 clients to receive updates from Configuration Manager + + +You can use the latest version of the [Office Deployment Tool](http://go.microsoft.com/fwlink/p/?LinkID=626065) to configure Office 365 clients to receive updates from Configuration Manager. + + + +To configure this capability, use a text editor, such as Notepad, to modify the configuration.xml file for the Office Deployment Tool. In the Add element, include the OfficeMgmtCOM attribute and set its value to True, as seen in the following example. + + + + + + +``` + + + + + + + + + + +``` + +Also, we recommend that you set the value of the Enabled attribute to True in the Updates element. If you set the value of the Enabled attribute to False, Office 365 clients can still receive updates from Configuration Manager. But, users won't see any notifications when updates are pending. + + + +Then, use the Office Deployment Tool and the configuration.xml file to install, for example, Office 365 ProPlus. If you've already installed Office 365 clients to your users, you can run the Office Deployment Tool with the configuration.xml on those computers to update the configuration. But, a better choice to configure computers that are already deployed might be Group Policy. + + + + +### Use Group Policy to enable Office 365 clients to receive updates from Configuration Manager + + +You can enable Configuration Manager to manage Office 365 client updates on specific computers by using Group Policy. This does the same thing as setting the OfficeMgmtCOM attribute to True in the configuration.xml file used by the Office Deployment Tool. But, with Group Policy, you can apply this setting to multiple computers, an organizational unit (OU), or a domain. + + + +To use Group Policy to enable this capability, you do the following: + + + + +- Download and install the [Office 2016 Administrative Template files (ADMX/ADML)](https://www.microsoft.com/download/details.aspx?id=49030) from the Microsoft Download Center. + + +- Enable the **Office 365 Client Management** policy setting. You can find this policy setting under Computer Configuration\\Policies\\Administrative Templates\\Microsoft Office 2016 (Machine)\\Updates. + + + +## Contents of the Office 365 client update package for WSUS + + +The update package that Microsoft publishes to WSUS only appears in the WSUS catalog. It doesn't contain a copy of the updated version of Office that's on the Office CDN. Instead, it contains information that Configuration Manager needs to be able to download and distribute the updated version of Office. + + + +The package contains a file named noop.exe. But, that file doesn't contain any code and shouldn't be downloaded or run. + + + +For each update release there are different packages for each architecture and for each update channel. For example, for the May update release, there is a package for the 32-bit edition of the Current Channel and a package for the 64-bit edition of the Current Channel. In June, there will be two new packages for Current Channel, one for each architecture. The packages contain information so that Configuration Manager knows which packages are more recent than other packages. For example, that the June package supersedes the May package. + + + +There aren't separate packages for the different Office 365 clients. For example, an update package for the 32-bit edition of the Current Channel has information about the Office 365 ProPlus, Visio Pro for Office 365, Project Online Desktop Client, and Office 365 Business clients. + + + + diff --git a/DeployOffice/overview-deploying-languages-in-office-365-proplus.md b/DeployOffice/overview-deploying-languages-in-office-365-proplus.md new file mode 100644 index 000000000..cf1346bbe --- /dev/null +++ b/DeployOffice/overview-deploying-languages-in-office-365-proplus.md @@ -0,0 +1,33 @@ +--- +title: Overview Deploying languages in Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 6467979c-3430-45c2-a28f-f9ac995731a5 +--- + + +# Overview: Deploying languages in Office 365 ProPlus +Resources for Click-to-Run for Office 365 products are packaged similarly to the way standard Office 2016 Windows Installer (MSI) resources are organized. Language-neutral product resources are packaged into a single file that contains all the neutral resources. Language-specific resources are packaged into language-specific files such as en-us for English (United States) resources.If you purchased an Office 365 subscription, you can use it to install Office in multiple languages. You do not have to buy a Language Pack. If your organization allows it, users can install Office 365 ProPlus languages directly from the [Office 365 portal](https://go.microsoft.com/fwlink/p/?LinkID=212232). When users install Office from the **software** page, they select a language from the **Language** drop-down box.In managed enterprise environments, end-users may not have permission to install software from the Office 365 portal. If you are configuring an on-premises deployment of Office 365 Click-to-Run applications for users in your organization, you can use the Office 2016 Deployment Tool to install Click-to-Run in multiple languages. The [Language elements](http://technet.microsoft.com/library/a204ecad-e546-4c9f-93a7-2b8a7ac1fb21%28Office.14%29.aspx#BKMK_LanguageElement) language elements that you specify in the configuration file for the Office 2016 Deployment Tool determine which languages will be installed. Administrators must specify the languages they want to install. The first language determines the Shell UI language. The Shell UI is the language that is used to display shortcuts, right-click context menus, and tooltips.If you decide that you want to change the Shell UI language after an initial installation, you have to uninstall Click-to-Run and reinstall it. Add the language that you want to set for the Shell UI as the first language in the custom Configuration.xml file.Additional language tools that you can install for Click-to-Run products include the following: +- **Language Interface Packs:** Translated User Interface that installs over a copy of a Click-to-Run installation. You can download and install a Language Interface Pack for free. After you install it, you can use Microsoft Excel, OneNote, Microsoft Outlook, PowerPoint, and Word features in a different language. You can use the **Office Language Preferences** dialog after installation to change a language and see a translated user interface. For information about how to change the editing, display or Help language for Office applications, see [Enable the use of other languages in your Office programs](https://go.microsoft.com/fwlink/p/?LinkId=281959). To set Office 2016 language options on a computer that is running Windows 10, type "Office 2016" at the **Start** screen, and select **Office 2016 Language Preferences** to open the **Microsoft Office 2016 Language Preferences** dialog box. + + +- **Proofing Tools:** Localized language versions of Office include proofing tools for a set of companion langauges. For more details and links to proofing tool downloads for each language, see [Proofing Tools for Office 365 ProPlus](proofing-tools-for-office-365-proplus.md). + + +- **ScreenTip Language:** Translations that show the text of display elements such as buttons, menus, and dialog boxes in another language. You can download [Microsoft Office ScreenTip Language 2013](https://go.microsoft.com/fwlink/p/?LinkId=281983) from the Microsoft Download Center. ScreenTip Language installs over a Click-to-Run installation. + + +For information about how to use the Configuration.xml file to specify language installation options, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md). +## See also + + +#### Other Resources + + + + + + [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) + + + + [Proofing Tools for Office 365 ProPlus](proofing-tools-for-office-365-proplus.md) diff --git a/DeployOffice/overview-of-licensing-and-activation-in-office-365-proplus.md b/DeployOffice/overview-of-licensing-and-activation-in-office-365-proplus.md new file mode 100644 index 000000000..bb8aea36b --- /dev/null +++ b/DeployOffice/overview-of-licensing-and-activation-in-office-365-proplus.md @@ -0,0 +1,131 @@ +--- +title: Overview of licensing and activation in Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 1096c33e-a6f2-44c8-9821-3cba07ec5750 +--- + + +# Overview of licensing and activation in Office 365 ProPlus + + **Summary:** Explains how to assign Office 365 ProPlus licenses to users, and how individual installations are activated. + + + + +To deploy Office 365 ProPlus to users in your organization, you start by assigning licenses to your users. Then, each user can install Office 365 ProPlus on up to five computers. Each installation is activated and kept activated automatically by cloud-based services associated with Office 365. This means you don't have to keep track of product keys. It also means you don't have to figure out how to use other activation methods such as Key Management Service (KMS) or Multiple Activation Key (MAK). All you have to do is make sure you purchase enough licenses, keep your Office 365 subscription current, and make sure your users can connect to Office Licensing Service via the Internet at least once every 30 days. +> [!NOTE] +> The information in this article also applies to Project Online Desktop Client and Visio Pro for Office 365, which are licensed separately from Office 365 ProPlus. + + + + + +## Licensing Office 365 ProPlus + + +The number of available licenses available for Office 365 ProPlus depends on your organization's Office 365 subscription level. To assign a license to a user, you select a check box on the licenses page for the user's account. + + + + + + + +![Office 365 licenses](images/15b018fe-c12e-4d78-9287-bc95d5e14cac.png) + + + + + + + +After that's done, the user can install Office directly from the Office 365 portal or you can deploy Office to your users from your local network. + + + +You can remove a user's license (for example, if the user leaves your organization). After you do this, any installations of Office 365 ProPlus that the user had go into [reduced functionality mode](overview-of-licensing-and-activation-in-office-365-proplus.md#BKMK_ReducedFunctionalityMode). The Office Licensing Service, a part of Office 365, keeps track of which users are licensed and how many computers they've installed Office on. + + + + +## Activating Office 365 ProPlus + + +As part of the installation process, Office 365 ProPlus communicates with the Office Licensing Service and the Activation and Validation Service to obtain and activate a product key. Each day, or each time the user logs on to their computer, the computer connects to the Activation and Validation Service to verify the license status and extend the product key. As long as the computer can connect to the Internet at least once every 30 days, Office remains fully functional. If the computer goes offline for more than 30 days, Office enters [reduced functionality mode](overview-of-licensing-and-activation-in-office-365-proplus.md#BKMK_ReducedFunctionalityMode) until the next time a connection can be made. To get Office fully functional again, usually a user can simply connect to the Internet and let the Activation and Validation Service reactivate the installation. + + + + +> [!IMPORTANT] +> Because of its online activation features, Office 365 ProPlus won't work on computers that are completely cut off from the Internet. For those computers, we recommend installing Office Professional Plus 2016 and using a [traditional activation method](https://technet.microsoft.com/EN-US/library/ee705504%28v=office.16%29.aspx) such as Key Management Service (KMS) or Active Directory Domain Services. + + + + + +### Managing activated installations + +Each Office 365 ProPlus license allows a user to install Office on up to five computers. The user manages installations in the Office 365 portal: + + + + + + + +![Managing Office 365 active installations](images/c830ebad-a255-4e32-8d7a-af5a687dc107.png) + + + + + + + +If the user decides to install Office 365 ProPlus on a sixth computer, she will need to deactivate one of the first five. Office 365 ProPlus goes into [reduced functionality mode](overview-of-licensing-and-activation-in-office-365-proplus.md#BKMK_ReducedFunctionalityMode) on the deactivated computer. + + + + +## What is reduced functionality mode? + + +In reduced functionality mode, Office 365 ProPlus remains installed on the computer, but users can only view and print their documents. All features for editing or creating new documents are disabled, and the user sees a message like the following: + + + + + + + +![Product deactivated](images/78aa59b0-8772-4ba2-8094-bfeb65602ab7.png) + + + + + + + +The user can then choose one of the available options to reactivate Office 365 ProPlus on that computer. + + + + +## See also + + + +#### Other Resources + + + + + + [Licensing and activation data sent to Office 365 by Office 365 ProPlus](licensing-and-activation-data-sent-to-office-365-by-office-365-proplus.md) + + + + [About Office 365 ProPlus in the enterprise](about-office-365-proplus-in-the-enterprise.md) + + + + [Choose how to deploy Office 365 ProPlus](choose-how-to-deploy-office-365-proplus.md) diff --git a/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus.md b/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus.md new file mode 100644 index 000000000..97587617f --- /dev/null +++ b/DeployOffice/overview-of-shared-computer-activation-for-office-365-proplus.md @@ -0,0 +1,159 @@ +--- +title: Overview of shared computer activation for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 836f882c-8ff6-4f19-8b24-0212e0111c94 +--- + + +# Overview of shared computer activation for Office 365 ProPlus + +Shared computer activation lets you to deploy Office 365 ProPlus to a computer in your organization that is accessed by multiple users. For example, several nurses at a hospital connect to the same remote server to use their applications or a group of workers share a computer at a factory. + + + + +The most common shared computer activation scenario is to [deploy Office 365 ProPlus to shared computers by using Remote Desktop Services (RDS)](deploy-office-365-proplus-by-using-remote-desktop-services.md). By using RDS, multiple users can connect to the same remote computer at the same time. The users can each run Office 365 ProPlus programs, such as Word or Excel, at the same time on the remote computer. +Shared computer activation is used only for situations where multiple users share the same computer. If you have users who are assigned individual computers, you [use product key activation for Office 365 ProPlus](overview-of-licensing-and-activation-in-office-365-proplus.md). + + + + + +## How to enable shared computer activation for Office 365 ProPlus + + +If you have an [Office 365 plan](https://go.microsoft.com/fwlink/p/?LinkId=510587) that includes Office 365 ProPlus, you can use shared computer activation. Make sure you [Assign or remove licenses for Office 365 for business](http://technet.microsoft.com/library/997596b5-4173-4627-b915-36abac6786dc%28Office.14%29.aspx) for Office 365 ProPlus and that users log on to the shared computer with their own user account. + + + + +> [!NOTE] +> You also can use shared computer activation to install Visio Pro for Office 365 or Project Online Desktop Client on a shared computer, if you have a subscription plan that includes those products. + + + + +To enable shared computer activation when you deploy Office 365 ProPlus, you need the following: + + + + +- The current version of the Office 2016 version of the Office Deployment Tool, which is available from the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkID=626065). + + +- At least version 15.0.4631.1002 of Office 365 ProPlus, which was released in July 2014. + + > [!TIP] + > To determine which version of Office 365 ProPlus is installed on a user's computer, go to **File** > **Account** in any Office 365 ProPlus program. The version is listed under the **Office Updates** section. + + You can download the Office 365 ProPlus software to your local network by using the [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md). + + +The Office Deployment Tool, combined with a simple text file, is used to install Office 365 ProPlus on the shared computer, and to enable shared computer activation for that computer. Add the following lines when you [create the text file](configuration-options-for-the-office-2016-deployment-tool.md). + + + + + + +``` + + + +``` + +After Office 365 ProPlus is installed, you can [verify that shared computer activation is enabled](http://technet.microsoft.com/library/c3aeb487-d45f-4079-8c35-7558a45b876cf%28Office.14%29.aspx#Enabled) on that computer. + + + + +## How shared computer activation works for Office 365 ProPlus + + +Here's what happens after Office 365 ProPlus is installed on a computer that has shared computer activation enabled. + + + + +1. A user logs on to the computer with her account. + + +2. The user starts an Office 365 ProPlus program, such as Word. + + +3. Office 365 ProPlus contacts the Office Licensing Service on the Internet to obtain a licensing token for the user. + + To determine whether the user is licensed to use Office 365 ProPlus, the Office Licensing Service has to know the user's account for Office 365. In some cases, Office 365 ProPlus prompts the user to provide the information. For example, the user might see the **Activate Office** dialog box. + + ![Activate Office](images/9cb7eef4-0ce6-428a-8f96-890e5237d17a.png) + + + If your environment is configured to synchronize Office 365 and network user accounts, then the user probably won't see any prompts. Office 365 ProPlus should automatically be able to get the necessary information about the user's account in Office 365. + + +4. If the user is licensed for Office 365 ProPlus, a licensing token is stored on the computer in the user's profile folder, and Office 365 ProPlus is activated. The user can now use Office 365 ProPlus. + + +These steps are repeated for each user who logs on to the shared computer. Each user gets a unique licensing token. Just because one user activates Office 365 ProPlus on the computer doesn't mean Office 365 ProPlus is activated for all other users who log on to the computer. + + + +If a user goes to another computer that also is enabled for shared computer activation, the same steps occur. There is a different licensing token for each computer that the user logs on to. + + + +If a user logs on to a shared computer again, Office 365 ProPlus uses the same licensing token, if it is still valid. + + + + +## Additional details about shared computer activation for Office 365 ProPlus + + + +- **Licensing token renewal** The licensing token that is stored on the shared computer is valid only for a few days. As the expiration date for the licensing token nears, Office 365 ProPlus automatically attempts to renew the licensing token when the user is logged on to the computer and using Office 365 ProPlus. + + If the user doesn't log on to the shared computer for several days, the licensing token can expire. The next time that the user tries to use Office 365 ProPlus, Office 365 ProPlus contacts the Office Licensing Service on the Internet to get a new licensing token. + + +- **Internet connectivity** Because the shared computer has to contact the Office Licensing Service on the Internet to obtain or renew a licensing token, reliable connectivity between the shared computer and the Internet is necessary. + + +- **Reduced functionality mode** If the user is not licensed for Office 365 ProPlus, or if the user closed the **Activate Office** dialog box, no licensing token is obtained and Office 365 ProPlus isn't activated. Office 365 ProPlus is now in reduced functionality mode. This means that the user can view and print Office 365 ProPlus documents, but can't create or edit documents. The user also sees a message in Office 365 ProPlus that most features are turned off. + + ![Reduced functionality](images/4e25a9fc-1844-4204-9b9d-40603ca1a091.png) + + + + + +- **Activation limits** Normally, users can install and activate Office 365 ProPlus only on up to five computers. Using Office 365 ProPlus with shared computer activation enabled doesn't count against the five computer limit. + + Microsoft allows a single user to activate Office 365 ProPlus on a reasonable number of shared computers in a given time period. The user gets an error message in the unlikely event the limit is exceeded. + + ![Too many computers activated message](images/e01c8a45-1814-4bfe-bb7e-c0176f393031.png) + + + + + + +## See also + + + +#### Other Resources + + + + + + [Deploy Office 365 ProPlus by using Remote Desktop Services](deploy-office-365-proplus-by-using-remote-desktop-services.md) + + + + [Troubleshoot issues with shared computer activation for Office 365 ProPlus](c3aeb487-d45f-4079-8c35-7558a45b876c.md) + + + + [Overview of licensing and activation in Office 365 ProPlus](overview-of-licensing-and-activation-in-office-365-proplus.md) diff --git a/DeployOffice/overview-of-the-office-2016-deployment-tool.md b/DeployOffice/overview-of-the-office-2016-deployment-tool.md new file mode 100644 index 000000000..aadf3ea43 --- /dev/null +++ b/DeployOffice/overview-of-the-office-2016-deployment-tool.md @@ -0,0 +1,460 @@ +--- +title: Overview of the Office 2016 Deployment Tool +ms.prod: OFFICE365 +ms.assetid: bb5b62d9-1168-47e9-9d54-15a958acfcca +--- + + +# Overview of the Office 2016 Deployment Tool + +The Office 2016 Deployment Tool (ODT) is a command-line tool that you can use to download and deploy Office 365 ProPlus to your client computers. The ODT gives you more control over an Office installation: you can define which products and languages are installed, how those products should be updated, and whether or not to display the install experience to your users. + + + + +If you're not an enterprise administrator and are looking to install Office UNRESOLVED_TOKEN_VAL(365) in your home or business, see [Install Office with Office 365](https://go.microsoft.com/fwlink/?LinkId=273820). +## Download the Office 2016 Deployment Tool + +Download the Office 2016 Deployment Tool from the [Microsoft Download Center](http://go.microsoft.com/fwlink/p/?LinkID=626065). + + + +After downloading the file, run the self-extracting executable file, which contains the Office 2016 Deployment Tool executable (setup.exe) and a sample configuration file (configuration.xml). + + + +Before using the ODT to download or install Office, we recommend making sure you have the latest version. + + + + +## Get started with the Office 2016 Deployment Tool + + +The ODT consists of two files: setup.exe and configuration.xml. To work with the tool, you edit the configuration file to define what options you want, and then run setup.exe from the command line. For example, you can edit the configuration file to download the 32-bit English edition of Office, or you can edit the file to install the 32-bit English edition of Office with the EULA automatically accepted and without Publisher. For the full set of options, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md). + + + +When running the ODT, you provide the location of the configuration file and define which *mode* the ODT should run in: + + + + +- To download Office 365 ProPlus products and languages, use **download** mode. Example: `setup.exe /download downloadconfig.xml` + + +- To install the downloaded Office 365 ProPlus products and languages on a client computer, use **configure** mode. You also use configure mode to remove and update Office products and languages. Example: `setup.exe /configure installconfig.xml` + + +- To create an App-V package from the downloaded Office 365 ProPlus products and languages, use **packager** mode. Example: `setup.exe /packager packageconfig.xml` + + +You can also use **help** mode to read command-line help for the tool. + + + + +## Download the installation files for Office 365 ProPlus + + +Follow these steps to download installation files for Office 365 ProPlus from the Office Content Delivery Network (CDN). + + + + **Step 1: Create the configuration file** + + + +When creating the configuration file, we recommend starting with an example file and updating it with the appropriate options for your environment. You can start by copying and pasting the example below into a text file, saving it with a name of your choosing, and then editing the XML elements and attributes to define the options you want. + + + +In this example, the configuration file downloads the installation files for a 32 bit English edition of Office 365 ProPlus 2016 and Visio Pro for Office 365 to \\\\server\\share on your network: + + + + + + +``` + + + + + + + + + + + + + +``` + +For more information about the configuration options and more examples, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md). + + + + **Step 2: Run the ODT executable in download mode** + + + +From a command prompt, run the ODT executable in download mode and with a reference to the configuration file you just saved. In this example, the configuration file is named **downloadconfig.xml:** + + + + `setup.exe /download downloadconfig.xml` + + + + **Step 3: Validate that the files have been downloaded** + + + +After running the command, go to the download location you defined in the configuration file and look for an Office folder with the appropriate files in it. If you run into problems, make sure you have the newest version of the ODT. You can also troubleshoot issues by reviewing the log file in the %temp% directory. + + + + +## Download the installation files for Office 365 ProPlus from a local source + + +You can use the Office 2016 Deployment Tool to download the installation files for Office 365 ProPlus from a local source on your network instead of from the Office Content Delivery Network (CDN). By doing so, you can store a central copy of multiple languages and products for Office and distribute just the languages and products that you need to other locations on your network. + + + +To download from a local source, follow the steps for downloading Office with the ODT, but include in your configuration file the download path, which defines where the installation files are downloaded from. For example, this configuration file downloads a 32 bit English edition of Office 365 ProPlus 2016 from **\\\\servera\\share** (the DownloadPath) to **\\\\serverb\\share** (the SourcePath): + + + + + + +``` + + + + + + + + + +``` + +Note that you must specify a **Version** when using DownloadPath. + + + + +## Install Office 365 ProPlus 2016 + + +After you download Office 365 ProPlus installation files, follow these steps to install Office on a client computer. As part of that installation, you can choose which products to install. + + + + **Step 1: Create the configuration file** + + + +When creating the configuration file, we recommend starting with an example file and updating it with the appropriate options for your environment. You can start by copying and pasting the example below into a text file, saving it with a name of your choosing, and then editing the XML elements and attributes to define the options you want. + + + +In this example, the configuration file installs a 32 bit English edition of Office 365 ProPlus 2016 without Publisher: + + + + + + +``` + + + + + + + + + + + +``` + +The location of the Office installation files is **\\\\server\\share**. The display level is set to **None**, which means the user will not see any user interface during the install, and the AcceptEULA is set to **TRUE**, which means your users will not have to click to accept the EULA during the installation. + + + +For more information about the configuration options, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md). + + + + **Step 2: Run the ODT executable in configure mode** + + + +From a command prompt, run the ODT executable in configure mode with a reference to the configuration file you just saved. In the following example, the configuration file is named **installconfig.xml**: + + + + `setup.exe /configure installconfig.xml` + + + +You must run the executable from the client computer on which you want to install Office and you must have local administrator permissions on that computer. + + + + **Step 3: Verify that installation was successful** + + + +After running the command, you should see the Office installation start (unless you set display level to none). After installation is complete, the command prompt will display "Products configured successfully." If you run into problems, make sure you have the newest version of the ODT. You can also troubleshoot issues by reviewing the log files in the %temp% and %windir%\\temp directories. + + + + +## Update Office 365 ProPlus + + +You can use the Office 2016Deployment Tool to make updates to your client computers after installing Office 365 ProPlus. There are two ways to do this: + + + + +- Use the ODT to install Office 365 ProPlus again, which will update Office to the newest version. Only the files that have changed in the new version will be updated. + + +- Use the ODT to download the Office installation files and then point your client computers to that location to receive their updates. (By default, clients are updated directly from the Office Content Delivery Network (CDN).) + + +To change where your client computers receive their updates, run the ODT in configure mode and specify an update path in the configuration file. For example, to have Office 365 ProPlus get updates automatically from a network share called **\\\\server\\updates**, include the following line in your configuration.xml file: + + + + `` + + + +This article does not cover all the issues related to managing updates for Office in your organization. For more information on that end-to-end scenario, including using Group Policy, see [Choose how to manage updates to Office 365 ProPlus](choose-how-to-manage-updates-to-office-365-proplus.md). + + + + +## Exclude or remove Office 365 ProPlus products from client computers + + +When installing Office 365 ProPlus, you can exclude specific products. To do so, follow the steps for installing Office with the ODT, but include the ExcludeApp element in your configuration file. For example, this configuration file installs all the Office 365 ProPlus products except Publisher: + + + + +``` + + + + + + + + +``` + +If you've already installed Office 365 ProPlus, you can also use the ExcludeApp element to remove a product that you've previously installed. For example, the configuration file above removes Publisher from the previous installation of Office. + + + +You can also remove an entire language version of Office 365 ProPlus. To do so, follow the steps for excluding products for installing Office with the ODT, but replace the configuration file with one that uses the **Remove** element. For example, this configuration file removes the Spanish language version of Office 365 ProPlus: + + + + + + +``` + + + + + + + + + +``` + +For more information about the options for excluding or removing apps, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md). + + + + +## Install Office in the same language as the client operating system + + +When using the ODT, you can automatically install the Office language that matches the display language of the client operating system. To do so, use **** in the configuration file. + + + +For example, this configuration file installs the 32-bit edition of Office 365 ProPlus in the same language as the client operating system--English for clients with the display language of English, Japanese for clients with Japanese, and so on: + + + + + + +``` + + + + + + + + + +``` + + +## Add languages to existing installations of Office 365 ProPlus + + +After installing Office, you can add use the ODT to install additional language packs for Office. To do so, you follow the steps for installing Office with the ODT, but use a new configuration file that indicates which languages to add. The new configuration file does not contain (and should not contain) any settings for Office, such as excluded apps or which channel to update. All those client settings are preserved when the new language packs are installed. If your clients are updated from a local source on your network, you must also download the Office installation files for the languages you want to add to that source. + + + + **Step 1: Download the Office installation files in the languages you want to add** + + + +If Office in your organization is updated from a local source, you must download the Office installation files for the languages you want to add. + + + + **Step 2: Create the configuration file for adding the language packs** + + + +When creating the configuration file, we recommend starting with an example file and updating it with the appropriate options for your environment. You can start by copying and pasting the example below into a text file, saving it with a name of your choosing, and then ensuring that the OfficeClientEdition and language IDs are what you want. + + + +In this example, the configuration file installs the French and Japanese language packs: + + + + + + +``` + + + + + + + + + + +``` + +It's important to emphasize that all the settings defined when you deployed or updated Office are preserved. For example, the source for the language pack is not provided in this configuration file--instead, the ODT will look for it in the source path defined in the configuration file you used to deploy Office. + + + +For a list of all languages, see [Language identifiers](https://technet.microsoft.com/EN-US/library/cc179219%28v=office.16%29.aspx). + + + + **Step 3: Run the ODT executable in configure mode** + + + +From a command prompt, run the ODT executable in configure mode with a reference to the configuration file you just saved. In the following example, the configuration file is named **installlanguage.xml**: + + + + `setup.exe /configure installlanguage.xml` + + + +You must run the executable from the client computer on which you want to install Office and you must have local administrator permissions on that computer. + + + + +## Create an App-V package for Office 365 ProPlus + + +In addition to downloading and deploying Office 365 ProPlus, you can use the Office 2016 Deployment Tool to create App-V packages. To do so, update the configuration file and then run the ODT in packager mode. You must create App-V packages on a computer with a clean install of the operating system. + + + +This article does not cover all the issues related to deploying App-V packages. For more information on that end-to-end scenario, see [Deploying Microsoft Office 2016 by Using App-V](https://technet.microsoft.com/en-us/library/mt590515.aspx). + + + + **Step 1: Create the configuration file** + + + +When creating the configuration file, we recommend starting with an example file and updating it with the appropriate options for your environment. You can start by copying and pasting the example below into a text file, saving it with a name of your choosing, and then editing the XML elements and attributes to define the options you want. + + + +In this example, the configuration file creates an App-V package from a 32-bit English edition of Office 365 ProPlus 2016 without Publisher: + + + + + + +``` + + + + + + + + + + +``` + +The location of the Office installation files is \\\\server\\share. For your configuration file, substitute the example values with the appropriate option for your environment. For more information about the options, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md), + + + + **Step 2: Run the ODT executable in packager mode** + + + +From a command prompt, run the ODT executable in packager mode with a reference to the configuration file you just saved and to the location where you want to save the App-V package. In the following example, the configuration file is named **packageconfig.xml** and the App-V package will be saved to **\\\\server\\share\\appv\\**: + + + + `setup.exe /packager packageconfig.xml \\\\server\\share\\appv\\` + + + + **Step 3: Verify that the package was created** + + + +After running the command, the package location should have an App-V Packages folder and a WorkingDir folder. You can troubleshoot issues by reviewing the log file in the %temp% directory. + + + + +## Related Topics + + + [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) + + + + diff --git a/DeployOffice/overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md b/DeployOffice/overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md new file mode 100644 index 000000000..1717e417b --- /dev/null +++ b/DeployOffice/overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md @@ -0,0 +1,258 @@ +--- +title: Overview of the upcoming changes to Office 365 ProPlus update management +ms.prod: OFFICE365 +ms.assetid: 78b33779-9356-4cdf-9d2c-08350ef05cca +--- + + +# Overview of the upcoming changes to Office 365 ProPlus update management + +On April 20th, we announced some changes to better align the Office 365 ProPlus and Windows 10 update models. In that [blog post](https://go.microsoft.com/fwlink/p/?linkid=846981), we highlighted these key changes: + + + + + +- **Two updates a year.** We will reduce the Office 365 ProPlus update cadence from three to two times a year, with semi-annual feature updates to Windows 10 and Office 365 ProPlus planned for March and September. + + +- **18 months of support.** We will extend the support period for Office 365 ProPlus semi-annual feature updates from 12 to 18 months (starting from the initial release) so IT professionals can choose to update once or twice a year. + + + +As part of these changes, Office 365 ProPlus is changing the names of its update channels to make them more descriptive. + + + + +All these changes will take effect in September 2017. +> [!NOTE] +> These changes also apply to Visio Pro for Office 365 and Project Online Desktop Client. + + + + +The following information is intended to help you understand these upcoming changes and understand what steps, if any, you need to take when it comes to updating Office 365 ProPlus on Windows 10. +- [The names of the Office 365 ProPlus update channels are changing](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Names) + + +- [The default enterprise release schedule for Office 365 ProPlus is changing to twice a year](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Schedule) + + +- [The support duration for Semi-annual Channel releases is increasing](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Duration) + + +- [The purpose of each Office 365 ProPlus update channel stays the same](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Purpose) + + +- [How you deploy updates for Office 365 ProPlus stays the same](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Deploy) + + +- [Recommended next steps](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Steps) + + +- [Upcoming schedule for Office 365 ProPlus releases](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Upcoming) + + + +## The names of the Office 365 ProPlus update channels are changing + + +We heard your feedback and we are making the names for our update channels more descriptive. + + + +Here is a list of the name changes for Office 365 ProPlus. We'll start using the new names in September 2017. + + + + + +|**New name**|**Old name**| +|:-----|:-----| +|Monthly Channel
|Current Channel
| +|Semi-annual Channel (Targeted)
|First Release for Deferred Channel
| +|Semi-annual Channel
|Deferred Channel
| + + +> [!NOTE] +> We've made some slight changes to the names for Semi-annual Channel. We've changed "(Pilot)" to "(Targeted)" and we've removed the "(Broad)" designation from the new name for Deferred Channel. These names will be aligned across Windows 10 and Office 365 ProPlus feature update releases. > For information about upcoming changes to the names of Windows 10 feature update releases, [read this blog post](http://blogs.technet.microsoft.com/windowsitpro/2017/07/27/waas-simplified-and-aligned/). + + + + + +## The default enterprise release schedule for Office 365 ProPlus is changing to twice a year + + +Currently, Office 365 ProPlus gets feature updates in First Release for Deferred Channel in February, June, and October. Those feature updates are then available in Deferred Channel four months later. + + + +Starting in September 2017, Office 365 ProPlus will get feature updates in Semi-annual Channel (Targeted) twice a year, in March and September. Those feature updates will then be available in Semi-annual Channel four months later, in July and January. + + + +Windows 10 also plans to target the March and September time frames for feature updates to Windows 10 in order to provide customers with a more predictable, consistent release schedule. The first alignment of Office 365 ProPlus and Windows 10 semi-annual releases is currently planned for September 2017. + + + +Office 365 ProPlus will continue to receive security updates and quality updates monthly, as needed, for these update channels on the second Tuesday of each month. There are no changes to the Office 365 ProPlus release schedule for Monthly Channel. + + + + +> [!IMPORTANT] +> Office still plans to release a new Deferred Channel and First Release for Deferred Channel on June 13, 2017. The new semi-annual schedule begins on September 12, 2017. This is a month earlier than the previously planned October release, so plan accordingly. For more information, see [Upcoming schedule for Office 365 ProPlus releases](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Upcoming) and [Recommended next steps](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Steps). + + + + + + + + + +## The support duration for Semi-annual Channel releases is increasing + + +With the change to a twice-a-year release schedule, the semi-annual feature update releases of Office 365 ProPlus will now be supported for 18 months, instead of 12 months, starting from the initial release. + + + +A new version, with feature updates, will be released to Semi-annual Channel (Targeted) in March and September. Four months later, that version, with those feature updates, will be released in Semi-annual Channel and will be supported for the next 14 months. For example, a new version of Semi-annual Channel (Targeted) will be released in March 2018. In July 2018, that version will be made available in Semi-annual Channel and will be supported until September 2019. + + + +This change provides more time and flexibility for IT Pros to deploy releases. For example, customers who want to update once a year will be able to do so with the extended support duration on Semi-annual Channel. For customers who want to get new features as quickly as possible, we will continue to offer an update channel that provides monthly feature updates. + + + +System Center Configuration Manager will support Office 365 ProPlus and Windows 10 across their 18 month support period. + + + + +## The purpose of each Office 365 ProPlus update channel stays the same + + +The names are changing, but the purpose of each update channel remains the same. For example, Monthly Channel, formerly named Current Channel, is still the release that provides new features to Office 365 ProPlus approximately every month. + + + +The following table provides a summary of the purpose, target audience, and release frequency of each update channel. + + + + + +||**Monthly Channel**|**Semi-annual Channel (Targeted)**|**Semi-annual Channel**| +|:-----|:-----|:-----|:-----| +|**Purpose**
|Monthly updates with the latest features
|IT pilots, application validation, and end-user acceptance testing before broad deployment
|Broad deployment
| +|**Target audience**
|Representative end users, developers, and ISVs
|IT testers, app and add-in owners, representative end users
|All enterprise end users
| +|**Release frequency**
|Monthly
|Twice per year, in March and September
|Twice a year, in January and July
| + +Semi-annual Channel (Targeted) releases for Office 365 ProPlus are intended to provide enterprises time to pilot and to validate their line-of-business applications, add-ins, and macros with Office 365 ProPlus before Semi-annual Channel is released. If you find problems with a release of Semi-annual Channel (Targeted), provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://go.microsoft.com/fwlink/p/?linkid=847275) agreement or your Microsoft account representative. + + + +The following illustration shows the relationship between the Office 365 ProPlus update channels and the approximate release schedule. + + + + + + + +![Office 365 update channels, showing the new update channel names and release cadence](images/16fae804-8d79-43db-8902-2adbbc6e0c9e.png) + + + +For more information about the Office 365 ProPlus and Windows 10 update models, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) and [Windows 10 servicing branches](https://go.microsoft.com/fwlink/p/?linkid=847276). + + + + +## How you deploy updates for Office 365 ProPlus stays the same + + +Even though there are changes to release names, release schedules, and support duration, how you update Office 365 ProPlus remains the same. + + + +For example, if Office 365 ProPlus is currently configured to use Deferred Channel and to get updates directly from the Office Content Delivery Network (CDN), there are no changes you need to make for the January 2018 release of the first Semi-annual Channel. You will continue to get updated automatically. + + + +If you manage the update process by downloading updated versions of Office 365 ProPlus and then deploying those updates with your enterprise software deployment tools, such as System Center Configuration Manager, you can continue to do that just like you have been doing. + + + + +## Recommended next steps + + +If you are currently using Deferred Channel, and doing enterprise pilots and application validation on First Release for Deferred Channel, be sure to review the [Upcoming schedule for Office 365 ProPlus releases](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Upcoming). Be aware that there will only be three months, instead of four months, to do enterprise pilots and application validation on the version of First Release for Deferred Channel that is scheduled to be released on June 13, 2017. + + + +If you've just started deploying Office 365 ProPlus, we recommend that you have less than 10% of your users on First Release for Deferred Channel to do your enterprise pilots and application validation. + + + +If your organization hasn't yet deployed Office 365 ProPlus or Windows 10, you can learn more here: + + + + +- [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) + + +- [Best practices guide for deploying Office 365 ProPlus in the enterprise](best-practices-guide-for-deploying-office-365-proplus-in-the-enterprise.md) + + +- [Application compatibility readiness](https://aka.ms/officeappcompat) + + +- [Windows 10 deployment considerations](https://go.microsoft.com/fwlink/p/?linkid=847277) + + +- [Overview of Windows as a service](https://go.microsoft.com/fwlink/p/?linkid=847278) + + +For deployment assistance with Office 365 ProPlus or Windows 10, [contact FastTrack ](https://go.microsoft.com/fwlink/p/?linkid=847279). + + + + +## Upcoming schedule for Office 365 ProPlus releases + + +The change to the Office 365 ProPlus release cadence begins with the release currently scheduled for September 12, 2017. + + + + +> [!IMPORTANT] +> Office still plans to release a new Deferred Channel and First Release for Deferred Channel on June 13, 2017. The first version of Semi-annual Channel (Targeted) is scheduled to be released on September 12, 2017. This is a month earlier than the previously planned October release, so plan accordingly. The first Semi-annual Channel is scheduled to be released on January 9, 2018. For more information, see the schedule listed below and [Recommended next steps](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md#BKMK_Steps). + + + + +Here's a schedule of key upcoming dates for Office 365 ProPlus releases, separated by update channel. All dates are approximate and not all dates are listed. + + + + + +|**Date**|**First Release for Deferred Channel
Semi-annual Channel (Targeted)**|**Deferred Channel
Semi-annual Channel**|**IT Pro action to take**| +|:-----|:-----|:-----|:-----| +|June 13, 2017
| New features are released to First Release for Deferred Channel.
Enterprise pilots and application validation should begin.
This is the last release using the name "First Release for Deferred Channel."
The next release with new features is scheduled for September 12, 2017.
**Important:** You only have 3 months, instead of 4 months, to do enterprise pilots and application validation, since the next release is scheduled for September, so plan accordingly.
| New features are released to Deferred Channel.
This version of Deferred Channel is supported until January 2018.
The next release with new features is scheduled for September 12, 2017.
**Important:** The next release with new features is only 3 months away, instead of 4 months, so plan accordingly.
| Continue to deploy these update channels in your environment as you have been doing previously.
For enterprise pilots, validate your line-of-business applications, add-ins, and macros with First Release for Deferred Channel.
If you find problems with First Release for Deferred Channel, provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://go.microsoft.com/fwlink/p/?linkid=847275) agreement or your Microsoft account representative.
| +|July 11, 2017
August 8, 2017
| If needed, quality updates and security updates are released to First Release for Deferred Channel.
This is the regular update schedule for this update channel.
| If needed, quality updates and security updates are released to Deferred Channel.
This is the regular update schedule for this update channel.
| Continue to update these update channels in your environment as you have been doing previously.
Continue to do enterprise pilots and application validation with First Release for Deferred Channel, and provide feedback to Microsoft, as needed.
| +|September 12, 2017
| The first Semi-annual Channel (Targeted) is released.
This release contains new features.
Enterprise pilots and application validation should begin.
This is the first release with the new name and the new release schedule.
The next release with new features is scheduled for March 13, 2018.
| New features are released to Deferred Channel.
This version of Deferred Channel is supported until July 2018.
This is the last release using the name "Deferred Channel."
The next release with new features is scheduled for January 9, 2018.
| Continue to deploy these update channels in your environment as you have been doing previously. Even though the names and cadence are changing, how you deploy remains the same.
For enterprise pilots, validate your line-of-business applications, add-ins, and macros with Semi-annual Channel (Targeted).
If you find problems with Semi-annual Channel (Targeted), provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://go.microsoft.com/fwlink/p/?linkid=847275) agreement or your Microsoft account representative.
Be sure to be aware of the new release schedule. There is no longer a release in October for Deferred Channel or for First Release for Deferred Channel.
| +|January 9, 2018
|| The first Semi-annual Channel is released.
This release contains new features.
This version of Semi-annual Channel is supported until March 2019.
This is the first release with the new name, new release schedule, and the new support duration.
The next release with new features is scheduled for July 10, 2018.
| Continue to deploy this update channel in your environment as you have been doing previously. Even though the name and cadence has changed, how you deploy remains the same.
Be sure to be aware of the new release schedule. There is no longer a release in February or June for Deferred Channel or for First Release for Deferred Channel.
| +|March 13, 2018
| New features are released to Semi-annual Channel (Targeted).
Enterprise pilots and application validation should begin.
The next release with new features is scheduled for September 11, 2018.
|| Continue to deploy this update channel in your environment as you have been doing previously. Even though the name and cadence has changed, how you deploy remains the same.
For enterprise pilots, validate your line-of-business applications, add-ins, and macros with Semi-annual Channel (Targeted).
If you find problems with Semi-annual Channel (Targeted), provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://go.microsoft.com/fwlink/p/?linkid=847275) agreement or your Microsoft account representative.
| +|July 10, 2018
|| New features are released to Semi-annual Channel.
This version of Semi-annual Channel is supported until September 2019.
The next release with new features is scheduled for January 8, 2019.
| Continue to deploy this update channel in your environment as you have been doing previously. Even though the name and cadence has changed, how you deploy remains the same.
| +|September 11, 2018
| New features are released to Semi-annual Channel (Targeted).
Enterprise pilots and application validation should begin.
The next release with new features is scheduled for March 12, 2019.
|| Continue to deploy this update channel in your environment as you have been doing previously. Even though the name and cadence has changed, how you deploy remains the same.
For enterprise pilots, validate your line-of-business applications, add-ins, and macros with Semi-annual Channel (Targeted).
If you find problems with Semi-annual Channel (Targeted), provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://go.microsoft.com/fwlink/p/?linkid=847275) agreement or your Microsoft account representative.
| + + diff --git a/DeployOffice/overview-of-the-update-process-for-office-365-proplus.md b/DeployOffice/overview-of-the-update-process-for-office-365-proplus.md new file mode 100644 index 000000000..8f36f220d --- /dev/null +++ b/DeployOffice/overview-of-the-update-process-for-office-365-proplus.md @@ -0,0 +1,151 @@ +--- +title: Overview of the update process for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 936cda26-41f9-45b5-a1f9-f9e1f485d23b +--- + + +# Overview of the update process for Office 365 ProPlus + +Unlike earlier versions of Office, individual security updates and other updates for Office 365 ProPlus aren't available on Windows Update. Instead, every time that updates are released — usually the second Tuesday of each month — Microsoft creates an updated version of Office 365 ProPlus and puts it on the Internet. This updated version contains all the updates for that month, in addition to all updates from previous months. Each updated version of Office 365 ProPlus is available on the Internet for 12 months. After 12 months, that specific version is no longer supported. + + + + + +> [!IMPORTANT] +> Because individual updates aren't available for Office 365 ProPlus, you can't use Windows Update, Windows Server Update Services (WSUS), or System Center Configuration Manager to download and apply individual updates to Office 365 ProPlus. + + + + + +To determine which version of Office 365 ProPlus is installed on a user's computer, go to **File > Account** in any Office program. The version is listed under the **Office Updates** section. + + + + + + + + +![Office version at Office Updates](images/15f0ae22-60d6-4484-838a-08b5e1312988.jpg) + + + + + + + + + + + + +## Update process for Office 365 ProPlus + + +There are three steps that occur automatically when the update process runs for Office 365 ProPlus: + + + + +1. Detect that updates are available + + +2. Download the updates + + +3. Apply the updates + + + +### Detect that updates are available for Office 365 ProPlus + + +When you install Office 365 ProPlus, a scheduled task called Office Automatic Updates is created. This scheduled task is configured to look for updates at the following times: + + + + +- Every Sunday, Tuesday, and Friday, at a randomly selected time between 3:00 AM and 7:00 AM. + + +- 15, 30, and 75 minutes after the user logs on to the computer. + + + + + + +![Automatic updates](images/2a4e0cfb-828b-4881-9db9-468a2b597b7d.jpg) + + + +When the task runs, it compares the version of Office 365 ProPlus on the computer to the version of Office 365 ProPlus on the update location. The update location is where Office looks for updates — for example, on a network share or from the Internet. By default, Office 365 ProPlus looks on the Internet for updates, but you can [configure the update location](configure-update-settings-for-office-365-proplus.md). + + + +If there's a difference between the two versions, the update process determines which files are different and need to be updated on the local computer. After that, the next step — downloading the updates — starts. + + + + +### Download the updates for Office 365 ProPlus + + +Only the files that are different are copied down to a Download folder on the local computer, and they're downloaded in a compressed form. This helps reduce the size of the download. + + + +The size of the download depends on several factors, such as how many security and other updates are released in a given month, and which version of Office 365 ProPlus you're updating from. For example, if you have the March version of Office 365 ProPlus installed, and you're updating to the July version, it's likely that more files are different between those two versions, than if you're updating from the June to the July version. Therefore, the download will probably be larger. + + + + +> [!NOTE] +> Starting in July 2014, the update process automatically uses a technology called binary delta compression to help reduce the size of the files downloaded even more. But, this technology is only used if you're updating from the most recent version of Office 365 ProPlus. For example, binary delta compression is used if you're updating from the June to the July version, but not if you're updating from the May to the July version. + + + + +If the download process is interrupted — for example, by a temporary loss of network connectivity — the download resumes after the interruption, instead of restarting from the beginning. After the updates are downloaded, the computer doesn't have to be connected to the Internet or the network for the updates to be applied. That's because all the files that are needed to apply the updates are already on the local computer. + + + + +### Apply the updates for Office 365 ProPlus + + +After the compressed files are downloaded, they're uncompressed and moved from the Download folder to the Apply folder. The scheduled task then attempts to install the updates in the background, without requiring any user intervention. + + + +Updates can't be applied if the Office program that has to be updated is being used by the user. If this is the case, the task tries to apply the updates the next time that the scheduled task runs. If updates can't be applied for several days, [users see a message](end-user-update-notifications-for-office-365-proplus.md) that updates are ready to install. If the user restarts the computer and updates haven't been applied, the updates are applied as Windows starts. This won't prevent the user from logging in. + + + +To make sure that users apply updates, you can [configure a deadline](configure-update-settings-for-office-365-proplus.md). The deadline specifies a date and time by when the updates must be applied. If the updates aren't applied by the deadline, Office automatically closes any open Office programs and applies the updates. Users are given [notifications leading up to the deadline](end-user-update-notifications-for-office-365-proplus.md). + + + + +## See also + + + +#### Other Resources + + + + + + [Choose how to manage updates to Office 365 ProPlus](choose-how-to-manage-updates-to-office-365-proplus.md) + + + + [Configure update settings for Office 365 ProPlus](configure-update-settings-for-office-365-proplus.md) + + + + [End-user update notifications for Office 365 ProPlus](end-user-update-notifications-for-office-365-proplus.md) diff --git a/DeployOffice/overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md b/DeployOffice/overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md new file mode 100644 index 000000000..9bf1cb015 --- /dev/null +++ b/DeployOffice/overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md @@ -0,0 +1,146 @@ +--- +title: Overview of the upgrade of Office 365 ProPlus to the Office 2016 version +ms.prod: OFFICE365 +ms.assetid: 7655b5cb-89ae-4a08-9621-e5af1b77cfe1 +--- + + +# Overview of the upgrade of Office 365 ProPlus to the Office 2016 version + + **Summary:** Provides information about the upgrade of Office 365 ProPlus to the Office 2016 version, including criteria for the upgrade and the steps taken during upgrade. + + + + +If you deployed the Office 2013 version of Office 365 ProPlus to the users in your organization, then you need to be aware of an upgrade coming from Microsoft. This will upgrade the Office apps, such as Word and Excel, from the Office 2013 version to the Office 2016 version. For information on the schedule for this upgrade, [review these key dates](upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Key). +> [!IMPORTANT] +> Support for the Office 2013 version of Office 365 ProPlus ended on February 28, 2017. For more information, see Microsoft Knowledge Base (KB) article [3199744.](https://support.microsoft.com/kb/3199744) + + + + +Before the upgrade begins, users see an upgrade notification when they open an Office app, such as Word. The notification appears just under the ribbon. Office is upgraded only if the user chooses **Update Office**. + + + +![Update Office notification](images/00a4d1a9-4c89-4534-93ed-affb3f47dde7.png) + + + +Not every user will see an upgrade notification. For example, only users that are local administrators on their computer see the upgrade notification. Also, only Office 2013 installations that meet [certain criteria](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md#BKMK_Criteria) receive an upgrade notification.The first check is to see how Office is configured to get updates. As shown in the following table, only Office installations that are configured to get updates automatically from the Office Content Delivery Network (CDN) on the Internet are considered for this upgrade. + +|**Update configuration**|**Considered for upgrade**| +|:-----|:-----| +|Automatically from the Office Content Delivery Network (CDN) on the Internet
|Yes
| +|Automatically from a location other than the CDN, such as an internal network share
|No
| +|Automatic updates disabled
|No
| + +You can look in the registry of the computer to [determine if Office is configured to get updates from the CDN](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md#BKMK_DetermineCDN). + +> [!NOTE] +> This information also applies to Visio Pro for Office 365 and Project Online Desktop Client. It also applies to Office 365 Business, which is the version of Office that comes with some Office 365 plans, such as Business Premium. + + + + + +## Criteria used to determine if Office can be upgraded successfully + + +Before upgrading to the Office 2016 version, Microsoft checks to see if Office can be upgraded successfully. It determines this by looking at the following criteria: + + + + +- Office is configured to get updates automatically from the CDN. + + +- Office has installed the most recent update. + + +- There is at least 3 GB of disk space available. + + +- Office isn't configured to use shared computer activation. + + +- If Project or Visio is installed on the computer, they are the subscription versions. + + +- If Project or Visio is installed on the computer, they are using the same language configuration as Office. + + +- Outlook can't be connected to Exchange Server 2007. + + +- Exchange Server that Outlook uses is configured to support Autodiscover. + + +- Business Contact Manager isn't installed on the computer. + + +If any of these criteria aren't met, then Microsoft won't attempt to upgrade Office. + + + +Also, there is a check to see if the user is a local administrator on the computer. If the user isn't a local administrator, then the user won't see the upgrade notification when an Office app is opened. That's because a user must be a local administrator on the computer to install or upgrade Office. + + + + +## Steps performed during the upgrade to Office 2016 + + +If it's determined that the Office installation is a suitable candidate to be upgraded, the following steps occur: + + + + +1. The files needed to upgrade to Office 2016 are downloaded in the background to the computer. The user can continue to use Office while the download occurs. Be aware that there are [network bandwidth implications](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Bandwidth) of each user downloading the files needed to upgrade Office. + + +2. The next time a user who is a local administrator on the computer opens an Office app, such as Word, the user sees a message below the ribbon letting them know that an upgrade is available. + + ![Update Office notification](images/00a4d1a9-4c89-4534-93ed-affb3f47dde7.png) + + + + + +3. If the user chooses to upgrade, the necessary steps are performed to remove Office 2013 and install Office 2016. No additional downloading is needed for this step. + + If there is a subscription version of Project or Visio installed on the computer, those also get upgraded to the 2016 version. + + +If the user chooses to ignore or close the **Get the new Office** message, the message reappears again the next time the user opens an Office app. + + + + +## Timing of the upgrade notifications + + +Not all Office installations that meet the criteria to be upgraded get the upgrade notification at the same time. Microsoft initially sends the notification to a small percentage of Office installations. Then, over time, Microsoft increases the number of notifications that it sends out. This means that it's likely that users in your organization will get upgrade notifications at different times, even possibly a week or more apart. + + + +Once Microsoft starts sending out upgrade notifications, users can upgrade Office before receiving a notification. They can start the upgrade by going to **File** > **Account** > **Update Options** in any Office app, and then choosing **Update Now**. If the Office installation meets all the [criteria](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md#BKMK_Criteria), the upgrade starts. Remember that users have to be local administrators on their computers to install or upgrade Office. + + + + +## See also + + + +#### Other Resources + + + + + + [Plan your upgrade from Office 365 ProPlus 2013 to 2016](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md) + + + + [Upgrade from Office 365 ProPlus 2013 to 2016](upgrade-from-office-365-proplus-2013-to-2016.md) diff --git a/DeployOffice/overview-of-update-channels-for-office-365-proplus.md b/DeployOffice/overview-of-update-channels-for-office-365-proplus.md new file mode 100644 index 000000000..c529f10a3 --- /dev/null +++ b/DeployOffice/overview-of-update-channels-for-office-365-proplus.md @@ -0,0 +1,245 @@ +--- +title: Overview of update channels for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 9ccf0f13-28ff-4975-9bd2-7e4ea2fefef4 +--- + + +# Overview of update channels for Office 365 ProPlus + +> [!IMPORTANT] +> On April 20, we announced changes to better align the Office 365 ProPlus and Windows 10 update models. In that [blog post](https://go.microsoft.com/fwlink/p/?linkid=846981), we highlighted changes to the release cadence and the support duration of feature updates for Office 365 ProPlus. As part of these changes, Office 365 ProPlus is also changing the names of its update channels. > For more information about these changes, see [Overview of the upcoming changes to Office 365 ProPlus update management](overview-of-the-upcoming-changes-to-office-365-proplus-update-management.md). > As most of these changes take effect in September 2017, this content will be updated in the next few months. + + + + +One of the benefits of Office 365 ProPlus is that Microsoft can provide new features for Office apps on a regular basis, through monthly updates. However, as the admin who deploys Office 365 ProPlus to the users in your organization, you might want to have more control over how often your users get these new features. For the Office 2016 version of Office 365 ProPlus, Microsoft provides you three options, called update channels, to control how often Office 365 ProPlus is updated with new features. Here's an overview of the three options. + +|**Update channel**|**Primary purpose**|**How often updated with new features**|**Default update channel for the following products**| +|:-----|:-----|:-----|:-----| +| [Current Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_CB)
|Provide users with the newest features of Office as soon as they're available.
|Monthly
|Visio Pro for Office 365
Project Online Desktop Client
Office 365 Business, which is the version of Office that comes with some Office 365 plans, such as Business Premium.
| +| [Deferred Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_CBB)
|Provide users with new features of Office only a few times a year.
|Every four months
|Office 365 ProPlus
| +| [First Release for Deferred Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB)
|Provide pilot users and application compatibility testers the opportunity to test the next Deferred Channel.
|Every four months
|None
| + +Which update channel you decide to deploy to your users depends on several factors, including how many line-of-business applications, add-ins, or macros that you need to test any time there is an updated version of Office 365 ProPlus. To help you make this decision, review the following information about the three update channels that are available for Office 365 ProPlus. +## Current Channel for Office 365 ProPlus + + +Current Channel might be the right choice for your organization in the following situations: + + + + +- You want to provide your users with the newest features of Office as soon as those features are available + + +- You don't have many line-of-business applications, add-ins, or macros that you need to test to determine if they work with an updated version of Office. + + +A new Current Channel is expected to be released at least once each month. The release can contain new or updated features, security updates, and non-security updates, such as updates that provide stability or performance improvements for Office. Not every Current Channel release will contain all of these. For example, there might be some months where there aren't any new features. + + + +A Current Channel release is supported only until the next Current Channel release is available. No new security updates are provided for previous Current Channel releases. + + + + +> [!NOTE] +> There is also First Release for Current Channel. This update channel provides an early look at the next Current Channel release. First Release for Current Channel is the same update channel that those in the [Office Insider](https://www.office.com/insider) program receive. + + + + + +## Deferred Channel for Office 365 ProPlus + + +If your organization doesn't want to deploy the latest features of Office right away or you have a significant number of line-of-business applications, add-ins, or macros that you need to test with Office, than Deferred Channel might be the better choice for your organization. That's because Deferred Channel is made available only a few times a year, instead of every month. Deferred Channel is the default update channel for Office 365 ProPlus. + + + +A new Deferred Channel is expected to be released every four months. It can contain new features, security updates, and non-security updates, such as updates that provide stability or performance improvements for Office. In the four months prior to a new Deferred Channel release, Microsoft provides builds of the upcoming release so that pilot users and application compatibility testers in your organization can work with the release. These builds are called [First Release for Deferred Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB). + + + + Deferred Channel won't have all the new features included in the most recent Current Channel. The features included in Deferred Channel are the features from the Current Channel four months ago. This four month difference is intended to give your organization time to test the new features. If you want some of your users to have the very latest features of Office 365 ProPlus, you can provide those users with Current Channel. + + + +The first Deferred Channel release will be available approximately four months after the release of Office 2016. After a Deferred Channel release is available, it only gets security updates, if there are any, in the following months. After it's been released, no new features are added to Deferred Channel. The next time you'll receive new features, if there are any, is when the next Deferred Channel release is made available. + + + +A Deferred Channel release is supported for eight months. When a new Deferred Channel release is made available, you can continue to use the Deferred Channel release that you've deployed. But four months later, when another Deferred Channel is released, your original Deferred Channel release is no longer supported and won't get any more security updates. + + + +Here's an example that might help clarify this: + + + + +- A new Deferred Channel is released. Let's refer to that as DC1. You deploy DC1 to the users in your organization. + + +- Four months later, another Deferred Channel release comes out - DC2. You decide not to deploy it. You stay with DC1 and continue to get security updates. + + +- Four months after that, DC3 is released. At this point, DC1 is no longer supported and won't get any new security updates. To stay on a supported release, you can either deploy DC2 or DC3 to the users in your organization. But keep in mind that in four more months, when DC4 is released, DC2 won't be supported anymore. + + +There are always two Deferred Channel releases available and supported. + + + + +## First Release for Deferred Channel for Office 365 ProPlus + + +To help your organization prepare for a Deferred Channel release, Microsoft provides First Release for Deferred Channel. This update channel is provided approximately four months before the availability of the next Deferred Channel. The primary purpose of this update channel is to give pilot users and application compatibility testers in your organization a chance to work with the upcoming Deferred Channel release. During this time, you might identify possible issues that you need to fix with your line-of-business applications, add-ins, or macros or that you want Microsoft to fix. + + + +During this four month testing phase, no new features are added to First Release for Deferred Channel. But, security updates and non-security updates, such as updates that provide stability or performance improvements for Office, can be added to this update channel. + + + +The initial First Release for Deferred Channel is expected to be available soon after Office 2016 is released. An updated version will be available approximately every month. Even though this update channel is primarily designed for your testing, it's a fully supported version of Office 365 ProPlus. + + + +After a Deferred Channel is released, a new First Release for Deferred Channel is made available to start testing the next Deferred Channel. + + + + +## Visual representation of the update channels for Office 365 ProPlus + + +Here's an illustration of how a Current Channel release is used to create a First Release for Deferred Channel release and how a First Release for Deferred Channel release becomes a Deferred Channel release. The illustration also shows that a Deferred Channel release continues to get security updates for up to eight months. Although not shown in the illustration, a First Release for Deferred Channel release also gets security updates during the four months it's available. + + + + + + + +![Update Channels visual representation](images/6769367a-3c03-4ada-94d4-6c75228aabb2.png) + + + + + + + + + + + + +## Frequency of updates for the update channels for Office 365 ProPlus + + +As a review, the following table provides information about how often each update channel can include feature updates, security updates, and non-security updates, such as updates that provide stability or performance improvements for Office. That doesn't mean an update channel contains any or all of these types of updates. For example, there might be a month when Current Channel doesn't contain any new or updated features. + + + + + +|**Update channel**|**Feature updates**|**Security updates**|**Non-security updates**| +|:-----|:-----|:-----|:-----| +| [Current Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_CB)
|Monthly
|Monthly
|Monthly
| +| [Deferred Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_CBB)
|Every four months
|Monthly
|Every four months
| +| [First Release for Deferred Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB)
|Every four months
|Monthly
|Monthly
| + + +## Configure the update channel to be used by Office 365 ProPlus + + +Deferred Channel is the default update channel for Office 365 ProPlus. But you can configure an Office 365 ProPlus installation to use Current Channel or First Release for Deferred Channel. Also, not all users in your organization have to be configured the same. For example, you might do the following: + + + + +- Provide a group of pilot users with Current Channel, so they can try out the new features of Office as they become available. + + +- Provide your finance department, which has several key line-of-business applications, with Deferred Channel. + + +- Provide your application compatibility testers with First Release for Deferred Channel so that they can test that the finance applications will work with the next Deferred Channel release. + + +To configure the update channel for an Office 365 ProPlus installation, you can use the latest version of the [Office Deployment Tool](http://go.microsoft.com/fwlink/p/?LinkID=626065) or use the [Group Policy Administrative Templates files (ADMX/ADML) ](https://www.microsoft.com/download/details.aspx?id=49030) for Office 2016. + + + +If you use the Office Deployment Tool, you can use the Channel attribute in the configuration.xml file. The Channel attribute can be specified in the Add element or the Update element. The relevant values are Current, Deferred, and FirstReleaseDeferred. For example, if you want to download and install the Current Channel of Office 365 ProPlus, your configuration.xml file would look like the following example. + + + + + + +``` + + + + + + + + +``` + +The name of the Group Policy setting is Update Channel. You can find this policy setting under Computer Configuration\\Administrative Templates\\Microsoft Office 2016 (Machine)\\Updates. The relevant choices when you enable the Group Policy setting are Current, Deferred, and FirstReleaseDeferred. + + + +You can also provide users with First Release for Deferred Channel by selecting them for the [First Release program for Office 365](https://support.office.com/article/3B3ADFA4-1777-4FF0-B606-FB8732101F47). If you do this, those users can install First Release for Deferred Channel directly from the **Software** page in the Office 365 portal. + + + + +## Additional information about the update channels for Office 365 ProPlus + + +Here is some additional information that might be useful to know as you determine how to configure and use Current Channel, Deferred Channel, and First Release for Deferred Channel in your organization. + + + + +- You can switch an Office 365 ProPlus installation from one update channel to another. For example, you might want to move a user from Current Channel to Deferred Channel. To switch update channels, you can use the Office Deployment Tool or Group Policy. + + +- If the user does an Online Repair of Office 365 ProPlus, the installation reverts to Deferred Channel, unless you've configured a Group Policy setting to provide a different update channel. + + +- If you have Visio Pro for Office 365 or Project Online Desktop Client installed on the same computer as Office 365 ProPlus, they all must use the same update channel. You can't have a mix of update channels on the same computer. + + + +## See also + + + +#### Other Resources + + + + + + [Version and build numbers of update channel releases](version-and-build-numbers-of-update-channel-releases.md) + + + + [Change management for Office 365 clients](change-management-for-office-365-clients.md) + + + + [Office 365 client update channel releases](https://go.microsoft.com/fwlink/?LinkId=626090) + + + + [Plan your upgrade from Office 365 ProPlus 2013 to 2016](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md) diff --git a/DeployOffice/plan-your-upgrade-from-office-365-proplus-2013-to-2016.md b/DeployOffice/plan-your-upgrade-from-office-365-proplus-2013-to-2016.md new file mode 100644 index 000000000..631573aa9 --- /dev/null +++ b/DeployOffice/plan-your-upgrade-from-office-365-proplus-2013-to-2016.md @@ -0,0 +1,265 @@ +--- +title: Plan your upgrade from Office 365 ProPlus 2013 to 2016 +ms.prod: OFFICE365 +ms.assetid: 733ff07f-8137-46e6-9904-70f59d716f6f +--- + + +# Plan your upgrade from Office 365 ProPlus 2013 to 2016 + +Office 2016 is the latest version of Microsoft's productivity apps, such as Word, PowerPoint, Excel, and Microsoft Outlook. You can provide the Office 365 ProPlus users in your organization with the new and enhanced features of Office 2016 by upgrading those users from the Office 2013 version of Office 365 ProPlus to the Office 2016 version. + + + + + +> [!IMPORTANT] +> Support for the Office 2013 version of Office 365 ProPlus ended on February 28, 2017. For more information, see Microsoft Knowledge Base (KB) article [3199744.](https://support.microsoft.com/kb/3199744) + + + + + +Before you upgrade your users to the Office 2016 version, we recommend that you review the following information so that you can develop a plan of how best to upgrade your existing Office 365 ProPlus installations. Some of the key steps in the planning process include the following: + + + + + +- [Review the system requirements](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_SysReqs) + + +- [Determine which update channel to use](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Channel) + + +- [Download the latest version of the Office Deployment Tool](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_ODT) + + +- [Copy existing Group Policy settings](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_GP) + + +- [Review the network bandwidth implications](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Bandwidth) + + +- [Understand how long you can continue to use the Office 2013 version](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Office2013) + + +- [Understand when upgrades will occur](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_WhenUpdates) + + +- [Prepare to support additional languages](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Languages) + + + +## Review the system requirements for Office 365 ProPlus + + + + + + +With any new software release, you should [review the system requirements](https://products.office.com/office-system-requirements) to ensure that your computers meet those requirements. For example, for Office 2016, the minimum requirement is now 2 GB of RAM. + + + +Another important change to be aware of is that Outlook 2016 doesn't support connecting to Exchange Server 2007. + + + + +## Determine which update channel to use for Office 365 ProPlus + + +In Office 2016, you can control how fast your users receive feature updates to Office 365 ProPlus. One choice is a monthly update to Office 365 ProPlus, which can contain new or updated features, security updates, and non-security updates, such as updates that provide stability or performance improvements for Office. This is called the Current Channel release. + + + +If your organization doesn't want to deploy the latest features of Office right away or you have a significant number of line-of-business applications, add-ins, or macros that you need to test with Office, then Deferred Channel might be the better choice for your organization. That's because Deferred Channel is made available only a few times a year, instead of every month. Deferred Channel is the default update channel for Office 365 ProPlus. + + + +To help your organization prepare for a Deferred Channel release, Microsoft provides First Release for Deferred Channel. This update channel is provided approximately four months before the availability of the next Deferred Channel. The primary purpose of this update channel is to give pilot users and application compatibility testers in your organization a chance to work with the upcoming Deferred Channel release. During this time, you might identify possible issues that you need to fix with your line-of-business applications, add-ins, or macros or that you want Microsoft to fix. + + + +For more information, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md). + + + + +## Download the latest Office Deployment Tool to deploy Office 365 ProPlus + + +In order to support new deployment capabilities available for the Office 2016 version of Office 365 ProPlus, there is a new version of the Office Deployment Tool. You can [download this new version](http://go.microsoft.com/fwlink/p/?LinkID=626065) from the Microsoft Download Center. The configuration.xml file used by the latest Office Deployment Tool supports new settings that allow you to configure the following: + + + + +- Which update channel to use + + +- Which language accessory packs to install + + +Also, be aware that the new version of the Office Deployment Tool can't be used to deploy the Office 2013 version of Office 365 ProPlus. You can continue to [use the previous version of the Office Deployment Tool](http://www.microsoft.com/download/details.aspx?id=36778) for those deployments. + + + + +## Copy existing Group Policy settings for Office 365 ProPlus + + +As with any new version of Office, there is a new set of Administrative Template files (ADMX/ADML) for Group Policy settings. You can [download the Administrative Template files](https://www.microsoft.com/download/details.aspx?id=49030) from the Microsoft Download Center. + + + +We've added some new settings, but maintained most of the existing Group Policy settings to help minimize changes you need to make. However, the registry location for the Group Policy settings has changed, so you need to copy your existing Group Policy settings to account for this change. All Group Policy settings for Office are now located in HKEY_LOCAL_MACHINE\\SOFTWARE\\Policies\\Microsoft\\Office\\16.0 and HKEY_CURRENT_USER\\SOFTWARE\\Policies\\Microsoft\\Office\\16.0, where 16.0 is the designation for Office 2016. For Office 2013, the Group Policy settings are located in keys named 15.0. + + + + + + + + +## Review the network bandwidth implications of upgrading Office 365 ProPlus + + +The installation files for Office 365 ProPlus are approximately 850 mb for the core files plus approximately 200 mb for each language deployed. Because of the underlying changes between the Office and Office 2016 versions of Office 365 ProPlus, the upgrade process takes longer and requires the entire Office 2016 build to be downloaded to users' computers. This will affect network bandwidth and is something that should be considered as part of your upgrade plan. + + + + +## Understand how long you can continue to use the Office 2013 version of Office 365 ProPlus + + +Support for the Office 2016 version of Office 365 ProPlus ends on February 28, 2017. Therefore, we recommend that you upgrade to the Office 2016 version of Office 365 ProPlus as soon as possible. For more information, see Microsoft Knowledge Base (KB) article [3199744](https://support.microsoft.com/kb/3199744). + + + +If you choose to continue to deploy the Office 2016 version of Office 365 ProPlus, you need to do the following: + + + + +- Continue to use the [Office 2013 version of the Office Deployment Tool](http://www.microsoft.com/download/details.aspx?id=36778). + + +- Make sure that your users' computers are configured to get updates from a location on your internal network. You can configure this either by using the Office Deployment Tool or by using Group Policy and the **Update Path** policy setting, + + + +## Understand when upgrades to Office 365 ProPlus will occur + + +The way that the users in your organization receive the upgrade to Office 2016 depends on where you've configured Office 365 ProPlus to get updates. + + + + +- **From the Internet** If you've configured your users to get updates directly from the Office Content Delivery Network (CDN) on the Internet, the upgrade to Office 2016 will occur based on this [schedule](upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Key). At that time, the Office 2016 files will be automatically downloaded to users' computers and the upgrade of Office 365 ProPlus will occur. For more information about the upgrade, [read this overview](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md). + + If you don't want these users to be upgraded, configure them to get updates from a location on your internal network. You can configure this either by using the Office Deployment Tool or by using Group Policy and the **Update Path** policy setting. + + +- **From a location on your internal network** If you've configured your users to get updates from a location on your internal network, then the upgrade to Office 2016 is under your control. When you're ready to upgrade your users, use the [Office 2016 version of the Office Deployment Tool](http://go.microsoft.com/fwlink/p/?LinkID=626065) to download the Office 2016 version of Office 365 ProPlus. Then, you'll need to use the Office Deployment Tool to install the Office 2016 version to your users. Just copying the Office 2016 files to the update location on your internal network isn't enough. You need to initiate the installation with the Office Deployment Tool to get Office 365 ProPlus to upgrade to the Office 2016 version. If you had certain configuration settings implemented for your 2013 installation, such as excluding certain apps from being installed or enabling shared computer activation, be sure that your configuration.xml file for the 2016 installation includes those same configuration settings. + + + +> [!IMPORTANT] +> **Downloading updates with the Office Deployment Tool** If you want to start using the Office 2016 version of Office 365 ProPlus before February, the following releases are available now:> Current Channel> First Release for Deferred Channel> To download and install either of these releases, use the new version of the [Office Deployment Tool](http://go.microsoft.com/fwlink/p/?LinkID=626065) and use the [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) in your configuration.xml file.> > **Installing from the Office 365 portal** Until February 2016, the version of Office 365 ProPlus that gets installed from the **Software** page on the Office 365 portal will remain the Office 2016 version. In February that will change to the Office 2016 version and it will be the Deferred Channel release.> > If, before February, you want some or all of your users to be able to install the Office 2016 version of Office 365 ProPlus from the **Software** page, you can enable the [Set up the Standard or First Release options in Office 365](http://technet.microsoft.com/library/3B3ADFA4-1777-4FF0-B606-FB8732101F47%28Office.14%29.aspx) and select which users you want to include. Those users can then install either the 2013 or 2016 versions from the **Software** page. + + + + + +## Prepare to support additional languages with Office 365 ProPlus + + +There is a change to the way additional languages are deployed in the Office 2016 version of Office 365 ProPlus. Previously, in Office, you could deploy an MSI-based language pack after you installed Office 365 ProPlus, even though those language packs weren't specifically designed to be used with Office 365 ProPlus. In Office 2016, using those language packs is no longer supported. + + + +Instead, with Office 2016, you install [Language Accessory Pack for Office 2016](http://technet.microsoft.com/library/82ee1236-0f9a-45ee-9c72-05b026ee809f%28Office.14%29.aspx) after you've deployed Office 365 ProPlus in one of its 40 base languages. + + + +There are two ways to install language accessory packs: + + + + +- Have your users download and install the language accessory packs that they need. There will be a link on the **Software** page in the Office 365 portal to the language accessory packs. + + +- Use the Office Deployment Tool to deploy the appropriate language accessory packs to your users + + +You can't just install a language accessory pack by itself. It needs to be installed along with or after Office 365 ProPlus has been installed in one of the 40 base languages. + + + + +## Additional planning considerations for upgrading Office 365 ProPlus + + +The following are some additional considerations that you may need to take into account as you develop your plan to upgrade the users in your organization to the Office 2016 version of Office 365 ProPlus. + + + + +### Support policy for installing other versions of Office side-by-side with Office 365 ProPlus + + +You can't have the Office 2013 and the Office 2016 version of Office 365 ProPlus installed on the same computer. Also, you can't have a volume licensed version of Office 2016 installed on the same computer as the Office 2016 version of Office 365 ProPlus. + + + + +### Visio and Project versions that can be installed on the same computer with Office 365 ProPlus + + +You can't have a volume licensed version of Visio 2016 or Project 2016 installed on the same computer as the Office 2016 version of Office 365 ProPlus. + + + +Also, if there is a 2013 version of Visio Pro for Office 365 or Project Online Desktop Client installed on the computer when you upgrade Office 365 ProPlus to the Office 2016 version, those versions of Visio and Project are removed from the computer. You won't be able to reinstall them after the Office 365 ProPlus installation finishes. However, you can install the 2016 versions of Visio Pro for Office 365 and Project Online Desktop Client on the same computer with the Office 2016 version of Office 365 ProPlus. + + + + +> [!IMPORTANT] +> If you have a volume licensed version of Visio 2016 or Project 2016 installed on the computer, it won't be removed from the computer during the upgrade of Office 365 ProPlus. You can continue to use the volume licensed version of Visio 2016 or Project 2016 on the computer with the Office 2016 version of Office 365 ProPlus. + + + + + +### Removal of InfoPath from Office 365 ProPlus + + + [InfoPath 2013 remains the current version](https://blogs.office.com/2014/01/31/update-on-infopath-and-sharepoint-forms/) and therefore won't be included in the Office 2016 version of Office 365 ProPlus. When you upgrade an existing installation of Office 365 ProPlus to the Office 2016 version, InfoPath is removed from the computer. If your users still need to use InfoPath, the previous version will be available for installation on the **Software** page in the Office 365 portal. + + + + +## Related Topics + + + [What's new: Deploying Office 365 ProPlus in the enterprise](what-s-new-deploying-office-365-proplus-in-the-enterprise.md) + + + + [Project 2016 - Deployment Guide for Admins](https://technet.microsoft.com/library/mt599788%28v=office.16%29.aspx) + + + + [Visio 2016 - Deployment Guide for Admins](https://technet.microsoft.com/library/mt599789%28v=office.16%29.aspx) + + + + [Supported scenarios for installing different versions of Office, Visio, and Project on the same computer](https://technet.microsoft.com/library/mt712177%28v=office.16%29.aspx) + + + + diff --git a/DeployOffice/proofing-tools-for-office-365-proplus.md b/DeployOffice/proofing-tools-for-office-365-proplus.md new file mode 100644 index 000000000..343a6ec5e --- /dev/null +++ b/DeployOffice/proofing-tools-for-office-365-proplus.md @@ -0,0 +1,216 @@ +--- +title: Proofing Tools for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 21c562f2-2e54-452d-8ef5-e39c236bfaf1 +--- + + +# Proofing Tools for Office 365 ProPlus + +Each language version of Office 2016 includes proofing tools for a set of companion languages. For example, when you deploy the English version of Office, users receive proofing tools for English, Spanish, and French. These proofing tools include spelling and grammar checkers, thesauruses, and hyphenators. They might also include language-specific editing features such as Language AutoDetect, AutoSummarize, and Intelligent AutoCorrect. + + + + +If you want to deploy proofing tools in additional languages beyond the companion languages, you can deploy the full language pack for that additional language or you can deploy just the proofing tools in that additional language. Many administrators choose to deploy just the proofing tools to conserve bandwidth on the network and speed up installation on client computers. +## Download proofing tools for Office 2016 + +Download the proofing tools in the languages you want from the [Microsoft Download Center](https://www.microsoft.com/en-us/download/details.aspx?id=52668). There's a separate executable (exe) file for each language. To see the full list of links to the available languages, see [Links to downloads for proofing tools ](proofing-tools-for-office-365-proplus.md#BKMK_LinksToDownloadsForProofingTools) at the end of this article. + + + + +## Deploy proofing tools for Office 2016 to client computers + +After deploying Office 2016 to your client computers, you can deploy proofing tools for additional languages. To do so, you can use the same products and processes you used to deploy Office, such as System Center Configuration Manager or a network installation share. + + + +To install the Proofing Tools on a single computer, you can run the setup.exe directly. To install the Proofing Tools with more controls, you can run the setup.exe from the command line with the following parameters: + + + + + +|**Command**|**Description**| +|:-----|:-----| +| `setup.exe /extract`
|Extracts the contents of the package to the same folder as setup.exe.
| +| `setup.exe /log:[path to log file]`
|Turns on verbose logging and stores it in the specified file. Example: `\\\\server\\log.txt`
| +| `setup.exe /quiet`
|Installs the update without displaying the user interface during the install. The Microsoft Software License Terms are accepted automatically.
| +| `setup.exe /passive`
|Installs the update without requesting any interaction from the user. The Microsoft Software License Terms are accepted automatically.
| + + +## Update proofing tools after installation + +After deploying proofing tools in additional languages, we recommend keeping them updated by enabling Microsoft Update on your client computers or by using your software distribution product, such as System Center Configuration Manager, to distribute updates. + + + + +## Companion proofing languages for Office + +The following table lists companion proofing languages for each primary language in Office 2016. + + + + + +|**Primary language**|**Companion proofing languages**| +|:-----|:-----| +|Arabic
|Arabic, English, French
| +|Brazilian
|Brazilian, English, Spanish
| +|Bulgarian
|Bulgarian, English, German, Russian
| +|Chinese (Simplified)
|Chinese (Simplified), English
| +|Chinese (Traditional)
|Chinese (Traditional), English
| +|Croatian
|Croatian, English, German, Serbian, Italian
| +|Czech
|Czech, English, German, Slovak
| +|Danish
|Danish, English, German, Swedish
| +|Dutch
|Dutch, English, French, German
| +|English
|English, French, Spanish
| +|Estonian
|Estonian, English, German, Russian, Finnish,
| +|Finnish
|Finnish, English, Swedish, German, Russian
| +|French
|French, English, German, Dutch, Arabic, Spanish
| +|German
|German, English, French, Italian
| +|Greek
|Greek, English, French, German
| +|Hebrew
|Hebrew, English, French, Arabic, Russian
| +|Hindi
|Hindi, English, Tamil, Telegu, Marathi, Kannada, Guajarati, Punjabi, Urdu
| +|Hungarian
|Hungarian, English, German
| +|Indonesian
|Indonesian, English
| +|Italian
|Italian, English, French, German
| +|Japanese
|Japanese, English
| +|Kazakh
|Kazakh, English, Russian
| +|Korean
|Korean, English
| +|Latvian
|Latvian, English, German, Russian
| +|Lithuanian
|Lithuanian, English, German, Russian, Polish
| +|Malay
|Malay, English, Chinese (Simplified)
| +|Norwegian (Bk)
|Norwegian (Bk), English, German, Norwegian (Ny)
| +|Polish
|Polish, English, German
| +|Portuguese
|Portuguese, English, French, Spanish
| +|Romanian
|Romanian, English, French
| +|Russian
|Russian, English, Ukrainian, German
| +|Serbian (Latin)
|Serbian (Latin), English, German, French, Croatian
| +|Slovak
|Slovak, English, Czech, Hungarian, German
| +|Slovenian
|Slovenian, English, German, Italian, Croatian
| +|Spanish
|Spanish, English, French, Basque (Basque), Catalan, Galician, Brazilian
| +|Swedish
|Swedish, English, Finnish, German
| +|Thai
|Thai, English, French
| +|Turkish
|Turkish, English, French, German
| +|Ukrainian
|Ukrainian, English, Russian, German
| +|Vietnamese
|Vietnamese, English, French
| + + +## Links to downloads for proofing tools + + +The following table lists the link for the proofing tool download in all available languages and editions. + + + + + +|**Language**|**Culture (ll-cc)**|**Download links**| +|:-----|:-----|:-----| +|Afrikaans
|af-za
| [x86](https://download.microsoft.com/download/3/B/F/3BFB8496-03FF-43AA-B992-CCCA81C222C0/proofingtools2016_af-za-x86.exe), [x64](https://download.microsoft.com/download/3/B/F/3BFB8496-03FF-43AA-B992-CCCA81C222C0/proofingtools2016_af-za-x64.exe)
| +|Albanian
|sq-al
| [x86](https://download.microsoft.com/download/9/F/5/9F50A654-7AB4-417C-BA28-487CCB48D4DD/proofingtools2016_sq-al-x86.exe), [x64](https://download.microsoft.com/download/9/F/5/9F50A654-7AB4-417C-BA28-487CCB48D4DD/proofingtools2016_sq-al-x64.exe)
| +|Arabic
|ar-sa
| [x86](https://download.microsoft.com/download/1/2/2/1229B8D7-1EEC-4DBD-AEBA-AC301AE1B8F8/proofingtools2016_ar-sa-x86.exe), [x64](https://download.microsoft.com/download/1/2/2/1229B8D7-1EEC-4DBD-AEBA-AC301AE1B8F8/proofingtools2016_ar-sa-x64.exe)
| +|Armenian
|hy-am
| [x86](https://download.microsoft.com/download/A/B/A/ABA51FD2-1CD2-4945-8614-6BC1750AEDE1/proofingtools2016_hy-am-x86.exe), [x64](https://download.microsoft.com/download/A/B/A/ABA51FD2-1CD2-4945-8614-6BC1750AEDE1/proofingtools2016_hy-am-x64.exe)
| +|Assamese
|as-in
| [x86](https://download.microsoft.com/download/7/F/C/7FC6FD83-F9CF-4045-938F-FC079C0AD9BC/proofingtools2016_as-in-x86.exe), [x64](https://download.microsoft.com/download/7/F/C/7FC6FD83-F9CF-4045-938F-FC079C0AD9BC/proofingtools2016_as-in-x64.exe)
| +|Azerbaijani (Latin)
|az-Latn-az
| [x86](https://download.microsoft.com/download/7/1/9/719D14CF-8493-4331-AC34-B8BCEE61D2A3/proofingtools2016_az-latn-az-x86.exe), [x64](https://download.microsoft.com/download/7/1/9/719D14CF-8493-4331-AC34-B8BCEE61D2A3/proofingtools2016_az-latn-az-x64.exe)
| +|Bangla (Bangladesh)
|bn-bd
| [x86](https://download.microsoft.com/download/1/E/E/1EEF5DD1-8BDB-4E31-9DD0-ADA4B99DD987/proofingtools2016_bn-bd-x86.exe), [x64](https://download.microsoft.com/download/1/E/E/1EEF5DD1-8BDB-4E31-9DD0-ADA4B99DD987/proofingtools2016_bn-bd-x64.exe)
| +|Bangla (Bengali India)
|bn-in
| [x86](https://download.microsoft.com/download/5/9/E/59E0E372-3393-4F08-8588-30DC933D93B1/proofingtools2016_bn-in-x86.exe), [x64](https://download.microsoft.com/download/5/9/E/59E0E372-3393-4F08-8588-30DC933D93B1/proofingtools2016_bn-in-x64.exe)
| +|Basque (Basque)
|eu-es
| [x86](https://download.microsoft.com/download/4/5/C/45C79C95-DF53-4426-B14C-BC4BB575078B/proofingtools2016_eu-es-x86.exe), [x64](https://download.microsoft.com/download/4/5/C/45C79C95-DF53-4426-B14C-BC4BB575078B/proofingtools2016_eu-es-x64.exe)
| +|Bosnian (Latin)
|bs-Latn-ba or bs-BA
| [x86](https://download.microsoft.com/download/1/A/7/1A796609-5733-4AD7-8BE4-41634D2011E1/proofingtools2016_bs-latn-ba-x86.exe), [x64](https://download.microsoft.com/download/1/A/7/1A796609-5733-4AD7-8BE4-41634D2011E1/proofingtools2016_bs-latn-ba-x64.exe)
| +|Bulgarian
|bg-bg
| [x86](https://download.microsoft.com/download/2/E/8/2E85747E-6EBF-400E-AE06-B8840CF3EFEE/proofingtools2016_bg-bg-x86.exe), [x64](https://download.microsoft.com/download/2/E/8/2E85747E-6EBF-400E-AE06-B8840CF3EFEE/proofingtools2016_bg-bg-x64.exe)
| +|Catalan
|ca-es
| [x86](https://download.microsoft.com/download/8/B/6/8B6577C3-81B3-41F1-85FB-CF608D18C089/proofingtools2016_ca-es-x86.exe), [x64](https://download.microsoft.com/download/8/B/6/8B6577C3-81B3-41F1-85FB-CF608D18C089/proofingtools2016_ca-es-x64.exe)
| +|Chinese (Simplified)
|zh-cn
| [x86](https://download.microsoft.com/download/4/C/0/4C0B7037-2E7F-4024-8BEC-4F151A910923/proofingtools2016_zh-cn-x86.exe), [x64](https://download.microsoft.com/download/4/C/0/4C0B7037-2E7F-4024-8BEC-4F151A910923/proofingtools2016_zh-cn-x64.exe)
| +|Chinese (Traditional)
|zh-tw
| [x86](https://download.microsoft.com/download/9/5/3/953B4F05-F95E-4E6F-A650-10B6527493E8/proofingtools2016_zh-tw-x86.exe), [x64](https://download.microsoft.com/download/9/5/3/953B4F05-F95E-4E6F-A650-10B6527493E8/proofingtools2016_zh-tw-x64.exe)
| +|Croatian
|hr-hr
| [x86](https://download.microsoft.com/download/0/5/7/05798269-56BE-482A-ACB6-05024501F165/proofingtools2016_hr-hr-x86.exe), [x64](https://download.microsoft.com/download/0/5/7/05798269-56BE-482A-ACB6-05024501F165/proofingtools2016_hr-hr-x64.exe)
| +|Czech
|cs-cz
| [x86](https://download.microsoft.com/download/1/4/0/1406C260-59F7-4CE9-96B0-CFBC418FA09F/proofingtools2016_cs-cz-x86.exe), [x64](https://download.microsoft.com/download/1/4/0/1406C260-59F7-4CE9-96B0-CFBC418FA09F/proofingtools2016_cs-cz-x64.exe)
| +|Danish
|da-dk
| [x86](https://download.microsoft.com/download/F/C/8/FC841CB4-B84E-47DE-A454-6B45894BCFFC/proofingtools2016_da-dk-x86.exe), [x64](https://download.microsoft.com/download/F/C/8/FC841CB4-B84E-47DE-A454-6B45894BCFFC/proofingtools2016_da-dk-x64.exe)
| +|Dutch
|nl-nl
| [x86](https://download.microsoft.com/download/B/B/0/BB0D89B0-F109-4233-8822-E059EDDC1D0B/proofingtools2016_nl-nl-x86.exe), [x64](https://download.microsoft.com/download/B/B/0/BB0D89B0-F109-4233-8822-E059EDDC1D0B/proofingtools2016_nl-nl-x64.exe)
| +|English
|en-us
| [x86](https://download.microsoft.com/download/9/5/A/95A40083-4ADA-4173-BE42-0C9F88AD8C0F/proofingtools2016_en-us-x86.exe), [x64](https://download.microsoft.com/download/9/5/A/95A40083-4ADA-4173-BE42-0C9F88AD8C0F/proofingtools2016_en-us-x64.exe)
| +|Estonian
|et-ee
| [x86](https://download.microsoft.com/download/7/C/B/7CB8D19E-07C9-4783-9E7B-62CAB2D2E7B4/proofingtools2016_et-ee-x86.exe), [x64](https://download.microsoft.com/download/7/C/B/7CB8D19E-07C9-4783-9E7B-62CAB2D2E7B4/proofingtools2016_et-ee-x64.exe)
| +|Finnish
|fi-fi
| [x86](https://download.microsoft.com/download/7/E/F/7EF2DBF6-3DCE-422A-B310-9EBE11F1EFBE/proofingtools2016_fi-fi-x86.exe), [x64](https://download.microsoft.com/download/7/E/F/7EF2DBF6-3DCE-422A-B310-9EBE11F1EFBE/proofingtools2016_fi-fi-x64.exe)
| +|French
|fr-fr
| [x86](https://download.microsoft.com/download/6/F/B/6FB241AB-E2C5-4668-AB0B-98628915EC3B/proofingtools2016_fr-fr-x86.exe), [x64](https://download.microsoft.com/download/6/F/B/6FB241AB-E2C5-4668-AB0B-98628915EC3B/proofingtools2016_fr-fr-x64.exe)
| +|Galician
|gl-es
| [x86](https://download.microsoft.com/download/5/A/A/5AAD14B7-65CE-40EB-9EEC-95526BEE393B/proofingtools2016_gl-es-x86.exe), [x64](https://download.microsoft.com/download/5/A/A/5AAD14B7-65CE-40EB-9EEC-95526BEE393B/proofingtools2016_gl-es-x64.exe)
| +|Georgian
|ka-ge
| [x86](https://download.microsoft.com/download/F/4/3/F4378696-38E3-4218-BBDB-03E801862B5A/proofingtools2016_ka-ge-x86.exe), [x64](https://download.microsoft.com/download/F/4/3/F4378696-38E3-4218-BBDB-03E801862B5A/proofingtools2016_ka-ge-x64.exe)
| +|German
|de-de
| [x86](https://download.microsoft.com/download/6/B/0/6B062E3D-412B-4E21-AF4D-1FA1E4610C57/proofingtools2016_de-de-x86.exe), [x64](https://download.microsoft.com/download/6/B/0/6B062E3D-412B-4E21-AF4D-1FA1E4610C57/proofingtools2016_de-de-x64.exe)
| +|Greek
|el-gr
| [x86](https://download.microsoft.com/download/E/5/6/E5640562-A233-4143-AE45-E74DD323CBA9/proofingtools2016_el-gr-x86.exe), [x64](https://download.microsoft.com/download/E/5/6/E5640562-A233-4143-AE45-E74DD323CBA9/proofingtools2016_el-gr-x64.exe)
| +|Gujarati
|gu-in
| [x86](https://download.microsoft.com/download/A/1/1/A11FAA12-F877-4D92-8325-0FA319F0B35A/proofingtools2016_gu-in-x86.exe), [x64](https://download.microsoft.com/download/A/1/1/A11FAA12-F877-4D92-8325-0FA319F0B35A/proofingtools2016_gu-in-x64.exe)
| +|Hausa
|ha-Latn-ng
| [x86](https://download.microsoft.com/download/3/7/1/37136A5F-005F-4788-B5BC-ED8FD6A1591F/proofingtools2016_ha-latn-ng-x86.exe), [x64](https://download.microsoft.com/download/3/7/1/37136A5F-005F-4788-B5BC-ED8FD6A1591F/proofingtools2016_ha-latn-ng-x64.exe)
| +|Hebrew
|he-il
| [x86](https://download.microsoft.com/download/C/F/3/CF33E691-22E5-4E02-9093-A995F6CF577C/proofingtools2016_he-il-x86.exe), [x64](https://download.microsoft.com/download/C/F/3/CF33E691-22E5-4E02-9093-A995F6CF577C/proofingtools2016_he-il-x64.exe)
| +|Hindi
|hi-in
| [x86](https://download.microsoft.com/download/7/7/9/7795F624-CC70-478B-8078-8130784715C9/proofingtools2016_hi-in-x86.exe), [x64](https://download.microsoft.com/download/7/7/9/7795F624-CC70-478B-8078-8130784715C9/proofingtools2016_hi-in-x64.exe)
| +|Hungarian
|hu-hu
| [x86](https://download.microsoft.com/download/3/4/4/34482994-23A9-40F1-8597-BE5FE88A0DFF/proofingtools2016_hu-hu-x86.exe), [x64](https://download.microsoft.com/download/3/4/4/34482994-23A9-40F1-8597-BE5FE88A0DFF/proofingtools2016_hu-hu-x64.exe)
| +|Icelandic
|is-is
| [x86](https://download.microsoft.com/download/2/A/D/2AD16E2A-C36B-4615-A066-F8D4B85F888D/proofingtools2016_is-is-x86.exe), [x64](https://download.microsoft.com/download/2/A/D/2AD16E2A-C36B-4615-A066-F8D4B85F888D/proofingtools2016_is-is-x64.exe)
| +|Igbo
|ig-ng
| [x86](https://download.microsoft.com/download/9/1/A/91AF892D-A2C4-455E-B44C-7A62B73F7E31/proofingtools2016_ig-ng-x86.exe), [x64](https://download.microsoft.com/download/9/1/A/91AF892D-A2C4-455E-B44C-7A62B73F7E31/proofingtools2016_ig-ng-x64.exe)
| +|Indonesian
|id-id
| [x86](https://download.microsoft.com/download/2/F/F/2FFDFCE6-8714-4084-8645-C196E2502EAB/proofingtools2016_id-id-x86.exe), [x64](https://download.microsoft.com/download/2/F/F/2FFDFCE6-8714-4084-8645-C196E2502EAB/proofingtools2016_id-id-x64.exe)
| +|Irish
|ga-ie
| [x86](https://download.microsoft.com/download/5/F/C/5FC510CF-1F1A-4233-AE4A-40FFC72B8539/proofingtools2016_ga-ie-x86.exe), [x64](https://download.microsoft.com/download/5/F/C/5FC510CF-1F1A-4233-AE4A-40FFC72B8539/proofingtools2016_ga-ie-x64.exe)
| +|isiXhosa
|xh-za
| [x86](https://download.microsoft.com/download/8/F/8/8F835563-F26D-4FDE-842B-5EE2497B7E91/proofingtools2016_xh-za-x86.exe), [x64](https://download.microsoft.com/download/8/F/8/8F835563-F26D-4FDE-842B-5EE2497B7E91/proofingtools2016_xh-za-x64.exe)
| +|isiZulu
|zu-za
| [x86](https://download.microsoft.com/download/9/8/1/981E5779-8A34-4443-922D-372DC7DDAD4F/proofingtools2016_zu-za-x86.exe), [x64](https://download.microsoft.com/download/9/8/1/981E5779-8A34-4443-922D-372DC7DDAD4F/proofingtools2016_zu-za-x64.exe)
| +|Italian
|it-it
| [x86](https://download.microsoft.com/download/B/6/F/B6F3A0E0-8540-4EC7-A97F-50EA1C47EDFC/proofingtools2016_it-it-x86.exe), [x64](https://download.microsoft.com/download/B/6/F/B6F3A0E0-8540-4EC7-A97F-50EA1C47EDFC/proofingtools2016_it-it-x64.exe)
| +|Japanese
|ja-jp
| [x86](https://download.microsoft.com/download/7/4/5/745809A6-D0B4-4FCC-B1D4-E75570695C39/proofingtools2016_ja-jp-x86.exe), [x64](https://download.microsoft.com/download/7/4/5/745809A6-D0B4-4FCC-B1D4-E75570695C39/proofingtools2016_ja-jp-x64.exe)
| +|Kannada
|kn-in
| [x86](https://download.microsoft.com/download/1/8/3/183DC332-CD83-4911-919C-EF29C3E327DC/proofingtools2016_kn-in-x86.exe), [x64](https://download.microsoft.com/download/1/8/3/183DC332-CD83-4911-919C-EF29C3E327DC/proofingtools2016_kn-in-x64.exe)
| +|Kazakh
|kk-kz
| [x86](https://download.microsoft.com/download/A/F/2/AF2AA7EC-EA6B-4355-BB2C-BA6B028CB009/proofingtools2016_kk-kz-x86.exe), [x64](https://download.microsoft.com/download/A/F/2/AF2AA7EC-EA6B-4355-BB2C-BA6B028CB009/proofingtools2016_kk-kz-x64.exe)
| +|Kinyarwanda
|rw-rw
| [x86](https://download.microsoft.com/download/4/C/4/4C41C36B-BA0D-4F51-96AD-71B184342506/proofingtools2016_rw-rw-x86.exe), [x64](https://download.microsoft.com/download/4/C/4/4C41C36B-BA0D-4F51-96AD-71B184342506/proofingtools2016_rw-rw-x64.exe)
| +|KiSwahili
|sw-ke
| [x86](https://download.microsoft.com/download/F/C/D/FCD45769-5148-4128-924F-762E8E3DEBBD/proofingtools2016_sw-ke-x86.exe), [x64](https://download.microsoft.com/download/F/C/D/FCD45769-5148-4128-924F-762E8E3DEBBD/proofingtools2016_sw-ke-x64.exe)
| +|Konkani
|kok-in
| [x86](https://download.microsoft.com/download/4/7/1/471635C7-1B63-4F3A-A0A6-8A6F34C995F6/proofingtools2016_kok-in-x86.exe), [x64](https://download.microsoft.com/download/4/7/1/471635C7-1B63-4F3A-A0A6-8A6F34C995F6/proofingtools2016_kok-in-x64.exe)
| +|Korean
|ko-kr
| [x86](https://download.microsoft.com/download/4/6/C/46CF642E-CD03-4B05-8121-2515D64B5F95/proofingtools2016_ko-kr-x86.exe), [x64](https://download.microsoft.com/download/4/6/C/46CF642E-CD03-4B05-8121-2515D64B5F95/proofingtools2016_ko-kr-x64.exe)
| +|Kyrgyz
|ky-kg
| [x86](https://download.microsoft.com/download/4/4/D/44D5B1F7-2BC1-4A04-A147-EF9E790DCB31/proofingtools2016_ky-kg-x86.exe), [x64](https://download.microsoft.com/download/4/4/D/44D5B1F7-2BC1-4A04-A147-EF9E790DCB31/proofingtools2016_ky-kg-x64.exe)
| +|Latvian
|lv-lv
| [x86](https://download.microsoft.com/download/5/3/4/534BC983-4588-4EBB-A035-BE834F6635C5/proofingtools2016_lv-lv-x86.exe), [x64](https://download.microsoft.com/download/5/3/4/534BC983-4588-4EBB-A035-BE834F6635C5/proofingtools2016_lv-lv-x64.exe)
| +|Lithuanian
|lt-lt
| [x86](https://download.microsoft.com/download/6/D/D/6DD6269A-CFC6-461B-B3AA-61530A12FF50/proofingtools2016_lt-lt-x86.exe), [x64](https://download.microsoft.com/download/6/D/D/6DD6269A-CFC6-461B-B3AA-61530A12FF50/proofingtools2016_lt-lt-x64.exe)
| +|Luxembourgish
|lb-lu
| [x86](https://download.microsoft.com/download/3/B/4/3B4A5DD5-C55C-4B3B-BC17-FA83E2E739D8/proofingtools2016_lb-lu-x86.exe), [x64](https://download.microsoft.com/download/3/B/4/3B4A5DD5-C55C-4B3B-BC17-FA83E2E739D8/proofingtools2016_lb-lu-x64.exe)
| +|Macedonian (FYRO Macedonia )
|mk-mk
| [x86](https://download.microsoft.com/download/4/1/D/41D0EFD1-B02F-48D4-8B7F-9AAB8218D630/proofingtools2016_mk-mk-x86.exe), [x64](https://download.microsoft.com/download/4/1/D/41D0EFD1-B02F-48D4-8B7F-9AAB8218D630/proofingtools2016_mk-mk-x64.exe)
| +|Malay (Latin)
|ms-my
| [x86](https://download.microsoft.com/download/F/C/8/FC81EC17-F044-4F00-B51B-B1F782855967/proofingtools2016_ms-my-x86.exe), [x64](https://download.microsoft.com/download/F/C/8/FC81EC17-F044-4F00-B51B-B1F782855967/proofingtools2016_ms-my-x64.exe)
| +|Malayalam
|ml-in
| [x86](https://download.microsoft.com/download/5/7/6/576F35DF-DE8C-432D-A410-B08FD076157D/proofingtools2016_ml-in-x86.exe), [x64](https://download.microsoft.com/download/5/7/6/576F35DF-DE8C-432D-A410-B08FD076157D/proofingtools2016_ml-in-x64.exe)
| +|Maltese
|mt-mt
| [x86](https://download.microsoft.com/download/8/5/A/85ABC7BE-921A-4480-BA3D-2C51BCB25972/proofingtools2016_mt-mt-x86.exe), [x64](https://download.microsoft.com/download/8/5/A/85ABC7BE-921A-4480-BA3D-2C51BCB25972/proofingtools2016_mt-mt-x64.exe)
| +|Maori
|mi-nz
| [x86](https://download.microsoft.com/download/0/0/4/00493C0C-2CE0-4F98-A048-23FE0ED788B4/proofingtools2016_mi-nz-x86.exe), [x64](https://download.microsoft.com/download/0/0/4/00493C0C-2CE0-4F98-A048-23FE0ED788B4/proofingtools2016_mi-nz-x64.exe)
| +|Marathi
|mr-in
| [x86](https://download.microsoft.com/download/9/6/C/96CA4369-C827-4E8F-92A7-9376780415E5/proofingtools2016_mr-in-x86.exe), [x64](https://download.microsoft.com/download/9/6/C/96CA4369-C827-4E8F-92A7-9376780415E5/proofingtools2016_mr-in-x64.exe)
| +|Nepali
|ne-np
| [x86](https://download.microsoft.com/download/7/2/A/72A53473-9DC4-40FF-A417-01FD4BB88861/proofingtools2016_ne-np-x86.exe), [x64](https://download.microsoft.com/download/7/2/A/72A53473-9DC4-40FF-A417-01FD4BB88861/proofingtools2016_ne-np-x64.exe)
| +|Norwegian Bokmål
|nb-no
| [x86](https://download.microsoft.com/download/8/C/7/8C75568F-CD19-4D9A-A231-93F00D8BD5C6/proofingtools2016_nb-no-x86.exe), [x64](https://download.microsoft.com/download/8/C/7/8C75568F-CD19-4D9A-A231-93F00D8BD5C6/proofingtools2016_nb-no-x64.exe)
| +|Norwegian Nynorsk
|nn-no
| [x86](https://download.microsoft.com/download/5/4/2/542A4BE5-8FC2-4624-969D-0D7E18D33539/proofingtools2016_nn-no-x86.exe), [x64](https://download.microsoft.com/download/5/4/2/542A4BE5-8FC2-4624-969D-0D7E18D33539/proofingtools2016_nn-no-x64.exe)
| +|Odia
|or-in
| [x86](https://download.microsoft.com/download/C/8/9/C89DCC82-5F9B-47A8-A756-35A06045DD0D/proofingtools2016_or-in-x86.exe), [x64](https://download.microsoft.com/download/C/8/9/C89DCC82-5F9B-47A8-A756-35A06045DD0D/proofingtools2016_or-in-x64.exe)
| +|Pashto
|ps-af
| [x86](https://download.microsoft.com/download/C/9/B/C9B8C543-4D08-4AD3-8348-B8D6CC3B9C2C/proofingtools2016_ps-af-x86.exe), [x64](https://download.microsoft.com/download/C/9/B/C9B8C543-4D08-4AD3-8348-B8D6CC3B9C2C/proofingtools2016_ps-af-x64.exe)
| +|Persian (Farsi)
|fa-ir
| [x86](https://download.microsoft.com/download/E/C/F/ECF7490C-1879-4412-9668-CEECCD892E9E/proofingtools2016_fa-ir-x86.exe), [x64](https://download.microsoft.com/download/E/C/F/ECF7490C-1879-4412-9668-CEECCD892E9E/proofingtools2016_fa-ir-x64.exe)
| +|Polish
|pl-pl
| [x86](https://download.microsoft.com/download/7/1/E/71EC2141-4781-4766-841C-6C5DF3085F4C/proofingtools2016_pl-pl-x86.exe), [x64](https://download.microsoft.com/download/7/1/E/71EC2141-4781-4766-841C-6C5DF3085F4C/proofingtools2016_pl-pl-x64.exe)
| +|Portuguese (Portugal)
|pt-pt
| [x86](https://download.microsoft.com/download/1/2/B/12B2F314-C901-4947-A005-6CA1CCD317DD/proofingtools2016_pt-pt-x86.exe), [x64](https://download.microsoft.com/download/1/2/B/12B2F314-C901-4947-A005-6CA1CCD317DD/proofingtools2016_pt-pt-x64.exe)
| +|Portuguese (Brazil)
|pt-br
| [x86](https://download.microsoft.com/download/C/9/6/C96FF7FE-2B8B-4D55-BFAF-A3497F70EAB3/proofingtools2016_pt-br-x86.exe), [x64](https://download.microsoft.com/download/C/9/6/C96FF7FE-2B8B-4D55-BFAF-A3497F70EAB3/proofingtools2016_pt-br-x64.exe)
| +|Punjabi (Gurmukhi)
|pa-in
| [x86](https://download.microsoft.com/download/E/C/D/ECDE79C2-46A0-44A2-A6DD-D8F2AD7298B1/proofingtools2016_pa-in-x86.exe), [x64](https://download.microsoft.com/download/E/C/D/ECDE79C2-46A0-44A2-A6DD-D8F2AD7298B1/proofingtools2016_pa-in-x64.exe)
| +|Romanian
|ro-ro
| [x86](https://download.microsoft.com/download/9/F/9/9F911231-FC5B-4046-8A27-6A6F20B59E94/proofingtools2016_ro-ro-x86.exe), [x64](https://download.microsoft.com/download/9/F/9/9F911231-FC5B-4046-8A27-6A6F20B59E94/proofingtools2016_ro-ro-x64.exe)
| +|Romansh
|rm-ch
| [x86](https://download.microsoft.com/download/9/F/0/9F083CEA-E12A-4E11-8973-8436FFD78653/proofingtools2016_rm-ch-x86.exe), [x64](https://download.microsoft.com/download/9/F/0/9F083CEA-E12A-4E11-8973-8436FFD78653/proofingtools2016_rm-ch-x64.exe)
| +|Russian
|ru-ru
| [x86](https://download.microsoft.com/download/A/1/D/A1D0C574-D661-4FA7-9ED7-386A222F786B/proofingtools2016_ru-ru-x86.exe), [x64](https://download.microsoft.com/download/A/1/D/A1D0C574-D661-4FA7-9ED7-386A222F786B/proofingtools2016_ru-ru-x64.exe)
| +|Scottish Gaelic
|gd-gb
| [x86](https://download.microsoft.com/download/4/7/9/4793661A-506A-4B40-8874-701FC77F9A96/proofingtools2016_gd-gb-x86.exe), [x64](https://download.microsoft.com/download/4/7/9/4793661A-506A-4B40-8874-701FC77F9A96/proofingtools2016_gd-gb-x64.exe)
| +|Serbian (Cyrillic, Serbia)
|sr-cyrl-rs
| [x86](https://download.microsoft.com/download/9/E/7/9E71790F-C8D5-4914-A7D4-2957364D5B80/proofingtools2016_sr-cyrl-rs-x86.exe), [x64](https://download.microsoft.com/download/9/E/7/9E71790F-C8D5-4914-A7D4-2957364D5B80/proofingtools2016_sr-cyrl-rs-x64.exe)
| +|Serbian (Latin, Serbia)
|sr-latn-rs
| [x86](https://download.microsoft.com/download/5/F/0/5F09A211-6C6A-4A32-88AE-1C0E2E5218E3/proofingtools2016_sr-latn-rs-x86.exe), [x64](https://download.microsoft.com/download/5/F/0/5F09A211-6C6A-4A32-88AE-1C0E2E5218E3/proofingtools2016_sr-latn-rs-x64.exe)
| +|Serbian (Cyrillic, Bosnia & Herzegovina)
|sr-cyrl-ba
| [x86](https://download.microsoft.com/download/4/3/F/43FA0DE8-3F95-4914-9B4C-4A169D9E3C69/proofingtools2016_sr-cyrl-ba-x86.exe), [x64](https://download.microsoft.com/download/4/3/F/43FA0DE8-3F95-4914-9B4C-4A169D9E3C69/proofingtools2016_sr-cyrl-ba-x64.exe)
| +|Sesotho sa Leboa
|nso-za
| [x86](https://download.microsoft.com/download/6/D/2/6D2AFAE0-58EA-483F-A7C4-7961D0B05C5F/proofingtools2016_nso-za-x86.exe), [x64](https://download.microsoft.com/download/6/D/2/6D2AFAE0-58EA-483F-A7C4-7961D0B05C5F/proofingtools2016_nso-za-x64.exe)
| +|Setswana
|tn-za
| [x86](https://download.microsoft.com/download/4/3/D/43D0FA88-7047-4A2B-B375-39FB819F89D1/proofingtools2016_tn-za-x86.exe), [x64](https://download.microsoft.com/download/4/3/D/43D0FA88-7047-4A2B-B375-39FB819F89D1/proofingtools2016_tn-za-x64.exe)
| +|Sinhala
|si-lk
| [x86](https://download.microsoft.com/download/A/E/E/AEEDC357-2CB3-4175-8F20-2BCFEC6BD395/proofingtools2016_si-lk-x86.exe), [x64](https://download.microsoft.com/download/A/E/E/AEEDC357-2CB3-4175-8F20-2BCFEC6BD395/proofingtools2016_si-lk-x64.exe)
| +|Slovak
|sk-sk
| [x86](https://download.microsoft.com/download/3/6/0/36015517-7814-4340-B20C-D3B180574F8D/proofingtools2016_sk-sk-x86.exe), [x64](https://download.microsoft.com/download/3/6/0/36015517-7814-4340-B20C-D3B180574F8D/proofingtools2016_sk-sk-x64.exe)
| +|Slovenian
|sl-si
| [x86](https://download.microsoft.com/download/A/E/D/AEDBA997-46B4-4BBE-91F1-96F607BEBA47/proofingtools2016_sl-si-x86.exe), [x64](https://download.microsoft.com/download/A/E/D/AEDBA997-46B4-4BBE-91F1-96F607BEBA47/proofingtools2016_sl-si-x64.exe)
| +|Spanish
|es-es
| [x86](https://download.microsoft.com/download/2/2/C/22C8AD6A-6D87-4C89-9905-53F325CAD071/proofingtools2016_es-es-x86.exe), [x64](https://download.microsoft.com/download/2/2/C/22C8AD6A-6D87-4C89-9905-53F325CAD071/proofingtools2016_es-es-x64.exe)
| +|Swedish
|sv-se
| [x86](https://download.microsoft.com/download/9/5/5/955DB0B4-0DBF-4924-A636-4B42801F1379/proofingtools2016_sv-se-x86.exe), [x64](https://download.microsoft.com/download/9/5/5/955DB0B4-0DBF-4924-A636-4B42801F1379/proofingtools2016_sv-se-x64.exe)
| +|Tamil
|ta-in
| [x86](https://download.microsoft.com/download/6/D/2/6D25FBE2-D82A-4A80-96B9-0226C39055F4/proofingtools2016_ta-in-x86.exe), [x64](https://download.microsoft.com/download/6/D/2/6D25FBE2-D82A-4A80-96B9-0226C39055F4/proofingtools2016_ta-in-x64.exe)
| +|Tatar (Cyrillic)
|tt-ru
| [x86](https://download.microsoft.com/download/B/B/7/BB783B34-2CD6-40CC-8160-2EFBB34A6054/proofingtools2016_tt-ru-x86.exe), [x64](https://download.microsoft.com/download/B/B/7/BB783B34-2CD6-40CC-8160-2EFBB34A6054/proofingtools2016_tt-ru-x64.exe)
| +|Telugu
|te-in
| [x86](https://download.microsoft.com/download/B/4/3/B4301105-7D4F-402D-AB82-AD4283E2A5AD/proofingtools2016_te-in-x86.exe), [x64](https://download.microsoft.com/download/B/4/3/B4301105-7D4F-402D-AB82-AD4283E2A5AD/proofingtools2016_te-in-x64.exe)
| +|Thai
|th-th
| [x86](https://download.microsoft.com/download/E/2/8/E28F8C68-40D5-440E-8557-611D56134A2E/proofingtools2016_th-th-x86.exe), [x64](https://download.microsoft.com/download/E/2/8/E28F8C68-40D5-440E-8557-611D56134A2E/proofingtools2016_th-th-x64.exe)
| +|Turkish
|tr-tr
| [x86](https://download.microsoft.com/download/8/4/A/84A17221-5466-4CE9-96B2-B8B78548668E/proofingtools2016_tr-tr-x86.exe), [x64](https://download.microsoft.com/download/8/4/A/84A17221-5466-4CE9-96B2-B8B78548668E/proofingtools2016_tr-tr-x64.exe)
| +|Ukrainian
|uk-ua
| [x86](https://download.microsoft.com/download/A/7/8/A7870796-B1B2-4162-A98E-AC8898985AD4/proofingtools2016_uk-ua-x86.exe), [x64](https://download.microsoft.com/download/A/7/8/A7870796-B1B2-4162-A98E-AC8898985AD4/proofingtools2016_uk-ua-x64.exe)
| +|Urdu
|ur-pk
| [x86](https://download.microsoft.com/download/9/E/4/9E4544E3-9530-45AE-B16F-3B912870D622/proofingtools2016_ur-pk-x86.exe), [x64](https://download.microsoft.com/download/9/E/4/9E4544E3-9530-45AE-B16F-3B912870D622/proofingtools2016_ur-pk-x64.exe)
| +|Uzbek (Latin)
|uz-Latn-uz
| [x86](https://download.microsoft.com/download/E/E/3/EE30D59A-1682-4D64-8A10-77612BC72034/proofingtools2016_uz-latn-uz-x86.exe), [x64](https://download.microsoft.com/download/E/E/3/EE30D59A-1682-4D64-8A10-77612BC72034/proofingtools2016_uz-latn-uz-x64.exe)
| +|Vietnamese
|vi-vn
| [x86](https://download.microsoft.com/download/B/7/F/B7F58237-9A45-4AFE-BD73-F8C52A555A17/proofingtools2016_vi-vn-x86.exe), [x64](https://download.microsoft.com/download/B/7/F/B7F58237-9A45-4AFE-BD73-F8C52A555A17/proofingtools2016_vi-vn-x64.exe)
| +|Welsh
|cy-gb
| [x86](https://download.microsoft.com/download/9/B/B/9BB9E4CF-B639-4C9A-964C-2C1579CB9959/proofingtools2016_cy-gb-x86.exe), [x64](https://download.microsoft.com/download/9/B/B/9BB9E4CF-B639-4C9A-964C-2C1579CB9959/proofingtools2016_cy-gb-x64.exe)
| +|Wolof
|wo-sn
| [x86](https://download.microsoft.com/download/C/9/3/C93F4B91-2897-4B0D-B84F-1A39692746E8/proofingtools2016_wo-sn-x86.exe), [x64](https://download.microsoft.com/download/C/9/3/C93F4B91-2897-4B0D-B84F-1A39692746E8/proofingtools2016_wo-sn-x64.exe)
| +|Yoruba
|yo-ng
| [x86](https://download.microsoft.com/download/1/D/B/1DBAEB2B-7648-47A5-8F26-7B9F9814E959/proofingtools2016_yo-ng-x86.exe), [x64](https://download.microsoft.com/download/1/D/B/1DBAEB2B-7648-47A5-8F26-7B9F9814E959/proofingtools2016_yo-ng-x64.exe)
| + + +## See also + + + +#### Other Resources + + + + + + [Plan for multilanguage deployment of Click-to-Run-based Office installations](http://technet.microsoft.com/library/a972905d-3f7b-47c1-8481-9a5ac6876283.aspx) diff --git a/DeployOffice/reference-articles-for-deploying-office-365-proplus.md b/DeployOffice/reference-articles-for-deploying-office-365-proplus.md new file mode 100644 index 000000000..0520a173e --- /dev/null +++ b/DeployOffice/reference-articles-for-deploying-office-365-proplus.md @@ -0,0 +1,25 @@ +--- +title: Reference articles for deploying Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 6df5de04-6b8e-48af-aede-dceaefacc278 +--- + + +# Reference articles for deploying Office 365 ProPlus + +This article lists all the reference articles about deploying Office 365 ProPlus in an enterprise environment. To see all the articles about Office 365 ProPlus deployment, see [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md). + + + + + ** [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md)** How to use the Office 2016 Deployment Tool to download, install, and update Office 365 ProPlus. ** [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md)** Detailed information on the configuration options for the Office Deployment Tool. ** [Overview of shared computer activation for Office 365 ProPlus](overview-of-shared-computer-activation-for-office-365-proplus.md)** What shared computer activation is and how it's used for Office 365 ProPlus deployments in which users access a shared computer. ** [End-user update notifications for Office 365 ProPlus](end-user-update-notifications-for-office-365-proplus.md)** What notifications your users see when updates for Office 365 ProPlus are available or must be applied. ** [Deploy Office 365 ProPlus as part of an operating system image](deploy-office-365-proplus-as-part-of-an-operating-system-image.md)** How to deploy Office 365 ProPlus as part of an operating system image with the Office 2016 Deployment Tool. ** [Deploy Office 365 ProPlus by using Remote Desktop Services](deploy-office-365-proplus-by-using-remote-desktop-services.md)** How to deploy Office 365 ProPlus to a shared computer by using Remote Desktop Services (RDS). ** [Proofing Tools for Office 365 ProPlus](proofing-tools-for-office-365-proplus.md)** How to download and deploy Proofing Tools in additional languages for Office 365 ProPlus. ** [Overview of licensing and activation in Office 365 ProPlus](overview-of-licensing-and-activation-in-office-365-proplus.md)** How to assign Office 365 ProPlus licenses to users and how individual installations are activated. ** [Licensing and activation data sent to Office 365 by Office 365 ProPlus](licensing-and-activation-data-sent-to-office-365-by-office-365-proplus.md)** What data Office 365 ProPlus sends to Office 365 services for licensing and activation purposes. +## See also + + +#### Other Resources + + + + + + [Deployment guide for Office 365 ProPlus](deployment-guide-for-office-365-proplus.md) diff --git a/DeployOffice/troubleshoot-issues-with-shared-computer-activation-for-office-365-proplus.md b/DeployOffice/troubleshoot-issues-with-shared-computer-activation-for-office-365-proplus.md new file mode 100644 index 000000000..75d638f01 --- /dev/null +++ b/DeployOffice/troubleshoot-issues-with-shared-computer-activation-for-office-365-proplus.md @@ -0,0 +1,222 @@ +--- +title: Troubleshoot issues with shared computer activation for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: c3aeb487-d45f-4079-8c35-7558a45b876c +--- + + +# Troubleshoot issues with shared computer activation for Office 365 ProPlus + + **Summary:** Explains how to troubleshoot issues with deployments of Office 365 ProPlus that are configured to use shared configured activation. + + + + +If you're having problems getting shared computer activation to work when you deploy Office 365 ProPlus to shared computers in your organization, try the following to fix the problem. +## Check that your Office 365 plan supports shared computer activation + + +To use shared computer activation, you must have an [Office 365 plan](https://go.microsoft.com/fwlink/p/?LinkId=510587) that includes Office 365 ProPlus. + + + + +> [!NOTE] +> You also can use shared computer activation with Visio Pro for Office 365 or Project Online Desktop Client. You just need a subscription plan that includes those products. + + + + + +## Verify that shared computer activation is enabled for Office 365 ProPlus + + +Here are two ways that you can check whether shared computer activation is enabled on the computer that has Office 365 ProPlus installed. + + + + +- Open any Office 365 ProPlus program, such as Word. Go to **File** > **Account** > **About Word** (or whatever the name of the app is). On the second line from the top, underneath the MSO version number, you should see **Shared Computer Activation**, instead of a Product ID. + + +- Use Registry Editor, and go to **HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Office\\ClickToRun\\Configuration**. There should be a value for SharedComputerLicensing with a setting of 1. + + + +## Verify that activation for Office 365 ProPlus succeeded + + +On the shared computer, after you open any Office 365 ProPlus program, go to the following folder: + + + + %localappdata%\\Microsoft\\Office\\16.0\\Licensing + + + +If activation succeeded, there are some text files in the folder. Don't make any changes to these files. + + + + +## Review error messages for shared computer activation + + +If you're having problems using shared computer activation, you might get one of the following error messages. + + + + +### The products we found in your account cannot be used to activate Office in shared computer scenarios. + + +This error means that you don't have an [Office 365 plan](https://go.microsoft.com/fwlink/p/?LinkId=510587) that includes Office 365 ProPlus. Therefore, you can't use shared computer activation. + + + + + + + +![Error message cannot activate products into shared scenario](images/67637fc5-35cc-4118-acc1-e68fe1155512.png) + + + + + + + + + + + + +### UNLICENSED PRODUCT Most features are turned off because a shared computer license isn't available. + + +This error means that a licensing token wasn't obtained from the Office Licensing Service on the Internet. Office 365 ProPlus is now in reduced functionality mode. The user can view and print Office 365 ProPlus documents, but can't create or edit documents. + + + +You can try these steps to fix this problem: + + + + +- [Assign or remove licenses for Office 365 for business](http://technet.microsoft.com/library/997596b5-4173-4627-b915-36abac6786dc%28Office.14%29.aspx) for Office 365 ProPlus. + + +- Check that the user signs in with her user account for Office 365 if the **Activate Office** dialog box appears when the user opens an Office 365 ProPlus program. + + +- Check that there is connectivity between the shared computer and the Internet. + + + + + + +![Unlicensed product error message](images/4bab7afd-4ffa-4775-bc8b-86767198d140.png) + + + + + + + + + + + + +### Sorry, we cannot verify the license currently installed for this product. + + +This error means that Office 365 ProPlus has a problem with the user's licensing token on the shared computer. The user should make sure to sign in to Office 365 ProPlus with his user account for Office 365 so that Office 365 ProPlus can obtain a new licensing token from the Office Licensing Service on the Internet. + + + + + + + +![Cannot verify product license message](images/f8bb9b93-f25d-44ff-b46e-a9e163704663.png) + + + + + + + + + + + + +### PRODUCT NOTICE Your shared computer license expires on and we're having trouble renewing it. + + +This error means that Office 365 ProPlus tried to renew the licensing token automatically, but there was a problem. One possible cause for this is that the shared computer wasn't connected to the Internet when Office 365 ProPlus tried to renew the licensing token with the Office Licensing Service. + + + +The licensing token is valid until the date listed in the error message. The user can continue to use Office 365 ProPlus to create, edit, and print documents. The user can choose **Renew** to try to renew the license before the license token expires. + + + + + + + +![Shared computer license expires date](images/f29ab2ab-6699-41b4-8fbb-232f66137426.png) + + + + + + + + + + + + +### Sorry, this Office 365 account has recently been used to activate too many computers. + + +Microsoft places a limit on the number of shared computers that a user can activate Office 365 ProPlus on in a given time period. This error means that the user exceeded that limit. + + + + + + + +![Too many computer activated](images/1166f881-87da-4667-a4bd-e92c23859de2.png) + + + + + + + + + + + + +## See also + + + +#### Other Resources + + + + + + [Overview of shared computer activation for Office 365 ProPlus](overview-of-shared-computer-activation-for-office-365-proplus.md) + + + + [Deploy Office 365 ProPlus by using Remote Desktop Services](deploy-office-365-proplus-by-using-remote-desktop-services.md) diff --git a/DeployOffice/upgrade-from-office-365-proplus-2013-to-2016.md b/DeployOffice/upgrade-from-office-365-proplus-2013-to-2016.md new file mode 100644 index 000000000..3ac8b8117 --- /dev/null +++ b/DeployOffice/upgrade-from-office-365-proplus-2013-to-2016.md @@ -0,0 +1,108 @@ +--- +title: Upgrade from Office 365 ProPlus 2013 to 2016 +ms.prod: OFFICE365 +ms.assetid: 5ce548ce-7a28-4ce4-a87f-ab4413bdcb40 +--- + + +# Upgrade from Office 365 ProPlus 2013 to 2016 + +To upgrade from Office 2013 to Office 2016 requires planning and testing. If you're an admin responsible for deploying Office 365 ProPlus in your organization, we want to provide you with information to help you prepare for and perform the upgrade. + + + + + +> [!IMPORTANT] +> Support for the Office 2013 version of Office 365 ProPlus ended on February 28, 2017. For more information, see Microsoft Knowledge Base (KB) article [3199744.](https://support.microsoft.com/kb/3199744) + + + + + +We'll be adding more guidance, but here are some things you can review in the meantime: + + + + + +- [Plan your upgrade from Office 365 ProPlus 2013 to 2016](plan-your-upgrade-from-office-365-proplus-2013-to-2016.md) + + +- [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) + + +- [Change management for Office 365 clients](change-management-for-office-365-clients.md) + + +In addition, to follow is information about [key dates](upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Key) to be aware of and what you can do now to start [testing Office 2016](upgrade-from-office-365-proplus-2013-to-2016.md#BKMK_Testing). +## Key dates for Office 365 ProPlus upgrades + + +As you plan your Office 365 ProPlus upgrade, the following table shows recent and upcoming dates to keep in mind. For information about earlier dates, refer to the table that follows this one. + + + + +**Recent and upcoming dates** + + +|**Date**|**What happens**|**More information**| +|:-----|:-----|:-----| +|March 21, 2017 (approximately)
|Microsoft-initiated upgrades are scheduled to resume.
| Microsoft-initiated upgrades were paused in December 2016 to make some changes based on customer feedback.
Microsoft-initiated upgrades are only for Office 365 ProPlus installations that are configured to receive updates automatically from the Office Content Delivery Network (CDN) and meet certain criteria. For more information about Microsoft-initiated upgrades, [read this overview](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md).
If you don't want to get these upgrade notifications, [review this information](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md) on how to configure the computers in your organization to prevent them from being considered for these upgrades.
A Microsoft-initiated upgrade isn't your only choice for upgrading your existing installations of Office 365 ProPlus. You can use the following upgrade methods and upgrade whenever is best for your organization:
Deploy Office 2016 to your users by using enterprise software deployment tools, such as System Center Configuration Manager.
Allow users to upgrade themselves from Office 365, if they're local administrators on their computer.
| +|February 22, 2017
|Version 1609 (Build 7369.2118) of Deferred Channel provides feature updates.
Version 1701 (Build 7766.2060) of First Release for Deferred Channel is available to begin enterprise validation.
|If you're using Deferred Channel and Office is configured to receive updates automatically from the Office Content Delivery Network (CDN), then you get these feature updates from Deferred Channel automatically.
If you have a specific business need to delay receiving these feature updates from Deferred Channel, you need to manually configure Office to continue receiving the most current security updates for Version 1605 of Deferred Channel. As of February 22, 2017, the most current release of Version 1605 is Build 6965.2136. For more information, see [Delay receiving feature updates from Deferred Channel for Office 365 ProPlus](delay-receiving-feature-updates-from-deferred-channel-for-office-365-proplus.md).
For enterprise validation, test your line-of-business applications, add-ins, and macros with First Release for Deferred Channel. If you find problems with the release, provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://premier.microsoft.com/) agreement, if you have one.
[Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_CBB)
[First Release for Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB)
| +|February 22, 2017
|In Deferred Channel, Office 2013 software that uses Click-to-Run can be installed on the same computer with Office 2016 software that uses Click-to-Run.
For example, installing the retail version of Visio Professional 2013, which uses Click-to-Run, on the same computer with the Office 2016 version of Office 365 ProPlus is supported.
|Only certain installation scenarios are supported. For more information, see [Supported scenarios for installing different versions of Office, Visio, and Project on the same computer](https://technet.microsoft.com/library/mt712177%28v=office.16%29.aspx).
These scenarios are supported starting with Version 1609 (Build 7369.2118) of Deferred Channel.
Support for these scenarios in Current Channel and First Release for Deferred Channel has been available since October 11, 2016.
| +|February 28, 2017
|**Important:** Support ends for the Office 2013 version of Office 365 ProPlus.
|Microsoft Knowledge Base (KB) article [3199744](https://support.microsoft.com/kb/3199744)
| +|June 13, 2017 (approximately)
|Deferred Channel provides feature updates.
First Release for Deferred Channel is available to begin enterprise validation.
|For enterprise validation, test your line-of-business applications, add-ins, and macros with First Release for Deferred Channel. If you find problems with the release, provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://premier.microsoft.com/) agreement, if you have one.
[Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_CBB)
[First Release for Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB)
| + +The following table provides information about earlier dates related to Office 365 ProPlus upgrades. The table is ordered by date, with the most recent date listed first. + + + + +**Earlier dates** + + +|**Date**|**What happens**|**More information**| +|:-----|:-----|:-----| +|October 11, 2016
|Version 1605 (Build 6965.2092) of Deferred Channel provides feature updates.
Version 1609 (Build 7369.2038) of First Release for Deferred Channel is available to begin enterprise validation.
|For enterprise validation, test your line-of-business applications, add-ins, and macros with First Release for Deferred Channel. If you find problems with the release, provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://premier.microsoft.com/) agreement, if you have one.
[Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_CBB)
[First Release for Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB)
| +|October 11, 2016
|Office 2013 software that uses Click-to-Run can be installed on the same computer with Office 2016 software that uses Click-to-Run.
For example, installing the retail version of Visio Professional 2013, which uses Click-to-Run, on the same computer with the Office 2016 version of Office 365 ProPlus is supported.
| Only certain installation scenarios are supported. For more information, see [Supported scenarios for installing different versions of Office, Visio, and Project on the same computer](https://technet.microsoft.com/library/mt712177%28v=office.16%29.aspx).
These scenarios are supported starting with the following releases:
Version 1609 (Build 7369.2038) of Current Channel.
Version 1609 (Build 7369.2038) of First Release for Deferred Channel.
Support for these scenarios in Deferred Channel is scheduled to be available in February 2017.
| +|July 3, 2016 (approximately)
|All Office 365 ProPlus installations that meet the criteria for a Microsoft-initiated upgrade should see the upgrade notification.
| [Criteria used to determine if Office can be upgraded successfully](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md#BKMK_Criteria)
[Timing of the upgrade notifications](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md#BKMK_Timing)
| +|June 21, 2016
|Microsoft-initiated upgrades resumed for computers that hadn't yet downloaded the Office 2016 upgrade files.
| Keep in mind that only Office 365 ProPlus installations that meet [certain criteria](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md#BKMK_Criteria) receive upgrade notifications. Also, [when an upgrade notification appears](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md#BKMK_Timing) can vary, even for computers in the same organization.
If you don't want to get these upgrade notifications, [review this information](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md) on how to configure the computers in your organization to prevent them from being considered for these upgrades.
Users who aren't local administrators on their computer won't see an upgrade notification. We're currently investigating ways to enable non-admin users to perform the upgrade. In the meantime, if you want to upgrade those users, you can do the following:
Temporarily provide your users with administrator rights on their computer, so that they can perform the upgrade.
Deploy Office 2016 to those users by using enterprise software deployment tools, such as System Center Configuration Manager.
A Microsoft-initiated upgrade isn't your only choice for upgrading your existing installations of Office 365 ProPlus. You can use the following upgrade methods and upgrade whenever is best for your organization:
Deploy Office 2016 to your users by using enterprise software deployment tools, such as System Center Configuration Manager.
Allow users to upgrade themselves from Office 365, if they're local administrators on their computer.
| +|June 14, 2016
|Microsoft-initiated upgrades resumed for computers that had downloaded the Office 2016 upgrade files prior to May 9, 2016.
|Between May 4 and May 9, some computers might have downloaded the files needed to upgrade to Office 2016, but the user hadn't yet seen an upgrade notification. When we paused Microsoft-initiated upgrades on May 9, upgrade notifications were also paused.
We have resumed Microsoft-initiated upgrades for those computers that already have the upgrade files downloaded. This means that users, who are local administrators on those computers, will begin to see upgrade notifications.
| +|June 14, 2016
|Deferred Channel provides feature updates.
First Release for Deferred Channel available to begin enterprise validation.
|If you're using Deferred Channel and Office is configured to receive updates automatically from the Office Content Delivery Network (CDN), then you get these feature updates from Deferred Channel automatically. These feature updates are in Version 1602 (Build 6741.2048).
If you have a specific business need to delay receiving these feature updates from Deferred Channel, you need to manually configure Office to continue receiving the most current security updates for Version 1509 of Deferred Channel. As of June 14th, the most current release of Version 1509 is Build 6001.1082. For more information, see [Delay receiving feature updates from Deferred Channel for Office 365 ProPlus](delay-receiving-feature-updates-from-deferred-channel-for-office-365-proplus.md).
For enterprise validation, test your line-of-business applications, add-ins, and macros with First Release for Deferred Channel. If you find problems with the release, provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://premier.microsoft.com/) agreement, if you have one.
[Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_CBB)
[First Release for Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB)
| +|May 9, 2016
|Microsoft-initiated upgrades paused.
| We identified a previously unknown caching issue with some Microsoft-initiated upgrades. This caching issue caused some Office 2013 licensing and program installation information to be deleted. Because of this issue, we've paused further Microsoft-initiated upgrades while we work on a resolution to the issue. At this time, users won't see any upgrade notifications.
We have developed a fix for this issue, which we'll release prior to resuming Microsoft-initiated upgrades. Those upgrades are currently scheduled to resume on or about June 21, 2016.
If you don't want to get these upgrade notifications, [review this information](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md) on how to configure the computers in your organization to prevent them from being considered for these upgrades.
If you're using other upgrade methods, such as the following, you can upgrade whenever is best for your organization:
Deploying the upgrade to your users. For example, by using enterprise software deployment tools, such as System Center Configuration Manager.
Allowing users to upgrade themselves from Office 365, if they're local administrators on their computer.
| +|May 4, 2016
|Microsoft-initiated upgrades resumed.
|Microsoft-initiated upgrades are only for Office 365 ProPlus installations that are configured to receive updates automatically from the Office Content Delivery Network (CDN) and meet certain criteria. For more information about Microsoft-initiated upgrades, [read this overview](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md).
| +|April 22, 2016
|Microsoft-initiated upgrades paused.
|Microsoft-initiated upgrades were paused due to an issue with the April 5, 2016 update for Outlook 2013 (KB3114941). This update can cause intermittent crashes of Lync 2013 (Skype for Business) or Outlook 2013. For more information about this issue, see Microsoft Support Knowledge Base (KB) article [3158521](https://support.microsoft.com/kb/3158521).
Microsoft-initiated upgrades won't resume until a fix for this issue is released. We don't want to begin an upgrade if we know there's a significant issue with Office 2013.
Some users still might see upgrade notifications, primarily users who have slow or unreliable Internet connections. That's because the files needed to upgrade to Office 2016 began downloading in the background, but didn't complete, before the Microsoft-initiated upgrades were paused. Once the download completes, users see the upgrade notification the next time they open an Office app.
| +|April 20, 2016
|Microsoft-initiated upgrades resumed to a small percentage of Office 365 ProPlus installations.
|Microsoft-initiated upgrades are only for Office 365 ProPlus installations that are configured to receive updates automatically from the Office Content Delivery Network (CDN) and meet certain criteria. For more information about Microsoft-initiated upgrades, [read this overview](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md).
| +|March 8, 2016
|First Release for Deferred Channel available to begin enterprise validation.
|For enterprise validation, test your line-of-business applications, add-ins, and macros with First Release for Deferred Channel. If you find problems with the release, provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://premier.microsoft.com/) agreement, if you have one.
[First Release for Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB)
[Office 365 client update channel releases](https://technet.microsoft.com/office/mt465751)
| +|February 25, 2016
|Microsoft-initiated upgrades paused.
| We identified an issue with the upgrade experience for users who aren't local administrators on their computer. Because of this issue, we paused further Microsoft-initiated upgrades while we worked on a mitigation for the issue.
If you're using other upgrade methods, such as the following, you can upgrade whenever is best for your organization:
Deploying the upgrade to your users. For example, by using enterprise software deployment tools, such as System Center Configuration Manager.
Allowing users to upgrade themselves from Office 365, if they're local administrators on their computer.
| +|February 23, 2016
|Microsoft-initiated upgrades begin to a small percentage of Office 365 ProPlus installations.
|Microsoft-initiated upgrades are only for Office 365 ProPlus installations that are configured to receive updates automatically from the Office Content Delivery Network (CDN) and meet certain criteria. For more information about Microsoft-initiated upgrades, [read this overview](overview-of-the-upgrade-of-office-365-proplus-to-the-office-2016-version.md).
| +|February 23, 2016
|The Office 2016 version of Office 365 ProPlus is available for users to install from the Software page in Office 365, if that's been configured by the admin.
| [Manage user software in Office 365](http://technet.microsoft.com/library/c13051e6-f75c-4737-bc0d-7685dcedf360%28Office.14%29.aspx)
| +|February 9, 2016
| The Office 365 admin center is updated to allow admins to do the following:
Control whether their users can install Office 2016 or Office 2013 from the Software page in Office 365.
Control which channel of Office 2016 users install: Current Channel or Deferred Channel.
| [Manage user software in Office 365](http://technet.microsoft.com/library/c13051e6-f75c-4737-bc0d-7685dcedf360%28Office.14%29.aspx)
| +|February 9, 2016
|Office 2016 is released in Deferred Channel.
| [Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_CBB)
[Office 365 client update channel releases](https://technet.microsoft.com/office/mt465751)
| +|September 22, 2015
| Office 2016 is released in the following channels:
Current Channel
First Release for Deferred Channel
| [Current Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_CB)
[First Release for Deferred Channel for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB)
[Office 365 client update channel releases](https://technet.microsoft.com/office/mt465751)
| + + +## Start testing Office 2016 with First Release for Deferred Channel + + +If you have line-of-business applications, add-ins, or macros, we recommend you begin testing now with [First Release for Deferred Channel](overview-of-update-channels-for-office-365-proplus.md#BKMK_FRCBB). To start testing, you can do the following: + + + + +- Download the [Office Deployment Tool](https://www.microsoft.com/download/details.aspx?id=49117) (Office 2016 version) + + +- Edit the [configuration.xml file](configuration-options-for-the-office-2016-deployment-tool.md), so that the value of the Channel attribute is set to FirstReleaseDeferred. + + +- Use the Office Deployment Tool and the XML file to download and install the First Release for Deferred Channel version of Office 365 ProPlus on to your test computers. + + +If you find problems with the release, provide feedback as soon as possible to Microsoft through your [Microsoft Premier](https://premier.microsoft.com/) agreement, if you have one. + + + + diff --git a/DeployOffice/use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md b/DeployOffice/use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md new file mode 100644 index 000000000..c9599d2af --- /dev/null +++ b/DeployOffice/use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md @@ -0,0 +1,445 @@ +--- +title: Use the Office Compatibility Toolkit to assess application compatibility for Office 365 ProPlus +ms.prod: OFFICE365 +ms.assetid: 9b0b48f2-1937-4b10-8274-1ccdb2f5d019 +--- + + +# Use the Office Compatibility Toolkit to assess application compatibility for Office 365 ProPlus + +The Office Compatibility Toolkit helps you identify compatibility issues with your Microsoft Visual Basic for Applications (VBA) macros and add-ins that you use with Office. The Office Compatibility Toolkit creates an Excel report with VBA macro compatibility and add-in readiness information to help your organization assess its readiness to move to Office 365 ProPlus. + + + + +You can download the Office Compatibility Toolkit for free from the [Microsoft Download Center](https://www.microsoft.com/downloads). +> [!IMPORTANT] +> The Office Compatibility Toolkit doesn't repair or fix the code in your VBA macros. If you create an advanced report, the report does provide guidance, when available, for remediating your VBA macro code. + + + + +The Office Compatibility Toolkit can scan for VBA macros in Word, Excel, PowerPoint, Access, and Visio files, for Office versions as far back as Office 2003. It can also scan for certain types of add-ins used with Office. Add-ins for all Office applications are identified, but it doesn't include web add-ins. For more information, see [File extensions scanned for VBA macros](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_FileExt) and [Types of add-ins for which the Office Compatibility Toolkit collects data](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_AddinTypes).The download is an MSI file that you can use to install the Office Compatibility Toolkit on a user's computer. After it's installed, when you run the Office Compatibility Toolkit, a UI wizard steps you through the process of creating a readiness report. There is also a standalone executable that can be run from the command line or used with scripts. This is useful if you need to collect readiness information from users throughout your enterprise in a more automated manner. For more information, see [Getting readiness information for multiple users in an enterprise ](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_Enterprise).The following information is provided to help you use the Office Compatibility Toolkit: +- [Creating a readiness report](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_Creating), including requirements and limitations, choosing the information to base your report on, and the difference between a basic and an advanced report. + + +- [Interpreting the information in the readiness report](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_Interpreting), for both VBA macros and add-in readiness. + + +- [Getting readiness information for multiple users in an enterprise ](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_Enterprise), and using a command-line version of the Office Compatibility Toolkit to scan multiple computers. + + +- [Additional information](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_AddInfo), including file extensions that are scanned by the Office Compatibility Toolkit, the types of add-ins the Office Compatibility Toolkit collects data on, and examples of the information sent to Microsoft when creating an advanced report. + + + +## Creating a readiness report + + + +### Requirements and limitations for using the Office Compatibility Toolkit + + +Before installing and using the Office Compatibility Toolkit, you should be aware of the following requirements: + + + + +- Windows 7 Service Pack 1 (SP1) or later + + +- Microsoft .NET Framework 4.5.1 or later + + +- Excel 2010 or later + + +- [Microsoft Power Query for Excel add-in ](https://www.microsoft.com/download/details.aspx?id=39379) (if you're not using Excel 2016) + + +- [Microsoft Access Database Engine 2010 Redistributable ](https://www.microsoft.com/download/details.aspx?id=13255) (only if you're using a Click-to-Run version of Access) + + +Also, there a few limitations about the Office Compatibility Toolkit that you should know about: + + + + +- The Office Compatibility Toolkit can't scan password protected files. If you try to scan one of these files, the file shows up as "Password protected" in the report. + + +- The Office Compatibility Toolkit can't scan files that are saved in a SharePoint document library, in OneDrive, or in some other type of cloud-based storage location. If you try to scan one of these files, the file shows up as "Cloud-based" in the report. + + +- The Office Compatibility Toolkit lists each issue with an Office document in a separate row in an Excel worksheet. Therefore, the Office Compatibility Toolkit can only return 1,046,575 results. The Office Compatibility Toolkit stops processing the report once it reaches that limit. If you expect to exceed these limits, we recommend that you narrow the scope of your report, such as to a specific department. + + + +### Choosing the information to use to create your report + + +To create a readiness report, you first need to select what information to use to create the report. The following table lists the possible options and an explanation of each option. It also specifies which type of readiness report is created with each option. + + + + + +|**Option**|**Explanation**|**Report created**| +|:-----|:-----|:-----| +|Most recently used Office documents and installed add-ins on this computer
|The Office Compatibility Toolkit only scans Office documents that are in the user's list of most recently used files. This allows you to narrow the focus of the scan to documents that a user accesses on a regular basis.
In addition, the Office Compatibility Toolkit looks for any add-ins for Office that are installed on the computer on which the Office Compatibility Toolkit is run.
|VBA and Add-in
| +|Office documents in a local folder or network share.
|The Office Compatibility Toolkit scans the Office documents in the folder or network share that you specify. The Office Compatibility Toolkit automatically scans the specified location, and all the subfolders in that location.
**Note:** With this option, the Office Compatibility Toolkit doesn't look for add-ins installed on the computer on which the Office Compatibility Toolkit is run.
|VBA only
| +|Previous readiness results saved together in a local folder or network share.
|This option allows you to create a consolidated report comprised of individual readiness results from multiple standalone computers.
For example, you might want to run the Office Compatibility Toolkit on all the computers in the Finance department, saving the results of each scan to a network share. Then, you can use this option to create a consolidated report for the Finance department.
For more information, see [Getting readiness information for multiple users in an enterprise ](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_Enterprise).
|VBA only, or VBA and Add-in, depending on what readiness results are being used.
| +|Add-in data from Office Telemetry dashboard.
|If you're already using [Office Telemetry Dashboard](https://technet.microsoft.com/library/jj822978%28v=office.16%29.aspx) to assess add-in compatibility, you can use that information which you've already collected to create a readiness report. You just need to provide the Office Compatibility Toolkit with the appropriate information to access the database for Telemetry Dashboard.
**Note:** With this option, the Office Compatibility Toolkit doesn't look for VBA macros.
|Add-in only
| + +Keep in mind that only Word, Excel, PowerPoint, Access, and Visio files are scanned for VBA macros. For a list of the type of files scanned, see [File extensions scanned for VBA macros](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_FileExt). + + + + +### Choosing between a basic and an advanced report + + +After you select what information to use to create your report and specify a location to save your report, you need to choose whether to create a basic report or an advanced report. + + + +We strongly recommend that you create an advanced report because an advanced report provides additional information to help you assess the compatibility of your VBA macros and add-ins with Office 365 ProPlus. For example, in an advanced report, you get the following additional information: + + + + +- Remediation advice, when available, for issues found in your VBA macros. This information is shown in a separate worksheet in the report. + + +- Readiness status for add-ins. For example, the report might show that the software provider has a supported version of the add-in for Office 365 ProPlus. + + +The readiness status for add-ins is derived from telemetry-based computations as well as explicit support statements from ISVs. + + + +To provide you with the most up-to-date remediation advice and readiness status, the Office Compatibility Toolkit contacts Microsoft when it creates the report. Some information about your VBA macros and add-ins is sent to Microsoft. For more information about what is sent, see [Examples of the information sent to Microsoft when creating an advanced report](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_InfoSent). + + + + +## Interpreting the information in the readiness report + + +The Office Compatibility Toolkit creates a readiness report as an Excel file. The readiness information available in the report depends on what information you based your report on, as well as whether you chose to create a basic or advanced report. + + + +Each report starts with an Overview page, which provides high-level information about the results, and links to the reports available - [VBA readiness reports](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_VBAReport) or [Add-in report](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_AddinReport) or both. + + + + +### VBA readiness reports + + +The following table provides a list of the different tabs (worksheets) that are shown in a VBA readiness report. + + + + + +|**Worksheet name**|**Contents**| +|:-----|:-----| +|VBA Overview
|Displays three pie charts to provide a high-level overview of the results of the scan.
Each pie charts shows different information: the status of the files scanned, the readiness status for the unique macros found during the scan, and readiness status of the unique files scanned. See the tables later in this section for more information about the file status and readiness status values that appear in these pie charts.
The Office Compatibility Toolkit creates a unique hash of the VBA macro code to identify macros that are reused in multiple files. The Office Compatibility Toolkit does something similar to identify duplicate files. The Office Compatibility Toolkit does this to provide you with a more realistic assessment of how many unique VBA macros and unique files need to be evaluated.
**Note:** If you plan to deploy the 64-bit version of Office 365 ProPlus, be sure that the "Include 64-bit readiness data" check box is selected and that you've refreshed the report.
| +|VBA Summary
|Provides some pre-defined PivotTables to allow you to analyze the data captured from the scan.
If these PivotTables don't meet your specific needs, you can create your own based on the data on the VBA Results worksheet.
| +|VBA Results
|Provides information on each file scanned by the Office Compatibility Toolkit. If multiple issues are found in a scanned file, there is a separate row for each issue.
See the table under the "Detailed VBA information" heading at the end of this section for an explanation of the information that appears in each column.
| +|VBA Remediation
|Provides proposed changes to VBA macro code found during the scan.
See the table under the "Detailed VBA information" heading at the end of this section for an explanation of the information that appears in each column.
| +|VBA References
|List references identified in code and in the VBA project. These references are generally used to call external DLLs or linked files for use by the VBA code.
See the table under the "Detailed VBA information" heading at the end of this section for an explanation of the information that appears in each column.
| + + **File status:** The report also categorizes, by a file status, the files that were scanned. The following table lists the possible file statuses that can appear in a readiness report, and an explanation of the file status. + + + + + +|**File status**|**Explanation**| +|:-----|:-----| +|No VBA
|The file was scanned and no VBA macro code was found.
| +|Has VBA
|The file was scanned and VBA macro code was found.
| +|Cloud-based
|The file couldn't be scanned because it is saved in a SharePoint document library, in OneDrive, or in some other type of cloud-based storage location.
| +|Password protected
|The file is password protected so it couldn't be scanned for VBA macros.
| +|Inaccessible
|The file couldn't be scanned for some reason, such as the Office Compatibility Toolkit had insufficient permission to access the file, the file is corrupted, or the file uses a very old Office file format.
| +|Locked
|The file was locked or in use when the scan was performed.
| +|Error
|The VBA code stream trying to be read during the scan wasn't in a valid format. Sometimes opening, and then saving, the file in a supported Office version will allow the Office Compatibility Toolkit to scan the file.
| + + **Severity level:** The report categorizes, by a severity level, the issues found with the VBA macros to help you estimate how much effort it will take to address the issues found. If multiple issues are found with a VBA macro, the report displays the highest severity level in the pie chart. + + + +The following table lists the possible severities that can appear in a readiness report, and an explanation of the severity level. + + + + + +|**Severity**|**Explanation**| +|:-----|:-----| +|Ready to upgrade
|No issues were found in this file and it's compatible with Office 365 ProPlus.
| +|Code design awareness
|While the code will function as expected and the user isn't likely to notice any change, the feature, property, or method works differently than previously or might be deprecated in favor of a newer version.
| +|Minimal validation recommended
|No runtime or compile time errors are expected, but the API functionality may have changed in some way. It's recommended that the user runs a spot check on the file with Office 365 ProPlus to ensure it continues to function as expected. To minimize environmental issues, ideally run the spot check on the computer that the macro usually runs.
| +|Limited remediation required
|Some refactoring of code will be required. But, there is a clear replacement and so the expectation is that the work required to fix the macro is significantly reduced.
| +|Significant remediation required
|Significant code refactoring will be required to enable the code to continue to function as it did in the legacy Office version. For example, an API that has been deprecated, but no replacement function has been provided. In this case, the only option available is to recreate the functionality.
| + + **Detailed VBA information:** The VBA Results, VBA Remediation, and VBA References tabs in the VBA readiness report each contain similar columns of information. The following table provides a list of those columns, along with an explanation of what information is contained those columns. + + + + + +|**Column name**|**Explanation**|**Example**| +|:-----|:-----|:-----| +|Guideline
|The guideline (rule) identified when document has been scanned.
|Program Toolbars and Menu Bars will no longer be visible in Access 2013.
| +|Severity
|Severity of issue identified.
|Significant remediation required
| +|Source Location
|Location of the file that was scanned.
|D:\\My Documents\\My Files\\
| +|Source File
|Name of the file that was scanned.
|MyFileName.xlsx
| +|Source File Hash
|Uniquely generated hash for the file.
|36426A0DCFC06F6425E205F107A5CA58
| +|Source File Extension
|Extension of the file that was scanned.
|.docm
| +|Module
|Name of the module where the code issue was identified.
|mDJSCommandBars
| +|Line #
|Line number where the code issue was identified.
|112
| +|Type
|Type of issue that has been identified.
|VBA
| +|Member
|VBA Module section name where the issue was identified (i.e. function).
|CommandBars
| +|Statement
|The section of the code where the issue was identified.
|Dim ctlName As CommandBarControl
| +|VBA Hash
|Uniquely generated hash for the VBA code.
|CC-D2-F3-9C-58-48-04-E4-16-5B-B6-44-B3-EB-EB-FE
| +|Reference
|Link to description of issue and help content (where applicable)
| [https://technet.microsoft.com/library/cc178954.aspx](https://technet.microsoft.com/library/cc178954.aspx)
| +|File Status
|Classification of the status of the file that was processed
|Password protected
| +|64Bit
|Specifies if the issues identified is 64-bit specific
|Yes
| +|UserHash
|User of the file
|Katharine Cruz
| +|DeviceName
|Name of the device where the scan was performed
|Laptop01
| + + +### Add-in report + + +The following table provides a list of the different tabs (worksheets) that are shown in an add-in report. + + + + + +|**Worksheet name**|**Contents**| +|:-----|:-----| +|Add-in Summary
|Provides a high-level overview of the add-ins found by the Office Compatibility Toolkit.
The data at the top of the worksheet is intended to give you a quick assessment of how many add-ins will likely be compatible with Office 365 ProPlus and how many add-ins you'll need to do more research on.
| +|Add-in details
|Provides metadata information about the add-ins found (for example, publisher and version number), the total number of installs of each add-in, and, if an advanced report, the readiness status (for example, "Supported version available").
| +|By computer name
|Provides similar information to what's on the Add-in details worksheet, but lists every computer that the add-in is installed on, instead of just a total number of installs for the add-in.
| + +You can adjust what information is shown in the add-in report by selecting choices from the drop-down lists on the Add-in Summary tab, and then refreshing the report. For example, you can adjust the report to only show information about Access and Excel add-ins. + + + +By default, add-ins that are shipped by Office aren't shown. If you want to see information about those add-ins, select "Yes" from the drop-down list and refresh the report. But, most enterprises won't need to worry about application compatibility of add-ins which are shipped with Office. + + + +If you plan to deploy the 64-bit version of Office 365 ProPlus, be sure to select "64-bit" from the drop-down list and refresh the report. This provides 64-bit specific readiness information about the add-ins. The default selection for reports is 32-bit. + + + +The following table lists the possible readiness statuses that you can see in the add-in report and an explanation of what each status means. + + + + + +|**Readiness status**|**Explanation**| +|:-----|:-----| +|Adopted
|This add-in is being used on Office 365 ProPlus in other organizations, but the software provider doesn't officially support the add-in on Office 365 ProPlus.
| +|Contact software provider
|This add-in might have issues with Office 365 ProPlus. You need to decide if this add-in is business critical and then contact the software provider for guidance.
| +|Supported version available
|A supported version of this add-in for Office 365 ProPlus is available from the software provider.
| +|Unknown
|This add-in is unknown to Microsoft. For example, it could be a line-of-business add-in that your in-house application development team created.
If you create a basic report, the readiness status for all add-ins is listed as Unknown. It's only when you create an advanced report that the Office Compatibility Toolkit contacts Microsoft to try to get readiness status of add-ins.
| + + **Detailed add-in information:** The "Add-in details" and "By computer name" tabs in the add-in report each contain similar columns of information. The following table provides a list of those columns, along with an explanation of what information is contained in those columns. + + + + + +|**Column name**|**Explanation**| +|:-----|:-----| +|Computer name
|The name of the computer on which the add-in is installed.
This column only appears on the "By computer name" tab.
| +|Add-in Name
|The name of the add-in.
| +|Add-in Publisher
|The name of the add-in's publisher.
| +|Add-in Version
|The version of the add-in.
| +|App
|The Office application that the add-in is used in. For example, Word or Excel.
| +|Total Installs
|The total numbers of installs of the add-in.
This column only appears on the "Add-in details" tab.
| +|Readiness status (32-bit)
|The readiness status for the add-in. Advanced reports only.
See the table above for a list of possible readiness statuses.
**Note:** If you chose "64-bit" from the drop-down list on the "Add-in Summary" tab, this column name displays as "(64-bit)" instead.
| +|Remarks
|Additional information, if available, about the readiness status of the add-in. Advanced reports only.
| +|More information
|Link to additional readiness information about the add-in. Advanced reports only.
| + + +## Getting readiness information for multiple users in an enterprise + + +It's easy enough to install and run the Office Compatibility Toolkit on a single user's computer to create a readiness report. But what if you're in a large organization and need to create readiness reports for an entire department or branch office? + + + +Along with the UI wizard version of the Office Compatibility Toolkit, there is also a standalone executable that can be run from the command line or used with scripts. It's named OfficeCompatibilityToolkit.exe and is located in the folder where the Office Compatibility Toolkit is installed. + + + +If you have your users run the UI wizard version of the Office Compatibility Toolkit, you end up with separate Excel files, one for each user. That makes it difficult to see readiness from a departmental or office-wide perspective. You also have to rely on the users to run the Office Compatibility Toolkit and follow the instructions correctly. + + + +The better alternative might be to use the command line capabilities of the Office Compatibility Toolkit and use a script to run the Office Compatibility Toolkit to collect the information on behalf of the user. You can save the files created by the Office Compatibility Toolkit to a network share. If you do this, make sure that the appropriate write permissions are given to the share. + + + +You can see a list of the available command line options by opening a command prompt, navigating to the folder where you installed the Office Compatibility Toolkit, and then typing the following command: + + + + + + +``` + +OfficeCompatibilityToolkit.exe -help +``` + +The command line version of the Office Compatibility Toolkit doesn't have the all the same capabilities as the UI wizard version. You can use the command line version to scan the most recently used Office documents and installed add-ins on a computer, or Office documents in a local folder or network share. + + + +The following is an example of a command line that you can run to scan for both VBA macros and add-ins, and save the results to a network share for the Finance department. Note that you have to include addinscan option as part of the command line for the add-in scan to occur.. + + + + + + +``` +OfficeCompatibilityToolkit.exe -mru -addinscan -output \\\\server01\\finance -silent +``` + +The following is an example of a command line that you can run to scan a user's most recently used Office documents and save the results to a network share for the Finance department. This only scans for VBA macros. + + + + + + +``` +OfficeCompatibilityToolkit.exe -mru -output \\\\server01\\finance -silent +``` + +The following is an example of a command line that you can run to scan a folder, and all its subfolders, and save the results to a network share for the Finance department. This only scans for VBA macros. + + + + + + +``` +OfficeCompatibilityToolkit.exe -p c:\\officefiles\\ -r -output \\\\server01\\finance -silent +``` + +It's important to note that when you run the Office Compatibility Toolkit from the command line, the Office Compatibility Toolkit doesn't create an Excel file. Instead the Office Compatibility Toolkit creates a TSV file or a JSON file. The TSV file contains the VBA macro information from the scan, and the JSON file contains the add-in information from the scan. + + + +To create a consolidated Excel report from these various command line scans, you need to run the UI wizard version of the Office Compatibility Toolkit. For the information source, select "Previous readiness results saved together in a local folder or network share," and then specify the location where you saved all the TSV and JSON files for the scans. The Office Compatibility Toolkit then consolidates the information from the TSV and JSON files into a readiness report in a single Excel file. + + + +Keep in mind that the Office Compatibility Toolkit lists each issue with an Office document in a separate row in the Excel worksheet. Therefore, the Office Compatibility Toolkit can only return 1,046,575 results. The Office Compatibility Toolkit stops processing the report once it reaches that limit. If you expect to exceed these limits, we recommend that you narrow the scope of your report, such as to a specific department. + + + + +## Additional information + + + +### File extensions scanned for VBA macros + + +The following table lists, by application, the file extensions that are scanned when the Office Compatibility Toolkit looks for VBA macros in Office documents. + + + + + +|**Application**|**File extension**| +|:-----|:-----| +|Access
|accdb, accdt, mdb
| +|Excel
|xla, xlam, xls, xlsm, xlsx, xlt, xltm, xltx
| +|PowerPoint
|pot, potm, potx, ppa, ppam, pps, ppsm, ppt, pptm, pptx, sld, sldm
| +|Visio
|vsd, vsdx, vsdm
| +|Word
|doc, docm, docx, dot, dotm, dotx
| + + +### Types of add-ins for which the Office Compatibility Toolkit collects data + + +The following table lists the types of add-ins that the Office Compatibility Toolkit collects data on. Add-ins for all Office applications are identified, but it doesn't include web add-ins. + + + + + +|**Add-in type**|**Office applications**|**Description**| +|:-----|:-----|:-----| +|Automation
|Excel
|Excel-supported automation add-ins are built upon COM add-ins. Functions in Automation add-ins can be called from formulas in Excel worksheets.
| +|COM
|Excel, Outlook, PowerPoint, andWord
|COM add-ins include add-ins usually written in C++ and Visual Studio Tools for Office (VSTO) developed using managed code.
| +|VBA
|Excel, PowerPoint, andWord
|VBA add-ins are application-specific files that contain VBA code. These include macro-enabled Word templates (.dotm), Excel add-ins (.xla, .xlam), and PowerPoint add-ins (.ppa, .ppam).
| +|WLL
|Word
|WLL (.wll) add-ins are specific to Word and built with any compiler that supports building DLLs.
| +|XLL
|Excel
|XLL add-ins (.xll) are specific to Excel and are built with any compiler that supports building DLLs (dynamic-link libraries). They do not have to be installed or registered. XLL add-ins also include DLLs that contain user-defined commands and functions.
| +|XLS RTD
|Excel
|XLS real-time data (RTD) add-ins are Excel worksheets that use the RealTimeData worksheet function to call an Automation server to retrieve data in real-time.
| + + +### Examples of the information sent to Microsoft when creating an advanced report + + +When you choose to create an [Choosing between a basic and an advanced report](use-the-office-compatibility-toolkit-to-assess-application-compatibility-for-off.md#BKMK_ChooseBasicAdv), some information is sent to Microsoft. + + + +The following table provides a list of the information that is sent to Microsoft about the VBA macros that are found during a scan. + + + + + +|**Data**|**Description**|**Example**| +|:-----|:-----|:-----| +|DevicesScanned
|Number of devices that were scanned.
|DevicesScanned: 23
| +|UniqueUsers
|Count of users included in scan.
|UniqueUsers: 14
| +|Rule
|Count of how many times a specific rule was found to apply to the VBA macros scanned. A GUID is used to uniquely identify the rule.
|48f05b1d-c8ad-4d0c-9453-1abdf007b2db: 23
74db65ab-76f3-43fb-997d-0d9750efb527: 2
| +|FilesWithIssues
|Count of unique files with compatibility issues.
|FilesWithIssues: 320
| +|FilesWithDuplicateVBA
|Count of unique files containing duplicate macros.
|FilesWithDuplicateVBA: 233
| +|FilesWithNoIssuesFound
|Count of unique files with no issues.
|FilesWithNoIssuesFound: 12
| +|InaccessibleFiles
|Count of unique inaccessible files.
|Inaccessible: 4
| +|FilesPasswordProtected
|Count of unique files that were password protected.
|FilesPasswordProtected: 123
| +|FilesLocked
|Count of unique locked files.
|FIlesLocked: 0
| +|FilesWithVBA
|Count of unique files with VBA.
|FilesWithVBA: 122
| +|FilesWithoutVBA
|Count of unique files without VBA.
|FilesWithoutVBA: 11
| +|Significantremediationrequired
|Count of unique files that require significant remediation.
|Significantremediationrequired: 12
| +|Limitedremediationrequired
|Count of unique files that require limited remediation
|Limitedremediationrequired: 12
| +|Minimalvalidationrequired
|Count of unique files that require minimal validation.
|Minimalvalidationrequired: 22
| +|CodeDesignChanges
|Count of unique files that contain use of features that we would recommend changes.
|CodeDesignChanges: 1
| + +The following table provides a list of the information that is sent to Microsoft about the add-ins that are found during a scan. + + + + + +|**Data**|**Example**| +|:-----|:-----| +|AddIn Prog ID
|PDFMOutlook.PDFMOutlook
| +|FriendlyName
|Acrobat PDFMaker Office COM Addin(Outlook)
| +|Description
|Acrobat PDFMaker Office COM Addin
| +|FullPath
|C:\\Program Files (x86)\\Adobe\\Acrobat DC\\PDFMaker\\Mail\\Outlook\\PDFMOutlookAddin.dll
| +|AddinCLSID
|{9177B23F-7D46-11D6-B816-00C04FC06913}
| +|Publisher
|Adobe Systems Incorporated
| +|FileTimestamp
|1426572631
| +|FileVersion
|15.7.20033.2203
| + + diff --git a/DeployOffice/use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016.md b/DeployOffice/use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016.md new file mode 100644 index 000000000..bb575d906 --- /dev/null +++ b/DeployOffice/use-the-office-deployment-tool-to-install-volume-licensed-editions-of-visio-2016.md @@ -0,0 +1,56 @@ +--- +title: Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016 +ms.prod: OFFICE365 +ms.assetid: 82691bd7-a3d5-47ca-8d8a-0ee43ec2c01f +--- + + +# Use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016 + +You can use the Office Deployment Tool to install volume licensed editions of Visio 2016 and Project 2016 on the same computer with a Click-to-Run version of Office 2016. For example, you can install a volume licensed edition of Visio Standard 2016 on the same computer with Office 365 ProPlus. + + + + +The Office Deployment Tool uses Click-to-Run to do the installation, instead of using Windows Installer (MSI). But, Visio and Project are still activated by [volume activation methods](https://technet.microsoft.com/library/ee624358%28v=office.16%29.aspx), such as [Key Management Service (KMS)](https://technet.microsoft.com/library/dn385356%28v=office.16%29.aspx) or [Multiple Activation Key (MAK)](https://technet.microsoft.com/en-us/library/dn385359%28v=office.16%29.aspx). +> [!NOTE] +> If you're using MAK for volume activation, be sure to get the correct key from the Volume Licensing Service Center (VLSC). You want the one that says "C2R-P for use with the Office Deployment Tool." > If you're using [Overview of shared computer activation for Office 365 ProPlus](overview-of-shared-computer-activation-for-office-365-proplus.md) with Office 365 ProPlus, you need to be using at least Version 1701 of Office 365 ProPlus in order to install a volume licensed edition of Visio 2016 or Project 2016 on the same computer.> If you're not familiar with the Office Deployment Tool, it's usually used to customize deployments of Click-to-Run versions of Office products, such as Office 365 ProPlus. For more information, see [Overview of the Office 2016 Deployment Tool](overview-of-the-office-2016-deployment-tool.md). + + + + +To begin, [download the most current version](http://go.microsoft.com/fwlink/p/?LinkID=626065) of the Office Deployment Tool from the Microsoft Download Center. Then, edit the Product element in the configuration.xml file, using the appropriate ID from the following table. To use a Generic Volume License Key (GVLK) for volume activation, use the appropriate value in the table for the PIDKEY attribute. + +|**Edition**|**ID**|**PIDKEY**| +|:-----|:-----|:-----| +|Visio Standard 2016
|VisioStdXVolume
|NY48V-PPYYH-3F4PX-XJRKJ-W4423
| +|Visio Professional 2016
|VisioProXVolume
|69WXN-MBYV6-22PQG-3WGHK-RM6XC
| +|Project Standard 2016
|ProjectStdXVolume
|D8NRQ-JTYM3-7J2DX-646CT-6836M
| +|Project Professional 2016
|ProjectProXVolume
|WGT24-HCNMF-FQ7XH-6M8K7-DRTW9
| + +You can also edit the Updates element in the configuration.xml file to determine how the installation of Visio or Project is updated. For example, you can configure it so that updates are automatically installed from the Office Content Delivery Network (CDN) on the Internet, which is the default, or from a file share on your local network.Here's an example of a configuration.xml file that can be used to install a 64-bit version of Visio Professional 2016 in English from the Office CDN using a GVLK. + + +``` + + + + + + + + + +``` + +For information about other settings, see [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md).Then, use the Office Deployment Tool to download and install Visio or Project. +## See also + + +#### Other Resources + + + + + + [Supported scenarios for installing different versions of Office, Visio, and Project on the same computer](https://technet.microsoft.com/library/mt712177%28v=office.16%29.aspx) diff --git a/DeployOffice/version-and-build-numbers-of-update-channel-releases.md b/DeployOffice/version-and-build-numbers-of-update-channel-releases.md new file mode 100644 index 000000000..ba0298d1d --- /dev/null +++ b/DeployOffice/version-and-build-numbers-of-update-channel-releases.md @@ -0,0 +1,190 @@ +--- +title: Version and build numbers of update channel releases +ms.prod: OFFICE365 +ms.assetid: ae942449-1fca-4484-898b-a933ea23def7 +--- + + +# Version and build numbers of update channel releases + + **Last updated:** August 8, 2017 + + + + +For each release of an [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) by Microsoft, there is a version and build number assigned to it. The following table lists the supported version, and the most current build number, for each update channel. Versions of update channels that aren't listed in the table are no longer supported. For example, Version 1604 of Current Channel is no longer supported. + +|**Channel**|**Version**|**Build**|**Release date**| +|:-----|:-----|:-----|:-----| +|Current
|1707
|8326.2070
|August 7, 2017
| +|First Release for Deferred
|1705
|8201.2171
|August 8, 2017
| +|Deferred
|1701
|7766.2099
|July 27, 2017
| +|Deferred1
|1609
|7369.2154
|July 27, 2017
| + +1 There are always two versions of Deferred Channel that are supported. Version 1701 contains newer features and is supported until January 2018. Version 1609 is supported only until September 2017.For a complete list of update channel releases, refer to the following tables: +- [Version and build information, organized by release date](version-and-build-numbers-of-update-channel-releases.md#BKMK_ByDate) + + +- [Version and build information, organized by version](version-and-build-numbers-of-update-channel-releases.md#BKMK_ByVersion) + + +To see what features, security updates, or non-security updates are included in a specific update channel release, see [Office 365 client update channel releases](https://technet.microsoft.com/office/mt465751).These versions and build numbers apply to the following Office 365 clients: +- Office 365 ProPlus + + +- Office 365 Business + + +- Visio Pro for Office 365 + + +- Project Online Desktop Client + + +Office 365 Business is the version of Office that comes with some Office 365 plans, such as Business Premium. +## Version and build information for update channel releases + + +Each [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md) that Microsoft releases has a version and build number assigned to it. The following two tables provide a complete list of update channel releases, one by release date and the other by version. + + + + +### Version and build information, organized by release date + + +The following table provides a list of the version and build numbers for each update channel release. The table is ordered by release date, with the most recent release date listed first. To see this information organized by version number, refer to the table that follows this one. The version and build number in bold text indicates the most current version and build number for that particular channel. + + + + +**By release date** + + +|**Release date**|**Current Channel**|**First Release for Deferred Channel**|**Deferred Channel**| +|:-----|:-----|:-----|:-----| +|August 8, 2017
|Not applicable
|**Version 1705 (Build 8201.2171)**
|Not applicable
| +|August 7, 2017
|**Version 1707 (Build 8326.2070)**
|Not applicable
|Not applicable
| +|July 31, 2017
| Version 1707 (Build 8326.2062)
|Not applicable
|Not applicable
| +|July 28, 2017
| Version 1707 (Build 8326.2059)
|Not applicable
|Not applicable
| +|July 27, 2017
| Version 1707 (Build 8326.2058)
|Version 1705 (Build 8201.2158)
|**Version 1701 (Build 7766.2099)**
Version 1609 (Build 7369.2154)
| +|July 19, 2017
| Version 1706 (Build 8229.2103)
|Not applicable
|Not applicable
| +|July 13, 2017
| Version 1706 (Build 8229.2086)
| Version 1705 (Build 8201.2136)
| Version 1701 (Build 7766.2096)
Version 1609 (Build 7369.2151)
| +|June 28, 2017
| Version 1706 (Build 8229.2073)
|Not applicable
|Not applicable
| +|June 13, 2017
| Version 1705 (Build 8201.2102)
| Version 1705 (Build 8201.2102)
| Version 1701 (Build 7766.2092)
Version 1609 (Build 7369.2139)
| +|June 7, 2017
| Version 1705 (Build 8201.2075)
|Not applicable
|Not applicable
| +|June 1, 2017
| Version 1704 (Build 8067.2157)
|Not applicable
|Not applicable
| +|May 18, 2017
| Version 1704 (Build 8067.2115)
|Not applicable
|Not applicable
| +|May 9, 2017
| Version 1703 (Build 7967.2161)
| Version 1701 (Build 7766.2084)
| Version 1609 (Build 7369.2130)
Version 1605 (Build 6965.2150)
| +|April 21, 2017
| Version 1703 (Build 7967.2139)
|Not applicable
|Not applicable
| +|April 11, 2017
| Version 1702 (Build 7870.2038)
| Version 1701 (Build 7766.2076)
| Version 1609 (Build 7369.2127)
Version 1605 (Build 6965.2145)
| +|March 27, 2017
| Version 1702 (Build 7870.2031)
|Not applicable
|Not applicable
| +|March 14, 2017
| Version 1702 (Build 7870.2024)
| Version 1701 (Build 7766.2071)
| Version 1609 (Build 7369.2120)
Version 1605 (Build 6965.2140)
| +|March 9, 2017
| Version 1702 (Build 7870.2020)
|Not applicable
|Not applicable
| +|February 23, 2017
| Version 1701 (Build 7766.2060)
|Not applicable
|Not applicable
| +|February 22, 2017
|Not applicable
| Version 1701 (Build 7766.2060)
| Version 1609 (Build 7369.2118)
Version 1605 (Build 6965.2136)
| +|January 31, 2017
|Version 1612 (Build 7668.2074)
|Not applicable
|Not applicable
| +|January 25, 2017
| Version 1612 (Build 7668.2066)
|Not applicable
|Not applicable
| +|January 10, 2017
|Not applicable
| Version 1609 (Build 7369.2102)
| Version 1605 (Build 6965.2117)
Version 1602 (Build 6741.2105)
| +|January 4, 2017
| Version 1611 (Build 7571.2109)
|Not applicable
|Not applicable
| +|December 13, 2016
| Version 1611 (Build 7571.2075)
| Version 1609 (Build 7369.2095)
| Version 1605 (Build 6965.2115)
Version 1602 (Build 6741.2098)
| +|December 6, 2016
| Version 1611 (Build 7571.2072)
|Not applicable
|Not applicable
| +|November 10, 2016
| Version 1610 (Build 7466.2038)
|Not applicable
|Not applicable
| +|November 8, 2016
|Version 1609 (Build 7369.2055)
| Version 1609 (Build 7369.2055)
| Version 1605 (Build 6965.2105)
Version 1602 (Build 6741.2088)
| +|November 2, 2016
|Version 1609 (Build 7369.2054)
|Version 1609 (Build 7369.2054)
|Not applicable
| +|October 11, 2016
| Version 1609 (Build 7369.2038)
|Version 1609 (Build 7369.2038)
| Version 1605 (Build 6965.2092)
Version 1602 (Build 6741.2081)
| +|October 4, 2016
| Version 1609 (Build 7369.2024)
|Not applicable
|Not applicable
| +|September 26, 2016
|Version 1608 (Build 7341.2035)
|Not applicable
|Not applicable
| +|September 21, 2016
|Version 1608 (Build 7341.2032)
|Not applicable
|Not applicable
| +|September 13, 2016
|Version 1607 (Build 7167.2060)
|Version 1605 (Build 6965.2084)
| Version 1602 (Build 6741.2071)
Version 1509 (Build 6001.1090)
| +|September 6, 2016
|Version 1607 (Build 7167.2055)
|Not applicable
|Not applicable
| +|August 31, 2016
|Version 1607 (Build 7167.2047)
|Not applicable
|Not applicable
| +|August 16, 2016
|Version 1607 (Build 7167.2040)
|Not applicable
|Not applicable
| +|August 9, 2016
|Version 1606 (Build 7070.2036)
|Version 1605 (Build 6965.2076)
| Version 1602 (Build 6741.2063)
Version 1509 (Build 6001.1087)
| +|July 26, 2016
|Version 1606 (Build 7070.2033)
|Not applicable
|Not applicable
| +|July 21, 2016
|Not applicable
|Version 1605 (Build 6965.2069)
|Not applicable
| +|July 20, 2016
|Version 1606 (Build 7070.2028)
|Not applicable
|Not applicable
| +|July 12, 2016
|Version 1606 (Build 7070.2026)
|Version 1605 (Build 6965.2066)
| Version 1602 (Build 6741.2056)
Version 1509 (Build 6001.1085)
| +|July 5, 2016
|Version 1606 (Build 7070.2022)
|Not applicable
|Not applicable
| +|June 30, 2016
|Version 1605 (Build 6965.2063)
|Version 1605 (Build 6965.2063)
|Not applicable
| +|June 14, 2016
|Version 1605 (Build 6965.2058)
|Version 1605 (Build 6965.2058)
| Version 1602 (Build 6741.2048)
Version 1509 (Build 6001.1082)
| +|June 7, 2016
|Not applicable
|Version 1602 (Build 6741.2047)
|Not applicable
| +|June 6, 2016
|Version 1605 (Build 6965.2053)
|Not applicable
|Not applicable
| +|May 23, 2016
|Version 1604 (Build 6868.2067)
|Version 1602 (Build 6741.2042)
|Not applicable
| +|May 10, 2016
|Version 1604 (Build 6868.2062)
|Version 1602 (Build 6741.2037)
|Version 1509 (Build 6001.1078)
| +|May 4, 2016
|Version 1604 (Build 6868.2060)
|Not applicable
|Not applicable
| +|May 3, 2016
|Not applicable
|Version 1602 (Build 6741.2033)
|Not applicable
| +|April 28, 2016
|Version 1603 (Build 6769.2040)
|Not applicable
|Not applicable
| +|April 12, 2016
|Version 1603 (Build 6769.2017)
|Version 1602 (Build 6741.2026)
|Version 1509 (Build 6001.1073)
| +|April 4, 2016
|Version 1603 (Build 6769.2015)
|Version 1602 (Build 6741.2025)
|Not applicable
| +|March 24, 2016
|Version 1602 (Build 6741.2021)
|Not applicable
|Not applicable
| +|March 23, 2016
|Not applicable
|Version 1602 (Build 6741.2021)
|Not applicable
| +|March 17, 2016
|Version 1602 (Build 6741.2017)
|Not applicable
|Not applicable
| +|March 16, 2016
|Not applicable
|Version 1602 (Build 6741.2017)
|Not applicable
| +|March 14, 2016
|Not applicable
|Version 1602 (Build 6741.2015)
|Not applicable
| +|March 8, 2016
|Not applicable
|Version 1602 (Build 6741.2014)
|Version 1509 (Build 6001.1068)
| +|March 4, 2016
|Version 1601 (Build 6568.2036)
|Not applicable
|Not applicable
| +|March 3, 2016
|Version 1601 (Build 6568.2034)
|Not applicable
|Not applicable
| +|February 16, 2016
|Version 1601 (Build 6568.2025)
|Not applicable
|Not applicable
| +|February 9, 2016
|Version 1511 (Build 6366.2068)
|Version 1509 (Build 6001.1061)
|Version 1509 (Build 6001.1061)
| +|January 25, 2016
|Version 1511 (Build 6366.2062)
|Not applicable
|Not applicable
| +|January 12, 2016
|Version 1511 (Build 6366.2056)
|Version 1509 (Build 6001.1054)
|Not applicable
| +|December 11, 2015
|Version 1511 (Build 6366.2036)
|Not applicable
|Not applicable
| +|December 8, 2015
|Version 1509 (Build 6001.1043)
|Version 1509 (Build 6001.1043)
|Not applicable
| +|November 10, 2015
|Version 1509 (Build 6001.1038)
|Version 1509 (Build 6001.1038)
|Not applicable
| +|October 21, 2015
|Version 1509 (Build 6001.1034)
|Version 1509 (Build 6001.1034)
|Not applicable
| +|October 5, 2015
|Version 1509 (Build 4229.1029)
|Version 1509 (Build 4229.1029)
|Not applicable
| +|September 22, 2015
|Version 1509 (Build 4229.1024)
|Version 1509 (Build 4229.1024)
|Not applicable
| + + +### Version and build information, organized by version + + +The following table provides a list of the version and build numbers for each update channel release. The table is ordered by version, with the most recent version listed first. Within a version, the most recent build is listed first. The date of the release is listed in parentheses. To see this information organized by release date, refer to the table that precedes this one. The build number in bold text indicates the most current build number for that particular channel. + + + + +**By version** + + +|**Version**|**Current Channel**|**First Release for Deferred Channel**|**Deferred Channel**| +|:-----|:-----|:-----|:-----| +|1707
|**8326.2070 (August 7, 2017)**
8326.2062 (July 31, 2017)
8326.2059 (July 28, 2017)
8326.2058 (July 27, 2017)
|Not applicable
|Not applicable
| +|1706
| 8229.2103 (July 19, 2017)
8229.2086 (July 13, 2017)
8229.2073 (June 28, 2017)
|Not applicable
|Not applicable
| +|1705
| 8201.2102 (June 13, 2017)
8201.2075 (June 7, 2017)
|**8201.2171 (August 8, 2017)**
8201.2158 (July 27, 2017)
8201.2136 (July 13, 2017)
8201.2102 (June 13, 2017)
|Scheduled for September 12, 2017
| +|1704
| 8067.2157 (June 1, 2017)
8067.2115 (May 18, 2017)
|Not applicable
|Not applicable
| +|1703
| 7967.2161 (May 9, 2017)
7967.2139 (April 21, 2017)
|Not applicable
|Not applicable
| +|1702
| 7870.2038 (April 11, 2017)
7870.2031 (March 27, 2017)
7870.2024 (March 14, 2017)
7870.2020 (March 9, 2017)
|Not applicable
|Not applicable
| +|1701
| 7766.2060 (February 23, 2017)
| 7766.2084 (May 9, 2017)
7766.2076 (April 11, 2017)
7766.2071 (March 14, 2017)
7766.2060 (February 22, 2017)
|**7766.2099 (July 27, 2017)**
7766.2096 (July 13, 2017)
7766.2092 (June 13, 2017)
| +|1612
| 7668.2074 (January 31, 2017)
7668.2066 (January 25, 2017)
|Not applicable
|Not applicable
| +|1611
| 7571.2109 (January 4, 2017)
7571.2075 (December 13, 2016)
7571.2072 (December 6, 2016)
|Not applicable
|Not applicable
| +|1610
| 7466.2038 (November 10, 2016)
|Not applicable
|Not applicable
| +|1609
| 7369.2055 (November 8, 2016)
7369.2054 (November 2, 2016)
7369.2038 (October 11, 2016)
7369.2024 (October 4, 2016)
| 7369.2102 (January 10, 2017)
7369.2095 (December 13, 2016)
7369.2055 (November 8, 2016)
7369.2054 (November 2, 2016)
7369.2038 (October 11, 2016)
| 7369.2154 (July 27, 2017)
7369.2151 (July 13, 2017)
7369.2139 (June 13, 2017)
7369.2130 (May 9, 2017)
7369.2127 (April 11, 2017)
7369.2120 (March 14, 2017)
7369.2118 (February 22, 2017)
| +|1608
| 7341.2035 (September 26, 2016)
7341.2032 (September 21, 2016)
|Not applicable
|Not applicable
| +|1607
| 7167.2060 (September 13, 2016)
7167.2055 (September 6, 2016)
7167.2047 (August 31, 2016)
7167.2040 (August 16, 2016)
|Not applicable
|Not applicable
| +|1606
| 7070.2036 (August 9, 2016)
7070.2033 (July 26, 2016)
7070.2028 (July 20, 2016)
7070.2026 (July 12, 2016)
7070.2022 (July 5, 2016)
|Not applicable
|Not applicable
| +|1605
| 6965.2063 (June 30, 2016)
6965.2058 (June 14, 2016)
6965.2053 (June 6, 2016)
| 6965.2084 (September 13, 2016)
6965.2076 (August 9, 2016)
6965.2069 (July 21, 2016)
6965.2066 (July 12, 2016)
6965.2063 (June 30, 2016)
6965.2058 (June 14, 2016)
| 6965.2150 (May 9, 2017)
6965.2145 (April 11, 2017)
6965.2140 (March 14, 2017)
6965.2136 (February 22, 2017)
6965.2117 (January 10, 2017)
6965.2115 (December 13, 2016)
6965.2105 (November 8, 2016)
6965.2092 (October 11, 2016)
| +|1604
| 6868.2067 (May 23, 2016)
6868.2062 (May 10, 2016)
6868.2060 (May 4, 2016)
|Not applicable
|Not applicable
| +|1603
| 6769.2040 (April 28, 2016)
6769.2017 (April 12, 2016)
6769.2015 (April 4, 2016)
|Not applicable
|Not applicable
| +|1602
| 6741.2021 (March 24, 2016)
6741.2017 (March 17, 2016)
| 6741.2047 (June 7, 2016)
6741.2042 (May 23, 2016)
6741.2037 (May 10, 2016)
6741.2033 (May 3, 2016)
6741.2026 (April 12, 2016)
6741.2025 (April 4, 2016)
6741.2021 (March 23, 2016)
6741.2017 (March 16, 2016)
6741.2015 (March 14, 2016)
6741.2014 (March 8, 2016)
| 6741.2105 (January 10, 2017)
6741.2098 (December 13, 2016)
6741.2088 (November 8, 2016)
6741.2081 (October 11, 2016)
6741.2071 (September 13, 2016)
6741.2063 (August 9, 2016)
6741.2056 (July 12, 2016)
6741.2048 (June 14, 2016)
| +|1601
| 6568.2036 (March 4, 2016)
6568.2034 (March 3, 2016)
6568.2025 (February 16, 2016)
|Not applicable
|Not applicable
| +|1511
| 6366.2068 (February 9, 2016)
6366.2062 (January 25, 2016)
6366.2056 (January 12, 2016)
6366.2036 (December 11, 2015)
|Not applicable
|Not applicable
| +|1509
| 6001.1043 (December 8, 2015)
6001.1038 (November 10, 2015)
6001.1034 (October 21, 2015)
4229.1029 (October 5, 2015)
4229.1024 (September 22, 2015)
| 6001.1061 (February 9, 2016)
6001.1054 (January 12, 2016)
6001.1043 (December 8, 2015)
6001.1038 (November 10, 2015)
6001.1034 (October 21, 2015)
4229.1029 (October 5, 2015)
4229.1024 (September 22, 2015)
| 6001.1090 (September 13, 2016)
6001.1087 (August 9, 2016)
6001.1085 (July 12, 2016)
6001.1082 (June 14, 2016)
6001.1078 (May 10, 2016)
6001.1073 (April 12, 2016)
6001.1068 (March 8, 2016)
6001.1061 (February 9, 2016)
| + + +## See also + + + +#### Other Resources + + + + + + [Configuration options for the Office 2016 Deployment Tool](configuration-options-for-the-office-2016-deployment-tool.md) + + + + [Download sizes (approximate) for channel updates to Office 365 ProPlus](download-sizes-approximate-for-channel-updates-to-office-365-proplus.md) diff --git a/DeployOffice/what-s-new-deploying-office-365-proplus-in-the-enterprise.md b/DeployOffice/what-s-new-deploying-office-365-proplus-in-the-enterprise.md new file mode 100644 index 000000000..741dfcb4f --- /dev/null +++ b/DeployOffice/what-s-new-deploying-office-365-proplus-in-the-enterprise.md @@ -0,0 +1,73 @@ +--- +title: What's new Deploying Office 365 ProPlus in the enterprise +ms.prod: OFFICE365 +ms.assetid: e270bbe0-5156-4587-871b-7b923b199743 +--- + + +# What's new: Deploying Office 365 ProPlus in the enterprise + +We continue to add new features and capabilities to help you deploy and manage Office 365 ProPlus in your organizations. The following is an overview of these changes, with the most recent changes listed first. + + + + + +## Use a new version of the Office Deployment Tool to manage Office 365 ProPlus deployments + +In order to support new deployment capabilities available for the Office 2016 version of Office 365 ProPlus, there is a new version of the Office Deployment Tool. You can [download this new version](http://go.microsoft.com/fwlink/p/?LinkID=626065) from the Microsoft Download Center. The configuration.xml file used by the latest Office Deployment Tool supports new settings that allow you to configure update channels and install language accessory packs. + + + +Also, be aware that the new version of the Office Deployment Tool can't be used to deploy the Office 2013 version of Office 365 ProPlus. You can continue to [use the previous version of the Office Deployment Tool](http://www.microsoft.com/download/details.aspx?id=36778) for those deployments. + + + + +## Use new Group Policy settings for Office 365 ProPlus + +For the release of Office 2016, there is a new set of Administrative Template files (ADMX/ADML) for Group Policy settings. You can [download the Administrative Template files](https://www.microsoft.com/download/details.aspx?id=49030) from the Microsoft Download Center. Included in the download is an Excel file that contains a list of all the Group Policy settings as well as a list of the new policy settings for Office 2016. + + + + +## Determine how often to update to new features of Office 365 ProPlus by selecting an update channel + + +In Office 2016, you can control how fast your users receive feature updates to Office 365 ProPlus. One choice is a monthly update to Office 365 ProPlus, which can contain new or updated features, bug fixes, and security patches. This is called the Current Channel release. + + + +If you prefer, you have the option to receive only security updates for Office 365 ProPlus each month, and instead defer for several months receiving any features changes and bug fixes. A few times a year, we'll provide an update to Office 365 ProPlus for you to test and deploy that contains those feature changes and bug fixes. This is called the Deferred Channel release. + + + +For more information, see [Overview of update channels for Office 365 ProPlus](overview-of-update-channels-for-office-365-proplus.md). + + + + +## View and manage users' installations of Office 365 ProPlus from the Office 365 admin center + + +Previously, only users could use the Office 365 portal to view a list of which computers they had installed Office 365 ProPlus on and deactivate an installation. Now, if you're a global admin or a user management administrator in Office 365, you can view which computers your users have installed Office 365 ProPlus on. Also, you can deactivate a user's installation of Office 365 ProPlus. To do this, go to the **Active Users** section of the Office 365 admin center, and then [follow these steps](https://blogs.technet.com/b/odsupport/archive/2015/06/22/office-365-proplus-user-activations-management.aspx). + + + +In addition to Office 365 ProPlus installations, you can also view and manage installations of Visio Pro for Office 365, Project Professional 2010, and Office 2016 for Mac. + + + + +## Related Topics + + + [Configure updates of Office 365 ProPlus to prepare for the upgrade to the Office 2016 version](configure-updates-of-office-365-proplus-to-prepare-for-the-upgrade-to-the-office.md) + + + + [What's New and Improved in Office 2016](https://support.office.com/article/95c8d81d-08ba-42c1-914f-bca4603e1426) + + + + diff --git a/LICENSE b/LICENSE index e056e7c3e..abe99dbee 100644 --- a/LICENSE +++ b/LICENSE @@ -1,395 +1,395 @@ -Attribution 4.0 International - -======================================================================= - -Creative Commons Corporation ("Creative Commons") is not a law firm and -does not provide legal services or legal advice. Distribution of -Creative Commons public licenses does not create a lawyer-client or -other relationship. Creative Commons makes its licenses and related -information available on an "as-is" basis. Creative Commons gives no -warranties regarding its licenses, any material licensed under their -terms and conditions, or any related information. Creative Commons -disclaims all liability for damages resulting from their use to the -fullest extent possible. - -Using Creative Commons Public Licenses - -Creative Commons public licenses provide a standard set of terms and -conditions that creators and other rights holders may use to share -original works of authorship and other material subject to copyright -and certain other rights specified in the public license below. The -following considerations are for informational purposes only, are not -exhaustive, and do not form part of our licenses. - - Considerations for licensors: Our public licenses are - intended for use by those authorized to give the public - permission to use material in ways otherwise restricted by - copyright and certain other rights. Our licenses are - irrevocable. Licensors should read and understand the terms - and conditions of the license they choose before applying it. - Licensors should also secure all rights necessary before - applying our licenses so that the public can reuse the - material as expected. Licensors should clearly mark any - material not subject to the license. This includes other CC- - licensed material, or material used under an exception or - limitation to copyright. More considerations for licensors: - wiki.creativecommons.org/Considerations_for_licensors - - Considerations for the public: By using one of our public - licenses, a licensor grants the public permission to use the - licensed material under specified terms and conditions. If - the licensor's permission is not necessary for any reason--for - example, because of any applicable exception or limitation to - copyright--then that use is not regulated by the license. Our - licenses grant only permissions under copyright and certain - other rights that a licensor has authority to grant. Use of - the licensed material may still be restricted for other - reasons, including because others have copyright or other - rights in the material. A licensor may make special requests, - such as asking that all changes be marked or described. - Although not required by our licenses, you are encouraged to - respect those requests where reasonable. More_considerations - for the public: - wiki.creativecommons.org/Considerations_for_licensees - -======================================================================= - -Creative Commons Attribution 4.0 International Public License - -By exercising the Licensed Rights (defined below), You accept and agree -to be bound by the terms and conditions of this Creative Commons -Attribution 4.0 International Public License ("Public License"). To the -extent this Public License may be interpreted as a contract, You are -granted the Licensed Rights in consideration of Your acceptance of -these terms and conditions, and the Licensor grants You such rights in -consideration of benefits the Licensor receives from making the -Licensed Material available under these terms and conditions. - - -Section 1 -- Definitions. - - a. Adapted Material means material subject to Copyright and Similar - Rights that is derived from or based upon the Licensed Material - and in which the Licensed Material is translated, altered, - arranged, transformed, or otherwise modified in a manner requiring - permission under the Copyright and Similar Rights held by the - Licensor. For purposes of this Public License, where the Licensed - Material is a musical work, performance, or sound recording, - Adapted Material is always produced where the Licensed Material is - synched in timed relation with a moving image. - - b. Adapter's License means the license You apply to Your Copyright - and Similar Rights in Your contributions to Adapted Material in - accordance with the terms and conditions of this Public License. - - c. Copyright and Similar Rights means copyright and/or similar rights - closely related to copyright including, without limitation, - performance, broadcast, sound recording, and Sui Generis Database - Rights, without regard to how the rights are labeled or - categorized. For purposes of this Public License, the rights - specified in Section 2(b)(1)-(2) are not Copyright and Similar - Rights. - - d. Effective Technological Measures means those measures that, in the - absence of proper authority, may not be circumvented under laws - fulfilling obligations under Article 11 of the WIPO Copyright - Treaty adopted on December 20, 1996, and/or similar international - agreements. - - e. Exceptions and Limitations means fair use, fair dealing, and/or - any other exception or limitation to Copyright and Similar Rights - that applies to Your use of the Licensed Material. - - f. Licensed Material means the artistic or literary work, database, - or other material to which the Licensor applied this Public - License. - - g. Licensed Rights means the rights granted to You subject to the - terms and conditions of this Public License, which are limited to - all Copyright and Similar Rights that apply to Your use of the - Licensed Material and that the Licensor has authority to license. - - h. Licensor means the individual(s) or entity(ies) granting rights - under this Public License. - - i. Share means to provide material to the public by any means or - process that requires permission under the Licensed Rights, such - as reproduction, public display, public performance, distribution, - dissemination, communication, or importation, and to make material - available to the public including in ways that members of the - public may access the material from a place and at a time - individually chosen by them. - - j. Sui Generis Database Rights means rights other than copyright - resulting from Directive 96/9/EC of the European Parliament and of - the Council of 11 March 1996 on the legal protection of databases, - as amended and/or succeeded, as well as other essentially - equivalent rights anywhere in the world. - - k. You means the individual or entity exercising the Licensed Rights - under this Public License. Your has a corresponding meaning. - - -Section 2 -- Scope. - - a. License grant. - - 1. Subject to the terms and conditions of this Public License, - the Licensor hereby grants You a worldwide, royalty-free, - non-sublicensable, non-exclusive, irrevocable license to - exercise the Licensed Rights in the Licensed Material to: - - a. reproduce and Share the Licensed Material, in whole or - in part; and - - b. produce, reproduce, and Share Adapted Material. - - 2. Exceptions and Limitations. For the avoidance of doubt, where - Exceptions and Limitations apply to Your use, this Public - License does not apply, and You do not need to comply with - its terms and conditions. - - 3. Term. The term of this Public License is specified in Section - 6(a). - - 4. Media and formats; technical modifications allowed. The - Licensor authorizes You to exercise the Licensed Rights in - all media and formats whether now known or hereafter created, - and to make technical modifications necessary to do so. The - Licensor waives and/or agrees not to assert any right or - authority to forbid You from making technical modifications - necessary to exercise the Licensed Rights, including - technical modifications necessary to circumvent Effective - Technological Measures. For purposes of this Public License, - simply making modifications authorized by this Section 2(a) - (4) never produces Adapted Material. - - 5. Downstream recipients. - - a. Offer from the Licensor -- Licensed Material. Every - recipient of the Licensed Material automatically - receives an offer from the Licensor to exercise the - Licensed Rights under the terms and conditions of this - Public License. - - b. No downstream restrictions. You may not offer or impose - any additional or different terms or conditions on, or - apply any Effective Technological Measures to, the - Licensed Material if doing so restricts exercise of the - Licensed Rights by any recipient of the Licensed - Material. - - 6. No endorsement. Nothing in this Public License constitutes or - may be construed as permission to assert or imply that You - are, or that Your use of the Licensed Material is, connected - with, or sponsored, endorsed, or granted official status by, - the Licensor or others designated to receive attribution as - provided in Section 3(a)(1)(A)(i). - - b. Other rights. - - 1. Moral rights, such as the right of integrity, are not - licensed under this Public License, nor are publicity, - privacy, and/or other similar personality rights; however, to - the extent possible, the Licensor waives and/or agrees not to - assert any such rights held by the Licensor to the limited - extent necessary to allow You to exercise the Licensed - Rights, but not otherwise. - - 2. Patent and trademark rights are not licensed under this - Public License. - - 3. To the extent possible, the Licensor waives any right to - collect royalties from You for the exercise of the Licensed - Rights, whether directly or through a collecting society - under any voluntary or waivable statutory or compulsory - licensing scheme. In all other cases the Licensor expressly - reserves any right to collect such royalties. - - -Section 3 -- License Conditions. - -Your exercise of the Licensed Rights is expressly made subject to the -following conditions. - - a. Attribution. - - 1. If You Share the Licensed Material (including in modified - form), You must: - - a. retain the following if it is supplied by the Licensor - with the Licensed Material: - - i. identification of the creator(s) of the Licensed - Material and any others designated to receive - attribution, in any reasonable manner requested by - the Licensor (including by pseudonym if - designated); - - ii. a copyright notice; - - iii. a notice that refers to this Public License; - - iv. a notice that refers to the disclaimer of - warranties; - - v. a URI or hyperlink to the Licensed Material to the - extent reasonably practicable; - - b. indicate if You modified the Licensed Material and - retain an indication of any previous modifications; and - - c. indicate the Licensed Material is licensed under this - Public License, and include the text of, or the URI or - hyperlink to, this Public License. - - 2. You may satisfy the conditions in Section 3(a)(1) in any - reasonable manner based on the medium, means, and context in - which You Share the Licensed Material. For example, it may be - reasonable to satisfy the conditions by providing a URI or - hyperlink to a resource that includes the required - information. - - 3. If requested by the Licensor, You must remove any of the - information required by Section 3(a)(1)(A) to the extent - reasonably practicable. - - 4. If You Share Adapted Material You produce, the Adapter's - License You apply must not prevent recipients of the Adapted - Material from complying with this Public License. - - -Section 4 -- Sui Generis Database Rights. - -Where the Licensed Rights include Sui Generis Database Rights that -apply to Your use of the Licensed Material: - - a. for the avoidance of doubt, Section 2(a)(1) grants You the right - to extract, reuse, reproduce, and Share all or a substantial - portion of the contents of the database; - - b. if You include all or a substantial portion of the database - contents in a database in which You have Sui Generis Database - Rights, then the database in which You have Sui Generis Database - Rights (but not its individual contents) is Adapted Material; and - - c. You must comply with the conditions in Section 3(a) if You Share - all or a substantial portion of the contents of the database. - -For the avoidance of doubt, this Section 4 supplements and does not -replace Your obligations under this Public License where the Licensed -Rights include other Copyright and Similar Rights. - - -Section 5 -- Disclaimer of Warranties and Limitation of Liability. - - a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE - EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS - AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF - ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, - IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, - WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR - PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, - ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT - KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT - ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. - - b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE - TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, - NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, - INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, - COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR - USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN - ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR - DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR - IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. - - c. The disclaimer of warranties and limitation of liability provided - above shall be interpreted in a manner that, to the extent - possible, most closely approximates an absolute disclaimer and - waiver of all liability. - - -Section 6 -- Term and Termination. - - a. This Public License applies for the term of the Copyright and - Similar Rights licensed here. However, if You fail to comply with - this Public License, then Your rights under this Public License - terminate automatically. - - b. Where Your right to use the Licensed Material has terminated under - Section 6(a), it reinstates: - - 1. automatically as of the date the violation is cured, provided - it is cured within 30 days of Your discovery of the - violation; or - - 2. upon express reinstatement by the Licensor. - - For the avoidance of doubt, this Section 6(b) does not affect any - right the Licensor may have to seek remedies for Your violations - of this Public License. - - c. For the avoidance of doubt, the Licensor may also offer the - Licensed Material under separate terms or conditions or stop - distributing the Licensed Material at any time; however, doing so - will not terminate this Public License. - - d. Sections 1, 5, 6, 7, and 8 survive termination of this Public - License. - - -Section 7 -- Other Terms and Conditions. - - a. The Licensor shall not be bound by any additional or different - terms or conditions communicated by You unless expressly agreed. - - b. Any arrangements, understandings, or agreements regarding the - Licensed Material not stated herein are separate from and - independent of the terms and conditions of this Public License. - - -Section 8 -- Interpretation. - - a. For the avoidance of doubt, this Public License does not, and - shall not be interpreted to, reduce, limit, restrict, or impose - conditions on any use of the Licensed Material that could lawfully - be made without permission under this Public License. - - b. To the extent possible, if any provision of this Public License is - deemed unenforceable, it shall be automatically reformed to the - minimum extent necessary to make it enforceable. If the provision - cannot be reformed, it shall be severed from this Public License - without affecting the enforceability of the remaining terms and - conditions. - - c. No term or condition of this Public License will be waived and no - failure to comply consented to unless expressly agreed to by the - Licensor. - - d. Nothing in this Public License constitutes or may be interpreted - as a limitation upon, or waiver of, any privileges and immunities - that apply to the Licensor or You, including from the legal - processes of any jurisdiction or authority. - - -======================================================================= - -Creative Commons is not a party to its public -licenses. Notwithstanding, Creative Commons may elect to apply one of -its public licenses to material it publishes and in those instances -will be considered the “Licensor.” The text of the Creative Commons -public licenses is dedicated to the public domain under the CC0 Public -Domain Dedication. Except for the limited purpose of indicating that -material is shared under a Creative Commons public license or as -otherwise permitted by the Creative Commons policies published at -creativecommons.org/policies, Creative Commons does not authorize the -use of the trademark "Creative Commons" or any other trademark or logo -of Creative Commons without its prior written consent including, -without limitation, in connection with any unauthorized modifications -to any of its public licenses or any other arrangements, -understandings, or agreements concerning use of licensed material. For -the avoidance of doubt, this paragraph does not form part of the -public licenses. - +Attribution 4.0 International + +======================================================================= + +Creative Commons Corporation ("Creative Commons") is not a law firm and +does not provide legal services or legal advice. Distribution of +Creative Commons public licenses does not create a lawyer-client or +other relationship. Creative Commons makes its licenses and related +information available on an "as-is" basis. Creative Commons gives no +warranties regarding its licenses, any material licensed under their +terms and conditions, or any related information. Creative Commons +disclaims all liability for damages resulting from their use to the +fullest extent possible. + +Using Creative Commons Public Licenses + +Creative Commons public licenses provide a standard set of terms and +conditions that creators and other rights holders may use to share +original works of authorship and other material subject to copyright +and certain other rights specified in the public license below. The +following considerations are for informational purposes only, are not +exhaustive, and do not form part of our licenses. + + Considerations for licensors: Our public licenses are + intended for use by those authorized to give the public + permission to use material in ways otherwise restricted by + copyright and certain other rights. Our licenses are + irrevocable. Licensors should read and understand the terms + and conditions of the license they choose before applying it. + Licensors should also secure all rights necessary before + applying our licenses so that the public can reuse the + material as expected. Licensors should clearly mark any + material not subject to the license. This includes other CC- + licensed material, or material used under an exception or + limitation to copyright. More considerations for licensors: + wiki.creativecommons.org/Considerations_for_licensors + + Considerations for the public: By using one of our public + licenses, a licensor grants the public permission to use the + licensed material under specified terms and conditions. If + the licensor's permission is not necessary for any reason--for + example, because of any applicable exception or limitation to + copyright--then that use is not regulated by the license. Our + licenses grant only permissions under copyright and certain + other rights that a licensor has authority to grant. Use of + the licensed material may still be restricted for other + reasons, including because others have copyright or other + rights in the material. A licensor may make special requests, + such as asking that all changes be marked or described. + Although not required by our licenses, you are encouraged to + respect those requests where reasonable. More_considerations + for the public: + wiki.creativecommons.org/Considerations_for_licensees + +======================================================================= + +Creative Commons Attribution 4.0 International Public License + +By exercising the Licensed Rights (defined below), You accept and agree +to be bound by the terms and conditions of this Creative Commons +Attribution 4.0 International Public License ("Public License"). To the +extent this Public License may be interpreted as a contract, You are +granted the Licensed Rights in consideration of Your acceptance of +these terms and conditions, and the Licensor grants You such rights in +consideration of benefits the Licensor receives from making the +Licensed Material available under these terms and conditions. + + +Section 1 -- Definitions. + + a. Adapted Material means material subject to Copyright and Similar + Rights that is derived from or based upon the Licensed Material + and in which the Licensed Material is translated, altered, + arranged, transformed, or otherwise modified in a manner requiring + permission under the Copyright and Similar Rights held by the + Licensor. For purposes of this Public License, where the Licensed + Material is a musical work, performance, or sound recording, + Adapted Material is always produced where the Licensed Material is + synched in timed relation with a moving image. + + b. Adapter's License means the license You apply to Your Copyright + and Similar Rights in Your contributions to Adapted Material in + accordance with the terms and conditions of this Public License. + + c. Copyright and Similar Rights means copyright and/or similar rights + closely related to copyright including, without limitation, + performance, broadcast, sound recording, and Sui Generis Database + Rights, without regard to how the rights are labeled or + categorized. For purposes of this Public License, the rights + specified in Section 2(b)(1)-(2) are not Copyright and Similar + Rights. + + d. Effective Technological Measures means those measures that, in the + absence of proper authority, may not be circumvented under laws + fulfilling obligations under Article 11 of the WIPO Copyright + Treaty adopted on December 20, 1996, and/or similar international + agreements. + + e. Exceptions and Limitations means fair use, fair dealing, and/or + any other exception or limitation to Copyright and Similar Rights + that applies to Your use of the Licensed Material. + + f. Licensed Material means the artistic or literary work, database, + or other material to which the Licensor applied this Public + License. + + g. Licensed Rights means the rights granted to You subject to the + terms and conditions of this Public License, which are limited to + all Copyright and Similar Rights that apply to Your use of the + Licensed Material and that the Licensor has authority to license. + + h. Licensor means the individual(s) or entity(ies) granting rights + under this Public License. + + i. Share means to provide material to the public by any means or + process that requires permission under the Licensed Rights, such + as reproduction, public display, public performance, distribution, + dissemination, communication, or importation, and to make material + available to the public including in ways that members of the + public may access the material from a place and at a time + individually chosen by them. + + j. Sui Generis Database Rights means rights other than copyright + resulting from Directive 96/9/EC of the European Parliament and of + the Council of 11 March 1996 on the legal protection of databases, + as amended and/or succeeded, as well as other essentially + equivalent rights anywhere in the world. + + k. You means the individual or entity exercising the Licensed Rights + under this Public License. Your has a corresponding meaning. + + +Section 2 -- Scope. + + a. License grant. + + 1. Subject to the terms and conditions of this Public License, + the Licensor hereby grants You a worldwide, royalty-free, + non-sublicensable, non-exclusive, irrevocable license to + exercise the Licensed Rights in the Licensed Material to: + + a. reproduce and Share the Licensed Material, in whole or + in part; and + + b. produce, reproduce, and Share Adapted Material. + + 2. Exceptions and Limitations. For the avoidance of doubt, where + Exceptions and Limitations apply to Your use, this Public + License does not apply, and You do not need to comply with + its terms and conditions. + + 3. Term. The term of this Public License is specified in Section + 6(a). + + 4. Media and formats; technical modifications allowed. The + Licensor authorizes You to exercise the Licensed Rights in + all media and formats whether now known or hereafter created, + and to make technical modifications necessary to do so. The + Licensor waives and/or agrees not to assert any right or + authority to forbid You from making technical modifications + necessary to exercise the Licensed Rights, including + technical modifications necessary to circumvent Effective + Technological Measures. For purposes of this Public License, + simply making modifications authorized by this Section 2(a) + (4) never produces Adapted Material. + + 5. Downstream recipients. + + a. Offer from the Licensor -- Licensed Material. Every + recipient of the Licensed Material automatically + receives an offer from the Licensor to exercise the + Licensed Rights under the terms and conditions of this + Public License. + + b. No downstream restrictions. You may not offer or impose + any additional or different terms or conditions on, or + apply any Effective Technological Measures to, the + Licensed Material if doing so restricts exercise of the + Licensed Rights by any recipient of the Licensed + Material. + + 6. No endorsement. Nothing in this Public License constitutes or + may be construed as permission to assert or imply that You + are, or that Your use of the Licensed Material is, connected + with, or sponsored, endorsed, or granted official status by, + the Licensor or others designated to receive attribution as + provided in Section 3(a)(1)(A)(i). + + b. Other rights. + + 1. Moral rights, such as the right of integrity, are not + licensed under this Public License, nor are publicity, + privacy, and/or other similar personality rights; however, to + the extent possible, the Licensor waives and/or agrees not to + assert any such rights held by the Licensor to the limited + extent necessary to allow You to exercise the Licensed + Rights, but not otherwise. + + 2. Patent and trademark rights are not licensed under this + Public License. + + 3. To the extent possible, the Licensor waives any right to + collect royalties from You for the exercise of the Licensed + Rights, whether directly or through a collecting society + under any voluntary or waivable statutory or compulsory + licensing scheme. In all other cases the Licensor expressly + reserves any right to collect such royalties. + + +Section 3 -- License Conditions. + +Your exercise of the Licensed Rights is expressly made subject to the +following conditions. + + a. Attribution. + + 1. If You Share the Licensed Material (including in modified + form), You must: + + a. retain the following if it is supplied by the Licensor + with the Licensed Material: + + i. identification of the creator(s) of the Licensed + Material and any others designated to receive + attribution, in any reasonable manner requested by + the Licensor (including by pseudonym if + designated); + + ii. a copyright notice; + + iii. a notice that refers to this Public License; + + iv. a notice that refers to the disclaimer of + warranties; + + v. a URI or hyperlink to the Licensed Material to the + extent reasonably practicable; + + b. indicate if You modified the Licensed Material and + retain an indication of any previous modifications; and + + c. indicate the Licensed Material is licensed under this + Public License, and include the text of, or the URI or + hyperlink to, this Public License. + + 2. You may satisfy the conditions in Section 3(a)(1) in any + reasonable manner based on the medium, means, and context in + which You Share the Licensed Material. For example, it may be + reasonable to satisfy the conditions by providing a URI or + hyperlink to a resource that includes the required + information. + + 3. If requested by the Licensor, You must remove any of the + information required by Section 3(a)(1)(A) to the extent + reasonably practicable. + + 4. If You Share Adapted Material You produce, the Adapter's + License You apply must not prevent recipients of the Adapted + Material from complying with this Public License. + + +Section 4 -- Sui Generis Database Rights. + +Where the Licensed Rights include Sui Generis Database Rights that +apply to Your use of the Licensed Material: + + a. for the avoidance of doubt, Section 2(a)(1) grants You the right + to extract, reuse, reproduce, and Share all or a substantial + portion of the contents of the database; + + b. if You include all or a substantial portion of the database + contents in a database in which You have Sui Generis Database + Rights, then the database in which You have Sui Generis Database + Rights (but not its individual contents) is Adapted Material; and + + c. You must comply with the conditions in Section 3(a) if You Share + all or a substantial portion of the contents of the database. + +For the avoidance of doubt, this Section 4 supplements and does not +replace Your obligations under this Public License where the Licensed +Rights include other Copyright and Similar Rights. + + +Section 5 -- Disclaimer of Warranties and Limitation of Liability. + + a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE + EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS + AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF + ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS, + IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION, + WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR + PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS, + ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT + KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT + ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU. + + b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE + TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION, + NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT, + INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES, + COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR + USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN + ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR + DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR + IN PART, THIS LIMITATION MAY NOT APPLY TO YOU. + + c. The disclaimer of warranties and limitation of liability provided + above shall be interpreted in a manner that, to the extent + possible, most closely approximates an absolute disclaimer and + waiver of all liability. + + +Section 6 -- Term and Termination. + + a. This Public License applies for the term of the Copyright and + Similar Rights licensed here. However, if You fail to comply with + this Public License, then Your rights under this Public License + terminate automatically. + + b. Where Your right to use the Licensed Material has terminated under + Section 6(a), it reinstates: + + 1. automatically as of the date the violation is cured, provided + it is cured within 30 days of Your discovery of the + violation; or + + 2. upon express reinstatement by the Licensor. + + For the avoidance of doubt, this Section 6(b) does not affect any + right the Licensor may have to seek remedies for Your violations + of this Public License. + + c. For the avoidance of doubt, the Licensor may also offer the + Licensed Material under separate terms or conditions or stop + distributing the Licensed Material at any time; however, doing so + will not terminate this Public License. + + d. Sections 1, 5, 6, 7, and 8 survive termination of this Public + License. + + +Section 7 -- Other Terms and Conditions. + + a. The Licensor shall not be bound by any additional or different + terms or conditions communicated by You unless expressly agreed. + + b. Any arrangements, understandings, or agreements regarding the + Licensed Material not stated herein are separate from and + independent of the terms and conditions of this Public License. + + +Section 8 -- Interpretation. + + a. For the avoidance of doubt, this Public License does not, and + shall not be interpreted to, reduce, limit, restrict, or impose + conditions on any use of the Licensed Material that could lawfully + be made without permission under this Public License. + + b. To the extent possible, if any provision of this Public License is + deemed unenforceable, it shall be automatically reformed to the + minimum extent necessary to make it enforceable. If the provision + cannot be reformed, it shall be severed from this Public License + without affecting the enforceability of the remaining terms and + conditions. + + c. No term or condition of this Public License will be waived and no + failure to comply consented to unless expressly agreed to by the + Licensor. + + d. Nothing in this Public License constitutes or may be interpreted + as a limitation upon, or waiver of, any privileges and immunities + that apply to the Licensor or You, including from the legal + processes of any jurisdiction or authority. + + +======================================================================= + +Creative Commons is not a party to its public +licenses. Notwithstanding, Creative Commons may elect to apply one of +its public licenses to material it publishes and in those instances +will be considered the “Licensor.” The text of the Creative Commons +public licenses is dedicated to the public domain under the CC0 Public +Domain Dedication. Except for the limited purpose of indicating that +material is shared under a Creative Commons public license or as +otherwise permitted by the Creative Commons policies published at +creativecommons.org/policies, Creative Commons does not authorize the +use of the trademark "Creative Commons" or any other trademark or logo +of Creative Commons without its prior written consent including, +without limitation, in connection with any unauthorized modifications +to any of its public licenses or any other arrangements, +understandings, or agreements concerning use of licensed material. For +the avoidance of doubt, this paragraph does not form part of the +public licenses. + Creative Commons may be contacted at creativecommons.org. \ No newline at end of file diff --git a/LICENSE-CODE b/LICENSE-CODE index b17b032a4..5c9653fad 100644 --- a/LICENSE-CODE +++ b/LICENSE-CODE @@ -1,17 +1,17 @@ -The MIT License (MIT) -Copyright (c) Microsoft Corporation - -Permission is hereby granted, free of charge, to any person obtaining a copy of this software and -associated documentation files (the "Software"), to deal in the Software without restriction, -including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, -and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, -subject to the following conditions: - -The above copyright notice and this permission notice shall be included in all copies or substantial -portions of the Software. - -THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT -NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. -IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, -WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE +The MIT License (MIT) +Copyright (c) Microsoft Corporation + +Permission is hereby granted, free of charge, to any person obtaining a copy of this software and +associated documentation files (the "Software"), to deal in the Software without restriction, +including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, +and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, +subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all copies or substantial +portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT +NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. +IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, +WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. \ No newline at end of file diff --git a/README.md b/README.md index 824a7c6d5..ec8a825db 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,3 @@ -## Microsoft Open Source Code of Conduct -This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). +## Microsoft Open Source Code of Conduct +This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. \ No newline at end of file diff --git a/ThirdPartyNotices b/ThirdPartyNotices index a0bd09d68..02439e89c 100644 --- a/ThirdPartyNotices +++ b/ThirdPartyNotices @@ -1,15 +1,15 @@ -##Legal Notices -Microsoft and any contributors grant you a license to the Microsoft documentation and other content -in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), -see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the -[LICENSE-CODE](LICENSE-CODE) file. - -Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation -may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. -The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. -Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653. - -Privacy information can be found at https://privacy.microsoft.com/en-us/ - -Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, +##Legal Notices +Microsoft and any contributors grant you a license to the Microsoft documentation and other content +in this repository under the [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode), +see the [LICENSE](LICENSE) file, and grant you a license to any code in the repository under the [MIT License](https://opensource.org/licenses/MIT), see the +[LICENSE-CODE](LICENSE-CODE) file. + +Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation +may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. +The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. +Microsoft's general trademark guidelines can be found at http://go.microsoft.com/fwlink/?LinkID=254653. + +Privacy information can be found at https://privacy.microsoft.com/en-us/ + +Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise. \ No newline at end of file