Office 365 ProPlus deployment from SCCM 2012

hi, I am trying to deploy office 365 proplus using sccm 2012 , everything seems to good, setup.exe run with /configure (path for file). but it is only running nothing installed on systems.
I used for reference
http://www.youtube.com/watch?v=-PNTdap9hwU
https://sccmguru.wordpress.com/tag/office-365-proplus/
please help .
manish yadav

Hi,
Please refer to the links below:
Using Office 365 ProPlus with the Office Deployment Tool
http://www.petri.com/using-office-365-proplus-with-office-deployment-tool.htm
How to deploy Office 365 with Click-to-Run and ConfigMgr
http://www.configmgr.no/2013/06/09/how-to-deploy-office-365-with-click-to-run-and-configmgr/
Getting started guide for deploying Office 365 ProPlus
http://technet.microsoft.com/en-us/library/jj839718(v=office.15).aspx
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Similar Messages

Office 365 ProPlus deployment and Automation

I will starting a project deploying office 365 ProPlus in an enterprise and seeking assistance on following:-
customer Scenario:
1- SCCM 2012 R2
2- Active Directory 2008 R2
3- Mix of Office 2010/2013 professional installed on client machine
I would like to understand following:-
Installation Scenario:
1- on Office 2013 installed desktop, can I run office 365 Proplus installation on top of existing office 2013 client (standalone)
2- on Office 2010 installed desktop, can I run office 365 Proplus installation on top of existing office 2010 client (standalone)
Uninstallation Scenario:
1- if existing Office need to be removed before deploying cloud Office, what is the best procedure to automate the installation of existing office client from desktop pc either using group policy or SCCM.
I am looking for fully automated uninstallation procedure irrespective of existing Office version or separately for Office 2010 and Office 2013 either using group policy or SCCM.
Farrukh Anwar

Hi Farrukh,
For the installation scenario, you can run the latest version of Office (click-to-run based version) side-by-side with an earlier version of Office that is already installed on your computer. That is to say:
MSI-based version of Office 2013 on a system with Click-To-Run-based version of Office 2013 (Office 365 Proplus ) installed side-by-side is not supported.
MSI-based version of Office 2010 and Click-To-Run-based version of Office 2013 (Office 365 Proplus ) will run side-by-side, but we don't recommend this for a long-term use.
Regarding the uninstallation scenario, you can automate the uninstallation of existing Office via
command line. It will look similar to the following example:
\\server\share\Office12\setup.exe /uninstall ProPlus /config <pathtoUninstallconfig.xml>\UninstallConfig.xml
You can easily integrate this command line into SCCM or a Group Policy computer startup scripts.
Here is a great blog post about how to upgrade to the latest version of Office, you might want to have a look:
http://blogs.technet.com/b/odsupport/archive/2014/11/03/how-to-uninstall-office-2010-and-move-to-office-2013-click-to-run-or-volume-license.aspx
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.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Exe application deployment from SCCM 2012 R2

Hi,
is any limitation to deploy the .exe application from SCCM 2012 R2??
Shailendra Dev

No limitation. You just need to know how to install it silently. It is a more manual configuration than if you had an MSI.
Example here
http://www.gerryhampsoncm.blogspot.ie/2013/03/sccm-2012-sp1-step-by-step-guide-part_20.html
Gerry Hampson | Blog:
www.gerryhampsoncm.blogspot.ie | LinkedIn:
Gerry Hampson | Twitter:
@gerryhampson

MS Office Pro 2013 Deployment through SCCM 2012 R2

Hi Friends,
I have deployed MS Office Pro 2013 through SCCM 2012. But from Windows 7 Client Machines It's not Installing. Noticed following error in Software Center.
I'm testing two deployments before bring into production.
Test Machine 1 : Purpose = Available
From Software Center I have found Test Machine 1 is Status failed.
Test Machine 2 : Purpose = Required
From Software Center I have found Test Machine 2 is Status post due-will be retried
The following Error code is same for both Machines.
====================================================
The software change returned error code 0x87D00607(-2016410105).
====================================================
Any idea please .
Regards,Ali

Hi,
Check out this great guide from Ronni on how to deploy Office 2013 using Configuration Manager 2012, a good read.https://gallery.technet.microsoft.com/office/How-to-Deploying-Office-0f954e7f
Are the content succefully deployed to all DPs?
Regards,
Jörgen
-- My System Center blog ccmexec.com -- Twitter
@ccmexec

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.

