If you want to keep using Project 2019 with Office 2016, please try to use click-to-run version of Office 2016 on the computer, such as Office 365 ProPlus and Office 2016 retailed version (not volume licensed version).Īdditionally, if you are using the RDS environment, it is recommended to use For more information about the Office version coexisting, please refer to: Supported scenarios for installing different versions of Office, Project, and Visio on the same computer Because Project 2019 are using the click-to-run installation technology while volume licensed Office Standard 2016 are using MSI We cannot install Project 2019 Standard (VolumeLicense) with Office 2016 Standard (VolumeLicense) on the same computer. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019. If you have feedback for TechNet Subscriber Support, here to learn more. Please remember to mark the replies as answers if they helped. Maybe you can directly submit a feedback to Office product team via the following method: #MICROSOFT PROJECT PROFESSIONAL 2016 VS STANDARD INSTALL#So I am not sure if there will be a plan to use Office deployment tool to install volume licensed Office 2016 product. And many Office subscription product are also recommended for best practice. I think the click-to-run installation technology is a trend for Office product. Just personal opinion, I am afraid there is no KMS or MAK activation planed to be supported for Office 2016 (Professional or Standard) click-to-run installation technology.Ĭurrently, Office 2019 is released in Microsoft and no MSI installation technology designed for it. Well, actually very bad documented by Microsoft, because you cannot read that out of the papers, until you are forced to use C2R with your 2016 Office Standard/ProPlus VL-license, because of the use of Visio/Project 2019ĭo you think, there will upcome a C2R installation version of Office 2016 Standard (VL), like it exists now for Project/Visio 2016(VL), or not, as it is only a question of Key Activation support of VL-keys in the C2R environment.? We would need for example auto-creation of Exchange Mailbox of the domain user, which was an option in the old customization tool. But as well, there is no option for Office 2016 Standard. The new way would be Registry Keys over to fill-in to the configuration.xml. #MICROSOFT PROJECT PROFESSIONAL 2016 VS STANDARD OFFLINE#The following question would be, that with Office 2016 we had a offline customization tool, we've created a MST files with plenty of information. #MICROSOFT PROJECT PROFESSIONAL 2016 VS STANDARD HOW TO#So I have no idea, how to install in co-existance Project 2019 Standard (VolumeLicense) with Office 2016 Standard (VolumeLicense), which need to co-exist over the C2R install way, it seems, on the RDS. There is plenty of product IDs, for the standalone products like Excel, Word, etc. The problem now is, that with the Office Deployment Tool, I cannot find any ProductID representing Office 2016 Standard (VolumeLicense), I could configure to the XML. So I've went through all the C2R things, and got installed Project 2019 Standard successfully. Then I wanted to install Project 2019 Standard (VolumeLicense), and got a message, that a co-existance with MSI installation is not supported. Originally I've had Office 2016 (VolumeLicense) installed on a RDS server with MSI option. I have a quite common scenario to deploy, I think and cannot find a solution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |