App Volumes 2.10 and Office 2016

[Mang0steen]

Hello everyone

I'm trying to appstack Office 2016. The creation and assignment of the appstack works fine, but as soon as I open the application itself (e.g. Word, Excel), the Office configuration dialog pops up and an error occurs.

I followed the instructions as in the user guides (not opening the Office application during the provisioning process, and set the activation through the kms server).

Office 2010 and Office 2013 work fine though. So I'm guessing Office 2016 isn't fully supported in AppVolumes 2.10?

[Jason_Marshall]

Only 2010 and 2013 are currently supported.

[jeffrobinson85]

Jason,

Can you tell us when Office 2016 will be supported by App Volumes?

Thanks

Jeff

[SanderMors]

We have similar problems in a 2.11 environment with the VLK (MSI) + KMS . I have seen the recipe for Office 365. Are all versions of Office 2016 fully supported at the moment?

[javier_roe]

I've got the same problem here... ¿is Office 2016 supported by AV 2.11?

[benstefan6]

I can replicate the same issue. Office 2016 Pro Plus AppVolumes 2.11 VLK + KMS. It appears that it is activation related. KMS cannot detect the product until the configuration fails. Then activation is successful.

[dazzy90]

Hi,

Did you ever get this working? If so which version of App Volumes are you using??

Did you use a 'provisioning' machine to capture the Office 2016 application?? Or did you use the gold master image as the 'provisioning' machine?

What experience has anyone had with Office Project and or MS Visio App Volumes and KMS activation?? I have a mixed experience using AV 2.9! I think I am going to need to upgrade AV to 2.10 or 2.11 right to support Office 2016 app stacks?

Regards,

Darren

[lansti]

I have the same issue.

Appvolumes agent 2.12, Office365 click to run.

If I install this on my golden image, it works fine, but if i create a appstack woth office365, i can start Office, but as a trial. It seems that the appstack do not activate.

I'm deploying this on non-persistent desktops, with shared computer switch during installation in the XML file.

Anyone seen the same?

I have also deployed adfs server in trusted zones with GPO.

[anthonymorey]

I have the same issue.

Appvolumes agent 2.12, Office365 click to run.

If I install this on my golden image, it works fine, but if i create a appstack woth office365, i can start Office, but as a trial. It seems that the appstack do not activate.

I'm deploying this on non-persistent desktops, with shared computer switch during installation in the XML file.

Anyone seen the same?

I have also deployed adfs server in trusted zones with GPO.

Hello.

I am in the same scenario.

I launch word and get the message "Sorry, something went wrong and Word was unable to start. (6)."

Most recently i have not performed any Optimization on the golden image only installed the agents.

AppVolumes 2.12 and office Click to run.  Office installed in base image works.

Looking to the community for help?

[lansti]

Hi, have you figured out more about this problem?

There has to be someone that have solved this one?

This is my install.xml file that i use during install of office to the appstack:

<Configuration>
  <Add SourcePath="" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="nb-no" />
    </Product>
  </Add>
  <Updates Enabled="FALSE" />
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Name="Office365Setup.log" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <Property Name="SharedComputerLicensing" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="1" />
</Configuration>

I found an article that told me to use:

<Setting Id="KMSSERVICENAME" Value="<server-name.org>.com"/>
<Setting Id="AUTO_ACTIVATE" Value="1" />

But as far as i understand, this is for the proplus installment.

[anthonymorey]

Hello.

I have gotten fed up with trying to resolve this and have since opened a case with VMWare.

I will be sure to report back when we have gotten to root cause of the problem.

The only other comments that i have managed to pick up from others it that O365 C2R is working fine when installed in the base image.

Rgds.

[lansti]

Hi anthonymorey, any breaking news regarding our issue?

[anthonymorey]

Ticket opened with VMware.

They have troubleshooted and now raising a PR with the Devs.

Sorry, that's all that i have for the moment.

Cheers for following along :smileygrin:

[Mark808]

Thanks Anthony for opening a ticket on this,

Please keep us posted on your progress and, when you find out, the version that will include the fix for this.  I experience the problem as well.

-Mark

[anthonymorey]

Hello People's.

As recommended by VMware.

It looks as though my first test of capturing the O365 2016 C2R using AppStack 2.12.1 is a success!

Kind Regards,

Anthony.

[lansti]

Nice to see it works for you.

But, i have upgradere app volumes server to 2.12.1, and installed appvolumes client on my golden image -> recomposed.

I have created a new appstack, installed office c2r with cmd as administrator.

msiexec /i "folder/setup.exe" /configure install.xml

used this xml file:

<Configuration>
  <Add SourcePath="" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="nb-no" />
    </Product>
  </Add>
  <Updates Enabled="FALSE" />
  <Display Level="None" AcceptEULA="TRUE" />
  <Logging Name="Office365Setup.log" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <Property Name="SharedComputerLicensing" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="1" />
</Configuration>

Still i got trial version when i assign this new one to på desktop pool.

Did you do something else?

Its your XML file any differewnt than mnine?

[anthonymorey]

Hiya.

So i upgraded to 2.12.1.

Upgraded Client and Golden Image.

Imported new appstack templates.

Deployed office by firing up an Administratrive Command prompt.  Changed directory to installation and ran command:  setup.exe /configure install.xml

<Configuration>

    <Add OfficeClientEdition="32" Channel="FirstReleaseDeferred" OfficeMgmtCOM="TRUE">

        <Product ID="O365ProPlusRetail">

            <Language ID="en-us" />

            <ExcludeApp ID="Groove" />

        </Product>

    </Add>

    <Logging Level="Standard" Path="c:\windows\temp" />

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

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

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

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

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

</Configuration>

That's it.  HTH's

Anthony.

[lansti]

Thanks, I just created new template, imported that one, and installed office all over again, but i still meet this issue.

It seems to me that my VDI cant reach microsoft licensing, or that i might miss a policy.

What kind of policies do you use to automatic authenticate Office with the windows user you log on with?

Or do you get the Activate Office dialog box at first run?