How to upgrade the Splunk App for Windows Infrastructure

The commands shown in this topic are PowerShell. If you use *nix, substitute the PowerShell directives with their *nix counterparts. If you use different directories for Splunk Enterprise and deployment server, substitute the directories shown with your specific directories.

The search head is the Splunk Enterprise instance that runs the Splunk App for Windows Infrastructure and shows all of the app data. These upgrade instructions should be performed on any host that has been designated as a search head in your deployment.

1. Backup local changes (local folder) created on the search head and search head deployer (Optional).
2. Remove the existing app and add-on from your search head (/etc/apps) or search head cluster (/etc/shcluster/apps) environment.
3. Put the new extracted app in the /etc/shcluster/apps/ directory on your search head deployer. If you have a single search head, put the new extracted app in /etc/apps/.
4. Copy the local folder in the /etc/shcluster/apps/splunk_app_windows_infrastructure/ on the searchhead deployer (in case of standalone searchhead, put the local folder in /etc/apps/splunk_app_windows_infrastructure/)
5. Push the updated bundle from the search head deployer to all your search heads.
6. Once the apps are pushed successfully, run the guided setup again on any one of the search heads.

Troubleshoot permissions issues after an upgrade

The Splunk App for Windows Infrastructure installs a new user role, winfra-admin. The Splunk user that uses the Splunk App for Windows Infrastructure must have this role, otherwise the app will not function correctly.

If, during the first time process, you see that the app does not find any data and you know that the data exists (such as in the case of an upgrade), be sure to add the winfra-admin role to the user that uses the app, as described in the troubleshooting page.