Office 2013 appv package upgrade to new service pack

scenario:
Office 2013 SP1 is published.
SP2 become available. What would be the steps for SP installation?
--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis

Create a new package using the same steps as the first, the Office deployment tool will download and package the latest version available by default (by which time hopefully Microsoft have fixed the issue where the latest version doesn't convert to App-V
successfully!).
Then deploy the package as an update as you would for any other package. Since the package GUID should be the same for all Office 2013 packages unless you manually changed it, the App-V client should treat this as an upgraded package and only stream down
the blocks that have been updated.
Dan Gough - UK App-V MVP
Blog: packageology.com
Twitter: @packageologist
LinkedIn

Similar Messages

Does acrobat pro 9 work with microsoft office 2013? Just upgraded and now Acrobat does not seem to "see" my documents

does acrobat pro 9 work with microsoft office 2013? Just upgraded and now Acrobat does not seem to "see" my documents

uninstall.
run the cleaner, http://labs.adobe.com/downloads/acrobatcleaner.html
restart your computer.
right click the setup file and click "run as administrator".

Upgraded to Vista Service Pack 2 on my Satellite L305-S5955...now there's no sound!

Last night I upgraded to Vista Service Pack 2 and today it says I don't have a soundcard. Out of all of computers, this is my only Vista, so I'm having trouble fixing this problem.
I tried to upgrade the drivers from the Toshiba website, but it's not a driver issue; there is no card being recognized.
So, I used the "Add New Hardware" wizard to re-add the soundcard. Doesn't work.
I see lots of people having trouble with this. And also, when the sound was working, it was really quiet. I'd have to turn off the dishwasher, heat, laundry machines, etc to hear anything!
Hope someone can help me on this.
-Gregg

Satellite L305-S5955
Not unusual.
How to troubleshoot sound problems that you experience after you install a Windows Vista Service Pac...
If you need it, this is the correct driver.
Realtek Audio Driver (32/64bit)
-Jerry

The configuration file did not contain well formed AppV configuration XML - When using Office 2013 ODT package

All,
I'm experiencing an issue where when using the Office 2013 package pulled down from ODT, that if I try to change the locations of either InfoPath Filler 2013 or Publisher 2013 from the default of Microsoft Office 2013 then I receive the message "The
configuration file did not contain well formed AppV configuration XML. Please check the management server event log for more information". If I check Applications and Services\Microsoft\AppV\Server-Management\Admin the error displayed there is "An
error was encountered parsing dynamic configuration file '0'. However I am able to change the shortcut location for all other applications except the above 2. I've tried redownloading the files using the ODT and also changing the version number (so far I've
tried both the 15.0.4631.1002 and 15.0.4659.1001 with the same result).
As all I'm interested in so far is having a package which contains Visio and Project I've tried following the article to exclude all the other Office elements:
http://technet.microsoft.com/library/jj219426(v=office.15).aspx#BKMK_ExcludeAppElement. However the package looks to be the same and when I load it into the management console all the options and elements to Office 2013 are available like they were before
when I hadn't set the exclude tags so I'm not sure whether the ExcludeApp parameters actually work correctly.
This then brings me onto the 3rd issue I've experienced. I have a group for the Visio users and I've set custom security for them to have Visio delivered to them but not Project and then a seperate group for just Project users who will have Project delivered
to them but not have Visio. When testing this sometimes seems to work but other times it seems to trip out and a user just in the Project or Visio group will get all of the Office 2013 applications and under the default location of Microsoft Office 2013. When
trying to spot correlation with this it appears random and can happen to any user on any device. We have sequenced a few applications ourselves where different parts are needed for different users and we have successfully managed this using different security
groups for different applications, just as I'm trying here with Office 2013.
Has anyone else experienced the issue with the "did not contain well formed XML" as at the start of the post and how were you able to resolve this? Also has anyone any advice on how to troubleshoot the issue with the security seeming to trip out
and publish all applications within a package to a user regardless of whether they are in the correct group or not?
The management / publishing servers are 5.0.1224.0 which is SP1 HF4 and the clients are on SP2 HF5.
Thanks

