none
App-V 5.0 Sequencing Office 2010 - Cannot verify the License for this Application KMS

    Question

  • Hey Guys,

    i already found some Topics about my Problem, but None of the Solutions i have found, help in my case. I hope someone can help...

    I Sequenced Office 2010 Professional Plus x86 on an App-V 5.0 Sequencer Client (x64) and streamed it to Windows 7 x64 and Windows Server 2012. While i was sequencing, i followed the Articles at http://blogs.technet.com/b/office_resource_kit/archive/2011/06/15/sequencing-office-2010-for-app-v-part-1-considerations.aspx and also used the Parameter:
    msiexec/i OffVirt.msi ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core PROPLUS=1

    In the sequencing Process anything ist working fine, i can start Word, Excel... and Office is activated. When i publish the Application and stream to the Client or RDS, i get the Error message in the Screenshot.

    I also tried to create a new Package and type in the KMS Client Key directly to Office, didnt work. In a third Sequencing Process (also new Sequence) i tried with an another Script what i have found: msiexec /i OffVirt.msi PROPLUS=1 KMSSERVICENAME=”SERVERNAME” KMSSERVICEPORT=1688

    Please help!!

    Best regards

    Wednesday, April 10, 2013 4:18 PM

Answers

  • Client Orchestration:
    Activity ConfigurePackageFinalize #46 failed on component ScriptManager (error: 0x79100710-0xD).

    ConfigurePackageFinalize activity #46 was failed by component ScriptManager (error: 0x55900C02-0x501), initiating a ConfigurePackageUndo.

    ConfigurePackage activity #46 failed with error code 0x55900C02-0x501.

    Client-Package Config:

    ConfigurePackage derived values: moniker 'F8AC77F7-0705-4134-A031-66DF3B313B22_3AD2A574-05C9-47B0-B194-7F0F973CD365'; package root 'C:\ProgramData\App-V\F8AC77F7-0705-4134-A031-66DF3B313B22\3AD2A574-05C9-47B0-B194-7F0F973CD365\root'; sequenced on 32-bit OS: true


    Someone an Idea?

    Have you enabled scripting on the clients?
    • Marked as answer by Cibaay_de Thursday, April 11, 2013 3:25 PM
    Thursday, April 11, 2013 2:39 PM
  • Client Orchestration:
    Activity ConfigurePackageFinalize #46 failed on component ScriptManager (error: 0x79100710-0xD).

    ConfigurePackageFinalize activity #46 was failed by component ScriptManager (error: 0x55900C02-0x501), initiating a ConfigurePackageUndo.

    ConfigurePackage activity #46 failed with error code 0x55900C02-0x501.

    Client-Package Config:

    ConfigurePackage derived values: moniker 'F8AC77F7-0705-4134-A031-66DF3B313B22_3AD2A574-05C9-47B0-B194-7F0F973CD365'; package root 'C:\ProgramData\App-V\F8AC77F7-0705-4134-A031-66DF3B313B22\3AD2A574-05C9-47B0-B194-7F0F973CD365\root'; sequenced on 32-bit OS: true


    Someone an Idea?


    Have you enabled scripting on the clients?


    How can i enable that? In the Sequencing process?

    I used following Command: Set-ExecutionPolicy ByPass; Import-Module AppvClient; Set-AppVClientConfiguration -EnablePackageScripts 1

    Its working now!!!!

    Thanks!

    Thursday, April 11, 2013 3:25 PM

