Failure to boot after W2k to W2k3 upgrade

Failure to boot after W2k to W2k3 upgrade

Post by Antonin Ko » Tue, 21 Sep 2004 15:39:24


I tried to upgrade my development PDC server from 2000 to 2003. When
upgrading
the computer started rebooting in a loop. I had to re-install 2000 and
restore
everything from backup.

However, I need to upgrade it. What can I do to make it successful?

Antonin
 
 
 

Failure to boot after W2k to W2k3 upgrade

Post by v-reb » Tue, 21 Sep 2004 16:52:46

i Antonin,

It is possible that you may encounter some issues when upgrading win2k to
win2k3. I suggest you use the following steps to perform the upgrade
process:

1. The following are some nice documents for upgrading from Windows 2000 to
Windows Server 2003:

325379 How to Upgrade Windows 2000 Domain Controllers to Windows Server 2003
http://support.microsoft.com/?id=325379

Upgrading from Windows 2000 Server to Windows Server 2003
http://www.microsoft.com/windowsserver2003/upgrading/w2k/default.mspx

Upgrading from Windows 2000 Server to Windows Server 2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2kto
ws03-2.mspx

2. Generally speaking, to upgrade Windows 2000 domain controllers to
Windows Server 2003 domain controllers by using Winnt32.exe, we need to use
the ADPREP commands ("ADPREP /FORESTPREP" and "ADPREP /DOMAINPREP") to
upgrade the existing Windows 2000 forest and domain to ensure that they
contain the additional objects, attributes and permissions necessary to
support the Windows Server 2003 Active Directory environment.

"ADPREP /FORESTPREP" is a one-time operation performed on the schema
operation master (FSMO) of the forest. The FORESTPREP operation must have
successfully completed and replicated to the infrastructure master of each
domain before "ADPREP /DOMAINPREP" can be executed in that domain.

To run "ADPREP /FORESTPREP", the user must be a member of the Schema
Admins, Domain Admins, and Enterprise Admins groups.

"ADPREP /DOMAINPREP" is a one-time operation run on the infrastructure
operation master domain controller of each domain in the forest being
upgraded.

To run "ADPREP /DOMAINPREP", the user must be a member of the Domain Admins
group of the domain in which you are running DOMAINPREP.

The following documents contain good information regarding these operations:

278875 Cannot Promote a Windows Server 2003 Domain Controller into a
Windows
http://support.microsoft.com/?id=278875

How to use the adprep command at the command line
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/ents
erver/adprep.asp

255690 HOW TO: View and Transfer FSMO Roles in the Graphical User Interface
http://support.microsoft.com/?id=255690

3. The DHCP, WINS, DNS services will be upgraded smoothly when upgrading
the operating systems.

4. From your post, I understand that you want to remove AD1 and AD2 after
finishing the upgrade project. I would like to suggest that you transfer
the GC and FSMO roles to other DCs first and then demote them by running
DCPROMO.

It is not a good method to take the DC away from the domain directly as it
may cause potential issues such domain replication. The following KB
articles should be helpful

816105 HOW TO: Create or Move a Global Catalog in Windows Server 2003
http://support.microsoft.com/?id=816105

324801 HOW TO: View and Transfer FSMO Roles in Windows Server 2003
http://support.microsoft.com/?id=324801

255504 Using Ntdsutil.exe to Seize or Transfer FSMO Roles to a Domain
Controller
http://support.microsoft.com/?id=255504

As always, it is recommended to perform a full backup before the migration.
If possible, it is a good idea to test the plan in your lab environment.

Further questions, let us get in touch!


Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


Microsoft Online Partner Support
Get Secure! - www.microsoft.com/se
 
 
 

Failure to boot after W2k to W2k3 upgrade

Post by Antonin Ko » Tue, 21 Sep 2004 17:22:21

i Rebecca,

Thanks for your reply.

