xewill0155
IS-IT--Management
Hi ,
Scenario.
A desktop pc was setup as a w2k3 DC in our exisitng tree to be a tempory spare in case the proper dc server died. We did this as we only had one dc and wanted some redundancy. Eventually we got another server installed with w2k3 and made that a DC as well. so we had dc01 dc02 and dc03.
The desktop pc that was dc02 has been "missing" for some time now ie its not where i left it. Nobody in the dept is sure whether its been formatted or what. Obviously we are now getting some AD replication errors
My question goes like this.
If i delete its account from the directory and some bright spark finds it and plugs it back in to the network what happens to my current AD ?
Am i right in thinking i can prevent replication using AD/Sites and service > NTDS settings and re-jigging the automatically generated config? Is this a safe thing to do?
Thanks nervously
Scenario.
A desktop pc was setup as a w2k3 DC in our exisitng tree to be a tempory spare in case the proper dc server died. We did this as we only had one dc and wanted some redundancy. Eventually we got another server installed with w2k3 and made that a DC as well. so we had dc01 dc02 and dc03.
The desktop pc that was dc02 has been "missing" for some time now ie its not where i left it. Nobody in the dept is sure whether its been formatted or what. Obviously we are now getting some AD replication errors
My question goes like this.
If i delete its account from the directory and some bright spark finds it and plugs it back in to the network what happens to my current AD ?
Am i right in thinking i can prevent replication using AD/Sites and service > NTDS settings and re-jigging the automatically generated config? Is this a safe thing to do?
Thanks nervously