|
OCS Update Server
check List |
This article will help you ensuring that OCS update
service is installed and configured properly.
Let’s understand the best practice and what Microsoft
supports about OCS update service.
1)
Sharepoint Server: This is a dedicated server for Sharepoint Service. You need to install Windows
Sharepoint Service 3.0 plus Service Pack 1 and
OCSSoftwareUpdateServiceSP.msi.
2)
OCS Update Server: The web component server. You need to
install OCS update server on each web component server.
These are also the OCS Front End servers.
Note: Ensure that above two servers are not
co-located. These should be two separate servers.
Before we begin:
Ensure that the web component service is working fine.
Internal users should be able to download address book
and expand dl in office communicator.
Verification of Sharepoint site:
Verify Sharepoint is working by navigating to
Administrative Tools and choose Sharepoint Products and
Technologies Configuration Wizard. When you complete
the Wizard the default Sharepoint site should open.
Ensure authentication page has right info:
Enable Anonymous Access on the Sharepoint site. Access
Sharepoint site (http://sharepoint_site/default.aspx)
=> Central Administration => Application Management =>
Application Security => Authentication Providers => Edit
authentication. On this page the web application should
be mapped to Sharepoint-80, Authentication type should
be “Windows”, Anonymous Access should be enabled.
Ensure that Alternate Mappings are configured
Access Sharepoint site (http://sharepoint_site/default.aspx)
=> Central Administration => Operations => Alternate
Access Mappings => Add Internal URLs. Add following
URLs…
http://servername
https://servername
http://servername.domain.com
https://servername.domain.com
Ensure that you have installed
OCSSoftwareUpdateServiceSP.msi on Sharepoint Server.
Ensure that Asp.Net v2.0.x and Windows SharePoint
Services V3 are allowed in the Web Service Extensions.
Create Sharepoint Site:
Access the location C:\Program Files\Common
Files\Microsoft Shared\web server extensions\12\ISAPI\
on the command prompt and run following command:
Microsoft.RTC.UCServer.SharePointSetup.exe
http://servername
50506 Administrator Administrator@ocspedia.com P@ssw0rd
ocspedia.com 80
In
above command:
http://servername
is the sharepoint server name.
50506 is the Sharepoint Central Adminisration port. You
can find this by selecting Web Sites from the IIS Admin
and looking at the port the SharePoint Central
Administration V3 web site is listening on.
Administrator is the SAMAccount which has permission to
create the site.
Administrator@ocspedia.com is the admin e-mail address.
P@ssw0rd is the password for the Admin account.
Ocspedia.com is the domain where admin account belongs
to.
80 is the TCP Port the Sharepoint - 80 site is listening
on.
Verify that you can access the UCUpdate server site by
navigating following URL.
http://servername/sites/UCUpdateServer/default.aspx
Ensure Web Components Service account has permission as
“Site Collection Administrators”.
Access http://servername/sites/UCUpdateServer/default.aspx
=> Site Actions => Site Settings => Users and
Permissions => site collection Administrators. Now enter
the service account (domain\rtccomponentservice) for the
Web Components Server. By default it is
rtccomponentservice.
Ensure you have correctly configured “Advanced
Permissions”
Access http://servername/sites/UCUpdateServer/default.aspx
=> Site Actions => Site Settings => Users and
Permissions => Advanced Permissions. On the Permissions
page, Under the Users and Groups, add the Web Components
service account. Under give users permissions directly,
choose Full Control.
Certificate to the Sharepoint server:
Request and assign a Web Server certificate to the
Sharepoint server. FQDN of the server should be the
Subject name.
Let’s move to the OCS Update Server:
Ensure that OCSSoftwareUpdateService.msi on each web
Component Server.
You can download the setup from
here…
Activate the OCS Update Server:
Open command prompt and navigate to the folder
c:\Program Files\Common Files\Microsoft Office
Communications Sever 2007. And run the following
command:
LCSCmd.exe
/Web /Role:UpdatesServer /Action:Activate /User:<RTC
Component Service Account Name> /Password:<Account
Password> /ExternalWebFqdn:<public fqdn of reverse
proxy>/RequestHandler/ucdevice.upx /PoolName:<host name
of pool>
An Example:
LCSCmd.exe /Web /Role:UpdatesServer /Action:Activate /User:rtccomponentservice
/Password:P@ssw0rd
/ExternalWebFqdn:sip.ocspedia.com/RequestHandler/ucdevice.upx
/PoolName:OCSSE
Ensure that the WMI attributes are having right value.
Start => run => type wbemtest => Connect =>
Root\CIMV2 => Enum Classes => Leave the super class name
blank and click Ok => In query result, double click
MSFT_SIPUpdatesServerSetting. This will open the
property sheet of WMI attributes related to OCS Update
server. Modify the following WMI Attributes as per the
following table.
|
WMI Attributes |
|
|
ExternalUpdatesDownloadURL |
https://<fqdn of revere proxy server>/RequestHandler/ucdevice.upx |
|
InternalUpdatesDownloadUrl |
https://<fqdn of OCS Pool or SE Server>/RequestHandler/ucdevice.upx |
|
ExternalUpdatesStoreURL |
https:// <fqdn of reverse proxy
server>/sites/ucupdateserver |
|
InternalUpdatesStoreURL |
http://<hostname or FQDN of WSS
Server>/sites/ucupdateserver |
|
MgmtConsoleURL |
https:// <fqdn of OCS Pool or SE Server>
/MgmtConsole |
Certificate on the OCS Update server virtual
directories.
Since you have installed OCS Update server on web
component server(s), so most probably you should have
already certificate assigned to the OCS update server
virtual directories. By any chance if the certificate is
not configured then do it now.
Verify you can open the management console.
Browse https:// <fqdn of OCS
Pool or SE Server>/MgmtConsole.
If you could browse this link, the OCS update server has
been installed.
Download the OCS Phone device update and upload it to
the Update Server.
Download the update from
here…
You will get .exe file. Extract it to get .cab file.
Browse
https:// <fqdn of OCS Pool or SE Server>/MgmtConsole
and upload the cab file.
After uploading to the update server, approve the
updates.
Add the Phone Devices:
Get IP Address of the Phone Device (Tanjay).
Find the Mac Address of the phone device from DHCP
Server with the help of IP Address.
Open the Management Console: Open a
browser and type
https://< <FQDN
of a Web ComponentsServer in the pool or your Standard
Edition server>/MgmtConsole/default.aspx
Click the Test Devices tab.
Click Add a new test device.
Under Friendly name, enter a
meaningful name for the device.
Under Type, select Mac Address
or Serial Number.
Under Unique identifier, enter the
Mac address or serial number.
Click Save.
Now restart the OCS Phone device which you added during
above process. During restart, the Phone device will
collect Update server information from the OCS Front End
Server.
Verify the Audit Logs
Use the following procedure to verify that the Software
Update Service correctly connected with your test device
and sent valid information.
Open the Update Site on your SharePoint
Services: Open a browser and type http://<FQDN of
SharePoint Server>/sites/UCUpdateServer/default.aspx/.
Under Documents, click Logs.
On the Logs page, click the
Server folder.
Click the Audit Folder.
Click the ImageUpdates Folder.
Open the current audit log. And check the
logs.
Check IIS Logs
Open the IIS logs and see if OCS Phone
devices are approaching to the IIS server to connect
with the right URL.
You need to collect IIS logs from the
following folder in order to check this.
%System Drive%\system32\LogFiles\W3SVC1
OCS
Phone Device Logs
You could also check the Phone devices log to see what’s
going on at the Phone Device end. You need to collect
logs from the following location…
ftp://<IP addr of the phone device>/logs/domotraces
If you find the above folder empty, you need to ensure
that the logging is enabled in Phone device. Follow the
steps mentioned below to do that…
Go to phone device and exit the application by pressing
the following key combination in quick succession:
Settings (checkbox key), Back, Options
Open My Devices
Open Windows
Open Register-mwi.exe
Verify that logging is set to High for all logs
Launch Domo.exe
It’ll ask you to sign in; do sign in so that the logs
get created.
Now access the FTP location to get the logs.
Related Links:
