Virtual Application: Activation Office 2013

Hello All,
We have created virtual office application as directed in Office Deployment method. In Config.xml we gave "ProPlusVolume" we got out final .appv file
We need to deploy this virtual application to all our clients. We are having a tough time in getting this done.
How do we activate this virtual application?
Some blogs say MAK and KMS cannot be used for Virtual application, it is supported only for Non-Virtual application
is this right? or using KMS we could achieve?
How activation for Office 2013 applications can be achieved using VLSC?
Any help would be greatly appreciated
Thanks!

Hello,
If you are using KMS / AD-based activation I would guess it would detect it automatically.
If using MAK - see the option to use ospp.vbs
http://technet.microsoft.com/en-us/library/dn385359(v=office.15).aspx
I haven't tried the above options, but it would be the most obvious chocies.
Nicke Källén | The Knack| Twitter:
@Znackattack

Similar Messages

Activating Office 2013 for Small Business Scenarios

Some advice required please. We're a small VAR and supply hardware and software to small businesses with no in house IT department.
When customers have purchased Office Licences in the past, we've maintained a log of the number of licences held by a given customer, and a list of licences. This has worked well for Office 2007 and Office 2010.
Please correct me if I am wrong, but I do not seem to be able to activate Office 2013 unless I associate it with a given email address, and I have issues with this approach. It is not ideal in a number of scenarios.
Is there any way to activate Office 2013 without having to associate the licence with a given users email address?
Stuart

No, we don't have to associate the licence with a given users email address.
The method to associate the licence with a email address is one of the available licensing methods, apart from which, we also have the traditional licensing method that is using product key.
For more licensing and purchase related topics, I'd suggest you to contact the Customer Service to obtain help:
http://www.microsoft.com/licensing/how-to-buy/how-to-buy.aspx
Also check the Buyer's guide:
http://www.microsoft.com/licensing/about-licensing/office.aspx
Max Meng
TechNet Community Support

Printing causes Office 2013 applications to crash

We’ve a fresh installed Windows 8 Pro and Office 2013. Printing works correctly in every application but Office 2013.
Word, Excel, Outlook … printing causes the application to crash.
Any idea if this is a known issue?
Regards.
Peter
Peter Van Keymeulen, IT Infrastructure Solution Architect, www.edeconsulting.be

