Exchange server 2010 mailbox role memory 100% - Virtual machine

Dear All
Please i need your help to accomplish this work.
we are using two mailbox servers and two hab/cas servers and around 2000 users are using mailbox in my organization.
Each mailbox server roles having 16GB RAM.
all the exchange server running on virtaul machine. until last week we didn't experience any problem. since last week memory and cpu consuming 100% in one of mailbox server.
i checked what are the process running while consuming 100% but couldn't  found any fishy process.
Parthiban selvaraj

Hi parthibanselvaraj,
The behavior you see on the mailbox servers for store.exe is completely normal. This is in order to allocate as much data in memory address space as possible, so that each user experience great performance in their Outlook clients.
If another process should need the more memory, the Exchange store.exe process will released it as required. This is by design.
By default, the msExchESEParamCacheSizeMax key is not set, which means the store can allocate the memory it needs dynamically. ESE (store.exe) will grow the cache to consume almost all available RAM on the server if there is no other memory pressure on the
system For example, if the server contains 16gb physical memory, if there is no other memory pressure, one could expect that the store.exe process will grow to use up to 14gb memory (16gb minus 2gb allocated to Kernel mode). This much larger database cache
size results in greatly reduced disk I/O, and is preferred anyways, as reading information from memory is much faster than reading information from disk. If memory pressure occurs, as when other applications request/require memory, ESE will appropriately shrink
the size of the database cache. It’s not recommended to modify the msExchESEParamCacheSizeMax attribute of the information store object. Lowering this value may degrade performance, in terms of server performance as well as in terms of end-user experience.
Hope it can be helpful.
Best regards,
Eric

