How to install BigFix Explorer on a custom path?

That. We never install applications on the C:\ drive and the Fixlet to install the BigFix Explorer service doesn’t allow to specify a custom installation path.

1 Like

We had the same issue. If the server is Windows, you can create a copy of the Install BigFix Explorer content and update line 11 from:

parameter "explorerDir" = "{pathname of program files x32 folder}\BigFix Enterprise\BES Explorer"

to

parameter "explorerDir" = "YOUR CUSTOM DRIVE:\Program Files (x86)\BigFix Enterprise\BES Explorer"
3 Likes

I will give it a try and report back, Thanks!

That worked like charm. However, after enabling the service and started seeing the API was routing the calls to the BigFix Explorer service I noticed the requests were timing out. They stay active for more than 10 min before timing out due to our code settings.

I enabled the service in a sandbox environment a few days ago and haven’t noticed it but the deployment in our prod environment is presenting this behavior. I am planning to open a support case with HCL next week in the meantime I am shutting down the service and let the REST API requests go through Web Reports.