locked
Virtualized Project Pro 2010 problems with KMS activation. RRS feed

  • Question

  • I have followed the guidelines for sequencing O2K10 per this link https://support.microsoft.com/en-us/kb/2830069.

    Setup:

    App-v Client and Sequencer are running App-V 5 SP3.

    Clients are x64 Windows 7 with x86 Office 2013 pro installed (virtual desktops provisioned with Citrix 7.6)

    Backend App-V infrastructure is App-V5 SP1 running on Windows 2008R2.

    Application is getting to the client, but when launched I get "Configuring Office 2010" followed by "installing" both windows close and that sequence runs twice more, "Configuring Office 2010" followed by "installing."  After the third time, the MS Project Window that had open closes without error.

    Windows Application log shows - 

    "Event 1029 - Source Office Software Projection Platform Service

    Unable to get detailed error information during license consumption.  Last error 0xC004F015"

    Haven't found a lot useful on the Internet on this one.

    About to go through the install process a third time going line by line with guide referenced about.

    Is it possible the existing installation of Office 2013 on the Sequencer is causing a problem capturing the Project Pro OSPP configuration?  All being activated with KMS BTW.

    I don't' expect any of you to have the answer offhand, but any troubleshooting suggestions would be greatly welcome.  Running out of rope here.

    Thanks,

    stutt


    d

    Tuesday, September 29, 2015 9:28 AM

Answers

  • How have you sequenced the package?

    Sequencing with integration or Sequencing without integration

    If you sequenced without integration, install the Office deployment kit on all App-V clients before you publish the package.

    msiexec /i OffVirt.msi   PROJECTPRO=1

    For info - http://app2pack.blogspot.com/2015/09/solution-microsoft-office-has.html

    Check this link about Office 2013 and office 2010 co-existence. This would give you brief idea and might provide you an answer.

    https://technet.microsoft.com/en-us/library/dn770198.aspx

    Hope this helps.


    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you. )

    Tuesday, September 29, 2015 10:21 AM
  • Have you published the package globally?

    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you. )

    Wednesday, September 30, 2015 4:13 AM
  • There is no need to deploy the msi manual (or with appsense), if you followed the stepts from the acticle to posted, it should intgegrated in the package. So did you enable script on the client (Set-AppvClientConfiguration -EnablePackageScripts 1)?
    If you deside to deliver Visio too, incl the switch for visio too.
    Tuesday, September 29, 2015 8:08 PM

All replies

  • How have you sequenced the package?

    Sequencing with integration or Sequencing without integration

    If you sequenced without integration, install the Office deployment kit on all App-V clients before you publish the package.

    msiexec /i OffVirt.msi   PROJECTPRO=1

    For info - http://app2pack.blogspot.com/2015/09/solution-microsoft-office-has.html

    Check this link about Office 2013 and office 2010 co-existence. This would give you brief idea and might provide you an answer.

    https://technet.microsoft.com/en-us/library/dn770198.aspx

    Hope this helps.


    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you. )

    Tuesday, September 29, 2015 10:21 AM
  • Sequenced with integration.

    Thanks for that link.  I'll review it now.


    d

    Tuesday, September 29, 2015 12:09 PM
  • Interesting......I followed the instructions for integrated installation.  For fun, I ran "msiexec /i OffVirt.msi   PROJECTPRO=1"  prior to launching the streamed version of Project Pro, and it worked.  So I surmise that what has failed is my attempt to integrate.  So the options I see are:

    * figure out why OffVirt.msi did not get captured during sequencing (still smells like pre-existing install of 2013 is a factor here.)

    * deliver the OffVirt.msi install via AppSense prior to the user logging in.  Downside being lots of users will have a Project shortcut they cannot use.

    Not really sure what will be lost by running non-integrated.  Read something vague about integration being involved with SharePoint.



    d

    Tuesday, September 29, 2015 1:29 PM
  • There is no need to deploy the msi manual (or with appsense), if you followed the stepts from the acticle to posted, it should intgegrated in the package. So did you enable script on the client (Set-AppvClientConfiguration -EnablePackageScripts 1)?
    If you deside to deliver Visio too, incl the switch for visio too.
    Tuesday, September 29, 2015 8:08 PM
  • Have you published the package globally?

    (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you. )

    Wednesday, September 30, 2015 4:13 AM
  • App-V 5 ---> One Office Package - per SKU - Per Version - published Globally.



    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Saturday, October 17, 2015 4:48 AM