All replies

  • hello,

    You need the deployment kit for v5;

    http://www.microsoft.com/en-us/download/confirmation.aspx?id=38399#


    Nicke Källén | The Knack| Twitter: @Znackattack

    • Marked as answer by Cibaay_de Wednesday, April 10, 2013 6:08 PM
    • Unmarked as answer by Cibaay_de Thursday, April 11, 2013 7:36 AM
    Wednesday, April 10, 2013 4:49 PM
  • And the sequencing guide for Office 2010 with App-V 5: http://support.microsoft.com/kb/2830069


    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually answer your question). This can be beneficial to other community members reading the thread.


    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.

    Twitter: @stealthpuppy | Blog: stealthpuppy.com | The Definitive Guide to Delivering Microsoft Office with App-V

    • Marked as answer by Cibaay_de Wednesday, April 10, 2013 6:08 PM
    • Unmarked as answer by Cibaay_de Thursday, April 11, 2013 7:36 AM
    Wednesday, April 10, 2013 4:58 PM
    Moderator
  • OK Thanks guys!
    Just one thing regarding the msiexec Deployment Kit Options. As i said, i have an App-V 5 Sequencer Client on an Windows 7 x64 Machine and want to Sequence Office Professional Plus 2010 x86 (without Visio and Project). Would this be the right msiexec Syntax? :

    msiexec /i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core,OSppWoW64 PROPLUS=1

    or is it:

    msiexec /i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core,OSppWoW64 PROPLUS=1KMSSERVICENAME=”kms.contoso.com” KMSSERVICEPORT=1689

    If the second one would be the right one, the KMS is actually not available over Port 1689, only over 1688.....

    Thanks and best regards



    Wednesday, April 10, 2013 6:21 PM
  • I Sequenced Office 2010 now with the Instructions you provided. I cannot stream the Package to Clients:

     I already installed App-V 5 SP1 but the Error is still existing. It is especially with Office 2010 x86 Package. I have 4 other Packages which are working fine.

    The Cliets get the following Errors:

    Part or all packages publish failed.

    published: 4

    failed: 1

    Please check the error events of 'Configure/Publish Package' before this message for the details of the failure.

    Package {f8ac77f7-0705-4134-a031-66df3b313b22} version {3ad2a574-05c9-47b0-b194-7f0f973cd365} failed configuration in folder 'C:\ProgramData\App-V\F8AC77F7-0705-4134-A031-66DF3B313B22\3AD2A574-05C9-47B0-B194-7F0F973CD365' with error 0x79100710-0xD.

    Some Ideas?

    Thursday, April 11, 2013 11:02 AM
  • Hello,

    See this topic;

    http://www.tmurgent.com/TmBlog/?p=1247

    For us to provide any ideas on the possible error - you need to enable more logging to identify why it fails. The above article explains the steps on howto do so


    Nicke Källén | The Knack| Twitter: @Znackattack

    Thursday, April 11, 2013 11:23 AM
  • Client Orchestration:
    Activity ConfigurePackageFinalize #46 failed on component ScriptManager (error: 0x79100710-0xD).

    ConfigurePackageFinalize activity #46 was failed by component ScriptManager (error: 0x55900C02-0x501), initiating a ConfigurePackageUndo.

    ConfigurePackage activity #46 failed with error code 0x55900C02-0x501.

    Client-Package Config:

    ConfigurePackage derived values: moniker 'F8AC77F7-0705-4134-A031-66DF3B313B22_3AD2A574-05C9-47B0-B194-7F0F973CD365'; package root 'C:\ProgramData\App-V\F8AC77F7-0705-4134-A031-66DF3B313B22\3AD2A574-05C9-47B0-B194-7F0F973CD365\root'; sequenced on 32-bit OS: true

    Thursday, April 11, 2013 12:08 PM
  • OK Thanks guys!
    Just one thing regarding the msiexec Deployment Kit Options. As i said, i have an App-V 5 Sequencer Client on an Windows 7 x64 Machine and want to Sequence Office Professional Plus 2010 x86 (without Visio and Project). Would this be the right msiexec Syntax? :

    msiexec /i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core,OSppWoW64 PROPLUS=1

    or is it:

    msiexec /i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core,OSppWoW64 PROPLUS=1KMSSERVICENAME=”kms.contoso.com” KMSSERVICEPORT=1689

    If the second one would be the right one, the KMS is actually not available over Port 1689, only over 1688.....

    Thanks and best regards



    Provided you have a correctly configured KMS server and you are sequencing on 64-bit you use:

    msiexec /i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core,OSppWoW64 PROPLUS=1

    If you need to specify the KMS server manually because you don't have relevant DNS records then use the other options to set the server name.  If you are using 32-bit then remove the OSppWow64 part.

    Thursday, April 11, 2013 12:48 PM
  • Client Orchestration:
    Activity ConfigurePackageFinalize #46 failed on component ScriptManager (error: 0x79100710-0xD).

    ConfigurePackageFinalize activity #46 was failed by component ScriptManager (error: 0x55900C02-0x501), initiating a ConfigurePackageUndo.

    ConfigurePackage activity #46 failed with error code 0x55900C02-0x501.

    Client-Package Config:

    ConfigurePackage derived values: moniker 'F8AC77F7-0705-4134-A031-66DF3B313B22_3AD2A574-05C9-47B0-B194-7F0F973CD365'; package root 'C:\ProgramData\App-V\F8AC77F7-0705-4134-A031-66DF3B313B22\3AD2A574-05C9-47B0-B194-7F0F973CD365\root'; sequenced on 32-bit OS: true


    Someone an Idea?
    Thursday, April 11, 2013 2:32 PM
  • Client Orchestration:
    Activity ConfigurePackageFinalize #46 failed on component ScriptManager (error: 0x79100710-0xD).

    ConfigurePackageFinalize activity #46 was failed by component ScriptManager (error: 0x55900C02-0x501), initiating a ConfigurePackageUndo.

    ConfigurePackage activity #46 failed with error code 0x55900C02-0x501.

    Client-Package Config:

    ConfigurePackage derived values: moniker 'F8AC77F7-0705-4134-A031-66DF3B313B22_3AD2A574-05C9-47B0-B194-7F0F973CD365'; package root 'C:\ProgramData\App-V\F8AC77F7-0705-4134-A031-66DF3B313B22\3AD2A574-05C9-47B0-B194-7F0F973CD365\root'; sequenced on 32-bit OS: true


    Someone an Idea?

    Have you enabled scripting on the clients?
    • Marked as answer by Cibaay_de Thursday, April 11, 2013 3:25 PM
    Thursday, April 11, 2013 2:39 PM
  • Client Orchestration:
    Activity ConfigurePackageFinalize #46 failed on component ScriptManager (error: 0x79100710-0xD).

    ConfigurePackageFinalize activity #46 was failed by component ScriptManager (error: 0x55900C02-0x501), initiating a ConfigurePackageUndo.

    ConfigurePackage activity #46 failed with error code 0x55900C02-0x501.

    Client-Package Config:

    ConfigurePackage derived values: moniker 'F8AC77F7-0705-4134-A031-66DF3B313B22_3AD2A574-05C9-47B0-B194-7F0F973CD365'; package root 'C:\ProgramData\App-V\F8AC77F7-0705-4134-A031-66DF3B313B22\3AD2A574-05C9-47B0-B194-7F0F973CD365\root'; sequenced on 32-bit OS: true


    Someone an Idea?


    Have you enabled scripting on the clients?

    How can i enable that? In the Sequencing process?
    Thursday, April 11, 2013 2:47 PM
  • Client Orchestration:
    Activity ConfigurePackageFinalize #46 failed on component ScriptManager (error: 0x79100710-0xD).

    ConfigurePackageFinalize activity #46 was failed by component ScriptManager (error: 0x55900C02-0x501), initiating a ConfigurePackageUndo.

    ConfigurePackage activity #46 failed with error code 0x55900C02-0x501.

    Client-Package Config:

    ConfigurePackage derived values: moniker 'F8AC77F7-0705-4134-A031-66DF3B313B22_3AD2A574-05C9-47B0-B194-7F0F973CD365'; package root 'C:\ProgramData\App-V\F8AC77F7-0705-4134-A031-66DF3B313B22\3AD2A574-05C9-47B0-B194-7F0F973CD365\root'; sequenced on 32-bit OS: true


    Someone an Idea?


    Have you enabled scripting on the clients?


    How can i enable that? In the Sequencing process?

    I used following Command: Set-ExecutionPolicy ByPass; Import-Module AppvClient; Set-AppVClientConfiguration -EnablePackageScripts 1

    Its working now!!!!

    Thanks!

    Thursday, April 11, 2013 3:25 PM
  • Hi Guys i have same problem but we dont use KMS activation  I have MAK key my commandline is following 

    msiexec /i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core,OSppWoW64 PROPLUS=1 PIDKEYS=XXXXX-XXXXX-XXXXX-XXXXX USEROPERATIONS=1

    and

    manifestUpdater.exe LICENSE="PROPLUS=1 PIDKEYS=XXXXX-XXXXX-XXXXX-XXXXX USEROPERATIONS=1"

    but it not work for me is there some mistake?

    I'm using windows8x64 enterprise to sequence office 2010 with sp1

    thanks 



    • Edited by OOSOO Saturday, June 01, 2013 8:33 PM
    Saturday, June 01, 2013 11:45 AM
  • I had the exact same problem, running this on the client fixed it immediately.

    I used following Commands:

    Set-ExecutionPolicy ByPass

    Import-Module AppvClient

    Set-AppVClientConfiguration -EnablePackageScripts 1

    • Proposed as answer by jb_pdx Monday, September 14, 2015 11:32 PM
    Monday, August 19, 2013 7:47 PM
  • I am having this same exact issue; however, I have done everything in the App-V 5.0 Sequencing document, and I have enabled Set-AppVClientConfiguration -EnablePackageScripts 1.

    The sequencer is on a Win 7 32-bit machine, so I used the following:

    msiexec /i OffVirt.msi ADDLOCAL=OSpp,OSpp_Core PROPLUS=1

    KMS is registered in DNS, so I shouldn't have to specify KMS.

    As soon as I start Office on a machine, setup screen comes up briefly, and then I see the: 

    "Microsoft Office cannot verify the license for this application. A repair attempt failed or was canceled by the user. The application will now shut down."

    I would use the package accelerator; however, it's a new Pro Plus 2010 build, and it says 12 files are missing from the install (files like the actual OffVirt.msi and manifest files).

    This is getting a little frustrating, as I've already tried the package 4 different times. I also tried this version:

    msiexec/i OffVirt.msi ADDLOCAL=Click2runMapi,Click2runOWSSupp,Click2runWDS,OSpp,OSpp_Core PROPLUS=1

    I am also using the latest SP2 client, Sequencer, and then the AppV 5.0 SP1 server is using the latest hotfix 4 which was released in April 2014.
    • Edited by jrmoat Thursday, May 08, 2014 4:54 PM
    Thursday, May 08, 2014 4:53 PM
  • I think we solved it. All of our machines are Syspreped. When I was sequencing, Office was activating on the machine. On all of the other machines it was giving that error.

    I did sequencing with the network cable unplugged, so KMS wouldn't activate Office 2010. After publishing the package, several Windows 7 and Windows 8.1 machines now can open Office 2010 without a problem!


    • Edited by jrmoat Thursday, May 08, 2014 10:14 PM
    • Proposed as answer by jrmoat Thursday, May 08, 2014 10:25 PM
    Thursday, May 08, 2014 10:14 PM
  • jrmoat,

    You need to separate the proxy and licensing parameters, using two lines.

    Run "msiexec /i OffVirt.msi" twice.

    • Proposed as answer by jrmoat Monday, May 12, 2014 2:48 PM
    Sunday, May 11, 2014 7:12 PM
  • Thank you Ben,

    I had no idea! Great to know.

    Monday, May 12, 2014 2:49 PM