Deploy Lumira with Custom settings for WinAD authentication and autoupdate

[Former Member]

Hi all,

We deploy Lumira as an package to our users via SCCM but are facing couple of issues listed below, any help in overcoming those will be appreciated -

1. WinAD authentication settings for connecting to universes -

     In order to get the windows authentication working, we have to modify the .ini for lumira and mention the location of the krb5 and bsclogin files. we are able to do that while deploying the package. the problem arises after the auto-update happens, it wipes the extra lines in the .ini file and windows authentication stops working until the user enters those lines manually again. How can we avoid this?

2. In order for auto update to work properly, users need to modify the Proxy details in the preference section. How can we automate that part while deploying the application as a package? which file (general.persistent ? ) needs to be modified?

3. Most of our users connect to universes for fetching the data-sets, is there a way we can save the system details (CMS cluster or host-name) so that they do just have to type in their username / pwd and hit enter without bothering about the system name to be entered.

[former_member183750 · Accepted solution]

Hi Smruti

Unfortunately, I do not have any good news for you on any of the points you raise.

Future product additions will have a "feature" called Desktop Governance. From what I know of the state of this feature, the points you raise would be great enhancements. But these features may be there already, we'll just have to see.

- Ludek

Senior Support Engineer AGS Product Support, Global Support Center Canada