Exchange 2013 - change user mailbox size to over 2GB

Estimates
They know how to set the mailbox size of a user to over 2GB in Exchange Server 2013
the console does not display alternatives, Please urgent thank you
saludos

Hi
Here you go
Set-Mailbox -Identity "Ayla Kol" -IssueWarningQuota 900mb -ProhibitSendQuota 950mb -ProhibitSendReceiveQuota 1gb -UseDatabaseQuotaDefaults $false
http://technet.microsoft.com/en-us/library/aa998353(v=exchg.150).aspx
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

Similar Messages

User mailbox size

Hi,
Im using XCH 07 with single mailbox database, total users around 50 users. i have one user with large mailbox size, and different between mailbox and outlook. at mailbox, it's 15gb meanwhile at outlook is only 4gb, change between cached and online mode not
help. this cause i got warning on exchange server with online maintenance termination with default maintenance schedule (1am-5am) and database size also increasing as that user mailbox size increasing. test with custom longer maintenance scehdule also not
help, still got termination due to overlapping (xch backup exclude when use custom scheudle). appreciate is anyone ever got this problem may share the solution. thanks
manggar77

Hi,
To get the size of a mailbox, we can use the Get-MailboxStatistics cmdlet to obtain information. In Exchange 2007, the ESM no longer exists. Where do you see the different mailbox size (15gb)? Do you mean EMC?
In EMC, Recipient Configuration->Mailbox, right click on the user mailbox and choose
Properties, under General tab, you can see the
Size.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Double prompts for Exchange 2013 migrated users: "The microsoft exchange administrator has made a change that requires you to restart outlook"

I have Exchange 2010 SP3 in my environment and am migrating to Exchange 2013. Whenever a mailbox is migrated, the Outlook 2013 client will prompt the user with a "the exchange administrator has made a change that requires you to restart
Outlook". When the user does so, he or she is prompted again. After he or she closes and reopens Outlook for the second time, the issue is gone permanently.
I've seen a number of other posts about repeated prompts like this but I haven't yet found one or someone gets exactly 2 prompts for each client and no more.
A couple of pieces of information that may be relevant:
1. On exchange 2013, the authentication method for the internal host name is NTLM
2. I have not yet migrated public folders from Exchange 2010. I plan to do that after the mailbox migration is complete.
Thanks in advance for your help.

Hi,
From your description, after mailboxes are moved from Exchange 2010 to Exchange 2013, users receive the following prompt when opening Outlook.
The Microsoft Exchange Administrator has made a change that requires you quit and restart Outlook.
In order to solve this issue, you need to apply the Outlook update that is described in KB 2863911.
For your reference:
Outlook 2013 cannot connect after an Exchange Server 2010 mailbox is moved to Exchange Server 2013
https://support.microsoft.com/kb/2934750?wa=wsignin1.0
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Unable to access public folders on Exchange 2007 when user mailbox is on Exchange 2013

Hi
I have coexistence with Exchange 2007 and Exchange 2013. I've moved a mailbox to Exchange 2013 and now cannot view the public folders on Exchange 2007. The error message I get is "could not connect to the public folder server. microsoft exchange is
not available. either there are network problems or the exchange server is down for maintenance."
Mailboxes on Exchange 2007 do not have any problems viewing public folders. I can't migrate users to Exchange 2013 until this issue is resolved.
The IIS permissions to the Public virtual directory on Exchange 2007 is set to Intergrated Windows and Basic authentication.

Hi northerly,
I recommend you follow the steps below for troubleshooting:
1. Please run the Get-OutlookAnywhere cmdlet to verify the Outlook Anywhere settings on Exchange Server 2013 Client Access servers.
2. If "ExternalHostName" is set, and "ExternalClientAuthenticationMethod" is Negotiate, change "ExternalClientAuthenticationMethod" to something other than Negotiate.
3. If "InternaClientlAuthenticationMethod" is set to Negotiate, and "InternalRequireSSL" is True, change "InternalClientAuthenticationMethod" to something other than Negotiate, or change "InternalRequireSSL" to False.
What's more, here is a helpful KB for your reference.
Users of Exchange Server 2013 or Exchange Online can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
http://support.microsoft.com/kb/2834139/en-us
Hope my clarification is helpful.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Exchange 2013 OWA user must change password at next logon not working