Deploying Office 365 Pro Plus via SCCM

Hi
I am trying to deploy Office 365 Pro Plus via SCCM, I followed this process https://gallery.technet.microsoft.com/How-To-Deploying-Office-70e8b1eb#content , we don't use the application catalogue but I made the application available to be run via system
center.
Though can't get it deployed, I keep getting some errors about checking internet connections ...though I can run the command manually and it'works.
Does anyone managed to install it via SCCM ?

Thank you for the reply,
Where I am lost is where it downloads the Office C2R from ?
Logs from the Temp folder
03/04/2015 10:51:15.947 SETUP (0xf10)
0x107c Click-To-Run
anhmm Medium
Prereq::PrereqsFailed: No prereqs have failed.
03/04/2015 10:51:16.228 SETUP (0xf10)
0x107c Click-To-Run
aoh9t Medium
TryLaunchClient::HandleStateAction: Launching OfficeClickToRun.exe with parameters: scenario=unknown acceptalleulas="True" cdnbaseurl="http://officecdn.microsoft.com/pr/39168D7E-077B-48E7-872C-B232C3E72675" productreleaseid="none"
displaylevel="False" culture="en-us" baseurl="C:\WINDOWS\ccmcache\5l" lcid="1033" platform="x86" updatesenabled="False" o365proplusretail.excludedapps="access,groove,lync,project,sharepointdesigner,visio"
version="15.0.4675.1003" productstoadd="O365ProPlusRetail_en-us_x-none" trackedduration=280
03/04/2015 11:01:12.393 SETUP (0xf10)
0x107c Click-To-Run
aoh72 Medium
ExitBootStateMachine::HandleStateAction: Bootstrapper workflow exiting with result: 0x0
Logs from SCCM AppEnforce shows this (can't see it failing)
<![LOG[+++ Starting Install enforcement for App DT "Install - Microsoft Office 365 ProPlus" ApplicationDeliveryType - ScopeId_2A03C658-AF66-44B9-85ED-4FADE04A803B/DeploymentType_5a39078c-a7a3-438c-af16-0cb0a0674479, Revision - 7, ContentPath
- C:\WINDOWS\ccmcache\5l, Execution Context - System]LOG]!><time="10:50:45.222-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appprovider.cpp:1702">
<![LOG[ A user is logged on to the system.]LOG]!><time="10:50:45.243-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appprovider.cpp:2083">
<![LOG[ Performing detection of app deployment type Install - Microsoft Office 365 ProPlus(ScopeId_2A03C658-AF66-44B9-85ED-4FADE04A803B/DeploymentType_5a39078c-a7a3-438c-af16-0cb0a0674479, revision 7) for system.]LOG]!><time="10:50:45.247-600"
date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_2A03C658-AF66-44B9-85ED-4FADE04A803B/DeploymentType_5a39078c-a7a3-438c-af16-0cb0a0674479, Revision: 7]]LOG]!><time="10:50:45.287-600" date="03-04-2015" component="AppEnforce"
context="" type="1" thread="5596" file="localapphandler.cpp:291">
<![LOG[ App enforcement environment:
Context: Machine
Command line: Setup.exe /configure Install.xml
Allow user interaction: No
UI mode: 1
User token: null
Session Id: 1
Content path: C:\WINDOWS\ccmcache\5l
Working directory: ]LOG]!><time="10:50:45.288-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appcontext.cpp:85">
<![LOG[ Prepared working directory: C:\WINDOWS\ccmcache\5l]LOG]!><time="10:50:45.290-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appcontext.cpp:189">
<![LOG[ Prepared command line: "C:\WINDOWS\ccmcache\5l\setup.exe" /configure Install.xml]LOG]!><time="10:50:45.340-600" date="03-04-2015" component="AppEnforce" context="" type="1"
thread="5596" file="appcontext.cpp:338">
<![LOG[ Executing Command line: "C:\WINDOWS\ccmcache\5l\setup.exe" /configure Install.xml with user context]LOG]!><time="10:50:45.341-600" date="03-04-2015" component="AppEnforce" context=""
type="1" thread="5596" file="appexcnlib.cpp:201">
<![LOG[ Working directory C:\WINDOWS\ccmcache\5l]LOG]!><time="10:50:45.341-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appexcnlib.cpp:215">
<![LOG[ Post install behavior is BasedOnExitCode]LOG]!><time="10:50:45.529-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appcommon.cpp:1094">
<![LOG[ Waiting for process 3856 to finish. Timeout = 120 minutes.]LOG]!><time="10:50:45.533-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596"
file="appexcnlib.cpp:1958">
<![LOG[ Process 3856 terminated with exitcode: 0]LOG]!><time="11:01:12.428-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appexcnlib.cpp:1967">
<![LOG[ Looking for exit code 0 in exit codes table...]LOG]!><time="11:01:12.429-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appexcnlib.cpp:505">
<![LOG[ Matched exit code 0 to a Success entry in exit codes table.]LOG]!><time="11:01:12.430-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appexcnlib.cpp:584">
<![LOG[ Performing detection of app deployment type Install - Microsoft Office 365 ProPlus(ScopeId_2A03C658-AF66-44B9-85ED-4FADE04A803B/DeploymentType_5a39078c-a7a3-438c-af16-0cb0a0674479, revision 7) for system.]LOG]!><time="11:01:12.621-600"
date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appprovider.cpp:2148">
<![LOG[+++ Application not discovered. [AppDT Id: ScopeId_2A03C658-AF66-44B9-85ED-4FADE04A803B/DeploymentType_5a39078c-a7a3-438c-af16-0cb0a0674479, Revision: 7]]LOG]!><time="11:01:12.739-600" date="03-04-2015" component="AppEnforce"
context="" type="1" thread="5596" file="localapphandler.cpp:291">
<![LOG[++++++ App enforcement completed (627 seconds) for App DT "Install - Microsoft Office 365 ProPlus" [ScopeId_2A03C658-AF66-44B9-85ED-4FADE04A803B/DeploymentType_5a39078c-a7a3-438c-af16-0cb0a0674479], Revision: 7, User
SID: ] ++++++]LOG]!><time="11:01:12.748-600" date="03-04-2015" component="AppEnforce" context="" type="1" thread="5596" file="appprovider.cpp:2448">

