This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Accept
Reject

The Community is now in read-only mode to prepare for the launch of the new Flexera Community. During this time, you will be unable to register, log in, or access customer resources. Click here for more information.

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Fnms migration in on-premise from OS 2012 to OS 2019, issue with IIS binding

csganesh
By
Level 3
Hi Team,
We are migrating our fnms 2019 R2, on our stage and prod environment from OS 2012 to OS 2019 on app server, beacon and db server. We are retaining the same IP address and hostname for the OS 2019 as of OS 2012. While we did that on stage, we can able successfully migrate to OS 2019 but the site was not resolving to the Alias name which we have on the IIS Bindings. We removed the bindings on old server and configured it on the new one. The site was accessible only through server name and IP address. Can any one suggest on how we can solve the issue.

Also any thing else we need to consider while doing the similar migration in Prod?

‎Nov 07, 2022 05:20 PM

0 Kudos
(1) Reply

durgeshsingh
By
Level 10

Can you please check if alias name has been created in DNS entry. You have to create certificate with alias , server name.

‎Nov 07, 2022 11:41 PM

0 Kudos