BUT, and this is a biggie, me and my guys could not get a machine to install over an existing NT install. We would even delete NT programs files all together, leaving just an NTFS disk with some unimportant (= to the install) data, .... still no go.
we did have one or two desktops we got working but there has been mystery problems ever since. But I would never ever try to upgrade a server in any manner. The last thing I need is more problems with IIS than just keeping up with the patches and the ASP cowboy newbies who host with us.
I believe it has something to do with data in the boot sector. Been noticing this type of problem with MS since Win 98.
Clean your disk... not FDISK, but if it is IDE, get a low level formatter (back up your data, of course). Low level formatting is a *must* to clean the boot sector. If SCSI, the built-in SCSI bios should do the trick (usually can be entered right after BIOS on boot. Then let 2000 do the partitioning and formatting (another thing I found out!)... It doesn't seem to like you doing the partitioning yourself beforehand.
I have been running MS servers and workstations since NT 3.51.... since before ASP (I belive it was IIS 2).... And after this last go around with 2000, I swore what I have swore a dozen times before.... slave the data disks, copy the data over, and do a low level and do a clean install.
In fact, in my 6-7 years of running MS OS's in production enviroments.... I have found the easiest way to fix any *system* problem is low level format and re-install.
pathetic in a way, but once you have 2000 operating, you will love it.
Any advice?
Merry Christmas to all!!