We have been implementing RTC 5.0.2 on two independent networks (production and integration-for testing) and plan to upgrade these to 6.0.2 in the near future.

We have a small extra network where it seems sensible to use RTC as well rather than have different CLM tools. This small network is entirely isolated with no internet access and no access to our other networks and an uncomfortable working environment in the server room where I would have to work when installing RTC.

Our IT security have said we need to keep entirely separate the RTC instance used by two projects working in this network so plan to install an ESX server with two VM's with RTC 6.0.2 installed on each. We plan a simple all on one server install with SQL backend for each server\project. We expect 10-15 users on each.

We are considering installing RTC 6.0.2 in the VM's while they are being built in one of our larger networks where it will be more comfortable and have easier access to internet resources in case of issues when installing RTC and then taking the VM's via external drive and importing into the ESX server in the small network.

My question is, If I set the URI when installing in the outside network to NOT have it as FQDN just https://servername:9443/jts and not import any data, and can get agreement from IT security to use the destination server name for the build in the source network will it make the rename unnecessary or, if only simpler, what steps would I need to do? Any data migration from the old tool into RTC will only happen after the RTC instance is up and running (probably to include CCM, QM, DM but little or no reporting.