Visio 2016 Volume License Install

[jmatz135]

We are using App Volumes 2.13.1 and I am trying to capture Visio 2016 volume license install i.e. one that uses the KMS server to activate.  Eventually I would like to have this as an addon to office but to simplify things for the moment I'm just trying to get it to work standalone.  We are using a click to run installer using the Volume licensing configuation:

</Product>

    <Product ID="VisioProXVolume">

<ExcludeApp ID="OneDrive" />

      <Language ID="en-us" />

    </Product>

On a normal machine this works fine and Visio installs and checks out its license properly from the KMS server, but if I try to do it in an appstack and apply it to a machine I get the following error:

If I choose close Visio just closes.  If I choose repair now then it restarts Visio and on the next launch I get the following:

This was captured on a provisioning machine without anything but the App Volumes agent (no MS Office installed) and deployed to a VM with no software on it (No MS Office installed).  Does app volumes just not work with the volume license version of Visio?  That can't actually be intended.

[Suman1209]

hi

Take a look at this VMware Knowledge Base  .

[jmatz135]

I've seen that article and there is nothing within it that says you can't use Click-To-Run package with the volume license of the software.  I am using App Volumes 2.13.1 so it is definitely within the compatibility matrix, so I'm not sure what exactly you are wanting me to look at.

[jmatz135]

I found in the cv_startup_postsvc.log for App Volumes the following:

11:04:00.323 svoffice Windows 7 Professional  6.1.7601  64-bit

11:04:00.323 svoffice Logon start 2017-11-30

11:04:00.339 svoffice Waited 0.016 seconds for log file lock

11:04:00.557 svoffice Built on 2017-09-27 at 09:35:39 UTC

11:04:00.620 svoffice {fd3f11d7-d5e7-11e7-9168-0050569c2245} App volume

11:04:00.620 svoffice {b7497ec6-0527-11e7-8f44-806e6f6e6963} Writable volume (system)

11:04:00.635 svoffice PostProvision log start

11:01:46.249 svoffice Windows 7 Professional  6.1.7601  64-bit

11:01:46.264 svoffice Built on 2017-09-27 at 09:35:39 UTC

11:01:46.264 svoffice PostProvision start 2017-11-30

11:01:46.264 svoffice Stopping OSPPSVC

11:01:46.311 svoffice No MSOffice products on the system volume

11:01:46.342 svoffice Wrote C:\SnapVolumesTemp\MountPoints\{c7e392f5-d5e6-11e7-9505-0050569c2245}\OfficeTokens\tokens.ospp.dat

11:01:46.342 svoffice Wrote C:\SnapVolumesTemp\MountPoints\{c7e392f5-d5e6-11e7-9505-0050569c2245}\OfficeTokensInitial\tokens.dat

11:01:46.342 svoffice Wrote C:\SnapVolumesTemp\MountPoints\{c7e392f5-d5e6-11e7-9505-0050569c2245}\OfficeTokensInitial\cache\cache.dat

11:01:46.342 svoffice Find licenses

11:01:46.389 svoffice Found 15 licenses

11:01:46.389 svoffice Found 1 product on the AppStack:

11:01:46.389 svoffice VisioProXVolume                2016-64  2017-11-30 15:58:14 UTC

11:01:46.389 svoffice Visio               2016-64  2017-11-30 15:58:29 UTC

11:01:47.481 svoffice C:\SnapVolumesTemp\MountPoints\{c7e392f5-d5e6-11e7-9505-0050569c2245}\SVROOT\Program Files\Microsoft Office\Office16\ospprearm.exe result: Microsoft Office rearm successful.

11:01:47.496 svoffice PostProvision end

11:04:00.635 svoffice PostProvision log end

11:04:00.651 svoffice Invalid Office product ID VisioProXVolume

11:04:00.651 svoffice Logon failed, details in the preceding log entries.  Windows logon will continue.

11:04:00.932 svoffice NoRereg start 2017-11-30

11:04:00.932 svoffice Waited 0.000 seconds for log file lock

11:04:00.947 svoffice NoRereg end

The key line here is 11:04:00.651 svoffice Invalid Office product ID VisioProXVolume, which of course isn't true.  VisioProXVolume is a valid product ID.  Does App Volumes just not understand that?

[fdrietatns]

Did you prepare the visio.ww config xml?

Prepare the installer

The KMS installer is embedded with the information required to activate the Office 2016 applications. You might need to edit the information in the installer depending on the configuration set up of your organization.

1. Locate and open the proplus.ww folder in the KMS installer.
2. Open the config.xml file in the proplus.ww folder.
3. Edit the SettingId to point to the KMS Server of the deployment organization:

For Example:

<Configuration Product="ProPlus">
<Display Level="full" CompletionNotice="yes" SuppressModal="no" AcceptEula="no" />
<Setting Id="KMSSERVICENAME" Value="<server-name.org>.com"/>
<Setting Id="AUTO_ACTIVATE" Value="1" />

[mmonkman]

Hey jmatz,

Did you ever resolve your issue?  Have the same thing here!

[Aldo_M]

Hi Jmatz,

have you found a solution?

i have the same issue with Visio.

office 2016 ProPlus installed on the base image, visio 2016 Pro on Appstack.

when starting i receive an error related to the license.

thanks

[jmatz135]

No, I have an open ticket with VMware for like 2 months with little to no action as far as I can tell.  I don't really think there is a solution without them updating App Volumes itself.

[Aldo_M]

Thanks Jmatz,

please let me know in case you receive a "solution" from VMware.

