Quantcast
Channel: Office 2013 and Office 365 ProPlus - Planning, Deployment, and Compatibility forum
Viewing all articles
Browse latest Browse all 3748

Update path Changed for unknown Reason

$
0
0

Hello,

Currently we are in the middle of an office 365 deployment company wide. We used the deployment tool to create a deployment from a share on a file server the organisation.

We set up the deployment path in the deploymeny.xml file like so

<Configuration>
  <Add SourcePath="\\servername\Office365_install" OfficeClientEdition="32">
   <Product ID="O365ProPlusRetail" >
     <Language ID="en-us" />     
   </Product>
  </Add>
<Updates Enabled="TRUE" UpdatePath="\\servername\Office365_install\" />
</Configuration>

The deployment is initiated via a batch file and Office 365 Is installed on client machines from the share, this is fine.

Checking the Registry on those machines shows in

HKLM\Software\Microsoft\Office\15.0\ClickToRun\configuration\UpdateURL is \\servername\Office365_install as expected.

Checking for updates from any office app says the program is up to date.

All looks good.

This morning we notice that some machines showed the Notification that a new update was available, as I am aware this should not happen if the Update URL is our local file share.

When a user clicked this the Office suite was updated to the latest version.

We do not want this behaviour.

Looking at the previous registry entry

HKLM\Software\Microsoft\Office\15.0\ClickToRun\configuration\UpdateURL is \\servername\Office365_install we find it is no longer there and cannot understand why.

A resintall from the same deployment batch file puts the registry key back in.

Any Idea why this would be happening?

Any Help greatly appreciated.


Viewing all articles
Browse latest Browse all 3748

Latest Images

Trending Articles



Latest Images

<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>