Uninstall Office 2010/2013 to deploy Office 365 ProPlus

following clarification is needed:-
some of the pc is installed with Office 64 Bit edition, we are trying to remove the existing office (desktop) before deploying office 365 ProPlus. SCCM 2012 R2 is going to be used to uninstall office. my question is that can I remove/uninstall 64 bit Office
using 32 Bit setup.exe or it has to be 64 bit for 64 bit office and 32 bit setup.exe for 32 bit office.
also if I am looking for assistance to create query that can result in 64 bit and 32 bit office using SCCM. please paste the query in the response if possible.
Thanks
Farrukh
Farrukh Anwar

I would recommend that deploy a script that first removes the old version of Office and then Deploy the new version.
My favorite script tool to use with SCCM is the PowerShell App Deployment Toolkit, and that would be great in this example too.
Ronni Pedersen | Microsoft MVP - ConfigMgr | Blogs:
www.ronnipedersen.com/ and www.SCUG.dk/ | Twitter
@ronnipedersen

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?

Lync 2013 x64 silent client deployment via SCCM 2012 SP1

Greetings everyone!
I ran into a problem with Lync 2013 x64 silent deployment.
I need to provide every workstation with Lync 2013 client, so i decided to use deployment via SCCM 2012 sp1.
I created 2 msp files with OCT, one based on x86 Office 2013 Proplus, and other based on x64 Office 2013 Proplus.
Added them as applications to sccm software library.
Deployment of Lync 2013 x86 application was a success with over than 80% compliance.
But all Lync 2013 x64 automatic installations finish with different errors.
I created special device collection for workstations with office 2010 x64 and 2013 x64, because i can't install other architecture products once it has x64 product installed.
My membership query-rules for this collection:
Office 2013 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90150000-0011-0000-1000-0000000FF1CE}"
Office 2010 x64
select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_INSTALLED_SOFTWARE on SMS_G_System_INSTALLED_SOFTWARE.ResourceId
= SMS_R_System.ResourceId where UPPER(SMS_G_System_INSTALLED_SOFTWARE.SoftwareCode) = "{90140000-0011-0000-1000-0000000FF1CE}"
My application deployment type points to setup.exe in office 2013 x64 installation folder, where i created msp file in updates folder via OCT and edited config.xml file in proplus.ww folder.
So my installation program looks like this setup.exe /adminfile updates\1lync.msp /config proplus.ww\config.xml
The same configuration works with Lync 2013 x86 deployment, except other setup folders.
When i try running installation program setup.exe with /adminfile and /config parameters locally, it installs successfully without errors or warnings.
I'm trying to find out problem source, does anyone have ideas what I am doing wrong?
Also i'm trying to reduce office 2013 installation folder size, what subfolders are necessary for Office 2013 proplus installation (still installing only lync with common files and tools)? Because now 3.5 GB package is quite hard to distribute to sccm secondary
sites with deployment point.
Thanks in advance.

