We have noticed that Infrastructure Manager uses different locations for storing the conf_*.exe probe configuration GUI utilities.
Examples include:
C:\Users\username\AppData\Local\Temp\util
C:\Users\username\AppData\Local\Temp\1\util
C:\Users\username\AppData\Local\Temp\2\util
etc.
Why does this differ and what determines which one is used?
I've seen error messages about a failure to write the UI files to other locations.
It seems like if this is going to be handled correctly the files should be written to:
C:\Program Files (x86)\Nimsoft\Users\<my_user_id>AppData\Local\Broadcom
or maybe
C:\Program Files (x86)\Nimsoft\Users\\<my_user_id>\AppData\Local\Nimsoft
for instance.
With the current randomness, you will frequently get the "cant write file to..." error dialog when opening the probe GUIs because if a common location is chosen and another user opened the GUI before you, likely you will not be able to replace the files. Similarly, if the server has multiple logins, it is possible that the same probe GUI will be open by another user.
And along the lines of items that are annoying about the IM probe GUIs, there are conflicting instances of the file nimbus_AES.dll and nimbusI18n.dll which get locked as soon as a probe GUI is launched and so you will get an error message if for instance, the cdm 6.84 GUI is open and you try to open cdm v4.60.
The infrastructure Manager (IM) first queries the %TEMP% environment variable to determine the appropriate temporary folder.
A number like \1\ or \2\ is automatically appended by the Windows API when requesting storage here.
If the user is directly logged into a physical server when creating the follder, it will go straight into \util\.
If the user is logged into a Remote Desktop session they will get a /1/ or /2/ depending on the version of Windows and on the number of other users logged in to the same system.