Hello, when trying to install the Mailbox Role: Transport Service, I get the following error:

Error:
The following error was generated when "$error.Clear();
configure-WSManIISHosting -EnableKerberosModule;
" was run: "Application 'PowerShell' doesn't exist in the default Web site in 'C:\Windows\system32\inetsrv\config\ApplicationHost.Config'. Make sure the application isn't deleted from the default Web site.".

Any ideas how to resolve this? I've tried everything.

Thank you.

I am writing up a plan to migrate from Exchange 2007, to 2013. When I stand up my first Exchange 2013 server, I believe an arbitration mailbox with "OrganizationCapabilityOABGen" will be created.

I will migrate user mailboxes and Public Folders to the new server and will delete PFs from my E2007 server. Since all of my current OABs are setup for PF and web distribution, I will also disabled PF distribution.

I have two questions:
1. Once I've disabled PF distribution of my OABs, will I be able to delete my PF database?
2. Do I need to do anything else to ensure that OAB generation is swung to Exchange 2013 (before decommissioning E2007)?

Thanks.

While trying to install Exchange 2013, it gives an error that sp3 needs to be applied to exchange 2010.  There are no exchange 2010 servers on the network, the one the existed on a mail server was formatted along with the server. I have tried removing all the orphaned objects in AD without success. I have tried ADSI EDIT there are no containers containing exchange. How do i get exchage out of AD in order to proceed with the installation of exchange 2013.

Hi,

We've recently migrated our on-premise Exchange to Office 365 but we keep management of users in our on-premise Active directory and dirsynced the attribute changes to Office 365. As per Microsoft recommendation, an Exchange server with CAS and Mailbox role should still be on-premise to manage the Exchange attributes. I have two Exchange 2013 servers, one CAS and one Mailbox, I wanted to decommission the Mailbox role server so that I can reuse the storage.

Is it possible to uninstall the Mailbox role and then add the role in the existing Exchange CAS server?

Or, I'll just uninstall Exchange on the 2 servers and setup a new Exchange server with both CAS and Mailbox role?

Hi There,

I wish to start a hosted exchange for some business I support. I ofcourse will run the server from my own location. It will be for maybe 5 mailboxes per company. I dont know how this works in terms of CALs? Any advice would be great.

thank you

Hello,

I'm trying to move mailboxes from Exchange 2007 to 2013. The move request seems to be stuck in the "Syncing" mode.
Exchange 2007 environment consists of CAS and MBX servers, Exchange 2013 has both roles on the same machine.
Mail traffic between servers, to/from internet works without issues.
Where would I start to troubleshoot it?

Thanks.

Memento Mori

I'm aware there is a Group Policy admin template available to force Outlook to request only NTLM or basic authentication, however, I'd like to disable Outlook Anonymous NTLM on the server side in our Exchange 2013 SP1 on-premises installation.

Is there a method to disable Anonymous NTLM for Outlook client connections for the cas or organization?  I've tried the "Set-OutlookAnywhere" InternalClientAuthenticationMethod and ExternalClientAuthentcationMethod but Outlook is still able to connect with Anonymous Authentication selected for the logon network security.

Thanks

John Lowery

We have Exchange 2007 installed currently (SP3, latest UR). I installed Exchange 2013 in preparation for migration, started working on configuration. After doing some digging, we realized we don't have any licensing for 2013 (miscommunication). The obvious solution is to purchase licensing for 2013, but the cost is an issue.

First questions: we do have licensing for 2010. Is there any way we can install Exchange 2010? Everything I'm reading says no, but would like confirmation. 2010 was never installed in the environment.

Second question: If I cannot install 2010, can I install a second 2007 server after 2013 has been installed (newer OS)? Safely uninstall 2013?

Thanks!

