Exchange Server 2013 setup / coexistance Exchange 2010

So started setting up Exchange 2013 and ran into a random issue regarding the OAB. Resolved by deleting/recreating the OAB in Exchange 2010.
My issue now is setup will not complete, just tells me an "Incomplete Installation Detected" starts to resume the installation. Upon "next" I receive just a hanging screen of "Setup Progress" which goes no where.
[06/12/2014 20:05:19.0860] [0] **********************************************
[06/12/2014 20:05:19.0876] [0] Starting Microsoft Exchange Server 2013 Setup
[06/12/2014 20:05:19.0876] [0] **********************************************
[06/12/2014 20:05:19.0876] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[06/12/2014 20:05:19.0876] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[06/12/2014 20:05:19.0876] [0] Setup version: 15.0.516.32.
[06/12/2014 20:05:19.0876] [0] Logged on user: DOMAIN\Admin.
[06/12/2014 20:05:19.0954] [0] Command Line Parameter Name='sourcedir', Value='F:\'.
[06/12/2014 20:05:19.0954] [0] Command Line Parameter Name='mode', Value='Install'.
[06/12/2014 20:05:19.0969] [0] RuntimeAssembly was started with the following command: '/sourcedir:F: /mode:Install'.
[06/12/2014 20:05:20.0344] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole AdminToolsRole
[06/12/2014 20:05:21.0391] [0] Setup is choosing the domain controller to use
[06/12/2014 20:05:21.0595] [0] The MSExchangeADTopology has a persisted domain controller: DOMAIN CONTROLLER
[06/12/2014 20:05:22.0485] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use DOMAIN CONTROLLER
[06/12/2014 20:05:22.0485] [0] Setup is choosing a global catalog...
[06/12/2014 20:05:22.0516] [0] Setup has chosen the global catalog server DOMAIN CONTROLLER.
[06/12/2014 20:05:22.0516] [0] Setup will use the domain controller 'DOMAIN CONTROLLER'.
[06/12/2014 20:05:22.0516] [0] Setup will use the global catalog 'DOMAIN CONTROLLER'.
[06/12/2014 20:05:22.0516] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
[06/12/2014 20:05:22.0532] [0] Exchange organization container for the organization is 'CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
[06/12/2014 20:05:22.0579] [0] Setup will search for an Exchange Server object for the local machine with name 'LOCALHOST'.
[06/12/2014 20:05:22.0751] [0] Exchange Server object found : 'CN=LOCALHOST,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
[06/12/2014 20:05:22.0751] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[06/12/2014 20:05:22.0751] [0] The following datacenter roles are unpacked:
[06/12/2014 20:05:22.0751] [0] The following roles are installed: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole AdminToolsRole
[06/12/2014 20:05:22.0766] [0] The local server has some Exchange files installed.
[06/12/2014 20:05:22.0798] [0] Server Name=LOCALHOST
[06/12/2014 20:05:22.0829] [0] Setup will use the path 'F:\' for installing Exchange.
[06/12/2014 20:05:22.0829] [0] Setup will discover the installed roles from server object 'CN=LOCALHOST,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=DOMAIN,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN,DC=LOCAL'.
[06/12/2014 20:05:22.0829] [0] 'BridgeheadRole' is installed on the server object.
[06/12/2014 20:05:22.0829] [0] 'ClientAccessRole' is installed on the server object.
[06/12/2014 20:05:22.0829] [0] 'MailboxRole' is installed on the server object.
[06/12/2014 20:05:22.0829] [0] 'UnifiedMessagingRole' is installed on the server object.
[06/12/2014 20:05:22.0845] [0] The installation mode is set to: 'Install'.
[06/12/2014 20:05:44.0768] [0] An Exchange organization with name 'DOMAIN' was found in this forest.
[06/12/2014 20:05:44.0768] [0] Active Directory Initialization status : 'True'.
[06/12/2014 20:05:44.0768] [0] Schema Update Required Status : 'False'.
[06/12/2014 20:05:44.0768] [0] Organization Configuration Update Required Status : 'False'.
[06/12/2014 20:05:44.0768] [0] Domain Configuration Update Required Status : 'False'.
[06/12/2014 20:05:44.0768] [0] The locally installed version is 15.0.516.32.
[06/12/2014 20:05:44.0768] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[06/12/2014 20:05:44.0830] [0] Applying default role selection state
[06/12/2014 20:05:44.0877] [0] Setup is determining what organization-level operations to perform.
[06/12/2014 20:05:44.0877] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN-NAME.
[06/12/2014 20:05:44.0877] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[06/12/2014 20:05:44.0893] [0] InstallModeDataHandler has 0 DataHandlers
[06/12/2014 20:05:44.0893] [0] RootDataHandler has 1 DataHandlers
[06/12/2014 20:05:45.0737] [0] Finished loading screen IncompleteInstallationDetectedPage.
[06/12/2014 20:05:48.0518] [0] Setup is determining what organization-level operations to perform.
[06/12/2014 20:05:48.0518] [0] Because the value was specified, setup is setting the argument OrganizationName to the value DOMAIN-NAME.
[06/12/2014 20:05:48.0518] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[06/12/2014 20:05:48.0518] [0] InstallModeDataHandler has 0 DataHandlers
[06/12/2014 20:05:48.0518] [0] RootDataHandler has 1 DataHandlers
[06/12/2014 20:05:48.0737] [0] Finished loading screen SetupProgressPage.