Hi,
I have installed Exchange 2013 on Windows 2012 Server. I create users in ECP and select "user must change password at next logon" option. When newly created user logs in, the OWA page doesn't prompt for password change and just throws error "The
user name or password you entered isn't correct. Try entering it again"
I have enabled Change Password feature in CAS server, but still not working.
Any answers, suggestions would be great help
Regards
Sunil

Hi Sunil,
Have you tried as Martina said and does it work?
If not, please try to set the Minimum Password Age to 1 according to link below. I found some threads which are similar to yours and were solved by this way in Exchange 2013 environment.
http://support.microsoft.com/kb/827614
And for further troubleshooting, please create a new user with "user must change password at next logon" option checked and see if he can log on domain-joined PC.
In addition, please check the event log to see if there is any related error message.
Regards,
Rebecca

Exchange 2013 Database and Mailbox sizing configuration feedback?

Hello,
I am in the process of deploying Exchange 2013 in our environment, it will co-exist with Exchange 2010 until we move everyone over to the new server.
My question is regards to the disk storage design, we have a SAN that Exchange will share with the rest of our Virtual Machines. I plan to have 20 live databases and 20 archive databases so I can balance out mailboxes per database so that each db is roughly
100GB in size.
The goal is is to keep the size down so that any database specific maintenance can finish quicker and if I ever had to deal with db corruption it is faster to restore, backup, etc.
My question is, is there a lot of overhead I will be adding onto the Exchange server by having 40 databases mounted?
Currently 300 users, 3.5TB in exchange databases between live and archive mailboxes (no mailbox caps), with 40 databases (20/20) it spreads out nicely with roughly 15 users per db, and db size is roughly 100GB.
My concern is having 40 databases mounted on a single EXCH2013 multi-role server? We have no DAG, etc.
The machine is a 4vCPU/32GB and the disks are on a Compellent tiered SAN shared among other VMs.
Thanks.

Hi,
It depends on various things. I would suggest you to start with Server Role Requirement Calculator to see your hardware is sufficient to handle the load or not...
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
http://gallery.technet.microsoft.com/Exchange-2013-Server-Role-f8a61780
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2013 / Outlook 2010+ Attachment size limit

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl

I have an issue with my Exchange 2013 deployment. I am unable to send attachments over 10MB. I know, I know not another one of those threads, but I promise I have searched for a solution to my issue as best I can before posting.
So in the EMC I have set the Send/Receive connectors to unlimited, I have set the organizational limits to unlimited, I have even set both the Internal and ExternalDsnMaxMessageAttachSize
to 2047MB.
I have restarted the the Exchange Transport service, failing that I restarted the Exchange Box. I have closed and opened my Outlook Client Several times but when ever
I select an attachment over 10MB I get the message "The Attachment size exceed the allowable limit"
There must be something I am missing but I can't see it. I did also check my (and other) user accounts to confirm that no limits had somehow been set, they are all unconfigured or
blank in the EMC which my research has told means there is no limit on the account.
Now I know in in non exchange environment there are limits on the client, but attached to an exchange server these limits are supposed to be driven by exchange.
Here is the output of Get-TransportConfig
AddressBookPolicyRoutingEnabled : False
AnonymousSenderToRecipientRatePerHour : 1800
ClearCategories : True
ConvertDisclaimerWrapperToEml : False
DSNConversionMode : UseExchangeDSNs
JournalArchivingEnabled : False
ExternalDelayDsnEnabled : True
ExternalDsnDefaultLanguage :
ExternalDsnLanguageDetectionEnabled : True
ExternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
ExternalDsnReportingAuthority :
ExternalDsnSendHtml : True
ExternalPostmasterAddress :
GenerateCopyOfDSNFor : {}
HygieneSuite : Standard
InternalDelayDsnEnabled : True
InternalDsnDefaultLanguage :
InternalDsnLanguageDetectionEnabled : True
InternalDsnMaxMessageAttachSize : 1.999 GB (2,146,435,072 bytes)
InternalDsnReportingAuthority :
InternalDsnSendHtml : True
InternalSMTPServers : {}
JournalingReportNdrTo : <>
LegacyJournalingMigrationEnabled : False
LegacyArchiveJournalingEnabled : False
LegacyArchiveLiveJournalingEnabled : False
RedirectUnprovisionedUserMessagesForLegacyArchiveJournaling : False
RedirectDLMessagesForLegacyArchiveJournaling : False
MaxDumpsterSizePerDatabase : 18 MB (18,874,368 bytes)
MaxDumpsterTime : 7.00:00:00
MaxReceiveSize : Unlimited
MaxRecipientEnvelopeLimit : 500
MaxRetriesForLocalSiteShadow : 2
MaxRetriesForRemoteSiteShadow : 4
MaxSendSize : Unlimited
MigrationEnabled : False
OpenDomainRoutingEnabled : False
RejectMessageOnShadowFailure : False
Rfc2231EncodingEnabled : False
SafetyNetHoldTime : 2.00:00:00
ShadowHeartbeatFrequency : 00:02:00
ShadowMessageAutoDiscardInterval : 2.00:00:00
ShadowMessagePreferenceSetting : PreferRemote
ShadowRedundancyEnabled : True
ShadowResubmitTimeSpan : 03:00:00
SupervisionTags : {Reject, Allow}
TLSReceiveDomainSecureList : {}
TLSSendDomainSecureList : {}
VerifySecureSubmitEnabled : False
VoicemailJournalingEnabled : True
HeaderPromotionModeSetting : NoCreate
Xexch50Enabled : True
Thanks in advance for any assistance.
Carl
1. If you send a message larger than 10MB from an external client to your org, does it bounce back because its over the limit?
2. Do you see the same problem sending internally with OWA?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2013 change account

So some net admins setup separate AD accounts for email access on the exchange 2013 server here at work. These accounts are separate from the accounts used by users to log on to their workstations.
I need to merge these email accounts to the correct domain accounts. In ECP, if I edit the account properties for a particular email account, can I just change the username shown there to use the correct AD account or do I need to wipe out the email
account and recreate it using the correct credentials?
Thanks.

Hi,
According to your description, you want to link a mailbox to an AD account. If I misunderstand your meaning, please feel free to let you know.
If yes, we can try the above suggestion: disable the mailbox and then make the disconnected mailbox connect to the AD account.
Here are some similar threads you can refer to:
http://social.technet.microsoft.com/Forums/exchange/en-US/975f0268-972b-45ce-b59a-8a8eefb94a38/link-old-mailbox-to-new-ad-user-account?forum=exchangesvradminlegacy
http://social.technet.microsoft.com/Forums/exchange/en-US/99614801-8257-4ced-9b94-faf6fdbe1771/create-new-ad-user-accounts-for-all-users-keep-old-mailboxemail-address?forum=exchangesvradminlegacy
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 - Public Folder Mailbox and Single Item Recovery

Hello,
I recently had a request to recover some messages that an ex-employee deleted from the "recover deleted items" folder in their public folder. Since this resides on a public folder mailbox and it does have the option for
"Single Item Recovery" to be enabled on the box (which I enabled not knowing if this really works or not), is there a way I can still recovery these items or do I have to go to a backup to obtain those messages. Since ExFolders does not work that
is not an option. I've seen commands to restore a public folder that was deleted but not items that were deleted directly from a public folder. I checked using MFCMAPI and I do see the dumper root and the public folder dumpster for each folder but it
looks to be only the "deletions" folder and don't see anything similar to a "purges" type folder. Any ideas or am I stuck recovering from backup? Thanks in advance!

So I think you are stuck and will need to restore the EDB to a Recovery Database to restore the items because when the end user purged the items from the "Recover Deleted Items" it removes them from the Recoverable Items/Deletions folder.
Check out this article
http://blogs.technet.com/b/exchange/archive/2013/08/23/recovering-public-folder-information-in-exchange-2013.aspx
I have not played with the recoverable items settings on the 2013 public folder enabled mailbox EDB but you might try checking out Litigation or In Place Hold to use as a safety mechanism moving forward. That said this will also increase the
DB size so consider all the options before implementing
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange 2013 SP1 users not receiving quota warning email message

