If anyone cares, I have a success story to report. The secret to a successful upgrade was to first copy the installation files to a local drive and then run setup. My first attempt that failed was from a CD-ROM.
Sincerely, Andrey Fyodorov Systems Engineer Messaging and Collaboration Spherion -----Original Message----- From: Fyodorov, Andrey Sent: Wednesday, October 15, 2003 11:16 AM To: Exchange Discussions Subject: RE: botched W2KAdvServer -> W2003 Enterprise upgrade I believe my drive is connected to an onboard IDE controller. It is a plain vanilla Dell desktop. But I will double-check. Thanks! -----Original Message----- From: Arlo Clizer [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2003 10:29 AM To: Exchange Discussions Subject: RE: botched W2KAdvServer -> W2003 Enterprise upgrade Do you have your hard drive(s) connected to a pci device? I've seen this problem with Promise RAID controllers. -----Original Message----- From: Fyodorov, Andrey [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 15, 2003 7:03 AM To: Exchange Discussions Subject: OT: botched W2KAdvServer -> W2003 Enterprise upgrade Hi all. I was playing with my home computer last night trying to upgrade it to Windows 2003. My machine is a Dell desktop. One hard drive with two partitions - C: and D:. C: is Windows ME D: was Windows 2000 Advanced Server. The Advanced server had been dcpromo-ed looong time ago. So when I started the upgrade to Windows 2003 Enterprise version, the setup detected the presence of AD and told me that first I should do ADPREP /forestprep and then ADPREP /domainprep. Did that. No problems. Started installing Windows 2003 Enterprise. No problems. It went through the first two stages, copied temporary files to the C: drive and rebooted. After the reboot it went back into the Setup. Everything looked OK, the setup screen showed up. Then it started checking disks and all of a sudden tells me that drives C: and D: are inaccessible (possibly corrupted). Only two choices - Enter to Retry or F3 to restart. After the restart tried to go back to setup - same result. Then I tried to boot into the Windows 2000 Advanced Server (choices were Windows ME, Windows 2000 Advanced Server, and Setup). It looks like Windows 2000 Advanced Server starts OK - it is obviously finding the necessary files to start: first the black screen with white bars across the bottom of the screen. Then the graphical splash screen with blue bars. The blue bars stop half-way and a few seconds later I get a BSOD telling me INACCESSIBLE_BOOT_DEVICE. I am looking for ideas as to what it is that it can't access. I installed another copy of Windows 2000 Adv Server in a separate directory, booted fine, and looked at the old WINNT files - everything looks OK. Does anyone know what Windows 2003 installation modifies to cause an inaccessible boot device? Thanks! _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&; lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED] _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Web Interface: http://intm-dl.sparklist.com/cgi-bin/lyris.pl?enter=exchange&text_mode=&lang=english To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
