Sccm 2007 office 2013 package downlown issue

Dear Exprt,
we have receive common issue with office 2013 package download.
[email protected]

Please check that all the files have been copied to the distibution point check the logs for errors and check the distibution package from the server share. Also make sure that the SCCM has correct rights the get the source material AND that the path to
source material is set correctly and contains no errors. When running the advertisement at the client side could you check that the local cache contains all the files you have set into the distribution point.

Similar Messages

Default appv Office 2013 package fail

I created office 2013 package with ODT.
Before tweaking the package I decided just to see if default configuration will work. So I didn't exclude any product from the package and want to see the result of Office language. I found the info that Office will take the OS language by default
and I distribute it to test Windows 7 French.
For a test I copied the AppVPackages folder created by ODT containging .appv to Content share and Published the package to computer group containing 2 test computers.
I get this error in eventvwr on client machine:
Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {047f1eb5-96e8-416b-9231-31f7030afd6c} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\047F1EB5-96E8-416B-9231-31F7030AFD6C' with error 0x79100710-0xD.
Do I have to change something in ProPlus_x86_DeploymaneConfig.xml prior publishing?
I renamed AppvPackages folder containing .appv and xml files more distinguished name on Content share. Could it be the reason of error?
"When you hit a wrong note it's the next note that makes it good or bad". Miles Davis

No, you should not require to change anything in the Deployment Configuration XML file.
Can you get a sequenced Office 2013 to work in any scenario e.g. on an English language machine for example?
PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog:
rorymon.com Twitter: @Rorymon

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

Office 2013 Packager failed: Office (32-bit) not packaging because of Office (64-bit)

Hello,
I used ODT to download Office 2013 Pro 32-bit and now I am trying to create a package from those files. I use the command line:
Setup.exe /packager configuration.xml "E:\Office 2013 Pro App-v"
When I try to run this, I immidiatly get the following message:
"We found a problem! We're sorry, Office (32-bit) couldn't be installed because you have these 64-bit Office programs installed on your computer. Microsoft Office 2013. 32-bit and 64-bit versions of Office programs don't get along, so you can only have
one type installed at a time. Please try installing the 64-bit version of Office instead, or uninstall your other 64-bit Office programs and try this installation again."
I checked my installed programs on the server, but I don't have Office 2013 64-bit installed. I did in the past create packages for Office 2013 64-bit , but it's currently not in published/installed on the server. I checked with revo uninstaller to be sure.
Is there a registry setting, or something that is misleading App-V to believe I still have Office 2013 64-bit somewhere installed? I really need to stream MS Access 32-bit to users. But cannot solve this issue.
Thanks in advance,

Hello,
Thanks for replying. Your solution works, BUT I'm immidiatly running into a second problem. The .appv package that is created, cannot be published. The error I get is:
An unexpected error occurred while retrieving AppV package manifest. Windows error code: 1465 - Windows was unable to parse the requested XML data.
I think this has to do with issues in the september releases of Office 2013. I'm gonna try downloading a previous versin using ODT. Changing the configuration.xml file to:
<Configuration>
<Add SourcePath="E:\DGI Applicaties\DGI Office 2013 Pro" OfficeClientEdition="32"
Version="15.0.4631.1002" >
    <Product ID="ProPlusVolume">
      <Language ID="nl-nl" />
<ExcludeApp ID="Excel" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Infopath" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Outlook" />
<ExcludeApp ID="Powerpoint" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="Publisher" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="Word" />
    </Product>
</Add>
    <Updates Enabled="False" />
    <Display Level="None" AcceptEULA="TRUE" />
<Logging Name="Office2013_package.txt" Path="%temp%" />
  <Property Name="AUTOACTIVATE" Value="1" />
</Configuration>

SCCM 2012: Office 2013 click to run deploy?

Hi,
We would like to run Office 2013 next to Office 2010. Therefore the click-to-run option (app-v is only possible for Office 2013 ProPlus) looks the way to go.
I found a nice guide a Office 2013 Plus “Click to run” Deploy in SCCM:
http://www.peters.com/Blogs/Lists/Posts/Post.aspx?ID=90 However (posted it also on the site), can I use the /admin to generate the configuration.xml instead and use it within SCCM 2012 deploy?
J
Jan Hoedt

No. Click-to-run does not use the traditional Office setup methodology and thus does not have the same configuration options. More info at
http://technet.microsoft.com/en-us/library/jj219420(v=office.15).aspx
Jason | http://blog.configmgrftw.com | @jasonsandys

Office 2013 Calendar Synchronization Issue

This is really odd, and has totally stumped me.
Our client is running a network with both local and remote desktop services, using Office 2010 locally and 2013 in the remote session. One user, before Christmas was not synchronising with a shared calendar, so we created a new user profile, completely separate,
which fixed the problem for a while. Now the issue has re-occurred, only with this one user, but it has happened on both her profiles.
The client has a number of shared calendars that users book multiple appointments in, and in testing when an appointment is booked, it shows up instantly on the other users' desktops. Except for this one user, it doesn't show up at all. And appointments
booked by her don't show on anyone else's version of that calendar. This happens on Office 2013 through the Remote Desktop, on OWA and on the local machines on Office 2010. There doesn't seem to be any corruption in the profile, and this has got me completely
stumped.
Help.

Hi,
Since the issue exists on both OWA and Outlook Client, I suppose creating a new profile won't work this time, probably an Exchange thing.
Have the user right click on the shared calendar, go to Properties
-> Permissions to check what permission she has. Remove and regain the proper permission for her, check if this helps.
I also suggest you check the her permission on the shared calendar on Exchange side, see if it meets the permisson displayed in Outlook.
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

Office 2013 KMS Activation Issues When Outlook 2010 Has Been Installed

Hi Everyone,
I have been looking everywhere for the answer to this question. I have been setting up a KMS server host for Office 2013 on Server 2012 R2. The issue I have ran into is that all of our computers currently have Office 2010 installed. Our Office 2013 KMS server
is installed on a different server than the KMS server that activates Office 2010. (Different Virtual Machine) If Office 2010 has been installed the KMS server will not activate with the upgrade to 2013. Troubleshooting below:
1. Leave office 2010 installed and simply click upgrade - did not work.
2. Completly uninstalled Office 2010 and tried ospp.vbs /act and ospp.vbs /act - did not work.
3. Completly uninstalled Office 2013 with all other versions of Office 2010 uninstalled. Did a fresh install of Office 2013 after a reboot and verified working.
Can anyone explain to me either why this is happening as well as a solution. I realize that I have a work around right now but it takes some time.

So, you have 2 KMShosts?
Host_A is KMShost for OFF2010
Host_B is KMShost for OFF2013
Are both hosts published in DNS?
(check with: nslookup -type=any _vlmcs._tcp)
Clients can resolve and connect to both hosts?
Or are you using static KMS location (do you manually configure your KMSclients to a specific hostname or IPaddress)?
Typically, a KMSclient will perform discovery via DNS lookup, and will try each KMShost until success occurs.
Possibly, when you installed WS2012R2, you chose ADBA instead of KMS ? (check the VA role on this server to confirm the mode)
You can check upon the KMShost, execute: cscript slmgr.vbs /dlv all
Another option, might be for you to co-host OFF2010 KMS and OFF2013 KMS upon the same (new WS2012R2) server, and de-commission the old KMShost function including removal of the DNS record for it. (Assuming this is consistent with your plans)
Example for OFF2013 ADBA:
http://blogs.technet.com/b/odsupport/archive/2012/11/07/how-to-setup-active-directory-based-activation-host-for-microsoft-office-2013.aspx
Example for OFF2013 KMS:
http://blogs.technet.com/b/odsupport/archive/2012/11/07/how-to-setup-kms-activation-host-for-microsoft-office-2013-on-windows-server-2012.aspx
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!)

Sccm check office 2013 users license status

Hi I tried to use sccm2012 to check the license report for office 2013 users, but there are nothing for office 2013. there are for office 2010,win7,etc. I run query and confirmed some pc have office 2013 installed. any advice how to get the report for
licensed products work?thanks
Thanks and best regards, -- KF

Here's a simple query which target the "Program and Features" (Add/Remove Program) of your computers.
Do you get any results ?
select B.Name0, B.AD_Site_Name0,B.Operating_System_Name_and0, A.DisplayName0
from v_Add_Remove_Programs A inner join v_r_system B on B.ResourceID=a.ResourceID
where DisplayName0 like '%Microsoft Office 2013%'
Benoit Lecours | Blog: System Center Dudes

Exchange 2007 - Exchange 2013 Mailbox Migration Issues

Exchange 2013 - Mail Flow is working. OWA Access is great. We have issues connecting Outlook 2010 Clients. If I create a new user and mailbox Outlook 2010 works fine. However, if we migrate a user's mailbox to the new Exchange
2013 server. Outlook Web (OWA) works and mail flow but "OUTLOOK 2010 can not connect to the new server" There is something different about a newly created account and a migrated account. Any help would be great. I did check
inheritance in AD and it was on for these accounts. This occurs with any account migrated to the new server.

1. Could you double check your Exchange 2007 Internal Autodiscover URI - it should be pointing to Exchange 2013. All clients should be receiving their autodiscover config from the Exchange 2013 server. Based on the client's mailbox location, Exchange 2013
generates and provides the correct information.
2. If the autodiscover URI is "autodiscover.yourdomain.com" and you've configured Split-Brain DNS or Pin-Point DNS zones on the local network, make sure the name is resolved to Exchange 2013 internal IP address.
Step by Step Screencasts and Video Tutorials

SCCM - Image/OS Installation Package Permissions issue

Hello,
I receive the following error message when I try to import a .wim image
(from the Vista DVD) as an Operating System Image or when I try to add the
entire Vista ROM as an Operating System Install Package:
"The specified source directory does not contain a valid operating system or
you do not have permissions to access it. Please specify a valid source
directory."
The error changes slightly when importing a .wim to:
"The specified source directory does not contain a valid WIM file or you do
not have permissions to access it. Please specify a valid path."
I've tried multiple .wim images in multiple shares- I've always specified
the .wim image name on the import line when importing a wim or the directory
path when importing the whole OS ROM.
I've mounted both .wim files to verify that they are valid.
I have changed the network access account I specified in Computer Client
Agent settings to a domain admin and verified that the credentials are
correct. I've added granular NTFS and share permissions to the domain admin
network access account I'm using.
I've rebooted the server.
I've tried importing from a share on another server (same errors).
This must be permissions related but I can't find the incorrect setting. Any
help would be appreciated.
Thanks!
Grant

I have the same issue with my installation.
WAIK was installed with SCCM as supposed.
No way to import .WIM images.
This is what OSDImageProperties.log states:
Opening image file \\de1-s039\osd\Images\ReferenceImage7700.wim
Unable to open the image file (0x80070005)
Opening image file \\de1-s039\osd\Images\install.wim
Unable to open the image file (0x80070005)
Any Ideas on this?

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

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

Office 2013 VL and app-v 5 SP2 on RDS server - package add fails with script error

We have used the MS Office Depolyment Tool for click-to-run to download the latest Office 365 version, and flatten it into an app-v 5 package - not a problem.
When we try to add the package to our client machine (Server 2008R2 running the app-v 5 SP2 client software), it fails with an message that a script has failed and not returned a 0 code. We have not added any scripting to this automatically created
package, so it seems that the app-v client does not like the "official" package. Any hints and tips gratefully accepted, thanks
App-v client has scripting enabled.
The powershell command line we are using is:
PS C:\windows\system32> Set-ExecutionPolicy Unrestricted
PS C:\windows\system32> Add-AppvClientPackage -path file://hostname/app-v/o365-noaccess/ProPlusVolume_en-us_zh-cn_x86.appv -DynamicDeploymentConfiguration \
\hostname\app-v\O365-NoAccess\ProPlusVolume_en-us_zh-cn_x86_DeploymentConfig.xml
with a result of:
Add-AppvClientPackage : Embedded Script process exited with an error code indicating failure (return code other than 0). Please ensure that Embedded
Script process can complete successfully and exits with 0.
Operation attempted: Configure AppV Package.
AppV Error Code: 100000000C.
Please consult AppV Client Event Log for more details.
At line:1 char:1
+ Add-AppvClientPackage -path
file://hostname/app-v/o365-noaccess/ProPlusVolum ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
    + CategoryInfo          : InvalidResult: (:) [Add-AppvClientPackage], ClientException
    + FullyQualifiedErrorId : ConfigurePackageError,Microsoft.AppV.AppvClientPowerShell.AddAppvPackage
