Dectection Method for Office 365 ProPlus installer in ConfigMgr CB 1803
Hello. I have been playing around with the Office 365 Client Management in ConfigMgr. When I look at the detection methods configured for the Office 365 Installer I can see that its based on the following registry setting. HKLM:\Software\Microsoft\Office\ClickToRun\Configuration\ VersionToReport = 16.0.XXXX.XXXX So far so good, but here is the thing. Let's say that you create a Office 365 ProPlus installer for a newer version and deploy it to a computer that have an older version installed where a user is signed in and running one or more Office apps, then the deployment will fail (ofc). From what I can see, the execution of the installer updates the VersionToReport value before the installation fails, therefor the new version will never be installed since the ConfigMgr client will evaluate the deployment as installed during next AppEval, but still the computer is running the old version. To me this is very bad behavour. Or have I done something wrong here?config.office.com gets a face lift and a few new features
On Monday, Sept 24 2018 at Ignite the Office team unveiled the new look for config.office.com as well as the addition of a few new deployment features to help you deploy Click-to-run Office products. The interface has been updated to ease navigation when using the full experience in the web browser and also optimized for the embedded experience for those of you who are using the Office Client Application Wizard in Configuration Manager (as of Current Branch 1806). New deployment features like MatchOS, Fallback to the CDN and RemoveMSI have been added making it easy to build more complex and capable deployment configurations. One of the most anticipated features allows you to include Office app settings with the deployment settings, allowing you to set the user preferences for Office according to how your organization uses Office. Take a look at the session from Ignite 2018 to see an overview of the new experience and a review of the deployment options available. Session code THR2022 – https://myignite.techcommunity.microsoft.com/sessions/64635Released – the Office Customization Tool
Today, the Office engineering team is announcing the general availability of the Office Customization Tool. With this new web-based tool you can easily customize the deployment of Office 365 ProPlus and other Click-to-Run managed Office products using a simple, intuitive, and web-based interface. The tool is an Azure-based cloud service which allows you to create XML configuration files that are used with the Office Deployment Tool. In the past, you needed to create the configuration files in Notepad or another text editor. The Office Customization Tool makes this part of the deployment process easier and less likely to introduce errors. This tool provides a simple experience which allows you to create a configuration file for use with the Office Deployment Tool, for scenarios where you need to customize the installation of Office 365 ProPlus. Common scenarios include: Initial installation of Office 365 ProPlus or Office 365 Business suites as well as Office 2019 suites, with the ability to include standalone products such as Visio and Project and various language packs. Adding additional products after the initial installation of the Office suite Adding additional language packs by configuring a ‘Language Only’ configuration after the installation of the Office suite or standalone products Standalone installation of Office 365 Access Runtime Installation of volume licensed products with automatic KMS and MAK activation Automatic removal of previous MSI based Office products To work with the service, go to https://config.office.com/ and choose the products, languages, and application settings you want to configure. For example, you can create a configuration file that downloads the 64-bit English version of Office 365 ProPlus, or you can create a file that installs the 64-bit English and German version of Office without Access and Publisher and with the EULA automatically accepted. When choosing a language, MatchOS is a popular option and allows Office to install support for the same languages that are installed for Windows on the targeted device. When you're done, you export the configuration file, which you can then use with the Office Deployment Tool or another software distribution solution to deploy Office in your organization. Choosing a product and a language are the minimum requirements to create a configuration file, but there are many more options to choose from to customize the deployment. Removal of existing MSI based Office products with the ability to ignore standalone products like Visio, Project, SharePoint Designer and InfoPath. These options ensure a smooth upgrade to the latest version of Office in a single deployment step. Choose to install and update directly from the Microsoft CDN or to host the Office package locally. Automatically accept the EULA and support for shared computer activation. Include Office application preferences to define the best experience for your users when they begin using the latest version of Office. You can also use the Office Customization Tool to make changes to existing configuration files, which is very useful when you need to modify the configuration of Office on devices that are already installed and configured or if you are creating a second or third configuration and you want to use your own baseline. Simply use the Import option and select the configuration file you wish to modify, make the desired changes, and use the Export option to generate a new configuration file. Are you using Configuration Manager to manage your deployments or configuration changes? If so you will be happy to know that as of 1806, Configuration Manager has integrated the Office Customization Tool with the Microsoft Office 365 Client Installation Wizard as part of their Application deployment workflow, giving administrators access to the same experience and the same set of features 1 described above. And if you haven’t yet upgraded to 1806, use the Office Customization Tool to generate the XML and incorporate that into your package. For more information, see the Overview of the Office Customization Tool. 1 – Some Click-to-Run deployment features are not compatible with Office deployments managed by Configuration Manager’s Application deployment workflow
Word Add-In Deployment
Hi there, I am trying to deploy an add-in for some users for MS Word (right now we're just testing so it is limited just to a few people in our IT Dept.). We are trying to deploy the DocuSign add-in. I have done this through the Integrated Apps section of the O365 Admin Centre and applied it to a Security Group in our Active Directory. The issue we are facing is, when deploying the add-in it does not seem to want to automatically install on most of our users' MS Word applications (we did have 2 test users who said it was automatically installed). What we've had to do for the other test users is go to the "Get Add-ins" section of MS Word and click on "Admin Managed", then click on DocuSign to add it to the ribbon. Is there some setting somewhere that would have it automatically installed on our users' systems as opposed to having them add it manually? Thanks!
Multi user device
Good afternoon 1. Need to set a desktop to allow a user 1 (agency worker) to use a guest1 account to login into Windows 10 and then activate office 0365 to be used for Word. Then need that person logs out of windows 10. 2. Next user2 (agency worker) to log into the device with the same guest1 account as user 1 and then activate their own o365 account. and again logs out of windows. This may be done with multiple users. Will they need to sign out of O365 each time 3. Also for it allow multiple users (Company worker) to login in with their personal windows 10 login and activate o365 and be able to use full MS office apps. Can this be done, at the moment the device is set up a multi-user device, which adds a token on for single login. At the moment we are finding that because of the token, a Guest1 account can only be associated with a 1 email address only. The Pc can be login in and out with 20 different people over a week. You help is most appreciated.