Nicke,
The config files are UTF-8. I did find the same article as yourself, however when searching for the value ‘TakeoverExtensionPointsFrom46=’ within either of the configuration.xml files that text isn’t found.
No sinister reason not to share the file used, just it’s the same structure as referenced in the article:
http://technet.microsoft.com/en-us/library/dn745895(v=office.15).aspx. The only difference being that I’m using ProPlusVolume and I’ve set a version number (which is the October
2014 update). I’ve even looked to follow the above example as closely as possible in just using the ExcludeApp ID of Access and InfoPath, just to try and prove the process. However I still get the usual full package. The version of the Click-to-Run setup.exe
I’m using is 15.0.4623.1001, so later than the version specified at the end of that article which is 15.0.4619.1000. Where can I expect to see the elements excluded? Will it be when loading the package into the management console or would it just not appear
on the machine when delivered?
<Configuration>
<Add SourcePath="C:\OfficeDeploymentToolV2" Version="15.0.4659.1001" OfficeClientEdition="32">
    <Product ID="ProPlusVolume">
      <Language ID="en-us" />
<ExcludeApp ID="Access" />
<ExcludeApp ID="InfoPath" />
    </Product>
</Add>
</Configuration>
3). We’ve not used global publishing in our environment yet so I will try that. I’ve set both GlobalRefreshEnabled and GlobalRefreshOnLogon to True and when using the command Get-AppvPublishingServer on the client I’m testing with I can see this is pulled
through correctly. I’ve also added the client name to the AD group used to grant access to the package and it is published. However nothing is pulling through onto the Client, so are there any steps I’ve missed or misinterpreted when looking to set this up?
I guess the global publishing is there to keep in with licensing for Office being per device? On a slight aside, as Windows licensing is being changed to allow per user licensing
http://www.zdnet.com/microsoft-to-make-per-user-windows-licensing-available-to-enterprise-customers-7000035401/ does anyone know if there are any plans to allow for Office / Project / Visio licenses to go per user as well? We’re a volume license customer
rather than subscription based so I think a lot of the options to selectively deploy Visio and Project are excluded for us.
Dan,
Ok that explains why the security could be tripping out then and leading to this result. As above I’ll try with global publishing and see how I get on.
From what I’ve read / watched I think only one Office 2013 package can be published to a machine, so we would be unable to have a separate package for Visio and a separate package for Project and then attempt to deliver
them both together. If a user wanted both Project and Visio then I guess we’d need to have a combined Project and Visio package to cover than scenario, but then 2 more separate Project and Visio packages for those who would only want either Project and Visio
(I think).
The scenario we’re looking at is to see whether we are able to deliver Project and / or Visio to different users through an AppV package and this will then cover users on XenApp or on fat clients. Only a small proportion of our
users will need access to Project and / or Visio so therefore we’d only have a small amount of Project and Visio licenses.
However from what I’ve tested up to this point and from what I’ve picked up from Forum posts / watched on TechEd sessions is that as publishing is Global and is unable to use different security groups for different elements of the
suite, then using Office through AppV is only suitable if you will be delivering the whole suite (including Project and Visio) to all of your users. So in a scenario where you’d only want certain elements to be delivered to a handful of users then you’d need
to keep with traditional ESD methods to have this installed onto fat clients and steer clear of XenApp. If wanting to install to XenApp then a lockdown tool like AppSense or AppLocker would also need to be brought into the equation.
Is my understanding above correct or have I missed some options / methods?
If the full Office package is always delivered but a company only has Office licenses and no Project and Visio licenses for all its users, how do they stop Project and Visio being delivered and being available? Or again if you have
this use case is the AppV method one which will be unsuitable?
Thanks

App-V 5 SP2 ODT Office 2013 32bit Package Import error

I have used ODT to package Office 2013/Project/Visio. The package is created without any errors. When I go to import the package using App-V Management Console i get the below error.
"There were problems interacting with the database on the server. The error was: String or binary data would be truncated.
The statement has been terminated."
There are no further errors and the import fails.
I have successfully imported the 64bit version using the exact same steps without issue. Can someone please advise?

