We have migrated our Enterprise platform from Win2k8R2 to Win2k16. We have only one webserver, with MANY links and embedded links directly pointing back to the old IIS7.5 server (don't ask, long story). The links are merely UNC paths and do not include the FQDN. We are quickly approaching the point where the old server needs to be shut down. We cannot just rename the new server to the old, as there is a Enterprise naming convention that must be adhered to.
I'm just wondering if "Re-Write" should work in this scenario. My co-worker has tried on their home set-up, (another story) with no luck.
I would like to test it on the production setup, as everyone knows the situation and would be warned when the old server is off for a short period of testing.
We have already asked our Enterprise DNS staff to look into it with a DNS Alias or Cname, etc , but they indicated that wouldn't work.
Does anyone have experience with Re-write, and should it work with the scenario described? (maybe include some examples?) If so, we'll keep at it. If not, we'll look at other ways, although we're running out of them.
Thanks in Advance.