This is the answer that fixes the problem every time, based on my experience and that of others. It works for both the 32 & 64-bit versions of Windows (I'm one of those odd ducks who runs 32-bit Windows 8.1 Professional and it worked perfectly for me).
The problem is not Windows, either 7 or 8, it's Office 2013 and a variety of unique HP LaserJet printers. By the way, the glitch occurs whether you use networked printing or a USB cable; I discovered that early-on when I
was trying to troubleshoot the issue. Also (and it should go without saying), always reboot the computer after you make the change to the driver. Thanks to Shane, who apparently was the first one to discover the solution over a year ago, right
after Office 2013 came out and the problem manifested itself.
After lots of testing I have found a setting that has fixed all my HP CP5520 and HP M4555 printers that were crashing when printing from Office 365's 2013 pro plus.
It's the driver setting in Device settings -> Installable options -> Printer Status notification, this needs to be disabled.
I hope this also fixes other peoples problems.
Shane

Office 2013 deployment tool Invalid product ID error

Hi,
Im in the process of virtualizing apps like Office 2013 with App-V.
Downloading the binaries with the Office Deployment tool and converting to app-v package is very easy, I've followed this kb
http://support.microsoft.com/kb/2915745
But now I want to sequence add-ins for Office 2013. So I need a local install of Office 2013 click to run.
Im trying to use the command line option setup.exe /configure <path to config.xml> but everytime I try this I receive this error:
Invalid product ProPlusVolume specified. Error configuring products
I have tried several different ProductID's like ProPlusVolume and StandardVolume. None of the volume ID's seem to work. When I changed the ID to ProPlusRetail, the setup worked flawless. But I need to install the Volume version for my RDS server...
I have found other people in the comment section in this blog: http://blogs.technet.com/b/office_resource_kit/archive/2013/12/03/3615124.aspx
(read the comments in the bottom section) But no solution..?

It's my understanding that you don't use the "/configure" parameter when using the "Volume" options.
Jeremy refers to this in the comments/responses.
In the main blog article, he refers to "You can now use the Deployment Configuration file to configure...."
This does not mean that you should use the "/configure" parameter - that is only used for C2R.
Don
(Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

Office 2013 (local) vs. Office 365 (cloud)

For the moment we are primarily interested in using the main Office 2103 apps from the user Desktops. (We do not want users to even store documents on the cloud)
1. Is there a URL indicating the feature differences between local and cloud Office 2013?
2. If we install the suite locally and Microsoft updates the cloud based version, I presume our local verisons will
not be updated automatically. Is that correct?
TIA,
edm2

FWIW, Office 365 desktop applications are Office 2013 and are installed locally, on your desktop, just like every other previous version. Storing documents in the cloud is optional with all versions of office, either subscription or the perpetual license
version.
1. Which office suite are you looking at? The subscription is office pro plus. See http://products.office.com/en-us/buy/compare-microsoft-office-products for the non-subscription offers. Also, the perpetual license doesn't get a license for ipad/android
tablets.
2. You'll be able to install updates as you do now using windows updates, but the updates may not be available for days or weeks after the click to run versions. (So far this isn't happening, but it could in the future.)
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter

Re-installing Office 2013

I have had some issues with Windows 8.1 on my Sony laptop, and Sony has told me that they recommend doing a factory reset on my computer and re-installing windows 8.1. I am concerned because I have Office 2013 installed on my computer, and my University
only gives us one free installation code. Will my activation code work when I re-install Office?

Hi,
Don't worry, if you reinstall Office 2013 on the same PC and you’re connected to the Internet, activation will happen silently.
The Activation Wizard will appear if you've made significant changes to the hardware on the PC.
Anyway, if you have trouble activating Office 2013, please contact Customer Service and explain to the service (human beings) your scenario.
You can find your local custom support number on the link below:
http://support.microsoft.com/gp/customer-service-phone-numbers/en-us
Hope this can help.
Regards,
Melon Chen
TechNet Community Support

Affects when migrating from Office 2013 to Office 365

I currently have office 2013, with two email addresses being used in Outlook. I need to download Office 365 which I have already purchased. Will this have any affect on my two Outlook email addresses, and all the emails that are there?

Hi,
The activation and licensing are different between the Office 2013 and Office 365. We can't just
switch activated Office 2013 to Office 365. We can only uninstall Office 2013 and then install Office 365. In theory, we won't lose any emails in the email accounts configured in Office 2013. Just in case, we can back up your Outlook data files
of the two email accounts and then conduct the migration. To back up the data files, please refer:
http://support.microsoft.com/kb/287070/en-us
Hope this helps.
Regards,
Steve Fan
TechNet Community Support

Adobe Creative Suite MS Office 2013 Capability

Hi,
Please advice if you have any concerns ref. the applications Adobe Creative Suite.   Can you please advise if,
•     Whether your application has anything to do with MS Office, if so
•     your applications are Office 2013 certified, if so which version

Hi Mylenium,
Thanks for the reply. As I am aware under Adobe Creative Suite Master Collection - Adobe Dreamweaver, Photoshop have Office addins.
I am wondering whehther these addins still work with Office 2013 and if so, which version is certifed with Office 2013
Thanks
Zoe

How to add MS Office add-in from inside a Thinapp 5 virtual application to a MS Office 2013 suite that is installed on a base image

Hi,
We have the following solution:
VMware Horizon View 5.3.1
Non-persistent Linked-clone pool with delete VM after logoff
Windows 8.1 Update 1 Enterprise 64 bit
MS Office 2013 32-bit installed on image
Thinapps registered for each user from logonscript with thinreg.exe command. Thinapps is located on a network share
Native Windows roaming profiles with appdata/roaming, appdata/local without appdata/locallow(persona management does not support Windows 8.1 in View 5.3.1)
This is our issue:
We have a 3rd party application with a couple Thinapp entrypoints(exe files) and in the Thinapp package process we also installed Office addins. We tested that the Add-ins was opened inside Outlook, Word and Powerpoint before post installation scan.
The problem is that the add-ins is not added to Office 2013 before or after the Thinapp is started on a test client.
I have tried several changes in the package.ini and virtual filesystem attributes(no registry changes yet):
Package.ini:
ChildProcessEnvironmentExceptions=WINWORD.EXE;EXCEL.EXE;POWERPNT.EXE;OUTLOOK.EXE;
ChildProcessEnvironmentDefault=External
ChildProcessEnvironmentExceptions=excel.exe;outlook.exe;powerpnt.exe;winword.exe
ChildProcessEnvironmentDefault=Virtual
VirtualizeExternalOutOfProcessCOM=0
DirectoryIsolationMode=Merged
RegistryIsolationMode=Merged
I have also read that you could make entrypoints to the locally installed Office 2013, but I get errors on the build process. ref. link: http://edwinfriesen.nl/content/?p=105#comments
The best thing would be if the add-ins were added in the logon process together with thinreg.exe, but if that is not supported, the add-ins must be added to Office either in a custom Office shortcut/entry point or after starting the Thinapp virtual application.
Remember that the application needs to registered every times the user logon, because we use a non-persistent View pool.
I would really appreciate if somebody could tell me how to add Office add-ins from inside a Thinapp virtual application/package to a locally installed MS Office 2013 suite on a Windows "base" image?
We do not want to add the whole Office suite to the Thinapp virtual package and not add the add-ins trough GPO,SCCM etc.

What about the COM object parameters in package.ini ?
We can live with scripting in logon or changed logon scripts etc.
And you don't no need to lock in the project files.
From package.ini documentation:
ObjectTypes Parameter
The ObjectTypes parameter specifies a list of virtual COM object types that are visible to other applications in
the physical environment. You can use scripts, such as VBScripts, to call objects that start captured applications.
An object type is registered to only one native or virtual application at a time. If you install Office 2003 on the
native machine and want to use a virtual Office 2007 package, you must determine whether to have the virtual
or native application handle the object types.
If you want the virtual Office 2007 to handle the object types, you can leave the ObjectTypes setting in the
Package.ini file, build the package, and register it using the thinreg.exe utility. If you want the native Office
2003 to handle the object types, you must remove the ObjectTypes setting from the Package.ini file before
building and registering the package.
You cannot add random entries to the ObjectTypes parameter.
You can only remove entries that were generated by the capture process.
Example: Starting a Virtual Application When a COM Object is Created
If a script or a native application creates an Excel.Application COM object or other COM objects listed in the
ObjectTypes parameter, ThinApp starts the virtual package.
[Microsoft Office Excel 2007.exe]
ObjectTypes=Excel.Application;Excel.Application.12;Excel.Chart;
Excel.Macrosheet;Excel.Sheet; Excel.Workspace

0x87D01280 "Virtual application is currently in use" error when uninstall App-V Office 2013 in Software Center

Getting the above error message when attempting to uninstall Office 2013 App-V version (downloaded using ODT) in Software Center. There are no office 2013 or App-V processes showing as running in Task Manager. Nothing in event viewer to show what is running
either. Any idea on what could be running and holding the uninstall from completing?

Hello,
These issues are caused if the virtual package is used during the attempt to uninstall.
SFTMIME is a legacy command-line interface for App-V 4.6, not supported for usage with App-V 5 (which is the only version that supports Office 2013).
App-V 5.0 SP2 has introduced the ability to divert required actions to next logoff / reboot depending on publishing, if the package is in use.
See these articles;
http://www.applepie.se/app-v-5-0-sp2-and-pending-removal-update
http://blogs.technet.com/b/virtualvibes/archive/2013/12/03/pending-tasks-in-app-v-5-0-sp2.aspx
Nicke Källén | The Knack| Twitter:
@Znackattack

Microsoft Office can't find your license for this application - multiple copies of Office 2013 x32 failing to start, Software Protection Service timing out

We're experiencing a growing problem with our users in several different domains running in to Microsoft Office 2013 x32 'activation' issues. We use KMS for licensing, which works properly, but some of the machines (~20-30 out of 1000+) sporadically
throw the following error:
'Microsoft Office can't find your license for this application. Microsoft Office will now exit.'
We know it's not an issue with the licenses per se, since they work on and off and we can force KMS activation correctly / talk to the KMS servers.
It appears to be an issue with the Software Protection service not starting properly. In Event Viewer, we see the following:
'Software protection service failed to start due to the following error- the service did not respond in a timely fashion.
Event 7000'
This is occurring on a variety of machines in a variety of environments, all fully patched with the latest Office updates. It's inconsistent, and the 'manually restart the Software Protection Service' solution is not viable as it's occurring on many
different workstations. Office repairs have also been unsuccessful.
Has anyone else come across this? Or have any idea why the Software Protection Service might be sporadically failing? Maybe an Office update in the last 2-3 months?
Thanks for any info.

We're experiencing a growing problem with our users in several different domains running in to Microsoft Office 2013 x32 'activation' issues. We use KMS for licensing, which works properly, but some of the machines (~20-30 out of 1000+) sporadically
throw the following error:
'Microsoft Office can't find your license for this application. Microsoft Office will now exit.'
We know it's not an issue with the licenses per se, since they work on and off and we can force KMS activation correctly / talk to the KMS servers.
It appears to be an issue with the Software Protection service not starting properly. In Event Viewer, we see the following:
'Software protection service failed to start due to the following error- the service did not respond in a timely fashion.
Event 7000'
This is occurring on a variety of machines in a variety of environments, all fully patched with the latest Office updates. It's inconsistent, and the 'manually restart the Software Protection Service' solution is not viable as it's occurring on many
different workstations. Office repairs have also been unsuccessful.
Has anyone else come across this? Or have any idea why the Software Protection Service might be sporadically failing? Maybe an Office update in the last 2-3 months?
Thanks for any info.

Activating MS Office 2013 ProPlus via KMS running on the same server

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Given: Microsoft Windows Server 2008 R2 Enterprise 64-bit, all the latest security updates applied.
KMS service set up and running, all the recommended updates applied (to handle possible activation issues for Windows 8 etc)
Microsoft Office 2013 Standard deployed on the server mentioned above and on workstations on intranet, volume licensing in effect (proper KMS key for activation of Microsoft Ofice 2013 has been entered).
Problem: I can't activate MS Office 2013 installation running on the same server where KMS service is being run.
There are no entries in KMS event log related to this failure.
Everything was restarted, reinstalled etc several times already (including installing 32-bit and 64-bit versions of the Office).
Output of slmgr.vbs /dlv 2E28138A-847F-42BC-9752-61B03FFF33CD:
Windows Script Host
Software licensing service version: 6.1.7601.17946
Name: Office 15, KMSHostVL edition
Description: Office 15, VOLUME_KMS channel
Activation ID: 2e28138a-847f-42bc-9752-61b03fff33cd
Application ID: 0ff1ce15-a989-xxxx-xxxx-xxxxxxxxxxxx
Extended PID: 55041-00206-234-486666-03-xxxx-xxxx.xxxx-xxxxxxx
Installation ID: 01683679734050124078134659xxxxxxxxxxxxxxxxxxxxxxxxxxx
Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88342
Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88343
Use License URL: http://go.microsoft.com/fwlink/?LinkID=88345
Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88344
Partial Product Key: xxxxx
License Status: Licensed
Remaining Windows rearm count: 4
Trusted time: 2/05/2015 10:00:12 AM
Key Management Service is enabled on this machine
Current count: 0
Listening on Port: 1688
DNS publishing enabled
KMS priority: Normal
Key Management Service cumulative requests received from clients
Total requests received: 0
Failed requests received: 0
Requests with License Status Unlicensed: 0
Requests with License Status Licensed: 0
Requests with License Status Initial grace period: 0
Requests with License Status License expired or Hardware out of tolerance: 0
Requests with License Status Non-genuine grace period: 0
Requests with License Status Notification: 0
OK
Output of cscript ospp.vbs /dstatus
Microsoft (R) Windows Script Host Version 5.8
Copyright (C) Microsoft Corporation. All rights reserved.
---Processing--------------------------
SKU ID: b13afb38-cd79-4ae5-xxxx-xxxxxxxxxxxx
LICENSE NAME: Office 15, OfficeStandardVL_KMS_Client edition
LICENSE DESCRIPTION: Office 15, VOLUME_KMSCLIENT channel
LICENSE STATUS: ---OOB_GRACE---
ERROR CODE: 0x4004f00c
ERROR DESCRIPTION: Run the following: cscript ospp.vbs /ddescr:0x4004f00c
Last 5 characters of installed product key: GVGXT
DNS auto-discovery: KMS name not available
Activation Interval: 120 minutes
Renewal Interval: 10080 minutes
KMS host caching: Enabled
---Exiting-----------------------------

Office 2013 applications cannot be made to show the "Documents" folder when opening and saving files

(Windows Server 2012R2 and Windows 8.1 PRO)
We are redirecting the user's "Documents" folder to the network (using Folder Redirection). The OS hides this fact however, and most applications simply see the "Documents" folder when opening or saving files, including Office 2003.
Office 2013 however displays the actual path, which in this case is:
\\sever1\redirect$\username\documents
Even if you forcibly set the "Default local file location:" in the Options Save area to the 'Documents' folder in, say, Word, Word immediately converts the local path to the network path.
Is there anyway to get Office 2013 to follow the virtual path? All of other apps follow it and expose the users only to "Documents".
Thank you so much.
Dana

There's nothing in my FAQ concerning screen savers, so I'm unsure why you decided to take that approach. From your description, it looks like you only tried a few of the suggestions before throwing in the towel. That's fine, it's your call.
I don't have the problems you described with 10.4.7. Usually when folks have problems after an update, these are caused by either installing an update on an already-corrutped system or they've installed third-party applications or hardware that have been rendered incompatible by the update.
Before installing software updates, you may wish to consider the advice in my "Installing Software Updates" FAQ. Taking the steps therein before installing an update often helps avert problems and gives you a fallback position in case trouble arises.
Good luck!
Dr. Smoke
Author: Troubleshooting Mac® OS X
Note: The information provided in the link(s) above is freely available. However, because I own The X Lab™, a commercial Web site to which some of these links point, the Apple Discussions Terms of Use require I include the following disclosure statement with this post:
I may receive some form of compensation, financial or otherwise, from my recommendation or link.

App-V 5.0: Adding Visio 2013 and Project 2013 to a previously deployed virtual Office 2013

Good morning.
I can successfully deploy Office 2013 via PowerShell and App-V v5.0 without difficulty. I've read the document at
http://support.microsoft.com/kb/2915745/en-us and followed all instructions successfully.
My question is this: If Office 2013 without Visio 2013 or Project 2013 is virtually deployed, how can those components be added later?
For instance, we may have 100 users that acquire a virtualized Office 2013 without Project or Visio. We then may have 25 users that require a virtualized Office and Visio without Project and, perhaps, another 15 that require Office and Project without
Visio.
Currently, when I attempt a second virtual deployment of one of these components, it removes Office 2013 making it inaccessible.
How can Project and/or Visio be deployed to an already existing virtually deployed Office 2013?
Thanks very much.
John
IAmStrings

As a part of MDOP, you'll also have access to UE-V which will provide a mechanism of moving user preferences across the same applications from difference packages.
It will require planning, configuration and deployment, but will ensure you don't face the same issue in the future.
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

App-V 5.0 MAK activation in Office 2013

Hi,
I created a App-V package for Visio and Project 2013 Standard Edition using ClicktoRun Office Deployment Kit. Now i have the Keys. How can i implement the MAK activation in the App-V package. Is there any thing that i can do in the configuration file. Please
help me.
Thanks,
Prem

Are you also virtualizing Office 2013?
Are they in separate packages from Office 2013? I think the packages are only supported if they're in a single package.
Test by creating an Office 2013 package with Project and Visio and see whether that activates successfully.
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

Virtual Application: Activation Office 2013

Similar Messages

Maybe you are looking for