I'm pulling my hair out... I've been trying to install this role for 3 days now on a new W2K8R2 server. I pulled updates for the OS from the existing WSUS server so the computer is at current patch level and tried installing the role and the install always fails at "Configuring the database". WID appears to install fine but when the configuration scripts are running through, the log shows they appear to work fine all the way up through the last, "Signing object:...", it creates the logins and gets to Updating [dbo].[tbSchedule] and there are dozens to hundreds of entries claiming that, "Access to table dbo.<insert_table_name> is blocked because the signature is not valid." I've tried dozens of variations of uninstall WID after the rollback of the WSUS completes, delete SYSMSI\*, delete registry entries, reboot. There are dozens of articles on the web of people describing this same problem (mostly related to SharePoint) with the fix seeming to be to run:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin\psconfig -cmd upgrade -inplace b2b
But that apparently doesn't exist in a base build of W2K8R2 or after the failed install of WSUS. I've verified that the computer cert is functional and the signing authority is in the Trusted Root Store.
If the above command is a definite fix outside of SharePoint, does anyone know if I can run that binary without SharePoint being installed? If so, what do I need to install? The SharePoint Admin tools?
If you're aware of an actual fix for this problem, I'd greatly appreciate the assistance.