The event log entries that keep coming up every 30 minutes are:
The local domain controller has been selected to be a global catalog.
However, the domain controller does not host a read-only replica of the
following directory partition.
Directory partition:
DC=pha,DC=xports,DC=nhs,DC=uk
A precondition to becoming a global catalog is that a domain controller must
host a read-only replica of all directory partitions in the forest. This
event might have occurred because a Knowledge Consistency Checker (KCC) task
has not completed or because the domain controller is unable to add a replica
of the directory partition due to unavailable source domain controllers.
An attempt to add the replica will be tried again at the next KCC interval.
The local domain controller has been selected to be a global catalog.
However, the domain controller does not host a read-only replica of the
following directory partition.
Directory partition:
DC=phcnt,DC=xports,DC=nhs,DC=uk
A precondition to becoming a global catalog is that a domain controller must
host a read-only replica of all directory partitions in the forest. This
event might have occurred because a Knowledge Consistency Checker (KCC) task
has not completed or because the domain controller is unable to add a replica
of the directory partition due to unavailable source domain controllers.
An attempt to add the replica will be tried again at the next KCC interval.
Promotion of the local domain controller to a global catalog has been
delayed because the directory partition occupancy requirements have not been
met. The occupancy requirement level and current domain controller level are
as follows.
Occupancy requirement level:
6
Domain controller level:
4
The following registry key value defines the directory partition occupancy
requirement level.
Registry key value:
HKeyLocalMachine\System\ CurrentControlSet\Services\NTDS\Parameters\Global
Catalog Partition Occupancy
Higher occupancy requirement levels include the lower levels. The levels are
defined as follows:
(0) Indicates no occupancy requirement.
(1) Indicates at least one read-only directory partition in the site has
been added by the Knowledge Consistency Checker (KCC).
(2) Indicates at least one directory partition in the site has been fully
synchronized.
(3) Indicates all read-only directory partitions in the site have been added
by the KCC (at least one has been synchronized).
(4) Indicates all directory partitions in the site have been fully
synchronized.
(5) Indicates all read-only directory partitions in the forest have been
added by the KCC (at least one has been synchronized).
(6) Indicates all directory partitions in the forest have been fully
synchronized.
The Global Catalog has no intra-site sources for at least one partition.
Replication to the Global Catalog is limited to scheduled replication from
inter-site sources.
Promotion of this domain controller to a global catalog will be delayed for
the following interval.
Interval (minutes):
30
This delay is necessary so that the required directory partitions can be
prepared before the global catalog is advertised. In the registry, you can
specify the number of seconds that the directory system agent will wait
before promoting the local domain controller to a global catalog. For more
information about the Global Catalog Delay Advertisement registry value, see
the Resource Kit Distributed Systems Guide.
Post by Jorge de Almeida Pinto [MVP]to be able to replicate that partition in a direct replication partner must
host that partition.
A host that can be used is another GC hosting a read only version of that
partition or a DC hosting a writable version of that partition
any other event IDs with errors/warnings?
--
Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto # MVP Windows Server - Directory Services
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
Post by Mr Major ThorburnIn our test tree I tried promoting a DC in the root domain to a Global Catalog.
The event log entries below indicate a sub-domain problem.
When I check on the live tree and look at the sites and servers replication
links I can see all the servers in the sub-domains.
In our test tree some of the sub-domain DCs are not visible.
Any ideas on how I can fix this?
Regards Major (thats is my Christain anme ;-) )
The local domain controller has been selected to be a global catalog.
However, the domain controller does not host a read-only replica of the
following directory partition.
DC=phcnt,DC=xports,DC=nhs,DC=uk
A precondition to becoming a global catalog is that a domain controller must
host a read-only replica of all directory partitions in the forest. This
event might have occurred because a Knowledge Consistency Checker (KCC) task
has not completed or because the domain controller is unable to add a replica
of the directory partition due to unavailable source domain controllers.
An attempt to add the replica will be tried again at the next KCC interval.