Exchange 2013 Virtual

Hello all,
We are going to deploy Exchange 2013 on virtual Infra with Hyprer-v
I need to know when we place the Exchange VMs, where should i put ? Can we keep it as like VHD files or any other option ?
we have 2000 users with UM.
regards

Hi,
Block level storage is a storage type that presents itself to servers using industry standard Fibre Channel and iSCSI connectivity mechanisms.
For more information, you can refer to the following article:
http://www.techrepublic.com/blog/the-enterprise-cloud/block-level-storage-vs-file-level-storage-a-comparison/3766/#.
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.
As far as I know, all storage used by an Exchange guest machine for storage of Exchange data must be block-level storage because Exchange 2013 doesn't support the use of network attached storage (NAS) volumes, other than in the SMB 3.0 scenario outlined
later in this topic. Also, NAS storage that's presented to the guest as block-level storage via the hypervisor isn't supported:
http://technet.microsoft.com/en-us/library/jj619301(v=exchg.150).aspx
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

SBS2011 - Cross domain Migration to Server 2012 R2 w/ Exchange 2013

I am attempting to find the best way to do this, and any input/guidance would be greatly appreciated.
Source Server: SBS 2011 Standard - Internal domain costco.local
Target Server: Server 2012 R2, 2 virtuals, one for the domain controller, one for Exchange 2013 - Internal domain ad.costco.com
I know that in order to establish a trust relation, I must add a secondary domain controller to the SBS2011 domain and transfer FSMO roles. My question is, can I use a trial Server 2008 R2 as an interim DC, create the trust, use ADMT to migrate user
accounts to the new domain and move mailboxes from the SBS server with the trust established on the Server 2008 DC? Or do I have to install an interim exchange server and move the mailboxes and remove the SBS server from the domain?
If that is the case, can I use a 180 Trial of Server 2008 R2 and Exchange 2010 on two separate virtuals on the old domain, move all user accounts and mailboxes to a standard domain temporarily. Then from the standard domain move user accounts and mailboxes
to the Server 2012 R2 DC and Exchange 2013 virtual?
It would be great if I could just establish a trust with with a second DC with SBS and move user accounts and mailboxes to the new internal domain, but I'm not sure if that is possible. Any insight would be greatly appreciated!

SBS can't do trusts but the migration prep tool temporarily allows them I believe. Have a look at this link dealing with migration to 2012 essentials from SBS, it doesn't deal with exchange though:
https://technet.microsoft.com/en-us/library/jj721754.aspx
There is also a recent thread "Migrating from SBS 2011 to Server 2012R2 Standard & Exchange 2013" that may have some info.
-- Al

SP1 for Exchange 2013 install fails with ECP virtual directory issues and now transport service won't start and mail is unavailable

