You need stop all services, expept database service.
1. Delete all certificates. they will be recreated during the next startup services
2. open phadmin c:\Program Files\Qlik\Sense\Repository\PostgreSQL\9.3\bin\pgAdmin3.exe and open Your DB
port localhost:4432 DB user Postgres. Password you specified during installation.
3. open DB QSR
4. in table ServerNodeConfigurations change Hostname and save
5. Try start services.
Take a look at this and see if this is helpful
There is a file named: Host.cfg located in <drive>:\ProgramData\Qlik\Sense
It has a base64 encoded string which when decoded you can see the hostname the product was installed on:
You can use this free online tool to decode and encode the string:
You can edit the Host.cfg and replace the encoded string with another encoded string and restart your services.
so - mynewhostname - will look like this in the Host.cfg file: bXluZXdob3N0bmFtZQ==
Note: When I did this (because my Amazon EC2 instanced had a hostname change) - it worked but - for some reason in the QMC it showed my scheduler and proxies as stopped even though they were running. You may have to restart the individual services (scheduler and proxy) a 2nd time again to get the notifications to clear in the QMC.
Hope this helps
Note: Please mark the appropriate replies as helpful / correct so our team and other members know that your question(s) has been answered to your satisfaction.
Since this is very useful to know is there a reason this method isn't (I believe) in the official documentation (or ideally, the interface itself)? Is it because it's a rather drastic change with many consequences (since it affects certificates, whitelists, proxy redirection paths etc)? I also believe some form of automatic hostname validation is needed since a misconfigured server name can have detrimental consequences with no obvious clues (e.g. the engine, proxy and printing services may appear to start normally but fail to resolve the provided hostname).
I was ready to take some of the steps above, which can be quite involved, later I realized that in my case, I only needed to add an extra host name in the "Host white list" for the default Virtual Proxy. I'm sure the people above had good reasons to change the original host name but if you just want to make the Qlik Sense hub available under an extra host name then adding it to the Host white list might be enough.