We were able to determine that the _conf.exe file is not always downloading correctly. We suspect this is because of anti-virus scanning, Carbon Black. The files normally get downloaded to the user's %TEMP% or %TMP% folder. The security software may be scanning that folder.
Since the Nimsoft folder is omitted from the scan, we can do the following. For each user's profile, we can modify the environment variables for the user (not the system) TEMP=C:\Program Files (x86)\Nimsoft\util TMP=C:\Program Files (x86)\Nimsoft\util
Alternatively, you can use a batch file to launch the IM console:
set TEMP=C:\Program Files (x86)\Nimsoft\util set TMP=C:\Program Files (x86)\Nimsoft\util "C:\Program Files (x86)\Nimsoft\bin\NimBUSManager.exe"
Process flow: The Infrastructure Manager console makes a call to the "distsrv" probe for the probe you are trying to open. This in on the archive of the hub you are connected to with IM. The "distsrv" looks for the probe archive package for a GUI (<probe_name>_conf.exe). It then transfers this back to the IM and puts it in the %temp% folder. T Next, the IM console makes a call ot get the .cfg for the probe and it is passed to the .exe for the probe to display.