Hi Forum

I have been trying to push Office 2013 click to run install through Intune.

I want to use the source files in the Cloud rather than on a Network Share.

So far I have:

• Downloaded the OCT and downloaded the Setup.exe and the Config.xml
• Changed the config file (a few times, testing and got this working using cmdline)
• I have run the /download and the /configure switch and managed to get this installing from the Cloud locally but not from Intune
• In Intune, I upload the Setup.exe (as primary) and my custom config.xml (is included) using this cmdline I deploy: setup.exe /configure configuration.xml (which managed to install the software locally)
• Then Deployed to the App Portal, I run the install and it fails at 50% every time.
• 

I have left the source path "empty" and with http://officecdn.microsoft.com/pr/?????????????? (link come from downloading .cab files)

Is there something I am doing wrong?

Thanks in advance
NN

One of my config file, replacing "?" with actual numbers from the /download switch

<Configuration>

<Add SourcePath="http://officecdn.microsoft.com/pr/????????????" Version="???.???.???" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>

<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

*Edit - this works locally

One of my config file, replacing "?" with actual numbers from the /download switch

<Configuration>

<Add SourcePath="http://officecdn.microsoft.com/pr/????????????" Version="???.???.???" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>

<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

*Edit - this works locally

• Edited by Naked Nuts Friday, April 26, 2013 12:59 PM

One of my config file, replacing "?" with actual numbers from the /download switch

<Configuration>

<Add SourcePath="http://officecdn.microsoft.com/pr/????????????" Version="???.???.???" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>

<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

*Edit - this works locally

• Edited by Naked Nuts Friday, April 26, 2013 12:59 PM

One of my config file, replacing "?" with actual numbers from the /download switch

<Configuration>

<Add SourcePath="http://officecdn.microsoft.com/pr/????????????" Version="???.???.???" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>

<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

*Edit - this works locally

• Edited by Naked Nuts Friday, April 26, 2013 12:59 PM

One of my config file, replacing "?" with actual numbers from the /download switch

<Configuration>

<Add SourcePath="http://officecdn.microsoft.com/pr/????????????" Version="???.???.???" OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
  </Add>

<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

*Edit - this works locally

• Edited by Naked Nuts Friday, April 26, 2013 12:59 PM

Hey NN,

do you see anything in the logfiles that are created on the machines that are failing?

Hey Philipp

Thanks for responding.
I couldn't find a log file on the VM for Office.

Do you agree that my process and config file looks right?

Thanks
NN

Hey NN,

at first glance i don't see any direct problems no. You could try removing SourcePath altogether:

SourcePath. Indicates the installation source path from which to install Office. If you do not specify SourcePath, Setup will attempt to find an\Office\Data\... folder structure in the working directory from which you are running setup.exe. Then it will fall back to install directly from the external Content Delivery Network Internet source.

Especially that last part makes me curious what would happen if you don't provide a sourcepath, if i read it correctly it should get it from the internet then.

Let me know what that results in.

Hi Philipp

See above "I have left the source path "empty" and with http://officecdn.microsoft.com/pr/?????????????? (link come from downloading .cab files)"

I have tried this one already, I can get this to work through cmdline locally both ways, as soon as I upload this to Intune, it fails 50%.

Weird... unknown why, maybe I am uploading this incorrectly?

I also tried downloading the .cab files and adding them to the upload in Intune, that didn't seem to make any difference, just a more drawn out time consuming 50% progress.

It is so close to working, but at 50% when it looks to the Cloud, it gets lost and fails.

Any other ideas?

NN

Hey NN,

sorry missed that line, i'll see if i can rig up a testlab and try this configuration over the weekend, if i find something i'll let you know.

Hi Solid

Wondering if you managed to get anywhere with this?

Thanks
NN

Hi Forum

Any one out there that can help advise.

I have tried a few ways now and still get stuck at 50%

NN

Calling Mr Jon. L, can you please help?

Hey guys,

We'll take a look at the click to run install of Office 2013 and see if we can provide details on packaging.

Give us a day or two to come back with results.

Thanks,

Jon L. - MSFT

Thanks Jon, appreciative as always.

NN

Hi all,

So after some initial investigation we found it is possible to package and deploy Click to Run 2013 Office.

Here it the configuration.xml I used:

  <Add OfficeClientEdition="32" >
    <Product ID="O365ProPlusRetail">
      <Language ID="en-us" />
    </Product>
    </Add> 
  <!--  <Updates Enabled="TRUE" UpdatePath="\\Server\Share\Office\" /> -->
  <Display Level="None" AcceptEULA="TRUE" />  
