Configuring Prerequisites
The
installation of the server portion of the process requires that certain
prerequisites be installed. Although the Add Roles Wizard can be used,
as shown in Figure 9, it is easier to install everything needed from a script:
Servermanagercmd -i web-server
Servermanagercmd -i web-webserver
Servermanagercmd -i web-common-http
Servermanagercmd -i web-static-content
Servermanagercmd -i web-dir-browsing
Servermanagercmd -i web-http-errors
Servermanagercmd -i web-http-redirect
Servermanagercmd -i web-health
Servermanagercmd -i web-http-logging
Servermanagercmd -i web-request-monitor
Servermanagercmd -i web-security
Servermanagercmd -i web-basic-auth
Servermanagercmd -i web-windows-auth
Servermanagercmd -i web-digest-auth
Servermanagercmd -i web-filtering
Servermanagercmd -i web-performance
Servermanagercmd -i web-stat-compression
Servermanagercmd -i web-mgmt-tools
Servermanagercmd -i web-mgmt-console
Servermanagercmd -i web-mgmt-compat
Servermanagercmd -i web-metabase
Servermanagercmd -i web-wmi
Servermanagercmd -i web-lgcy-scripting
Servermanagercmd -i web-lgcy-mgmt-console
Servermanagercmd -i rsat
Servermanagercmd -i rsat-addc
Servermanagercmd -i rsat-role-tools
Servermanagercmd -i rsat-web-server
Servermanagercmd -i was
Servermanagercmd -i was-process-model
Servermanagercmd -i was-config-apis
Take the preceding code and copy it in Notepad.exe. Save the file on the root of the C: drive and call it OCSPreReq.bat. The script running on the server can be seen in Figure 10. A reboot will be required when the script completes.
Deploying an OCS 2007 Server
After all the
prerequisites have been satisfied and the AD schema has been extended,
the process for installing an OCS 2007 standard server can begin. To
begin this process, perform the following steps:
1. | From the Deployment Wizard, click Deploy Standard Edition Server.
|
2. | Under Step 2, click Run.
|
3. | Click the Run button in the Deploy Server section at the screen that appears, as shown in Figure 11.
|
4. | Click OK if prompted to install Media Format Runtime. If a reboot is required, reboot the server and repeat steps 1 through 3.
|
5. | Click
Next on the first screen, accept the license agreement, and click Next.
Leave the installation folder at the default, and click Next to
continue.
|
6. | Select the appropriate Application Configuration. The default is All Services Selected.
|
7. | At
the account information field, select Use an Existing Account, and
enter the service account information entered in the previous steps for
delegation.
|
8. | At
the Component Service Account dialog box, choose Use an Existing
Account, and then enter the second service account created during the
delegation steps and its password. Click Next to continue.
|
9. | In the Web Farm FQDNs dialog box, shown in Figure 12, enter the external FQDN of the farm as it will be made available to Internet users (if applicable). Click Next to continue.
|
10. | Enter the database and log information into the fields in the Database File dialog box. Click Next to continue.
Note
For best performance, separate the RTCDYN and RTC logs onto physically separate drive sets.
|
11. | Click Next at the Ready to Deploy Server dialog box.
|
12. | Click Finish. |
