Installing win2003 server

Do not install Windows Server on the same partition with another version of Windows Server. Following are the best practices for client computer configuration: Automatically configure all of your domain member Do not use password-based authentication methods because they are vulnerable to a variety of attacks and are not secure.

You can also use your CA to deploy computer certificates to domain member computers and user certificates to members of the Users group in Active Directory. Your NPS server provides authentication, authorization, and accounting for connection attempts to your organization network.

When Remote Desktop Connection users log on, they can view only their individual client sessions, which are managed by the server and are independent of each other. In addition, Remote Desktop Connection provides bit encryption between client and server. Use Internet Protocol security IPsec to encrypt confidential data. You can use event logging to record NPS events in the system and security event logs.

This information is used primarily for auditing and troubleshooting connection attempts. Logging user authentication and accounting requests. Request logging is used primarily for connection analysis and billing purposes, and is also useful as a security investigation tool, providing you with a method of tracking down activity after an attack.

If you can't open the CD drive while your computer is off, put the CD into the drive while the computer is on, and then restart your computer. This is so the computer loads from the CD to begin the installation process. Wait as the Windows Setup screen loads. Hit the "Enter" button once the "Welcome to Setup" message appears. Read the Windows Licensing Agreement and hit the "F8" button to agree to the terms and continue to the next screen. Create the partition on your hard drive where you will install Windows Server Highlight "Unpartitioned space" and hit the "C" key.

Type in the amount of the drive you would like to partition. If you want to use the whole drive, type in the same number as shown next to "The maximum size for the new partition. Wait as the installer formats the drive. Then, wait as the installer copies the Windows Server files to your hard drive.

A yellow progress bar will show you the progress of each of these processes. Hit the "Enter" key to reboot your computer after the setup process completes. Wait as the installer loads device drivers for your computer. Click "Next" on the screen titled "Regional and Language Options. Enter your name and organization on the next screen and click "Next.

Click "Next. Think of an administrator password and enter it on the next screen. Change the computer name. Configure your network settings by clicking "Custom settings" on the screen titled "Network Settings" and clicking "Next.

Click "OK" and then click "Next. I'm wondering is the driver definitely the problem? Because I have tried over 10 different drivers separately. Any driver that has anything to do with Perc 6 and windows server I have tried. Well I did start thinking that myself until I got to the point when you said you had tried 3 diff machines, so this made me think it can't be the hardware. I spent weeks on this as a side project. I have 5 R servers so I tried most of them with perc drivers. I even put windows server onto one just to make sure it was working, installed fine.

I have a R with server on it, but I didn't set it up. Is there any way I can get information from that to help me install Win on a clean server from scratch? I have imaged it and that worked, but I want to do it from scratch. I know it is possible.

Welcome to the community!! What is the reason to install server right now? It has been out of support so whatever you need should be either virtualized or moved to a newer system. What do you need from that server? If you really cannot use virtualization and you must use and nothing else, why not simply install it on a PC, it's limited in what it can do and the ram it can use anyway. Curious, why can it not be virtualized? It is being used as a hot spare.

There is one already set up. We want another set up the same way in case the working one goes down. Is the application a 32 bits application? If so it should be able to be virtualized, does it depend on any hardware to function like a printer or serial connection? Because you can always convert those connections to network. You can also check with the software vendor. It doesn't really matter as I have been told it cannot be visualised.

The boss does not want it visualised, as the previous build was not done that way. However, we want to build the machine from scratch also. It has been done, so we want to get to the bottom of it and do it ourselves. For now, if a machine goes down I am covered. But I wanted to start this discussion as I know it can be done from scratch and I want help on how to do it. This post should give you an idea as well I just cannot recommend installing Server on a piece of hardware right now.

Can we keep in mind that I am newly graduated from college so I might make some mistakes, feel free to correct me and ask questions again!