Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1662
  • Last Modified:

public folders in exchange 2013

I just migrated from exchange 2007 to 2013. I never received any emails from exchange saying that my public folders are becoming too large.

Now, with exchange 2013, I keep on getting emails from exchange saying "your public folder is becoming too large"
Then in the email body, this is what it says:

Your public folder "\Media\Aim Reports\Station Summary" is becoming too large. The current size is 57 MB.
Please reduce the size of your public folder by deleting any items you don't need.


Why is this happening?  I never set quotas on public folders....

Any advise how to fix this?
0
afacts
Asked:
afacts
4 Solutions
 
Gregory MillerGeneral ManagerCommented:
Try this PowerShell command to turn it off:
Set-PublicFolder -Identity "\My Public Folder" -UseDatabaseQuotaDefaults: $False

Open in new window

0
 
Marshal HubsEmail ConsultantCommented:
A solution to your problem is given in this article : http://searchexchange.techtarget.com/tip/Set-storage-limits-for-Exchange-public-folders . Just go through this article and then follow the steps given to resolve your problem.
0
 
afactsNetwork EngineerAuthor Commented:
Marshal hubs, that article is for exchange 2003.  I have 2013.

My total size of public folders is only 2.8 gb.
For the total size.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
afactsNetwork EngineerAuthor Commented:
Technodweeb,

Where it says \my public folders,   Do I just put the name of my root folder of my public folders?   I believe the name is public folders, so I just substitute that in there, and will it work for the root, which should propagate to every other sub public folder, right?
0
 
Simon Butler (Sembee)ConsultantCommented:
"My total size of public folders is only 2.8 gb."

This is probably the reason for the prompt.
Remember that public folder behaviour in Exchange 2013 has changed. They are no longer stored in their own database, but with the mailboxes in a special public folder mailbox.
By default, the mailbox size is 2gb, hence the alert.
You will need to remove the limit on the public folder mailbox to stop the warning message.

Simon.
0
 
afactsNetwork EngineerAuthor Commented:
Well, in looking via the ECP at my public folders, it's already set to "unlimited", so why is it still sending out emails that we're low on space?

I've attached the picture.
pfusage.jpg
0
 
afactsNetwork EngineerAuthor Commented:
Technodweeb,

When I ran that command, I get this error message:
"A parameter cannot be found that matches parameter name 'UseDatabaseQuotaDefaults'"

I just copied and pastes your command and only changed the name of my public folders, which is "\Public Folders"

Any thoughts?
0
 
Simon Butler (Sembee)ConsultantCommented:
That is because that is a command for Exchange 2010/2007 public folders. It doesn't apply to Exchange 2013.

Simon.
0
 
afactsNetwork EngineerAuthor Commented:
So what do I do for exchagne 2013, as that's what I'm running now?
0
 
Simon Butler (Sembee)ConsultantCommented:
I told you what I suspected it was above - the size of the public folder mailbox.

Simon.
0
 
afactsNetwork EngineerAuthor Commented:
So how exactly do I increase the size of the public folder mailbox.  The ECP is not that good at managing public folders.  2003 was great, everything was done via the gui, there's no all of these commands you have to learn.

I think the total size of the public folders is 2.8GB, but the size is set to 15 GB I believe.
0
 
afactsNetwork EngineerAuthor Commented:
I tried finding what the folder size limits are via the GUI, and I don't see it anywhere. This is so frustrating to have some settings via the ECP and some via the powershell.
0
 
Simon Butler (Sembee)ConsultantCommented:
Better get used to the command line - as that is how all Microsoft products are going. Command line first, GUI second. Everything can be done in the command line and it is a lot more efficient way of doing things. I configured a 12 server installation last week in less than 15 minutes using the command line, if I had to use the GUI it would have taken me hours.

The first thing you should do is check the limit of the Mailbox itself.
You can do that with the GUI if you wish - under Public Folders, Public Folder Mailboxes. Double click on the mailbox and then select Mailbox Usage.

The limits for each public folder are on the properties of the folder, under limits.

Simon.
0
 
afactsNetwork EngineerAuthor Commented:
Simon,  Thanks for the reply.

I have attached the picture with my settings.  Everything was already set to "unlimited", but the mailbox still shows that I'm using 1.6Gb of 2GB, I don't understand that, because if it's set to unlimited, what doesn't it understand of unlimited?

I guess I'm not sure where else there might be settings that I need to change?

I agree with you that powershell is very powerful and that you can probably do things much faster, but I guess I'm just to busy to learn a new language, I'm the only admin managing my entire organization and up til now, I guess I've been telling myself I don't have time to learn a new language, but perhaps somewhere, I should carve time and learn it.
My next question is, how would you recommend that someone that knows almost NOTHING about powershell learn it?  What's the easiest way for me to learn it? Do I just buy a book and read through the book, are there any very good websites that I can learn it?

I still have 3 major problems from this migration and I guess that's what still frustrating me with this exchange 2013, as I had very few issues when I upgraded to ex 2007.

Not sure if you know the following as well, or if I should make a new post:
1. All my remote users, whether win xp or win 7, it just continuously prompts them for their user/pass.  I have verified that they are entering the correct information and that their accounts are not locked, as they can access the web outlook app.  With one user, I even uninstalled office, and installed office 2013 from scratch, and it's still prompting him, internally, I actually had this user bring in their laptop, and on my LAN, and it's still doing this.

2. Internally, I have some users, win 7, outlook 2010, with all the required updates, where email will not send, just stays in outbox.  I deleted the .ost file, and that solved it for a few hours, or a day, but the problem comes right back.  I'm lost as how to solve this issue as well.

Thanks,
Dan
PF.JPG
0
 
Simon Butler (Sembee)ConsultantCommented:
Username/password prompts are very common. If you search this site and others for that problem you will easily find the most common solutions. Usually it is an SSL certificate issue - nothing to do with the username/password, as Outlook cannot cope with the SSL prompts if there is an SSL issue.

For the other problem about messages staying in the outbox, I would suggest a new question.

As for the public folder size, that may well be a bug. SP1 is due shortly, so you should probably deploy that. Another option would be to set a specific limit rather than unlimited. That will have to be done via the shell, perhaps set it to 4gb.

Simon.
0
 
afactsNetwork EngineerAuthor Commented:
Can anyone modify the above command to also include what the total storage limit is?
The code that Technodweeb attached above.

That would really help me  a lot, because then I would know which accounts are affected.
0
 
afactsNetwork EngineerAuthor Commented:
thanks guys for your help, I called a friend and helped me get it going.
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now