The other (semi/un-supported) way is to manually copy the “configuration.xml” and make a Shared Activation flavor of it, then add a new deployment type, set some sort of condition to control the scope of that deployment type, and go that route. The first is to simply build a new deployment, which sounds like a waste of storage space (compared with traditional O365 ProPlus deployment builds using ODT and XML files) but if you have deduplication turned on for the content source location it shouldn’t be a concern. One is supported, the other is unknown (at this point). The Visio Pro deployment uses a different detection rule and seems to work fine.Īs for Shared Computer Activation deployments, there are at least two (2) ways to go. Just change the detection rule and it works. So the install (deployment) on a machine with O365 Pro Plus (latest/same version) causes the Project deployment to think it’s already installed. However, the Project Online client has an issue with the Detection Rule being the same as Office 365 ProPlus. I meant to post this a few weeks ago, but anyhow… Microsoft released an updated ODT which removes the “Match Current OS” option from the language options list.
