Jump to content


kesh

Office 365 Deployment

Recommended Posts

Hi, I am having a problem with my Office 365 ProPlus deployment on SCCM. If I deploy it via an application, it does deploy to the device and installs and there are no issues. However, if i look at my software center, it says that it failed. How can I get that failed to change as this will cause a problem with my users. Also, is it possible to have it install completely silently without the user seeing anything.

I then tried to add it my my Task Sequence, but it does not install. How can I get Office 365 to be included in my TS? My TS goes through fine and installs everything else fine except. Office

 

This is my XML file:

<Configuration>

  <Add OfficeClientEdition="32">
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
    
  </Add>

  <!--  <Updates Enabled="TRUE" Branch="Current" /> -->

  <!--  <Display Level="None" CompletionNotice="no" SuppressModal="yes" AcceptEula="TRUE" />  -->

  <!--  <Property Name="AUTOACTIVATE" Value="1" />  -->

</Configuration>

 

2.jpg

3.jpg

4.png

Share this post


Link to post
Share on other sites

Not sure if you did but first off I would use this to create your XML file:

https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html

It looks like you're just missing the detection method, hence why it's installing but saying failed. Use the MSI code {90160000-008F-0000-1000-0000000FF1CE} as your detection method in SCCM and it should work fine.

Share this post


Link to post
Share on other sites

1 hour ago, jfarmer said:

Not sure if you did but first off I would use this to create your XML file:

https://officedev.github.io/Office-IT-Pro-Deployment-Scripts/XmlEditor.html

It looks like you're just missing the detection method, hence why it's installing but saying failed. Use the MSI code {90160000-008F-0000-1000-0000000FF1CE} as your detection method in SCCM and it should work fine.

Thank you Sir,

I've recreated my XML and changed the detection from registry to MSI code and the standard deployment works with no failed message. I am going to test it on my TS now and feedback later

Share this post


Link to post
Share on other sites

this is the errors I have:

 

Policy Evaluation failed, hr=0x87d00269 InstallApplication 21 Aug 2017 2:48:04 PM 1892 (0x0764)
Setting TSEnv variable 'SMSTSAppPolicyEvaluationJobID__ScopeId_0FE58C1E-2689-48D2-A82C-582D52C27DAC/Application_1cbcb636-f787-47bc-839f-65a356b58062'='' InstallApplication 21 Aug 2017 2:48:04 PM 1892 (0x0764)
EvaluationJob complete InstallApplication 21 Aug 2017 2:48:04 PM 1892 (0x0764)
MP list missing in WMI after policy evaluation InstallApplication 21 Aug 2017 2:48:04 PM 1892 (0x0764)
Sending message to location service to refresh client, retrieve MP list and try again (after delay of 60l sec - up to 1 times). InstallApplication 21 Aug 2017 2:48:04 PM 1892 (0x0764)
m_hResult, HRESULT=87d00269 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1157) InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Step 2 out of 2 complete InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Install application action failed: 'Office 365 ProPlus'. Error Code 0x87d00269 InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Sending error status message InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Setting URL = http://xxxxxxxxxxxxx, Ports = 80,443, CRL = false InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Setting Server Certificates. InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Setting Authenticator. InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Set authenticator in transport InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Setting Media Certificate. InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Sending StatusMessage InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Setting message signatures. InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Setting the authenticator. InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
CLibSMSMessageWinHttpTransport::Send: URL:xxxxxxxxxxxxxxx:80 CCM_POST /ccm_system/request InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Request was successful. InstallApplication 21 Aug 2017 2:49:23 PM 1892 (0x0764)
Process completed with exit code 0 TSManager 21 Aug 2017 2:49:23 PM 3836 (0x0EFC)
!--------------------------------------------------------------------------------------------! TSManager 21 Aug 2017 2:49:23 PM 3836 (0x0EFC)
Successfully completed the action (Install Office365) with the exit win32 code 0 TSManager 21 Aug 2017 2:49:23 PM 3836 (0x0EFC)

Share this post


Link to post
Share on other sites

4 hours ago, kesh said:

Policy Evaluation failed, hr=0x87d00269

 

4 hours ago, kesh said:

MP list missing in WMI after policy evaluation InstallApplication

Your problem seems to lie not in the application itself.

Check out this post. https://larslohmann.blogspot.de/2014/01/task-sequence-fails-with-error.html

Maybe it will help you to solve this.

Share this post


Link to post
Share on other sites

thank you for the link Peter33. I actually tried my TS without the "Setup Windows and Configuration Manager step", and I got the same result and Office still didn't install, as I thought that would be the same as installing a work group computer. I fill try to add the FQDN of the MP to see if that will make a difference.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.