OCS 2007 R2 (RTM) Installation Walkthrough Part I
OCS 2007 R2 (RTM) Installation Walkthrough Part II
OCS 2007 R2 (RTM) Installation Walkthrough Part III
In the presence of an internal PKI infrastructure network based on Windows Server 2003 (or 2008) Certificate Services enhanced with Web-enrollment support, executing step 3 Configure Certificate under Deploy Standard Edition Server should be a real breeze.
Just create a new certificate and send it to an online Windows CA. The latter should be automatically detected by R2 to be fit for use. You should take all the suggested defaults and supply information that require human input i.e. Organization, Organization Unit and geographical information. Pay attention that the Subject Name and Subject Alternate Name have valid values specified. Then, dispatch the certificate at once which should permit you to Apply certificate immediately (recommended).
If you need help for Step 4 Configure Web Components Certificates, it is a matter of hitting the Help hyperlink to solicit more information to guide you. Step 5 Verify Replication is a manual process where you can use tools like repadmin.exe (ships with Windows Server 2008) to wok on this task.
With all this behind you, Step 6 is perhaps the most critical and can take quite a while to finish. As long as 10 out of the 11 OCS services start without any hiccups, R2 setup is almost done. You will find that except for the Monitoring agent that reports “Failure [0xC3EC79E6] Service failed to start as requested”, the deployment log should list the rest as Success. You can revisit to solve this issue later as monitoring is not part of the standard front-end server installation.
Clicking on the final Step 7 Validate Server Functionality hyperlink pops you into a 6-step Validate Pool or Server Functionality screen. Depending on your OCS infrastructure, you may want to run some or all of the validation tests to satisfy yourself that everything functions accordingly. Be prepared to see red errors if features such as enterprise voice, access edge / remote access or voice mail integration (Exchange 2007 Unified Messaging) are not installed or enabled in your environment. In any case, you can always return at a later time to conduct any of the tests at will.
You will want to connect to the upgraded UC platform with Microsoft Office Communicator clients (MOC), supported web browsers and Live Meeting client and run through a series of checks / functional tests as the next action.
The eleven Office Communications Server services are Front-End, Telephony Conferencing, IM Conferencing, Web Conferencing, Audio/Video Conferencing, Application Sharing, Monitoring Agent, Conferencing Attendant, Conferencing Announcement, Response Group and Outside Voice Control. One other outside this group is the Application Host.
All are set to Automatic as the service startup type and depend on the domain RTCService or RTCComponentService accounts to work.
No Comments »
Leave a Reply
You must be logged in to post a comment.