Hello, A server SOTFCSSQL1 has been renamed to SOPFCSRS1 and now I have an error: Log Name: System Source: Microsoft-Windows-DistributedCOM Date: 2/11/2011 12:40:00 PM Event ID: 10009 Task Category: None Level: Error Keywords: Classic User: N/A Computer: SOPFCSRS1.ad Description: DCOM was unable to communicate with the computer SOTFCSSQL1.ad using any of the configured protocols. It is still trying to access the old computer renamed three weeks ago... This is used by Microsoft Forefront Client Security, I have the error every 30 minutes...and I think it is the issue for the task SystemCenterDTSPackageTask to fail to populate the dashboard on the other server. How to clean this? I found this but not sure if it will fit for this issue: Reinstall COM+ and reset the DCOM permissions. Its a simple process. Open a command prompt Type ren %WinDir%System32Clbcatq.dll %WinDir%System32~Clbcatq.dll Reboot the computer Open regedit Delete the following key: HKEY_LOCAL_MACHINESOFTWAREMicrosoftCOM3 Open a command prompt Type cd %windir% Type rmdir /s Registration Open Control Panel Open Add/Remove Programs and then click on Add/Remove Windows Components Simply click next to start the reinstall. You may need your Windows CD. If you have IIS installed, run the following command: rundll32 %windir%system32inetsrvwamreg.dll, CreateIISPackage Reboot the computer Thanks, Dom System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Think I'd ask them here. http://social.technet.microsoft.com/Forums/en/category/forefront Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]

I tried already this one but it did not work http://social.technet.microsoft.com/Forums/en/Forefrontclientsetup/thread/975fee29-cf1e-4398-a7b3-ab79743bf9e2 I asked also http://social.technet.microsoft.com/Forums/en/Forefrontclientgeneral/thread/73f63f66-e39a-482e-9392-6f0f0d2e4b62 but nothing working so far System Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager

Then I'll take a stab at this. I know nothing of the Forefront stuff but the error is not specifically a DCOM problem. The software was configured to use DCOM to communicate with server by name and as you suspected results are from the name change. Seems like the fix will be to reconfigure the Forefront app or possibly some sort of repair installation of Forefront. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows]

I will give a try Thanks, DOmSystem Center Operations Manager 2007 / System Center Configuration Manager 2007 R2 / Forefront Client Security / Forefront Identity Manager