Hi,
We are on Exchange 2013 SP1 and Exchange 2010 SP3 co-existence mode and currently migrating users from Exchange 2010 to 2013. We have noticed that users are not receiving email message when their mailbox quota warning when its near to maximum limit.
If I log in via OWA it shows the notification (Pop up) that your mailbox is almost full but no message received in email. Most of the users do not log into OWA but only uses Outlook.
It looks like other people are also seeing this similar issue but I am unable to find any solution for it.
How users will know if their mailbox is almost full if they are traveling and only using Mobile phone for emails to send and receive.
Thanks,
Raman

Hi Thanks for your response. Our Quota is set on Database level. I am seeing these event ids as well.
Log Name: Application Source: MSExchangeIS Date: 12/31/2014 10:07:12 PM Event ID: 1077 Task Category: MAPI Level: Warning Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f on database
326f0997-4fe5-4b31-873b-6a3396e7a91c is approaching its storage limit. A notification has been sent to the user. This warning will not be sent again for at least twenty four hours.
========================
Log Name: Application Source: MSExchange Store Driver Submission Date: 12/31/2014 10:07:12 PM Event ID: 1012 Task Category: MSExchangeStoreDriverSubmission Level: Error Keywords: Classic User: N/A Computer: Exch2013mail01.company.com Description: The store
driver failed to submit event 8237691 mailbox e3d48b23-0740-46ab-89f7-3b035dacf28f MDB 326f0997-4fe5-4b31-873b-6a3396e7a91c and couldn't generate an NDR due to exception Microsoft.Exchange.MailboxTransport.StoreDriverCommon.InvalidSenderException at Microsoft.Exchange.MailboxTransport.Shared.SubmissionItem.SubmissionItemUtils.CopySenderTo(SubmissionItemBase
submissionItem, TransportMailItem message) at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.GenerateNdrMailItem() at Microsoft.Exchange.MailboxTransport.Submission.StoreDriverSubmission.MailItemSubmitter.<>c__DisplayClass1.<SubmitNdrForFailedSubmission>b__0()
at Microsoft.Exchange.MailboxTransport.StoreDriverCommon.StorageExceptionHandler.RunUnderTableBasedExceptionHandler(IMessageConverter converter, StoreDriverDelegate workerFunction).
Raman

Exchange 2007 servers reports mailbox size full, but mailbox shows empty in OWA or Outlook.

When the users log into their mailboxes in OWA or Outlook get this warning: "You have exceeded your limit quota and can not send or receive mail" but really they have the mailbox empty, there's nothing in calendar, folders or deleted items.
I ran this command Get-MailboxStatistics and the mailbox reports for example 500 MB.
I deleted the deleted items and I configured deleted items retention to 0 days to ensure that it wasn't the problem, but the servers still reporting the same mailbox size (500 MB).
This happen to some mailboxes, not all
Please help, what can I do?

1. How many Exchange 2007 servers do you have?
2. What service pack and rollups are installed on the Exchange 2007 server(s)?
3. If you have more than one server, are you using any form of replication: LCR, SCR, CCR... etc. ?
4. What 3rd party software is installed on the Exchange 2007 server(s)? For example, antivirus, archiving, etc.
5. Can you confirm that this happens in OWA as well? I see you mentioned OWA but I've just glanced at another problem with incorrect folder size being indicated in Outlook and it apparently had to do with the .OST file. Of course, if the problem occurs with
OWA as well, then the OST file would not come into play. Sorry to insist on that but I'm trying to rule some things out, if possible (like 3rd party apps, maybe something with replication, maybe a problem that was corrected in a service pack or rollup).
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Installation of Exchange 2013 Failed on Mailbox Role Transport Service

Hi All,
Getting this error when trying to install a new exchange 2013 server. Thanks in advance
Error:
The following error was generated when "$error.Clear();
          if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
            Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
        " was run: "Microsoft.Exchange.Data.DataValidationException: Database is mandatory on UserMailbox.
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Data.Directory.Recipient.ADRecipientObjectSession.Save(ADRecipient instanceToSave)
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.Link()
   at Microsoft.Exchange.Management.Deployment.UpdateRmsSharedIdentity.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

