Office 2013 partialy virtualized breaks Outlook2013

Hi,
We tryed to virtualize Access Visio and Project 2013 in one package using the Click to Run method. For this method we made a xml file with the following content:
<Configuration>
    <Add SourcePath="C:\Temp\Project\Download" OfficeClientEdition="32" >
    <Product ID="ProPlusVolume" >
      <Language ID="nl-nl" />
      
<ExcludeApp ID= "Outlook" />
      <ExcludeApp ID= "Excel" />
      <ExcludeApp ID= "Groove" />
      <ExcludeApp ID= "InfoPath" />
      <ExcludeApp ID= "Lync" />
      <ExcludeApp ID= "OneNote" />
      <ExcludeApp ID= "PowerPoint" />
      <ExcludeApp ID= "Publisher" />
      <ExcludeApp ID= "SharePointDesigner" />
      <ExcludeApp ID= "Word" />
    </Product>
    <Product ID="ProjectProVolume" >
      <Language ID="nl-nl" />
      
    </Product>
    <Product ID="VisioProVolume" >
      <Language ID="nl-nl" />
      
    </Product>
</Add>
  
<Display Level="None" AcceptEULA="TRUE" />
  <Logging Name="Office2013Setup.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
When using this xml to download and build the appv package the ExcludeApp tags seem to be ignored. I end up with a package containing all parts. But this is only problem 1 there is a second problem: When the AppV package is deployed on a machine with Outlook
2013 and installed in the base image with the Office 2013 installer. Then each time Outlook is started it gets repaired. When the AppV is unpublished this behaviour stops.
The question i have is it supported to deploy Office 2013 half native and half as AppV on the same system. This sounds wierd but many organisations only want part of their employers to have tools like Access. In case of deploying on terminal server it is
nice to give most users the base like Outlook,Word,Excel and Accessruntime. And some privileged users the Access,Visio Project AppV package as addition.
Is this scenario possible with AppV 5 or should all parts be installed native and use a some sort of user profile control to control who gets what?
regards,
Leon.

Use a clean machine for ODT, I use a VM with snapshots.
See:
https://social.technet.microsoft.com/Forums/en-US/2bda7882-80d1-4ebc-a6e8-32d47f74aaad/office-2013-packageguid?forum=mdopappv#9c5478e8-9cac-434d-bd50-f59b0aae13f7

Similar Messages

Office 2013 Installation stuck on Windows 8.1 ESXi virtual machine

When I try to install Office 2013 32 Bit - on a Windows 8.1 64 Bit Virtual Machine that is hosted on ESXi Host server .....it stucked installing it for hours and hours without finishing ....... I tried to install locally on a mounted ISO image with the same
result !!
It happens on many machines not a specific one !
Does any one know what can be a reason for that ?!
Hossam Wael Elmosallamy (IT Support Engineer-ECC Solutions) MCSE - CCNA [email protected] Mobile:(011)-49464671 www.eccsolutions.net "Experience Reliability&quot

Hi,
At which specific percentage will the setup hang? Vuk is right above, but it's really hard to say what's the cause of your case.
Please first take a look at this KB article and see if it is helpful for you:
Microsoft Office 2013 or Office 365 hangs during setup
I would suggest you go and check the setup log files to troubleshoot the issue, which is the best way to narrow down the issue I think.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

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

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

Office 2013 breaks vfpoledb ?

Hi
I've used this function for getting vfp data into Word (up to Office 2010) for a long while :
.ActiveDocument.MailMerge.OpenDataSource(lcDBPath,0,0,0,0,0,"","",0,"","",lcConnect,lcSQL)
... now with 32-bit Word 2013 it always breaks and I get a dialog 'Could not find installable ISAM'.
I have the latest version of vfpoledb installed.
In further testing, if in Word or Excel I open the data connection wizard, choose 'Other/advance' and then select 'Microsoft OLEDB Provider for Visual Foxpro' and click 'Next ' I always get 'Microsoft Excel (/Word) has stopped working': ie a crash!
I've tested this out on 3 different machines with Win7 and Win8 installed and always get the same result. Other OLEDB providers all work fine.
I could of course work around this, but I'm interested to know- does vfpoledb just not work with Office 2013, or is there some workaround, or ... ?
Brian Abbott
Brian Abbott