Hi,
Let's try the following resolutions:
1. Check if the discovery SearchMailbox is present on Exchange 2010 when you run the Exchange 2013 Install.
2. Reinstall your Exchange 2013 server:
Open ADSIEDIT, CN=Configuration, DC=your domain ->CN=Services ->CN=Microsoft Exchange ->CN=First Organization ->CN=Administrative Groups ->Cn=Exchange Administrative Group ->CN=Servers ->CN=Server name
After remove the exchange server, please reinstall your exchange server to test the result.
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

I update my exchange server 2013 cu6 with exchange 2007 and my exchange 2013 db shutdown every 25 minute and recover. You have any hotfix I can use for this solution.

Hi,
From your description, you have deployed Microsoft Exchange Server 2013 and Microsoft Exchange Server 2007 in a co-existence environment. After you upgrade to CU6, databases unexpectedly shut down. In your case, here is a kb for your reference.
Exchange Server 2013 databases unexpectedly fail over in a co-existence environment with Exchange Server 2007
http://support2.microsoft.com/kb/2997209
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

New Exchange Server 2013 in a Exchange 2007 Org, can't get cu's to install

Hi,
We have an Exchange Server 2007 in our organization. I installed an Exchange Server 2013 but could not get the CU3 to install, would throw exceptions. I tried CU2 and it got a lot further but failed to start a service near the end. Don't ask for specifics
as I got frustrated and blew this machine away and installed a fresh VM. I read that you can install the CU's as if they are a fresh installation. I tried this but it fails saying "the Exchange server is in an inconsistant stet....recover". There
IS no Exchange server yet!!
What am I doing wrong? I used the command line for CU3, like: setup /mode:install /roles:ca,mb,mt /IAccept blah blah blah. I didn't set powershell execution policy, not sure if that was it. Are there switches I am missing? I want to see if I can install
the Exchange CU3 right from the get-go.
HeLp!

Hi,
According to the error message, this issue may occur if the previous Exchange installation or un-install failed to complete. This situation leaves the Exchange server
object in Active Directory and prevents a new installation.
We can try:
1. Install ADSI Edit.
2. Launch ADSI Edit. To do this, click Start, click Run, type adsiedit.msc in the text box, and then click OK.
3. Locate the Exchange server object by going to the following location: CN=Configuration, DC= Domain Name, DC=com, CN=Services, CN=Microsoft Exchange, CN=<Organization
Name>, CN=Administrative Groups, CN= <Exchange Administrative Group>, CN=Servers, CN=<Server Name>.
4. Delete the server object.
5. Remove the Exchange server's machine account from Security groups Exchange Servers and Exchange Install Domain Servers.
Regards,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Exchange server 2013 ECP, OWA, Exchange Management Shell, Outlook access and a few more problems.

