#ATIVADOR OFFICE 365 64 BITS HOW TO#

Requirements for using the MigrateArch Office 365 attribute If youвЂ™re unfamiliar with the tools, weвЂ™ll cover every step in this post. Important InfoIf you are already familiar with the Office Deployment Tools, the short version of this post is to download an Office version at least 1902 and create a new configuration file (.xml) with the MigrateArch attribute to deploy your new installation. Michael Niehaus (Principal Program Manager at Microsoft) also publish this tweet to recommend using Office 64-bits: If youвЂ™re unsure if you need to install Office 64 or 32bits, you can read the Office support article that covers this subject. We could have used the Office 365 installer from SCCM but the built-in customization tool doesnвЂ™t support the MigrateArch yet.

#ATIVADOR OFFICE 365 64 BITS HOW TO#

In this post, we will show you how to migrate an Office 365 32-bit version to an Office 365 64-bit version in an automated and silent way using SCCM.

If desired you can also make changes to the installed products and languages. When set to True, the Office 365 installation will be migrated to the architecture specified in the OfficeClientEdition attribute.ДЄnother great feature is that MigrateArch, will preserve all the installed products, languages and other deployment settings. Now, the Office Deployment Tool and its configuration files support a new attribute: MigrateArch. In the past, if you had a computer with Office 365 32-bit version and wanted to migrate to the Office 365 64-bit version, you needed to uninstall the existing 32-bit version before installing the 64-bit version.

Ativador office 365 64 bits