Hi, We've been using IBCM successfully for a few years under CM07 and CM12. Server is internal, behind TMG. (DirectAccess is not an option for me today, thanks!)
With the CM12 SP1 upgrade, we saw all internet clients start to fail scanning, which turned out to be because our internet-enabled SUP stopped syncing until we reconfigured it after the SP1 upgrade. So, we figured that out and got synchronization running again and now our Server 2003 internet clients are scanning with success, but our 2008 R2 boxes are getting scan errors around the EULA .txt files. I am pretty sure these EULA .txt errors were not a problem before the upgrade (we had been patching successfully), but since the logs have rolled over I don't have a history to be certain. The EULA .txt errors have two issues: 1) they are making the request over 8530 HTTP rather than 8531 HTTPS (unreachable because we have only ever had HTTPS ports open on TMG and core firewall) 2) even though they are scanning against the correct Internet host name, the EULA .txt URLs are being returned with the Intranet host name (unreachable because... Internet). MS Support is sort of pushing back to say 8530 must be open, which I didn't think should the case, and even if we did open 8530 the clients would still be trying to get the EULA .txt files from the wrong host name and the MS System Center support engineer is kind of stuck, stating that he can't reproduce the issue and that it is more of a WSUS-related issue than a CM12 issue. Any ideas? Thanks. -ben
