Exchange 2007 CCR into existing Exchange 2000 Org - Public Folders   

As the Subject states, this question is specifically for a new CCR 
installation ino an Existing Exchange 2000 Organization, and Public 
Folder-related errors.

I have read several KB articles and posts regarding some of the limitations 
of running CCR and Public Folders (can only have 1 PF database, PF's are 
limited to their own replication technology, etc.) but am still unclear on 
what a supported installation process should look like. Although the 2007 
servers are being installed into the production environment, they will not 
actually be utilized for production for several months.

The Org I'm installing into has 3 Back-End 2000 Servers, each with their own 
copy of the PF database. If I understand this correctly, that means that the 
CCR CLuster cannot host it's own copy. However, the Exchange 2007 CCR 
installation tries to create it's own copy of the 'Second Storage Group' by 
default. Inevitably, this causes a failure on the installation, because this 
resource cannot be brought online. This First Storage Group seems to operate 
fine.

Is there a way to prevent the PF database to be part of the install? If the 
Second Storage Group is removed from CCR after installation,  will this 
accomplih the same thing?

date: Tue, 18 Dec 2007 07:14:01 -0800   author:   Jorge Azcuy

Re: Exchange 2007 CCR into existing Exchange 2000 Org - Public Folders   

Simply put, if you have other servers with PFs, you shouldn't have a PF 
Store on your CCR CMS. If you do, it shouldn't use PF replication. If you do 
use replication, it will be supported during the "migration phase".

Worst case: The PF Store on the CMS may not mount.

For supportability, unless the CMS is the only mailbox server in the Org, I 
would stay away from hosting PFs on it.
-- 
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"Jorge Azcuy"  wrote in message 
news:EDEC9112-A5ED-407F-A3C4-E97F5F837AEC@microsoft.com...
> As the Subject states, this question is specifically for a new CCR
> installation ino an Existing Exchange 2000 Organization, and Public
> Folder-related errors.
>
> I have read several KB articles and posts regarding some of the 
> limitations
> of running CCR and Public Folders (can only have 1 PF database, PF's are
> limited to their own replication technology, etc.) but am still unclear on
> what a supported installation process should look like. Although the 2007
> servers are being installed into the production environment, they will not
> actually be utilized for production for several months.
>
> The Org I'm installing into has 3 Back-End 2000 Servers, each with their 
> own
> copy of the PF database. If I understand this correctly, that means that 
> the
> CCR CLuster cannot host it's own copy. However, the Exchange 2007 CCR
> installation tries to create it's own copy of the 'Second Storage Group' 
> by
> default. Inevitably, this causes a failure on the installation, because 
> this
> resource cannot be brought online. This First Storage Group seems to 
> operate
> fine.
>
> Is there a way to prevent the PF database to be part of the install? If 
> the
> Second Storage Group is removed from CCR after installation,  will this
> accomplih the same thing?

date: Tue, 18 Dec 2007 09:56:26 -0800   author:   Bharat Suneja [MVP]

Re: Exchange 2007 CCR into existing Exchange 2000 Org - Public Fol   

So does this mean that leaving the PF store unmounted or simply deleting it 
will nt affect other functionality?

"Bharat Suneja [MVP]" wrote:

> Simply put, if you have other servers with PFs, you shouldn't have a PF 
> Store on your CCR CMS. If you do, it shouldn't use PF replication. If you do 
> use replication, it will be supported during the "migration phase".
> 
> Worst case: The PF Store on the CMS may not mount.
> 
> For supportability, unless the CMS is the only mailbox server in the Org, I 
> would stay away from hosting PFs on it.
> -- 
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> exchangepedia.com/blog
> ----------------------------------------------
> 
> 
> "Jorge Azcuy"  wrote in message 
> news:EDEC9112-A5ED-407F-A3C4-E97F5F837AEC@microsoft.com...
> > As the Subject states, this question is specifically for a new CCR
> > installation ino an Existing Exchange 2000 Organization, and Public
> > Folder-related errors.
> >
> > I have read several KB articles and posts regarding some of the 
> > limitations
> > of running CCR and Public Folders (can only have 1 PF database, PF's are
> > limited to their own replication technology, etc.) but am still unclear on
> > what a supported installation process should look like. Although the 2007
> > servers are being installed into the production environment, they will not
> > actually be utilized for production for several months.
> >
> > The Org I'm installing into has 3 Back-End 2000 Servers, each with their 
> > own
> > copy of the PF database. If I understand this correctly, that means that 
> > the
> > CCR CLuster cannot host it's own copy. However, the Exchange 2007 CCR
> > installation tries to create it's own copy of the 'Second Storage Group' 
> > by
> > default. Inevitably, this causes a failure on the installation, because 
> > this
> > resource cannot be brought online. This First Storage Group seems to 
> > operate
> > fine.
> >
> > Is there a way to prevent the PF database to be part of the install? If 
> > the
> > Second Storage Group is removed from CCR after installation,  will this
> > accomplih the same thing? 
> 
> 
>

