Hey everyone,

I made an Office 2013 Standard package with the Deployment Kit from Microsoft. When I tested it in our environment it worked totally fine. In the configuration.xml I've set a MAK key which appears correctly so that the user can activate Office without any problems. This package is actually for one of our customers so I haven't activated Office but when I looked into the account configuration it said that I can activate my Office 2013 Standard any time. (The setting in my configuration.xml was "StandardVolume" not "ProPlusVolume")

So after I checked that everything was alright with the package I deleted it from the management console of my company and copied the folder with the complete App-V package to the environment of our customers. I added the package in the management console, set the AD-authorization and published the package.

Everything worked fine until I opened one of the applications. After an application like word opened I was immediately prompted to set a valid product key. Since I already set a key which should be activated by the user I was a bit confused. When I looked into the account configuration like I did before it said that I need to change the product key to activate my Office 2013 Professional Plus. The applications which are included in Microsoft ProPlus are not even implemented in my App-V Package...

I've searched for a solution, I even checked if I copied the wrong package but it was definitely the same cause the package Id was identical. I deleted all packages in my management console, deleted the cached packages on my client/terminalserver, used the Microsoft fix it tool to deinstall any office related programs (the tool didn't find anything) and I even reinstalled the client with all the hotfixes. Still it's not working and I have no clue why. Does someone faced the same problem and found a solution or has anyone an idea?

Thanks in Advance

Are you user targeting or machine targeting with the AD groups?

I'm targeting users with the AD groups.

I got a win8 test client in the customers environment and the office 2013 package with the license was delivered  totally fine. Since I only have that issue when using the Terminalserver of our customers the problem is definitely located there. I guess there was another version of office previously installed (most likely 2013 proplus) and there are some registry settings left which cause that license issue.

I'm gonna try to find the problem on the terminalservers which prevents the App-V package from working correctly. When I find a solution I'll post it here.

• Edited by Michael.tec Tuesday, June 30, 2015 12:42 PM

FYI you need to publish Office 2013 globally (AD group containing computers) for the full integration to work correctly. This is the only recommended publishing method by Microsoft.

@Nathan Okay I admit that I forgot that but still it made no difference changing it the problem was still the same and I already searched for left entries in the registry and file system of the terminalservers but haven't found anything so far. I'm out of ideas why the appv package is working fine in my companies environment and on the customers win8 client but not on the terminalservers of my customer. I don't want to reinstall the terminalservers and I'm not sure if I even get the permission to do so.

• Edited by Michael.tec 21 hours 53 minutes ago

On the RDS (Terminal Server) what output do you get if you run this from the command prompt (elevated) "cscript.exe  C:\Program Files (x86)\Microsoft Office\Office15\OSPP.VBS /dstatus" ?

When the App-V Office 2013 package is added, it will use an embedded script event under "AddPackage", that should like something like this in Manifest file:

<appv:AddPackage>
  <appv:Path>"[{AppVPackageRoot}]\..\Scripts\Integrator.exe"</appv:Path> 
  <appv:Arguments>/I /Msi /License /AppV PackageGUID=<PackageGUID> PackageRoot="[{AppVPackageRoot}]" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=<MAK/KMS Key> PRIDName=<Product Version></appv:Arguments> 
  <appv:Wait Timeout="0" RollbackOnError="true" /> 
</appv:AddPackage>

Look in the Manifest file on the RDS server and see if you can see this script event. By default you should find the file in C:\ProgramData\Microsoft\AppV\Client\Catalog\Packages\<PackageGUID>\<VersionGUID>\Manifest.XML.

You could try running the command from command prompt (elevated) manually and see what results you get.

@Nathan I got an error message that it couldn't find a script file but it's working fine now cause the terminalserver were reinstalled by our customers cause of another issue. So the problem really was the terminalserver and not the app-v package itself. When I asked the administrator if there was any office proplus installed before he said no but now he says it could be but it's now working so I shouldn't think about it. Well I can't do anything about it but accept it since I'm not able to reproduce the problem now. Thanks for your informations they'll help me next time I have such a problem.

Thanks for the great help everyone :)

• Marked as answer by Michael.tec 21 minutes ago