Good Morning,
I really need some help please.
Our Server 2012 std. with Exchange 2013 std. installation was running like a dream. The tech responsible for our installation left the company to work in the UK and reported to us that there were minor issues with the installation that
needed attention.
on investigation we have found issues in that we cannot access ECP or OWA and in fact Internet explorer most of the time. on further investigation we found management shell for exchange gives errors on start up and new users and outlook cannot
be added to the domain.
On contacting the tech via phone he said he had issues with Certificates but could not help any further.
I have googled the problems and read much in TechNet and believe that in order not to make things worse than they are to approach those that know more than I do at present. I am not sure where to start right now.
Where do I start?????
ps. There does not seem to be any backups that we can fall back on.
regards Tom

Hi Winnie,
Please check me on this. Authentication seems to be incorrectly configured.
Attached below is the output from the commands you requested me to run.
ecp
Identity                      : NORTH2012-SERV\ecp (Exchange Back End)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Identity                      : NORTH2012-SERV\ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
OWA
Identity                      : NORTH2012-SERV\owa (Exchange Back End)
InternalAuthenticationMethods : {Ntlm, WindowsIntegrated}
BasicAuthentication           : False
WindowsAuthentication         : True
DigestAuthentication          : False
FormsAuthentication           : False
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
Identity                      : NORTH2012-SERV\owa (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
BasicAuthentication           : True
WindowsAuthentication         : False
DigestAuthentication          : False
FormsAuthentication           : True
LiveIdAuthentication          : False
AdfsAuthentication            : False
OAuthAuthentication           : False
ExternalAuthenticationMethods : {Fba}
regards
Tom

Exchange server 2013 setup encounter error

anyone pls help me, i'm ready setup few time still facing same error.
Error:
The following error was generated when "$error.Clear();
if ($RoleCustomerFeedbackEnabled -ne $null)
$organizationConfig = get-OrganizationConfig;
if ($organizationConfig.CustomerFeedbackEnabled -ne $False)
Set-ExchangeServer -Identity $RoleFqdnOrName -CustomerFeedbackEnabled $RoleCustomerFeedbackEnabled;
" was run: "Property CustomerFeedbackEnabled can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).".

Hi,
First, please make sure you have installed all the required prerequisites. For Exchange 2013 prerequisites, please refer to this
article.
Then please verify if there is a legacy server via ADSIEDIT. If there is a legacy object, please delete this legacy object. In registry editor, remove the watermark key and action key from the following path and then reinitiate the setup to check the result.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ExchangeServer\v15\HubTranportRole
If the issue persists, to narrow down the issue, I recommend you check the setup log for related error message.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Installation error for Exchange Server-2013

I am trying to install exchange server-2013 on my Windows server-2012
machine. I have configured per-requisite applications and develop the server environment with active directory roles.
At my readiness check option, it shows the following error:-
"An unsupported operating system was detected . Exchange server-2013 client access and mailbox server roles support windows server -2008R2 SP1 or later and windows server-2012".
I am not using any V-machine or option. So how do i resolve the issue to install the Exchange server-2013? Please help me.
Regard
Azad
Azadur Sarker 6, Seaford street Stoke-on-Trent, ST4 2EU

