Exchange 2010 Slow Database Mount Time - Almost 1 Hour

Hello -
We have 2 DAG nodes on the production site running EX2010 SP3 RU6
In preparation for Windows patching I moved the active copy of DB2 active from EX2 to EX1, this took approx 20 seconds as per usual
Patching happened, and EX2 got a reboot
Later that evening I moved the active copy of DB2 back from EX1 to EX2
The move took 59 minutes and 32 seconds
During which time the DB status showed as mounting on EX2 and mailboxes where inaccessible [luckily this was out of hours]
The DB is 185 GB with 4 GB of logs at that time
There weren't ESE events related to playing transaction logs
There have been ESE 629 events in the log for a while showing... "While attempting to move to the next or previous node in a B-Tree, the database skipped over 25583 non-visible nodes in 73 pages... The database may benefit from widening the online maintenance
window..." but these warnings show up really quickly on our site even with a new database
We also have a problem that emerged approx 2 weeks ago where CPU runs at 100% for prolonged periods [mainly store.exe for 10/20/30 mins] and people get slow response times in Outlook, it's running on 4 x vCPU's and 18 GB RAM
Could the really slow mount time be related to DB corruption?
Thanks

Thanks for the feedback
This is not related to a dirty shutdown
According to Get-MailboxDatabaseCopyStatus etc all DB copies are healthy
I tested the DB activation again last night
Mailbox Database 2 is normally active on EX2
So we made the copy on EX1 active [server is on the same network] and this took 3 secs
When it came to making the same DB active on EX2 again it took 1 hr 46 mins 34 seconds!
We ran the task from EMC and the GUI did not hang, all the while it kept counting the hours, minutes & seconds
During this time mailboxes were unavailable, and the DB status showed as Mounting in EMC
From the Event Log, when ESE event 326 is finally logged there are some timings…
 Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.031, [4] 0.000, [5] 0.000, [6] 0.094, [7] 0.000, [8] 6386.578,
[9] 0.016, [10] 0.000, [11] 0.000, [12] 0.047.
And step 8 [whatever that is] took 6386 seconds while everything else flew
Of the 2 other Mailbox DB’s… DB1 took 7 seconds to activate on EX2 and DB3 took 32 minutes 41 seconds
Any ideas what is going on?
Thanks
Log Name:      Application
Source:        MSExchangeRepl
Date:          12/08/2014 21:02:02
Event ID:      2090
Task Category: Action
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
EX2.company.com
Description:
Database: Mailbox Database 2\EX2
Mailbox server:
EX2.company.com
A failover or switchover occurred. Database Mailbox Database 2\EX2 will be
mounted with no data loss.
Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          12/08/2014 21:02:05
Event ID:      9539
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
EX2.company.com
Description:
The Microsoft Exchange Information Store database "c21e43b5-feb8-4bde-a993-aca830cd71a3: /o=Company X/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=xxx.company.com/cn=Microsoft
Private MDB" was stopped.
Log Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          12/08/2014 21:02:05
Event ID:      1000
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
EX2.company.com
Description:
Attempting to start the Information Store "Mailbox Database 2".
Log Name:      Application
Source:        ESE
Date:          12/08/2014 21:02:05
Event ID:      102
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2:  The database engine (14.03.0162.0000) is starting a new instance (4).
Log Name:      Application
Source:        ESE
Date:          12/08/2014 21:02:06
Event ID:      105
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2: The database engine started a new instance (4). (Time=0 seconds)
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.109, [4] 0.079, [5] 0.000, [6] 0.000, [7] 0.000, [8] 0.000, [9] 0.219, [10] 0.000, [11] 0.000.
Log Name:      Application
Source:        ESE
Date:          12/08/2014 22:48:33
Event ID:      326
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:     
EX2.company.com
Description:
Information Store (4308) Mailbox Database 2: The database engine attached a database (4, X:\Database\Mailbox Database 2\Mailbox Database 2.edb). (Time=6386 seconds)
Internal Timing Sequence: [1] 0.000, [2] 0.000, [3] 0.031, [4] 0.000, [5] 0.000, [6] 0.094, [7] 0.000, [8] 6386.578, [9] 0.016, [10] 0.000, [11] 0.000, [12] 0.047.
Saved Cache: 1

