This is really weird. Installed Exchange 2007, it works fine. Installed Virtual Server, it works fine. But the Event Logs are cross-linked. Exchangeevents destined for the application log get duplicated in the Virtual Server log and some Virtual Server Events destined for the Virtual Server log get duplicated in the application log. The events that are in the wrong logs dont get decoded by Event Viewer because there is no decode resource definition for these sources. Have checked the log file name and sources registry entries for each log and they appear normal, as do the sub keys for each source. Almost looks like a bug in the Event Log service. Anyone else seen this or know how to fix it? Also the business of having separate Windows Power Shell and Power Shell logs seems odd. What is that all about? While we're at it, a small request for SP1: Can you please put all exchange server events in an application specific log. It is slightly ridiculous cranking so many informational events into the generic application log.

Update: Interlude while VMWare's freebie offering looked at and rejected (too slow),Uninstalling VS, rebooting then re-installing eventually fixed the problem.Simply uninstalling and re-installing without reboot did not get rid of the problem. However, after good reinstall Admin account could no longer use Exchange admin GUI, complaining that it couldn't find the Exchange server (there is only one box and everthing else AD related worked including Exchange itself). A clone of the Admin account had no such problems so resorted to standard Exchange 2K7 fix-all stunt: Delete the Admin account's profile Reboot machine (just logging back on as Admin recreating profile doesn't do the trick). That brought the console back to life OK. VS is nowputting some Events into the system log, which appears to be its normal behaviour for virtual network related events though again there is no decode resource registered for these events. The dying Exchange console again points to something related to RPC failure thatisuser profile, possible securityor.NET framework related (since non-framework stuff still works fine) - allas happens with the install problemwhere setup can'tfind Active Directory. There is definitely abug here somewhere but it's hard to pin down. Phew! At last I have something reasonably stable I can do development against.