In the default installation of Windows Server 2008, the installation of server roles is performed in the Manager that is automatically launched upon system startup. In the Core Installation, though, it has a more spartan look:
The server role display is reminiscent of the DOS command "tree"
As in good old DOS, OCList brings up an overview of the available roles in a tree structure. In addition, the program also shows which server roles have been installed.
A server role is installed using the Ocsetup command, using as a parameter the name of the server role that the user would like to install. Here’s an example of what this looks like for the DHCP server:
Installation of a server role, in this instance a DHCP server
Note that the command start/w ensures that the command prompt waits until the end of the command.
Generally speaking, if there is no alert after execution of the command, then everything is fine.
After the installation of a server role, a few more steps are required. In particular, the DHCP server is still not active after installation, and needs to be switched on, and there is no Management console to assist you with this.
Enable the server role to start: setting the configuration on automatic start
In order to start the designated role, the server’s configuration must be changed from deactivated to automatic .
sc config dhcpserver start= auto
It is important to include the space after the term start=. If the space is left out, the command will not execute properly.
- Windows Server 2008 Core Installation
- Installation Of The System
- The First Login
- The "Desktop"
- Graphical Elements In The Core Installation
- Network Facilities
- Establishing The Network (continued)
- Installing Server Roles
- Uninstallation Of Server Roles
- Remote Access In The Console
- Remote Configuration With The mmC
- Screensaver Switched Off
- Activating The System
- Comparison: Core Installation Vs. Normal Installation
- Conclusion: A Server Installation For Professionals