Similar Messages

  • Cisco 5 with Exchange 2010 and Database Availability Groups

    Hi,
    Unity 5 was installed a long time. Recently installed with the latest ES88 to the system. The fact is we have Exchange 2007 (clustered) mailbox server in the network environment, and introduced the Exchange 2010 (with DAG activated).
    So far we didn't do any "re-partnering" from the Exchange 2007 to Exchange 2010. The end users are working fine by leaving voice message and can retreive their voice without too much issue, no matter where the End Users account are located, Exchange 2007 or Exchange 2010.
    But lately, there was some actions taken in the Exchange environment. Some Exchange 2010 mailstore databases in one of the Exchange 2010 server, with DAG has been activated.
    In this case, we are now unable to leave any voice messages to the end usrs. All the voice messages are now being held in C:\CommServer\UnityMTA.
    Want to ask, does Unity 5 and Exchange 2010 compatible with DAG? Also, is that my problem is caused by re-partnering server not taken place? If yes, which Exchange 2010 mailbox database server I should point to? Reason is, there will have 3 physical servers, and with several DB mailstore, if I select one of the physical server, and one of the D mailstore, will this be affected when the DAG is activated?
    Thanks
    Timothy

    Hi Yancy,
    If you're referring to integrating Microsoft Exchange 2010 with Cisco Unified Communications Manager (CUCM) 5.x for voicemail purposes, via a SIP Trunk, then you could certainly have a go at it (a Media Termination Point would be required and the codec would be G.711).   However, I'm not aware of anyone having properly tested it with CUCM 5.x; given that it's not having software maintenance releases written for it anymore.   CUCM 5.0 stopped having software maintenance releases written for it in June 2009, and CUCM 5.1 in February this year.
    The following Tech Tip is likely to assist:
    https://supportforums.cisco.com/docs/DOC-12544
    Kind regards,
    Craig

  • Exchange 2010 SP1 database size limit?

    I have seen several posts concerning exchange 2010 Standard database limit being 50GB but can be increased by modifying the registry. We were migrated from Exchange 2003 to Exchange 2010 by a vendor. My current database is  188.1GB. I searched the registry
    for the changes to increase the database form the 50GB limit but it does not look like they made the changes. What has me baffled is how can my database be 188.1 GB if they did not modify the registry?
    Thank you,
    Cecil

    So you only use Database Size Limit in GB registry if you want to hard set the size? From some of the posts I had seen they were saying it was 50 GB by default and could be expanded to 1TB by modifying the registry. I did not understand
    why the instructions included modifying the registry if it was not needed. I am by no means trying to dispute it just trying to understand. 
    Thanks for the reply.
    Cecil

  • Microsoft Exchange Server/Exchange 2010/Mailbox/Database Copy Mounted

    Good Morning everyone!!!
    I Have SCOM 2007 R2 CU5 Envoirnment and i am monitoring Microsoft Exchange 2010 SP1 Messaging infrastracture,
    I have Microsoft Exchange  2010 SP1 Monitoring MP, MP version is 14.2.71.0.
    Case:-
    When exchange is having issue with DAG, SCOM monitoring rule:- KHI: The database copy is not mounted on the local server. Another database copy may be mounted on a different server.
    is generating the alert but alert Description is only "    _ef4a8515_1cc0_48a9_aa12_92ba059a6eae_ " and rest of the things are blank
    and because of this ticketing team is unable to process these alerts,
    Impact:-
    Whenever DAG is unavailable, messaging team is not getting notification and because of this. Exchange services are failing down,
    Does anyone having this kind of issues on their exchange environment?
    I am looking solution for this issue, please let me know if anyone is aware about this.
    Regards, Ganesh M <!> Microsoft MPN - Member =========================================================== Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer
    your question. This can be beneficial to other community members reading the thread.

    Does anyone has updated information regarding Exchange 2010 DAG monitoring fix, <o:p></o:p>
    As i see there was exchange MP release on 31st Aug 2012
    ID
    Name
    Targets
    _ef4a8515_1cc0_48a9_aa12_92ba059a6eae_
    KHI: The   database copy is not mounted on the local server. Another database copy may   be mounted on a different server.
    Root   Management Server
    _EF51D339_22C5_49b3_8B6B_25002BE31D4A_
    KHI: Retry   Mailbox Delivery Queue Length - sustained for 90 minutes - Red(>1) - Hub   Transport.
    Root   Management Server
    _93558cf0_e063_45b1_b57a_0d4b53e0d615_
    KHI: The   Microsoft Exchange Information Store service (MSExchangeIS) isn't running.
    Root   Management Server
    My monitoring is affected for these rules which i mentioned below, here alerts
    information is shown as rule ID instead of Rule name. and we don’t get alert description
    for above rules when the generate alerts.<o:p></o:p>
    Response would be appreciated <o:p></o:p>
    Regards, Ganesh M <!> Microsoft MPN - Member =========================================================== Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer
    your question. This can be beneficial to other community members reading the thread.

  • I can't either mount for remove Exchange 2010 mailbox database file

    Yesterday I proceeded with moving Exchange 2010 database file to a newly installed hard drive because my "C" drive was running out of space. After dismouting both the mailbox database and the public folder database, I used EMC's  "move
    data path" wizard to move both the mailbox database and public folder database to "mailbox" folder in "D" drive.  The move was successful without an error, but when I opened "mailbox" folder in "D" drive, both
    the database file and public folder database files weren't there.  All the other files were moved, but the mailbox database file was gone.  
    Luckily I manually copied entire mailbox folder to another folder in "D" drive.  So I manually copied mailbox database file (it is about 20GB) to "d:\mailbox".  When I try to mount, I received the following error message.
    Microsoft Exchange Error
    Failed to mount database 'Mailbox Database 1658107303'.
    Mailbox Database 1658107303
    Failed
    Error:
    Couldn't mount the database that you specified. Specified database: Mailbox Database 1658107303; Error code: An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC
    error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3..
    An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3.
    Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3
    When I try to move the database path back to the original path, I received the following error message.
    Mailbox Database 1658107303
    Failed
    Error:
    There are no source files under the path:d:\emailbox\Mailbox Database 1658107303. Use the command Move-DatabasePath -ConfigurationOnly in the Exchange Management Shell to set the new path in Active Directory only.
    Exchange Management Shell command attempted:
    move-DatabasePath -Identity 'Mailbox Database 1658107303' -EdbFilePath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox database 1658107303\Mailbox Database 1658107303.edb' -LogFolderPath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox
    database 1658107303'
    EMC would not even delete the database file.
    I need help.  I need to mount my mailbox database file.  Please help.

    If the database was fine pre move I doubt it needs a repair, however if you want to validate do an eseutil /mh ReplaceWithYourDatabaseName.edb and post the results here
    did you move the logs as well or are they still in same location
    I have seen this before if everything is where its supposed to bea restart fixed it so I would recommend that you put the DB back into the  NEW D path and do a restart to see if that resolves the issue
    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 2010 - mailbox database in a DAG different sizes

    HI
    After a recent health check on our Exchange 2010 (SP3) environment I noticed that our mailboxes databases in the DAG, which consists of 4 Exchange Servers, had used
     different capacity.
    Could someone why the mounted database and the 3 healthy copies are not the same size?
    Many thanks

    Hi,
    Based on your description, the active database and passive database have different size.
    Apart from Willard Martin's suggestions, please update database copy using the following command and then check result.
    Update-MailboxDatabaseCopy -Identity DB -SourceServer activeserver
    Please make sure the passive databae copy has healthy state.
    Best regards,
    Belinda Ma
    TechNet Community Support

  • Import Exchange 2010 Mailbox Database .edb into Exchange 2013

    My Exchange 2010 server recently crashed I am in the process of setting up a new 2013 server. Is it possible to import the .edb file from my old server to the new server to recover the mailboxes?

    Hi sapper,
    Thank you for your question.
    We could not mount the database to new server simply, because all services are still on Exchange 2010. So we could refer to the following link:
    Perform disaster recovery by the following link:
    https://technet.microsoft.com/en-us/library/dd876880(v=exchg.141).aspx
    Migrate Exchange 2010 to Exchange 2013 by the following link:
    https://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
    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

  • Exchange 2010 Mailbox database Defragment

    Hi
    I have Exchange 2010 DAG with 4 Nodes .
    I want to know when shall i make offline fragment ?and what is the procedures ?
    thanks
    MCP MCSA MCSE MCT MCTS CCNA

    Hello,
    Please check if these applies:
    http://blogs.technet.com/b/rmilne/archive/2013/08/23/offline-defrag-and-dag-databases_2c00_-oh-my_2100_.aspx
    http://support.microsoft.com/kb/328804
    Since this forum is for general questions and feedback related to Outlook, if you need further assistance on this issue, I'd recommend you post your question to the forum for Exchange:
    https://social.technet.microsoft.com/Forums/office/en-US/home?category=exchangeserver 
    The reason why we recommend posting appropriately is you will get the most
    qualified pool
    of respondents, and other partners who read the forums regularly can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
    Steve Fan
    Forum Support
    Come back and mark the replies as answers if they help and unmark them if they provide no help.
    If you have any feedback on our support, please click
    here

  • Exchange 2010 - Mail Database Recovery after Database Portability Applied

    Background:
    We had a city-wide power failure  at Office A and as a result Exchange Server A (ES-A) was taken offline for an extended period of time.  The last good backup of ES-A-DB was from the previous business day.  The DR plan was enacted and the
    ES-A mailbox database (ES-A-DB) was recovered to Exchange Server B (ES-B) as ES-B-DB2.  Keeping in mind that a days worth of emails still reside on ES-A-DB.
    Process:
    I employed the database portability method when restoring the ES-A-DB to ES-B-DB2 at Office B.  I rehomed the exchange users in active directory to now use ES-A-DB2.  Users are working fine, activesync worked without issue.  All is well.
    I now face the situation where power has been restored to Office A and the server is available.  I have NOT turned this server on yet as I am not sure what the net affect will be on ES-A and ES-A-DB.
    The primary goal of the business is to recover the mail items from the missing day that was not backed up and recovered to ES-B-DB2.  What would be the best way to do achieve this objective?  
    This is what I am thinking, though its all theoretical since I've never been in this situation.
    - boot the Exchange Server with the network card disconnected
    - Dismount ES-A-DB from ES-A
    - Remove ES-A-DB from Exchange Org on ES-B
    - Process logs and put the ES-A-DB in a Clean state
    - mount as recovery database
    - copy differential mail items to ES-B-DB2 mailboxes
    Anyone have insight on this?
    Thanks for your help in advance.

    No need to dismount , remove from the org or boot the server w/o a NIC. The association between Exchange and the user is in AD and you already changed that when you set the new database with database portability.
    I would just follow the instructions for restoring back to their current production mailboxes (DB2).
    http://exchangeserverpro.com/restoring-mailbox-exchange-server-2013-recovery-database/
    Try it with a sample mailbox or two and see how it handles the conflict resolution for duplicates.
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Macbook Air 11  Late 2010 - Slow start up times

    I used to have a start up time of around 10-15 seconds with my mb air (11 inch 4gb ram core 2 duo 1.6 128gb SS). Now, it takes 40-50 seconds to fully load it.
    I've done the ff
    1) verified and fixed permisions
    2) used clean my mac
    3) used onyx
    4) ensured that my hard drive is the start up drive ( start up disk)

    Safe boot always takes longer because it checks the drive, clears caches, etc. Perhaps using Snow Leopard Cache Cleaner to clear out all your user, system, and font caches will help. As will doing this:
    Repair the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
    If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.

  • Exchange 2010 database mailbox restore after restore server form disaster recovery

    Hello ,
    after my exchange server failed  i am installed new server and recovered server
     successfully, i have 4 database mailbox all this database dismount and users cannot
    connect their mailbox , i have backup for all database(separate).
    what should to do to restore database mailbox. so that users can connect their mailbox
    thanks

    Hi activenew
    Thank you for your question.
    After we recover the exchange successfully by using “Setup /m:RecoverServer” cmdlet, the exchange server database is in the dismount status, then we will restore the exchange database by your backup tool. After we restore database, the database
    is mount, then our client can connect exchange server and send/receive email .
    We can refer to the follow link:
    http://exchangeserverpro.com/exchange-2010-mailbox-database-backup-restore-windows-server-backup/
    We can also refer to recovering an exchange database:
    http://technet.microsoft.com/en-us/library/bb124040(v=exchg.65).aspx 
    If there are any questions, please let me know.
    Best Regard,
    Jim

  • Exchange 2010 "This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000].

    Exchange 2010 "This message could not be sent. Try sending the message again later, or contact your network administrator.  Error is [0x80004005-00000000-00000000].
    In a mixed client environment, mostly Outlook 2010 & 2013 clients. Only Outlook 2013 clients (about only 4 mailboxes) are receiving this error immediately after sending an email. My temp band-aid at the
    moment is to: from the client, go into the "address book" & select a different address book like "Contacts" & then select the address again & select the Global Address List, which is the default. (it will have the users email
    + at the beginning of the field, it reads, Global Address List - (email of the user), then I close Outlook & open it back up, & the problem is solved. But on some mailboxes, not all, the issue comes back. From my research, I know that our individual
    mailboxes do not send out over 500 emails in one day. Most users will send out maybe 20 or 30 in one day, so I don't think it's that. 
    But I'm not sure if this is related, but I have noticed that the log files for the Exchange 2010 seems to only hold logs with date stamps of only a couple of days. It used to hold log files indefinitely until they were archived, deleted, etc. So, this is
    a new, unusual issue I have seen as well. 
    We have 2 .edb's, one active: 78 GB's and one disabled at 7 GB's. Exchange 2010 is running on Windows Server 2008 r2, Enterprise Ed. We have had Exchange 2010 running now for about almost 2 years now and this is the first time this particular issue has come
    up.
    Thanks.

    Hi,
    You can refer to the following steps to rebuild an Offline Address Book.
    1. Open EMS. Update OAB using the Update-OfflineAddressbook "offline address book" cmdlet. Restart Background Intelligent Transfer Service on the Mailbox server.
    2. Initiate OAB replication from mail box server to CAS server. Execute for each CAS server using the Update-FileDistributionService "CASServerName" cmdlet.
    3. Start Outlook and download OAB.
    What's more, here is an article for your reference.
    How to Quickly Rebuild an Exchange 2010 Offline Address Book
    http://social.technet.microsoft.com/wiki/contents/articles/7725.how-to-quickly-rebuild-an-exchange-2010-offline-address-book.aspx
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2010 coexist with exchange 2013

    Hi All ,
    Planning to have a coexistence scenario in my environment which is mentioned below
    Exchange 2010 - ambiguous url in place - OA enabled 
    For mapi/rpc traffic - mail.domain.in -  exchange 2010
    For https traffic - mail.domain.in - exchange 2010
    mail.domain.in will get resolved in to cas array in exchange 2010 .
    After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
    exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
    just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
    Note : 
    On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
    Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
    Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
    exchange server via exchange 2013 server.
    question : I would like to know above mentioned scenario is possible or not ?
    On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
    So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
    All of you tell me your valuable suggestions.
    Regards
    S.Nithyanandham

    Hi,
    Going Straight to the point... and answering your question...
    The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
    As per Exchange Team...
    In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
    breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
    their DNS cache expires after the shared FQDN is moved to CAS 2013.
    As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
    change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
    URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
    on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
    fix existing Outlook clients with the old value in the server field. 
    So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
    Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
    Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
    Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
    Outlook 2013: 15.0.4420.1017 (RTM or later)
    I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
    As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
    Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
    From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx> 
    Hope it can help you!
    Cheers,
    Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

  • SBS2011 (Exchange 2010 SP2) - limiting cache size doesn't appear to work

    Hi All,
    Hoping for some clarification here, or extra input at least.  I know there are other posts about this topic such as
    http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/thread/5acb6e29-13b3-4e70-95d9-1a62fc9304ac but these have been
    incorrectly marked as answer in my opinion.
    To recap the issue.  The Exchange 2010 store.exe process uses a lot of memory.  So much in fact it has a negative performance impact on the server (sluggish access to the desktop etc).  You can argue about this all day - it's by design
    and shouldn't be messed with etc but the bottom line is that it does use too much memory and it does need tweaked.  I know this because if you simply restart the Information Store process (or reboot the server) it frees up the memory and the performance
    returns (until its cache is fully rebuilt that is).  I have verified this on 4 different fresh builds of SBS2011 over the last 6 months. (all on servers with 16GB RAM)
    I have scoured the internet for information on limiting how much memory exchange uses to cache the information store and most articles point back to the same two articles (http://eightwone.com/2011/04/06/limiting-exchange-2010-sp1-database-cache/
    and
    http://eightwone.com/2010/03/25/limiting-exchange-2010-database-cache) that deal with exchange 2010 and exchange 2010 SP1, notably not exchange 2010 SP2.  Ergo most articles are out of date since exchange 2010 SP2 has been released since these articles
    were posted.
    When testing with our own in house SBS2011 server (with exchange 2010 SP2) I have found that specifying the min, max and cache sizes in ADSIEDIT has varying results that are not in line with the results documented in the articles I mentioned above. 
    I suspect the behaviour of these settings has changed with the release of exchange 2010 SP2 (as it did between the initial release and SP1).
    Specifically here's what I have found using ADSIEDIT;
    If you set the msExchESEParamCacheSize to a value - it doesn't have any effect.
    If you set the msExchESEParamCacheSizeMax to a value - it doesn't have any effect.
    If you set the msExchESEParamCacheSizeMin to a value - it always locks the store.exe process to using exactly this value.
    I have also tested using combinations of these settings with the result that the size and max size values are always ignored (and the store.exe process uses the maximum available amount of memory - thus causing the performance degradation) but as soon as
    you specify the min value it locks it to this value and it doesn't change.
    As a temporary solution on our in-house SBS2011 I have set the min value to 4GB and it appears to be running fine (only 15 mailboxes though).
    Anyone got some input on this ? thank you for your time.

    I concur with Erin. I'm seeing the same behaviour across all SBS2011 boxes, whether running SP1, SP2 or SP3.
    If a minimum value is set, the store cache size barely rises above the minumum. I have one server with 32GB RAM. Store.exe was using 20GB of RAM, plus all the other Exchange services which total 4GB+. That left virtually no free RAM and trying to do
    anything else on the server was sluggish at best.
    All the advise is that setting a maximum alone has no effect and a minimum must be set too. But when set, the store cache size barely rises above the minimum. I have set a 4GB minimum and 16GB max, but 5 days later it's still using only slightly more than
    4GB and there's 8GB free. Now the server as a whole is responsive, but doing anything with Exchange is sluggish.
    Just saying leave Exchange to manage itself is not an answer. The clue is in the name - Small Business Server. It's not Exchange Only Server - there are other tasks an SBS must handle so leaving Exchange to run rampant is not an option. Besides, there are
    allegedly means to manage the Exchange cache size - they just don't apparently work!
    I'm guessing nobody has an answer to this so the only solution is to effectively fix the cache size to a sensible value by setting min and max to the same value.
    Adam@Regis IT

  • Exchange 2010 - Decommissioning Exchange 2007 Coexistence and Removal of Public Folders

    We are about to decommission exchange 2007, currently in coexistence with Exchange 2010.
    We do not want to use ANY public folders in exchange 2010 going forward. Will do this after decom of 2007:
    http://technet.microsoft.com/en-us/library/dd876883(v=exchg.141).aspx
    I see this in the outlook connection status in outlook:
    I have changed all Exchange 2010 mailbox databases to use a temporary 2010 public folders db named "public1" so that it is not communicating with the 2007 mailbox virtual server. However, the exact same connection status appears after I changed
    the 2010 mailbox DBs to use a 2010 public folder db instead of the old 2007.
    Question is, is it safe to decom the 2007 environment now? Is it normal to still have a connection to 2007  in "connection status" in outlook when the users mailbox is on a 2010 mailbox db? Is this connection related to public folders or something
    else that needs modified before decom?
    Thanks,
    Josh

    So, that wasn't the answer. I switched the Public folder DB on each mailbox database to a exchange 2010 server, PF DB, but hadn't actually moved any data from 2007 to 2010. 
    I didnt realize this is needed when we don't use public folders except for free-busy, default, etc.
    What is the correct way to move the default public folders to a 2010 public folder?
    I'm using the below URL as a template to migrate this info to a 2010 PF db.
    https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
    "The user Public Folders then need to be replicated to the Exchange 2010 Public Folder database as well. It is possible to manually configure
    all Public Folders with a new replication partner, but it’s better to use PowerShell scripts that Microsoft delivers with Exchange Server 2010. Open the Exchange Management Shell and navigate to the Scripts directory
    by entering the CD $ExScripts command,
    and execute the following script:
    AddReplicaToPFRecursive.ps1 -Server 2007MBX -TopPublicFolder "\" 
    -ServerToAdd 2010MBX"
    My question is, do I have to do this "3rd step" since I don't think i have any custom "user public folders". Is this the user's free busy that I have to migrate, or is this author referring to custom PF db info?
    Do I have to have public folders for free-busy and default exchange services at all in 2010?

Maybe you are looking for