Hi I found after promoting the exchange server as a Domain controller re-installing AD prep and running extending Schema completed successfully , I'm now able to get rid of exchange cmdlet logs event id and can successfully see and connect through the
exchange 2013 management shell
"Get-Exchangeserver"
However still not able to connect to https://localhost/eac and when i re-run setup
01-28-2014 21:10:16.0804] [0] Starting Microsoft Exchange Server 2013 Setup
[01-28-2014 21:10:16.0804] [0] **********************************************
[01-28-2014 21:10:16.0804] [0] Local time zone: (UTC-05:00) Eastern Time (US & Canada).
[01-28-2014 21:10:16.0804] [0] Operating system version: Microsoft Windows NT 6.2.9200.0.
[01-28-2014 21:10:16.0804] [0] Setup version: 15.0.516.32.
[01-28-2014 21:10:16.0804] [0] Logged on user: TESTLAB\Administrator.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='sourcedir', Value='D:\'.
[01-28-2014 21:10:16.0867] [0] Command Line Parameter Name='mode', Value='Install'.
[01-28-2014 21:10:16.0882] [0] RuntimeAssembly was started with the following command: '/sourcedir:D: /mode:Install'.
[01-28-2014 21:10:17.0085] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:17.0726] [0] Setup is choosing the domain controller to use
[01-28-2014 21:10:17.0820] [0] The MSExchangeADTopology has a persisted domain controller: Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] PrepareAD has been run, and has replicated to this domain controller; so setup will use Exch2013.Testlab.labyyz.testnet.rim.net
[01-28-2014 21:10:18.0023] [0] Setup is choosing a global catalog...
[01-28-2014 21:10:18.0023] [0] Setup has chosen the global catalog server Exch2013.Testlab.labyyz.testnet.rim.net.
[01-28-2014 21:10:18.0023] [0] Setup will use the domain controller 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Setup will use the global catalog 'Exch2013.Testlab.labyyz.testnet.rim.net'.
[01-28-2014 21:10:18.0023] [0] Exchange configuration container for the organization is 'CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0038] [0] Exchange organization container for the organization is 'CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0054] [0] Setup will search for an Exchange Server object for the local machine with name 'EXCH2013'.
[01-28-2014 21:10:18.0210] [0] Exchange Server object found : 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0210] [0] The following roles have been unpacked: BridgeheadRole ClientAccessRole MailboxRole UnifiedMessagingRole FrontendTransportRole AdminToolsRole CafeRole
[01-28-2014 21:10:18.0210] [0] The following datacenter roles are unpacked:
[01-28-2014 21:10:18.0210] [0] The following roles are installed: BridgeheadRole AdminToolsRole
[01-28-2014 21:10:18.0210] [0] The local server has some Exchange files installed.
[01-28-2014 21:10:18.0226] [0] Server Name=EXCH2013
[01-28-2014 21:10:18.0242] [0] Setup will use the path 'D:\' for installing Exchange.
[01-28-2014 21:10:18.0257] [0] Setup will discover the installed roles from server object 'CN=EXCH2013,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=TestLab,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Testlab,DC=labyyz,DC=testnet,DC=rim,DC=net'.
[01-28-2014 21:10:18.0257] [0] 'BridgeheadRole' is installed on the server object.
[01-28-2014 21:10:18.0257] [0] The installation mode is set to: 'Install'.
[01-28-2014 21:10:39.0632] [0] An Exchange organization with name 'TestLab' was found in this forest.
[01-28-2014 21:10:39.0632] [0] Active Directory Initialization status : 'True'.
[01-28-2014 21:10:39.0632] [0] Schema Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Organization Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] Domain Configuration Update Required Status : 'False'.
[01-28-2014 21:10:39.0632] [0] The locally installed version is 15.0.516.32.
[01-28-2014 21:10:39.0632] [0] Exchange Installation Directory : 'C:\Program Files\Microsoft\Exchange Server\V15'.
[01-28-2014 21:10:39.0664] [0] Applying default role selection state
[01-28-2014 21:10:39.0710] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:10:39.0710] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:10:39.0710] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:10:39.0710] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:10:39.0710] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:10:40.0273] [0] Finished loading screen IncompleteInstallationDetectedPage.
[01-28-2014 21:11:08.0117] [0] Setup is determining what organization-level operations to perform.
[01-28-2014 21:11:08.0117] [0] Because the value was specified, setup is setting the argument OrganizationName to the value TestLab.
[01-28-2014 21:11:08.0117] [0] Setup will run from path 'C:\Program Files\Microsoft\Exchange Server\V15\'.
[01-28-2014 21:11:08.0117] [0] InstallModeDataHandler has 0 DataHandlers
[01-28-2014 21:11:08.0117] [0] RootDataHandler has 1 DataHandlers
[01-28-2014 21:11:08.0335] [0] Finished loading screen SetupProgressPage.
[01-28-2014 21:15:30.0513] [0] End of Setup
[01-28-2014 21:15:30.0513] [0] **********************************************

Error occurred at the 7 of 15 step of Microsoft Exchange Server 2013

Hi all to every techies ....
I'm a new to exchange server 2013 , I tried to install exchange server 2013 on windows server 2012 but couldn't get the success , It stops either 7 or 8 step of 15 , I tried to google it out but can not getting any progress , I tried to remove it , I deleted
by using ADSI Edit then I removed from the IIS then I delete the Microsoft folder from the Installed directory , and also I removed it from the registry editor as well , Thing thing is pulling my hair out my scalp , Any related help highly appreciated ,
The registry key (pickup / transport) doesn't exist in specified registry location , (i.e HKEYLM_SOFTWARE_MICROSOFT_EXCHANGESERVER
Thank you all
Neil Patric