OK I've been doing a bit more experimenting.
In Word 2010 this string works:
.ActiveDocument.MailMerge.OpenDataSource(lcDBPath,0,0,0,0,0,"","",0,"","",lcConnect,lcSQL)
... where
lcConnect = "DSN=Visual FoxPro Database;UID=;PWD=;SourceDB=" + lcDBPath + ;
";SourceType=DBF;Exclusive=No;BackgroundFetch=Yes;Collate=Machine;"
As you say Olaf this in fact uses the DSN - that is, ODBC (something that had escaped me, I for some reason thought it was using OLEDB - though since I wasn't using any VFP6+ table features that didn't matter).
With Word 2013 the above doesn't work but I eventually found that it can be made to work by changing the .Opendatasource call very slightly:
.ActiveDocument.MailMerge.OpenDataSource("",0,0,0,0,0,"","",0,"","",lcConnect,lcSQL)
(that is, the first parameter is empty rather than specifying the source DBF location).
Separately to this, is the issue of a call to VFPOLEDB from Word.
In Word 2010 I can select VFPOLDB and it generates an .odc file whose meat is this:
<meta name=SourceType content=OLEDB>
<meta name=Table content=tosend>
<title>(Default) tosend</title>
<xml id=docprops><o:DocumentProperties
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns="http://www.w3.org/TR/REC-html40">
<o:Name>(Default) tosend</o:Name>
</o:DocumentProperties>
</xml><xml id=msodc><odc:OfficeDataConnection
xmlns:odc="urn:schemas-microsoft-com:office:odc"
xmlns="http://www.w3.org/TR/REC-html40">
<odc:Connection odc:Type="OLEDB">
<odc:ConnectionString>Provider=VFPOLEDB.1;Data Source=D:\VFP\WINSIMS;Mode=Share Deny None;Extended Properties="";User ID="";Mask Password=False;Cache Authentication=False;Encrypt Password=False;Collating Sequence=MACHINE;DSN="";DELETED=True;CODEPAGE=1252;MVCOUNT=16384;ENGINEBEHAVIOR=90;TABLEVALIDATE=3;REFRESH=5;VARCHARMAPPING=False;ANSI=True;REPROCESS=5</odc:ConnectionString>
<odc:CommandType>Table</odc:CommandType>
<odc:CommandText>`tosend`</odc:CommandText>
</odc:Connection>
</odc:OfficeDataConnection>
</xml>
... and this works fine.
With Word 2013, on several different machines, it always breaks at the point when I specify VFP OLEDB in the dialog. (I don't have Office 2007 so can't test that).
Brian Abbott

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

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

Add font for virtualized Office 2013

Hi,
I need to add a font for Office 2013.
Usually, a font should be added to Windows\Fonts. I believe it should work for virtual Apps too?
Can we do it on package level?
Thanks.
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Generally you can add fonts to app-v packages.
Tim Mangan did some research on the pulishing performance of that and also documents some background information: http://www.tmurgent.com/appv/index.php/resources/research/293-deploymentperformance
However: As the Office 2013 App-V package can't be modified with the Sequencer, you'd have to find other methods. One would be to copy/install the Font inside the virtual package using a DeploymentConfig, or you install the Font locally - maybe also using
the DeploymentConfig.
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

Replace Scenario : USMT Break Office 2013

