Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Command-line - Enviroment name
#1
Hi,

We are publishing ASG as RemoteApp, for most of our internal users, and have been playing around with the command-line parameter.
The following works perfectly:

asgrd.exe "/dcsBig Grinata Source=sqlserver.domain.local;Initial Catalog=ASG_RD_DB;Integrated Security=True"

When users are opening that RemoteApp, the Envoriment is called "Portable", and i cant seem to find the correct parameter, to change that to our company name.
Is there any solution, to fix the Enviroment name?
Reply
#2
Portable is in this case not really the right name :-)

If you preconfigure your environment in environments.xml (or via UI with Environment Manager) - you can store database profiles in Program Data path (in UI User for all users) so it is available for all users...

Then you can just use the Environment name with the parameter /instance:>your_env_name<
Regards/Gruss
Oliver
Reply
#3
Hi,

Thx for the reply.
We would rather use the command-line parameters, instead of configuring files.
We have several backend servers, that we would need to edit the enviroment files at, when we make a change - when at the RemoteApp frontend, we can just change the paramters for all users
Reply
#4
(02-08-2018, 01:35 PM)DevOma Wrote: Portable is in this case not really the right name :-)

If you preconfigure your environment in environments.xml (or via UI with Environment Manager) - you can store database profiles in Program Data path (in UI User for all users) so it is available for all users...

Then you can just use the Environment name with the parameter /instance:>your_env_name<

Hi,

Any updates on this matter?

Im afraid its not a solution, to have the /profilefile stored locally on each Session host.
We tried storing it at an SMB share, but that dosent seem to work - even with "Everyone" having full control over the share (for testing purposes).

So what paramter should we apply, to the DCS: part, in order to change the Enviroment name?
Reply
#5
Its not the profile.xml - environments are listed in environments.xml - and this file can be stored in Program Data so it is used for all users.

Currently I have no other solution - we can try to change for the next Patch...
Regards/Gruss
Oliver
Reply
#6
(06-08-2018, 02:36 PM)DevOma Wrote: Its not the profile.xml - environments are listed in environments.xml - and this file can be stored in Program Data so it is used for all users.

Currently I have no other solution - we can try to change for the next Patch...

Hi,

Thanks for the update.
We are aware that it can be done, by storing the enviroments.xml in Program Data, but thats not a working solution for us im afraid.
If you could change this in the upcoming patch, that would be much appreciated! Smile
Reply
#7
How do you like a solution - should be the environment name the database name of the Connection String or should we add a new parameter for the command line for the environment name?
Regards/Gruss
Oliver
Reply
#8
(07-08-2018, 07:57 AM)DevOma Wrote: How do you like a solution - should be the environment name the database name of the Connection String or should we add a new parameter for the command line for the environment name?

We would like to use an extra parameter, for the asgrd.exe file - so we specify the /dcs: AND then an /EnviromentName: - or something similar.
As long as we can specify that name in the "string" that is used for the asgrd.exe, that would work.
Reply




Users browsing this thread: 1 Guest(s)