| ... | Table of Content |
| ... | Preface |
| ... | About This Book |
| 1 | Overview and History |
| 2 | Installation |
| 3 | Licensing |
| 4 | Configuration |
| 5 | Client Software |
| 6 | Application Installation |
| 7 | System Administration |
| 8 | Network Planning |
| 9 | Printing |
| 10 | User Environment |
| 11 | Virtualization |
| 12 | RDS Internals |
| 13 | Remoting Protocol Details |
| 14 | Security |
| 15 | Registry Settings |
| 16 | Server Sizing |
| 17 | Resource Management |
| 18 | Testing and Quality Assurance |
| 19 | RDS Scripting |
| 20 | RDS for Developers |
| ... | About |
| ... | Benny's Biography |
| ... | Presentations 2009, 2008, 2007, 2006, 2005, 2004 and earlier |
Posted by Benny Tritsch on September 10, 2008; updated on December 31, 2008
[System Installation] [Requirements] [Installation Phases] [Server Manager]
Read in this lesson...
To successfully install Windows Server 2008, you need to make sure that you have the adequate hardware platform acting as a target. If your server hardware has less than the minimum requirements, you will not be able to install the operating system correctly.
To install Windows
During installation you will be asked if you want to join a Windows domain or a workgroup. If you decide to join an existing domain, you need a domain name and an account for the server you want to install. The former can be obtained from the administrator of the domain name system (DNS), the latter from the domain administrator. You need both before you can install your new system. You can only generate a domain name and a server account during installation if you have domain administrator privileges.
NOTE: To join a domain, you need to make sure that a domain controller is available and that a server with DNS service is activated on your network.
If you are on a small network that has no domain or if you prefer to join the domain later, you can join a workgroup. You can select the name of an existing workgroup or create a new workgroup.
Before you install the server, you should also decide on a password for the local administrator account. The password should conform to general security guidelines to protect your server from potential attacks right from the start. If you enter a non compliant password, a corresponding message will appear. If you leave the password blank, you will not be able to access the server later using Terminal Services from a remote client.
NOTE: Like Microsoft, I do not advice to install Terminal Services on a domain controller. Better plan to install Terminal Services in application server mode on a member server or a standalone server, but never on a domain controller. When installed on a domain controller, Terminal Services performance is affected because of the additional memory, network traffic, and processor cycles required to performing the tasks of a domain controller. Additionally, security settings may be affected in a negative way.
The Windows Server 2008 operating system is delivered with all necessary components on one DVD-ROM. There are different installation methods, depending on the current configuration.
In many environments, terminal servers are installed on enterprise-class system rather than on standard PC-based hardware. There are simple reasons for this. Enterprise-class servers are systems specifically built for large networks. They are designed for being extremely scalable and may even include redundant components due to unexpected issues which cause the server to fail. This means that an enterprise-class server usually contains advanced hardware, such as Redundant Arrays of Inexpensive Disks (RAID). Implementing RAID is a best practice when deploying an enterprise class server, but missing or inadequate RAID drivers will prevent a successful installation of Windows Server 2008.
Typically, enterprise-class servers are shipped with their own management software tools which, among other important tasks, are used to install drivers. To configure RAID prior to the operating system installation sequence, you most probably will have to use the server BIOS or a management utility that came with the server. This being said, you must make sure that you have all of the drivers and software needed for the deployment of Windows Server 2008.
When installing Windows Server 2008, you may encounter issues even if you believe you fulfill the requirements mentioned previously. These issues may be created by one of the following reasons.
Make sure that you are following the correct upgrade paths.
| Read in this chapter... | |
| 2 | System Installation |
| 2.1 | Installation Requirements |
| 2.2 | System Installation Phases |
| 2.3 | Server Manager and Server Roles |