Hi,
This problem occurs because the federated built-in e-mail account that links to the computer account no longer exists. Or, the federated built-in e-mail account in the AD
directory service is corrupted.
Please try to follow these steps to solve this problem.
    1. Remove the FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 e-mail account by using the ADSIEDIT tool. To do this, follow these steps:
Click Start, click Run, type adsiedit.msc, and then click
OK.
Locate the Default Naming Context node, and then locate to the
CN=Users container.
Locate and then right-click the CN=FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 container. Then, click
Delete.
    2. Rerun the Exchange Server 2013 Mailbox role setup application.
    3. Create a new federated e-mail account by using the following command:
New-Mailbox -Arbitration -Name FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042 -UserPrincipalName FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042@<Default_Accepted_Domain>
If this issue persistes, please let me know.
Best Regards.

OWA Users Mailbox Size Inceasing

Hi Guyz,
Hope ur all doing good. I have a query regarding OWA, we have so many remote users who only uses OWA and cannot use outlook. Now their mailbox size are increasing, is there any way to archive their emails and still allowing them to access their archived
emails as well? Cannot use outlook and also dont have enough space to use Personal Archives option, please suggest any other solution or any tool
Virgo

Well the main question is why you want to archive the data in the first place? If they're accessing the email via webmail then what ever you do the messages will have to remain in Exchange, since there's no way for those users to access email exported in
a .pst file. Obviously that means there's little point archiving if the aim is to reduce the overall amount of disk space used by Exchange. Additionally, I can't imagine their mailboxes are large enough that Exchange can't handle the size of them.
However, if you wanted to do something like reduce the amount of data being backed up, by spitting the old messages out of the mailbox store holding them, then I guess one option would be to export those messages into a separate "archive" mailbox for each
user. That way if you have multiple mail stores configured you could move those archive mailboxes to a different store, with perhaps a smaller backup frequency etc.
Since OWA does allow users to open additional mailboxes that they have permission to, so long as you granted the users full mailbox permissions to their corresponding archive mailbox, they could then access the old data from OWA still. You can export the
messages using New-MailboxExportRequest
http://technet.microsoft.com/en-us/library/ff607299(v=exchg.150).aspx and specify the period of time you want to archive. I can't see a method to directly archive from one mailbox to another, but you could use that to archive to .pst on the server, and
then use
New-MailboxImportRequest http://technet.microsoft.com/en-us/library/ff607310(v=exchg.150).aspx to import it into the archive mailbox.

Exchange 2013 - Logging folder - huge size

friends i have exchange 2013 SP1... my logging folder is growing like anything .. can some one advise the best practices around it .. i am not sure how i can clean this ... same is happening with inetpub log .. is this related???.. in few months its around
22 GB ...
Please advise
Thanks
Happiness Always
Jatin

This is by design due to the architectural changes in the product. However have seen cases where it caused issues. you can:
Move Logging folders to another drive in Exchange 2013 via Powershell:
http://social.technet.microsoft.com/wiki/contents/articles/22479.move-logging-in-exchange-2013-via-powershell.aspx
Or alternatively you can disable some of the tasks under Windows\PLA in the Task Scheduler Manager.
You can also do a clean-upand delete some of the files older than a specified day.
Get-ChildItem 'C:\Program Files\Microsoft\Exchange Server\V15\Logging','C:\inetpub\logs' -Directory | get-childitem -Include '*.log' -Recurse | ? LastWriteTime -lt (Get-Date).AddDays(-XX) | Remove-Item
CK

Looking for a report on user mailbox size in Unity Connection 8.5.1

Cannot find a report that shows mail box size so that we can identify users approaching limit.
The canned reports don't have mailbox size. Thanks in advance. Mel

Hi Melvin,
You can use the User Data Dump tool. Check out the following post: https://supportforums.cisco.com/message/3403809#3403809
HTH,
Chris

Exchange 2013 - change user mailbox size to over 2GB

Similar Messages

Maybe you are looking for