Hello,I'm trying to run the Exchange Troubleshooting Assistant on an E2K7 SP2 CCR cluster and I am unable to.I get the error \\exchangecluster\c$\Perflogs "The Network Name cannot be found"I am able to map a drive to \\exchangecluster however I cannot map to a share.Is there a way I can run the ExTra on a cluster?Thanks,J.Jack

on the advance options under data directory use the IP address of CMS as \\192.168.1.100\PerfLogs assuming ----->192.168.1.100 ( CMS IP address)Perflogs is shared directory, if not you need to do this \\192.168.1.100\c$\Perflogs ( assuming perflogs is in the C directory of the Exchange Server , if you want to place the folder , change the drive letter accordingly.... 1.Click on Hide advance data collections options 2.Go to Data Directory on the server 3.Use IP address instead of NetBIOS name or FQDN as \\IPAresssOfCMS\C$\PerfLogs , verify this is working from RUN command window , as far as I understand from your post ----> this is faling\\exchangecluster\c$\Perflogs----->\\X.X.X.X\c$\Perflogs this should work (-: ( X.X.X.X is your CMS IP address)good luck,ocd

FYI I too have the same issue, but this seems to be something specific with Windows 2008. I support a client environment where Exchange 2007 is on a Windows 2003 cluster and I don't have issues with Performance Troubleshooter. Under the Data directory on the server path, I've tried using \\<CMS-IP-Address>\perflogs. I've also tried to use \\<CMS-IP-Address>\C$\perflogs. Shared permissions seem to be OK to me. The Everyone group has Full Control. I can connect to the share using the CMS IP Address from another workstation. Any other ideas?

I am also having this issue. If you try to use \\XXX.XXX.XXX.XXX\c$\perflogs, you just get "Failed to find directory \\servername\c$\XXX.XXX.XXX.XXX\c$\perflogs" If you try to use the cluster node name, it doesn't detect it as a Mailbox server. Hitting Browse and trying to find the mailbox server doesn't seem to work at all either. I get the first 100 computers in my environment alaphabetically, mailbox server is not on the list. Is there some sort of workaround? This is extremely frustrating.

I tried via CMS name and the actual node name followed by c$ but nothing works. This happens only in Windows server 2008. On 64bit server 2003, I dont have this problem.