Hi,

I'm using ODT on my organization to make a network share that has the updated version of Click-To-Run Office 2013 Home and Business x86.

The problem is that I want to keep the folder with the latest updates using a scheduled task and it isn't working.

The scheduled task runs this batch file:

setup.exe /download configuration.xml

The content of configuration.xml is:

<Configuration>

  <Add SourcePath="\\server\odt\" OfficeClientEdition="32" >
    <Product ID="HomeBusinessRetail">
      <Language ID="pt-br" />
    </Product>
  </Add>
  <Updates Enabled="TRUE" UpdatePath="\\server\odt" />
  <Logging Path="\\server\odt\userlogs" />

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

</Configuration>

When I run the batch file, it downloads the updated version. Using scheduled task, it does nothing.

Hi Vandrey:

Based on your description, it's more likely a scheduled task setting issue. As this forum is focusing on Office client related issue, this forum will be the best place for your question if you are using Windows server, otherwise you can post it in Windows forum if you are using Windows client.

However we can perform some basic troubleshooting regarding this as following:

1. Make sure the user account you set to this task is in admin group and had the permission to run this task.

2. Make sure in your batch file, you specified the UNC path of setup.exe and the configuration.xml

3. Make sure your action setting is correct.

   

4. Check the history of your scheduled task, see if there any error logged there, it might helpful for you to narrow down the issue.

    

Thanks for your understanding.

Hi Vandrey:

Based on your description, it's more likely a scheduled task setting issue. As this forum is focusing on Office client related issue, this forum will be the best place for your question if you are using Windows server, otherwise you can post it in Windows forum if you are using Windows client.

However we can perform some basic troubleshooting regarding this as following:

1. Make sure the user account you set to this task is in admin group and had the permission to run this task.

2. Make sure in your batch file, you specified the UNC path of setup.exe and the configuration.xml

3. Make sure your action setting is correct.

   

4. Check the history of your scheduled task, see if there any error logged there, it might helpful for you to narrow down the issue.

    

Thanks for your understanding.

• Proposed as answer by Chloe WangMicrosoft employee, Moderator 3 hours 52 minutes ago

Hi Vandrey:

Based on your description, it's more likely a scheduled task setting issue. As this forum is focusing on Office client related issue, this forum will be the best place for your question if you are using Windows server, otherwise you can post it in Windows forum if you are using Windows client.

However we can perform some basic troubleshooting regarding this as following:

1. Make sure the user account you set to this task is in admin group and had the permission to run this task.

2. Make sure in your batch file, you specified the UNC path of setup.exe and the configuration.xml

3. Make sure your action setting is correct.

   

4. Check the history of your scheduled task, see if there any error logged there, it might helpful for you to narrow down the issue.

    

Thanks for your understanding.

• Proposed as answer by Chloe WangMicrosoft employee, Moderator Sunday, July 12, 2015 3:33 AM
• Marked as answer by Vandrey Trindade 19 hours 47 minutes ago

Hi Vandrey:

Based on your description, it's more likely a scheduled task setting issue. As this forum is focusing on Office client related issue, this forum will be the best place for your question if you are using Windows server, otherwise you can post it in Windows forum if you are using Windows client.

However we can perform some basic troubleshooting regarding this as following:

1. Make sure the user account you set to this task is in admin group and had the permission to run this task.

2. Make sure in your batch file, you specified the UNC path of setup.exe and the configuration.xml

3. Make sure your action setting is correct.

   

4. Check the history of your scheduled task, see if there any error logged there, it might helpful for you to narrow down the issue.

    

Thanks for your understanding.

• Proposed as answer by Chloe WangMicrosoft employee, Moderator Sunday, July 12, 2015 3:33 AM
• Marked as answer by Vandrey Trindade Sunday, July 12, 2015 11:44 AM

Chloe Wang,

Hi.

Thanks for trying to help but it's not a permission problem. Double checked that. I'm running the task as domain administrator. Doesn't matter the path... It happends the same. The task runs for a while... And nothing gets downloaded. No error from nowhere... No logs... Nothing.

Hi Vandrey:

As if you run the script manually it worked fine, we can narrow down it to the scheduled task. What is the OS of your machine where you set-up this scheduled task? Have you shared the target download folder which you gave in the SourcePath?

Chloe Wang,

Thanks a lot for your time and attention.

I'm using Windows Server 2008 R2 and the folder was shared.

But anyway... Tried here to recreate the process and found what was the problem.

I was using a task that triggered a batch file ODTDownload.bat that has this code:

setup.exe /download download.xml

That batch file was on a folder on the file server.

When the task scheduler started that task it was running from C:\Windows\System32

So there is no setup.exe on this path (and even if there was one file with that name on the directory it should not have the parameters /download download.xml lol).

So I've changed the ODTDownload.bat source code to access the correct directory first.

(More info that could help more people: http://www.blogfodder.co.uk/2012/4/20/win-2008-task-scheduler-with-return-code-1-0x1)

Thanks once again!

• Marked as answer by Vandrey Trindade 16 hours 59 minutes ago
• Edited by Vandrey Trindade 14 hours 23 minutes ago

Chloe Wang,

Thanks a lot for your time and attention.

I'm using Windows Server 2008 R2 and the folder was shared.

But anyway... Tried here to recreate the process and found what was the problem.

I was using a task that triggered a batch file ODTDownload.bat that has this code:

setup.exe /download download.xml

That batch file was on a folder on the file server.

When the task scheduler started that task it was running from C:\Windows\System32

So there is no setup.exe on this path (and even if there was one file with that name on the directory it should not have the parameters /download download.xml lol).

So I've changed the ODTDownload.bat source code to access the correct directory first.

(More info that could help more people: http://www.blogfodder.co.uk/2012/4/20/win-2008-task-scheduler-with-return-code-1-0x1)

Thanks once again!

• Marked as answer by Vandrey Trindade Friday, July 10, 2015 2:31 PM
• Edited by Vandrey Trindade Friday, July 10, 2015 5:06 PM

Chloe Wang,

Thanks a lot for your time and attention.

I'm using Windows Server 2008 R2 and the folder was shared.

But anyway... Tried here to recreate the process and found what was the problem.

I was using a task that triggered a batch file ODTDownload.bat that has this code:

setup.exe /download download.xml

That batch file was on a folder on the file server.

When the task scheduler started that task it was running from C:\Windows\System32

So there is no setup.exe on this path (and even if there was one file with that name on the directory it should not have the parameters /download download.xml lol).

So I've changed the ODTDownload.bat source code to access the correct directory first.

(More info that could help more people: http://www.blogfodder.co.uk/2012/4/20/win-2008-task-scheduler-with-return-code-1-0x1)

Thanks once again!

• Marked as answer by Vandrey Trindade Friday, July 10, 2015 2:31 PM
• Edited by Vandrey Trindade Friday, July 10, 2015 5:06 PM

Thanks for the update.

BTW, that was what I talked about in my first reply.

Chloe Wang,

"Make sure in your batch file, you specified the UNC path"

My apologize =p

Marked as an answer your reply! =]

• Edited by Vandrey Trindade 19 hours 46 minutes ago

Chloe Wang,

"Make sure in your batch file, you specified the UNC path"

My apologize =p

Marked as an answer your reply! =]

• Edited by Vandrey Trindade Sunday, July 12, 2015 11:44 AM

No problem at all. Thank you for using our forum support service.