Hi there,
We are planning to integrate another remote office soon with our deadline farm, but due to the limited bandwidth between that location and the LA datacenter, we would like to disable self updating on those machines, so that rollouts can be handled locally.
It would be great to have an ‘enable/disable self updating’ option thats controllable via the database for each slave from the monitor.
If this option already exists, please forgive my ignorance 
cheers,
laszlo
Hey Laszlo,
We don’t have this option yet, but this is a good example of why we should add it. I think we need to add this as a Client-level setting (ie: in the local deadline.ini file on each machine) as opposed to a slave setting. The reason is that the Launcher invokes the auto-update, not the slave. I can see us adding a flag to the client installer to set this, as well as add an entry to it for Auto Configuration.
Also, since the Monitor could also trigger an update, that’s probably a good excuse to extend Auto Configuration to work when the Monitor starts up as well.
Cheers,