RE: Restoration of Domain Controller on Different Hardware System
- From: v-xuwen@xxxxxxxxxxxxxxxxxxxx (Vincent Xu [MSFT])
- Date: Tue, 19 Dec 2006 02:00:06 GMT
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.
======================================================
--------------------
SystemThread-Topic: Restoration of Domain Controller on Different Hardware
Ithread-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
setwork for in order to test a variety of things. We have a Windows domain
Controllersup in our regular network environment with two Windows 2000 Domain
Controllers (at our primary location) and two Windows 2003 Domain
need(at our other location). I have set up 6 computers off our network, and
ofto make one of them a domain controller.
So far, I have managed to restore the system state and system disk of one
tothe Windows 2000 domain controllers via Directory Services Restore Mode
andthis designated machine (HP Compaq dx2000 MT) in the test environment,
realcan 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
install,network environment) is an HP ProLiant DL380 G3 Server.
I know that documentation suggests at this juncture to do a repair
regularbut I've tried that and it just makes things worse - I can get into
Pack,Windows 2000 server at that point, but I've gone from SP4 to no Service
Activeand everything seems screwed up after the repair install, including
machineDirectory itself. I think it would be easier to figure out why the
thencan't boot into regular mode and fix it than to do a repair install and
appreciated.go through fixing everything that gets screwed up by the repair install.
Any help regarding this issue, or any suggestions are greatly
Thanks!
Marc
.
- Follow-Ups:
- Prev by Date: RE: ADMT v3 not updating attributes
- Next by Date: Re: Orphaned Child Domains into new forest
- Previous by thread: RE: Fatal Error When Using File Server Migration Toolkit
- Next by thread: RE: Restoration of Domain Controller on Different Hardware System
- Index(es):
Relevant Pages
|