OCS 2007 Installation - Part 1

March 5, 2008

Assumed Pre-Existing Environment

 

This will be the first part of many in showing the steps necessary for standing up an OCS 2007 server. In the examples that follow the internal domain name is ptown.com and the SIP domain, or my external facing address will be confusedamused.com

tap-dc-2k3.ptown.com

• Domain Controller for ptown.com
• DNS Server for ptown.com
• Certificate Authority named P-Town Certificate Authority
• Domain in 2003 Native Mode
• IP Configuration: 192.168.0.10 / 24
• Gateway: 192.168.0.1
• DNS: 127.0.0.1

tap-ocs-2k7.ptown.com

• Blank Windows 2003 Server joined to the ptown.com domain
• IIS Installed with ASP.net enabled
• Adminpak.exe installed
• IP Configuration: 192.168.0.20 / 24
• Gateway: 192.168.0.1
• DNS: 192.168.0.10

Schema Preparation

On tap-ocs-2k7.ptown.com run the setup.exe application to start the installation. You’ll see a message that the Visual C++ 2005 redistributable must be installed. Click Yes.

On the main setup screen click Deploy Standard Edition Server.

Now click Prepare Active Directory.

Press the Run button under Prep Schema.

The Schema Preparation Wizard starts. Click Next.

Assuming the installation media has not been modified, the schema files should be in the same directory as setup so press Next.

Press Next again to start the schema preparation.

A success dialog will appear when it finishes. Check the box to view the log if desired, but press Finish to continue.

At this point you should wait and then verify the schema has replicated to all domain controllers in the forest before continuing.

Forest Preparation

Press the Run button under Prep Forest.

The Forest Preparation Wizard starts. Press Next.

Leave the default selection of System container in the root domain and press Next.

Select forest root domain, ptown.com in the drop down and press Next.

Select the external SIP domain, confusedamused.com, for default routing and press Next.

Confirm the forest preparation settings and press Next.

A success dialog will appear when it finishes. Check the box to view the log if desired, but press Finish to continue.

Again, wait for the changes to be replicated to the entire forest before continuing.

Domain Preparation

Press the Run button under Prep Domain.

The Domain Preparation Wizard starts. Press Next.

Press Next to acknowledge the warning about group creation.

Confirm the domain preparation settings and press Next.

A success dialog will appear when it finishes. Check the box to view the log if desired, but press Finish to continue.

This time wait for the changes to be replicated to the entire domain OCS is being deployed within. Run the domain preparation wizard for any other domains hosting OCS.

At this point OCS admin rights can be delegated to users and groups. This can also be accomplished later by running the wizard again. Press the Deploy Standard Edition link at the top to go back and deploy the Standard Edition Server.

Deploy Server

Click the Run button under Deploy Server to start the installation process.

The Deploy Server Wizard starts. Press Next.

Accept the license terms and press Next.

Choose an installation location and press Next.

Enter a password for the RTCService account and press Next.

Enter a password for the RTCComponent account and press Next.

Accept the default blank external web farm FQDN’s for now. The external address will adjusted later. Press Next.

Select a location for the database and transaction logs. Ideally, these should be on separate disk controllers. Press Next.

Review the configuration settings and press Next to start the installation.

A success dialog will appear when it finishes. Check the box to view the log if desired, but press Finish to continue.

Configure Server

The Deploy Server section should now have a green checkmark next to it. Click the Run button under Configure Server to continue.

The Configure Pool/Server Wizard should start. Press Next to continue.

Press Next to accept the only server installed so far, tap-ocs-2k7.ptown.com.

The SIP domain was already entered earlier, but additional SIP domains can be added here. Press Next to continue.

Choose the option Some or all clients will use DNS SRV records for automatic logon and check the box Use this server or pool to authenticate and redirect automatic client logon requests. Press Next.

Choose the SIP domain for automatic logon, confusedamused.com and press Next.

Select Do not configure for external access now and press Next.

Review the configuration settings and press Next to begin the configuration.

A success dialog will appear when it finishes. Check the box to view the log if desired, but press Finish to continue.

That concludes Part 1 of this series. Not very interesting yet, or hard to screw up either. The other parts should be much more interesting.

This entry was posted on Wednesday, March 5th, 2008 at 10:46 am and is filed under Office Communications Server 2007. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.