I have two clients who will be merging their on-prem Exchange 
organizations. Different forests.  I've done many cutover migrations to
Office 365 for other clients so I'm familiar with the process.  My 
question is:  Is it possible to do an O365-style cutover migration (create migration endpoint, cutover batch, etc.) from
an on-prem Exchange 2010 server to an on-prem Exchange 2013 server using
the same steps?

Thanks in advance for any input. 

Steve

We are trying to migrate from SBS2003 to 2012R2 with Exchange 2010 with the ultimate goal of upgrading then to Exchange 2013. Trying to follow all the migration documents we have integrated the Server 2012 and Active Directory appears fine. the issue is when we try to open the Exchange Management Console or  Shell, we receive the error "Connecting to remote server "Servername.Domainname.local" failed with the following message: The WinRM client received an HTTP status Code of 403 from the remote WS-Management service. For more information, see the about_Remote_Troubleshooting Help topic. It was running the command 'Discover-ExchangeServer -UseWIA $true -SuppressError $true -CurrentVersion 'Version 14.3 (Build123.4)''.

We can add the exchange management powershell snapin manually and verify the Exchange accounts are present using the Get-CASmailbox command. Running EMTshooter.ps1 gives a result of Your Powershell Virtual Directory is M.I.A.

Any help on this would be appreciated. I believe this is an issue with IIS but cannot seem to locate the problem.

We have not yet transfered the FSMOs from the 2003 SBS as we wanted be be sure Exchange 2010 was functional first.

Thanks for any assistance.

I have just installed my first Exchange 2013 deployment.  Small single server install, no Edge Server.  Things seem to have gone pretty well.  I haven't enabled external mail yet but just wanted to do a bit of testing.  I can send test messages and log in via OWA just fine.

However, when I try to connect an Outlook client I get the message: "Outlook cannot log on.  Verify you are connected to the network.  The connection to Microsoft Exchange is unavailable."  I have an internal DNS record for autodiscover and the internal urls in Exchange.

Before I go much further, I will also add that I have not yet installed the cert.  So I do get the certificate error when setting up Outlook.  I think I read that without a valid cert install, Outlook will not connect to Exchange 2013.  Is that true?  I will be finishing things up and installing the cert soon.  Once I do that, do you suspect the above error message will go away?

Also, after the error above, the dialog box appears that lists the server name.  Instead of what I would consider a valid server name, the name shows up as 505ef3b4-5d84-458e-b084-53d45c532bf0@domain.com.  Is that normal?

Thanks for any clarification

I am about to migrate a Windows Server 2003r2 Active Directory that has an Exchange 2003 server. This domain started as an NT4 domain and has been upgraded to its current level and is working well.

I plan to migrate to Server 2012R2 and Exchange 2013.

The domain is relatively small. I can migrate (I think, with an intermediary ‘08R2 server), or I can start a fresh ‘12R2 Forest/Domain and fresh Exchange.

I would prefer to migrate, but I am worried about namespace issues.

Current namespace is      internaldomain.loc    and machines are  servername.internaldomain.loc   .

NetBIOS domain name is        internaldomain    

Users are identified as   internaldomain\username   or    internaldomain.loc\username

The Active Directory DNS server is set with forwards to our ISPs DNS servers.

We have real world      externaldomain.com   MX record forwarded through our firewall to port 25 on our Exchange server.

Is it still a supported practice in Server 2012R2 to keep internal DNS  internaldomain.loc    and the external reference  externaldomain.com    ?

One of my SSL SAN certificate vendors mentioned something about  .loc   and   .local   suffixes being disallowed on new certificates. We do not use any web interfaces to Exchange internally, and if we did for any reason, I do not mind the warning message about the certificate not being trusted (internally).

All our internal access to the Exchange server 2013 will be from Outlook 2010 or Outlook 2013.

I think all the external services such as Active Sync, Outlook Anywhere, or Outlook Web Access, or the AutoDiscover service can be referenced to the  externaldomain.com     name and internally to the Exchange Server’s external facing interface just like I do in Windows Server 2008R2 and Exchange 2010, but I am not completely sure.

