Professional Documents
Culture Documents
Communications
Server 2007 –
Software Update
Service Deployment
Guide
Published September 2007
Updated October 2007
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise
noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples
herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or
event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the
rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any
form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written
permission of Microsoft Corporation.
Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this
document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give
you any license to these patents, trademarks, copyrights, or other intellectual property.
Microsoft, Windows, Windows NT, Windows Server, Windows Vista, RoundTable, and SharePoint are either registered trademarks or
trademarks of Microsoft Corporation in the United States and/or other countries.
Introduction
Unified communication (UC) devices, such as Microsoft® Communicator Phone Experience and
Microsoft RoundTable™, enable rich communication within an organization. Deploying these
devices requires regular maintenance by the IT department, which includes providing available
software updates to these unified communications devices. All UC devices rely on an automatic
mechanism to obtain software update required on a regular basis.
Microsoft Office Communications Server 2007 Upgrade Service provides an automated way to
update all unified communications devices deployed in an organization. These software updates can
be the latest enhancements or fixes to known issues in the current version already deployed on the
device.
This document guides you through the process of deploying the Office Communications Server 2007
Software Update Service in your organization.
Supported Topologies
The Software Update Service must be installed on an Office Communications Server on which the
Web Component Server role is running. You can deploy the Software Update Service on the
following Office Communications Servers:
• A Standard Edition Server
• Each Enterprise Edition Server in the consolidated pool configuration
• Each Web Components (IIS) Server in the expanded pool configuration
6 Microsoft Office Communications Server 2007 Update Server
You must install the SharePoint Server on a dedicated separate computer from the Office
Communications Server 2007 Software Update Service.
If your organization contains multiple pools and Standard Edition Servers, you must install the
Software Update Service on each pool (all servers running the Web Components Server role) and
each Standard Edition Server.
Based on SharePoints usage model that assumes a 10% concurrent connection rate, a single
SharePoint Server update site can support up to 90,000 devices for an organization. If you assume a
usage model of up to 50% of the organization using devices, a single SharePoint Server can be used
for an organization with a user base of 180,000 users.
• Auto updates – This component gets newly published device updates from the Microsoft
Update Service (MUS), Windows Server® Update Service (WSUS), or the Windows Update
Agent. If your organization does not automatically connect to a Microsoft Update site, you can
manually download cab files that contain update metadata from the Microsoft Web site.
• SharePoint Server – The Update Site serves as the central repository for the update
information, logs, and audit information. The Update Site provides the installation point for
devices that require updates. It also allows administrators to view logs and other update data on
the SharePoint Server that contains a data store with the following information:
• Configuration information – Information such as the file storage host and share name,
Windows Server Update Service server information, the life time of the log folder, and other
configuration information required by Update Service is stored in the data store on the
SharePoint Sever.
SharePoint with
OCS with Update Module
Network
Update Service
UC Endpoints
Round Table
Public IP
HTTP
Perimeter
Communicator
Reverse
Proxy UC Endpoints UC
Phone Experience
Administrator
Communicator
Phone Experience RoundTable
External Internal
MUS data path OCS/Update Server data path
• If Communicator Phone Edition is connecting from within the intranet, it sends an HTTPS
request over port 443 to the SharePoint site.
• If Communicator Phone Edition is connecting from outside the intranet, it sends an HTTPS
request over port 443 to the SharePoint site.
5. The image is downloaded to the device.
6. The device waits for five minutes of idle activity, and then restarts
7. When restart is complete, the device is updated.
Overview of Deployment
Deployment involves two major tasks:
Introduction 11
• Configuring the SharePoint Server for the Software Update Service site and installing the
Software Update Service component on the SharePoint site. (This installation creates the
Software Update Services site.)
• Deploying the Office Communications Server 2007 Software Update Service on an Office
Communications Server.
Prerequisites
Ensure that you check for the following prerequisites before you start deploying.
1. Windows SharePoint Services is installed in your environment.
2. Microsoft Office Communications Server 2007 is deployed in your environment. You must
install the Software Update Service component on an Office Communications Server 2007
Standard or Enterprise Edition Server, as described earlier.
3. An existing PKI infrastructure is in place and devices are configured with a valid certificate
issued from a public CA (recommended) or a private CA that allows the device to connect to the
Update Service from outside the intranet.
4. If you intend to support external access to the Software Update Service to enable users with UC
devices to connect to the Software Update Service from outside your intranet: You must have:
• A supported edge topology deployed and operational in your perimeter network and remote
user access enabled for users with UC devices. For more information about deploying edge
servers, see the Microsoft Office Communications Server Edge Serve Deployment Guide.
• A reverse proxy in your perimeter network if you intend to support external access to the
Software Update Service.
5. If your organization uses IPSec, it must be configured to run in boundary or request mode.
Dependencies for Automatic Uploads
As explained earlier, if you want to automatically receive updates, the following is required:
• Microsoft Windows Server Update Service
• Microsoft Update Service
Configuring SharePoint
Configuring SharePoint involves the following steps:
Step 1 Create the SharePoint Default Site
Step 2 Enable Anonymous User Access
Step 3 Configure Alternate Mapping Access
12 Microsoft Office Communications Server 2007 Update Server
Step 4 Install Files for the SharePoint Server Software Update Service Component
Step 5 Create the Software Update Service SharePoint Site
Step 6 Grant Service Account Permissions to Administer the SharePoint Site
Step 7 Configure Certificates on the SharePoint Server
5. On the Add Internal URLs page, click No Selection, and then click Change Alternate Access
Mapping Collection.
Introduction 15
8. Repeat the following steps 4 – 7 and add each of the following URLs.
http://<SharePointServer fully qualified domain name> (http URL with fully
qualified domain name (FQDN) of the server)
https://<SharePointServer fully qualified domain name> (https URL with FQDN of
the server)
9. Verify that the following URLs display on the Alternate Access Mapping page.
https://<SharePointServer Name> (https URL with computer name)
16 Microsoft Office Communications Server 2007 Update Server
IIS Configuration
Use the following procedure to verify the proper settings in IIS.
To verify the proper configuration in IIS
1. Open Internet Information Services (IIS) Manager: Click Start, point to Administrative Tools,
and then click Internet Information Services (IIS) Manager.
2. In Internet Information Services (IIS) Manager, expand your server, and then expand
Application pools.
3. Verify that the following nodes display:
• SharePoint – 80
• SharePoint Central Administration v3
4. Under Application Pools, click Web Service Extensions.
5. In the details pane, verify that Asp.NET v2.0.50727 and Windows SharePoint Services V3
display with an Allowed status.
Administrator
Port number
Admin UserID This is the administrator user ID who can create the
SharePoint site.
Admin Email The e-mail alias for the administrator.
Password The administrator password.
Domain The domain on which the administrator account
resides.
SharePoint port The SharePoint port (TCP port of SharePoint – 80
site), port 80
For example:
Microsoft.RTC.UCServer.SharePointSetup.exe http://SharepointServer1 28406 ted
ted@contoso.com MyPassword corp.contoso.com 80
3. On the Site Settings page, under Users and Permissions, click Site Collection Administrator.
4. On the Site Collection Administrator page, next to Site Collection Administrators, type the
name of the service account used by the Web Components Server. If your organization uses the
default service account name, enter it (<domain>\RTCComponentService). If your organization
uses a different account, enter that service account name.
5. Click OK.
6. On the Site Settings page, click Advanced Permissions.
7. On the Permissions page, click New.
8. Click Add Users.
20 Microsoft Office Communications Server 2007 Update Server
9. Under Users and Groups, type the name of the service account used by Office Communications
Server 2007 Web Components. If your organization uses the default service account name, enter
it, RTCComponentService. If your organization uses a different account, enter that service
account name.
10. Under Give Permissions, click Give users permissions directly, and then click Full Control –
has full control.
14. On the SSL port page, accept the default port 443, and then click Next.
15. On the Choose a Certification Authority page, click your CA in the list, and then click Next.
16. On the Certificate Request Submission page, review the settings that you specified, and then
click Next.
17. Click Finish.
18. Open your SharePoint Server site using HTTPS: https://<FQDN of your server>
/sites/UCUpdateServer/default.aspx.
For example: https://sharepointserver1.contoso.com /sites/UCUpdateServer/default.aspx
Prerequisites
As explained earlier, to support Office Communications Server 2007 Software Update Service, an
Office Communications Server 2007 Standard Edition Server or Enterprise pool must be deployed in
your organization.
You must install the Office Communications Server 2007 Software Update Service on one of the
following:
• Office Communications Server 2007 Standard Edition
• Office Communications Server 2007 Enterprise Edition Server in a pool in the consolidated
configuration
• Office Communications Server 2007 Web Components Server (the server running IIS) in a pool
in the expanded configuration
Introduction 23
/user:RTCComponentService /Password:<password>
/ExternalWebfqdn:<External FQDN of Web farm>
where:
• InternalUpdatesStoreURL is the internal URL used to access the SharePoint Update site
from inside the intranet.
• ExternalUpdatesStoreURL is the external URL link to the SharePoint Update site from
inside the intranet. Use the following format: https://<ExternalFQDN>/sites/ucupdateserver.
• ExternalWebfqdn is the FQDN that devices use to connect to the Software Update Service
from outside the intranet. Use the following format: <external server FQDN>.
For a
Note:
• User identifies the service account under which Office Communications Server 2007 Web
Components is run. The default service account is RTCComponentService.
• Password is the password for the service account.
• guest is the guest user account used in Office Communications Server (the default account
is RTCGuestAccessUser) or it can be any domain user.
• guestpassword is the password for the guess user account.
Directory Use
https://<external server The external URL to the Web
FQDN>/RequestHandler/ucdevice.upx Components Server running
Software Update Service
https://<ExternalFQDN>/sites/ucupdate The external URL for the SharePoint
server Update site
Note: This directory is not accessible
from the outside because it does not
allow anonymous access.
UC devices use a fully qualified path to
the specific update they require.
The detailed steps in this section describe how to configure an ISA 2006 server as a reverse proxy. If
you are using a different reverse proxy, consult the documentation for that product. If you already
have an ISA Server or another reverse proxy configured for external user access for Office
Communications Server, proceed to Request and Configure a Certificate for Your Reverse HTTP
Proxy.
Introduction 27
You can use the information in this section to set up ISA as the reverse proxy, which requires
completing the following procedures.
• Configure Network Adapters
• Install ISA Server 2006
• Request and Configure a Certificate for Your Reverse Proxy
• Configure Web Publishing Rules
• Verify or Configure Authentication
• Create a DNS Record
• Verify Access through Your Reverse Proxy
ISA Server uses Web publishing rules to securely publish internal resources, such as a meeting URL,
over the Internet. Publishing information to Internet users makes computing resources inside the
internal network available to users outside the network.
Configure Network Adapters
You must assign one or more IP addresses to the external network adapter and at least one IP address
to the internal network adapter. For information about deploying ISA Server with a single network
adapter, see Configuring ISA Server 2004 on a Computer with a Single Network Adapter at the
Microsoft TechNet Web site. This document also applies to ISA Server 2006.
In the following procedures, the ISA Server computer has two network adapters:
• A public, or external, network adapter, which is exposed to the clients that attempt to connect to
your Web site (usually over the Internet)
• A private, or internal, network interface, which is exposed to the internal Web servers to which
outside users connect
6. In the Network Connections dialog box, right-click the internal network connection to be used
for the internal interface, and then click Properties.
7. Repeat steps 3 through 5 to configure the internal network connection.
Install ISA Server 2006
• Install ISA Server 2006 according to setup instruction included with the product. For more
information about installing ISA Server, see Microsoft ISA Server 2006 - Getting Started at the
Microsoft TechNet Web site.
Note
After completing the ISA Server setup, a default access rule
denying traffic to all network resources is present. You need to
configure your firewall rules as defined in the previous
procedure to resolve this denial.
Note
This procedure assumes that ISA Server 2006 Standard Edition
is installed.
To create a Web server publishing rule on the ISA Server 2006 computer
1. Click Start, point to Programs, point to Microsoft ISA Server, and then click ISA Server
Management.
2. In the left pane, expand ServerName, right-click Firewall Policy, point to New, and then click
Web Site Publishing Rule.
Introduction 29
3. On the Welcome to the New Web Publishing Rule page, enter a friendly name for the
publishing rule, and then click Next. For example, the name of the rule can be
OfficeCommunicationsWebDownloadsRule.
4. On the Select Rule Action page, select Allow, and then click Next.
5. On the Publishing Type page, select Publish a single Web site or load balancer, and then
click Next.
6. On the Server Connection Security page, select Use SSL to connect to the published Web
server or server farm, and then click Next.
7. On the Internal Publishing Details page, enter the FQDN of the internal Web farm that hosts
the Software Update Service in the Internal Site name box, and then click Next.
8. On the Internal Publishing Details page, enter /* as the path of the folder to be published in the
Path (optional) box, and then click Next.
Note
The ISA Server must be able to resolve the FQDN to the IP
address of the internal Web server. If the ISA Server is not able
to resolve the FQDN to the proper IP address, you can select
Use a computer name or IP address to connect to the
published server, and then enter the IP address of the
internal Web server in the Computer name or IP address
box. If you do this, you must ensure that the ISA Server has
port 53 opened and can reach an internal DNS server or a DNS
server that resides in the perimeter network.
• If your internal server is a Standard Edition, this FQDN is the Standard Edition server
FQDN.
• If your internal server is an Enterprise pool, this FQDN is the internal Web farm FQDN.
Note
In the Web site publishing wizard you can only specify one
path. Additional paths can be added by modifying the
properties of the rule.
9. On the Publish Name Details page, confirm that This domain name is selected for Accept
Requests for, type the external Web farm FQDN for the Software Update Service in the Public
Name box, and then click Next.
10. On the Select Web Listener page, click New to create a new Web listener.
11. On the Welcome to the New Web Listener Wizard page, type a name for the Web listener in
the Web listener name box, and then click Next. For example, type Web Servers.
30 Microsoft Office Communications Server 2007 Update Server
12. On the Client Connection Security page, select Require SSL secured connections with
clients, and then click Next.
13. On the Web Listener IP Address page, select External, and then click Select IP Addresses.
14. On the External Listener IP selection page, select Specified IP address on the ISA Server
computer in the selected network, select the appropriate IP address, click Add, and then click
OK.
15. Click Next.
16. On the Listener SSL Certificates page, select Assign a certificate for each IP address, select
the IP address you just added, and then click Select Certificate.
17. On the Select Certificate page, select the certificate that matches the public name specified in
step 10, click Select, and then click Next.
18. On the Authentication Setting page, select No Authentication, and then click Next.
19. On the Single Sign On Setting page, click Next.
20. On the Completing the Web Listener Wizard page, review the Web listener settings, and then
click Finish.
21. Click Next.
22. On the Authentication Delegation page, select No delegation, but the client might authenticate
directly, and then click Next.
23. On the User Set page, click Next.
24. On the Completing the New Web Publishing Rule Wizard page, review the Web publishing
rule settings, and then click Finish.
25. In the details pane, click Apply to save the changes and update the configuration.
To create a Web server publishing rule on the ISA Server 2006 computer
for the SharePoint site
1. Click Start, point to Programs, point to Microsoft ISA Server, and then click ISA Server
Management.
2. In the left pane, expand ServerName, right-click Firewall Policy, point to New, and then click
Web Site Publishing Rule.
3. On the Welcome to the New Web Publishing Rule page, enter a friendly name for the
publishing rule, and then click Next. For example, the name of the rule can be
OfficeCommunicationsWebDownloadsRule.
4. On the Select Rule Action page, select Allow, and then click Next.
5. On the Publishing Type page, select Publish a single Web site or load balancer, and then
click Next.
6. On the Server Connection Security page, select Use SSL to connect to the published Web
server or server farm, and then click Next.
Introduction 31
7. On the Internal Publishing Details page, enter the internal FQDN of the SharePoint Server
hosting the Software Update Service site in the Internal Site name box, and then click Next.
8. On the Internal Publishing Details page, enter /* as the path of the folder to be published in the
Path (optional) box, and then click Next.
Note
The ISA Server must be able to resolve the FQDN to the IP
address of the internal Web server. If the ISA Server is not able
to resolve the FQDN to the proper IP address, you can select
Use a computer name or IP address to connect to the
published server, and then in the Computer name or IP
address box, enter the IP address of the internal Web server.
If you do this, you must ensure that the ISA Server has port 53
opened and can reach an internal DNS server or a DNS server
that resides in the perimeter network.
Note
In the Web site publishing wizard you can only specify one
path. Additional paths can be added by modifying the
properties of the rule.
9. On the Publish Name Details page, confirm that This domain name is selected for Accept
Requests for, type the external FQDN for the SharePoint Server hosting the Software Update
Service site in the Public Name box, and then click Next.
10. On the Select Web Listener page, click New to create a new Web listener.
11. On the Welcome to the New Web Listener Wizard page, type a name for the Web listener in
the Web listener name box, and then click Next. For example, type Web Servers.
12. On the Client Connection Security page, select Require SSL secured connections with
clients, and then click Next.
13. On the Web Listener IP Address page, select External, and then click Select IP Addresses.
14. On the External Listener IP selection page, select Specified IP address on the ISA Server in
the selected network, select the appropriate IP address, click Add, and then click OK.
15. Click Next.
16. On the Listener SSL Certificates page, select Assign a certificate for each IP address, select
the IP address you just added, and then click Select Certificate.
17. On the Select Certificate page, select the certificate that matches the public name specified in
step 9, click Select, and then click Next.
18. On the Authentication Setting page, select No Authentication, and then click Next.
32 Microsoft Office Communications Server 2007 Update Server
Note
Perform the following procedure on each IIS Server in your
internal Office Communications Server.
The following procedure is for the default Web site in IIS.
Introduction 33
1. Click Start, point to All Programs, point to Administrative Tools, and then click Internet
Information Services (IIS) Manager.
2. Expand ServerName, and then expand Web Sites.
3. Right-click <default or selected> Web Site, and then click Properties.
4. On the Web Site tab, ensure that the port number is 443 in the SSL port box, and then click
OK.
5. On the Directory Security tab, click Server Certificate under Secure communications. This
opens the Welcome to the Web Server Certificate Wizard.
6. Click Next.
7. On the Server Certificate page, click Assign an existing certificate, and then click Next.
8. On the SSL Port page, ensure that the value is 443 in the SSL port this Web site should use
box, and then click Next.
9. On the Certificate Summary page, verify that settings are correct, and then click Next.
10. Click Finish.
11. Click OK to close the Default Web Site Properties dialog box.
Create a DNS Record
Create an external DNS A record that resolves the external Web farm FQDN to the external IP
address of the reverse proxy. The device uses this record to connect to the reverse proxy.
Verify Access through Your Reverse Proxy
Use the following procedure to verify that your users can access information on the reverse proxy.
You might need to complete the firewall configuration and DNS configuration before access works
correctly.
To verify that you can access the Web site through the Internet
1. Access your internal SharePoint Software Update Service site.
2. Under Updates, click UCPhone.
3. Select a vendor folder, select a model folder, select the hardware revision and software locale,
and then select the update type.
4. At the specific folder containing the update, right-click one of the update files, and then click
Properties.
5. In the Properties dialog box, copy the URL in the Address field, and then paste it into a
browser.
The URL looks similar to the following example.
34 Microsoft Office Communications Server 2007 Update Server
http://<internalSharePointServerFQDN>/sites/UCUpdateServer/Updates/UCPhone/Poly
com/CX700/A/ENU/CPE/CPE.cat
7. From outside your intranet, open a browser and ensure you can access the URL.
The following request receives a response from the Software Update Service because the device
is running an older version.
36 Microsoft Office Communications Server 2007 Update Server
Appendix A: Troubleshooting
This appendix lists possible conditions or problems you might encounter and the recommended
resolutions.
where:
• InternalUpdatesStoreURL is the internal URL used to access the SharePoint Update site
from inside the intranet.
• ExternalUpdatesStoreURL is the external URL link to the SharePoint Update site from
inside the intranet.
• ExternalWebfqdn is the FQDN that devices use to connect to the Software Update Service
from outside the intranet.
• User identifies the service account under which Office Communications Server 2007 Web
Components Server is run. The default service account is RTCComponentService.
• Password is the password for the service account.
• guest is the guest user account used in Office Communications Server (the default account
is RTCGuestAccessUser) or it can be any domain user.
• guestpassword is the password for the guess user account.
5. If the SharePoint Server changes, add the new account to the SharePoint site administrator.
If you change the port setting for a SharePoint site, use the following steps to update other settings:
1. The corresponding port changes should be updated in the Alternate Access Mapping.
2. Verify that the port has the correct certificate installed.
3. Update the URL details in the WMI entries.
Argument Description
Servername The SharePoint Server name, for example
http://TanjayTestSPS.
SharePoint The TCP port in the SharePoint Central
Central Administration.
Administrator
Port number
Admin UserID The user ID of the administrator who can create
the SharePoint site.
Admin Email The e-mail alias for the administrator.
Password The administrator password.
Domain The domain on which the administrator account
resides.
SharePoint port The SharePoint port (TCP port of SharePoint – 80
site).
For example:
Microsoft.RTC.UCServer.SharePointSetup.exe http://SharePointServer1:28406 Admin
admin@contoso.com ******* corp.contoso.com 80
2. If you encounter a site creation error with Operation Time Out, run the same command and
during the setup process, choose option 2 to delete the partially created site.
Introduction 39
3. On the Site Settings page, click Advanced Permissions under Users and Permissions.
40 Microsoft Office Communications Server 2007 Update Server
5. On the Change Anonymous Access page, select Lists and Libraries under Anonymous users
can access, and then click OK.
6. On the Permissions: Updates Server page, click Documents.
8. On the Updates page, click Settings, and then click Document Library Settings.
9. On the Customize Updates page, click Permissions for this document library.
42 Microsoft Office Communications Server 2007 Update Server
10. On the Permissions Updates page, click Settings, and then click Anonymous Access.
11. On the Change Anonymous Access Settings: Updates page, select the View Items check box,
and then click OK.
Introduction 43
2. After you change the settings to suit your particular installation, save the configuration (as
RTConfig.xml, for example) to the same directory as Rtmanage.exe. The section following this
procedure provides details of the InfoPath configuration form.
3. Open a command prompt, change the directory to %ProgramFiles%\Microsoft
RoundTable\DeviceManagement\, and then type the following command line.
Rtmanage.exe -m:img -i:config -f:RTConfig.xml
5. If there are no errors, proceed to the next step. Otherwise fix the errors and repeat from step 3.
6. Restart the device by running this command line.
Rtmanage.exe -m:cfg -r
4. The following shows an example of the configuration file. The portion in bold is specific to a
particular device.
<?xml version="1.0" encoding="UTF-8"?><?mso-infoPathSolution
solutionVersion="1.0.0.72" PIVersion="1.0.0.0"
name="urn:schemas-microsoft-com:office:infopath:DeviceConfig:http---www-
microsoft-com-RoundTable-DeviceManagement-RoundTable-
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:msdata="urn:schemas-microsoft-com:xml-msdata"
xmlns:mstns="http://www.microsoft.com/RoundTable/DeviceManagement/RoundTable.xs
d"
xmlns:xd="http://schemas.microsoft.com/office/infopath/2003">
<mstns:RoomSettings mstns:RoomName="Example" mstns:RoomSize="Medium"
mstns:TableSize="10'x5'" mstns:Lighting="Normal"
mstns:TextField1="" mstns:TextField2=""
mstns:TextField3=""></mstns:RoomSettings>
<mstns:NetworkSettings mstns:DeviceName="Example1"
mstns:DHCPEnabled="true" mstns:IPAddress="" mstns:SubnetMask=""
mstns:DefaultGateway="" mstns:PreferredDNSServer=""
mstns:AlternateDNSServer=""></mstns:NetworkSettings>
<mstns:TimeSettings mstns:TimeZone="Pacific Standard Time"
mstns:DaylightSaving="true"></mstns:TimeSettings>
<mstns:DisplaySettings mstns:DisplayLanguage="English"
mstns:ScreenSaverText=""></mstns:DisplaySettings>
<mstns:TelephonySettings mstns:PhoneNumber="" mstns:FlashTiming="700"
mstns:DialWithoutToneDetection="Off"></mstns:TelephonySettings>
<mstns:SoftwareUpdatesSettings mstns:UseAutoUpdate="true"
mstns:ExcludeConfig="false" mstns:UpdateTime="03:30:00"
mstns:UpdateInterval="Everyday"
mstns:Server="UpdateServer1.Domain1.Forest1.Contoso.com" mstns:Port="80"
mstns:Uri="/RequestHandler/ucdevice.upx"></mstns:SoftwareUpdatesSettings>
<mstns:LogSettings mstns:LogToServer="true" mstns:UploadTime="12:30:00"
mstns:UploadInterval="Every hour"
mstns:MaxLogSizeInMemory="1024"
mstns:Server="UpdateServer1.Domain1.Forest1.Contoso.com" mstns:Port="80"
Introduction 47
mstns:Uri="/RequestHandler/ucdevice.upx"></mstns:LogSettings>
<mstns:PowerManagementSettings
mstns:LCDBacklightOff="5"></mstns:PowerManagementSettings>
<mstns:AdvancedSettings
mstns:SpeakerDetectionAlgorithm="AudioVideoSpeakerSelection"
mstns:SpeakerSwitchingFrequency="Normal" mstns:WhiteBalanceSetting="Auto"
mstns:LightTemperature="4100K">
<mstns:DebugSettings mstns:AudioSetting="Off"
mstns:VideoSetting="Off" mstns:System="Off"
mstns:ExtendedProperties=""></mstns:DebugSettings>
</mstns:AdvancedSettings>
<mstns:SpeedDials>
<mstns:SpeedDial mstns:Name=""
</mstns:SpeedDials>
</mstns:RoundTable>
where:
• InternalUpdatesStoreURL is the internal URL used to access the SharePoint Update site from
inside the intranet.
• ExternalUpdatesStoreURL is the external URL link to the SharePoint Update site from inside
the intranet. Use the following format: https://<ExternalFQDN>/sites/ucupdateserver.
• ExternalWebfqdn is the FQDN that devices use to connect to the Software Update Service
from outside the intranet. Use the following format: https://<external server
FQDN>/RequestHandler/ucdevice.upx.
• User identifies the service account under which Office Communications Server 2007 Web
Components is run. The default service account is RTCComponentService.
• Password is the password for the service account.
• guest is the guest user account used in Office Communications Server (the default account is
RTCGuestAccessUser) or it can be any domain user.
• guestpassword is the password for the guess user account.
Use the following procedure to update the URLs external download URL, the internal download
URL, or the external download used by the SharePoint Update site.
To configure the external Web farm FQDN to the Software Update Service
1. Log on to an Enterprise Edition server hosting the Update Server. Use an account that is a
member of the RTCUniversalServerAdmins group or has equivalent privileges.
2. Click Start, click Run, type cmd in the Open box, and then click OK.
3. At the command prompt, type wbemtest.
4. Click Connect.
5. In the Namespace box, type root\cimv2, and then click Connect.
6. Click Query.
7. Select one of the following:
• On a Standard Edition server, type the following:
Select * from MSFT_SipUpdatesServerSetting where BackEnd="(local)\\rtc"
8. Click Apply.
9. Double-click the result returned.
10. In Object Edit, double-click the ExternalUpdatesDownloadURL property.
11. In the Value box, type the external URL used to connect with the Software Update Service using
the format https://<external server FQDN>/RequestHandler/ucdevice.upx.
50 Microsoft Office Communications Server 2007 Update Server