M
Mark Heywood
Scenario:
We have a client with a single domain forest with a remote site which is
connected via VPN.
The DC at the remote site was dying and a new DC was installed. This new DC
only replicated to the other (dying) DC at the remote site, as the VPN link
was not working properly.
The original DC at the remote site has now failed completely.
This means:
We have a DC at the remote site which is completely orphaned from the rest
of AD at head office.
The AD at HO doesn't have a computer account for this DC, so there is no
Kerberos trust relationship.
Is there a way to create the missing entries manually, or shall we attempt
to demote this 'DC' and re-promote it ?
The other thing is they have created some accounts in the remote DC which do
not exist in HO since there has been no AD Replication.
Thanks
Mark.
We have a client with a single domain forest with a remote site which is
connected via VPN.
The DC at the remote site was dying and a new DC was installed. This new DC
only replicated to the other (dying) DC at the remote site, as the VPN link
was not working properly.
The original DC at the remote site has now failed completely.
This means:
We have a DC at the remote site which is completely orphaned from the rest
of AD at head office.
The AD at HO doesn't have a computer account for this DC, so there is no
Kerberos trust relationship.
Is there a way to create the missing entries manually, or shall we attempt
to demote this 'DC' and re-promote it ?
The other thing is they have created some accounts in the remote DC which do
not exist in HO since there has been no AD Replication.
Thanks
Mark.