Config Groups - Deploy to users

We use the smart client. We have created new Config Groups in Configuration Manager so that users won't have to see all configurations and only see the Prod Configs or TEST Configs. How do we deploy these config groups or update the users current installations to use these new config groups?

0911060553270289.pdf

Find more posts tagged with

General Discussions

Accepted answers

All comments

Rees Howel

In the Cloud the distinction is made in the URL. Before the Smart Client was taken away, the download URL used to be something like:

https://csi10a.erpsl.eu1.inforcloudsuite.com/clientdeploy/mongoose.application?ConfigGroup=COMPANYNAME

and the Webclient URL would be:

https://csi10a.erpsl.eu1.inforcloudsuite.com/WSWebClientM/Default.aspx?ConfigGroup=COMPANYNAME

In the webclient, limiting the logon scope to the Test environment is achieved by:

https://csi10a.erpsl.eu1.inforcloudsuite.com/WSWebClientM/Default.aspx?ConfigGroup=COMPANYNAME_TRN

If Config Groups COMPANYNAME_PROD and COMPANYNAME_TEST exist in your system, appending the ?ConfigGroup switch to the download URL as above ought to work with the Smart Client too.

You'll probably need to get the users to uninstall and then re-install using the new link.

mtolliver

I was able to get this to work with the web client, however with the smart client it is not working to filter the configs. We are on prem and I have added ?ConfigGroup=TRN to the end of our clientdeploy link and it runs the install and then opens with all configs listed.

Rees Howel

Don't know which build you're on but have a look at KB 2289713. That gives a 'resolution' to what sounds like your problem.

As a matter of interest, which browser are you launching the install URL from? Edge should be Ok but Chrome and Firefox generally do odd things to the configuration list.

mtolliver

We use chrome. I will check out the KB - thanks!

Copyright © 2025 Infor. All rights reserved.