To use the MigrateArch attribute, you need the following: Requirements for using the MigrateArch attribute
The 32-bit version will be uninstalled and then the 64-bit version will be installed. For more information, see Sample configuration.xml file to use with the Office Deployment Tool. But, if you want to make any changes to the installed products and languages, or other deployment settings, you can do that as part of the migration process by explicitly specifying those settings in your configuration.xml file. The migration process will preserve those during the migration process. With MigrateArch, you don't have to account for all the installed products and languages or other deployment settings. If the MigrateArch attribute is set to True, then your installation of Microsoft 365 Apps will be changed to the architecture (sometimes referred to as the bitness) that is specified in the OfficeClientEdition attribute. It also required that you account for all the other deployment settings configured for that device, such as the update path and the installed languages, so that those settings would be included when you did the 64-bit installation.īut now, to make it easier to change from a 32-bit to a 64-bit installation of Microsoft 365 Apps, the Office Deployment Tool and its configuration.xml file supports an optional attribute named MigrateArch.
Will office 2016 64 bit overwrite 32bit install#
Up to now, if you had the 32-bit version of Microsoft 365 Apps installed on a device and you wanted to change to the 64-bit version, you needed to uninstall the existing 32-bit version and then install the 64-bit version.
0 kommentar(er)
