RE: Help with replacing DC while keeping same DC name.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hi,

I am just writing to see how everything is going. If you have any updates
or need any further assistance on this issue, please feel free to let me
know.

Thanks & Regards,

Ken Zhao

Microsoft Online Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security <http://www.microsoft.com/security>
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.




--------------------
| X-Tomcat-ID: 59644098
| References: <B0B579A9-C9AB-486C-8B09-408E3BF8CEF1@xxxxxxxxxxxxx>
| MIME-Version: 1.0
| Content-Type: text/plain
| Content-Transfer-Encoding: 7bit
| From: v-kzhao@xxxxxxxxxxxxxxxxxxxx ("Ken Zhao [MSFT]")
| Organization: Microsoft
| Date: Thu, 10 May 2007 03:43:37 GMT
| Subject: RE: Help with replacing DC while keeping same DC name.
| X-Tomcat-NG: microsoft.public.windows.server.general
| Message-ID: <KDakwVrkHHA.5432@xxxxxxxxxxxxxxxxxxxxxx>
| Newsgroups: microsoft.public.windows.server.general
| Lines: 110
| Path: TK2MSFTNGHUB02.phx.gbl
| Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.general:12599
| NNTP-Posting-Host: TOMCATIMPORT1 10.201.218.122
|
| Hello,
|
| Thank you for using newsgroup!
|
| From your post, based on my knowledge, there is no recommended procedure
| for replacing DC will keeping the same DC name from Microsoft.
|
| The official method is:
| Demote old DC
| Promote new DC with a different DC name
| Remove the old DC and change the new DC name to be the same as old one
| (this is a complex step and more information will be changed).
|
| This is a quick way but this is not an official way:
| You can use ghost to clone the old DC to a new one and then remove the
old
| DC. The two machines must have the same hardware device environment.
|
| Thanks & Regards,
|
| Ken Zhao
|
| Microsoft Online Support
| Microsoft Global Technical Support Center
|
| Get Secure! - www.microsoft.com/security
<http://www.microsoft.com/security>
| ====================================================
| When responding to posts, please "Reply to Group" via your newsreader so
| that others may learn and benefit from your issue.
| ====================================================
| This posting is provided "AS IS" with no warranties, and confers no
rights.
|
|
|
|
|
| --------------------
| | Thread-Topic: Help with replacing DC while keeping same DC name.
| | thread-index: AceSZNgWvJCvBbk/SNiO/wporrdRjg==
| | X-WBNR-Posting-Host: 207.46.19.197
| | From: =?Utf-8?B?QmlnTW8=?= <BigMo@xxxxxxxxxxxxxxxx>
| | Subject: Help with replacing DC while keeping same DC name.
| | Date: Wed, 9 May 2007 11:07:02 -0700
| | Lines: 52
| | Message-ID: <B0B579A9-C9AB-486C-8B09-408E3BF8CEF1@xxxxxxxxxxxxx>
| | MIME-Version: 1.0
| | Content-Type: text/plain;
| | charset="Utf-8"
| | Content-Transfer-Encoding: 8bit
| | X-Newsreader: Microsoft CDO for Windows 2000
| | Content-Class: urn:content-classes:message
| | Importance: normal
| | Priority: normal
| | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.2826
| | Newsgroups: microsoft.public.windows.server.general
| | Path: TK2MSFTNGHUB02.phx.gbl
| | Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.general:12573
| | NNTP-Posting-Host: tk2msftibfm01.phx.gbl 10.40.244.149
| | X-Tomcat-NG: microsoft.public.windows.server.general
| |
| | I have 3 DC's coming off of lease and need to remove one and replace
two
| of
| | them using the same DC name.
| |
| | Does my plan, listed below, make sense or can someone direct me to
| | Microsoft's recommended procedure for replacing DC will keeping the
same
| DC
| | name.
| | I have a single domain, no outside trusts, no dhcp or exchange.
| |
| | 1. Permently remove DC3. Point DC3 to DC1 for DNS. This will ensure
that
|
| | DCPROMO successfully unregister's all the SRV records for the old DC.
| | 2. Remove Global Catalog.
| | 3. Be patient, let domain run for a few days to make sure users can
still
| | login.
| | 4. Run dcpromo to remove Active Directory.
| | 5. Remove DNS Role. Probably not necessary, but what the heck.
| | 6. Join the now Member server to a workgroup called FRED.
| | 7. Once I've demoted, and disjoined, check AD for errors
| | 8. Check DNS and remove any records that belong to DC3.
| | 9. Replace DC2:
| | a. Point to DC1 for DNS
| | b. Remove Global Catalog.
| | c. Dcpromo to remove AD
| | d. Remove DNS role.
| | e. Disconnect from network, but donâ??t turn off. Check for AD
errors.
| | f. If I have no life threatening errors, reconnect to network and
| join
| | Workgroup FRED.
| | g. Power down the system.
| | h. Remove any DC2 records from DC1 DNS.
| | i. Bring up new server and Dcpromo.
| | j. Add DNS role and point it to itself for primary DNS.
| | k. Make it a Global Catalog.
| | l. Wait for replication to take place across the domain.
| | m. Check for errors.
| | 10. Replace DC1:
| | a. Transfer all FSMO roles to the new DC2.
| | b. Point to DC2 for DNS.
| | c. Remove Global Catalog.
| | d. Dcpromo server to remove AD.
| | e. Remove DNS role.
| | f. Disconnect from network, but donâ??t turn off. Check for AD
errors.
| | g. If you have no life threatening errors, reconnect to network and
| join
| | Workgroup FRED.
| | h. Power down the system.
| | i. Remove any DC1 records from DC2 DNS.
| | j. Bring up new server as DC1 and Dcpromo.
| | k. Add DNS role and point it to itself for primary DNS.
| | l. Make it a Global Catalog.
| | m. Wait for replication to take place across the domain.
| | n. Check for errors.
| |
| | Thanks.. BigMo
| |
| |
|
|

.