09-22-2016 11:32 AM
I am preparing Unity client for OnBase 16 to push out to users via SCCM. We are going to be using ADFS for authentication. How can I package the installer with a configuration file that contains the ADFS settings we need? Page 363 of "UnityClient1600.pdf" explains how to make these settings manually, but no mention of how to push them out to a large group of users.
I don't see anything in the ADDLOCAL properties in the command line installation section.
Here is my installation command thus far:
msiexec /i "Hyland Unity Client.msi" ADDLOCAL=Unity_Client
CREATE_DESKTOP_SHORTCUTS="1"
SERVICE_LOCATION_NT_AUTH="true"
SERVICE_LOCATION_SERVICE_PATH="onbase.mydomain.com/.../Service.asmx"
09-23-2016 06:55 AM
Hi Tia,
Thank you for posting your question on Community.
To answer your question, we do not currently support configuring the AD FS sections via the Unity Client installer UI or command line interface at this time. If this is something you would like to see, you can submit an SCR for Development to review.
In this case you have a few options to mass-deploy an AD FS configured Unity config file.
The first being to utilize the Unity ClickOnce installer. Which will allow you to modify the config file and then provide a URL to your users so they can install Unity with the changes. More information can be found in the Unity v16 MRG starting on page 392.
You can also push out the modified config file via GPO, or PowerShell. There are also programs available to automate pushing software/files domain wide which you may already be using in-house.
Please let me know if you have any questions.
09-23-2016 06:55 AM
Hi Tia,
Thank you for posting your question on Community.
To answer your question, we do not currently support configuring the AD FS sections via the Unity Client installer UI or command line interface at this time. If this is something you would like to see, you can submit an SCR for Development to review.
In this case you have a few options to mass-deploy an AD FS configured Unity config file.
The first being to utilize the Unity ClickOnce installer. Which will allow you to modify the config file and then provide a URL to your users so they can install Unity with the changes. More information can be found in the Unity v16 MRG starting on page 392.
You can also push out the modified config file via GPO, or PowerShell. There are also programs available to automate pushing software/files domain wide which you may already be using in-house.
Please let me know if you have any questions.
09-27-2016 07:20 AM
10-06-2016 07:30 AM
10-06-2016 07:44 AM
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.