<Logging Name="Office2013Click2RunWindowsIntune.txt" Path="%temp%" />
  <!--  <Property Name="AUTOACTIVATE" Value="1" />  -->
</Configuration>

Now you'll notice I removed the "Source Path" you had in your file.  That is only used if you want to point to another web/network share.  In this case, we are pulling directly from Microsoft, so we don't need that.  We also removed the Visio install from the standard Configuration.Xml.

The Command Line Parameters we used in the Intune Package were "/configure configuration.xml" (no quotes)

With that setup, we had no issues installing on a Windows 7 machine.

Now, if the install runs longer than expected (30+ minutes), the install may be timing out and failing.  I'm checking on that and I'll report back after I get my findings.  

Thanks.

Thanks Jon,

Tested this and still getting the above error.

Not too sure what I have done wrong... or what is going wrong.

Any suggestions?

Thanks in advance
NN

edit*

Also, it doesn't make sense how "Source Path" works locally through the cmdline but when in Intune does not.

I am baffled by the fact I can get this to work through cmdline in a number of ways but when uploaded, it fails 50% every time, there must be something blocking this?

**Additional, I have tried without "Source Path" as said above.

The 50% does not happen after 30mins, it happens after around 10 seconds of it reaching that point.

Thanks Jon,

Tested this and still getting the above error.

Not too sure what I have done wrong... or what is going wrong.

Any suggestions?

Thanks in advance
NN

edit*

Also, it doesn't make sense how "Source Path" works locally through the cmdline but when in Intune does not.

I am baffled by the fact I can get this to work through cmdline in a number of ways but when uploaded, it fails 50% every time, there must be something blocking this?

**Additional, I have tried without "Source Path" as said above.

The 50% does not happen after 30mins, it happens after around 10 seconds of it reaching that point.

• Edited by Naked Nuts Thursday, May 02, 2013 8:49 AM

Thanks Jon,

Tested this and still getting the above error.

Not too sure what I have done wrong... or what is going wrong.

Any suggestions?

Thanks in advance
NN

edit*

Also, it doesn't make sense how "Source Path" works locally through the cmdline but when in Intune does not.

I am baffled by the fact I can get this to work through cmdline in a number of ways but when uploaded, it fails 50% every time, there must be something blocking this?

**Additional, I have tried without "Source Path" as said above.

The 50% does not happen after 30mins, it happens after around 10 seconds of it reaching that point.

• Edited by Naked Nuts Thursday, May 02, 2013 8:49 AM

Thanks Jon,

Tested this and still getting the above error.

Not too sure what I have done wrong... or what is going wrong.

Any suggestions?

Thanks in advance
NN

edit*

Also, it doesn't make sense how "Source Path" works locally through the cmdline but when in Intune does not.

I am baffled by the fact I can get this to work through cmdline in a number of ways but when uploaded, it fails 50% every time, there must be something blocking this?

**Additional, I have tried without "Source Path" as said above.

The 50% does not happen after 30mins, it happens after around 10 seconds of it reaching that point.

• Edited by Naked Nuts Thursday, May 02, 2013 8:49 AM

Thanks Jon,

Tested this and still getting the above error.

Not too sure what I have done wrong... or what is going wrong.

Any suggestions?

Thanks in advance
NN

edit*

Also, it doesn't make sense how "Source Path" works locally through the cmdline but when in Intune does not.

I am baffled by the fact I can get this to work through cmdline in a number of ways but when uploaded, it fails 50% every time, there must be something blocking this?

**Additional, I have tried without "Source Path" as said above.

The 50% does not happen after 30mins, it happens after around 10 seconds of it reaching that point.

• Edited by Naked Nuts Thursday, May 02, 2013 8:49 AM

Can you post your current configuration.xml here?

Thanks.

<Configuration>

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

<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

Can you look in the updates.log in the c:\program files\microsoft\online management\logs and see what the error code is being returned from your installer?

If you want, open a support case and we can perform a remote session and do some debugging today.  Let the support agent know you are working with me and to bring me into any remote sessions.

Thanks,

Jon

Hallalujah!

Don't know what the issue was... but it works now.

Thanks for your help. I am guessing an update, but... I cannot be sure.

I will post back if i find an answer to the problem.

This config file does work:

<Configuration>

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

<Display Level="None" AcceptEULA="TRUE" />
<Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

Thanks

NN

Hi,

Could you please tell me if Windows Intune only loads 167Kb of Office 365 Pro Plus Click To Run software?

