Implementar aplicaciones de Microsoft 365 desde un origen local

Sigue los pasos de este artículo para implementar Aplicaciones de Microsoft 365 en equipos cliente desde una carpeta compartida en la red con la Herramienta de implementación de Office (ODT).

Antes de empezar

Make sure your users have local admin privileges on their client devices. If that is not the case, then you should use your organization's standard deployment tools and processes to install Office.

Si aún no lo ha hecho, complete las fases de valoración y planificación para la implementación de Office.

This 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 Microsoft 365 or Office 2021 on a PC or Mac or Use the Office offline installer.

Procedimientos recomendados

Los pasos de este artículo se basan en los siguientes procedimientos recomendados, si ha elegido implementar el canal empresarial semestral:

  • Manage updates to Office automatically, without any administrative overhead. For more details, see Choose how to manage updates. (If you want to manage updates from a local source, you need to change the configuration files. For more details, see configuring updates).
  • Build two Office installation packages: One package uses Semi-Annual Enterprise Channel for 64-bit and the other uses Semi-Annual Enterprise Channel (Preview) for 64-bit. Each installation package includes all the core Office apps. If you want to deploy the 32-bit version of Office instead, you can select that option when creating the installation package. To deploy both versions, you create additional installation packages. For more details, see Define your source files.
  • Deploy to two deployment groups: a pilot group that receives Semi-Annual Enterprise Channel (Preview) and a broad group that receives Semi-Annual Enterprise Channel. For more details, see Choose your update channels.

You can customize these options to match the requirements for your organization, including deploying to more than two groups, changing update channels, and deploying Visio and Project. For more details, see Customize your deployment.

Paso 1: Crear carpetas compartidas para los archivos de instalación de Office

Because you're deploying Microsoft 365 Apps from a local source, you have to create folders to store the Office installation files. You'll create one parent folder and two child folders, one for the pilot group, with the version of Office from Semi-Annual Enterprise Channel (Preview), and one for the broad group, with version of Office from Semi-Annual Enterprise Channel. This structure is similar to the one that the Office Content Delivery Network (CDN) uses.

  1. Cree las carpetas siguientes:

    • \\Server\Share\M365: almacena la Herramienta de implementación de Office y los archivos de configuración que definen cómo se descargará e implementará Office.
    • \\Server\Share\M365\SECP: almacena los archivos de instalación de Aplicaciones de Microsoft 365 del Canal empresarial semestral.
    • \\Server\Share\M365\SEC: almacena los archivos de instalación de Aplicaciones de Microsoft 365 desde el Canal empresarial semestral.

Estas carpetas contendrán todos los archivos de instalación de Office que hay que implementar.

  1. Assign Read permissions for your users. Installing Office from a shared folder requires only that the user have Read permission for that folder, so you should assign Read permission to everyone. For details about how to create shared folders and assign permissions, see Shared Folders

Nota

In this article, 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.

Paso 2: Descargar la Herramienta de implementación de Office

Download the ODT from the Microsoft Download Center to \\Server\Share\M365. If you've already downloaded the ODT, make sure you have the latest version.

Después de descargar el archivo autoextraíble, ejecútelo para extraer el archivo ejecutable de la Herramienta de implementación de Office (setup.exe) y un archivo de configuración de ejemplo (configuration.xml).

Paso 3: Crear un archivo de configuración para el grupo piloto

To download and deploy Microsoft 365 Apps to the pilot group, you use a configuration file with the ODT. To create the configuration file, we recommend using the Office Customization Tool.

  1. Go to Office Customization Tool and configure the desired settings for your Microsoft 365 Apps installation. We recommend the following options:
  • Products: Microsoft 365 Apps. You can also include Visio and Project if you plan to deploy those apps.
  • Canal de actualización: elija Canal empresarial semestral (vista previa) para el paquete de instalación para el grupo piloto.
  • Language: Include all the language packs you plan to deploy. We recommend selecting Match operating system to automatically install the same languages that are in use by the operating system and any user on the client device. We also recommend selecting Fallback to the CDN to use the Office CDN as a backup source for language packs.
  • Installation: Select Local source, and type "\\Server\Share\M365\SECP" for the source path. Office will be downloaded to and then installed from \\server\share\M365\SECP on your network
  • Actualizaciones: para actualizar los dispositivos cliente de forma automática, haga clic en CDN y Comprobar automáticamente si hay actualizaciones.
  • Upgrades: Choose to automatically remove all previous MSI versions of Office. You can also choose to install the same language as any removed MSI versions of Office, but make sure to include those languages in your installation package.
  • Propiedades adicionales: para instalar Office en modo silencioso para los usuarios, elija Desactivado para el Nivel de visualización y Activado para Aceptar los términos de licencia automáticamente.
  • Preferencias de aplicación: defina las opciones de Office que quiera habilitar, incluidas las notificaciones de macros VBA, las ubicaciones de archivo predeterminadas y los formatos de archivo predeterminados.
  1. Cuando haya completado la configuración, haga clic en Exportar en la esquina superior derecha de la página y, después, guarde el archivo como config-pilot-SECP.xml en la carpeta \\Server\Share\M365.

