Hello!
Could you plaease help me with the question? We have Hostmonitor (v.8.82) that we planning to migrate to other server with diferent name (and domain).
Unfortunatly, man who was the best in the software left the company, so may be someone can help me to craete something like plan for such movement...
Of coause, I can create new one instance of HM and relink to in it all my servers (networking), but how in this case save all my tests, statistics, user access rules?
Thank you for support!
Migrate, Move hostmonitor server from one server to other
-
- Posts: 2832
- Joined: Tue May 16, 2006 4:41 am
- Contact:
Please check the following topic:
http://www.ks-soft.net/cgi-bin/phpBB/vi ... php?t=1099
http://www.ks-soft.net/cgi-bin/phpBB/vi ... php?t=1099
Not sure why exactly do you need this...
HostMonitor itself does not care about local server name. Usually when you check remote systems, you provide remote system name or IP; when you check local system you provide "localhost" or "127.0.0.1" as target name
Probably you think about Web Service started on some remote system?
RMA agents? Passive or Active agent?
IP filter enabled for old server IP?
Regards
Alex
HostMonitor itself does not care about local server name. Usually when you check remote systems, you provide remote system name or IP; when you check local system you provide "localhost" or "127.0.0.1" as target name
Probably you think about Web Service started on some remote system?
RMA agents? Passive or Active agent?
IP filter enabled for old server IP?
Regards
Alex
Ok, let me try to explan again (sorry, if I am not so good in English)
We are using active agents.
For example, in Windows systems with kerberos aouthentication, if I will do such (update old server a-dns record that will point to the new server with NEW netbiosname and the same IP), windows clinet will not been granted access to the server with error something like: the name you are trying to connect do not match....
So, just simple question, if all my active agent now connects to
old-server.my.domain
192.168.0.1
Do they will be able to connect by (old) dns name old-server.my.domain, when in @reality@ it will be new-server.mynew.domain
?
We are using active agents.
For example, in Windows systems with kerberos aouthentication, if I will do such (update old server a-dns record that will point to the new server with NEW netbiosname and the same IP), windows clinet will not been granted access to the server with error something like: the name you are trying to connect do not match....
So, just simple question, if all my active agent now connects to
old-server.my.domain
192.168.0.1
Do they will be able to connect by (old) dns name old-server.my.domain, when in @reality@ it will be new-server.mynew.domain
?