Strange issue here today when we decommisioned an old domain controller(successfully dcpromo'd, verified removal in DNS, ADUC, etc. replication ok etc.)
Immediately our metastorm 7.6 install became very slow to click around in the web interface by users and some processes became unusable. Previously we had verified all processes were pointing to new domain controllers etc.
We searched config files, the database, etc. but couldn't find anything pointing to the old DC.
Our last option was to re-image the old DC and rebuild then dcpromo with same computer name and IP address. After restarting Metastorm all is now working great.
Why is Metastorm looking for a specific DC and how can I change/update that setting?
thanks for your help
Immediately our metastorm 7.6 install became very slow to click around in the web interface by users and some processes became unusable. Previously we had verified all processes were pointing to new domain controllers etc.
We searched config files, the database, etc. but couldn't find anything pointing to the old DC.
Our last option was to re-image the old DC and rebuild then dcpromo with same computer name and IP address. After restarting Metastorm all is now working great.
Why is Metastorm looking for a specific DC and how can I change/update that setting?
thanks for your help
Forum: Engine