Hi,
Here are some tips and tricks for your reference.
Tips and Tricks: Deploying Lync 2013 client using SCCM 2012 | Lync 2013 Client Customization for SCCM 2012 Deployment Package
http://zahirshahblog.com/2014/01/08/tips-and-tricks-deploying-lync-2013-client-using-sccm-2012-lync-2013-client-customization-for-sccm-2012-deployment-package/
Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

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.

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

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 ProPlus Outlook freezes

I am doing a 365 deployment for a company and some of the users previously had office 2007 and some had office 2013. The issue I am running into deals with the people that had office 2007. I use the Microsoft Fix It tool to uninstall Office 2007. After the
computer restarts, I install Office 365 ProPlus from OWA for each individual user. When setting up these people's Outlook profiles, it always hangs up on the Windows Security Credentials asking for the exchange password again. I have to open task manager and
close out Outlook. There are no issues with the users who had 2013 installed on their computers. Does anyone have a solution to this problem?
Nick

Hi,
We may need to collect information from the Event Logs to find the cause of this issue.
Press Win + R, type "eventvwr" in the blank box, press Enter.
Browse to Windows Logs -> Application, once the issue occurs, there should be some error messages from which we may find the cause of the problem.
You can also send us the logs if there is any, thus we can help analyze the issue. To protect your private information, please send the information to our email address:
[email protected]
Regards,
Melon Chen
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 Shared Computer Activation - users are prompted to activate, proxy issue?

Hi all,
We're currently testing the roll-out of Office 365 ProPlus with shared computer activation but are having problems with Office automatically activating (with no user prompts) when using our web proxy.
I've already added proxy exceptions (in our PAC file) for the 'Office 365 portal and identity' and 'Office 365 ProPlus' URLs (not Content Delivery Network) from
https://technet.microsoft.com/en-us/library/hh373144.aspx but test licensed Office 365 E4 users still get the 'Activate Office' prompt and even if they enter in their credentials are ultimately
told 'There is a problem with your account. Please try again later'.
Testing this on a computer not directed through the web proxy works fine and users get no pop-ups whatsoever and Office is licensed.
The problem is I can check the traffic passing through the proxy in real-time and no traffic destined for any of the URLs on the TechNet page actually goes out over the proxy, indeed there is no Microsoft orientated traffic at all. It's as if simply
specifying a proxy on IE's connection settings breaks shared computer activation.
I'm in the process of a support case with our web proxy company itself but if there's anyone out there who can shed any light on this it'd be appreciated.
Thanks in advance.

Read this:
https://technet.microsoft.com/en-us/library/gg702620.aspx
Next read this:
http://blogs.technet.com/b/neiljohn/archive/2012/01/26/office-365-proxy-server-exclusion-list-office-365-service-url-s.aspx
Last: My workaround that's about 6 months old:I
went through the same issue with Websense Cloud Web Security Gateway in my RDSH environment.
Off and on, and seemingly without provocation, users would be prompted for credentials and these credentials would sometimes be accepted and other times they could just cancel out and continue working.
I chalked this up to Microsoft's continual tuning and scaling of their cloud environment (we use Office 365). I suspect Websense was not able to add hosts fast enough and the authentication issue just popped up from time to time.
My solution? A workaround...set the list of recommended MS servers on "bypass" so that any traffic destined to these servers Websense would essentially permit without interference.
Best of luck to you.

Office 365 ProPlus deployment from SCCM 2012

Similar Messages

Maybe you are looking for