For more details on how to use the Office Customization Tool, see Overview of the Office Customization Tool. For more information about the configuration options, see Configuration options for the Office Deployment Tool.

Note that the Office installation files and Office updates will come from Semi-Annual Enterprise Channel (Preview). For more details on the most recent version of Office based on the different update channels, see Release information for updates to Microsoft 365 Apps.

Paso 4: Crear un archivo de configuración para el grupo general

Con la Herramienta de personalización de Office, cree el archivo de configuración para el grupo general.

  1. Go to Office Customization Tool and configure the desired settings for your Microsoft 365 Apps installation. We recommend matching the same options as the pilot group in Step 3, except for the following changes:
  • Canal de actualización: elija Canal empresarial semestral para el paquete de instalación para el grupo piloto.
  • Installation: Select Local source, and type "\\Server\Share\M365\SEC" for the source path. Office will be downloaded to and then installed from \\server\share\M365\SEC on your network
  1. Cuando termine la configuración, haga clic en Exportar en la esquina superior derecha de la página y, a continuación, guarde el archivo como config-broad-SEC.xml en la carpeta \\Server\Share\M365.

This configuration file is used to download Office installation files and then deploy them to the broad group. The settings are exactly the same as the first configuration file, except the source path points to a different folder (SAC), and the update channel is set to Semi-Annual Enterprise Channel.

Paso 5: Descargar el paquete de instalación de Office para el grupo piloto

Desde un símbolo del sistema, ejecute el ejecutable de la ODT en modo de descarga e incluya una referencia al archivo de configuración del grupo piloto:

\\server\share\M365\setup.exe /download \\server\share\M365\config-pilot-SECP.xml

The files should begin downloading immediately. After running the command, go to \\server\share\M365\SECP and look for an Office folder with the appropriate files in it.

Note that when you download Office to a folder that already contains that version of Office, the ODT will conserve your network bandwidth by downloading only the missing files. For example, if you use the ODT to download Office in English and German to a folder that already contains Office in English, only the German language pack will be downloaded.

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% folder.

Paso 6: Descargar el paquete de instalación de Office para el grupo general

Desde un símbolo del sistema, ejecute el ejecutable de la ODT en modo de descarga e incluya una referencia al archivo de configuración del grupo general:

\\server\share\M365\setup.exe /download \\server\share\M365\config-broad-SEC.xml

The files should begin downloading immediately. After running the command, go to \\server\share\M365\SEC and look for an Office folder with the appropriate files in it.

Paso 7: Implementar Office en el grupo piloto

To deploy Office, we'll provide commands that users can run from their client computers. 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\M365).

Desde los equipos cliente del grupo piloto, ejecute el comando siguiente con privilegios de administrador desde un símbolo del sistema:

\\Server\Share\M365\setup.exe /configure \\Server\Share\M365\config-pilot-SECP.xml

Nota

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.

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% folder.

After Office has deployed to the pilot group, test Office in your environment, particularly with your hardware and device drivers. For more details, see Choose your update channels.

Paso 8: Implementar Office en el grupo general

After you've finished testing Office with the pilot group, you can deploy it to the broad group. To do so, run the following command from a command prompt with admin privileges:

\\Server\Share\M365\setup.exe /configure \\Server\Share\M365\config-broad-SEC.xml

Este comando es el mismo que para el grupo piloto, excepto que hace referencia al archivo de configuración del grupo general.

Después de ejecutar el comando, la instalación de Office se iniciará inmediatamente.

Personalizar la implementación

The steps in this article cover the standard best practice recommendations from Microsoft, if you've chosen to deploy Semi-Annual Enterprise Channel. This section covers the most common customizations to these best practices.

Creación e implementación de varios paquetes en varios grupos de implementación

If you want to deploy both the 32-bit and the 64-bit version of Office, you can create additional installation packages. (Two different architectures cannot be included in the same package.) For more details, see Define your source files.

Uso de otros canales de actualización de Office

With Microsoft 365 Apps, you can control how frequently your users receive feature updates to their Office applications. To do so, you choose an update channel for your users. For more information, see Overview of update channels for Microsoft 365 Apps.

In this article, we're using Semi-Annual Enterprise Channel (Preview) for your pilot group and Semi-Annual Enterprise Channel for the rest of your organization. You can, however, choose to deploy Current Channel, which provides users with the newest features of Office as soon as they're ready. In that scenario, you'd deploy Current Channel (Preview) to your pilot group.

Un único paquete de instalación de Office solo puede incluir un tipo de canal de actualización, de modo que cada canal nuevo necesita un paquete adicional.

Implementación de Visio y Project junto con las aplicaciones principales de Office

To deploy Visio and Project with Microsoft 365 Apps, you can include them as part of the Office application when building it in Configuration Manager. For more details on licensing and system requirements, see Deployment guide for Visio and Deployment guide for Project.

Opciones de configuración de la Herramienta de implementación de Office

Información general sobre la Herramienta de implementación de Office

Información general de la Herramienta de personalización de Office

Guía de implementación de Aplicaciones de Microsoft 365