date: Tue, 18 Dec 2007 10:04:03 -0800   author:   Jorge Azcuy

Re: Exchange 2007 CCR into existing Exchange 2000 Org - Public Fol   

No PF Store is created/exists by default, so there's noting to 
delete/unmount.

-- 
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"Jorge Azcuy"  wrote in message 
news:DB16CE96-0B01-41AA-ABFF-10C73E1FE29D@microsoft.com...
> So does this mean that leaving the PF store unmounted or simply deleting 
> it
> will nt affect other functionality?
>
> "Bharat Suneja [MVP]" wrote:
>
>> Simply put, if you have other servers with PFs, you shouldn't have a PF
>> Store on your CCR CMS. If you do, it shouldn't use PF replication. If you 
>> do
>> use replication, it will be supported during the "migration phase".
>>
>> Worst case: The PF Store on the CMS may not mount.
>>
>> For supportability, unless the CMS is the only mailbox server in the Org, 
>> I
>> would stay away from hosting PFs on it.
>> -- 
>> Bharat Suneja
>> MVP - Exchange
>> www.zenprise.com
>> NEW blog location:
>> exchangepedia.com/blog
>> ----------------------------------------------
>>
>>
>> "Jorge Azcuy"  wrote in message
>> news:EDEC9112-A5ED-407F-A3C4-E97F5F837AEC@microsoft.com...
>> > As the Subject states, this question is specifically for a new CCR
>> > installation ino an Existing Exchange 2000 Organization, and Public
>> > Folder-related errors.
>> >
>> > I have read several KB articles and posts regarding some of the
>> > limitations
>> > of running CCR and Public Folders (can only have 1 PF database, PF's 
>> > are
>> > limited to their own replication technology, etc.) but am still unclear 
>> > on
>> > what a supported installation process should look like. Although the 
>> > 2007
>> > servers are being installed into the production environment, they will 
>> > not
>> > actually be utilized for production for several months.
>> >
>> > The Org I'm installing into has 3 Back-End 2000 Servers, each with 
>> > their
>> > own
>> > copy of the PF database. If I understand this correctly, that means 
>> > that
>> > the
>> > CCR CLuster cannot host it's own copy. However, the Exchange 2007 CCR
>> > installation tries to create it's own copy of the 'Second Storage 
>> > Group'
>> > by
>> > default. Inevitably, this causes a failure on the installation, because
>> > this
>> > resource cannot be brought online. This First Storage Group seems to
>> > operate
>> > fine.
>> >
>> > Is there a way to prevent the PF database to be part of the install? If
>> > the
>> > Second Storage Group is removed from CCR after installation,  will this
>> > accomplih the same thing?
>>
>>
>>

date: Tue, 18 Dec 2007 10:36:41 -0800   author:   Bharat Suneja [MVP]

Re: Exchange 2007 CCR into existing Exchange 2000 Org - Public Fol   

I understand - but right now I have the Second Storage Group created, byt 
default, as a cluster resource that is in a failed state. What I'm asking is 
if it's OK to leave it like this? Will this affect other functionality?

Thanks

"Bharat Suneja [MVP]" wrote:

> No PF Store is created/exists by default, so there's noting to 
> delete/unmount.
> 
> -- 
> Bharat Suneja
> MVP - Exchange
> www.zenprise.com
> NEW blog location:
> exchangepedia.com/blog
> ----------------------------------------------
> 
> 
> "Jorge Azcuy"  wrote in message 
> news:DB16CE96-0B01-41AA-ABFF-10C73E1FE29D@microsoft.com...
> > So does this mean that leaving the PF store unmounted or simply deleting 
> > it
> > will nt affect other functionality?
> >
> > "Bharat Suneja [MVP]" wrote:
> >
> >> Simply put, if you have other servers with PFs, you shouldn't have a PF
> >> Store on your CCR CMS. If you do, it shouldn't use PF replication. If you 
> >> do
> >> use replication, it will be supported during the "migration phase".
> >>
> >> Worst case: The PF Store on the CMS may not mount.
> >>
> >> For supportability, unless the CMS is the only mailbox server in the Org, 
> >> I
> >> would stay away from hosting PFs on it.
> >> -- 
> >> Bharat Suneja
> >> MVP - Exchange
> >> www.zenprise.com
> >> NEW blog location:
> >> exchangepedia.com/blog
> >> ----------------------------------------------
> >>
> >>
> >> "Jorge Azcuy"  wrote in message
> >> news:EDEC9112-A5ED-407F-A3C4-E97F5F837AEC@microsoft.com...
> >> > As the Subject states, this question is specifically for a new CCR
> >> > installation ino an Existing Exchange 2000 Organization, and Public
> >> > Folder-related errors.
> >> >
> >> > I have read several KB articles and posts regarding some of the
> >> > limitations
> >> > of running CCR and Public Folders (can only have 1 PF database, PF's 
> >> > are
> >> > limited to their own replication technology, etc.) but am still unclear 
> >> > on
> >> > what a supported installation process should look like. Although the 
> >> > 2007
> >> > servers are being installed into the production environment, they will 
> >> > not
> >> > actually be utilized for production for several months.
> >> >
> >> > The Org I'm installing into has 3 Back-End 2000 Servers, each with 
> >> > their
> >> > own
> >> > copy of the PF database. If I understand this correctly, that means 
> >> > that
> >> > the
> >> > CCR CLuster cannot host it's own copy. However, the Exchange 2007 CCR
> >> > installation tries to create it's own copy of the 'Second Storage 
> >> > Group'
> >> > by
> >> > default. Inevitably, this causes a failure on the installation, because
> >> > this
> >> > resource cannot be brought online. This First Storage Group seems to
> >> > operate
> >> > fine.
> >> >
> >> > Is there a way to prevent the PF database to be part of the install? If
> >> > the
> >> > Second Storage Group is removed from CCR after installation,  will this
> >> > accomplih the same thing?
> >>
> >>
> >> 
> 
> 
>

