Well that looks like it will require a new name and IP to create on a existing CCR cluster. So now I guess the question is how do you get the Troubleshooting Assistant to work on a CCR cluster if that is not configured? It only uses the exchange cluster server name.
-----Original Message----- From: Tom Kern [mailto:tpk...@gmail.com] Sent: Thursday, August 20, 2009 1:27 PM To: MS-Exchange Admin Issues Subject: Re: W2K8, E2K7, CCR, admin shares issue it means you either have to use the local node name or run Enable-ContinuousReplicationHostName for the replication service to pragmatically create the share scoped to the CMS name On Thu, Aug 20, 2009 at 12:28 PM, Senter, John<john.sen...@etrade.com> wrote: > Am I missing something in that article because I do not see a way to get > around that. I cannot run the Troubleshooting tools for my CCR servers as it > wants to use the UNC name \\Exchserver\c$\Perflogs. The only options I have > is to use the local drive letter. > > -----Original Message----- > From: Tom Kern [mailto:tpk...@gmail.com] > Sent: Thursday, August 20, 2009 11:48 AM > To: MS-Exchange Admin Issues > Subject: Re: W2K8, E2K7, CCR, admin shares issue > > File share scoping feature in Win2k8 > > http://blogs.technet.com/timmcmic/archive/2008/12/23/exchange-replication-service-exchange-2007-sp1-and-windows-2008-clusters.aspx > > > On Thu, Aug 20, 2009 at 11:33 AM, Senter, John<john.sen...@etrade.com> wrote: >> I have a issue with accessing the admin shares on a Windows 2008 server, >> Exchange 2007 SP1 RU8, doing CCR. I can access the admin shares (C$, D$, >> etc) if I user the physical server name or the cluster IP, but if I use the >> Exchange cluster name or CMS cluster name I get path not found. I found >> this out while trying to run the Exchange 2007 Performance Troubleshooter >> and it failed to access \\exchangeservername\C$\Perflogs, then I tried all >> the drive$ shares and they failed. I have disabled IPv6 in the registry as >> outlined by the MS article. The exchange cluster name validates correctly >> in DNS. >> >> Any ideas? >> > > > > >
