Today we installed the Web Scheduler of Live Meeting 2007. It takes my a while to install this web scheduler so for you a quick wrap-up.
What do you need to know before installing?
General information:
Web Scheduler is a resource kit tool for Microsoft Office Communications Server 2007. It provides a Web-based alternative to the add-in for the Microsoft Outlook messaging and collaboration client for the purpose of scheduling a meeting using Office Communications Server 2007. It also provides a browser-based conference management experience that includes operations such as:
- Scheduling a new Live Meeting conference or conference call.
- Viewing and modifying details of an existing conference.
- Listing all existing user schedules of a Microsoft Office conference.
- Deleting an existing conference.
- Sending an e-mail invitation to conference participants by using a configured SMTP mail server.
- Joining an existing conference.
Implementation steps:
Step 1. Install the Web Scheduler of Live Meeting 2007.
Download and install it on your Web Components Sever (in our case a Standard Edition server) download it here
Step 2. Active Web Scheduler
After installation is complete, you need to activate Web Scheduler using the same user name and password that you used to activate Web Components on the computer. If you do not remember the user name used to activate Web Components, use the following steps. Open IIS Manager (%SystemRoot%\system32\inetsrv\iis.msc), and then navigate to Local Computer, Application Pools, and LSGroupExpAppPool. Right-click LSGroupExpAppPool, click Properties, and then click the Identity tab. Note the user name under Configurable identity type. You only need the name part of the string. If the user name string is Domain\RTCComponentService, RTCComponentService is what you need to use in the activation procedure.
To activate Web Scheduler on Standard Edition, use the following command line:
LcsCmd.exe /web /action:Activate /role:Meeting /poolname:<pool_name> /User:<user_name> /Password:<password>.
Make sure the pool name is: computername otherwise you will get an (Pool is not ready error in your HTML debugfiles)
LcsCmd.exe tool is located under %CommonProgramFiles%\Office Communications Server 2007. Use pool_name = name of the computer (for example, computer1).
In our case:
C:\Program Files\Common Files\Microsoft Office Communications Server 2007>LCSCmd
/web /action:Activate /role:Meeting /poolname:<COMPUTERNAME> /User:RTCComponentService /
Password:V*******:-)
3. edit your web.config files
To configure the Web servers for sending e-mail invitations to invited participants, you need to configure an SMTP server. Make sure you edit both web.config files @
C:\Program Files\Microsoft Office Communications Server 2007\Web Components\Conf\Ext
C:\Program Files\Microsoft Office Communications Server 2007\Web Components\Conf\Int
*****extract from our web.config file*****
<?xml version="1.0"?>
<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">
<appSettings>
<add key="IsExternal"/>
<add key="SMTPServer" value="<MAILSERVERFQDN>"/>
And up and running! Enjoy. And some screenshots how it works and looks:
7 comments:
I tried to active Webscheduler by following your code. I get a message saying "The system cannot find the file specified".
All requirements are installed, the lcscmd file is on the server and the path is correct.
Any idea, what could be missing?
Apreciate your help
Ken
Make sure the appropiate application pool is selected and the RTCservice account is correctly configured. Did you also reset IIS?
Has anyone noticed that installing the Web Scheduler removes the externalwebfarm fqdn settings from WMI?
No, I didn't see that before.
I have gone through this process on our OCS Enterprise server. I am still getting the "Pool is not ready" error when trying to activate the web scheduler. Do you have any suggestions as to things I can check as I try to troubleshoot this problem?
Can you book a re-occurring meeting with web scheduler? Doesn't appear that you can.
yes this will remove your externalURL
you will need to reapply this either using WMI or export / import steps
we had to do this
Post a Comment