RE: Restoration of Domain Controller on Different Hardware System

Hi,

I've been trying to restore a domain controller backup (system state and
system disk) to a different machine with a different hardware make-up for use
on a test network environment (it will be the only domain controller on the
test network and it will not have access to any of the real domain
controllers). So far, I've followed the instructions in the following
documents:

- http://support.microsoft.com/?id=263532 : How to perform a disaster
recovery restoration of Active Directory on a computer with a different
hardware configuration
(I used a slipstreamed SP4 CD)

- http://support.microsoft.com/kb/265706 : DCDiag and NetDiag in Windows
2000 Facilitate Domain Join and DC Creation
(I Just used DCDiag.exe for testing to see what else needed to be fixed)

- http://support.microsoft.com/kb/255504 : Using Ntdsutil.exe to transfer or
seize FSMO roles to domain controller
(I seized all the roles)

- http://support.microsoft.com/kb/216498 : How to remove data in Active
Directory after an unsuccessful domain controller demotion
(I cleaned up all the other domain controllers off this one)


Additionally, this domain controller that I'm trying to restore was not a
global catalog server, so after removing all the other domain controllers
from this one (via http://support.microsoft.com/kb/216498), I made this one a
global catalog server via Active Directory Sites and Services.

At this point, things look pretty good, and I think most things are working
now, but the problem is that client machines on the test network (which are
ghost image replicas of existing machines in our real network) still don't
seem to be able to communicate with the domain controller (i.e. I can't log
in to them with different domain accounts, etc.). Also, the netlogon folder
doesn't seem to be shared out, and the C:\winnt\sysvol directory and
sub-directories on the test domain controller don't contain nearly as many
items as the C:\winnt\sysvol directory and sub-directories on the real domain
controller.

I tried to follow the directions here:

- http://support.microsoft.com/?id=296882 - How to promote a domain
controller to a global catalog server

- http://support.microsoft.com/default.aspx?scid=kb;en-us;295419 - XADM: How
to move the global catalog role to another domain controller

- http://support.microsoft.com/?id=316790 - The Sysvol and Netlogon shares
are missing after you restore a domain controller from backup

- http://support.microsoft.com/?id=315457 - How to rebuild the SYSVOL tree
and its content in a domain


But so far nothing seems to be working (probably because some of these
require at least one other domain controller to be active). Does anyone have
any advice on how I can fix the problems I'm experiencing and finally get
this domain controller up and running on my test network?

Any help is GREATLY appreciated! Thanks.

Marc

P.S. at this point, this machine now passes all dcdiag.exe tests.

"Vincent Xu [MSFT]" wrote:

Hi,

I do understand your concerns and I'm sorry for misunderstand your
situation.

However,please understand Microsoft does not support restoring a system
state backup from one computer to a second computer of a different make,
model, or hardware configuration. Microsoft will only provide commercially
reasonable efforts to support this process. Even if the source and
destination computers appear to be identical makes and models, there may be
driver, hardware, or firmware differences between the source and
destination computers.

I know it is a public forum and I hope others can provide their experience
on this specific issue.

I'll appreciate your understanding.


Best regards,

Vincent Xu
Microsoft Online Partner Support

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



--------------------
Thread-Topic: Restoration of Domain Controller on Different Hardware
System
thread-index: AccjcaUya5K6xU3DQaKsoxG+NxuY+Q==
X-WBNR-Posting-Host: 12.109.191.2
From: =?Utf-8?B?TWFyYw==?= <Marc@xxxxxxxxxxxxxxxxxxxxxxxxx>
References: <5E8C44A1-E76E-4FEE-8116-CA5AAD4E2D5E@xxxxxxxxxxxxx>
<WK4IrFxIHHA.516@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Restoration of Domain Controller on Different Hardware System
Date: Tue, 19 Dec 2006 05:29:01 -0800
Lines: 136
Message-ID: <37375F61-152C-42DD-A03F-2C6689494F3D@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
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.2757
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl microsoft.public.windows.server.migration:150
NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
X-Tomcat-NG: microsoft.public.windows.server.migration

Hi Vincent,

I'm confused about your reply since I'm not experiencing a blue screen
error
any longer (not since I did a system restore using both the system state
and
system disk), but rather just a freeze at the Windows 2000 splash screen.

Any help regarding this is greatly appreciated. Thanks.

Marc

"Vincent Xu [MSFT]" wrote:

Hi Marc,

Following is my opinions:

1. We don't recommend restore Domain Controller on Different Hardware
System

2. To locate the exact problem of the stop error, we need to analyze
the
crash dump file. Unfortunately, we cannot help you analyze the dump
file in
newsgroup. To trouble shoot this problem efficiently, I suggest that
you
speak directly with a Microsoft Support Professional so that the crash
dump
can be analyzed. Here are some articles that will help prepare you for
this
call:

Blue Screen Preparation Before Contacting Microsoft
ID: 129845.KB.EN-US
http://support.microsoft.com/?id=129845

Gathering Blue Screen Information After Memory Dump in Windows 2000 or
Windows NT
ID: 192463.KB.EN-US
http://support.microsoft.com/?id=192463

For a complete list of Microsoft Customer Service and Support (CSS)
phone
numbers and information about support costs, please go to the following
address on the World Wide Web:
<http://support.microsoft.com/directory/overview.asp>

3. Following newsgroup appears to be more appropriate because migration
newsgroup mainly focus on the process of migration between domain.

microsoft.public.windows.server.active_directory

Thanks for your understanding.



Best regards,

Vincent Xu
Microsoft Online Partner Support

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



--------------------
Thread-Topic: Restoration of Domain Controller on Different Hardware
System
thread-index: Acci3AapYrakln+DQ8qpfyIlch0kIw==
X-WBNR-Posting-Host: 12.109.191.2
From: =?Utf-8?B?TWFyYw==?= <Marc@xxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Restoration of Domain Controller on Different Hardware System
Date: Mon, 18 Dec 2006 11:38:00 -0800
Lines: 29
Message-ID: <5E8C44A1-E76E-4FEE-8116-CA5AAD4E2D5E@xxxxxxxxxxxxx>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
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.2757
Newsgroups: microsoft.public.windows.server.migration
Path: TK2MSFTNGHUB02.phx.gbl
Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.migration:141
NNTP-Posting-Host: tk2msftsbfm01.phx.gbl 10.40.244.148
X-Tomcat-NG: microsoft.public.windows.server.migration

Hi,

I am currently trying to set up a test network environment at the
company
I
work for in order to test a variety of things. We have a Windows
domain
set
up in our regular network environment with two Windows 2000 Domain
Controllers (at our primary location) and two Windows 2003 Domain
Controllers
(at our other location). I have set up 6 computers off our network,
and
need
to make one of them a domain controller.

So far, I have managed to restore the system state and system disk of
one
of
the Windows 2000 domain controllers via Directory Services Restore
Mode
to
this designated machine (HP Compaq dx2000 MT) in the test
environment,
and
can boot it up in safe mode. However, try as I might, I cannot get
the
machine to boot into regular mode - it constantly freezes at the
splash
screen. The source machine (i.e. the current domain controller in
our
real
network environment) is an HP ProLiant DL380 G3 Server.

I know that documentation suggests at this juncture to do a repair
install,
but I've tried that and it just makes things worse - I can get into
regular
Windows 2000 server at that point, but I've gone from SP4 to no
Service
Pack,
and everything seems screwed up after the repair install, including
Active
Directory itself. I think it would be easier to figure out why the
machine
can't boot into regular mode and fix it than to do a repair install
and
then
go through fixing everything that gets screwed up by the repair
install.

Any help regarding this issue, or any suggestions are greatly
appreciated.
Thanks!

Marc






.

Relevant Pages

  • Re: DC promo wnoT happen
    ... RESTORE FROM BACKUP ... If you cannot restart a domain controller in Directory Services Restore ... Verify Active Directory restore. ...
    (microsoft.public.win2000.active_directory)
  • Re: Disaster Recovery - Virtualized environment
    ... Starting an Active Directory domain controller whose operating system resides in a virtualized hosting environment such as Microsoft Virtual PC, ... Starting an Active Directory domain controller that is located on a volume where the disk subsystem loads using previously saved images of the operating system without requiring a system state restoration of Active Directory. ... The only supported way to roll back the contents of Active Directory or the local state of an Active Directory domain controller is to use an Active Directory-aware backup and restoration utility to restore a system state backup that originated from the same operating system installation and the same physical or virtual computer that is being restored. ...
    (microsoft.public.windows.server.active_directory)
  • Re: AD Disaster recovery setup
    ... The scenario of running on a single domain controller for some ... Restore 1 domain controller, seize all the roles, clean up all of the ... When new hardware is available install new domain controller, promote it, ... later time you must delete the replication links via the Repadmin /delete ...
    (microsoft.public.windows.server.active_directory)
  • Re: Ziel-principal name ist falsch
    ... > Damit war übrigens nicht VMWare, ... > the virtual machine to an earlier state. ... > Backup and Restore Considerations ... > The supported method of restoring a domain controller to a healthy state is ...
    (microsoft.public.de.german.windows.server.active_directory)
  • RE: Restoration of Domain Controller on Different Hardware System
    ... We don't recommend restore Domain Controller on Different Hardware System ... Blue Screen Preparation Before Contacting Microsoft ... For a complete list of Microsoft Customer Service and Support phone ...
    (microsoft.public.windows.server.migration)