Monitor opens up reporter using short name

[davegold]

Hi,

I've noticed that when I click the "Reports" button in VeeamOne Monitor, it opens up the Reporter web page using the short name ("veeam1"), instead of the fully qualified name ("veeam1.sub.domain.com"). I've set the name of the veeamOne monitor server to the fully qualified name in the client settings (in monitor), but don't see a place to force the reporter server name to be fully qualified.

Does anyone know if there is such a setting or other way to force it to use the fqdn?

Thanks,

Dave

[Vitaliy S.]

Hi Dave, there is no such setting, but could you please tell me why would you like to force it to use FQDN and not just a hostname?

[davegold]

We have multiple domains in our site, and my workstation is not in the same domain as the VeeamOne server. So if it tries to connect using the hostname, it fails dns lookups.

I've had enough customers with similar situations that I think it makes sense to log this as an RFE. Perhaps the reporter link should follow the name configured in Options-->Client Settings-->General?

Thanks for the reply,

Dave

[Vitaliy S.]

Yes, thanks for a good suggestion, makes sense.

To resolve your current issue, you may want to edit etc/hosts file to change your DNS settings on the local machine, should help.

[brupnick]

It doesn't look like this has been addressed in 6.5. Is this something that we can look forward to in the not too distant future? I'm in a similar situation where my ONE server and the workstations are in different domains.

[Vitaliy S.]

Let me discuss it with the dev team, I guess it shouldn't be too hard to implement.

[Vitaly.Mzokov]

Brian,

To resolve this particular issue right now, you will have to apply changes against Veeam ONE database.
Here you go the script which updates the hyperlink to Veeam ONE Web UI server:

Code: Select all

UPDATE [XXX].[common].[ServerSettings] SET ReporterUri='http://YYY:1239'

where
XXX - name of your Veeam ONE database
YYY - FQDN of your Veeam ONE Web UI server

Do not forget to make a backup file of your Veeam ONE database before you do any changes against it. Just to be on a safe side.

-VM.

[brupnick]

Looks like that worked. Thanks Vitaliy!!