I have done a certain amount of research and think I can just migrate with my current namespace, but I would like to make sure I don’t create issues.

Can I migrate with my current namespace?

I think this is straightforward, but I would like some expert opinions and advice please.

I will post this in the Windows Server and Exchange server forums.

Thank you.

Fabio Martins MCDST/MCSA Brasil!!!

We are in an hybrid environment of Exchange OnPremises and Exchange Online and in the OnPremises environment we have cohexistence of Exchange 2010 and Exchange 2013. 

As a backup solution we have CA Arcserve Backup, that allow us to make a backup in document level of the exchange 2013 mailboxes. 

We still can´t do the backup document level. In the logs files from the ca agent installed in the server, we found some MAPI errors. 

We followed all the articles bellow, but without success. 

We had a remote support from CA and they told us that we are facing a problem on the Exchange Server. 

We ran the Test-MapiConectivity that returns Success.

Below of the links, follow the logs, if someone could help-me to diagose the MAPI on Exchange 2013, I will be vary glad. 

http://www.arcserve-knowledgebase.com/index.php?View=pdf&EntryID=4969

https://arcserve.zendesk.com/hc/en-us/articles/201992659-Exchange-2013-Document-Level-Backup-fails-to-backup-n-mailboxes-Error-AE9609-A-necessary-Exchange-service-is-not-running-Please-start-the-related-service-on-the-Exchange-server-manually-

http://www.arcserve-knowledgebase.com/index.php?View=entry&EntryID=5481

https://arcserve.zendesk.com/hc/en-us/articles/202153889-AE9609-AE9603-AW9627-ErrErr-800000008004011d

https://communities.ca.com/thread/241692506

https://communities.ca.com/thread/241690757 

http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=2

http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=1193

http://arcserve-knowledgebase.com/index.php?View=entry&EntryID=2522

http://arcserve-knowledgebase.com/index.php?View=pdf&EntryID=4600

https://arcserve.zendesk.com/hc/pt-br/requests/10740

<01/28/2015-17:36:16:852 TID:20ac>Begin MAPILogonEx() failed MAPICODE: 0 
<01/28/2015-17:36:16:992 TID:20ac>End MAPILogonEx() failed MAPICODE: 0 
<01/28/2015-17:36:17:08 TID:20ac>After  MAPILogonEx() before call my failed MAPICODE: 0 

Thanks in advance!

Fabio Martins MCDST/MCSA Brasil!!!

Fabio Martins MCDST/MCSA Brasil!!!

On my passive Server "Content Index State" mailbox database is still Failed and Suspended for almost a week. 

Actions Taken to Resolve the Issue:

 - Update-mailboxdatabasecopy

 -Delete the exisiting folder of database on passive server and run database copy on EAC

Still got FAILED AND SUSPENDED content index state.

Need some advice guys.. 

Thanks!

Hi,

I have a 2 exchange 2013 servers in windows 2012 OS both servers are configured with DAG one is active and the other one is passive

I moved the 5 databases in other drive and it was successful but no matter what I try one of my database in passive server show "ContentIndexState: FailedandSuspended" 

I tried to manually copy the database file from the active server to passive server but still the status is the same. Tried to reseed the database and wait for at least 1 day to change the status from FailedandSuspended to healthy but still no changes happened.

I tried to delete the afftected database in passive server and copy the healthy database from active to passive again and do the reseed procedure but still the problem is the same. Please help. Thank you! 

Hi everybody!  We recently migrated to from Exch 07 to 13, and there seems to be a small problem in OWA. 

In OWA 2013, when users creates an invite in Calendar, and switch back to Mail, a menu appears (see below) and then disappears immediately.  Instead of allowing users to choose whether to save or discard changes to their invites, it automatically discards, and goes to Mail.  It happens in both IE and Chrome, and for all users. Any ideas what's going on?   Tried all the usual - clearing cache, etc.  It doesn't appear to be a problem with the client.  Thanks!

