Exchange 2013 - Quota notifications problem

Hello,
First of all I want to express mild disappointment with the way quota notification alerts are documented on Technet for Exchange 2013. The only reference I could find is that QuotaNotificationSchedule parameter of the Set-MailboxDatabase cmdlet no longer
does anything: "This parameter has been deprecated in Exchange 2013 and it no longer does anything.".
The only other reference I could find is this forum post:
http://social.technet.microsoft.com/Forums/exchange/en-US/f30bb2ca-91ab-4e69-a8b6-720e6a8a5b83/exchange-2013-quota-notification-message-not-sent-during-schedule?forum=exchangesvrgeneral
where it says: "Quota messages are generated once the user log in to mailbox in exchange 2013."
However, Microsoft Press published a book in 2013 "Inside Out: Microsoft Exchange Server 2013: Mailbox and High Availability" where QuotaNotificationSchedule parameter is being referenced as a working parameter which controls when Quota notification
are being sent.
My experience says that the forum post is correct.
Now onto the problem.
While our customer was still on Exchange 2010 they were the victims of this issue:
http://support.microsoft.com/kb/2480474/en-us which could easily be fixed with
CheckWarningQuota registry key.
Now we have migrated those mailboxes to Exchange 2013 and again, users are not receiving quota notification e-mails. Only a few users receive quota notifications e-mails and those are users that got their mailbox created on the new Exchange 2013 system.
Migrated users do not receive notifications. We have tried CheckWarningQuota on Exchange 2013 but it does nothing. Our theory is that mailbox flag introduced in Exchange 2010 SP1 is migrated with the mailboxes to Exchange 2013 and is the
reason why we are not receiving quota notifications again.
I appreciate thoughts and comments.
Regards,
Dinko

CU8 addresses this issue, however, only for mailboxes not yet moved to 2013: https://support.microsoft.com/en-us/kb/303695
Mailboxes already moved will have to be manually fixed. The issue is they are missing their lcid (location ID). For whatever reason, the attribute does not make it across from 2010 to 2013. However, if you move the mailbox again to another 2013 database,
it fills in the lcid automatically. That is one workaround, but not necessarily a good one for people who have migrated a ton of their users already. So what do you do?
In the KB article, it shows you how to identify the users who are missing their LCID by doing the following in the exchange management shell:
#first load in the ManagedStoreDiagnosticFunctions, you will need this for the get-storequery cmdlet to work.
. .\'C:\Program Files\Microsoft\Exchange Server\V15\Scripts\ManagedStoreDiagnosticFunctions.ps1'
#then generate the list of all mailboxes with an LCID of 0.
$mbxs = get-mailbox –resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
$mbxsq = $mbxs | %{Get-StoreQuery -Database $_.database -query "select * from Mailbox where Mailboxguid = '$($_.ExchangeGuid)'"}
$mbxsq | ? {$_.lcid -eq 0} |fl displayname, mailboxguid, lcid
You can modify the script to dump the list to a text file if you need to.
Now, to address this, I simply populated the lcid for all my mailboxes. All of mine were en-US or lcid 1033, so it was easy to set them all at once. I just grabbed all Exchange 2013 mailboxes and applied the language (en-US) and DateFormat (MM/dd/yyyy) to
them (replace DOMAIN with your domain name) which in turn sets the lcid to 1033:
$mailboxes = get-mailbox -resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
($mailboxes).SamAccountName| %{set-MailboxRegionalConfiguration "DOMAIN\$_" -Language en-us -DateFormat MM/dd/yyyy} | FT -a
Incidentally, if you have already migrated all of your 2010 mailboxes, and you are on at least Exchange 2013 CU6, that script will resolve the issue whether you apply CU8 or not. CU8 fixes it for any other mailboxes that have not yet been migrated to 2013.
Hopefully this help you out.
Chris Allen
Microsoft Support Escalation Engineer