Hi guys, in the midst of a project to refresh client Operating Systems - the refresh involves using the User State Migration Tool version 5 to capture user settings/preferences and data from old devices and restore to new machines once the Operating
System and applications such as Office are deployed.
SCCM infrastructure is 2012 SP1. Source/old machines are running Windows Vista or Windows 7, Office 2007 and have the Enterprise Vault Add-In for Outlook version 9.0.2.1136. Target/new machines have Windows 7 SP1, Office 2013 and Enterprise Vault Add-In
for Outlook version 10.0.3.1090. All operating systems are 32-bit.
USMT 5 has been extended with the hotfix for Office 2013 (new MigApp.xml) - otherwise the capture is effectively vanilla.
On machines where the User State Migration Tool is used every time Outlook is opened the following error is presented:
Either there is no default mail client or the current mail client cannot fulfill the messaging request.
If Outlook is started using outlook.exe /safe it opens without issue. If I disable the Enterprise Vault Add-In within Outlook, it opens without issue.
I’ve been through the following to no avail:
http://support.microsoft.com/kb/813745
http://www.symantec.com/business/support/index?page=content&id=TECH20486&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1377114331330xz9e5SBBuT28VInhuBHCHNIlGKF39rjY1sr1c
Removing the Enterprise Vault Add-In and re-installing doesn’t resolve the issue, neither does the ResetEVClient.exe utility.
Run fixmapi.exe to no avail.
A repair of Office itself fixes the problem, however this is not feasible across the thousands of machines we're looking to migrate!
What we have noted is that the issue affects every Windows profile on the machine, those copied over by the User State Migration Tool, but also new ones - so whatever is occurring is breaking Outlook/the Enterprise Vault Add-In for the machine, not a specific
profile.
Finally, if we don't use USMT (not viable on the number of machines we have to replace!) I'm able to logon, and under a fresh user profile can open Outlook without issue.
If anyone has any ideas please let me know!
MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Finally have a workaround - known error caused by USMT. Working with MS PSS modification of the following reg key will resolve the issue without an Office repair:
HKLM\SOFTWARE\Clients\Mail\Microsoft Outlook\MSIComponentID
Set this to the following value to resolve the issue: (6DB1921F-8B40-4406-A18B-E906DBEEF0C9}Initial tests excluding this from capture/restore via a custom XML but this doesn't seem to work.
We're now using the following Run Command Line step in the USMT Task Sequence to resolve the issue:
reg add "HKLM\SOFTWARE\Clients\Mail\Microsoft Outlook" /v MSIComponentID /t REG_SZ /d {6DB1921F-8B40-4406-A18B-E906DBEEF0C9} /f
MCTS 70-640 | MCTS 70-642 | Prince2 Practitioner| ITIL Foundation v3 | http://www.cb-net.co.uk

Windows Updates keeps BREAKING Office 2013, SkyDrive, ETC

Everytime I do the Updates my system and Office 2013 becomes completely unstable.
As a result I only do upgrades every 2 weeks. On Friday, April 24 I sat down to do my 2 week update and had almost 40 updates that had to be done. (goodbye 4 hours of my life)
After the updates, just like clockwork, office, sharepoint and onedrive stopped working. I am going to try to provide as much detail as possible so as to notify Microsost in hopes this stop and in case anyone else has the issues. I will also provide
the steps I took to fix some of the issues.
Note:
I am running Windows 8.1, 64-bit on HP-ENVY 17" touch laptop
I DO NOT have any virus', malware, etc. I have ran MalwareBytes, Windows Defender and Webroot (as I always do before and after updates)
I have office 2013 and subscribe to office 365 for business - I have a license key for Office 2013 but was told somewhere that it conflicts with the click-to-run we are forced to use with 365 so I only do the office 365 version
I do have Sharepoint Designer on my system as I am the administrator of our sharepoint site
I access our sharepoint documents via Windows Explorer
After the updates I have experienced the following
I tried to open a ppt, xls and doc file and nothing would open giving random errors. I then did the control panel --> office click to run --> change --> reinstall everything. I did this and then some of the documents opened fine (goodbye
another hour of my life)
After trying to open a file from my windows explorer in our sharepoint site I get a continuous and recoccuring popup from Microsoft OneDrive for Business that says "Sorry, we can't perform this action. Incompatible Office Products are installed
on your machine. If you have an administrator, please contact them for help." (The last part just makes me laugh because I AM the administrator)
This annoying popup NEVER stops. It keeps popping up every 60 seconds if I close it. I have kiiled the onedrive process, paused the syncing, killed the office click-to-run task. Shut down all office products. Nothing makes this stop except for a full reboot
Please HELP or tell me what to do so that I can once again open my sharepoint files (and all of my employees can do so as well!)

