Qlik Sense server host name

[#1]

Hi,

I am installing qlik sense central node on a domain environment. The server I am installing on is srv.company.local

The installation wizard when I come to the Host name section is giving me this:

Enter the address for this machine...

srv.company.local

as suggestion

I read in a Qlik documentation that if you have domain environment we need to use only the server name but not FQDN so do I need to manually change it to srv only without the domain part?

[phaneendra_kunc]

I usually kept the same machine name.

What ever you will find in --> my computer -->properties --> computer name

i kept the same name...

Not sure what u mean by FQDN...

[Gysbert_Wassenaar]

Yes, that's right. Just the server name will do inside the domain.

[#4]

Does it matter if people are accessing it remotely like from the internet?

Will that make a difference.

[#5]

FQDN is computer name + domain like srv.company.local whereas computer name will only be srv

I just confused which one to use as by default Qlik is giving me as a suggestion srv.company.local

[Gysbert_Wassenaar]

Yes, it does. Users outside the domain won't be able to access the machine using only it's name without the domain name added to it.

[#7]

I put the machine name only, and after installation qmc and hub are not starting.

I tried to reboot the services but they are giving me errors. Dont know if its connected.,

I have installed it previously as src.company.local on a different domain and was working fine.

[phaneendra_kunc]

Keep how ever it auto populates. probably it is srv.company.local

[Levi_Turner]

In principle, it doesn't matter what name you use initially. Strictly speaking the documentation says FQDN is best. The server-name and how users access Qlik Sense are two very separate things.

So you can install Sense onto appserver01-g2.domain.local but then setup a cname entry for analytics.domain.local for ease of use by internal users, then long-term, in conjunction with your network admins, expose the site externally as analytics.domain.com. While making sure that you update the virtual proxy whitelist for each of these entry points.

It's best from a troubleshooting perspective to keep the different functions separate.