Hi,
To understand more about the issue, I’d like to confirm the detail error when the installation failed.
As far as I know, deployment of an Exchange Server 2013 server goes through three main stages.
1. Preparing Active Directory (if you are installing Exchange Server 2013 for the first time)
2. Installing the Exchange Server 2013 pre-requisites on the server
3. Running Exchange Server 2013 setup
For more information, you can refer to the following article:
http://exchangeserverpro.com/how-to-install-exchange-server-2013/
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,
Angela Shi
TechNet Community Support

Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?

Using Outlook Web App Web Parts in Exchange Server 2013 - OWA ? Possible?
We recently upgraded from Exchange 2010 to Exchange 2013.
The links that used OWA Web parts have completely stopped working and generate the " :( something went wrong contact your help desk" screen for domain Authenticated users other than myself. The links accessed content of a Shared Account of which
I am an owner and can set the necessary permissions using the Outlook 2013 client.
Using the example from the link provided below we were able to provide calendar access to all authenticated users in our area. The link for calendar still works for me but for noone else. Additionally, all navigation menus are missing when I use this link.
<server>/owa/<SMTP address>/?cmd=contents&module=calendar&view=weekly name
Another crafted link provided web access to our group's task list. This has completely stopped working for anyone including myself. However, when I use "open another mailbox" I am able to navigate to the needed pages.
<server name>/owa/<SMTP address>/?cmd=contents&module=tasks
These links were crafted using advice provided from this provided link.
technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx
Is it still possible to use Outlook Web App Web Parts in Exchange Server 2013 - OWA?
Or
Is this a misconfiguration of some sort?
My IT support has given up and closed out the ticket stating that maybe Microsoft will fix this someday...

