On a couple of test machines, attempts to install VisioProXVolume and having a licensed user sign in results in an activation failure. Starting in late August, some of our staff began getting an activation failure. Again, this is how it has been done for the past nearly 4 years. If a user didn't have one of the MAK keys installed, but was assigned a licenses in Azure, both Project or Visio would be licensed and function fine. In addition, we began purchasing licenses in Azure and assigning the " Visio Plan 2 for GCC" license to individuals, allowing us to continue using the existing 10 MAK licenses while adding additional licenses in the cloud. This allowed us to continue using a MAK key for 10 users (we had to convert the existing MAK key to the C2R version). Here's the specific ProductID used in the XML: When it came time for the migration to 365, we uninstalled their current Visio Pro 2016 MSI version and, using the Office deployment tool and an XML file, deployed Office 365 with the click-2-run Visio and Project version. We had 10 existing Visio Professional 2016 licenses using a single MAK key. Nearly 4 years ago our organization was migrating from Office 2010 to 365.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |