Office 365 ProPlus Source files & Updates.

Morning everybody,
Still planning my O365 deployment, so the following is so far has only been applied to a small number of test machines.
When updating O365 on my endpoints, the source of those updates is set by the configuration.xml I use when running the initial install. As the updates are not likely to amount to a huge amount of data, the updatepath is set to a network share.
In the same config.xml, the sourcepath is set as a local path on the machine, because rather than having 4000 machines all try to pull over a gig of source files down over the network (half of which will be on via VPN), it made sense to stage them locally
via SCCM for the sake of that initial setup.
My questions are as follows:
When updating, does the sourcepath set in the config.xml need to still exist on the local machine, or do the updates go straight into the Program Files folder?
Once that initial setup is complete, is there any reason those source files which I've stored locally shouldn't be deleted?
Many thanks,
AP

Hi,
As per your description, I understand that you've deployed Office 365 with a customized configuration.xml file. In the XML file, the
SourcePath attribute was set to a local path, and the UpdatePath
was set to a network share.
With this configuration, your Office 365 will check the update path for updates instead of using the cloud as the “update source.” The difference – or delta – between the new build and the existing one will be installed directly when Office apps/processes
aren’t running.
The build/source in your sourcepath is not involved during the whole update process, you can delete it after the initial installation.
Hope this helps.
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.

Similar Messages

Working with Excel references error with Office 365 ProPlus on Shared Drive

I came across an issue with the Excel version of Office 365 ProPlus, as below described.
A.xls(x) contains formula that links to B.xls Sheet1. When working on A.xls. I decide to navigate through windows explorer and open B.xls(x). Once I do all references to Sheet1 turns into #REF of A.xls(x). And naturally all values that were previously correct
now returns #REF. Even without making any changes to B.xls(x), just opening the file cause this problem. Both these files are on the mapped network location within the same LAN. User is on Win7 & Office 365 ProPlus. The server is running on Windows 2008
R2 with no office installed. This occurred to users who are member of the AD and in Workgroup. We have tried re-installing, repairing, etc. but the problem remains the same. But if the files were on the local HDD, we didn't face the same issue.

Hi,
According to your description, this issue may be caused by the hyperlink/reference changed from relative to absolute links. For example, if you use the reference in formula, we only need to enter like this:[filename.xlsx]Sheet1'!$C$107:$C$112, when we re-open
the file, Excel will autocomplete the path, like: [C:\Mydir\filename.xlsx]Sheet1'!$C$107:$C$112.
To workaround the issue, we may update the link manually, please see the image below:
Go to Data tab>Edit link>Update value or change data source.
More references for the common scenarios of this issue:
You map a drive under the root of a share. For example, you map drive Z to \\<var>Server</var>\<var>Share</var>\Folder1.
You create links to a workbook that is stored at the mapped location after you open the file through that mapped drive.
You open the file by a UNC path.
As a consequence the link will be broken.
https://support.microsoft.com/kb/328440/en-us?wa=wsignin1.0
Hope it can be helpful to you.
Regards,
George Zhao
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.

Unable to license Office 365 ProPlus when customized at the application level

It has long been claimed that Office 365 ProPlus can only be installed as one single package, and that Click-to-Run is not customizable at the application level. Microsoft lists the following at
http://technet.microsoft.com/en-us/library/jj839718.aspx “Office 365 ProPlus installs as one package. This means you can't choose to deploy Word and PowerPoint to users, but not Access.
If you don’t want users to run Access, you can customize the installation by using App-V. You can also use AppLocker to prevent users from starting certain Office applications.”
Can anyone then explain the purpose of the additional product ID’s specified in the following kb article:
http://support.microsoft.com/kb/2842297
Using the product ID’s listed here, I set the Configuration.xml file to selectively install only four Office products, which included Access, Excel, PowerPoint and Word. In this example, I removed the Product ID O365ProPlusRetail and instead just included
the Product ID’s for the individual applications we wanted to install.
<Configuration>
<Add OfficeClientEdition="32">
   <Product ID="AccessRetail" >
     <Language ID="en-us" />
   </Product>
   <Product ID="ExcelRetail" >
     <Language ID="en-us" />
   </Product>
   <Product ID="PowerPointRetail" >
     <Language ID="en-us" />
   </Product>
   <Product ID="WordRetail" >
     <Language ID="en-us" />
   </Product>
</Add>
<Updates Enabled="TRUE" />
<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />
</Configuration>
Given what I had read throughout multiple areas of documentation, especially the line that mentions, “Click-to-Run is not customizable at the application level,” I was surprised and excited to see that the click to run installer only installed the applications
that I specified.
Using the Configuration.xml file I specified above, I was able to complete a custom install of Office 365 ProPlus, and included only programs that I wanted to have installed.
The issue comes when you go to license the software. I can launch any of the individual programs without issue, but I am unable to complete the process of activating the license.
For example, see below where I have launched Word, entered my account information and attempted to activate. Everything has worked fine up to this point, but I am told that I cannot activate because the product is not installed. It seems that
my custom install has prevented needed information from being added to my system to allow for the activation wizard to detect the presence of the installed Office software and to activate appropriately.
Can anyone from Microsoft comment on this? Is there any way possible to proceed given my configurations? If not, what is the purpose of
http://support.microsoft.com/kb/2842297 ?
In what case would you actually be able to use the additional product IDs? (AccessRetail, ExcelRetail, WordRetail, etc.)

Whilst I don't work for MS, I have a few thoughts on this..
The documentation refers to the use of ODT for customisation, but that is mainly for customising the install-time aspects and the update sources, not the resultant feature state.
For controlling feature state, either AppLocker of re-packaging/sequencing via App-V is suggested.
KB2842297 mentions the products that ODT will "recognise" for the purposes of "customisation", but doesn't really detail how nor why.
C2R, as it is a pre-packaged sequenced output, is intended to be consumed as-is, by the vast majority.
Re-packaging/sequencing of a complex product such as Office isn't for the faint of heart (and to be honest, the installers for Office have long been a complex topic over many years)
MS have stated for many years that the individual component applications of the Office suites, are not permitted to be broken up out of the suite, for license compliance.
e.g. If you install OfficeProPlus, and via customisation, disable or do-not-install specific component apps, you must hold a license for the relevant suite (ProPlus in this example).
Even if you re-compose the resultant installed apps, such that only those apps that would equate to OfficeStd, because you installed ProPlus, it is a ProPlus license that you must hold.
Similarly, if you were to install individual apps, composing a feature-equivalent result to ProPlus, and "functionally" have the same set of apps that ProPlus would give you, holding a license for ProPlus is not sufficient, becuase it is not ProPlus
that you have installed.
So, when you modified the configuration XML, and downloaded and installed "WordRetail" + "ExcelRetail" etc, this is not equivalent to ProPlus (neither from an installed-product perspective, nor from a licensing perspective).
It seems to me, that your license (as recorded/represented in your MS account) is finding that you have products installed for which you don't hold a license.
And, that the license that you do hold, is not a match for the products you are trying to activate.
In years gone by, MS did make available individual products (e.g. Word, Excel etc) for sale.
I don't know if MS continue do make individual apps, in C2R form, available for sale, but the Office product team have created ODT in such a way that ODT can cater for them.
Perhaps in some global markets, or possibly in the future, MS might make those individual products available in C2R form.
So I'm not all that surprised, based on nothing more than previous experience (sprinkled with some assumption and theory), that you've found some interesting, slightly-mystifying things ;)
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 365 pro plus 2013 update won't apply automatically

Hi
We have started to use office 365 pro plus 2013 click to run. The issue / problem we have is that the updates are installing but does not apply. The version of word,excel.. Is old
and i need to manually go to example word and account to apply the updates. I want the updates to automatically apply.
In the config file i have enabled updates. <Updates Enabled="TRUE" />. I have also enabled updates thru group policy and checked that the policy is applying.
In the registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\15.0\ClickToRun\propertyBag i have the following keys:
updatesenabled = 1
UpdatesDiscoveryPeriodComplete = 1
updatesreadytoapply = 15.0.4535.1511,en-us
UpdatesDiscoveryPeriodStartTime = 13026393682226
updatesthrottlevalue = 313
version = 15.0.4535.1004
Does anyone have this problem and know how to make the updates apply automatically. I know that if there are office applications open it won’t apply or update but i have a test
computer with no office applications running in the process list and still it won’t apply the updates.
Joakim Tomren

Please make sure that the necessary port isn't blocked in your environment.
http://technet.microsoft.com/en-us/library/jj219420.aspx#BKMK_C2RUpdates
Then, try to download the Office Deployment Tool and create an XML file with the instructions to deploy the Office 365 update, please refer to the link below:
http://blogs.technet.com/b/office_resource_kit/archive/2013/08/08/how-to-deploy-office-365-proplus-from-an-on-premises-web-portal.aspx
The following article may also help you:
http://technet.microsoft.com/en-us/library/gg998766.aspx
We may also post the thread to the forum for Office 365:
http://community.office365.com/en-us/forums/default.aspx
Cheers,
Tony 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 contact
[email protected]

Office 365 Pro Plus Security Update User Permissions - Sccm

I plan to deploy Office 365 Pro Plus using Sccm 2012. My configuration setup file has this line Updates Enabled="TRUE" UpdatePath="Share" . My users are not local administrators of their workstations. If I update the office
share with a patch, will my users have permissions to install the update? If not then how will my users get updated?
Steve Bender

Hi Steve,
Yes, with this confirguration, every Office 365 client will automatically check updates from the update location configured during setup - "Share", in your case.
You should make sure that it's a share (like an internal UNC or HTTP path) that every Office 365 client has permission to access.
Here's the references you'll need:
Managing Updates for Office 365 ProPlus – Part 1
Managing Updates for Office 365 ProPlus – Part 2
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 365 ProPlus will not install

Hi,
I have tried many attempts at manually installing Office 365 ProPlus using the deployment toolkit but so far nothing has worked. I downloaded the bits first and I'm now trying to install Office using the deployment toolkit. This test is in preparation of
a deployment of Office 365 ProPlus throughout our organization. The bits are copied to C:\Office365 and actually reside in C:\Office365\Data. I copied the deployment toolkit to C:\Office 365.
The test computer is freshly imaged using Windows 7 SP1 Enterprise 32-bit from media and is in a workgroup so I don't get any company policies added. All available Windows updates have been installed. Windows Update is enabled but set to only notify
about updates rather than automatically install.
Install.xml looks like this:
<Configuration>
    <Add SourcePath="C:\Office365\Data\" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="C:\Office365\Updates\" />
<Display Level="None" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
I open a command window as administrator, navigate to C:\Office365 and run - setup /configure C:\Office365\install.xml. I changed the command line in many ways but it always fails to install with the same error message. A window appears that says
"Couldn't install - We're sorry, we had a problem installing your Office program(s). Is your internet connection working? Do you have enough free space on your main hard drive? Please try installing again after you've checked the above.
My internet connection is good and my hard drive has over 100GB free. I tried clicking the link "Go online for additional help" but that didn't help at all. The Windows Firewall is turned off. No anti-virus is installed and no proxy is in use.
Does anyone know how to move past this issue?
Thanks,
Rob

I can see it installing now but I need to be sure it's not pulling bits from the internet. I had this happen before when I completely removed the SourcePath. Display level is set to "full" but I am not getting an interface. When I'm done with this
project, display level will be 'none' but I changed it for now just to see something happen.
UPDATED:
I reinstalled Windows 7 SP1 and did not install any drivers. The test computer has no network connectivity of any kind because drivers are required. I copied my downloaded bits to the test computer and ran the install. Office 365 installed without any errors.
I'm absolutely convinced that there is no way the bits were downloaded on-demand in this configuration.
Here is the final XML file I used:
<Configuration>
    <Add SourcePath="C:\Office365\" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
</Add>
<Updates Enabled="TRUE" UpdatePath="C:\Office365\" />
<Display Level="none" AcceptEULA="TRUE" />
<Property Name="AUTOACTIVATE" Value="1" />
</Configuration>
Here is the final folder/file arrangement:
C:\Office365\setup.exe
C:\Office365\install.xml
C:\Office365\Office\Data\v32.cab
C:\Office365\Office\Data\v32_15.0.4659.1001.cab
C:\Office365\Office\Data\15.0.4659.1001\i321033.cab
C:\Office365\Office\Data\15.0.4659.1001\i641033.cab
C:\Office365\Office\Data\15.0.4659.1001\s320.cab
C:\Office365\Office\Data\15.0.4659.1001\s321033.cab
C:\Office365\Office\Data\15.0.4659.1001\stream.x86.en-us.dat
C:\Office365\Office\Data\15.0.4659.1001\stream.x86.x-none.dat
Thanks a lot for your help! I really appreciate it!
Rob

Office 365 ProPlus Activation Issues

Issue Resolved:
After adding all of the Office 365 URL's and Address Ranges to our internet filters exception list activation worked.
Hi Everyone
I'm preparing for a deployment of Office 365 ProPlus using the Office Deployment Tool (ODT) and having trouble getting Office to activate after installation. Using my custom .xml file, I'm able to install only Office products that are needed without
issue using a Group Policy start-up script. It is necessary for me to do this because none of the users in my environment have local administrator rights and cannot install Office on their own using Click-to-Run. Installing with a start-up script
uses the System account to circumvent that issue. Upon first launch of Office 365 ProPlus I'm prompted to enter my email address and password for activation and promptly receive the error "There is a problem with your account. Please try again
later."
I've verified that an Office 365 ProPlus license has been provisioned for my account through our portal and have ADFS running without issue. Here's where things start to get strange... In testing, I added myself as a local administrator to my desktop
and downloading/installed the Click-to-Run from our Office portal. Upon launching Office for the first time it was activated automatically and the portal showed that a license was used.
As of right now I'm at a bit of a loss as to why I can't activate Office using valid credentials with proper licenses provisioned when installing with the ODT but it auto activated when using Click-to-Run. Any help or suggestions would be much appreciated.
See below for a copy of my configuration.xml
<Configuration>
<Add SourcePath="PATH TO OFFICE INSTALL FILES" OfficeClientEdition="32">
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
<ExcludeApp ID="Access" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="InfoPath" />
<ExcludeApp ID="Lync" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
</Product>
</Add>
<Display Level="None" AcceptEULA="TRUE" />
<Logging Level="Standard" Path="%temp%" />
<Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
</Configuration>
**note: Add SourcePath="PATH TO OFFICE INSTALL FILES" points to the Office\Data folders which were created when using the ODT in /download mode.
Edit:
After troubleshooting the issue more yesterday I found that whenever I try to activate Office 365 ProPlus an error is generated in the application log.
The description for Event ID 0 from source MSOIDSVC.EXE cannot be found. Either the component that raises
this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
InitializeSvcAPI failed with hr = 0x8004825b
I've thus far been unsuccessful in figuring out what MSOIDSVC.EXE is or what it does.
Edit:
http://community.office365.com/en-us/w/sso/534.aspx
MSOIDSVC.EXE is part of the Microsoft Services Sign-In Assistant (MSO SIA). After installing MSO SIA and verifying that the services were running activation still failed.

hi,
Thank you for sharing your solutions and experience here. It will be very beneficial for other community members
who have similar questions.

Display level suppressed when installing Office 365 ProPlus via SCCM even though XML says Display Level="Full"

As the title says the display level is suppressed when installing Office 365 ProPlus via SCCM even though XML says Display Level="Full"
I would like to install Office ProPlus with the display level visible to the user. Not all users are local admins so I've installed Office within the admin context. Does this happen because SCCM installs under system context and as such suppresses
pop ups to the end user?
Has anyone been able to get this to work or am i doing something wrong? If someone can offer me some guidance please. Here is my XML:
<Configuration>
<Add OfficeClientEdition="32" >
<Product ID="O365ProPlusRetail">
<Language ID="en-us" />
<ExcludeApp ID="Access" />
<ExcludeApp ID="InfoPath" />
<ExcludeApp ID="Groove" />
<ExcludeApp ID="Project" />
<ExcludeApp ID="SharePointDesigner" />
<ExcludeApp ID="Visio" />
<ExcludeApp ID="OneNote" />
<ExcludeApp ID="Publisher" />
</Product>
</Add> -->
<Updates Enabled="True" />
<Display Level="Full" AcceptEULA="TRUE" />
<Property Name="FORCEAPPSHUTDOWN" Value="1" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

When i install Office 365 ProPlus manually (independently of SCCM) I see the prompts (same SCCM Package and configuration.xml file). This suggests it is suppressed when ran in the system context via SCCM.
How does Microsoft expect you to maintain the build versions (running setup.exe /configure XML) if users are unable to view the prompts? This is significant if the user is already in an Office program they'd get prompted with a message to close the app else
it automatically closes OR fails depending on if you include the ForceAppShutdown switch in the configuration.xml file.
The users in the environment are not all local admins which is why i cannot run the deployment in the user context.
I really need some help, anyone?

Office 365 ProPlus App-V 5.0 Package installs Lync, Outlook, Infopath and Onenote even though they are not selected for publishing

I have created an App-V 5.0 Package for Office 365 ProPlus using the documentation provided here:
http://technet.microsoft.com/en-us/library/jj219422.aspx
I am able to load the App-V Package into my SCCM 2012 SP1 environment and deploy the package to a test machine
Within SCCM, I have configured the deployment type to only select a couple of applications. Notice that Lync, Outlook, Infopath and Onenote are not selected.
http://i.imgur.com/1eMxUlY.jpg
For my deployment type, I only selected Word, Excel and Powerpoint. Looking at my test machine, those 3 applications now show up in my start screen.
http://i.imgur.com/amZmxAT.jpg
I don't see any of the other Office applications be default on my start screen, so I would think all looks good. If I type another Office application, lets say access at the start screen I get, "No apps match your search."
http://i.imgur.com/fxbWEvb.jpg
But if I type Lync, Outlook, Infopath or Onenote, it shows me that those applications are available, and I can launch them as an App-V application just as I could Excel, Word or Powerpoint, the applications that I wanted to have available.
This is not what I was expecting when I went through the trouble to create an App-V package. It looks like almost all of the apps become available on my client machine, all App-V is doing is making the application button in the start screen a little
harder to find.
What is interesting is that for the applications I did want published, I can search for them by just entering a few letters of the application name, and they show up with the 2013 version label, see below for an example search for Word.
http://i.imgur.com/0LeS05z.jpg
For the applications that I did not publish but still show up on my client, I have to type in the full name of the application for the launch button to come up. For example, I can't type lyn and expect to see Lync, but if i type lync I will get an
option to launch the application. The same goes for Outlook, Infopath and Onenote, and when you do type in the full namke of the app, it doesn't show the version number like Word does as Word 2013, it just shows Lync, or Outlook, or Infopath, or
Onenote.
http://i.imgur.com/QV1afuc.jpg
vs
http://i.imgur.com/PxgSmUc.jpg
Can anyone from Microsoft confirm that this is expected behavior. If this is to be expected this is pretty disappointing, because a main point of the App-V package is it is the only way to limit which applications are deployed via Office 365 ProPlus
but from what I can tell, it really isn't limiting anything beyond the start screen for most cases.

So it looks like the config xml files are the best option
http://blogs.technet.com/b/office_resource_kit/archive/2013/12/02/announcing-app-v-5-0-sp2-support-for-office-2013-volume-licensing-editions.aspx
You can now use the Deployment Configuration file to configure the Office installation. One question I often get is, “How do I disable msaccess.exe or infopath.exe from an Office install if I am not using the MSI package?” This can be done by modifying the
Deployment Configuration file in App-V with entries like the following:
<Application Id="[(AppVPackageRoot}]\office15\MSACCESS.EXE" Enabled="false">
<VisualElements>
<Name>Access 2013</Name>
<Icon />
<Description />
</VisualElements>
</Application>
That will prevent App-V from publishing msaccess.exe on the system and/or you can remove any undesired application shortcuts from publishing on the targeted computer using the shortcuts properties by deleting or commenting them out. Once you’ve configured your
Deployment and User Configuration files, you’ll have everything you need to import the packages into your App-V environment to start testing.

Problems with Lync integration in App-V Package for Office 365 ProPlus

We have problems with setting Lync 2013 to automatic start after Windows start with Office 365 ProPlus App-V Package made by Office Deployment Tool. We use latest version for both (ODT and download package) at Windows 7 Enterprise 64 bit.
We have done this for Lync 2010 and also for Lync 2013 (MSI installations) and it works correctly.
User can choose to start Lync automatically, but this settings is ignored and in virtual registry is set wrong. We look for possible ways to set this by GPO (in ADMX is not this option available) by inserting in virtual registry with Package ID and user
SID in registry path.

Usually setting apps to auto start sets a registry key under HKCU\Software\Microsoft\Windows\CurrentVersion\Run, but since this registry key is inside the virtual environment, Windows does not read it at logon.
The workaround is to either set this key in the native registry (perhaps by an App-V script), or easier still, just copy the shortcut to the Start Menu\Programs\Startup folder. Since you can't really modify Office 2013 packages with the sequencer, you'd
have to add this shortcut by modifying the deployment config file.
Dan Gough - UK App-V MVP
Blog: packageology.com
Twitter: @packageologist
LinkedIn

DirSync AD Attributes for Office 365 ProPlus services.

Hello,
I am installing Directory Synchronization tool on my DirSync server. By default it syncs lots of AD attributes to cloud. What are the minimum Ad attribute requirements that must be synced to cloud for proper authentication to Office 365 ProPlus services.
Thanks
NerKO

Actually DirSync has been around a lot longer than O365, both ADAM and ADLDS leverage dirsync. FIM itself started as MIIS, which Microsoft acquired in 1997. It has gone through various iterations since them from ILM to FIM.
It is not reverse engineering to use Dirsync to synchronize objects between directories. FIM gives one the ability to transform objects and attributes during the synchronization and easily connect multiple LDAP sources.

Cannot "Save As" any Office 365 Pro Plus files e.g ppt to my OneDrive for Business folder

Hi, I am unable to save any Office 365 ProPlus files to my OneDrive for Business.
When I am in the document, I select File | Save As, browse to my OneDrive for Business folder and Click Save. I get the error
"This file cannot be saved to this location because there is no connection to the server. Check your network and try again."
I can drag and drop the file into OneDrive using Windows Explorer and my OneDrive is Synchronizing files OK. This is happening to my collegue as well. Any ideas on why Save As does not work and how to reslve it?

Hi,
Based on the error message, it seems that the connection between the OneDrive for Business folder and the library in Office 365 site does not connected due to some reasons.
I recommend to click the OneDrive for Business button and click Sync Now to reconnect the folder with the site.
And then check the status of the OneDrive for Business folder to see if the sync is OK.
After that, use Save As to save the documents to the OneDrive for Business folder and compare the results.
If above cannot help, I recommend to clear the OneDrive for Business cache and re-sync the library.
You can refer to the link below for detailed steps:
http://its.uiowa.edu/support/article/102675
Best regards.
Thanks
Victoria Xia
TechNet Community Support

By default Office 365 Proplus save as Office 2010

Hi,
Operating System: Windows 7 (SP1); Office 2010 Professional SP1 and also Office 365 proplus...
By default I have installed office 2010 and later I installed office 365 proplus online.
My issue is when I am saving office365 proplus (Word,excel) file then by default it saving as office 2010.
When I opening it by open with but there office proplus (word / excel) option is not available.
All desktop files showing in office 2010 format.
I office 365 proplus repair but issue is same.
(FYI: when I uninstall office 2010 then by default office 365 proplus both saving and displaying)
Please anyone help me about to above issue to resolve before uninstalling office 2010..........

Hi,
I have tested this in my testing environment that by default Office 365 Pro Plus will take over your existing Office 2010 files if you install Office 365 Pro Plus later. And the new Office icon will show on all of your existing files.
Usually, do a Online Repair of the Microsoft Office 365 Pro Plus will fix the broken of file type associations. Not sure how you repaired your Office 365 Pro Plus, please try again follow the steps below:
1.Click Start, click Control Panel, and then click
Programs and Features.
2.Click your Microsoft Office program, and then click Change.
3.Select Online Repair, and then click Repair.
If the Online Repair doesn't fix the issue, I would suggest you to try using Microsoft Fix It tool to remoe Office 365 completely, then reinstall it:
http://support.microsoft.com/kb/2739501
Hope this helps, and feel free to post back with any feedback.
Thanks,
Ethan Hua CHN
TechNet Community Support

How to uninstall unwanted programs on Office 365 ProPlus

Dear Sir,
I use Windows 8.1 and use Office 365 ProPlus. When I install it, the Office is streamed and installed as a whole in my computer.
How can I remove the unwanted program (like Access) ?
Thanks,
Joe.

The setup.exe version is 15.0.4623.1001
I also use your configuration's content to test, but it still get the same error.
It refers to below link :
http://support.microsoft.com/kb/2696484/en-us
As a test I tried this:
<Configuration>
<Add SourcePath="" OfficeClientEdition="32" >
<Product ID="VisioProRetail">
<Language ID="en-us" />
<ExcludeApp ID="Visio" />
</Product>
</Add>
</Configuration>
This installed VisioPro, with the Visio application "Excluded".
The end result = VisioPro was "installed" without the Visio "application".
(yes, it's kind of a stupid test, but it verified the syntax on the XML file)
To make this work, I needed to uninstall VisioPro first.
You may need to uninstall/reinstall Office, since your Office installation state may be inconsistent?
[if you do this, apply your modified XML file during the reinstallation (/configure) phase]
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!)

Customize Office 365 ProPlus Installation

Hello,
I have Office 365 E3 licenses.
I would like to customize the Office 365 ProPlus so it does the following:
Uninstalls the existing Office 2007 Standard and Lync 2010.
Installs Office 365 ProPlus, but excludes Access.
Does this silently / without user interaction.
How can I accomplish this?
Thank you

Hi
We might be able to do this using the
Office Deployment Tool. There are just a few easy steps you’ll need to take to reproduce the experience of installing Office 365 ProPlus from the Office 365 portal:
Download the Office Deployment Tool
Create an XML file with instructions on how to install Office 365 ProPlus
Create a self-extracting executable (.exe) file that runs the Office Deployment Tool along with the xml file
After you create and test your self-extracting .exe file, publish it to your company portal.
Here’s a link for your reference:
http://blogs.technet.com/b/office_resource_kit/archive/2013/08/08/how-to-deploy-office-365-proplus-from-an-on-premises-web-portal.aspx
http://blogs.technet.com/b/microsoft_in_education/archive/2013/11/11/what-are-my-options-to-deploy-office-365-proplus.aspx
For detailed information on configuration.xml file, refer to the article below:
http://technet.microsoft.com/en-us/library/jj219426.aspx
Here’s a link on Office Deployment Tool:
http://technet.microsoft.com/en-us/library/jj219422.aspx
Best regards
Tylor Wang
TechNet Community Support

Office 365 ProPlus Source files & Updates.

Similar Messages

Maybe you are looking for