SP1 for Exchange 2013 install failed on me with ECP virtual directory issues:
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ecp (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The virtual directory 'ecp' already exists under 'server/name'.
Parameter name: VirtualDirectoryName".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
Error:
The following error was generated when "$error.Clear();
          $BEVdirIdentity = $RoleNetBIOSName + "\ECP (name)";
          $be = get-EcpVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
          if ($be -eq $null)
          new-EcpVirtualDirectory -Role Mailbox -WebSiteName "name" -DomainController $RoleDomainController;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
          set-EcpVirtualdirectory -Identity $BEVdirIdentity -InternalUrl $null -ExternalUrl $null;
          . "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeECPAppPool" -Version:"v4.0";
        " was run: "The operation couldn't be performed because object 'server\ECP (name)' couldn't be found on 'DC0xx.domain.com'.".
!! And now transport service won't start and mail is unavailable !!
Any help would be appreciated.
I have removed the ecp site from default site and attempting to rerun SP1 now. I do not have high hopes. :(

Hi,
Thanks for your response.
From the error description, you need to manually remove the ECP with IIS manager in both the Default Web Site and the Exchange Back End firstly. And then continue the upgrade to check the result.
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 or SP1 Installaing Single CAS Role not installaing EWS virtual directory in mixed environment

Hi Experts,
I am facing issue while installing exchange 2013 sp1 in mixed(2007, 2010 and 2013) environment, the issue is: CAS role not installing/configuring "Echangeweb" (ews) virtual directory if i install only CAS role. If i install CAS role and mailbox
role then there is no issue, everything is fine.
In single CAS role installation, "EWS" folder is creating inside "Exchangeweb" folder but it shows empty folder.
If any one have any idea please let me know, why this is happening? was i am doing anything wrong while installing?
Regards,
Ravi Nalla
Hewlett-Packard
ravinalla

Hi Ravi,
Agree with Martina. I install Exchange 2013 CAS server and Mailbox server separately. "exchweb" folder exists on Mailbox server only. Here is the exchweb folder information on Mailbox server for your reference.
Here is the ews folder information on CAS server for your reference.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Re-Create the "Exchange" virtual directory in the "Exchange Back End" Site on Exchange 2013

Sorry for this stupid question.
In IIS, I accidentaly deleted the "Exchange" virtual directory in the "Exchange Back End" Site on Exchange 2013 (Mailbox Role).
What I need to know is the physical path to re-create it.
Thanks

Check http://blogs.technet.com/b/get-exchangehelp/archive/2013/02/07/managing-exchange-2013-iis-virtual-directories-amp-web-applications.aspx

Exchange 2007 to 2013 virtual directories

I'm gathering information before I do my transition to Exchange 2013. One thing I'm not sure about is the virtual directory for OWA. The information I have gathered states to change the internal/external URL to legacy.domain.com. However
my virtual directory for OWA are not defined. How do I approach that? do I just not set anything?
Thanks

I planned on configuring each like this below. I'm not using UM but that is also good to know. Outlook Anywhere is enabled on the 2007 side. This is also just a single exchange server
Internal DNS and Certificate will have these entries.
mail.mydomain.com - Points to Exchange 2013
autodiscover.mydomain.com - Points to Exchange 2013
legacy.mydomain.com - Points to Exchange 2007
Set the Virtual Directories on Exchange 2013
Set-OutlookAnywhere -Identity "EXC02\RPC (Default Web Site)" -IISAuthenticationMethods Basic,NTLM
Set-ECPVirtualDirectory -Identity "EXC02\ecp* -InternalURL
https://mail.mydomain.com/ecp -ExternalURL
https://mail.mydomain.com/ecp
Set-OWAVirtualDirectory -Identity "EXC02\OWA* -InternalURL $null -ExternalURL $null
Set-WebServicesVirtualDirectory -Identity "EXC02\ews* -InternalURL
https://mail.mydomain.com/ews/exchange.asmx -ExternalURL
https://mail.mydomain.com/ews/exchange.asmx
Set-OABVirtualDirectory -Identity "EXC02\oab* -InternalURL
https://mail.mydomain.com/oab -ExternalURL
https://mail.mydomain.com/oab
Set-ActiveSyncVirtualDirectory -Identity "EXC02\microsoft* -InternalURL
https://mail.mydomain.com/Microsoft-Server-ActiveSync -ExternalURL
https://mail.mydomain.com/Microsoft-Server-ActiveSync
Set-PowershellVirtualDirectory -Identity "EXC02\powershell* -InternalURL
https://mail.mydomain.com/Powershell -ExternalURL
https://mail.mydomain.com/Powershell
Set-ClientAccessServer -Identity EXC02 -AutoDiscoverServiceInternalURI
https://autodiscover.mydomain.com/autodiscover/autodiscover.xml
Set the Virtual Directories on Exchange 2007
Set-OutlookAnywhere -Identity "EXC01\RPC (Default Web Site)" -IISAuthenticationMethods Basic,NTLM
Set-OutlookAnywhere -Identity "EXC01\Rpc (Default WebSite)" -IISAuthenticationMethods Basic,Ntlm
Set-OWAVirtualDirectory -Identity "EXC01\OWA* -InternalURL https://legacy.mydomain.com/owa -ExternalURL
https://legacy.mydomain.com/owa
Set-WebServicesVirtualDirectory -Identity "EXC01\ews* -InternalURL
https://mail.mydomain.com/ews/exchange.asmx -ExternalURL
https://mail.mydomain.com/ews/exchange.asmx
Set-OABVirtualDirectory -Identity "EXC01\oab* -InternalURL
https://legacy.mydomain.com/oab -ExternalURL
https://legacy.mydomain.com/oab
Set-ActiveSyncVirtualDirectory -Identity "EXC01\microsoft* -InternalURL
https://mail.mydomain.com/Microsoft-Server-ActiveSync -ExternalURL $null
Set-PowershellVirtualDirectory -Identity "EXC01\powershell* -InternalURL
https://legacy.mydomain.com/Powershell -ExternalURL
https://legacy.mydomain.com/Powershell
Set-ClientAccessServer -Identity EXC01 -AutoDiscoverServiceInternalURI
https://autodiscover.mydomain.com/autodiscover/autodiscover.xml

Out of Memory Exception on Virtual Exchange 2013

I am having an issue with my Exchange 2013 server having multiple OutOfMemory Errors. I am receiving these errors for Event ID 1026 Source .Net Runtime, Event ID 1325 Source ASP.NET, Event ID 4999 Source MSExchange Common, and Event ID 1106 Source
MSEchange ActiveSync. I am also receiving an Application error Event ID 1000. Exchange is running on a virtual machine with 16 GB of memory. Any help or suggestions will be greatly appreciated. Below is the error message from Event ID 1106.
--- Exception start --- Exception type: System.OutOfMemoryException Exception message: Exception of type 'System.OutOfMemoryException' was thrown. Exception level: 0 Exception stack trace: at Microsoft.Exchange.Data.Storage.GenericListData`2.DeserializeData(BinaryReader
reader, ComponentDataPool componentDataPool) at Microsoft.Exchange.AirSync.DeviceBehaviorData.DeserializeData(BinaryReader reader, ComponentDataPool componentDataPool) at Microsoft.Exchange.Data.Storage.DerivedData`1.DeserializeData(BinaryReader reader, ComponentDataPool
componentDataPool) at Microsoft.Exchange.Data.Storage.GenericListData`1.DeserializeData(BinaryReader reader, ComponentDataPool componentDataPool) at Microsoft.Exchange.Data.Storage.GenericDictionaryData`3.DeserializeData(BinaryReader reader, ComponentDataPool
componentDataPool) at Microsoft.Exchange.Data.Storage.SyncState.DeserializeSyncStateTable(Int64 idxTable) at Microsoft.Exchange.Data.Storage.SyncState.Deserialize(PropertyDefinition property) at Microsoft.Exchange.Data.Storage.SyncState.Load(Boolean reloadFromBackend,
PropertyDefinition[] additionalPropsToLoad) at Microsoft.Exchange.Data.Storage.SyncState..ctor(SyncStateStorage syncStateStorage, StoreObject storeObject, SyncStateInfo syncStateInfo, Boolean syncStateIsNew) at Microsoft.Exchange.Data.Storage.CustomSyncState.GetSyncState(SyncStateStorage
syncStateStorage, Folder syncStateParentFolder, SyncStateInfo syncStateInfo, StoreObjectId storeObjectId) at Microsoft.Exchange.Data.Storage.SyncStateStorage.GetCustomSyncState(SyncStateInfo syncStateInfo) at Microsoft.Exchange.AirSync.GlobalInfo.LoadFromMailbox(MailboxSession
mailboxSession, SyncStateStorage syncStateStorage, ProtocolLogger protocolLogger) at Microsoft.Exchange.AirSync.Command.OpenSyncStorage(Boolean shouldOpenGlobalSyncState, Boolean shouldUseBudget) at Microsoft.Exchange.AirSync.Command.WorkerThread() --- Exception
end ---

Hello,
According to the error, the memory is not enough.
Please describe your environment and post the detailed event information.
Besides, I recommend you use Server Role Requirements Calculator to calculate memory and CPU.
Here is an article for your reference.
http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
Cara Chen
TechNet Community Support

Move Exchange 2013 installation to new virtual machine

Currently have: 1 virtual server - Server 2012 (DC, Global Catalog), Exchange 2013 CU1 installation (yes I know- dont install Exchange on DC etc etc ... ). Server2012/Exchange2013 is installed on one VMDK, EDB and logs are saved on another VMDK.
Want to do: Create second virtual machine and install Server 2012 (different name), add it as a member to the same domain (also in the same network), install Exchange 2013, move all mailboxes to the new server, uninstall the old Exchange 2013.
Question is- is it possible to somehow unmount the existing database (I am only using one database for mailboxes and public folders) and mount it to the new server or do I have to create a new database on the new server and move the mailboxes there? I've
heard that the Exchange EDB databases were supposed to be portable between same versions of Exchange.
Any advice is appreciated.

Hi,
Agree with Andy, to avoid down time, we can depend on database portability.
And here are the steps you can refer to:
1. Install new Exchange server on the member server.
2. Move Mailbox Database using Database Portability:
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
3. Move the public folders (if any), re-home the offline address book, and move your SMTP connectors
http://support.microsoft.com/kb/822931
4. Remove the old Exchange server.
Thanks,
Angela Shi
TechNet Community Support
Thanks for the reply.
I'm a bit confused on the instructions from
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx- does step 4 instruct me to overwrite the newly created database (on the new server) with the old database and then mount it on the new server? Also, as the public folders are now in
a mailbox on the same database- aren't they moved with the database without extra hassle?
Also the link you gave me in Step 3 in your post refers to Exchange 2003.
Thanks in advance.

Move Exchange 2013 to new Virtual Server including settings?

Since we have a failing VM Exchange 2013, we need to move the installation to a new server. We have created a new Hyper-V Server 2012 and installed a new Exchange 2013 on it. After connecting the new server to the domain we can see all settings and users
of the existing Exchange Installation.
Since the old server has a corrupt RAID, we need to move all data and settings to the new server. We have moved some user mailboxes with the ecp to the new server. They are still working, but mailtraffic takes exactly 1 hour now?! Also these users who logon
with Outlook now get the error message 'problem with the safetycertificate of the proxyserver (translated)'. The mail still works, but 1 hour delay.
Can we now move the other mailboxes too? And if we have moved them, how can we move the settings of this server? If we shutdown the old server, will Exchange (the moved one) still be up and running? Because we are afraid that when we shutdown the old server
it will not boot again.
Thanx for any tips of leads in the right direction.

1. Outgoing mail from https://echange/owa is
working.
Did you try https://ip-address-of-newserver/owa and send an email outside?
2. Outlook 2010 does not start, cannot find mailboxes to open, so user won't have mail in the morning.
Get-OutlookProvider -Identity EXCH | FL
If is field CertPrincipalName empty type following:
Set-OutlookProvider EXCH -CertPrincipalName msstd:FQDN-YOUR-MAIL-SERVER
After this it should work (assuming all your mailboxes moved to the new server).
Please check this to see you the mailbox servername
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
3. Incoming mail cannot be delivered by the Barracuda (connection refused).
Ensure Barracuda is sending email to the new server and new server is not blocking incoming traffic.
4. OWA and ECP not working from outside (public IP).
Ensure you NAT is correct by site. Check it is listening to the port using http://www.canyouseeme.org/
Please check these and get back
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

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"

SBS2008: Move email from Exchange 2007 to new server with Exchange 2013

We have an old server (SBS2008) and plan to buy a new server with (Server 2012). I need to move all the exchange emails, contacts & calendars to the new server. We will no longer use the old server.
Is there a document or migration tool that will help me understand how to move this data form the old exchange server to the new one?
Old Server:
SBS2008 running Exchange 2007
New Server:
Server 2012
Exchange 2013
Any help is appreciated!

Hi Dave,
It can be done, and as Larry suggested you will consider two Server 2012 installs in order to achieve an environment that looks like your current SBS roles; Exchange 2013 on an Active Directory controller isn't a good long-term solution (SBS did this for
you in the past).
For your size operation, a virtual server host, with a Windows Server 2012 license, and two virtual machines would probably be a suitable design model. In this manner, you have Server 2012 license that permits 1 +2 licenses (one host for virtualization,
up to 2 Virtual Machines on same host).
There's no migration tool. That comes with experience and usually trial and error. You earn the skills in this migration path, and for the average SBS support person you should plan on spending 3x (or more) your efforts estimate in hours planning your migration.
You can find a recommended migration path at this link to give you an idea of the steps, but its not exactly point by point going to cover you off for an sbs2008 to server 2012 w/exchange 2013 migration. But the high points are in here. If it looks
like something you would be comfortable with then you should research more.
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Specific around integrating Exchange 2013 into an Exchange 2007 environment, guidance for that can be found here:
http://technet.microsoft.com/en-us/library/jj898582(v=exchg.150).aspx
If that looks like something beyond your comfort level, then you might consider building a new 2012 server with Exchange 2013 environment out as new, manually export your exchange 2007 mailbox contents (to PST) and then import them into the new mail server,
and migrate your workstations out of old domain into new domain. Whether this is more or less work at your workstation count is dependent upon a lot of variables.
If you have more questions about the process, update the thread and we'll try to assist.
Hopefully this info answered your original question.
Cheers,
-Jason
Jason Miller B.Comm (Hons), MCSA, MCITP, Microsoft MVP

Exchange 2013 /m:recoverserver constantly failing due to MSExchangeSubmission.exe

Hi all,
I am trying to recover my lab Exchange 2013 server after removing a component of IIS messed all IIS functions, including all virtual directories.
The server is running on Hyper-V so I have removed and rebuilt the OS disk whilst the Exchange data resides on a separate disk. I've reset the computer account in AD and then run the command:
setup /m:recoverserver /targetdir:"d:\Program Files\Microsoft Exchange\v15" /DoNotStartTransport /IAcceptExchangeServerLicenseTerms
I have now done this a number of times and on each occasion it fails when attempting to start the Microsoft Exchange Transport Submission service. The error in the event log is as follows:
Log Name:      Application
Source:        Application Error
Date:          30/03/2013 20:18:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HV-E2K13
Description:
Faulting application name: MSExchangeSubmission.exe, version: 15.0.516.29, time stamp: 0x506956b8
Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.516.27, time stamp: 0x5064072e
Exception code: 0xc00000fd
Fault offset: 0x0000000000639d07
Faulting process id: 0x1cc8
Faulting application start time: 0x01ce2d83cbb5568e
Faulting application path: D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll
Report Id: 0a1e3a42-9977-11e2-93f1-00155d0a4b05
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-30T20:18:53.000000000Z" />
    <EventRecordID>112812</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HV-E2K13</Computer>
    <Security />
</System>
<EventData>
    <Data>MSExchangeSubmission.exe</Data>
    <Data>15.0.516.29</Data>
    <Data>506956b8</Data>
    <Data>Microsoft.Exchange.Net.ni.dll</Data>
    <Data>15.0.516.27</Data>
    <Data>5064072e</Data>
    <Data>c00000fd</Data>
    <Data>0000000000639d07</Data>
    <Data>1cc8</Data>
    <Data>01ce2d83cbb5568e</Data>
    <Data>D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe</Data>
    <Data>C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll</Data>
    <Data>0a1e3a42-9977-11e2-93f1-00155d0a4b05</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>
Any thoughts?
Paul

Hi,
Im dealing with the same errors when i'm trying to restore our productive mailbox from a disaster.
I've tried everything listed here but last Milind Naphade commentary.
I'm in that right now, i ll tell if it's working soon.
Ty!
Hi Again. It Failed to start MSExchangeSubmission.exe
Here is the event on eventvwr (Some details on spanish wich is the language of my server)
Nombre de la aplicación con errores: MSExchangeSubmission.exe, versión: 15.0.516.29, marca de tiempo: 0x506956b8
Nombre del módulo con errores: Microsoft.Exchange.Net.ni.dll, versión: 15.0.516.27, marca de tiempo: 0x5064072e
Código de excepción: 0xc00000fd
Desplazamiento de errores: 0x000000000062f697
Identificador del proceso con errores: 0x7d0
Hora de inicio de la aplicación con errores: 0x01cfac0a0bb16a68
Ruta de acceso de la aplicación con errores: C:\Program Files\Microsoft\Exchange Server\V15\Bin\MSExchangeSubmission.exe
Ruta de acceso del módulo con errores: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\b028905d8fd3faa99c9801b69b1500da\Microsoft.Exchange.Net.ni.dll
Identificador del informe: 4a9638fc-17fd-11e4-9404-000c29f101d8
Nombre completo del paquete con errores:
Identificador de aplicación relativa del paquete con errores:
ExchangeSetup.log ends with:
[07/30/2014 15:19:10.0220] [1] The following 1 error(s) occurred during task execution:
[07/30/2014 15:19:10.0220] [1] 0. ErrorRecord: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
[07/30/2014 15:19:10.0220] [1] 0. ErrorRecord: Microsoft.Exchange.Configuration.Tasks.ServiceDidNotReachStatusException: El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.
en Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
en Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.WaitForServiceStatus(ServiceController serviceController, ServiceControllerStatus status, Unlimited`1 maximumWaitTime, Boolean ignoreFailures, Boolean sendWatsonReportForHungService)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(ServiceController serviceController, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
en Microsoft.Exchange.Management.Tasks.ManageSetupService.StartService(String serviceName, Boolean ignoreServiceStartTimeout, Boolean failIfServiceNotInstalled, Unlimited`1 maximumWaitTime, String[] serviceParameters)
en Microsoft.Exchange.Management.Tasks.StartSetupService.InternalProcessRecord()
en Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
[07/30/2014 15:19:10.0236] [1] [ERROR] The following error was generated when "$error.Clear();
start-SetupService -ServiceName MSExchangeSubmission
" was run: "El servicio 'MSExchangeSubmission' no puede alcanzar el estado 'Running' en este servidor.".
[07/30/2014 15:19:10.0236] [1] [ERROR] Service 'MSExchangeSubmission' failed to reach status 'Running' on this server.
[07/30/2014 15:19:10.0236] [1] [ERROR-REFERENCE] Id=MailboxServiceControlLast___23a36fed7b6947e0906f388b5a90135c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[07/30/2014 15:19:10.0251] [1] Setup is stopping now because of one or more critical errors.
[07/30/2014 15:19:10.0251] [1] Finished executing component tasks.
[07/30/2014 15:19:10.0267] [1] Ending processing DisasterRecovery-MailboxRole
[07/30/2014 15:19:10.0282] [0] No se completó la operación de instalación de Exchange Server. Puede encontrar más detalles en ExchangeSetup.log ubicado en la <SystemDrive>: carpeta \ExchangeSetupLogs.
[07/30/2014 15:19:10.0282] [0] End of Setup
[07/30/2014 15:19:10.0282] [0] **********************************************
Any suggestion please??? idk what else can i do!

Exchange 2013 CU7 - Frequent Outlook 2013 Disconnections and Delays

We currently have the following environment:
Windows 2012 VM on Hyper-V with 24GB of RAM and 4 virtual procs (1 socket)
Cisco UCS, B200 M3 Blades
Exchange 2013 CU7
Exchange 2007 is in our environment, but public folders have been removed and only a few stale, unused accounts exist on it.
Two dual-role CAS/Mailbox servers
Mailbox servers are in a DAG
MAPI/HTTP is our connection protocol
.NET Framework 4.5.2
Clients are Outlook 2013 SP1 on Windows 7 and 8.1
(Currently round robin DNS, but we have a hardware load balancer we've temporarily taken out of the mix to solve this problem)
What we're seeing is frequent disconnections from Exchange, regardless of the CAS server. That is, both CAS servers will disconnect clients, but not at the same time. When we look at the Exchange boxes, we notice that the CPU is 99% - 100% each time the
disconnections occur. When we hunt down the IISWorker process causing the sudden CPU run, we see it comes back to the following app pools:
MSExchangeMAPIFrontEndAppPool
MSExchangeMAPIMailboxAppPool
(We were running RPC/HTTP, but switched to MAPI/HTTP to resolve the problem. We had the same issue with equivalent RPC app pools at the time.)
Eventually, within a minute or two, the CPU load will decrease and the clients connected via that CAS will regain connection. As you can imagine, the pain is felt more frequently by uncached clients--although everyone, regardless of caching, will see
the disconnections.
Basically, the problem sounds exactly as shown in this KB: http://support.microsoft.com/kb/2995145 Unfortunately, we already had .NET 4.5.2 installed, and have changed the environment variable and registry as shown in the article.
We're in contact with Microsoft Support, but thus far they're scratching their heads.
I'm clearing up all small errors to decrease the noise in the application error logs, but the most persistent one is Event ID 106 (MSExchange Common):
"Performance counter updating error. Counter name is Time in Resource per second, category name is MSExchange Activity Context Resources. Optional code: 2. Exception: The exception thrown is : System.InvalidOperationException: Instance 'ad-powershell-defaultdomain'
already exists with a lifetime of Process. It cannot be recreated or reused until it has been removed or until the process using it has exited."
Loading/reloading and recreation of the performance counters does not fix the problem, by Microsoft Support or us. Of course, this error existed before we started having issues; I'd just like to clean it up just in case it's a contributing factor.
Has anyone seen anything similar?

We're using a Barracuda load balancer (641), but we've eliminated that as a source of the problem. The CPU spikes and disconnections happen whether or not the load balancer is in use.
This problem is still ongoing, and we're still working with Microsoft Support. Right now they're focused on our environment, but having combed through it numerous times, there's nothing that stands out. I suspect this is a bug in CU7 (yet I would
readily accept our environment being at fault if it means we can identify and resolve the problem), but that's not the road Support is going down.
We've looked at storage I/O on the VM hosts (disk responses are 10 MS or less), added double the CPUs to each mail server (for a total of 8, each), disabled TCP chimney offload, run numerous Experfwiz log collections, etc... Now
the tech is focused on a particular mailbox database being the culprit because it also takes up more CPU when the MAPI app pools are gunning pretty high. I suspect that it is a symptom and not the problem, but I have no choice but to follow his lead.
What is your environment like? Are you also CU7? And did the problem show itself after a cumulative update was applied?

Exchange 2013 installation Problem on Hyper-V

Hello,
I have a very interesting problem Exchange 2013 installation step on Hyper-V.
I have 2 server. I installed on server Server 2012 R2 Standart. And then installed hyper-v role for both server.
I created virtual machine for first server and this virtual machine domain controller.
And then I created virtual machine for second server and this virtual machine Exchange 2013.
I installed all prequisites and exchange 2013 finished successfuly. When I opened https://server/ecp it give me http 500 internal error. I checked almost all forums but any recommendation didn't solve my problem.
And then I removed hyper-v role and installed vmware v11. and installed same applications like above.
Very interesting finished installation and opened ecp console. eveythink seen to good.!
Actualy I find problem.
There is exchange feature installation command on microsoft exchange prequisite. When ruunning this command installing two program on program and feature name is "c++ redistrubutable x64 and x32"
I must uninstall this programs before install unified communication api 4.0.
I cannot see on hyper-v when running this feature.
But I can see on vmware this features on programs and feature.
This is very absurt.
Anybody have an idea for this
Thank you for your clarify.

Hi,
Thanks for your reply.
I run this command before Exchange 2013 installation:
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience,
NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering,
RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell,
Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth,
Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging,
Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase,
Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression,
Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
later run this code on vmware platform , installing 2 program in programs and feature. name is Visual
C++ Redistributable package x64 and x86. I know Unified Communications Managed API 4.0
install same program too. But I must unintall Visual C++ Redistributable package before
install Unified Communications Managed API 4.0. But My problem I cannot see this two program
in programs and feature on hyper-v platform.
I tried it many times.

Exchange 2013 - The connection to Microsoft Exchange is unavailable

Hi there,
i have some problems on my new Exchange 2013 Server: Here is the topology:
1 serveur 2012 in workgroup with the Hyper-V role
2 VM: DC2012 is the DC of the domain: intra.mydomain.com, Windows 2012
The other VM is member of the domaine, Windows 2012, Exchange 2013 SP 1 installed.
So, i have dc2012.intra.mydomain.com and mail1.intra.mydomain.com (another DC: DC2008, name: dc2008.intra.mydomain.com)
I have some troubles with the SSL and the connexion of Outlook outside the LAN.
In the LAN on a client, i launch Outlook 2010 and the autodiscver make the rest. The connexion is ok.
But i have a client not in the LAN, so i configured a SSL. I made a request. First Question:
In the ECP, Server, Certificate, i have 3 times "Microsoft Exchange Server Auth Certificate" and 3 times "Microsoft Exchange" with differents dates. Why?
I installed my PKI on the DC2012, and paste the request and download the certificate. I retuned on the exchange server in ECP, Server, Certificate and treat the pending request. In Services i checked IMAP, POP, IIS, SMTP.
Then, in Server, Server, Mail1, OutlookAnywhere, in url extternal: mail.mydomain.com and Authentification: NTLM.
In ECP, Servers, Virtual Directories i wrote the same url external and internal: mail.mydomain.com for ECP, OWA, ActiveSync, OAB.
In my DNS on the DC, i created a CNAME record for mydomain.com et i created a A record for mail. on a client if i make nslookup then mail.mydomain.com the IP is the LAN IP of my exchange server.
I modified the MX record of my public domain: mail.mydomain.com to point on my Public IP. That works.
On the client outside of the LAN, i installed the root certificate and the exchange certificate.
second question:
Why my client outside of the LAN can't connext with outlook.
Thanks a lot for your answers and sorry for the long post.
Alex

I resolved my problem!
here is the solution that solved it:
actually, i tried to connect Outlook 2010 ti Exchange 2013. I knew that Exchange now connect Outllok via rpc over http(s), BUT, the Autodiscover (in LAN) transform the field server to something like that:
[email protected] , the xxx correspond to the GUID of the mailbox. So, for my remote user, i launch this command on Exchange 2013:
Get-Mailbox test | fl name, exchangeguid , it give to me the GUID, then in te field "Server" i fill ([email protected]): [email protected]
And in advanced parameters, same things i mentioned in previous post. And it works!!!!!
Thanks to me.

Exchange 2013 Virtual

Similar Messages

Maybe you are looking for