Today I tried the .config workaround.
Since my servers were already at .Net 2.0.50727 I didn't have to apply to hotfix.
Went to BIN or CLIENTACCESS directory and altered all Exchange related config files:
BinEdgeTransport.exe.config
BinExBPA.exe.config
BinExBPACmd.exe.config
BinExTRA.exe.config
BinMicrosoft.Exchange.Cluster.ReplayService.exe.config
BinMicrosoft.Exchange.EdgeSyncSvc.exe.config
BinMicrosoft.Exchange.Monitoring.exe.config
BinMicrosoft.Exchange.Search.ExSearch.exe.config
BinMicrosoft.Exchange.ServiceHost.exe.config
BinMSExchangeMailboxAssistants.exe.config
BinMSExchangeMailSubmission.exe.config
BinMSExchangeTransportLogSearch.exe.config
ClientAccessPopImapMicrosoft.Exchange.Imap4.Exe.config
ClientAccessPopImapMicrosoft.Exchange.Pop3.Exe.config
Where necessary I created the additional config files:
BinMicrosoft.Exchange.AntispamUpdateSvc.exe.config
BinMsExchangeFDS.exe.config
BinMSExchangeTransport.exe.config
Added
<generatePublisherEvidence enabled="false"/>
to each .config file
OR if the files did not exist, created these files with following content
<configuration>
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
</configuration>
Typically a .config file has to be changed or created for each installed Exchange 2007 Service.
Thanks for the tip!! I'm happy it worked!!
Hopefully the next update or rollup will fix this...