Hello,
At present, there is no official article to verify whether we can use Outlook Web App Web Parts in Exchange Server 2013. In exchange online, the Outlook Web App Parts is supported.
Cara Chen
TechNet Community Support
Hi, you said this feature is supported in Exchange Online (I understand you're referring to Office 365). Can you please point me to some documentation as I was trying to use it with my E3 account and it doesn't seem to work?
What I'm trying to acomplish is something similar to our old URL (Exchange 2010) in Office 365:
https://ourserver.mydomain.com/owa/[email protected]/?cmd=contents&module=calendar&view=monthly
The best I can do in Office 365 is this:
https://outlook.com/owa/mydomain.com/[email protected]/#path=/calendar
But it's clearly not the same and Office 365 ignores all the information I add to the URL. I would greatly appreciate something in the line of the document referred by 'MarquetteENG' (technet.microsoft.com/en-us/library/bb232199(v=exchg.141).aspx)
Thanks.
Paulo.
Paulo Dias - IT Pro Evangelist

Public Folder in exchange server 2013

We are using an legacy application developed in Classic ASP. In this application we are rendering the message items in the public folder on the exchange server 2003.
Now we are going to migrate our exchange server 2003 to exchange server 2013.
Do exchange server 2013 have public folder? Is this migration have impact on the public folders usage.
Please let me know for any clarifications.

There will be no co-existence support for Exchange Server 2003. In your scenario, you will have to migrate twice, once from Exchange 2003 to Exchange 2007 or 2010, then again to Exchange 2013 or another option you have to proceed that by using any third-party
migration tool to accomplish this task in one go. When you preparing to migrate mailbox, you can have a look at
exchange server deployment assistant to see the current recommended steps for your configuration. A good resource for swing migration direct from exchange 2003 to 2013 can be explored at
here.
In the same way, You cannot migrate public folders directly from Exchange 2003. You will have to move all public folder databases and replicas to Exchange 2007 SP3 RU10 or later. No public folder replicas can remain on Exchange 2003.
I would like to refer on couple of links mentioned below. It will help you better to clarify the scenario further :
Understanding the public folder architecture
Public folder migration

New Deployment of Exchange Server 2013.

Hello All,
Good Day !!
We are planning to install Exchange 2013 Mailbox and Client Access on single server ( Windows Server 2012 Standard).
Currently Active Directory roles runs on windows server 2008R2 Sp1.
Its a new deployment for exchange as currently we are using Godaddy email server ( Can we migrate all our emails from Go daddy to our exchange Server).
Also confirm current active directory will support the installation and deployment of Exchange Server 2013.
How much HDD, RAM and CPU cores are required to support exchange Server Mailbox and Client Access roles( Users are 30 ).
How many Static IP's and SSl certificates are required for exchange.
Atlast as i said its new deployment please suggest if anything else is missing from my end.

Hello,
I recommend using professional cheat-sheet articles for Exchange 2013 sizing:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part1.html
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-sizing-cheat-sheet-part2.html
The server's requirements depend on many factors ie. number of emails received/sent, mailboxes sizes etc.
In addition your AD environment's level supports Exchange 2013 deployment. You will need only prepare your schema and forest for Exchange installation. You will need also at least one public IP address and SSL certificate for that server.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

Exchange server 2013 Standard will support for Exchange cal Enterprise???

Hi,
We have Purchased Exchange Server 2013 STD Edition and Exchange server CALs are Enterprise.
is it compatable for this...
can u give reply for this...

Hello Sashys,
Here’s full explanation:
http://office.microsoft.com/en-us/exchange/microsoft-exchange-server-licensing-licensing-overview-FX103746915.aspx. You should have at least standard CAL for each of your users. Enterprise CAL's are an add-on to the standard license, that provides additional
features. Moreover both types of CAL's can be used with either Exchange server 2013 Standard or Exchange server Enterprise.
Hope it helps,
Adam
www.codetwo.com
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others
find the answer faster.

Microsoft Exchange Server 2013 Cumulative Update 7 Setup - Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error - Set-SharedConfigDC

What am I trying to do?
I have tried installing Microsoft Exchange Server 2013 Cumulative Update 7 Setup on a fresh install of Windows Server 2012 R2 but it gets stuck when running the setup exe on Step 8 of 14 “Mailbox Transport Service” I have included full
error logs at the bottom of the page but the basics are in order it will throw which loop around are:
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
Exchange is currently running in the envirmonet on 2010 Sp3 I am installing 2013 CU7 fresh so I can migrate the databases over.
What am I running?
2 X DC on domain and forest functional level 2008R2 both writable
1 X fresh install of Windows 2012 R2 which is domain joined
What have I tried?
Checked Ipv6 is enabled on all DC NICS and Existing Exchange Servers
Rebooted every server
Run setup as Administrator
My account is part of the domain Enterprise Admin group
Tried adding "Exchange Server" or "Exchange Enterprise Servers" to the group policy and doing the relevant gpupdate /force and reboot :
Computer Configuration Windows Settings
Security Settings + Local Policies
User Rights Assignment Mange auditing and security log
Turned off firewall on DC and Exchange Server even stopped the service
Turned off all AV on the DC and Exchange Server
Checked I could telnet to global catalog servers on port 3268 which I can
Checked the global catalog records existed in DNS which they all do
Done the obvious ping tests all round which confirms connectivity
Schema has been prepared using appropriate commands before running the setup exe
setup.exe /PrepareSchema /IacceptExchangeServerLicenseTerms
Making sure the following path has full permissions:
EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
Restarted Microsoft Exchange Active Directory Topology service
DcDiag all looks good
What have I noticed that is suspicious?
Microsoft Exchange Transport service will not start even though both of its dependences services have started:
Microsoft Filtering Management Service
Microsoft Exchange Active Directory Topology Service
It will eventually error with
“Windows could not start the Microsoft Exchange Transport Service on local computer
Error 1053: This Service did not respond to the start of control request in a timely fashion”
This error is from the GUI wizard itself:
Error:
The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
" was run: "System.Exception: Unable to set shared config DC.
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Exchange logs which have been written:
**The error will loop around for 8 minutes on trying to set-sharedconfig DC whatever this is trying to do ??
[01/20/2015 17:13:20.0084] [2] Active Directory session settings for 'Set-SharedConfigDC' are: View Entire Forest: 'True', Configuration Domain Controller:mydomain.com', Preferred Global Catalog: 'mydomain.com', Preferred Domain Controllers:
'{ mydomain.com}'
[01/20/2015 17:13:20.0084] [2] User specified parameters:
-DomainController:mydomain.com' -ErrorVariable:'setSharedCDCErrors' -ErrorAction:'SilentlyContinue'
[01/20/2015 17:13:20.0084] [2] Beginning processing Set-SharedConfigDC
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details No Minimal Required Number of Suitable Directory Servers
Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0178] [2] No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites.
[01/20/2015 17:13:20.0178] [2] Ending processing Set-SharedConfigDC
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] An error ocurred while setting shared config DC. Error: The call to Microsoft Exchange Active Directory Topology service on server 'TopologyClientTcpEndpoint (localhost)' returned an error. Error details
No Minimal Required Number of Suitable Directory Servers Found in Forest mydomain.com Site Default-First-Site and connected Sites..
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:20.0193] [2] Waiting 30 seconds before attempting again.
[01/20/2015 17:13:20.0193] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0195] [2] Beginning processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0273] [2] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [2] Ending processing Write-ExchangeSetupLog
[01/20/2015 17:13:50.0288] [1] The following 1 error(s) occurred during task execution:
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] 0. ErrorRecord: System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)
[01/20/2015 17:13:50.0288] [1] [ERROR] The following error was generated when "$error.Clear();
$maxWait = New-TimeSpan -Minutes 8
$timeout = Get-Date;
$timeout = $timeout.Add($maxWait);
$currTime = Get-Date;
$successfullySetConfigDC = $false;
while($currTime -le $timeout)
$setSharedCDCErrors = @();
try
Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;
$successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);
if($successfullySetConfigDC)
break;
Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);
catch
Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);
Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");
Start-Sleep -Seconds 30;
$currTime = Get-Date;
if( -not $successfullySetConfigDC)
Write-ExchangeSetupLog -Error "Unable to set shared config DC.";
        " was run: "System.Exception: Unable to set shared config DC.
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target, Boolean reThrow, String helpUrl)
   at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
   at Microsoft.Exchange.Management.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
