Which is strange as I was applying Internet Explorer 8 security patch MS11-081, on Windows XP.

Strange because the OCInstall function was first introduced with Windows 2000 SP3/SP4.  Strange also that a Microsoft security patch was triggering it.  But it gets stranger still.

My *guess* is that because the customer wanted to go the cheap route and in-place upgrade Windows 2000 to Windows XP, that it’s caused this strange error.

The extra strangeness?  It fails when we install via SMS 2003, but if I log on as an Admin and manually run it, it works.  No, I don’t know why.

Related posts:

Bypassing Internet Explorer Group Policy lockdowns. Two SMS 2003 servers, one returns different data format for same query. So you’re missing the MSI source package

Powered by YARPP.