Upgrade the remote upgrader without the deployment server

​You can configure the remote upgrader to upgrade itself by dropping the upgrader package and .sig file into the directory C:\ProgramData\splunk\upgrader. ​

​Download the latest version of the remote upgrader and extract the remote upgrader package and .sig file. Once you install the universal forwarder remote upgrader on the Windows box, the directory C:\ProgramData\splunk\upgrader is created, which receives the universal forwarder packages. ​

​To distribute the universal forwarder package without the deployment server, put the following files into this directory: ​

• splunk-upgrader-win.zip

• splunk-upgrader-win.zipsig​

Then ​create a trigger file start_uf_upgrade​ in the directory C:\ProgramData\splunk\upgrader​.

​ You can optionally put both the remote upgrader and universal forwarder packages into the remote upgrader. When you do this, the remote upgrader will self upgrade first, and then the updated remote upgrader will upgrade the universal forwarder. You can deliver the universal forwarder packages using the deployment server and trigger the already running Remote Upgrader for Windows Universal Forwarders to run through the upgrade process. You can do this whether your universal forwarders are running as Admin. For planning purposes, internal testing determined that it takes two hours to distribute 100MB universal forwarder packages to 6800 universal forwarders, with CPU at 40% and memory at 2%. ​