and these are the error messages we see in the debug app-v client logs:
Script Launcher successfully waited for script with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe" /I /Msi /License /AppV PackageGUID=D24C3BDD-8FAD-44d3-998C-933F8F053682
PackageRoot="C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root" MsiName=SPPRedist.msi,SPPRedist64.msi PidKey=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx,xxxxx-xxxxx-xxxxx-xxxxx-xxxxx
PRIDName=ProPlusVolume'.
and...
Package {d24c3bdd-8fad-44d3-998c-933f8f053682} version {cd9725ce-4503-4932-863b-4fcda3f9551d} failed configuration in folder 'C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D' with error 0x79100E10-0xC.
and...
machine script for event AddPackage with command line: '"C:\ProgramData\App-V\D24C3BDD-8FAD-44D3-998C-933F8F053682\CD9725CE-4503-4932-863B-4FCDA3F9551D\Root\..\Scripts\Integrator.exe"'
exited with failure error code: The extended attributes are inconsistent.. Because Rollback is set to true in the script definition, the current AppV Client operation was rolled back.
We believe this last error message is the kicker, but can't debug any further.

Just to validate the problem, I started again.
I have just downloaded the latest ODT from MS, and then downloaded the latest Office 2013 packaged - volume license. Then created the app-v package - all went perfectly, no error messages. Uploaded the package to the app-v 5 server and published
it. I have made NO changes to any of the files.
I have just built a brand new Windows Server 2008R2 Datacentre VM, patched it to the hilt, and installed the RDS role, powershell 3 and appv 5.0 SP2 client for RDS.
I then use powershell as above:
          scripting unrestricted
          app v client scripting enabled
         app v server added
          global and user update enabled
         add-appvclient package "url of office package.appv"
             and received exactly the same error message.
It is not complaining that scripting is not allowed, it is complaining that the script is invalid.
Help!!!!

Any Fix / Update For Microsoft Office 2013 Free/Busy Information Issue

Any official update / fix regarding the Microsoft Office 2013 Free/Busy Information Issue? (not the workaround I found to uninstall KB2837618
and re-create profile).
Reference: http://helpdesk.missouristate.edu/news/two-microsoft-updates-cause-problems-with-outlook-2013
Thanks a lot,
Moshe

Refer to the solution which delivery by Hypocrit from another thread with the same topic.
http://social.technet.microsoft.com/Forums/en-US/827a12f0-c785-43df-a71f-0b21aeffa176/outlook-2013-freebusy-fails-after-updates?forum=officeitpro
I've copied the replies below:
"With mfcmapi open your Profile under the Profile->Show Profile
then double-click "Outlook" or how your Profile is named
then double-click "Microsoft Exchange"
then double-click your mailaddress (both) and remove PR_DELETED_FOLDERCOUNT with value SMTP: or correct them"
http://mfcmapi.codeplex.com/releases/view/101020
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.
More reference post:
http://social.technet.microsoft.com/Forums/en-US/a926f0b5-0e66-4f43-8ac3-50791df16154/microsoft-office-2013-freebusy-information-issue?forum=officeitp
Tony Chen
TechNet Community Support

How to uninstall Office 2010 32 bit and install Office 2013 64 bit

Hi Everyone,
I am rather new to SCCM. I have setup a SCCM 2012 SP1 system. I am now trying to setup an Application where it will install Office 2013 64 bit. Everything seemed to go smoothly until I tried testing it. I received an error that I
cannot install the 64 bit version of Office 2013 because Office 2010 32 bit is already installed.
I tried to modify the MSP where it will uninstall Office 2010 before installing Office 2013 but apparently as soon as it starts it checks for the 32 bit installation and exits when it finds it.
Could someone give me a detailed solution (since I am new to SCCM)?
Ken

While referring to older versions of office I think this link may apply: http://social.technet.microsoft.com/Forums/en-US/f255e17d-4e1f-4231-8a88-d63f41c83c52/how-to-automatcally-uninstall-office-2007-32-bit-for-installation-of-office-2010-64-bit?forum=officesetupdeployprevious
Also you might create an office 2010 package, with an uninstall program that removes it.
Then in your office 2013 package make the uninstall for 2010 to be run first.

Sccm 2007 office 2013 package downlown issue

Similar Messages

Maybe you are looking for