yermeme.blogg.se

On newly enrolled devices, the GUI option worked without any problems but sometimes on an existing device the 32 bits Office apps were installed without issues, other times the 32 bits version installed but after a while, the Office 365 apps reversed back to the 64 bits version because “something went wrong”.) (I tried the GUI version first, but it resulted in no fixed outcome. To be sure the Office 365 32 bits apps will be installed without any issues, I manually configured the XML instead of choosing the GUI option. Configuring the Office 365 apps (32 Bits Version) One for the 64 bits version and one 32 bits version and assign the proper groups 3. Because like I told you earlier, we only want to deploy the Office X86 Apps to a subset of users.Īfter we created the group, we can create the Microsoft 365 Apps. The first thing we need to do is to create a new group: Office365Apps_x86. How are we going to make sure, when we are using the built-in option to make sure the proper device will receive the proper Microsoft 365 apps version. Of course, we could switch to a Win32App that contains the ODT as I am explaining in the blog below but that’s not what this blog is about!. Looking at the built-in option you will notice it is missing the “Requirements” tab.

I couldn’t find much information about deploying/migrating 64 bits and 32 bits of the built-in Microsoft 365 Office apps and how to make sure the proper device would get the right version. I will divide this blog into multiple parts How are you going to make sure all new and existing devices will get the version of the Office 365 Apps they need. Imagine the next scenario: You have a customer with the need for Microsoft 365 Apps but some of the employees need the 32-bit / x86 Office 365 Apps instead of the 64 bits / 圆4 Office 365 Apps.