I have read some articles and cannot see anything wrong with what I am
doing. I ran the ADPREP and successfully install new 2003 server on another
computer and promoted it as a second DC to my development DC.
When I ran the winnt32 I get few warning but nothing what should prevent the
upgrade.
I do not know if I should try it again (and get more practice in restore) or
ask my manager for a new computer and do a clean installation.

Antonin

"Rebecca Chen [MSFT]" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
to
2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2kto
use
Admins
operations:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/ents
Interface
migration.
rights.


 
 
 

Failure to boot after W2k to W2k3 upgrade

Post by Antoni » Wed, 22 Sep 2004 15:00:19

gave it another try. This time it was not rebooting in a loop. It even
looked promising but than it said it could not start Active Directory.

Any suggestion?

Antonin

"Rebecca Chen [MSFT]" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
to
2003
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/win2k/w2kto
use
Admins
operations:
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/ents
Interface
migration.
rights.


 
 
 

Failure to boot after W2k to W2k3 upgrade

Post by v-reb » Wed, 22 Sep 2004 20:00:39

Hi Antonin,

What is the exact error message? Please write down the exact error message
for research.

In addition, this issue seems to related to the
hardware/driver/incompatible software.

Have you checked the HCL with the current machine? Please go to the
following link to make sure the hardware is compatible with Windows 2003:
http://www.yqcomputer.com/


Any update, let us get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


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 your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
 
 

Failure to boot after W2k to W2k3 upgrade

Post by Antoni » Wed, 22 Sep 2004 22:09:38

Hi Rebecca,

Forgive me my ignorance. How do I find on that site if Compaq Evo 300 is
compatible with Windows 2003?

Thanks,
Antonin




rights.
 
 
 

Failure to boot after W2k to W2k3 upgrade

Post by v-bpen » Thu, 23 Sep 2004 15:27:44

Hi Antonin,

This is Bill. I think you can contact HP to confirm it. The HCL lists all
2k3 signed hardware devices. If you don't know the exact hardware model and
type, you need to contact the hardware manufacturer.

Before upgrade any OS or deploy Service Packs, I recommend you to perform
the following steps to reduce the failure rate.

Step 1. SFC.

1. Insert the original Windows installation CD to the CD-Rom.
2. Run the following command and complete the scan.
sfc /scannow

Step 2. Scan Virus and Spyware.

Please make sure that you've entered into Safe Mode and scaned viruses with
the latest signature and scaned spyware with at least 2 spyware removal
tools.

Step 3. Contact the hardware manufacturer.

Please contact the hardware manufacturer to check whether the computer is
compatible with Windows XP SP2. If it is not compatible, please check
whether there is a updated driver.

Step 4. Disable and remove all USB devices.

I hope the above info helps.

Please post back if you have further questions.

Have a great day!

Bill Peng
MCSE 2000, MCDBA
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 your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
 
 
 

Failure to boot after W2k to W2k3 upgrade

Post by Antoni » Thu, 23 Sep 2004 19:16:35

Hi Bill,

Thanks for your reply. Today I tried do a new installation rather than
upgrade. It looked promising. However, after reboot I got this error:

Windows could not start because the following file is missing or corrupt.
<Windows root>\system32\ntoskrnl.exe
Please re-install a copy of the above file.

I could not find my PC, Compaq Evo 300, in the HCL list. It is hardly
surprising as my PC is 5 years old. It is late evening here in Australia. I
try to contact the manufacturer tomorrow.

Antonin






and
with
rights.
 
 
 

Failure to boot after W2k to W2k3 upgrade

Post by v-bpen » Thu, 23 Sep 2004 20:44:44

Hi Antonin,

I recommend you to use Recovery Console with Expand command to expand a
file to %windir%\system32\ to replace the corrupted/lost ntoskrnl.exe.

Please refer to:
How To Use the Recovery Console on a Windows Server 2003-Based Computer
That Does Not Start
http://www.yqcomputer.com/ ;en-us;326215

Let's wait for the computer manufacturer's answer to the hardware
compatiblility.

Have a good night!

Bill Peng
MCSE 2000, MCDBA
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 your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.