[01/20/2015 17:13:50.0288] [1] [ERROR] Unable to set shared config DC.
[01/20/2015 17:13:50.0288] [1] [ERROR-REFERENCE] Id=AllADRolesCommonServiceControl___ee47ab1c06fb47919398e2e95ed99c6c Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[01/20/2015 17:13:50.0288] [1] Setup is stopping now because of one or more critical errors.
[01/20/2015 17:13:50.0288] [1] Finished executing component tasks.
[01/20/2015 17:13:50.0304] [1] Ending processing Install-BridgeheadRole
Windows Event Viewer:
Process Microsoft.Exchange.Directory.TopologyService.exe (PID=5276) Forest mydomain.com. Exchange Active Directory Provider couldn't find minimal required number of suitable Global Catalog servers
in either the local site 'Default-First-Site' or the following sites:

Hi apl228,
1. Please make sure the IPv6 is enabled.
2. Please make sure the account that install Exchange server has Administrator permission.
3. Please make sure DNS has been configured correctly.
Thanks
Mavis Huang
TechNet Community Support

Mail Delivery betweek Exchange Server 2013 co-existance with Exchange server 2010

Hello Guys
I have a mailflow issue, hoping someone can help with detail description, below is the setup
Exchange server 2010 SP3 with all roles in one server
Exchange server 2013 SP1 with CU6 with all roles in one server - this server is in a different subnet to the 2010 server. I am able to see exchange 2010 databases and mailboxes from Exchange 2013. For testing purposes, I have moved 3 mailbox from 2010
to 2013. These 3 mailbox, is able to send and receive email from Internet but to each other via OWA or Outlook. These 3 mailbox also not able to send to receive email from any mailbox that is still in 2010 server via OWA or Outlook. I am not planning the whole
server cutover in a go and planning to do state by stage mailbox migration so I need mailflow working properly. When I send an email from one of the migrated mailbox that is in 2013 server, I can see that the email leaves the mailbox outbox and sits in the
queue ..
Can someone please provide detailed solution what needs to be configured?
MCITP, MCSA, MCSE,VCP - Consultant, Solution Design, Implementation

