Hi Ralph Andreas,
nicht unbedingt in Bezug auf das konkrete Problem, aber "ja" - der PDCe ist auch bei DFSN in einigen Bereichen relevant. Siehe dazu beispielsweise den root scalability mode:
http://www.microsoft.com/windowsserver2003/techinfo/overview/dfsfaq.mspx
Q. How many root servers can host a domain-based DFS namespace?
A. Use 16 or fewer root targets unless you enable root scalability mode by using the /RootScalability parameter in Dfsutil.exe. When root scalability mode is enabled, DFS root servers get updates from the closest domain controller instead of from the server acting as the primary domain controller (PDC) emulator master. As a result, root scalability mode reduces network traffic to the PDC emulator master at the expense of faster updates to all root servers. With this mode enabled, you can have as many root targets as you need, as long as the size of the DFS Active Directory object (for each root) is less than 5 MB.
Note that the PDC emulator master is not removed entirely from DFS operations. The PDC emulator master is still used as follows:
• When you make changes to the namespace, the changes are made on the PDC emulator master also, but the root servers no longer poll the PDC emulator master hourly for those changes. Instead, they poll the closest domain controller. If the root server is a domain controller, the root server uses itself as the source. If the root server is not a domain controller and is in the same site as the PDC emulator master, the root server treats the PDC emulator master as it would any other domain controller.
• When the DFS service starts on a root server, the DFS Active Directory object is accessed on the PDC emulator master. On the next polling interval, DFS accesses the closest domain controller, which might or might not be the PDC emulator master.
Do not use root scalability mode if any of the following conditions exist in your organization:
• Your namespace changes frequently, and users must have a consistent view of the namespace.
• Domain controller replication is slow. Slow replication increases the amount of time it takes for the PDC emulator master to replicate DFS changes to other domain controllers, which in turn replicate changes to the root servers. Until this replication is complete, the namespace remains inconsistent on all root servers.
Note: The number of root targets running Windows 2000 should be limited to 16 for any one namespace. After you enable root scalability mode in a namespace with root servers running Windows 2000 and Windows Server 2003, root servers running Windows 2000 Server still obtain updates from the PDC emulator master.
Daher meine Nachfrage, um das Problem besser zu verstehen.
Meine Vermutung ist noch immer, daß auf dem abgeschalteten Server ein weiterer Namespace existiert (ggf. auch Stand-Alone), der nach der Abschaltung nicht mehr erreicht werden kann. Zwar sagte jenso, daß das bei ihm nicht der Fall ist, aber ich würde es nicht ausschließen wollen.
Schaut doch bitte einmal auf den folgenden Registry Schlüssel auf beiden Systemen:
HKLM\SOFTWARE\Microsoft\Dfs\Roots\Domain --> ist dort wirklich nur der in der GUI angezeigte Namespace sichtbar?
Viele Grüße
Fabian
http://blogs.technet.com/deds
