Problem with non-default installation path

It sounds like the issue mentioned above may be related to a problem I'm seeing too.

 

 

The server we installed the F5 MP on (the latest 1.4.1.93 version) does not have a C drive. The drives are remapped to non-standard letters. For example, the system drive is X: rather than C, so that %PROGRAMFILES% is 'X:\Program Files'

 

 

During the F5 MP install, it correctly recognized the different drive letter for the default installation as 'X', so I used that.

 

The MP was installed in that default X:\Program Files directory. HOWEVER, when I try to use it within the SCOM console, the action tasks tools on the right side of the console all reference a C drive, so none of them work.

 

 

For example, if I click on the F5 Action 'Discover F5 devices', it fails and pops up a message stating:

 

 

"Application C:\Program Files\F5 Networks\Management Pack\f5mpgui.exe

 

Parameters: -DiscoverDevices

 

 

Error Message: The system cannot find the file specified"

 

 

It is similar for the other F5 action tasks available.....

 

 

Will that be fixed too?

 

 

It appears I can run the commands manually from a command prompt referencing the correct path, but it would be nice to have this flexible enough to recognize the proper drive within the icons in the SCOM console.

 

 

Thank you