Hello,

We have Exchange 2013 CU5 and are looking to install CU7. I have downloaded and extracted the set-up files, however when try to run the update I reveive a number of concerning errors regarding Active Directory. 

I am aware that the update will require Schema updates, however I thought the GUI installed handled these for me. 

Exchange is deployed at a AD site that is not in the same site as the Schema Master. Could this be the issue? Do I have to update the schema manually? The only other thing to say is that we do still have an Exchange 2010 SP3 server in the organisation, however everything (including public folders) have been migrated across to 2013 and is just awaiting decommissioning and un-installing.

Errors are below

Error:

The Mailbox server role isn't installed on this computer.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.UnifiedMessagingRoleNotInstalled.aspx

Error:

The Mailbox server role isn't installed on this computer.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.BridgeheadRoleNotInstalled.aspx

Error:

Setup can't continue with the upgrade because the perfmon (2112) has open files. Close the process, and then restart Setup.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ProcessNeedsToBeClosedOnUpgrade.aspx

Error:

The Active Directory schema isn't up-to-date, and this user account isn't a member of the 'Schema Admins' and/or 'Enterprise Admins' groups.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.SchemaUpdateRequired.aspx

Error:

Global updates need to be made to Active Directory, and this user account isn't a member of the 'Enterprise Admins' group.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalUpdateRequired.aspx

Error:

You must be a member of the 'Organization Management' role group or a member of the 'Enterprise Admins' group to continue.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.GlobalServerInstall.aspx

Error:

You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedBridgeheadFirstInstall.aspx

Error:

You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedCafeFirstInstall.aspx

Error:

You must use an account that's a member of the Organization Management role group to install the first Client Access server role in the topology.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedFrontendTransportFirstInstall.aspx

Error:

You must use an account that's a member of the Organization Management role group to install or upgrade the first Mailbox server role in the topology.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedMailboxFirstInstall.aspx

Error:

You must use an account that's a member of the Organization Management role group to install or upgrade the first Client Access server role in the topology.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedClientAccessFirstInstall.aspx

Error:

You must use an account that's a member of the Organization Management role group to install the first Mailbox server role in the topology.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.DelegatedUnifiedMessagingFirstInstall.aspx

Error:

Setup encountered a problem while validating the state of Active Directory: Exchange organization-level objects have not been created, and setup cannot create them because the local computer is not in the same domain and site as the schema master.  Run setup with the /prepareAD parameter on a computer in the domain powerplay and site Default-First-Site-Name, and wait for replication to complete.  See the Exchange setup log for more information on this error.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.AdInitErrorRule.aspx

Error:

The forest functional level of the current Active Directory forest is not Windows Server 2003 native or later. To install Exchange Server 2013, the forest functional level must be at least Windows Server 2003 native.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.ForestLevelNotWin2003Native.aspx

Error:

The Mailbox server role isn't installed on this computer.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.MailboxRoleNotInstalled.aspx

Error:

Either Active Directory doesn't exist, or it can't be contacted.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.CannotAccessAD.aspx

Warning:

Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2007 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2007 servers.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE12ServerWarning.aspx

Warning:

Setup will prepare the organization for Exchange 2013 by using 'Setup /PrepareAD'. No Exchange 2010 server roles have been detected in this topology. After this operation, you will not be able to install any Exchange 2010 servers.

For more information, visit: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.NoE14ServerWarning.aspx

Hi Guys,

I need your expertise guidance on Exchange server consolidation. The environment is very complex. It has almost all versions of exchange starting from 5.0 to 2010 in different locations and different AD forests/domains. We are looking for a solution of Unified Exchange email system (On premise). We are planning to build a new exchange organization with Exchange 2013. Could anyone guide how to go about this consolidation.  What are challenges, Risks, limitations ..etc involved in this project?

How can we do cross forest mailbox migration in this scenario? Please suggest me..

Nagesh