Similar Messages

  • Exchange Server 2010 Mailbox Role Installation Problem

    I got  Error in Install Software Exchange Server 2010 64 bit. Which I am Given Below.
    1. Active Directory Does not exist and can't be Concatenated.
    2. This System Has no Domain.
    please help me regarding install Software and please give  any solution.
    How to Install.

    Hi,
    We can't install the actual Exchange server role on Windows 7, we can install the Management Tools on it. For more information about this, please see the "Supported operating system platforms" section in the following article.
    http://technet.microsoft.com/library/ff728623(v=exchg.150).aspx
    Do you want to install Exchange 2010 Management Tools on Windows 7 64-bit?
    If so, please make sure you meet the Exchange 2010 system requirements.
    You can refer to the following article to install the Exchange 2010 Management Tools.
    http://exchangeserverpro.com/exchange-2010-install-management-tools/
    Best regards,
    Belinda
    Belinda Ma
    TechNet Community Support

  • Exchange Server 2010 with SP3 Management Tools

    Recently I have installed brand new Exchange Server 2010 with SP1 in my test domain. Afterwards I upgraded it to Exchange Server 2010 with SP3. On client machine (Windows 7 Pro with SP1 x64) I run setup.exe for Exchange Server 2010 with SP1 installation
    DVD to install Management Tools. All checks passed successfully but after installation was completed there was an error in EMC:
    The World Wide Web Publishing Service (W3SVC) isn't running on any Exchange servers in the site.  If you want to connect to Remote Powershell, this service must be running.  Make sure that the W3SVC is running on at least one Exchange server.
    Of course service is running. I read this has something to do with different versions of Exchange Server itself and Management Tools. Since there is no installation of Exchange Server 2010 with SP3 how to solve this? I assume if I have installation of Exchange
    Server 2010 with slipstreamed Service Pack 3, management tools installed from this installation would work.
    Also does this mean that, if I have working tools for Exchange Server and SP for it is installed later, tools will stop functioning?

    I would install SP3 on all servers and workstation as SP1 and SP2 aren't supported anymore and see how it is behaving...
    http://blogs.technet.com/b/rmilne/archive/2013/01/04/end-of-exchange-2010-sp1-support.aspx

  • Problems installing Mailbox role on Exchange Server 2010 SP3

    I am in the process of installing Exchange Server 2010 SP3 on a Windows Server 2012 server in order to migrate our existing Exchange 2003 server. Everything went well with the installation process until I went to add the Mailbox server role, which is giving
    me the following error (from the log file):
    [05/03/2013 21:58:09.0090] [1] Executing: 
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
    [05/03/2013 21:58:09.0105] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'TAM-FS2.tacomaartmuseum.org', Preferred Global Catalog: 'TAM-FS2.tacomaartmuseum.org', Preferred Domain
    Controllers: '{ TAM-FS2.tacomaartmuseum.org }'
    [05/03/2013 21:58:09.0105] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [05/03/2013 21:58:09.0276] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" 
    [05/03/2013 21:58:09.0344] [2] Process standard output: 
    [05/03/2013 21:58:09.0344] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
    [05/03/2013 21:58:09.0347] [2] [ERROR] Unexpected Error
    [05/03/2013 21:58:09.0347] [2] [ERROR] Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0350] [2] Ending processing Start-SetupProcess
    [05/03/2013 21:58:09.0350] [1] The following 1 error(s) occurred during task execution:
    [05/03/2013 21:58:09.0350] [1] 0.  ErrorRecord: Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0350] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0351] [1] [ERROR] The following error was generated when "$error.Clear(); 
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 87.".
    [05/03/2013 21:58:09.0351] [1] [ERROR] Process execution failed with exit code 87.
    [05/03/2013 21:58:09.0351] [1] [ERROR-REFERENCE] Id=MailboxComponent___13A8A6B7DE0A4fe3BEB5CB1D86105DA3 Component=EXCHANGE14:\Current\Release\PIM Storage\Content Indexing
    [05/03/2013 21:58:09.0351] [1] Setup is stopping now because of one or more critical errors.
    [05/03/2013 21:58:09.0351] [1] Finished executing component tasks.
    [05/03/2013 21:58:09.0393] [1] Ending processing Install-MailboxRole
    I've searched all over but can't seem to find any reference to "exit code 87" - does anyone have any ideas?
    Thanks,
    Matt

    Error 87 -with these details below - and a fix. The situation that got me here by the way was an incomplete install that was uninstalled, then installed again.
    [02/24/2014 06:49:06.0967] [2] Active Directory session settings for 'Start-SetupProcess' are: View Entire Forest: 'True', Configuration Domain Controller: 'xxxxxxxxxxxxxxx', Preferred Global Catalog: 'xxxxxxxxxxxxxxxxxxxxxxxx', Preferred Domain Controllers:
    '{ xxxxxxxxxxxxxxxxxxxxxxx }'
    [02/24/2014 06:49:06.0967] [2] Beginning processing Start-SetupProcess -Name:'C:\Windows\system32\wevtutil.exe' -Args:'im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man" '
    [02/24/2014 06:49:06.0967] [2] Starting: C:\Windows\system32\wevtutil.exe with arguments: im "C:\Program Files\Microsoft\Exchange Server\V14\Scripts\TSCrimsonManifest.man"
    [02/24/2014 06:49:07.0592] [2] Process standard output:
    [02/24/2014 06:49:07.0592] [2] Process standard error: The value for channel property Type contains an invalid value. The parameter is incorrect.
    [02/24/2014 06:49:07.0592] [2] [ERROR] Unexpected Error
    [02/24/2014 06:49:07.0592] [2] [ERROR] Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0592] [2] Ending processing Start-SetupProcess
    [02/24/2014 06:49:07.0592] [1] The following 1 error(s) occurred during task execution:
    [02/24/2014 06:49:07.0592] [1] 0.  ErrorRecord: Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0592] [1] 0.  ErrorRecord: Microsoft.Exchange.Configuration.Tasks.TaskException: Process execution failed with exit code 87.
    [02/24/2014 06:49:07.0608] [1] [ERROR] The following error was generated when "$error.Clear();
              $wevtutil= join-path (join-path $env:SystemRoot system32) wevtutil.exe;
              $manifestPath = [System.IO.Path]::Combine($RoleInstallPath, "Scripts\TSCrimsonManifest.man");
              Start-SetupProcess -Name:"$wevtutil" -Args:"im `"$manifestPath`" "
            " was run: "Process execution failed with exit code 87.".
    [02/24/2014 06:49:07.0608] [1] [ERROR] Process execution failed with exit code 87.
    I found I could fix this by removing the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\Microsoft-Exchange-Troubleshooters/Operational
    and everything underneath it.
    My guess is that wevtutil didn't like adding an event log where it already existed but was slightly different in setup (no idea how, exactly).
    After 24 hours I'll try post again - giving things time to make sure they are actually working.

  • Processor requirments for Exchange Server 2010 roles

    I am looking at migrating from Exchange Server 2003 to Exchange Server 2010.  My exchange environment has 350 mailboxes.  Can anyone tell me how much processing power will be required for each exchange role to run on VMware?  I know Microsoft's recommendation is 1GB per core.

    Hi Amyraghunath,
    It's hard to give general guidance on sizing Exchange 2010 since it is heavily dependent on your specific configuration.  The key number to use for sizing the Mailbox server role is to know the number of messages sent/received per day.  That number will help you size CPU and memory for your Mailbox server which will ultimately drive the sizing for the other roles.
    A good place to start is the following article: http://technet.microsoft.com/en-us/library/ee712771(v=exchg.141).aspx
    That article describes the impact of messages sent/received per day has on sizing the Mailbox server and shows the math that is involved as well.  Once you know how to size the Mailbox server, you can size the other roles as well.
    You can also use the Exchange Mailbox sizing calculator here ( Exchange 2010 Server Role Requirements Calculator - Exchange Team Blog - Site Home - TechNet Blogs), though be careful with this because if you aren't sure what you're entering in here you could end up with incorrect results.
    Finally, here are some other great links that should be helpful to you in sizing your Exchange 2010 environment on vSphere:
    http://technet.microsoft.com/en-us/library/dd346700.aspx
    http://technet.microsoft.com/en-us/library/dd346699.aspx
    VMware: Run Microsoft Exchange Server Software on a Virtualization Platform - United States
    Hope these links help!  If not feel free to post back here.
    Matt
    http://www.thelowercasew.com

  • Exchange Server 2010 - DAG - Physical and Virtual

    Hi All,
    we are trying to configure Exchange Server 2010 SP1 DAG with TWO Servers, we are getting the error sector size on log file header was mismatch
    1) Physical Server -  when we check the sector size on log file - 512 bytes   (RAID5)
    2) Virtual Server  -  when we check the sector size on log file - 4096 bytes
    is there any workaround to solve this issue or do i need to re-install the physical server with 4096 sector size..
    When i check the Volume details on both machine
    1)
    Bytes Per Sector  :               512
    Bytes Per Physical Sector :       <Not Supported>
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024
    2)
    Bytes Per Sector  :               512
    Bytes Per Physical Sector :  4096
    Bytes Per Cluster :               4096
    Bytes Per FileRecord Segment    : 1024
    MCITP

    Hi Jared,
    I've got a question regarding your answer.
    We have an existing Exchange 2010 DAG configuration with 3 mailbox servers in NL and 3 in the UK.
    2 for normal databases at each site and 1 for Archive databases at each site.
    The current Mailbox servers for the Archive databases are Hyper V 2008 R2 based VM's with a passthrough for storing the databases.
    We now want add 1 new Mailbox server for storing archive databases at each site and add them to the DAG.
    Can we use Windows 2012 Hyper-V hosts and create the new VM's with 4k sectorsize vhdx files for the new mailbox servers ?
    Regards
    Misha Verhoeven 

  • SCOM 2012 R2 & Exchange Server 2010 SP3 - Mailbox services not monitored

    Having done everything depicted in Exchange Server 2010 MP I still have trouble with some Exchange services - they are in not monitored state (five days passed):
    Mailbox All Database Services - Default-First-Site-Name
    Mailbox Database Service - Management - test.local
    Mailbox Database Service - PublicFolders - test.local
    Mailbox Database Service - Users - test.local
    Mailbox Many Database Service - Default-First-Site-Name
    OfflineAddressBook Service - Default-First-Site-Name
    Why is this happening? Since monitoring exchange mailbox databases is one of the most important tasks SCOM should be doing I assume something wrong is going on here. However there are no errors or alerts in SCOM console nor in OpsMgr
    log on Exchange server itself.

    Hi There,
    Did you install the Microsoft Exchange monitoring correletion service while importing the Exchange 2010 management pack ?
    Does your MS have RMS Emulator role ? As many alerts in the Exchange 2010 MP are targetted to Root management server class.
    Also did you configure Test mailboxex and stuff post Exchange 2010 Import ?
    Did you analyse the Ops manager Event logs in the MS and Agent ? Can you post the critical and Warnign events here.
    Also is Agent proxy enabled ?
    Also is the Action account of the Agents System or Domain account ?
    Also refer: http://blogs.catapultsystems.com/jcowan/archive/2013/03/26/opsmgr-2012-and-2007-exchange-server-2010-monitoring-management-pack-how-to-perform-the-optional-configurations-for-synthetic-transactions-and-kerberos-authentication.aspx
    Gautam.75801

  • How to configure Mailbox Read-Only access for Mailbox's owner on Exchange Server 2010?

    I have to configure the Exchange Server 2010's mailbox to only grant Read-Only Access on the mailbox's owners.  So they can only allowed to read their messages and cannot modify or remove them.  Are there any references or methods to do?

    Hi,alexchy8
    We can make use of 2 PowerShell commands to achieve this goal.
    Add-MailboxPermission and Add-MailboxFolderPermission.
    Execute the Add-MailboxPermission command to delegate the read permission at mailbox level.
    Execute the Add-MailboxFolderPermission command to delegate the required permissions on specific folders inside the mailbox.
    You can read the following article as reference:
    http://www.exchangedictionary.com/articles/assign-read-only-mailbox-permission-on-exchange-2010-2013-powershell
    Note: Microsoft is providing this information as a 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.
    Best Regards.

  • Exchange Server 2010 Room Mailboxes Double Booking

    We are have several room mailboxes setup on Exchange Server 2010 and are having an issue with rooms being double booked.
    I have "Allow Conflicting Meeting Requests" unchecked on the Resource Policy Tab but if a user try's to book a room that is already reserved it gets accepted and put on the calendar.
    How do I stop this from happening?
    Here are the settings for the room:
    AutomateProcessing                  : AutoAccept
    AllowConflicts                      : False
    BookingWindowInDays                 : 365
    MaximumDurationInMinutes            : 1440
    AllowRecurringMeetings              : True
    EnforceSchedulingHorizon            : True
    ScheduleOnlyDuringWorkHours         : False
    ConflictPercentageAllowed           : 0
    MaximumConflictInstances            : 0
    ForwardRequestsToDelegates          : True
    DeleteAttachments                   : True
    DeleteComments                      : False
    RemovePrivateProperty               : True
    DeleteSubject                       : False
    AddOrganizerToSubject               : True
    DeleteNonCalendarItems              : True
    TentativePendingApproval            : True
    EnableResponseDetails               : True
    OrganizerInfo                       : True
    ResourceDelegates                   : {}
    RequestOutOfPolicy                  : {}
    AllRequestOutOfPolicy               : False
    BookInPolicy                        : {}
    AllBookInPolicy                     : True
    RequestInPolicy                     : {}
    AllRequestInPolicy                  : False
    AddAdditionalResponse               : False
    AdditionalResponse                  :
    RemoveOldMeetingMessages            : True
    AddNewRequestsTentatively           : True
    ProcessExternalMeetingMessages      : False
    RemoveForwardedMeetingNotifications : False
    MailboxOwnerId                      : gsc.local/Users/Board Room
    Identity                            : gsc.local/Users/Board Room
    IsValid                             : True

    The most common cause of this issue is that you have both Outlook Direct Booking and AutoAccept enabled. To fix this logon to the Mailbox using Outlook and disable direct booking see (or use a script) http://blogs.technet.com/b/exchange/archive/2013/07/15/a-significant-update-to-remove-directbooking-script-is-now-available.aspx
    and   http://blogs.technet.com/b/mohammad_qassim/archive/2011/05/22/meeting-rooms-double-booking-in-exchange-2007.aspx
    Cheers
    Glen

  • Exchange Server 2010: Convert Mailbox to MailUser

    Dear All,
    I plan to cutover migration exchange on-premises to exchange online with single-sign-on.
    http://community.office365.com/en-us/w/exchange/835.cutover-exchange-migration-and-single-sign-on.aspx
    In Step 2: It need to Convert on-premises mailboxes to mail-enabled users. it has only instruction guide for exchange server 2003 and 2007. it didn't have for exchange server 2010 or 2013.
    Could you guide what is the best solution to convert mailbox in exchange server 2010?
    BR,
    Khemarin
    [email protected]

    Hi Khemarin,
    You can use the following cmdlet to convert a mailbox to a MailUser:
    $DomainController = (Get-ADServerSettings).DefaultConfigurationDomainController.domain
    $MailboxList= Get-Mailbox
    foreach ($Mailbox in $MailboxList) {
        Disable-Mailbox -Id $mailbox.Identity -Confirm:$False -DomainController $DomainController
        Enable-MailUser -Id $mailbox.Identity -ExternalEmailAddress ($mailbox.alias +"@domain.com") -DomainController $DomainController
        Set-MailUser -Id $mailbox.Identity `
         -DomainController $DomainController `
         -CustomAttribute1 $Mailbox.CustomAttribute1
    For more information, here is an article for your reference.
    Converting a Mailbox to a MailUser
    http://mikecrowley.wordpress.com/2010/12/09/converting-a-mailbox-to-a-mailuser-and-not-loosing-attributes/
    Note: Microsoft is providing this information as a convenience to you. The site is not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any information found there. Please make sure that
    you completely understand the risk before retrieving any suggestions from the above link.
    Hope this can be helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Amy Wang
    TechNet Community Support

  • Use Different mailbox or same mailbox if setup two accepted domains in one Exchange Server 2010

    Hi,
    I want to know if I setup two accepted domain in one Exchange Server 2010, will it have another mailbox or use same mailbox?

    Hi,
    Based on my knowledge, to add a new name in the accepted domain list is to add a SMTP address suffix for the mailboxes. Thus, it uses the same mailbox if you setup two accepted domain in one Exchange Server 2010.
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Recover mailbox from Exchange server 2010 information store to exchange server 2013

    I have a big issue. I have a correct exchange server 2010 where the active directory is corrupt but the information store is good.
    I would like to recover a couple of mailboxes to an exchange server 2013.
    Can anyone give me a detailed walk through of how I can accomplish this?
    Thank in advance

    Well if your AD is messed up that leaves you in a jam for sure because;
    1. Database portability ONLY works within the same organization, so you cannot just install a new 2010 server in a completely different forest and then move the DB in hopes that DB portability will work.
    2. As Ed said you should build a new Exchange 2010 server and use portability but it has to be in the same organization.
    3. Here is a good article on how to accomplish
    http://exchangeserverpro.com/exchange-2010-database-portability-disaster-recovery/
    4. Now if you by chance have an AD backup before it went south you could build a separate network with same names etc just keep it isolated from the production server and then restore AD to that environment and you could then use DB portability.
    That said if you don't have any other machines to work with then you are in a bit of a pickle and will have to use a 3rd party product to get to that data within the 2010 DB.   We make a product that can do this (DigiScope), however if you don't
    have any budget to handle its a non-issue.
    The only other thing you could consider is to restore your AD from a previous point in time, however BE VERY CAREFUL if you consider this since it could cause more issues then you have now.
    BTW if you AD is messed up, where are you putting this new 2013 server?
    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 automapping issues after updated to Rollup 5 for Exchange Server 2010 SP3

    Hi,
    i have problem with Outlook Uses who have Full Access on other mailbox.
    An authentication window pop up very time a user start Outlook.
    If i remove the access everything is ok.
    if i insert manual the mailbox everything is ok
    The System was for 3 days ago updated to Rollup 5 for Exchange Server 2010 SP3
    Before the update, was no issue.
    i will appreciated any help
    Thanks

    Same issue here. Ever since we installed Update Rollup 5 for SP3 Exchange 2010 mailboxes that were auto mapped are not accessible. They all get the same error.
    Cannot expand the folder. The set of folders cannot be opened. The attempt to log on to the Microsoft Exchange has failed.
    What I have been doing is removing the users permission, then adding them back using the noautomap switch in Powershell. After doing that, the user manually adds the mailbox and all is well.
    Just a note here, I suspect it may have something to do with the version of Outlook 2010. We are running an older version here. I think only SP1 with no other incremental updates. Office is up to SP2. Also, one of the users I was working with could not access
    the mailbox no matter what we tried but she can walk over to another workstation and open Outlook and access the very same mailbox so that pretty much proves its software related particularly with Outlook.
    I cannot reproduce the problem on a workstation (XP) with a newer version of Outlook.
    This has been wearing me out and I suspected the Update Rollup all long. Now I am confident as others are having the same problem. If you find out anything on how to fix this other than the steps above, let me know.

  • Exchange Server 2010 get error HResult = -2147024891 when Accessing Virtual Directories on CAS

    I've just installed a Exchange 2010 server in an Exchange 2007 server environment.
    The 2007 enviroment include two exchange server "Server-A" and "Server-B"
    and "Server B" has dead on hardware issue for half year.
    When I go to Microsoft Exchange On-Premises -> ServerConfiguration -> Client Access and receive the following error message
    An IIS directory entry couldn't be created. The error message is Access is denied. . HResult = -2147024891 It was running the command 'Get-OabVirtualDirectory'
    I try run the “Get-OwaVirtualDirectory” in powershell and get following result
    From the power Shell command prompt .. Run
    [PS] C:\Windows\system32>Get-OwaVirtualDirectory
    An IIS directory entry couldn’t be created. The error message is Access is denied.
    . HResult = -2147024891
    + CategoryInfo : NotInstalled: (<Server-B\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
    , IISGeneralCOMException
    + FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
    I've google that i need to add "Exchange Trusted Subsystem" as a member in local admin group in Exchange 2007
    but my exchange 2007 "Server-B" already dead, how should i fix it?
    Appreciate for any help!!

     re-create the new virtual directories does not work for me.
    still got the error
    An IIS directory entry
    couldn’t be created. The error message is Access is denied.
    . HResult = -2147024891
    + CategoryInfo : NotInstalled: (<Server-B\Exchange (Default Web Site):ADObjectId) [Get-OwaVirtualDirectory]
    , IISGeneralCOMException
    + FullyQualifiedErrorId : 4B12EB5D,Microsoft.Exchange.Management.SystemConfigurationTasks.GetOwaVirtualDirectory
    I don't understand why change new exchange server 2010 setting require me to have permission to access
    my dead exchange server 2007

  • Migrate from Exchange Server 2010 sp3 to 2013 sp1

    I have one Exchange Server 2010 SP3 server (300 mailboxes) installed on Windows Server 2008 R2 SP1 with three major roles on it (CAS, MB and HT) - typical installation. Edge Transport server is not installed thus for controlling of mail flow
    Symantec Messaging Gateway Virtual Appliance is used as Smart Host. UM server is not installed either. I set up test domain environment where I installed one domain controller (Windows Server 2008 R2 SP1) and one Exchange Server 2010 SP3 (Windows
    Server 2008 R2 SP1) at first place and yesterday I did everything necessary to install Exchange Server 2013 SP1 on new test virtual server running Windows Server 2012 R2 which I successfully did.
    Now in test domain I have two Exchange Servers (2010 SP3 and 2013 SP1). Is there any 100% reliable documentation with all actions that had to be taken in order to successfully migrate Exchange Server 2010 SP3 to 2013 SP1? I would want to know what
    needs to be done not only for my scenario but also for other scenarios (DAG, CAS array, Edge, UM, multiple HT servers . . .) since I am interested in digging deep into Exchange Server 2013.
     

    Hi BoxiKG,
    In addition to the above mentioned, and this for your reference:
    Upgrade from Exchange 2010 to Exchange 2013
    http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
    Best regards,
    Eric

Maybe you are looking for