Skip to main content

Hi Guys, 

I have a question with EdgeDrive i Webconsole. 

We implement the Edge Drive functionality.

The DMZ hosts the "files.kowr.gov.pl" host and is connected to it by external users via Webconsole. When generating a public link through the browser, everything is OK, the link is correct, that is. https://files.kowr.gov.pl/webconsole/gtl.do?gid=w8EcrEkbS

I specify the e-mail addresses to which the public link is to be sent:

And in the received e-mail, the link changes, i.e. the host name in the link changes from files.kowr.gov.pl "to" cv-commserve.ap.arr.gov.pl 

Please help where you can change any parameter to make the link correct, i.e. with the correct host.

In addition, please let me know how the template of the sent e-mail can be changed so that I can make changes in accordance.

 

Hi @kszaf , I just spoke to the manager of that team who suggested you open a case so we can get this to dev.

Can you share the case once you do?

@Mike Struening thanks here case > https://ma.commvault.com/Case/Details/211028-435

Perfect, thanks!  I’ll follow this as well.

Sharing the resolution as I see your case is closed:

Below registry keys with the value of the URL https:// url> Resolved the issue
https://documentation.commvault.com/11.24/expert/4344_changing_web_console_url_for_commserve.html


https://documentation.commvault.com/additionalsetting/details?name=%22sWebConsoleURLForEmail%22&id=6968


https://documentation.commvault.com/additionalsetting/details?name=%22UseCompanyUrlInReportMails%22&id=9962

 

@Mike Struening I'm encountering a similar issue but in my case it's related to e-mail alerts. The links in the HTML-based e-mail alerts are based on the (internal) hostname of the server running the Command Center role and I would like to make sure it is replaced with the public facing FQDN.

I tried the settings as suggested here:
sWebConsoleURLForEmail = https://fqdn
UseCompanyUrlInReportMails = false

Example




 

@Onno van den Berg , I’d create a case as well for this one.  The prior incident earlier in the thread went up to development to address.  I’d bet they will need to address your function/use case as well.

Let me know once you have a case number.

We fixed it. After some additional testing we also noticed it was working fine in our production environment but we couldn't find the mismatch. Following some advice from @MFasulo we added 
https://documentation.commvault.com/11.24/essential/112096_updating_web_console_url_for_commserve_computer_using_command_line_interface.html


Now the funny thing is, is that this setting is exactly the same as the one you also posted which I thought was already in place. https://documentation.commvault.com/11.24/expert/4344_changing_web_console_url_for_commserve.html 


Can you please make sure all references to the "qoperation.exe execscript" command who insert values in the DB are replaced by documentation telling the customer to insert an additional setting. The issue with the qoperation method is that it is untraceable.

Sure thing @Onno van den Berg , I’ll message the docs team now.

Thanks!

Reply


Terms & ConditionsCookie settings