Default Startup Settings when starting from share?

Hello,

when someone starts the ARM GUI for the first time they have to enter the server.

We have a lot of new people using ARM and switching devices. It would be nice if there were a way how we could pre-fill the Server field.

Is there any way to achieve this?

I haven't found any documentation on how to do this, but it seems like it should be doable somehow. Only thing i was able to find was this documentation on various pdfs and pages. I would expect this information to be on here, but it isn't: https://documentation.solarwinds.com/en/success_center/arm/content/provide-access-to-the-gui.htm

Are there any startup options? Or configurations for the app8Man.exe.config? Or maybe even a registry key? (I mean when I restart my PC I don't have to re-enter it a second time, so it has to be saved somewhere)

We're about to re-deploy the shortcut to about 50 PCs, so it would be nice if this was a possibility

Thanks in advance

Find more posts tagged with

gui

Accepted answers

All comments

_dp_

Check the C:\Users\USERNAME\AppData\Roaming\SolarWinds_Worldwide,_LLC folder. In there, you will find two subfolders, one for the ARM client and the other for the ARM Configuration client. Inside them, there should be user.config files saved in the folder, which are named as the currently installed ARM version.

I guess you can copy past these config files to the new machines, haven't tested it out.

LLJack

Thanks, for a quick test this seems like it's working.

However this is not a really clean approach, as we would have to redeploy this everytime we update the ARM Server.

.exe Startup options or being able to change this in a central configuration would be a much cleaner approach. But it seems like it isn't really possible at the moment, judging from the lack of answers. I may write a feature request in the future.

But thanks for your Answer, seeing where this file is saved helped me a lot!

_dp_

Yeah, it is not a clean approach, I agree. But right now, I see it as the only workaround.

This could be an interesting feature request. Please write one here if you have time.