Introduction to Windows .NET Server Page 2
If you elect to upgrade your current Server Operating system you need to be aware that the Setup program will automatically install Windows .NET Standard Server into the same folder as the currently installed operating system, regardless of its naming convention.
You can perform direct upgrades to
Windows .NET Standard Server from the following versions of
Windows NT Server 4.0 with Service Pack 5 or later
Windows NT Server 4.0, Terminal Server Edition, with Service Pack 5 or later. (Even though Setup will allow the upgrade, Windows .NET Standard Server will not allow for the same level of terminal services that was previously provided by Windows NT Server 4.0, Terminal Server Edition. If you want the same level of Terminal Server functionality you will need to upgrade to Windows .NET Enterprise Server, not Windows .NET Standard Server.)
Windows 2000 Server, on a computer with one or two processors. While Windows 2000 Server supports 4 processors, Windows .NET Standard Server does not.
You cannot upgrade from Windows 9x, ME, Windows NT Workstation, Windows 2000 Professional and Windows XP Home and Professional directly to Windows .NET Server BETA 3. (Clean installations from within those existing operating systems to other partitions or over, as in overwrite, are allowed.) Also, if you have Windows NT 4.0 Server Enterprise Edition, you can upgrade to Windows .NET Enterprise Server but not Windows .NET Standard Server. Service Pack 5 or later is still a requirement. If you have a version of Windows NT earlier than 4.0, such as Windows NT Server 3.x, you cannot upgrade directly to any product in the Windows .NET Server family. You can first upgrade to Windows NT 4.0 and apply Service Pack 5 and then perform a direct upgrade if desired.
You can to confirm that your hardware is compatible with Windows .NET Server by running a pre-installation compatibility check from the Setup CD.
Typing <CDROM DRIVE>\i386\winnt32 /checkupgradeonly either from a command line or the RUN box will launch the Setup Wizard to perform only a system check of the current hardware from within an existing operating system.
The results screen will appear with any
pertinent information after a few moments.
Regardless of whether you intentionally run the pre-installation compatibility check step ahead of time or not, the Setup Wizard checks hardware and software compatibility at the beginning of a "standard" installation or upgrade and displays a report if there are any known incompatibilities.
If you insert the installation disk into the CDROM drive and autorun is enabled, the Welcome screen shown below will appear and allow you to either attempt an upgrade or a clean installation, as well as perform any additional tasks or to check system compatibility.
If you elect to perform a "manual" system compatibility check, you are allowed to either run the check against the local database (the CDROM) or to visit the compatibility web site. (The compatibility web site offered no information on Windows .NET Server at the time of this writing.)
As you can see, an error is generated as I am not allowed to upgrade from Windows XP Professional to Windows .NET Standard Server.
Again, this does not prevent you from installing Windows .NET Standard Server as a clean install in this particular instance.
Installing Windows .NET Standard Server (BETA 3)
After performing the standard BIOS configurations to allow booting from the CDROM you can load the bootable disk and begin the installation.
The first screen you'll see will be the black Setup is inspecting your computer's hardware configuration. (If there is an active partition on any of the installed hard drives in the system, you will see a "Press any key to boot from the CD" message before you reach this screen. If you do not hit a key before the timeout, the CDROM will be bypassed in favor of your local active partition.)
From here, Setup continues to the Windows .NET Server Setup screen where all of the drivers are loaded.
After the drivers load, the Windows Setup screen appears and Setup copies the required temporary files to the local hard drive after you acknowledge the location of the setup files.
After the file copy is complete, the Setup Program will append any existing boot.ini file (or write a new one) and will reboot and continue the installation from the locally copied temporary files.
After the system restarts and continues past the splash screen, you'll arrive at the Windows .NET Standard Server Setup screen where you will select ENTER to continue with the normal installation. (This is also where you would be able to repair a failed installation using the Recovery Console.)
You will then arrive at the partition selection screen. The hardware layout of your system and whether or not you have any existing partitions installed will affect what this screen displays. In my example, I already have formatted partitions and two other operating systems installed. I pre-named the partition where I wanted to install the Windows .NET Standard Server, (NETSERVER), so I have selected it and hit enter. (Other options include deleting existing partitions and creating new ones from free space or recently deleted partitions, as listed in the image below.)
After selecting the partition and hitting ENTER, I am brought to the file system selection screen as shown below. Here I can choose to convert my FAT32 partition to NTFS or to leave it as is. (I can always perform CONVERT after the operating system is installed as well.)
I selected to convert the partition by arrowing up the menu one space and hitting ENTER, which brought me to the conversion screen, shown below.
I hit 'C' to perform the process of converting the drive to NTFS, which will happen at the next reboot.
Setup continues from here by copying files from the temporary location on the hard drive to the default installation folder <DRIVE LETTER>\Windows. As with Windows XP Professional, you can only select the installation path drive letter and not the name of the systemroot folder during a standard installation. (If you use an unattended setup file you can then include a path designation other than WINDOWS.)
When this section of the file copy is finished, the system will reboot. Upon restart the FAT32 partition will be formatted with the NTFS file system and the system will reboot again.
IT Solutions Builder TOP IT RESOURCES TO MOVE YOUR BUSINESS FORWARD
Which topic are you interested in?
What is your company size?
What is your job title?
What is your job function?
Searching our resource database to find your matches...