Deployment of Webex app via SCCM

[EdKeup64769]

Hi there, 

We are deploying the Webex application during SCCM task Sequencing.  The installer leverages the SITEURL command to integrate the default URL for the users.  As we have multiple sites configured globally, we need to populate that URL based on the users configuration.    So, our installer will look something like this: msiexec.msi /q /i webexapp.msi SITEURL="https://sample.webex.com"

When the user logs into Windows 10 and opens Webex for the first time, the URL is not present.  However, if the user quits Webex, and restarts the app, or if they reboot, the URL is present.  Is this expected behavior?  

In older versions of the Webex application (way back in version 30 or something similar), we did not have this issue.  It seems odd that we cannot pre-populate that URL without the user having to restart the app. 

[lior look]

first of all, the behavior is defensively not should be like this, the siteurl have to present for the first time in the second page.
in good scenario, the first page is to insert email address and the second is to insert siteurl (there it should be present already).
now you have this doc to extend your options https://www.cisco.com/c/dam/en/us/td/docs/collaboration/webex_centers/esp/webex_b_it-administrator-guide-mass-deployment-meetings.pdf

if you have SSO enabled in your environment I suggest you to deploy the app by two parameters siteurl=example.webex.com and emailsignin=-1

this will bring u option to hide the regular pages and show only single page with next button, the end user will not need to insert anything except to click on next.

you need to edit the msi by Microsoft orca one time, in registry page go and remove the # from the emailsignin parameter.

than click save.

msiexec /qb /i webexapp.msi siteurl=example.webex.com emailsignin=-1

be aware that the siteurl should be the url without the "https://"
it have to deploy by silent mode by /qb

[EdKeup64769]

A nice idea... but it didn't help.  tried /q /qb /qn. no difference for me.  

[ericsc001]

I was having the same issue, for me using /qb instead of /q populated that correctly the first time