Hi,
"I tried to open a ppt, xls and doc file and nothing would open giving random errors." Could you please provide some of these errors to me? Then I can do some research based on the errors.
Based on your error message, please make sure you have installed this update:
February 10, 2015 update for Office 2013 (KB2920798)
We can also collect some event logs after the issues occur, press Win + R, type "eventvwr" in the blank box, press Enter.
Browse to Windows Logs -> Application, check if there are any logs about the issue.
You can send the logs to our email address, we will then help analyze the information. Please send the logs to this email address below:
[email protected]
Please add this thread's url in the email for easy tracking.
Regards,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here.

Excel COM object calls break with Office 2013 upgrade on 64-bit OS?

Out of the 1000+ computers in the company mine is the only one running 64-bit windows 7. I have noticed that when i try to run a small DLL i created to convert Excel files to Tab Delimited files it is crashing only on my computer.
I have debugged the source code and found that there is no real exception being thrown except a popup does appear in the background stating "We're sorry, but Excel has run into an error that is preventing it from working correctly. Excel will need to
be closed as a result. Would you like us to repair now? [Repair Now][Help][Close]"
If i open excel via the main application this same popup comes up and when i click repair excel closes. when re-opened Excel re-activates and then works fine.
here is a sample of my (VERY simple) code which has worked for years on office 2007 with 64-bit OS:
Dim excelPath As String = "C:\test.xlsx"
Try
objXL = CreateObject("Excel.Application")
With objXL.Application
.displayalerts = False
.Visible = False
.workbooks.Open(excelPath)
.Workbooks(ExcelFileName).SaveAs(csvPath & csvFileName, Excel.XlFileFormat.xlCurrentPlatformText, , , , , Excel.XlSaveAsAccessMode.xlNoChange, , , , , )
.workbooks(csvFileName).Close(csvPath & csvFileName, savechanges:=True)
End With
Catch ex2 As Exception
Throw ex2
Finally
objXL.Quit()
objXL = Nothing
End Try
I have isolated the exact line that is causing the exception to be thrown...
.Visible = False
Why would hiding the Excel UI cause an error of "We're sorry, but Excel has run into an error that is preventing it from working correctly" to be displayed?
If i remark out this line then the application seems to work properly for me...

That I do not know. Do you have another machine where Office 2013 is installed, and where you can test? It could be system configuration issue, could be a change in the application behavior or a difference between 32-bit and 64-bit. You are updating
at least a couple of generations of software and now running in a 64-bit environment so there is always the potential for changes in behavior and software defects.
Unfortunately, I do not have Office 2013 64-bit installed so I cannot test this scenario.
You could also try posting to the
Excel for Developers forum to see if anyone has encountered the same issue when using Excel automation.
Paul ~~~~ Microsoft MVP (Visual Basic)

Office 2013 app-v packages

In this article, http://blogs.windows.com/itpro/2013/12/02/announcing-mdop-2013-r2/   I see mention of an Office version called "Office 2013 ProPlus
App-V Package".    Is this a download? I don't see it available as one when I login to my VLSC site.
We plan to install Office 2013 pro plus VLA LOCALLY (on C:) in our vdisk for virtual machines, but will want to stream Visio,Project,Access 2013 to our users' VMs, using App-V.    (We used to use Citrix XenApp to stream them)
In the Citrix world, "streaming" is the opposite of Publishing or Hosting (running the app ON the server). Streaming means it copies over the files to the user's C: drive on their VM when they launch the appl.
Please advise.

Hi,
As far as I know, Microsoft Office 2013 App-V packages are created by using the Office Deployment Tool (ODT). The created packages may have Subscription Licensing or Volume Licensing.
You need to download Office applications through the ODT first, then convert it into an Office 2013 App-V package with ODT tool.
For more details, please refer to this KB article:
http://support.microsoft.com/kb/2915745/en-us
More reference:
Supported scenarios for deploying Microsoft Office as an App-V package:
http://support.microsoft.com/kb/2772509/en-us
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Office 2013 Std (local) in combination with Office 2013 Pro (App-V)

