Our company has decided to shift from one domain to another one partially. In this case, harvest users on new domain (who has shifted to new domain) cannot login to CA SCM on their client PC. But they can login from any PC which is defined in old domain. Is there any solution for working in two different domains?
I can suggest one thing to do.You can change the broker name to its Fully Qualified Domain Name( FQDN).
Ex: if it is now "broker_name" you can change it to "broker_name.xyz.com" and then ask everyone to connect to broker using FQDN from both workbench and administrator.
How to change broker name to FQDN ,you can refer Page 346 of Implementation Guide of R12.5 Bookshelf.I am mentioning it here anyways but do consult the bookshelf.
In Control Panel, System, Environment Variables, add, as a SYSTEM VARIABLE, the
variable RT_FORCE_NODE_NAME with a value of m1.company.com
Add RT_FORCE_NODE_NAME=m1.company.com; export RT_FORCE_NODE_NAME to
the USER PROFILE for every product user on the computer or the SYSTEM PROFILE.
The above solution will work if network allows the resolution of both domains with respect to each other.
Actualy I'm a little bit late to respond, but I really want to share the solution.
To solve the problem, our system team configured DNS servers to resolve the domain name of requests, as the Harvest Servers real domain names, even if users are on the other domain. So without changing the harvest configuration, users on both domains can use Harvest.