Thanks

HI,

I wondered if anyone can help. I too would like to able to install Office 2013 from my Office 365 account to all PC's using Intune. 

I have tried to follow the documentation but cant get this to work. Here is where I am so far:

1. Downloaded Office Deployment Tool for Click to run
2. Ran the setup /download "Path to Config File"
3. Used this Config file

<Configuration>

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

<Display Level="None" AcceptEULA="TRUE" />
< Logging Name="OfficeSetup.txt" Path="%temp%" />

</Configuration>

This downloaded OK but not sure where. I am unsure what to do after that. I am, at this point just trying to get it working locally. I ran setup /configure "Path to Config File"  that prompted me to run the Click to run install, however, this just flashes up on the screen and is gone.

Please advise, I don't know when this should be so difficult

Regards

Jason

Once you hit 'Run' it will install silently in the background, it is not an instant install you will need to be patient before you see any changes, then it will appear the same as any other version of Office. I suggest you open your own thread to get a solution fit for yourself.

If you use this thread as a guide on the install you shouldn't go far wrong.

NN

Once you hit 'Run' it will install silently in the background, it is not an instant install you will need to be patient before you see any changes, then it will appear the same as any other version of Office. I suggest you open your own thread to get a solution fit for yourself.

If you use this thread as a guide on the install you shouldn't go far wrong.

NN

• Proposed as answer by Thimo Buchheister Tuesday, August 06, 2013 6:50 AM
• Unproposed as answer by Thimo Buchheister Tuesday, August 06, 2013 6:50 AM

Once you hit 'Run' it will install silently in the background, it is not an instant install you will need to be patient before you see any changes, then it will appear the same as any other version of Office. I suggest you open your own thread to get a solution fit for yourself.

If you use this thread as a guide on the install you shouldn't go far wrong.

NN

• Proposed as answer by Thimo Buchheister Tuesday, August 06, 2013 6:50 AM
• Unproposed as answer by Thimo Buchheister Tuesday, August 06, 2013 6:50 AM

Once you hit 'Run' it will install silently in the background, it is not an instant install you will need to be patient before you see any changes, then it will appear the same as any other version of Office. I suggest you open your own thread to get a solution fit for yourself.

If you use this thread as a guide on the install you shouldn't go far wrong.

NN

• Proposed as answer by Thimo Buchheister Tuesday, August 06, 2013 6:50 AM
• Unproposed as answer by Thimo Buchheister Tuesday, August 06, 2013 6:50 AM

Once you hit 'Run' it will install silently in the background, it is not an instant install you will need to be patient before you see any changes, then it will appear the same as any other version of Office. I suggest you open your own thread to get a solution fit for yourself.

If you use this thread as a guide on the install you shouldn't go far wrong.

NN

• Proposed as answer by Thimo Buchheister Tuesday, August 06, 2013 6:50 AM
• Unproposed as answer by Thimo Buchheister Tuesday, August 06, 2013 6:50 AM

Thanks I will try some patience :) Does the method look to be correct so far ?

try this:

Open CMD from the file explorer using shift right click, open CMD

type setup.exe /configure configuration.xml

A bootstrapper prompt should appear, click yes.

that should install locally after time and will in appear in All Programs.

Thanks
NN

Thanks that is what I have done. How patient should I be. It has been over an hour, are there any logs I can look at or see any process that may be running ? 

I have posted new thread BTW and will revert to that one (cant post a link until my accounts has been verified.

Subject: Office 2103 Deployment from Windows Intune

@Jon

I've uploaded setup.exe and configuration.xml to my intune storage. I have specified the cmdline for the software to be /configure configuration.xml. I see an app running labeled integratedoffice.exe running but nothing is happening. I don't see any new office apps showing up, and unless i'm dense I don't see anything related to setup, office, or configuration.xml listed in the update log.

My target machine is Windows 8.1 Pro, is there something different about this? is there something I am missing?

Additionally I do not see it listed in my company portal under apps, so that makes me think that perhaps my deployment is wrong? I have it set to install as soon as possible on the group my computer is in. I also have it deployed to all users and after a policy refresh I am not seeing it show up in the company portal for installation.

Here are the details for the app

Requirements:

Architecture = Any

Operating System = Windows 7 to all newer

Detection Rules:

Default Rules

Command Line Arguments:

/configure configuration.xml

Return Codes:

Default

I'm actually tempted to remove the software rename my update log and then redeploy. In fact, I think i'll do that now and then get back to you.