Exchange 2013 Mailbox Size Limits

Are there any hard limits on mailbox sizes in Exchange 2013 (either in terms of mailbox size or item count)?
Note: I am aware of the public folder mailbox size limits as well as the hard limit of 2TB for mailbox databases.

I believe the max mailbox size is 100 GB
http://blogs.technet.com/b/ashwinexchange/archive/2012/12/17/3541150.aspx
Major changes in Information Store
Managed Store
Newly rewritten Information Store processes, Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe.
Each database runs under its own process, allowing for isolation of store issues to a single database.
Tightly integrated with MSExchangeRepl.exe to provide higher availability through improved resiliency.
Public Folder Database no longer exist.
Exchange 2013 it supports up to 100 GB of Mailbox size, with OL2013 OST file size can be controlled.
Exchange 2013 Enterprise Edition can only mount 50 databases on a mailbox server

Similar Messages

Exchange 2013 Mail Size Limits

I am having an issue with setting the max send and receive size on Exchange 2013. I keep getting the following error when I attempt to send a 20 meg file server to an internal exchange account OR if I attempt to send a 20 meg file from the exchange
server to an external account:
#550 5.3.4
ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##
I have checked the mail sizes and below is the report. I currently have both send and receive set to 100MB. Is there some other setting in 2013 that I am not aware of?
AnonymousSenderToRecipientRatePerHour                       : 1800
ClearCategories
: True
ConvertDisclaimerWrapperToEml                               : False
DSNConversionMode
: UseExchangeDSNs
ExternalDelayDsnEnabled                                     : True
ExternalDsnDefaultLanguage                                  :
ExternalDsnLanguageDetectionEnabled                         : True
ExternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 bytes)
ExternalDsnReportingAuthority                               :
ExternalDsnSendHtml
: True
ExternalPostmasterAddress                                   :
GenerateCopyOfDSNFor                                        :
HygieneSuite
: Standard
InternalDelayDsnEnabled                                     : True
InternalDsnDefaultLanguage                                  :
InternalDsnLanguageDetectionEnabled                         : True
InternalDsnMaxMessageAttachSize                             : 100 MB (104,857,600 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
: 100 MB (104,857,600 bytes)
MaxRecipientEnvelopeLimit                                   : 500
MaxRetriesForLocalSiteShadow                                : 2
MaxRetriesForRemoteSiteShadow                               : 4
MaxSendSize
: 100 MB (104,857,600 bytes)
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

Hello Landfish,
Good Day...
The output gives the information that Size limit set for Receive and Send is 100 mb, but setting could have changed. So you can follow the below steps to resolve the issue.
There are basically three places where you can configure default message size limits on Exchange:
Organization transport settings
Send/receive connector settings
User mailbox settings.
To check your server’s current limit you can open Exchange Management Shell
Try the below commands to check the Message quota size limit
get-transportconfig | ft maxsendsize, maxreceivesize
get-receiveconnector | ft name, maxmessagesize
get-sendconnector | ft name, maxmessagesize
get-mailbox Administrator |ft Name, Maxsendsize, maxreceivesize
To change the above size limits based on your requirement.
Set-TransportConfig -MaxSendSize 200MB -MaxReceiveSize 500MB (Size is based on your requirement)
Attachment size limit
To set up the rule you can use the below PowerShell cmdlet, as the method is quite simple
New-TransportRule -Name LargeAttach -AttachmentSizeOver 20MB -RejectMessageReasonText "Message attachment size over 20MB - email rejected."
For More info
https://technet.microsoft.com/en-us/library/bb124708(v=exchg.150).aspx
Remember to 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 Check out my latest blog posts @ Techrid.com

Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

Hi Team,
I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
open and throws an error of some "cannot open set of folders".
Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
Kindly share some KB or tip. Any help is appreciated. Thank You.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 mailbox added to the CAS array

We are upgrading to Exchange 2013 from Exchange 2010. Following the development guide, we have
installed the first mailbox server in the Exchange 2010 environment which has 3 Exchange 2010 CAS server
in the array. When installing the mailbox role, we did not choose the client access role but after
the installation we can see that the Exchange 2013 Mailbox server is added to the CAS array and yet
we did not choose the client access role. How does this happen, and to proceed ?

I see the same thing in my lab:
Get-ClientAccessArray | FL
RunspaceId        : 16b992b3-270f-4ae1-a3c3-fa9e2ea73d69
ExchangeLegacyDN : /o=Wingtiptoys/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=Ou
                    tlook.wingtiptoys.ca
Fqdn              : Outlook.wingtiptoys.ca
Site              : wingtiptoys.ca/Configuration/Sites/Default-First-Site-Name
SiteName          : Default-First-Site-Name
Members           : {EXCH-2010, EXCH-2013}
AdminDisplayName :
ExchangeVersion   : 0.1 (8.0.535.0)
Name              : Outlook.wingtiptoys.ca
DistinguishedName : CN=Outlook.wingtiptoys.ca,CN=Arrays,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administr
                    ative Groups,CN=Wingtiptoys,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=wingtiptoys,DC=ca
Identity          : Outlook.wingtiptoys.ca
Guid              : 27968af1-1624-4ff3-85c8-e38e68183afe
ObjectCategory    : wingtiptoys.ca/Configuration/Schema/ms-Exch-Client-Access-Array-2
ObjectClass       : {top, server, msExchExchangeServer, msExchClientAccessArray}
WhenChanged       : 4/12/2014 12:51:18 PM
WhenCreated       : 4/12/2014 12:51:18 PM
WhenChangedUTC    : 4/12/2014 7:51:18 PM
WhenCreatedUTC    : 4/12/2014 7:51:18 PM
OrganizationId    :
OriginatingServer : DC-1.wingtiptoys.ca
IsValid           : True
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
the following command:
Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
Many thanks.

Hi Dennis,
Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
Please check your connection authentication. We can run the following command to set your Outlook Anywhere for Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
In Outlook side, please ensure the following settings in Account Settings:
In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 Mailbox Role Installation Error

Hi All,
I am getting the below error when installing Exchange 2013 Mailbox Role. This is a Windows Server 2012. Previous Exchange 2013 setup was removed since it had issues with CAS. Now we have removed all previous Exchange software and attributes.
Error:
The following error was generated when "$error.Clear();
          Install-ExchangeCertificate -services IIS -DomainController $RoleDomainController
          if ($RoleIsDatacenter -ne $true -And $RoleIsPartnerHosted -ne $true)
            Install-AuthCertificate -DomainController $RoleDomainController
        " was run: "Microsoft.Exchange.Management.Metabase.IISGeneralCOMException: An IIS directory entry couldn't be created. The error message is The system cannot find the path specified.
. HResult = -2147024893 ---> System.Runtime.InteropServices.COMException: The system cannot find the path specified.
   at System.DirectoryServices.DirectoryEntry
   at System.DirectoryServices.DirectoryEntry.Bind()
   at System.DirectoryServices.DirectoryEntry.RefreshCache()
   at System.DirectoryServices.DirectoryEntry.FillCache(String propertyName)
   at System.DirectoryServices.PropertyCollection.KeysCollection.GetEnumerator()
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetProperties(DirectoryEntry webObj)
   at Microsoft.Exchange.Management.Metabase.IisUtility.GetWebSiteSslCertificate(String webObjectPath)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.FindIisCertificate()
   at Microsoft.Exchange.Management.SystemConfigurationTasks.InstallExchangeCertificate.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Any views on this is appreciated.
Regards
Boniface
Senior Systems Administrator

Hi,
After uninstalling the IIS, please run the following command to install prerequisites.
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45,
Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service,
Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Then remove the “water mark” key and “action” key under the following registry and initiate the setup again.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15.0\HubTransportRole
In addition, please disable any third-part software for troublwshooting.
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Exchange 2013 mailbox name resolving vs. exchange server name (mailbox rule)

Hello guys,
I am running exchange 2007 and exchange 2013 CU7 in hybrid mode, while internal autodiscover a record is pointing to exchange 2007 client rule server.
When I configure outlook mailbox located on exchange 2007- I can use autodiscover using mail address ore resolve mailbox name vs. exchange server name.
When I configure outlook mailbox located on exchange 2013- I can configure it only using autodiscover mechanism ( email address - next- next etc.).
We are using EMC backup software which works with MAPI. Since I wasn't able to restore granular mailboxes, I contacted EMC and they claimed that it's very important to configure mailboxes resolving.
What should I check and configure to make it work?

Hi,
I think if we want to browse single mailbox by backup software, it will be regard to resolve mailbox name using server name, I suggest you contact EMC supplier to improve it.
By the way, they I type mailbox name which located on exchange 2013 server database and typing exchange 2007 cluster name, server name of exchange 2007 cluster changes automatically to exchange 2013 server on which this mailbox located.
A: first, we should make sure cluster was worked without any problem. Then make sure Exchange 2013 mailbox server was included in cluster.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

How to introduce exchange 2013 mailbox server in an existing Exchange 2010 Environment

Hi All,
we are planning to install exchange 2013 mailbox server in an Exchange 2010 environment. we have 3 MB servers, 1 CAS 1 HUB which is installed with Exchange 2010 SP3 Enterprise Edition. how to install new exchange server 2013 and i have to add the 2013
servers in to existing DAG and migrate all mailboxes in to 2013 server. Please advise me from the scratch. also will it be create any impact in my existing setup.
Thanks, Venkatesh. "Hardwork Never Fails"

For a step by step follow the deployment assistant
http://technet.microsoft.com/en-US/exdeploy2013/Checklist?state=2419-W-AAAAAAAAQAAAAAEAAAAAAAA%7e
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Performance counters for exchange 2013 mailbox & cas servers?

what are the Performance counters for exchange 2013 mailbox & cas servers?
similar to rpc request for troubleshooting exchange slowness, I haven't found any technet article for exchange 2013.

Hi,
Please see this:
Ask the Perf Guy: Sizing Exchange 2013 Deployments
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
Hope it is what you need.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2013 mailbox migration stalled duration

I am in the process of migrating mailboxes from Exchange 2007 to 2013. The moves seem to take an awfully long time. I am migrating a batch of 10 users and the total mailbox size is 32GB. It has been running for 12 hours and is not complete. I have notice
that there is a "Stalled Duration Time" what does that represent? Also, what should I expect in terms of migration time?

Also, seeing this in the logs. It's been about 18 hours now.
Relinquishing job because of large delays due to unfavorable server health or budget limitations.
12/15/2014 9:06:11 PM [Server01] Copy progress: 7546/44948 messages, 167.4 MB (175,539,357 bytes)/2.441 GB (2,620,927,938 bytes), 9/300 folders completed.
12/15/2014 9:06:11 PM [Server01] Relinquishing job because of large delays due to unfavorable server health or budget limitations.
12/15/2014 9:22:30 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:24:35 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:27:10 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:31:53 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:36:51 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:39:47 PM [Server01] Relinquishing job: The request has been temporarily postponed: Resource reservation has expired. --> Resource reservation has expired.
12/15/2014 9:41:21 PM [Server01] The Microsoft Exchange Mailbox Replication service 'Server01.domain.com' (15.0.995.31 caps:1FFF) is examining the request.
12/15/2014 9:54:43 PM [Server01] Connected to target mailbox 'f491b26b-4a91-4b23-a9aa-d256e8acb8c4 (Primary)', database 'Server0101', Mailbox server 'Server01.domain.com' Version 15.0 (Build 995.0).
12/15/2014 9:54:44 PM [Server01] Connected to source mailbox 'f491b26b-4a91-4b23-a9aa-d256e8acb8c4 (Primary)', database 'mailbox01\Database\DatabaseDB', Mailbox server 'MAILBOX01.domain.com' Version 8.3 (Build 379.0).
12/15/2014 9:58:16 PM [Server01] Request processing continued, stage LoadingMessages.

Exchange 2013 STD - Capacity Limits

Hi,
I plan to deploy, exchange 2013 STD with 400 users.
I understand the exchange STD 2013, supports 5 mounted (active mailbox database).
---> I've seen the mailbox database can grow to 2 TB size limit.
Questions:
1. What is the maximum mailboxes can I create with a single mailbox database? What is the recommended ratio ?
2. I plan to have 100 mailboxes per mailbox database would this be a good idea ?
Thanks,
Paul

Hi Paul,
Same concern has been raised earlier which clarified in this thread. Please checkout this :
http://social.technet.microsoft.com/Forums/exchange/en-US/975492cb-3510-4add-8a4d-f48bda76038a/maximum-number-of-user-mailboxes-supported-by-single-exchange-database-in-2007-2010-2013-?forum=exchangesvradmin

Exchange 2013 Mailbox- Need to see how many sessions of a sinlge mailbox is opened ? Ex: Scenario is 10 helpdesk engineers using single mailbox in different machines

Can we get details of on how many machines a sinle mailbox has been opened in the company in exchange 2013 CU5 envinronmnet
Manju Gowda

Hi,
Since there is no official article for Exchange 2013, we can refer to the 2010 article here:
Exchange Store Limits
http://technet.microsoft.com/en-us/library/ff477612(v=exchg.141).aspx
Thanks,
Simon Wu
TechNet Community Support

Exchange 2013 Attachment Size Issue

Hi everybody,
I'm having some trouble with an Exchange 2013 server.
The users are not able to receive messages with a size bigger than 10MB, i tried with serveral attachments.
I already did te following:
Changed the maximum receive size through the ECP to 60MB (on the default frontend Exchange), and restarted te transport service.
Set the receive size through PowerShell with the following command.
set-transportconfig -maxreceivesize 35MB
when i check the receive size properties, it accepts 35MB messages. (get-transportconfig -property maxreceivesize)
Also restarted serveral Exchange transport services.
Checked the router if there are any special firewall rules, but there are none.
When I send an email with an attachment (PDF about 4 meg), it receives like it should.
Once I send a same email but with an 11meg PDF file, it is not delivered.
When sending this e-mail and attechment, i checked the box to notify me when the message has been deliverd.
I don't get any response, no NDR, nothing...
Tried e-mail tracking but there is no trace of my message.
Am I missing anything?
Kind regards,
Tim

Hi,
Please check the message size limit on receive connector, by default it’s 35MB
Get-ReceiveConnector “connector name”| fl MaxMessageSize
Also check if there are any message size limit in transport rule.
Get-transportrule | fl MessageSizeOver
Message size limits
https://technet.microsoft.com/en-us/library/bb124345(v=exchg.150).aspx
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

Hi,
I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
Configuration server Exchange 2007 SP3 :
Domain : test.com
OS : Windows 2008 server SP2 (not R2)
Firewall : OFF
Exchange roles are on separate three servers : CAS - MAILBOX - HUB.
Configuration Server Exchange 2013 :
Domain : new.com
OS: Windows 2012 R2
Firewall : OFF
This environment is on a closed network unable to reach internet.
I have try to restart the Replication service, but it didn't worked.
I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
Anyone ever had this issue?
Thanks you and have a nice day.

Hi ,
Based on my knowledge below things need to checked.
1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
DataMoveReplicationConstraint : None
Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
3.Restart the Microsoft exchange mailbox replication service and check the results.
4. Have you tried moving the same mailboxes to the different databases.
5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Exchange 2013 mailbox auditing command with showdetails parameter in ps1 script is not working via task scheduler

Hi All ,
In my environment we are having exchange 2013 enterprise edition with SP1 which is installed in windows server 2012 standard edition.
We have enabled mailbox auditing for few mailboxes and also we have made simple powershell script with only the below mentioned commands .when i run the ps1 script in exchange management shell ,i can able to get the relevant output.
CMDLETS in powershell script :
Search-MailboxAuditLog -StartDate ((Get-Date).AddHours(-24)) -EndDate (Get-Date) -showdetails | fl >e:\output.txt
Note : we are having only the above commands in ps1 script , apart from that we don't have anything in it .
Sametime i have scheduled the same powershell script via task scheduler .But i cannot able to get the valid output ,instead of that i was getting a blank output file with no data in it .
Steps handled on my side to run the powershell script in task scheduler:
1.when i remove the parameter showdetails in the ps1 script ,i can able to get the output in the txt file .But in my scenario showdetails is the only parameter which will brought me more and in depth details about mailbox auditing.
The Difference what i have seen between exchange 2010 and exchange 2013
when in run the same powershell script via task scheduler in exchange 2010 enterprise environment installed in windows server 2008 r2 enterprise OS, i can able able to get the proper output without removing the showdetails parameter .
I am using the below methods to run the ps1 file via task scheduler in exchange 2013 environment .
program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments : -PSConsoleFile "E:\Program Files\Microsoft\Exchange Server\V15\Bin\exshell.psc1" -Command ". 'C:\scripts\MailboxAuditReport\test.ps1'"
I have mentioned the error below and that is the one what i have faced, when i try to run the PS1 script directly in windows powershell and not in exchange management shell .
Error message : "the requesting account does not have permission to access the audit log"
Please help me out to resolve this case .
Thanks
S.Nithyanandham

Hi All ,
In my environment we are having exchange 2013 enterprise edition with SP1 which is installed in windows server 2012 standard edition.
We have enabled mailbox auditing for few mailboxes and also we have made simple powershell script with only the below mentioned commands .when i run the ps1 script in
exchange management shell,i can able to get the relevant output.
CMDLETS in powershell script :
Search-MailboxAuditLog -StartDate ((Get-Date).AddHours(-24)) -EndDate (Get-Date) -showdetails | fl >e:\output.txt
Note : we are having only the above commands in ps1
script , apart from that we don't have anything in it .
In case, if i have scheduled the same powershell script via task scheduler .But i cannot able to get the valid output ,instead of that i was getting a blank output file with no data in it .
Steps
handled on my side to run the powershell script in task scheduler:
1.when i remove the parameter showdetails
in the ps1 script ,i can able to get the output in the txt file .But in my scenario showdetails is the only parameter which will brought me more and in depth details about mailbox auditing.
The
Difference what i have seen between exchange 2010 and exchange 2013
when in run the same powershell script via task scheduler in exchange 2010 enterprise environment installed in windows server 2008 r2 enterprise OS, i can able able to get the proper output without removing the showdetails parameter .
I
am using the below methods to run the ps1 file via task scheduler in exchange 2013 environment .
program/script : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
Add arguments : -PSConsoleFile "E:\Program
Files\Microsoft\Exchange Server\V15\Bin\exshell.psc1" -Command ". 'C:\scripts\MailboxAuditReport\test.ps1'"
I have mentioned the error below and that is the one what i have faced, when i try to run the PS1 script directly in windows powershell and not in exchange management shell .
Error message : "the requesting account does
not have permission to access the audit log"
Please help me out to resolve this case .
Thanks
S.Nithyanandham

Exchange 2013 Mailbox Size Limits

Similar Messages

Maybe you are looking for