in the meanwhile, i have updated App Volumes to the latest version with any luck. still not working.

[Ray_handels]

Looking at the office license you should not activate it during sequencing. Do you have Office installed within your golden image?

If so, make sure to use a packaging machine that is a clone of the golden image and remove the VMWare Agents from it.

Then install the application without activating it. Normally you should have a KMS setting within your golden image and Visio will start up and activate against the settings set in your golden image.

If you have a KMS database key within the golden image and one within the appstack these two will clash and activation will be corrupted.

[mmonkman]

jmatz, I have Visio volume license edition installed via the C2R method in an appstack.  I would recommend the provisioning machine being a clone of the base image minus the horizon agent yes, but having any part of Office installed in the base image is not required.

Try adding the Visio GVLK using the PIDKEY parameter to the config.xml .  This will register the product with a temp OOB grace license until the KMS is discovered via DNS when opening Visio on your instant clone.

        <Product ID="VisioProXVolume" PIDKEY="69WXN-MBYV6-22PQG-3WGHK-RM6XC">

            <Language ID="en-us" />

        </Product>

[jmatz135]

My config file.  As you can see I already have the PIDKEY set.  Doesn't work.

<Configuration>

  <Add OfficeClientEdition="32" Channel="Deferred">

    <Product ID="VisioProXVolume" PIDKEY="69WXN-MBYV6-22PQG-3WGHK-RM6XC">

  <ExcludeApp ID="OneDrive" />

      <Language ID="en-us" />

    </Product>

  </Add>

<Updates Enabled="FALSE" UpdatePath=""/>

<Display Level="Full" AcceptEULA="TRUE" />

<Property Name="AUTOACTIVATE" Value="1" />

<Property Name="PinIconsToTaskbar" Value="FALSE"/>

<Property Name="SharedComputerLicensing" Value="1" />

<Logging Level="Standard" Path="%programdata%\Appdeploy\Office2016" />

</Configuration>

[mmonkman]

OK.  I don't think you posted the whole config.xml before?

Anyway, it won't work with SharedComputerLicensing=1

That's why you're getting the sign-in page.

If you run cscript c:\"Program Files (x86)\Microsoft Office\Office16"\OSPP.VBS /dstatus on an instant clone what comes back - No Installed Product Keys ?

If so set SharedComputerLicensing=0 in the registry, Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration and restart the Microsoft Click-to-Run Service

Manually install the GVLK ; cscript c:\"Program Files (x86)\Microsoft Office\Office16"\OSPP.VBS /inpkey:69WXN-MBYV6-22PQG-3WGHK-RM6XC

and run Visio.  See what happens.

If your end game is to run O365 C2R (subscription licensing) with Visio Volume license edition (KMS) all in an Appstack or all in the base image - it will not work  VMware have confirmed this.

[jmatz135]

"If your end game is to run O365 C2R (subscription licensing) with Visio Volume license edition (KMS) all in an Appstack or all in the base image - it will not work  VMware have confirmed this."

I've had a ticket open with VMware for 3 months and they know the situation and haven't confirmed this.  Also, why if you put everything in the base image will it not work?  It works perfectly fine everywhere else.

[jmatz135]

I tried creating an appvolume with Visio 2016 from the C2R package using a config file with the SharedComputerLicensing commented out.  It didn't work.  Here is the error:

So I ran the dstatus command and I received No Installed Product Keys

So I checked for the key which didn't exist so I created it and set it to 0 as you said and restarted the Microsoft Click-to-Run Service.

Then I tried to run cscript c:\"Program Files (x86)\Microsoft Office\Office16"\OSPP.VBS /inpkey:69WXN-MBYV6-22PQG-3WGHK-RM6XC

Which returned the following error:

The Product Licensing Service reported the product key is invalid.

Please note this is Visio captured on a provisioning machine without Office installed and deployed to an instant clone without Office or and appstack containing Office installed.

Also note, on the exact same provisioning machine if I install the software with the exact same config file the product licenses just fine:

[mmonkman]

Correction - Appvolumes does not support the two different Office licensing models.  Everything in the base is OK, apologies.

The only methods that VMware currently support are outlined here which i'm sure you've come across before. Neither of them suggest that C2R and KMS licensed products can co-exist on an appstack.

https://kb.vmware.com/s/article/2146035

https://communities.vmware.com/docs/DOC-31399

I have the same goal as you because our O365 subscription plan doesn't include Visio and Project.  The Product Management team are being consulted to determine if it can be supported in the future.

[mmonkman]

The Product Licensing Service reported the product key is invalid. - That's odd!

Can you make sure that all traces of Office are removed from the provisioning machine;

Uninstall Office from a PC - Office Support

[Aldo_M]

Hi mmonkman,

could you please tell me:

i have the parent image with office 2016 ProPlus correctly activated via KMS.

now i would like to AppStack Visio 2016 Pro.

the capture is done on a clean VM where only Office 2016 is installed.

attaching the stack after the capture, generates an error related to the license.

may i am doing something wrong during the capture procedure?

if i install Visio on a "clone VM" the activation works correctly

thanks

[jmatz135]

The provisioning machine was clean built.  Never had office installed.

Yeah, I figured mixing the two licensing schemes in an appstack probably wouldn't work, but I can't even get the volume licensing to work in the first place so I'm trying to go one step at a time.

[Ray_handels]

The provisioning machine was clean built.  Never had office installed.

Does your golden image have office installed? If so than that's at least one of your issues. And you can only use KMS activation with Appvolumes for as far as I know.