Similar Messages

  • Exchange 2013 mail flow problem

    Hello!
    We have problem, could not send mails via Exchange 2013 server.
    Symptoms:
    -no messages in message queue
    -if sending mail  to this domain, the message seems sent at Sender.
    -if sending mail from this domain, the messages are in the mailboxes' DRAFT folder
    Here are some SMTP logs:
    2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,10,192.168.3.2:26408,192.168.3.2:2525,<,250-STARTTLS,
     2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,11,192.168.3.2:26408,192.168.3.2:2525,<,250-AUTH NTLM,
     2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,12,192.168.3.2:26408,192.168.3.2:2525,<,250-8BITMIME,
    2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,13,192.168.3.2:26408,192.168.3.2:2525,<,250-BINARYMIME,
    2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,14,192.168.3.2:26408,192.168.3.2:2525,<,250 CHUNKING,
    2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,15,192.168.3.2:26408,192.168.3.2:2525,*,,"EHLO options between current server and proxy target do not match : Xrdst, . Critical
    non matching options : Xrdst, . Failing over."
    2013-04-03T20:52:25.448Z,Inbound Proxy Internal Send Connector,08CFFEB14C28BE2C,16,192.168.3.2:26408,192.168.3.2:2525,>,QUIT,
    Software Enviroment:
    -Windows Server 2012 Server Standard
    -Exchange Server 2013
    -fully patched system (includes the brand new Exchange 2013 CU1), the error was realized before this update.
    Regards.
    molni

    Hi
       Can you run ipconfig/flushdns or create hosts file recorder?
    Terence Yu
    TechNet Community Support

  • Exchange 2013 - Mail receive problem -Help!

    Exchange 2013 SP1 -fresh install -test environment with one test mailbox setup in addition to the Administrator account. Using default Receive Connectors and it is set for Anonymous. Using OWA and Outlook 2010 for testing.
    We can send/receive mail INTERNALLY in both Outlook & OWA between our test user and the Administrator user.
    We can send mail externally from both accounts.
    We are not receiving mail into the Inbox of either OWA or Outlook.
    We are not seeing any authentication issues with Outlook -always shows connected to Exchange. But if we have same problem in OWA then we are just testing with it for now.
    We ran the Microsoft Connectivity Analyzer for both Inbound and Outbound SMTP and it passed with no errors/warnings L
    We did NSLOOKUP, from a Command prompt at the server wtith this result -not sure why it shows server as unknown?:

    Thank you for replying. Yes the mailbox is at Time Warner and I can use their webmail interface and see the messages I sent to the test user are there.
    No, our domain name is companyname.com  (if you need the actual name..I am not sure if I should send it to you?) and we use
    [email protected] for email.
    Our external A records and MX records are at Network solutions and that is posted here-- but decided to start another thread with more concise information as I learned of it:
    http://social.technet.microsoft.com/Forums/office/en-US/0b18e928-0207-4ab9-bc12-c00a75088bdc/new-deployment-outlook-can-send-but-not-receiving-messages?forum=exchangesvrsecuremessaging
    When I do NSLOOKUP of our domain I get just the two MX records at Time Warner. Not anything with our actual domain name for email in it. I just added the A records for mail.companyname.com and autodiscover at Network Solutions yesterday...but though those
    were only for use externally for OWA, ActiveSync, etc
    Note we do not use Split-DNS on our internal domain either. Our AD name is different than our public domain name - The AD is named with a subdomain: qs.companyname.com
    Lastly, I did not create an MX record at network solutions for mail.domainname.com. Should I do that and set it to a higher priority?

  • Exchange 2013 & 2010 coexist problem. Authentication Credentials Prompt in Outlook

    Hello Forum
    We have two Exchange servers coexisting together. A new 2013 and a old 2010.
    Everything was setup with the help of the Exchange Deployment Assistant.
    I have had alot of trouble with Outlook 2013 Prompting for credentials on Exchange 2013 Mailboxes. None of the 2010 Mailboxes expericence this popup.
    I solved most of the popup issues with this by changing the ExternalClientAuthenticationMethod to ntlm.(from negotiate)
    http://blog.gothamtg.com/2013/10/15/users-constantly-prompted-for-credentials-after-being-migrated-to-exchange-2013/
    and installing this update for Outlook:
    http://support2.microsoft.com/kb/2899504/en-us
    Now 2013 Mailboxes Work without any anoying popups. Except when they try to open another users mailbox that is located on the old 2010 server or a shared 2010 calander.
    The connection to Exchange 2010 is working if I input the users password, but should it not work without this popup too?
    This connections name acording to Outlook is called: Exchange-Mail RPC/HTTP (remote [NTLM])
    We use the same domain for external and internal autodiscover connections.
    Test Exchange Connectivity Analyzer shows everything ok.
    If i run
    get-outlookanywhere | fl *external*
    (2013 server)
    ExternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Ntlm
    ExternalClientsRequireSsl          : True
    (2010 server)
    ExternalHostname                   : webmail.domain.com
    ExternalClientAuthenticationMethod : Basic
    ExternalClientsRequireSsl          : True  
    Only one thing I am wondering here is. If I change my old 2010 Auth Method to NTLM if that will break anything i OWA and so on.
    What do you Guys have setup in your environments and can you point me towards any troubleshooting?
    Thanks!

    For us, the changes made in IIS are permanent, there quite possibly is a powershell way of doing it but I am still getting to grips with PS myself so I don't know.
    I wont plagiarise others work but these two links here give a good explanation between Basic and NTLM. personally, I have always used basic because I always seem to get problems with NTLM, though one time it did work as expected but I forgot what I did to
    get it working now.
    https://social.technet.microsoft.com/Forums/exchange/en-US/92178beb-3310-4363-8848-d022a6e2a77f/basic-vs-ntlm-authentication-outlook-anywhere
    http://www.sysadminlab.net/exchange/outlook-anywhere-basic-vs-ntlm-authentication-explained  

  • Exchange 2013 - Shared Calendar problems

    Since we put in Exchange 2013 in July 2013 we have had a problem with Shared Calendars.  Even though a User has Owner Permission on another Calendar, New Appointment is Grayed Out and the User cannot add or amend and occasionally Outlook will hang. 
    We have tried Outlook 2010 and 2013 Clients as well as Cached Mode and Online Access.  Exchange Server Standard 2013 CU2 was installed and this seemed to stop the problem for a while and now it has returned.
    Permissions have been removed and reapplied both through the Exchange Powershell Interface and on the Mailbox.  All other aspects of the system seem fine.
    Any advice would be welcome.

    Hi,
    Please check your application logs in your Exchange server. Confirm whether there are some error logs such as Event 9646.
    It may because there are too many users connect to shared calendar at the same time that cause this issue. And there is a limit on the number of items that clients can open.
    If so, we can change regedit
    on the Exchange computer to resolve this issue. For more information, please click the following KB:
    http://support.microsoft.com/kb/830836/en-us
    Thanks,
    Winnie
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Exchange 2013 sp1 DAG problem on Wondows 2012 r2

     Hi,
     I have configured this on my servers. It seems to be working almost 100%.
     When I look at  server-databeses in ecp  I see the DB is healthy both active and psssive.
     When I run  this (Get-DatabaseAvailabilityGroup) | ForEach {$_.Servers | ForEach {Test-ReplicationHealth -Server $_}}
     I get DatabaseAvailabilty   FAILED  on  both  active and passife  DB.
     When I Switchover to the other sever I get no errors  but in ca. 2 min it Switches back.
     If I try to move mailbox from Exchange 2010 sp3 to  Exchange 2013 sp3 I get 
    Data migrated: 1.327 GB ‎(1,425,379,174 bytes)‎
    Migration rate: 0 B ‎(0 bytes)‎
    Error: MigrationPermanentException: Error: Mailbox changes failed to replicate. Database 18475dc2-2111-4da6-854b-6583d42c9279 doesn‎'t satisfy the constraint SecondCopy because the commit time 3/12/2014 12:17:49 PM isn‎'t guaranteed by replication
    time 1/1/0001 12:00:00 AM.
    I admit that I had this configured before I installed SP3 :( Do I need to delete the DAG and create it again?
    thanks.
    Erró

    Hello,
    Please use Get-MailboxDatabaseCopyStatus cmdlet to view health and status information about one or more mailbox database copies.
    Based on your environment, please set DataMoveReplicationConstraint to None to check the result.
    Set-MailboxDatabase "mailbox database name" -DataMoveReplicationConstraint None
    After you have done the move, please set DataMoveReplicationConstraint to SecondCopy again.
    Set-MailboxDatabase "mailbox database name" -DataMoveReplicationConstraint SecondCopy
    If you have any feedback on our support, please click
    here
    Cara Chen
    TechNet Community Support

  • Exchange 2010 to Exchange 2013 Public Folder Problem

    Dear Experts,
    I am in a face of migrating Exchange 2010 to Exchange 2013. Below are my infrastructure details,
    1) Parent Domain in Site A (abc.com)
    2) One Child domain in Site A named child1.abc.com and Exchange 2007 is running in Site A child domain
    3) One Child domain in Site B named me.abc.com and currently Exchange 2010 is running in Site B.
    I have installed Exchange 2013 in Site B in coexistence scenario now Exchange 2013 users in Site B trying to attempt connection with a public folder store in the Site A Exchange 2007 servers instead of Site B Exchange 2010 servers.
    Anyone help will be highly appreciated.
    Thanks & Regards,
    ZB

    so you want users to access the PF in site B.
    Check the setting of Databases in Exchange 2013 and find out what is default Public Folder setup for those Database. You will basically need to change the default Public Folder in Exchange 2013 from Site A PF to Site B,, the way you have explained the scenario.
    run this for Exchanger 2013 DA
    Get-mailboxDatabase -Identity Exchange2013DBNAME | fl
    Get-MailboxDatabase -Identity e15-db1 | fl *PublicFolder*
    Where Technology Meets Talent

  • Exchange 2013 wildcard certificate - problem IMAP POP Because the matter is not a fully qualified domain name

    Hi all, I have an Exchange 2013 SP1, I have installed a third-party SSL certificate and correctly on the server, but when I assign the POP and IMAP services, I see this error
    The certificate with thumbprint XXXXXXXXX and subject '*. Xxxx.yyy' can not be used for POP SSL / TLS connections because the matter is not a fully qualified domain name (FQDN). Use the Set-POPSettings X509CertificateName command to set the FQDN of the service.
    I tried to run this command and restart the POP and IMAP services
    ImapSettings set-ca-server-1-X509CertificateName mail.xxxxx.yyy
    POPSettings set-ca-server-1-X509CertificateName mail.xxxxx.yyy
    But the POP and IMAP services, the certificate is not assigned.
    You know as you can solve
    regards
    Microsoft Certified IT Professional Server Administrator

    Hi,
    Before we go further, I’d like to confirm if you can use POP and IMAP properly.
    If everything goes well, we can safely ignore it:
    http://www.hsuconsulting.com/wildcard-ssl-certificate-exchange-2013-imap-and-pop-error/
    If not, we can try the following commands :
    Set-POPSettings -ExternalConnectionSetting {mail.domain.com:995:SSL}
    Set-ImapSettings -ExternalConnectionSetting {mail.domain.com:993:SSL}
    http://careexchange.in/how-to-enable-and-configure-pop-imap-in-exchange-2013/
    Note: Microsoft is providing the above information as convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information
    found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Exchange 2007 to exchange 2013 Mailbox Move problem

    Data migrated:
    Migration rate:
    Error:MigrationPermanentException: Active Directory property ‎'homeMDB‎' is not writeable on recipient ‎'domain.org/ICT_Dept/Abu Bakar Siddikuzzaman‎(ICT-Mirpur)‎‎'. --> Active Directory property ‎'homeMDB‎' is not writeable on recipient
    ‎'domain.org/ICT_Dept/Abu Bakar Siddikuzzaman‎(ICT-Mirpur)‎‎'.
    Md. Ramin Hossain

    [PS] C:\Windows\system32>Get-Mailbox arahaman | New-MoveRequest -TargetDatabase "Head-Office"
    Active Directory property 'homeMDB' is not writeable on recipient 'domain.org/ICT_Dept/Atikur Rahaman'.
        + CategoryInfo          : NotSpecified: (:) [New-MoveRequest], RemotePermanentException
        + FullyQualifiedErrorId : [Server=HYPER-SUNMAIL,RequestId=fbb3dcab-54a3-423f-81b5-9c5c397b34b4,TimeStamp=7/2/2014
       5:46:07 AM] [FailureCategory=Cmdlet-RemotePermanentException] 63F06918,Microsoft.Exchange.Management.RecipientTask
      s.NewMoveRequest
        + PSComputerName        : hyper-sunmail.domain.org
    Md. Ramin Hossain

  • Cannot send mail from Exchange 2013 to Exchange 2007

    I have an
    Exchange 2007server with all roles in the same server (Version:
    08.03.0327.001 ) on a Windows 2008 R2 server. I have now installed two Exchange 2013 servers both with CAS and MBX roles on Windows 2012 servers
    (full patched). There is also a DAG between the new servers. All mail goes through a BorderWare besides the internal mail.
    I can send mail from both environments to the Internet. I can also send internal mail from Exchange 2007 to Exchange 2013.But the problem is that I am unable to send from Exchange 2013 to Exchange 2007. I've debugged, but not solved the problem and there are
    few articles on the Internet.
    Any suggestions?

    These two sentences are in conflict : "I can also send
    internal mail
    from Exchange
    2007 to
    Exchange 2013. But
    the problem is
    that I am unable
    to send from Exchange
    2007 to
    Exchange 2013. "
    Can you describe what is your real problem? Flow from E2007->E2013? Or vice versa?
    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. Thank you! Damir

  • Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

    Hello, everyone, my name is rafl
    I have a problem with exchange 2013 active sync.
    I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
    but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
    (legacy.domain.com)
    the process of moving mailboxes successfully without error.
    Access OWA for exchange 2007 and exchange 2013 is running normally
    access mail from Outlook running normally
    Certificate request has been installed and has no problem with it
    The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
    The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
    ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
    user mailboxes are still on exchange 2007 is not problematic.
    only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
    but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
    only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
    any ideas for this problem, and what should I check on the exchange server ..?

    i have run the activesync test connectivity and get some error :
    Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 3091 ms.
    Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21072 ms.
    Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
    The specified port is either blocked, not listening, or not producing the expected response.
    A network error occurred while communicating with the remote host.
    Elapsed Time: 21049 ms.
    I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
    for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

  • Outlook 2007 - single profile connecting to Exchange 2013 / 2007 mailboxes

    Hi,
    I am in the early part of a migration from Exchange 2007 to Exchange 2013. So far I have 2013 installed and running in a DAG and just moved my own mailbox to the new server.
    I set up a new profile in Outlook 2007 which connects to my mailbox on Exchange 2013. The problem is that I need to add additional mailboxes to my profile which are still hosted on Exchange 2007, however this is not working.
    I thought at one stage I tested this and was able to get it work with a test mailbox also hosted on Exchange 2013.. but maybe I never did.
    Does anyone know if this is possible at all (single Outlook profile, primary mailbox hosted on Exchange 2013 and other mailboxes on Exchange 2007). Most of our users have an additional mailbox mapped in their profile so I hope there is some way around this.
    Thank you!

    Hi,
    It is possible to open a shared mailboxes on a legacy server.
    Your problem could be caused by:
    Not having one of the later CU installed (read CU4 or CU5)
    Incorrect authentication methods configured (see link below)
    Outlook is not at the latest patch level
    Users of Exchange Server 2013 can't open public folders or shared mailboxes on an Exchange 2010 or Exchange 2007 server
    http://support.microsoft.com/kb/2834139
    Martina Miskovic

  • Need help regarding the location of Exchange 2013 Logs for parsing

    Hi, I am trying to create reports based on the logs that are created on my exchange server. I am using
    exchange 2013. My problem is that I cannot handle every log, and instead want specific types of logs.
    I need help finding the specific locations of the following types of logs (If they even exist), so that I can parse them and use them effectively:
    Audit Logs (Mailbox logons, Mailbox permission changes, Mailbox property changes,
    Exchange store changes)
    Mail Report Logs (Mailbox size and growth, Mailbox storage growth, Enabled users, Expired and Soon-to-Expire Mailboxes)
    Exchange Traffic Reports (Details on size and amount of messages sent and recieved, Internet traffic [to and from], Traffic between exchange users)
    I understand this might sound like a huge undertaking, but any help that can be provided would be appreciated.
    Again, I need information on the locations of these types of logs on the exchange server, so that I can parse them. Collecting them all and searching through them is not practical for my available resources.
    Thanks,
    Matt

    Audit Logs (Mailbox logons, Mailbox permission
    changes, Mailbox property changes, Exchange
    store changes) ---- these are two type of logs, 1. mailbox audit logs and that is stored in each mailbox under dumpster
    http://technet.microsoft.com/en-us/library/ff461930(v=exchg.150).aspx however you need to
    enable
    it for individual mailboxes... 2. admin audit log, this is stored into a system mailbox dumpster.... http://technet.microsoft.com/en-us/library/dd335052(v=exchg.141).aspx
    Mail Report Logs (Mailbox size and growth, Mailbox
    storage growth, Enabled users, Expired and Soon-to-Expire Mailboxes) ---- there isn't any specific log for this, you would need to create some time of script to collect this every day for you and store it somewhere... This is a good start... http://www.stevieg.org/2011/06/exchange-environment-report/
    Exchange Traffic Reports (Details on size and
    amount of messages sent and recieved, Internet traffic [to and from], Traffic between exchange users) ----- This you can get from message tracking log... http://technet.microsoft.com/en-us/library/bb124375(v=exchg.150).aspx

  • Anyone done SBS 2008 to Exchange 2013 migration - disable IPv6 on SBS?

    IPv6 enabled on ours without any problems. THanks for the links Anil, had not heard of those problems before

    Well, considering over the scenario you have mentioned, I would like to refer you on this informative article that covers few parts of causes when disabling IPV6 on Exchange 2013 Server installation : http://mike-graham.co.uk/blog/2013/08/12/disabling-ipv6-on-exchange-2013-servers-causes-problems/Here is a well documented technet resource that also provides step-wise instructions when proceeding to migrate from Exchange 2007 to 2013 by checking all the required prerequisites : http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migra...Moreover, while need to migrate users mailboxes from Exchange 2007 to 2013, you may also consider on LepideMigrator for Exchange tool that provides a hassle-free environment to get this job done without having downtime or any further interruption.

  • 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

