the health check reported that we failed the download folders health check for our main relay. I attempted to run the ‘BES Server/Relay have too many download folders’ fixlet
I run the fixlet on the relay and get the following…
continue if {exists file “downloadcleanerdata.txt” of folder “__Download”}
delete “{value “wwwRootFolder” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server” of registry as string}\downloadcleanerdata.txt”
move “__Download\downloadcleanerdata.txt” “{value “wwwRootFolder” of key “HKEY_LOCAL_MACHINE\SOFTWARE\BigFix\Enterprise Server” of registry as string}\downloadcleanerdata.txt”
When I try to run the task manually, I get an error about not having a DSN available. Any thoughts?
For this Fixlet, you are supposed to run it on the BES Server computer first using the first action (which looks like the one you tried to run) even if the problem isn’t on the BES Server.
After running it on the BES Server, then you use the second action to run it on the BES Relay.
Basically, you have to run it on the BES Server first which creates a data file that the BES Relay version uses.
Check the BES Server version, if you are running 7.2 than you can just upgrade your BES Relay to 7.2 as well. The download folder issue is fixed in 7.2 and above.
If the BES Server is version 6, 7.0 or 7.1, then I would probably just deploy the Fixlet and set the relevance for your action to be true so it will run. Basically, force the action to run on the server and disregard the relevance checks.
Otherwise, you could try running it on the BES Relay manually and giving it commandline arguments to connect to the database. Run the tool with the -h option to get help output with information on database connections (probably need to use the -d, -u and -p options).