7.000sp2.246 minor annoyance
Today I decided to add an extra IP so my users laptops can connect to a public IP when out of the office. I thought it moist logical to do this in the DC server migration settings and simply put the original name and IP in the Server IP box and my public (firewall mapped) IP in the secondary IP box and push it out to all clients. Effectively migrating to and from the same server but advising clients that a second IP is available for when they cannot see the primary IP.
It will not let me do this, the new primary IP cannot be the same as the old one. I accept that in most cases that may be an error but not always. You are trapping an potential error that may not actually be an error. It also now pops up messages saying the configurations will not longer be valid as the server has been migrated. Simple to fix I think?
Jon Sanderson
It will not let me do this, the new primary IP cannot be the same as the old one. I accept that in most cases that may be an error but not always. You are trapping an potential error that may not actually be an error. It also now pops up messages saying the configurations will not longer be valid as the server has been migrated. Simple to fix I think?
Jon Sanderson