So you may have read some blog posts about the perils of installing OCS SUS, to update the Tanjay device. I recently attempted this myself and hit several glitches. This is definitely not an easy procedure.
When you begin with the OCS SUS Deployment Guide, it assumes that you have a SharePoint site collection at http://<hostname-of-sharepoint-server> listening on port 80. The SUS SharePoint site MUST be located at http(s)://<hostname-of-sharepoint-server>/sites/UCUpdateServer. The UCUpdateServer site will be created by the SUS SharePoint installation process but the root Site Collection must already exist for the Deployment Guide to make any sense. The Deployment Guide refers to the root site collection as SharePoint-80.
When you get to the point in the Deployment Guide when you are ready to activate the SUS server with the ConfigUpdateServer.vbs, STOP and read.
http://aspoc.net/archives/2007/11/05/ocs-software-update-and-the-address-book-service/
If you decide to follow the alternative instructions at LCSKid’s blog, then you should be aware that is instructions in Step 1 are incomplete if you are running an Enterprise Pool instead of a Standard Server. You will get the error: “ERROR (0xC3EC7922): Guest access user or user password isn’t specified.” Apparently the /Guest and /GuestPassword switches are necessary for Enterprise Pool deployments. Use the RTCGuestAccessUser and password that were created when the pool was initally deployed. The command now looks like this:
Step 1:
LcsCmd.exe” /Web /Role:UpdatesServer /Action:Activate /User:<RTC Component Service Acct Name> /Password:******** /ExternalWebFQDN:<public fqdn of ISA Server>/RequestHandler/ucdevice.upx /PoolName:<host name of pool> /Guest:RTCGuestAccessUser /Password:*********
example:
LcsCmd.exe” /Web /Role:UpdatesServer /Action:Activate /User:RTCComponentService /Password:******** /ExternalWebFQDN:portal.modalitysystems.com/RequestHandler/ucdevice.upx /PoolName:OCSPool01 /Guest:RTCGuestAccessUser /Password:*********
Important: Don’t use “https://” in public FQDN.
I got to this point and couldn’t figure out how to modify or view these WMI values in Step 2. I found that you can use lcscmd.exe to export these values. See Resolution 2 on KB Article 938288 for an example on exporting. You can then use Resolution 1 as an example on how to modify these values.
Exporting:
Lcscmd /web /action:ListWMISettings /poolname:poolName
Modifying:
| 1. | Log on to the computer that is running Communications Server 2007 Standard Edition or Communications Server 2007 Enterprise edition by using an account that is a member of the RTCUniversalServerAdmins group or that has equivalent permissions. |
| 2. | Click Start, click Run, type wbemtest, and then click OK. |
| 3. | In the Windows Management Instrumentation Tester dialog box, click Connect. |
| 4. | In the Connect dialog box, type root\cimv2 in the Namespace box, and then click Connect. |
| 5. | In the Windows Management Instrumentation Tester dialog box, click Query. |
| 6. | In the Query dialog box, type the following in the Enter Query box according to the edition of Communications Server 2007 that you are using, and then click Apply:For Communications Server 2007 Enterprise pool
Select * from MSFT_SIPUpdatesServerSetting where backend=”server name\\sql instance“ For Communications Server 2007 Standard Edition Select * from MSFT_SIPUpdatesServerSetting where backend=”(local)\\rtc“ |
| 7. | In the Query Result dialog box, double-click the result. |
| 8. | Modify the properties as decribed by LCSKid. |
| 9. | Click Save Object, and then click Close |
EDIT: It turns out that instructions for modifying the WMI values are in Appedix C of the SUS Deployment Guide as well.
Comments on this entry are closed.