This post comes courtesy of an MVP and partner in our voice program, John Lamb with Modality Systems (www.modalitysystems.com)

Tom-LCSKID: Many partners and customers are reporting problems using the script used for configuring the Update Server. We, Microsoft, are aware of the issue and looking at how best to resolve these problems (my guess is a mix of documentation and likely script update (do not read this as confirmed or committed, simply my personal conjecture))

John shares the information below

Instead of running ConfigUpdateServer.vbs, do this instead:

Step 1:

LcsCmd.exe" /Web /Role:UpdatesServer /Action:Activate /User:<RTC Component Service Acct Name> /Password:******** /ExternalWeb

fqdn:<public fqdn of ISA Server>/RequestHandler/ucdevice.upx /PoolName:<host name of pool>

example:

LcsCmd.exe" /Web /Role:UpdatesServer /Action:Activate /User:RTCComponentService /Password:******** /ExternalWeb

Fqdn:portal.modalitysystems.com/RequestHandler/ucdevice.upx /PoolName:OCSPool01

Important:  Don’t use “https://” in public FQDN.

Step 2:

Update these WMI properties manually:

WMI Attributes

Examples

ISA Web Publishing Rules

TomL-LCSKID on behalf of John Lamb