There is currently no supported way to remove the last public folder database 
from an Exchange organization except via version migration.

I recommend two full replicas because recovery databases can only be mailbox 
databases. That is, the recovery implementation does not support public folder 
databases. Therefore, if you need to recover a PF DB, you have to build not 
only a recovery SERVER but a full recovery FOREST in order to do so.

With CSS/PSS you should always be able to request an escalation after 24 hours. 
But you have to request it. And be firm.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com


-----Original Message-----
From: Crawford, Scott [mailto:crawfo...@evangel.edu] 
Sent: Monday, July 25, 2011 10:27 PM
To: NT System Admin Issues
Subject: RE: Exchange 2010 System Public Folders

Thanks.  How 'bout after I'm done with all PFs?

If I were to build a new Exchange 2010 box (unlikely) and not install a PF on 
it?

> Hopefully, you have at least two complete sets of replicas.
How come? I only have one server (2010) so only one set of replicas.

> I think that your goal is likely to cause more trouble than benefit it 
> provides.
Probably :), but I like cleaning up unneeded stuff when I can. I'm not a big 
fan of extra cruft that I'm too scared to touch because by definition, it's 
something in my environment that I don't understand, and I like to understand 
things :)

> I'd raise a case with CSS/PSS if you really want to do this.
Maybe at the end of the year if I still have one of my two free cases left. 
But, frankly, dealing MS support lately has become more frustrating than it's 
worth. I've got a case open right now that's been open for weeks and we're just 
going round in circles explaining the problem, being assured they understand it 
and will call me back with a solution, only to have me re-explain the problem.  
Do you have any tricks for getting escalated to US based support quickly?

-----Original Message-----
From: Michael B. Smith [mailto:mich...@smithcons.com] 
Sent: Monday, July 25, 2011 7:03 PM
To: NT System Admin Issues
Subject: RE: Exchange 2010 System Public Folders

You can't eliminate the last replica of system folders in your organization, if 
you've create a PF DB on the highest version Exchange in the organization.

To say that another way, if you migrate from Exchange 2003 to Exchange 2010, 
and you create a PF DB on Exchange 2010, you must keep a replica of the system 
folders in the organization.

Hopefully, you have at least two complete sets of replicas.

I think that your goal is likely to cause more trouble than benefit it provides.

I'd raise a case with CSS/PSS if you really want to do this.

Regards,

Michael B. Smith
Consultant and Exchange MVP
http://TheEssentialExchange.com

-----Original Message-----
From: Crawford, Scott [mailto:crawfo...@evangel.edu]
Sent: Monday, July 25, 2011 6:41 PM
To: NT System Admin Issues
Subject: RE: Exchange 2010 System Public Folders

True, but cleaning unneeded stuff now prevents having to figure out which is 
which if there ever is a crisis down the line.  Kinda like reducing your attack 
surface; I'd rather have fewer things that can use up system resources.

-----Original Message-----
From: Joseph Heaton [mailto:jhea...@dfg.ca.gov]
Sent: Monday, July 25, 2011 5:07 PM
To: NT System Admin Issues
Subject: RE: Exchange 2010 System Public Folders

hmmm, if it ain't broke, don't fix it?

>>> Brian Desmond <br...@briandesmond.com> 7/25/2011 3:00 PM >>>
No they're probably not, but, they're probably also not causing you any 
problems.

Thanks,
Brian Desmond
br...@briandesmond.com<mailto:br...@briandesmond.com>

c   - 312.731.3132

From: Crawford, Scott [mailto:crawfo...@evangel.edu]
Sent: Monday, July 25, 2011 4:04 PM
To: NT System Admin Issues
Subject: RE: Exchange 2010 System Public Folders

Well, I'm pretty sure I've got some extras from old servers and I was setting 
out to clean up the old ones. For instance I have 5 OWAScratchPad and 5 
StoreEvents. But, when I tried to determine which ones were active, I found 
that neither of my database GUIDs matched the GUIDs on the names of the public 
folders, which leads me to believe they're not needed at all.

From: Brian Desmond 
[mailto:br...@briandesmond.com]<mailto:[mailto:br...@briandesmond.com]>
Sent: Monday, July 25, 2011 3:59 PM
To: NT System Admin Issues
Subject: RE: Exchange 2010 System Public Folders

I don't expect that it's possible to have normal folders without the system 
ones. I would leave it alone.

Thanks,
Brian Desmond
br...@briandesmond.com<mailto:br...@briandesmond.com>

c   - 312.731.3132

From: Crawford, Scott 
[mailto:crawfo...@evangel.edu]<mailto:[mailto:crawfo...@evangel.edu]>
Sent: Monday, July 25, 2011 3:54 PM
To: NT System Admin Issues
Subject: Exchange 2010 System Public Folders

Now that we're 100% Outlook 2007/2010 and Exhchange 2010, is there any reason I 
shouldn't delete the System Public Folders? I still have other public folders, 
so I don't want to remove all public folders yet.

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to 
listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com>
with the body: unsubscribe ntsysadmin

~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin



~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ 
<http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

---
To manage subscriptions click here: 
http://lyris.sunbelt-software.com/read/my_forums/
or send an email to listmana...@lyris.sunbeltsoftware.com
with the body: unsubscribe ntsysadmin

Reply via email to