If you were upgrading a large number of desktops in a managed corporate
environment, you would probably automate this, setting it up to create a strong
password and adding the Domain Administrators group to the local Administrators group.
This last step lets administrators control the machine without having to know the
Administrator password. If the desktops in a managed environment have all the user
accounts stored on a domain controller, the issue of passwords can be ignored.
After I set the passwords, the installation routine started Windows 2000 and I
saw a desktop that almost mirrored my previous Windows 95 desktop. I was amazed -- it
actually worked. I would not have thought you could upgrade a personal operating system
such as Windows 95 to a professional business operating system such as Windows 2000 so
easily and with so few problems.
It's possible that I just got lucky, of course. For one guy I talked to, the
system hung in the middle of the upgrade when the program was detecting hardware. He
had to restart the system, which left the system in an inconsistent state and unable to
be successfully booted. He thinks the problem was due to a graphics card, but -- the
question of blame aside -- nothing was logged and he wasn't given any warning. Luckily,
he was experienced enough just to format and do a fresh install. More importantly, he
had a backup of his data.
I would recommend that Microsoft include better logging during the upgrade
process, as well as a rollback feature that would allow a failed upgrade to revert back
to the previous OS. Until then, users and administrators should have a complete and
tested backup of their system data. They should also verify their hardware against
Microsoft's hardware compatibility list.
A final potential problem, for some sites at least, is that Windows 2000 is
installed into the
C:\Windows directory, which is
the default for Windows 95. Although this might not seem like that big of a deal, new
machines will probably use the
which could cause problems for large installations, where corporate standards are
important to maintaining help-desk sanity.
In my opinion, the installation should change all references from
rename the directory during the upgrade. While it is possible to manually specify the
use of a directory called
C:\Winnt during the
installation, it is highly recommended that you not do so.