Maybe you are looking for

  • How to convert a word document to PDF from a criteria workflow

    Hi, How to create a new revision in PDF format from a word document inside a criteria workflow? The inbound refinery converts documents to PDF automatically upon check-in, but I want to make the conversion in a specific step of a workflow. Thanks, Mi

  • Adding and deleting additional tab in Equipment master

    Hi, I tried to add some extra tab in the equipment master ...by getting into set view profiles and clicked the equipment group and also click the activity and layout of views in left and added the warrant and given 110 also...then i did clicked in ic

  • How to get PC from ucontext_t structure

    Hi, I am getting some performance tuning and stumble on following problem: optimize_me(){ ucontext_t context; int err, param err = getcontext ( &context ); err = walkcontext( &context,my_fn, &param ); The problem seem to be in calling walkcontext too

  • GUI_UPLOAD error when reading PDF

    Hi, I am using GUI_UPLOAD to read a PDF and store it against a material number. When I go into MM03 to view all the attachments it shows that it is there but when I try to open it an error appears stating 'There was an error opening this document. Th

  • Macbook Pro Recent Heat Increase

    I have a 2 year old 13" Macbook Pro from 2009. My macbook pro has alway ran hot as they all do, especially in the top left corner near the escape key where all of the ports are. Recently, in the past month or two, my macbook has been running very sig