Hi,
1.please check the mailbox send and receive quota for exchange 2013 migrated mailbox.
2.Please check the email attributes of the exchange 2013 migrated mailbox because it seems to be a problem with that particular mailbox.
3.Then do the message tracking and that would be the only way to find the where the send messages has gone.
4.Please check and confirm you have an enough space on the disk where exchange queue database is residing.
I think I need to create a receive connector in the 2013 to receive from 2010 ?
No need ,by design exchange 2013 cas server default frontend receive connector will be having an
entire ipv4 and ipv6 segment and anonymous connection is checked by default.
I think I also need to create a send and receive connector for 2013 users to each other?
No need , an intra organisation send connector and the default receive connectors in exchange will be used
for internal mail flow between the exchange 2013 users.
Please reply me if you have any queries .
Regards
S.Nithyanandham
Thanks S.Nithyanandham

Exchange Server 2013 Database not showing in ECP after removal of Exchange Server 2010

I recently complete the migration of my Exchange 2010 server to Exchange 2013. I then proceeded to uninstall the 2010 server using setup.com /m:uninstall. At the end of the process I received an error that it did not complete the uninstall.
I checked the server and Exchanged 2010 was removed. When I checked ECP on 2013 it still showed the old 2010 server listed. I used ADSI edit and manually removed the old sever.
Now when I log into 2013 ECP I only see the one serve but when I go into databases, none are listed. I check under the server itself and it shows the database that it is using but it is not listed under the database tab.
If I do a search under the database tab I can find it and adds it to the list. I can then open and view details.
My issue is, after I log out and then back in, I have to run the search to find the database again. In ideas on how to have it show up in the list like it did before I removed the 2010 Exchange server?
Thank you,

Hi,
From your description, I recommend you verify the following things for troubleshooting:
1. Please make sure that AD replication is completely by checking the user object's homeMDB attribute. This value should contain the DN value of the Exchange Server 2013 mailbox database.
2. Wait 30 minutes for the cache on the Exchange Server 2013 Client Access Server to clear or restart the MSExchangeOWAAppPool on the Exchange Server 2013 Client Access Server.
For more information, here is a kb for your reference.
Exchange 2013 Redirects to Exchange 2010 for OWA and ECP
http://support.microsoft.com/kb/2931385
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange Server 2013 - Lab setup with internal emails only

Hi,
I'm new to Exchange Server 2013. I've started a POC on the product by setting up a Lab environment with one 1 AD server and 1 Exchange server (Both Windows 2012 R2). As this is a POC I just need the internal email communication. I don't want the mails to
go over the internet.
I've completed the installation part and just started to configure Send/Receive connectors and got stuck with the question whether the connectors are required or not.
Could someone please help me out in configuring internal email setup for Exchange 2013 lab setup.
Regards,
Nithin

Hi,
You need not to configure send/receive connectors for internal email.
The following article for your reference:
http://technet.microsoft.com/en-us//library/aa996395(v=exchg.150).aspx
Default Receive connectors created during setup
Certain Receive connectors are created by default when you install the Mailbox server role.
Default Receive connectors created on a Mailbox server running the Transport service
When you install a Mailbox server running the Transport service, two Receive connectors are created. No additional Receive connectors are needed for typical operation, and in most cases the default Receive connectors don't require a configuration change.
These connectors are the following:
Default <server name>   Accepts connections from Mailbox servers running the Transport service and from Edge servers.
Client Proxy <server name>   Accepts connections from front-end servers. Typically, messages are sent to a front-end server over SMTP.
Each connector is assigned a TransportRole value. You can use it to determine the role the connector is running in. This can be helpful in cases where you are running multiple roles on a single server. In the case of each Receive connector previously
mentioned, their TransportRole value is HubTransport.
To view the default Receive connectors and their parameter values, you can use the
Get-ReceiveConnector cmdlet.
Default Receive connectors created on a Front End Transport server
During installation, three Receive connectors are created on the Front End transport, or Client Access server. The default Front End Receive connector is configured to accept SMTP communications from all IP address ranges. Additionally, there is a Receive
connector that can act as an outbound proxy for messages sent to the front-end server from Mailbox servers. Finally, there is a secure Receive connector configured to accept messages encrypted with Transport Layer Security (TLS). These connectors are the following:
Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.
Outbound Proxy Frontend <server name>   Accepts messages from a Send Connector on a back-end server, with front-end proxy enabled.
Client Frontend <server name>   Accepts secure connections, with Transport Layer Security (TLS) applied.
In a typical installation, no additional Receive connectors are required.
Niko Cheng
TechNet Community Support

Exchange Server 2013 setup / coexistance Exchange 2010

Similar Messages

Maybe you are looking for