CardSpace is actually a NET Framework 3.0 component, if you uninstall this from the server the errors should cease, as it is also not supported on the Enterprise Vault servers either currently at this time.
As for the DCOM errors, DCOM Errors typically tend to come from when an application on a server is attempting to start something that has not been fully initialized yet.
In the majority of cases it is due to the Admin Service starting up, and when it starts up it trying to connect to the Directory Service, but may take 2 or 3 attempts connecting before the Directory Service has started up correctly, each of those failed connections will generate a DCOM.
Same as if you stopped a service such as Directory or Storage where another computer is trying to create that DCOM object, but it can't because the service is not running.
A couple of things about this error is that this is usually benign and no changes to the DCOM packages need be made.
We are looking to address this in a later service pack, however it would just lessen the amount of DCOM errors, there is nothing we can do to stop them completely as these are regular DCOM errors that you may see in other apps that have services that aren't up 100% of the time (ie restarting for backups etc)