date: Tue, 18 Dec 2007 10:57:02 -0800   author:   Jorge Azcuy

Re: Exchange 2007 CCR into existing Exchange 2000 Org - Public Fol   

No, it won't affect anything. Alternatively, you can simply remove it.

-- 
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------


"Jorge Azcuy"  wrote in message 
news:1F4CF73F-FD0E-4BBB-B833-E2955B91FFE4@microsoft.com...
>I understand - but right now I have the Second Storage Group created, byt
> default, as a cluster resource that is in a failed state. What I'm asking 
> is
> if it's OK to leave it like this? Will this affect other functionality?
>
> Thanks
>
> "Bharat Suneja [MVP]" wrote:
>
>> No PF Store is created/exists by default, so there's noting to
>> delete/unmount.
>>
>> -- 
>> Bharat Suneja
>> MVP - Exchange
>> www.zenprise.com
>> NEW blog location:
>> exchangepedia.com/blog
>> ----------------------------------------------
>>
>>
>> "Jorge Azcuy"  wrote in message
>> news:DB16CE96-0B01-41AA-ABFF-10C73E1FE29D@microsoft.com...
>> > So does this mean that leaving the PF store unmounted or simply 
>> > deleting
>> > it
>> > will nt affect other functionality?
>> >
>> > "Bharat Suneja [MVP]" wrote:
>> >
>> >> Simply put, if you have other servers with PFs, you shouldn't have a 
>> >> PF
>> >> Store on your CCR CMS. If you do, it shouldn't use PF replication. If 
>> >> you
>> >> do
>> >> use replication, it will be supported during the "migration phase".
>> >>
>> >> Worst case: The PF Store on the CMS may not mount.
>> >>
>> >> For supportability, unless the CMS is the only mailbox server in the 
>> >> Org,
>> >> I
>> >> would stay away from hosting PFs on it.
>> >> -- 
>> >> Bharat Suneja
>> >> MVP - Exchange
>> >> www.zenprise.com
>> >> NEW blog location:
>> >> exchangepedia.com/blog
>> >> ----------------------------------------------
>> >>
>> >>
>> >> "Jorge Azcuy"  wrote in message
>> >> news:EDEC9112-A5ED-407F-A3C4-E97F5F837AEC@microsoft.com...
>> >> > As the Subject states, this question is specifically for a new CCR
>> >> > installation ino an Existing Exchange 2000 Organization, and Public
>> >> > Folder-related errors.
>> >> >
>> >> > I have read several KB articles and posts regarding some of the
>> >> > limitations
>> >> > of running CCR and Public Folders (can only have 1 PF database, PF's
>> >> > are
>> >> > limited to their own replication technology, etc.) but am still 
>> >> > unclear
>> >> > on
>> >> > what a supported installation process should look like. Although the
>> >> > 2007
>> >> > servers are being installed into the production environment, they 
>> >> > will
>> >> > not
>> >> > actually be utilized for production for several months.
>> >> >
>> >> > The Org I'm installing into has 3 Back-End 2000 Servers, each with
>> >> > their
>> >> > own
>> >> > copy of the PF database. If I understand this correctly, that means
>> >> > that
>> >> > the
>> >> > CCR CLuster cannot host it's own copy. However, the Exchange 2007 
>> >> > CCR
>> >> > installation tries to create it's own copy of the 'Second Storage
>> >> > Group'
>> >> > by
>> >> > default. Inevitably, this causes a failure on the installation, 
>> >> > because
>> >> > this
>> >> > resource cannot be brought online. This First Storage Group seems to
>> >> > operate
>> >> > fine.
>> >> >
>> >> > Is there a way to prevent the PF database to be part of the install? 
>> >> > If
>> >> > the
>> >> > Second Storage Group is removed from CCR after installation,  will 
>> >> > this
>> >> > accomplih the same thing?
>> >>
>> >>
>> >>
>>
>>
>>

date: Tue, 18 Dec 2007 14:46:07 -0800   author:   Bharat Suneja [MVP]