Unsolved
6 Posts
0
197
November 11th, 2022 00:00
Migrate NW server 19.6.0.3 from windows2012 to windows2019
Hi,
I've a server NW v19.6.0.3 and I have to migrate it from windows2012 to windows2019. I have to create a brand new windows machine and apply a procedure to move the old networker configuration to the new system. The new system can have different name or the same name.
Which is the correct and supported procedure to do it?
Are there implications with windows domain ??
Any suggestion is wel. accepted
Pierpa
No Events found!
bingo.1
2.4K Posts
0
November 11th, 2022 04:00
In general I recommend that you use the same hostname as the obstacles will be minimal. In general this is a host transfer using the same OS family.
The main issues I see will be
- a licensing problem as you now use a new host id. The exact solution depends on you licensing method.
- problems with the SSL information which need to be updated among the computers.
There are general migration procedures available (https://solve.dell.com/solve/home) but in any case you should handle them with care.
My personal suggestion is that you rebuild the scenario in a virtual environment and that you test the migration here before you touch the productive environment. Everything will be possible except for the licensing issue. But this is a minor issue.
barry_beckers
393 Posts
0
November 14th, 2022 02:00
officially NW from NW9 onwards does not support any renaming of the NW server (if you do, then you are own your own), so the best approach is always to use the exact same name, that you can have full control over by setting the hosts file in the required manner. I have posted about the approach for this in a few earlier posts, showing host file examples and the behavior of NW, where it looks for the NW server short name and then if there is another name mentioned that is stated before the short name in the same host file line, then it will use that name as NW server name.
I think that migrating to another nw server name is no longer supported, due to the introduction of the authc service in nw9 and tight integration of the name into configuration, besides settings underneath the nsr install directory.
The migration option on the solve website asks you the question "Does the target server use the same name as the source server?" and gives only one option to choose from: "yes". Also it assumes the same OS "Select the operating system that applies to both the source and target server", either Windows or Linux as source and target server.
So use the nsrdr procedure to recover unto a new server with the exact same name. You can use a temporary ip address to be able to setup the new NW server, before shutting down the old one and giving the new one the same ip as the old nw server and then perform nsrdr.