When we first rolled out Windchill late last year we connected it to our MS Active Directory system for authentication. Worked great. At the time the AD system was two servers, call them AD1 and AD2, acting in failover mode. Windchill talked to AD1. At one point AD1 failed, so AD2 took over and I had to repoint Windchill to AD2- still fine. Now they AD system has been reconfigured to be load balanced and failover. So AD1 and AD2 are constantly sharing the load and if one dies, the other takes on 100% of the work. Since that change, and it's purely correlation in timing that has me speculating there may be a cause - effect relationship, the time it takes for Windchill to present a login when starting Pro/E has gotten much longer. It was nearly instant, now it takes 20-30 seconds for some users and I'm getting complaints. Has anyone else seen anything like this? And, is there any way to designate Windchill so it knows there are two AD servers working in parallel AND that if one doesn't respond to look for the other one? PTC's page only indicates "contact PTC Global Services" for that kind of configuration.
Thanks
Erik
Windchill 10 M030
Pro/E Wildfire 4 M220
Clients - Windows 7 64 bit, IE9