Hello,
I have multiple RDS servers, that have Office 2013 Std installed locally. I did this on purpose, after reading some blogs pointing out Office 2013 is a complicated applicatie to stream well. And of course Office 2013 is highly critical to my clients.
So I have a local installation of Office 2013 Std on every RDS server.
The catch is, that the client also has an open license for Office 2013 Pro. This is because some users need to work with 'Access 2013'.
So I thought it would be nice to use App-V to stream Access 2013 to the RDS servers. I have created the package for Office 2013 Pro, with Access in it. And I succesfully published Access 2013 to the group of users. So I can use Access on the RDS servers.
The problem is, that when I click on the appliation "MSACCESS.exe", the application pops up in taskmanager and is immidiatly shut down again. So it never launches. No error, no nothing.
I can't find any directions in the server, applicatie or App-V logs in the eventviewer. Does anyone have a clue where to look?
Thanks in advance

I think to be on a safe side, using a 'true' control system like AppSense or using dedicated RDS servers would be the only legally valid option.
Even when Office (or at least Access) is virtualized, the licensing part and product key handling is done natively on the RDS servers by the 'Office 2013 Deployment Kit'. Besides others this includes a locally installed 'licensing stump'. Therefor there
can be only one Office Suite product key be assigned to a RDS server machine.
In fact you could tell the Deployment Kit to use the Office Pro key (allowing a virtualized Access to run), but then also the locally installed Office Version would (attempt to ) be licensed as 'Pro'. That potentially won't work. In fact you could re-configure
the local Standard Office installation to consume Pro licenses, but that doesn't fit to your legal licenses.
As Aaron write, legally an Office license is bound to the endpoint device, so you'd have to make sure that your Access App-V package can only be access by permitted client machines. And while App-V can filter application on the accessing user and the executing
machine, it can't filter on the accessing end-point.
Though we don't like it... 3rd party or a server silo seem the way to go.
Falko
Twitter
@kirk_tn   |   Blog
kirxblog   |   Web
kirx.org   |   Fireside
appvbook.com

Office 2013 Click-to-Run

All,
We are having issues with some customers that have the Office 2013 Home and Business Click-to-Run version of office installed. Users are randomly having their installation corrupted. This interestingly enough didn't start happening until SP1 was released
for Office 2013. I am aware that click-to-run installations of office don't update via Windows Updates direct but through another method. Is anyone else seeing this happen? Any thoughts would be appreciated.
Some of the symptoms are as follows:
1. None of the Office apps open. You double-click but nothing happens nor are there any processes running.
2. If you open an office document direct you might get a message something to the effect of There was a Problem sending the command to the program. None of the documented fixes appear to correct the issue for this type of error.
3. A system restore point fixes it but it breaks again within a day or two.
4. The only fix at this point is to uninstall (Using FixIt KB2739501) and reinstall which of course pulls down the latest build with SP1.

Hi,
You can probably fix the issue by updating the video driver to the latest.
Please refer to this thread below, many users had the same issue and solved it by updating the video driver:
http://social.technet.microsoft.com/Forums/en-US/34401d63-6c3b-47e6-ab20-9ed9b70d890b/outlook-2013-sp1-unusable-since-sp1-update-?forum=officesetupdep
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

This copy of Microsoft Office 2013 cannot be used on a computer running Terminal Services" error message when you try to open the Click-to-Run version of an Office 2013 program or suite on a terminal server

Hi All,
I have Citrix VDI (Virtual Desktop Infrastructure) Implemented
in my company and installed few Applications on App Server lets say.... MS Office 2013, filzialla, putty, etc...
I assigned these apps to the users through CITRIX STUDIO, when I try to use these apps. on VDI everything is working fine only when i tried to open Word, Excel or Powerpoing, outlook it throws error as
""This copy of Microsoft Office 2013 cannot be used on a computer running Terminal Services" error message when you try to open the Click-to-Run version of an Office 2013 program or suite on
a terminal server"" and apps gets closed.
Please help me on this ASAP.
Thanks & Regards,
Sachin Shinde

Hi,
As mentioned in ths article below, run for Office 365 products on to a Remote Desktop Session Host server is not supported. You can install Office products for Office 365 to a virtual desktop, but the virtual desktop must be assigned to a single user.
http://technet.microsoft.com/en-us/library/jj219423(v=office.15).aspx
Regards,
Melon Chen
TechNet Community Support

Office 2013 partialy virtualized breaks Outlook2013

Similar Messages

Maybe you are looking for