Thanks for the escalation Brandon. Yes i have created the 32bit version without the Languages, and this has worked. so it looks as if there is a String that is being created which may exceed the limits of the Database.
I was able to open the Appv file in Sequencer and just change the name using that. I am now able to publish the App. I still find it strange that ODT allows the file to be created with such a long string and then throw an error.

SharePoint 2013 Update Workflow Manager problems after Service Pack 1

Hello guys,
I've installed the service pack 1 for SharePoint 2013 and then I tried to update the workflow manager, but I always get an error message that the workflow manager could not be updated!
Is the installing order wrong? should I first install the update for the worklfow manager and then the update for SharePoint 2013?
Best regards
Matthias

The error message see below for "Cumulative Update for Workflow Manager 1.0 (KB2799754)
"One of the custom actions failed. The installation cannot continue. See log for details!"
[06/06/14 09:48:44] Performing install.
[06/06/14 09:48:44] At least one of the product packages has been detected.
[06/06/14 09:48:44] preReqUpdateDisplayName is :
[06/06/14 09:48:44]
[06/06/14 09:48:44] Wizard mode on.
The following products will be enhanced:
Workflow Manager 1.0
Attempting to open cached Msi package for product code: {04A7199E-565D-4654-88A3-80A9A7BADDD9}
Successfully opened cached Msi package.
[06/06/14 09:48:48] Opening Service Control Manager...
[06/06/14 09:48:48] Operation succeeded.
[06/06/14 09:48:48] Copying files...
[06/06/14 09:48:48] Checking and creating target directory C:\ProgramData\Microsoft\E-Business Servers Updates\Updates\Uninstall2799754.
[06/06/14 09:48:48] Package Workflow Manager Client 1.0 is not installed. Skipping it.
[06/06/14 09:48:48] Package Workflow Manager Client 1.0 is not installed. Skipping it.
[06/06/14 09:48:48] Package Workflow Manager 1.0 is installed.
[06/06/14 09:48:49] Copying file AppServerV1-WorkflowManagerpatch30.msp ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file AppServerV1-WorkflowManagerpatch30.msp ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file TargetWFVersion.txt ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file UnifiedWFHotfixUpgrade.PS1 ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file Setup.xml ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Copying file Setup.exe ...
[06/06/14 09:48:49] Operation succeeded.
[06/06/14 09:48:49] Package Workflow Manager 1.0 is installed.
[06/06/14 09:48:49] Package code is {04A7199E-565D-4654-88A3-80A9A7BADDD9}.
[06/06/14 09:48:49] Executing preinstall custom actions. 1 actions to execute.
[06/06/14 09:48:49] Starting process "C:\Windows\system32\..\sysnative\windowspowershell\v1.0\powershell.exe" -NoLogo -NonInteractive -NoProfile -WindowStyle Hidden -ExecutionPolicy RemoteSigned -File UnifiedWFHotfixUpgrade.PS1 -HotfixType "CS" -PackageType
"server" -opcode "PatchBefore" -platform "x64" ...
[06/06/14 09:48:50] Process exit code is -1.
get-itemproperty : Cannot find path 'HKLM:\Software\Microsoft\Service Bus\1.0'
because it does not exist.
At C:\ProgramData\Microsoft\E-Business Servers
Updates\Updates\Uninstall2799754\UnifiedWFHotfixUpgrade.PS1:971 char:21
+ $sbinstallpath = (get-itemproperty "HKLM:\Software\Microsoft\Service
Bus\1.0" ...
That's the log file
Best regards
Matthias

Upgrading wl702 to service pack 6 fails

Hi,
I'm trying to install Service Pack 6 on a solaris sparc machine in console mode.
The installation aborts with the "**** The existing product directory does not have enough space. It requires at least 144MB." message, although sometimes it claims it requires atleast 50MB. The disk has over 280 megs free space, so whats the catch here?

k, works now. I had the .bin file in /tmp, which is physically a different drive than being used on /opt/wl702. I copied the .bin to /opt/wl702 and run it from there. It stated that /var/tmp doesn't have enough space, and i told it to use /tmp instead (1.5Gb free), and the upgrade is running nicely at the moment.
Don't know why it failed when I tried to run from the /tmp, but at least it works now

How to Repair Microsoft Dynamics CRM Server 2013 once the update rollup or service pack is installed?

Hello,
I am going through the following Technet article:
Repair Microsoft Dynamics CRM Server 2013 (
https://technet.microsoft.com/en-us/library/hh699749(v=crm.6).aspx )
The repair option asks for the original CRM DVD media location. The problem is that how the repair procedure knows about the service packs or update rollup files location?
My concern is that the repair procedure replaced the update DLLs (or other files installed by CRM service pack installer) by the RTM files in the original setup DVD.
Is there any special consideration for repairing Microsoft Dynamics CRM Server 2013 once the Service Pack or Update Rollup is installed?
Thank you,

Hello,
I am going through the following Technet article:
Repair Microsoft Dynamics CRM Server 2013 (
https://technet.microsoft.com/en-us/library/hh699749(v=crm.6).aspx )
The repair option asks for the original CRM DVD media location. The problem is that how the repair procedure knows about the service packs or update rollup files location?
My concern is that the repair procedure replaced the update DLLs (or other files installed by CRM service pack installer) by the RTM files in the original setup DVD.
Is there any special consideration for repairing Microsoft Dynamics CRM Server 2013 once the Service Pack or Update Rollup is installed?
Thank you,

MS Office Programs won't open after installing Service Pack 1?

Hello
I'm working on an inherited MacBook Pro, and Installing the MS Office 2008 program from my employer, an online educator. The program installs, but I can't open any of the applications except for Entourage.
Any info or advice would be greatly appreciated!
Thanks
Barb

I suggest you post your question on Microsoft's own forums for their Mac products, as it's their software you're having issues with:
http://answers.microsoft.com/en-us/mac

Office 2013 SP1 fails with code 17302 - SCCM 2007 R2

Hi,
I am trying to deploy Office 2013, along with SP1, in the following order:
1. Prompt to close all office apps and continue (vbs)
2. Installation of Office 2013, using modified msp.
3. Restart
4. Installation of SP1 with command line /passive /norestart.
I am doing this all through a package I created in SCCM 2007 R2.
The first few programs works well. However, when the installation of SP1 starts, SCCM launches the program, then SP1 fails with code 17302.
Manual installation, through command prompt, with the same switches works fine.
The error is only when remotely deploying.
The system is Windows 7 X86 with latest SP.
Please help!

Hi,
Have you checked the log file? Does it say anything there? Also, where is the SP1 installation file stored? Since this only happens while remotely deploying, check the network or the setting of your filewall.
By the way, you can slipstream Service Pack 1 with your Office 2013 installation media, Office 2013 will be directly installed at Service Pack 1 level, saving you the trouble of applying it afterwards. For the details, please refer to this article:
http://www.howto-outlook.com/otherprograms/slipstreamoffice2013sp.htm
(Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.)
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.

Uninstall App-v office 2013 package sccm 2012

Hi ,
how do we add uninstall command to office 2013 appv appliation in sccm 2012, i see no option were we can give command lines unlike normal msi apps.
please confirm
Thanks

Please take a look at this previous thread:
https://social.technet.microsoft.com/Forums/en-US/6663cb6e-23c1-48e6-a62e-85c447b88f3d/appv-application-uninstall-with-sccm-2012-integration?forum=mdopappv
PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
rorymon.com Twitter: @Rorymon

Are admin and office clients always updated for each service pack.

Hi,
I am investigating upgrading our BPC version from 7.0 SP3. The question I have been asked by my business clients is "do the admin and office clients of BPC always get updated with each service pack?" I assume they do because the install guide indicates that you must update them to the same version as the server. Upgrading the client versions is always a concern here because since we don't allow the automatic update our plans have to include packaging an SMS deployment to over 500 workstations of several different configurations and locations.

Hi,
Yes, there are changes in the clients in every service pack. This is why it's important that the version of the client matches the version on the server. We've seen issues where there was a mismatch and no one could log in because of the changes in the client.
I would advise always updating the clients when adding a new service pack.
Regards,
Jason

Lenovo G560 and Office 2013 installation problems.

I recently acquired a copy of Office 2013 and I upgraded my office 2010 to 2013. However, I get a response that some office packages could not open because set up could not find or validate an installition file. Please try reinstalling office from the installation source, or if you installed from a downloaded package, please redownload and reinstall. I have tried severally to reinstall but still facing the same problem. The only Office 15 package that work is Powerpoint. Im running Office on a Lenovo G560 core i3 processer, 3GB RAM and 320 HDD. The Office 15 package is OFFICE 2013 VL. Please help. I am desperate. Please help.

hi onyanchaerick,
If the above procedure doesn't work, you can also try to:
1. Fully remove MS Office 2010 by following this or this guide.
2. If you have an Office Professional Plus 2013, download a trial version here, then activate it with your full version product key.
Goodluck!
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Office 2013 Professional Plus configures each time you start

I have a problem that has been well documented for Office 2010.
I have just installed Office 2013 as an upgrade from Office 2010 and every time I open an Office 2013 application I get the following message:
'Please wait while windows configures Microsoft Office Professional Plus 2013".
I have tried to follow the solutions provided for Office 2010, particularly Microsoft article ID 2528748; Method 1 did not solve the problem and using Method 2 the Fix It was not applicable and as I am using Windows 7, I was unsure how to manually apply
the fix.
Has anyone else experienced this problem and found a solution.
Regards
As an update, I did manually apply Method 2 but it still did not solve the problem. I considered doing a System Restore back to Office 2010 and found there were resore points created to 'uninstall' and 'reinstall' Office 2013 which corresponded to 'configures'
message.

Below is the answer I got from Max Meng (a forum moderator) when I posted a new question (it looks like I am going to have to completely uninstall and reinstall to see if that fixes it, but maybe this will help someone else). The thread this comes
from is:
http://social.technet.microsoft.com/Forums/en-US/officeitpro/thread/105fb8c6-c974-42c1-b783-c5e6f31d6d17
I thought restoring all security settings to default values was interesting. I noticed that I had some issues in my registry that prevented the SecEdit command from completing properly, but even when I had cleared them up, I still haven't fixed the
problem. I am also checking into possible interaction with Dragon Naturally Speaking (does anyone else who has the problem have that installed?). Here is what Max told me:
Not sure if you have tried to repair your Office, if no, please try to repair your Office as a quick fix.
If that doesn't work, try to fix it with the following methods:
Method 1:
Open an elevated Command Prompt, type the following command, and then pressENTER:
secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose
Method 2:
Try start Office in safe mode, see if this problem will still persists. (Press and hold the CTRL key, and then click the Office program to start it in safe mode.)
If the problem does not occur in safe mode, this issue might be related to third-party add-ins. Disable the add-ins and start Office to see whether the problem continues to occur.
If the problem continues to occur in safe mode, we recommend that you uninstall Office and then install it. To do this, read the following Microsoft knowledge base article:
http://support.microsoft.com/kb/2739501

Excel connection manager - Error after Installing Office 2013

Hi Team,
My SSIS package used to work fine until I Upgraded my Office 2010 to Office 2013. After upgrading to 2013, the SSIS package which is created using SQL 2012 is throwing error for Excel Connection manager. Below is the error what I see
TITLE: Microsoft Visual Studio
Could not retrieve the table information for the connection manager 'Excel Connection Manager'.
Failed to connect to the source using the connection manager 'Excel Connection Manager'
BUTTONS:
OK
FYI, I am running the package with Run64BitRunTime property = False.
Do let me know the solution please. It will be of great help as we are proposing this tool in a migration project.

I found the solution. Thanks
You don't need office on your server (not recommended and not supported). You should install
Microsoft Access Database Engine 2010 Redistributable for excel (xlsx) files and then use the Excel
This download will install a set of components that facilitate the transfer of data between existing Microsoft Office files such as Microsoft Office Access 2010 (*.mdb and *.accdb) files and Microsoft Office Excel 2010 (*.xls, *.xlsx, and *.xlsb) files to
other data sources such as Microsoft SQL Server. Connectivity to existing text files is also supported. ODBC and OLEDB drivers are installed for application developers to use in developing their applications with connectivity to Office file formats.

Office 2013 appv package upgrade to new service pack

Similar Messages

Maybe you are looking for