ColinHardie asked a question.
Bit of an open question I know but is anyone aware of anything changing with Visio 2016 recognition recently?
Looking at the following graph in SLM, we can see a pretty steep usage increase of it.
Our SAM team have asked the question and I'm struggling to explain it. Have confirmed with our SCCM guys that nothing significant has changed in the packages that are typically provisioned to end-users so am working on the assumption that something has changed in how the product is recognised...e.g. has a DIS rule been added/changed that would start recognising a specific file on users machine as having this product installed?
It looks like machines that were reporting 'Visio Plan 2' before February are generally reporting 'Visio Plan 2' and 'Visio 2016' e.g.
Anybody have an explanation? 😬
Hi,
Did you recently updated Snow Recognition Service? Might be some new rules were applicable for Visio 2016, I think you can even check from SQL when was this rule updated. Might give you some hint.
Thanks
I have checked a few of our customers and they show the same behaviour against there data for Visio.
As an addition it's all against Visio 2016 where other installations exist for 2016 Standard or Professional. So it's missing any edition info.
Aside from checking when the SRS rule was updated i would say this gives better recognition.
If a user was part of the Visio Plan 2 they have the option to install the Visio 2016 software so it's now showing where folks have both the plan license and installed the software.
I'd imagine if you look for just users who have the Plan only but no install this shows they have been given a license in the O365 portal but never used it, thus are ripe for reharvesting that license.
Happy to learn if the above is not quite accurate though.
Well, you can use Visio without having the application installed, simply logging into the https://office.microsoft.com portal and start Visio as a web application. It will trigger usage on Visio Plan 2 if you have the O365 connector with the Graph API defined
What Joe wrote seems to be a good aspect.
I have just checked another customer environment without O365 connector, and I cannot confirm this behaviour there.
So, rather than a SRS update, something in combnation with O365 seems likely.