First Exchange 2013 server in an Exchange 2010 SP3 organization

I've read the documentation that states to install Exchange 2013 with CU2 as the first Exchange 2013 server in an organization running Exchange 2010 SP3. Maybe I over-read this to mean "Exchange 2013 with at least CU2" (meaning to start with Exchange2013-x64-cu3.exe),
but when I installed the CU3 version I ended up with Standard rather than Enterprise. I need to run 2013 with Enterprise. I've looked around for an Enterprise version of Exchange2013-x64-cu3.exe but cannot find one.
How do I install Exchange 2013 Enterprise into my Exchange 2010 SP3 organization? Thank you.

Please review
http://technet.microsoft.com/en-us/library/bb232170(v=exchg.150).aspx
These (Exchange 2013 Standard Edition and Enterprise Edition)
licensing editions are defined by a product key. When you enter a valid license product key, the supported edition for the server is established. Product keys can be used for the same edition key swaps and upgrades only; they can't be used
for downgrades. You can use a valid product key to move from the evaluation version (Trial Edition) of Exchange 2013 to either Standard Edition or Enterprise Edition.
You can also use a valid product key to move from Standard Edition to Enterprise Edition.

Similar Messages

Exchange 2013 server to new Exchange 2013 server

Hello,
We have a Exchange 2013 server that is hosted outside the company and would like to move the server in house.
To do this we plan on standing up our own Exchange 2013 server and move the mailboxes and such over to the new server. My question is there any kind of documentation with steps to take to make sure nothing is left behind\missed?
THank you.
Tom

Hi Tom,
Its two different organization and you need to follow cross forest migration to migrate mailbox from one organization to another. Below links has the details steps to perform cross forest migration for exchange 2010 and you could follow the same step for
Exchange 2013 as well.
http://blogs.technet.com/b/meamcs/archive/2011/06/10/exchange-2010-cross-forest-migration-step-by-step-guide-part-i.aspx
http://blogs.technet.com/b/meamcs/archive/2011/10/25/exchange-2010-cross-forest-migration-step-by-step-guide-part-ii.aspx
http://blogs.technet.com/b/meamcs/archive/2011/10/25/exchange-2010-cross-forest-migration-step-by-step-guide-part-iii.aspx
Alternatively, you could also use some third party tool like Exchange Server Manager to perform this task much easier
http://www.lepide.com/exchange-manager/
Regards,
Krishna
http://smtpport25.wordpress.com

Unable to connect to local Exchange 2013 server when opening Exchange Management shell

Hi Everyone
Yesterday evenything was working fine, and then this morning, I`m unable to establish a connection with the Exchange shell. I receive the following errors. Any help is appreciated.
         Welcome to the Exchange Management Shell!
Full list of cmdlets: Get-Command
Only Exchange cmdlets: Get-ExCommand
Cmdlets that match a specific string: Help *<string>*
Get general help: Help
Get help for a cmdlet: Help <cmdlet name> or <cmdlet name> -?
Show quick reference guide: QuickRef
Exchange team blog: Get-ExBlog
Show full output for a command: <command> | Format-List
Tip of the day #55:
Want to view the mounted status of all mailbox databases? Type:
Get-MailboxDatabase -Status | Format-Table Name, Server, Mounted
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH02.BLCLAB.CA.
New-PSSession : [c-exch02.blclab.ca] Connecting to remote server c-exch02.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
VERBOSE: Connecting to C-EXCH01.BLCLAB.CA.
New-PSSession : [c-exch01.blclab.ca] Connecting to remote server c-exch01.blclab.ca failed with the following error
message : The client cannot connect to the destination specified in the request. Verify that the service on the
destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service
running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following
command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see
the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : CannotConnect,PSSessionOpenFailed
Failed to connect to an Exchange server in the current site.
Enter the server FQDN where you want to connect.:
VERBOSE: Connecting to .
New-PSSession : Cannot bind parameter 'ConnectionUri'. Cannot convert value
"http:///powershell?serializationLevel=Full;ExchClientVer=15.0.516.32;clientApplication=ManagementShell;TargetServer="
to type "System.Uri". Error: "Invalid URI: The hostname could not be parsed."
At line:1 char:30
+ New-PSSession -ConnectionURI "$connectionUri" -ConfigurationName Microsoft.Excha ...
+                              ~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [New-PSSession], ParameterBindingException
    + FullyQualifiedErrorId : CannotConvertArgumentNoMessage,Microsoft.PowerShell.Commands.NewPSSessionCommand
[PS] C:\Windows\system32>
Ernie Prescott
Updated information.
I can succussfully connect to the exchange powershell from a remote computer, using this method.
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
http://<FQDN of Exchange 2013 Client Access server>/PowerShell/ -Authentication Kerberos
Import-PSSession $Session
So the problem is localised on the server.
Regards

Hi
Try the steps for Error 1 on this link
http://www.petenetlive.com/KB/Article/0000477.htm
Hope it will help
Cheers
If you have any feedback on our support, please click
here
Zi Feng
TechNet Community Support

New Exchange 2013 server, reusing name of 2010 servers

Hi,
I've uninstalled my Windows 2008 R2, 2010 Exchange server from the control panel and removed it from the domain.
The computer object still remains in AD though disabled.
I want to re-use the same computer name on a new server build with Windows 2012 R2, 2013 Exchange.
Do I just delete the disabled object? Do I need to wait sometime before deleting it to allow AD to replicate? Or whats best practise?
Thanks!

A computer object in AD is just an object. You can do anything with it. You can delete it (and it will be recreated when you add a new computer with the same name) or keep it intact (and then a new computer with the same name will attach itself to that object).
Unless your old server was a DC, you needn't any special procedures to follow when deleting its computer object.
Evgeniy Lotosh
MCSE: Server infractructire, MCSE: Messaging

Built-in domain Administrator account not given full access to new Exchange 2013 server

I migrated from Exchange 2010 to 2013 over the weekend. I cannot log into the EAC with my domain administrator account I use to log into all my other servers. I also cannot run the clean-mailboxdatabase cmdlet logged in as this user. I
had no trouble moving mailboxes from the old server to the new server with this account though.
This account is a member of: Domain Admins, Enterprise Admins, Exchange Full Admin, Exchange Organization Admin, Organization Management, Schema Admins, Server Management.
I can log into the EAC with another admin account that has the same memberships as the Administrator account.
I tried giving the account the role of "Databases" as suggested by others to fix the clean-mailboxdatabase issue but that did not work for me either.
The Administrator mailbox has been moved to the new database on the Exchange 2013 server. The Exchange 2010 has been decommissioned and is turned off.

Hi,
Based on my research, to retrieves the mailbox statistics for the disconnected mailboxes for all mailbox databases in the organization, we can try the following command:
Get-MailboxDatabase | Get-MailboxStatistics -Filter 'DisconnectDate -ne $null'
http://technet.microsoft.com/en-us/library/bb124612(v=exchg.150).aspx
Additionally, The Identity parameter specifies the disconnected mailbox in the Exchange database and it can be display name instead of mailbox GUID.
http://technet.microsoft.com/en-us/library/jj863439(v=exchg.150).aspx
Hope it can help you.
Thanks,
Angela Shi
TechNet Community Support

First Exchange 2013 server in 2010 Deployment - 2010 edge is routing SOME inbound mail to new server where it fails.

I have a Barracuda filter receiving all inbound internet mail which delivers to the edge server (both in DMZ). I have one 2010 edge server and one 2010 ht,cas,mailbox server. I have added a 2013 server and started working
on configuring virtual directories. This is a far as I have gotten. Goal is once new box is working to move all mailboxes to 2013 server and remove 2010 mail box server and keep Barracuda and 2010 edge server to pass mail to the 2013 box.
My issue is the edge server is already passing inbound internet mail to the new 2013 server. I see the mail being accepted by the Barracuda and message tracking on the edge shows it as delivered to the new 2013 server, but mailbox
users never receive.
Is my solution to simply create a new send connector from the 2013 server to the 2010 box or could this be something else?
And why is it delivering to a server with now mailboxes on it yet?
Thank you for any help
dean

Hello Dean,
I understand that the message tracking log indicates the email delivered to Exchange 2013 server. Please check the message tracking log on both Exchange 2013 server and Exchange 2010 server.
How about the result? Have you created new 2013 mailbox and tested if it works?
As for the send connector, actually an intra-org send connector will be involved for internal mail flow within an organization. So there is no need to create another send connector.
In addition, I’d like to share you an article about Edge Subscriptions:
Title:
Understanding Edge Subscriptions
Link:
http://technet.microsoft.com/en-us/library/aa997438(v=exchg.141).aspx
Regards,

How to uninstall first exchange 2013 server

I have an existing exchange 2010 SP3 organization. I am planning to install Exchange 2013 RTM on a production server
to try it out.
Can I easily uninstall the exchange 2013 completely after I am finished ? Is it just a matter of control panel/ add remove programs?
Anand_N

Hi Anand,
Before you remove the first Exchange Server computer in the site, I would like to clarify the following thing:
If there are any users or public folders (non-site) homed on this Exchange Server computer, you must move the mailboxes to another server in the site, and you must replicate any public folders to other servers in the site, to ensure that you do not lose
data.
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

First exchange 2013 server install in coexistence: Recreating arbitration mailboxes first

Hi
We have exchange 2010 servers and I want to introduce the first exchange 2013 server.
Some of our arbitration mailboxes currently in 2010 have become corrupt and my initial exchange 2013 installation failed.
Question: Can I remove existing exchange 2010 arbitration mailboxes and recreate them using EXCHANGE 2013 "SETUP /PrepareAD"???????? Afterall there are no 2013 servers in the environment yet
I wonder if it will fail due to version incompatibilities
Thanks

Hi,
Agree with DJ Grijalva. Exchange 2013 /prepareAD will create the arbitration mailboxes for Exchange 2013. And the arbitration mailboxes between Exchange 2010 and Exchange 2013 are different. So I recommend you use the 2010 /prepareAD to recreate the arbitration
mailboxes for 2010.
Hope my clarification is helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Addition of Exchange 2013 server to Exchange 2010 organization broke Exchange

This is somewhat of an emergency, since Exchange is down completely for us right now.
I just migrated from SBS2003 to Exchange 2010 on Windows 2012 over last weekend. Everything is now stable, and SBS2003 is shut down. Now I am attempting to migrate from Exchange 2010 to Exchange 2013.
The plan was this:
Install Exchange 2013 on another server (Windows 2008R2)
Wait until everything is replicated
Remove the Exchange 2010 server from the organization
Uninstall Exchange 2010
Install Exchange 2013 on the Windows 2012 server
Wait until everything is replicated
Remove Exchange 2013 from the Windows 2008R2 server
But here is what actually happened:
Installed all Exchange 2013 prerequisites on the Windows 2008R2 server
Began Exchange 2013 server setup on the Windows 2008R2 server. Included both Mailbox & CAS roles
At step 11 of 15 (not sure what that was, though), received this error message:
Error: The following error was generated when "$error.Clear();
netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes
" was run: "The term 'netsh' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.".
And setup halted. I ran the netsh command via the command prompt, and it correctly said something about four rules being created or updated (not sure of exact verbiage). Now, when I try to restart setup, it says it is in the middle and will try to complete
but stays at 0%. But here is the most immediate issue:
Now I cannot access e-mail from any workstations (says Exchange server is unavailable)
Opening EMC on the Exchange 2010 server: I get as far as Microsoft Exchange -> Microsoft Exchange On-Premises and get this error:
The attempt to connect to http://[Exchange 2010 FQDN]/PowerShell using "Kerberos authentication failed: Processing data from remote server [Exchange 2010 FQDN] failed with the following error message:
Couldn't find Enterprise Organizaiton container. (Note that it refers to the local server as remote server)
I get an event 7031 on the Exchange 2010 server: The Microsoft Exchange Service Host service terminated unexpectedly
Opening the Exchange Management Shell on the Exchange 2010 server yields the same message regarding "Couldn't find the Enterprise Organization container..."
It also says, "Connecting to [Exchange 2013 server FQDN], then says connected to that server. Opening EMS on the Exchange 2013 server seems to connect correctly to the Exchange 2013 server, but there is no EM Console available there.
At this point, I am lost. I will continue to research this online but may have to call Microsoft soon, since we are entirely down at the moment. Any help is much appreciated!

All of the above, I believe. And E2003 is on the DC (and functioning just fine); E2012 on a member server (this is a very small environment--they have only the DC, a DB2 database server, and a lightly-used and old terminal server). I just spent 12 hours
on the phone with MS support on this issue, and it has now come down to this: the Exchange 2013 installation will not run to completion. It has failed repeatedly at a few points today, all related to the shell being unable to access Windows EXEs or environment
variables with variations on this error:
"...not recognized as the name of a cmdlet, function, script file, or operable program..." for each of these:
netsh (windows exe)
sc.exe (windows exe)
hostname (windows command that returns workstation name)
These all work from the command prompt. I am currently stuck on sc.exe failing on each attempt to install Exchange 2013 or Exchange 2013 SP1. Nor can I just remove it--it insists on attempting to proceed with installation even with the manual command-line
argument to remove it instead.
At this point, I am awaiting a night call back from Microsoft support, since the technician that worked on it with me for 12 hours today had to go home.

Howto deploy a temporary exchange 2013 server for migration between two Office 365 accounts?

Objective:
We plan to migrate our office 365 from our current tennant (E3) to a new tennant (M) to drastically cut our annual costs for the same services, while retaining the mail and group memberships of all our users. This will involve installing an exchange server
to download and upload mail from the old tennant to the new tennant.
Background:
We are a longtime O365 customer, and have been a customer since before the "Midsize business" plans existed. There is no "cookie cutter" migration path from E3 to M. Microsoft currently recommends deploying an MS exchange server and off-boarding
the mailboxes from your E3 subscription and then On-boarding them to a new account under the M plan. As ridiculous as this is, this is indeed the path our company has decided to go. It isn't cool/fair that we're being shackled to the E plans (that are
vastly more expensive) when we're a small/midsize business that has been a longtime customer of O365, while new customers of equal size to us can expect to save over $4000 annually. The services (when compared) offered are nearly identical.
After calling MS support several times for guidance for this issue, I am advised that we should contact a 'partner' and ask for their support in doing this migration. We did as requested and were provided a quote to the tune of approximately $15,000 to do this
migration for us. Obviously this is unacceptable, and thus our business has decided to rely on my abilities to get it done. Again, involving an MS partner is not an option.
Environment:
1 MS AD domain:
- Original FQDN was @contoso.ca of this domain and UPNs were [email protected]
- UPN has been changed to [email protected] to allow for ADFS
- ADFS has been deployed and SSO works for all users with UPN [email protected]
- An "On-Prem exchange server" does not yet exist
1 O365 Account where main tennant FQDN is @corp.com
- There are 5 registered domains
-contoso.ca
-corp.com
- contoso.legacy.ca
-deprecated/will be deleted
-deprecated/will be deleted
- There are 40 E3 licenses, all using a @corp.com UPN
- There are 5 E1 licenses (we acknowledge that these will be upgraded to an M following the migration) that use the UPN contoso.legacy.ca
- No accounts currently use contoso.ca for email
- O365 was upgraded to 'the latest version' sometime in summer 2013.
Migration Plan (High Level):
Setup a local windows server (trial license)
Deploy an exchange 2013 server (trial license) on the aforementioned windows server http://technet.microsoft.com/en-us/evalcenter/hh973395.aspx
  Prepare and deploy Dirsync Deployment
of Dirsync
Add exchange to office 365 and begin replicating the mailboxes from the cloud to the exchange server. Wait for synchronization to complete.
More information: http://technet.microsoft.com/en-us/library/hh534377(v=exchg.150).aspx
http://help.outlook.com/en-us/140/ff633682.aspx
Evaluate total time it took to sync data.
Time it takes to download data to exchange should be relatively similar to time it takes to restore mail to the new service.
Open a new office365 account under the M plan.
  Plan a 1 hour mail & contoso.ca domain login outage
temporarily change all user UPN's to match the new tennant
perform a dirsync to the new tennant
disable dirsync after all accounts have been auto-created/provisioned
re-establish UPN + mail access.
Plan a date and time for the cut over.
remove the exchange hybrid server from the old tennant.
Point MX records directly to the exchange server.
Cut office 365 service.
  After the 30 minutes ~ 1 hour 'mandatory' wait time imposed by MS to 'register' the domain with O365, add @corp.com to
the new tennant
fix all user UPN's in the cloud to match their real UPN's.
This can be done with powershell.
attach exchange hybrid server to new tennant
Point MX records to the new tennant
Migrate all data from the local exchange server to the cloud under the new plan.
Current progress (Lab):
I have created a sandbox (Lab with no internet access or connectivity to production) environment in VMware and cloned the following servers to it:
1x Domain Controller (DC) running windows server 2012 (named DC02)
1x DC running windows server 2008 R2 (named DC01)
1x windows server 2012 R2 - prepped with all the pre-requisites to install exchange 2013. (named EXC01)
Where I am stuck / Problem:
I have installed exchange on the server EXC01 in the lab environment using my account. I am a domain administrator in the contoso.ca domain, but my UPN is [email protected].
After the installation of exchange, I notice that my email address in Active Directory changed from @corp.com to @contoso.ca. By default, I do not see @corp.com to be an available email address to select as my email address, and changing it in AD does not resolve
the problem.
In the exchange portal, I found "Mail flow ---> Accepted Domains", and believe I should add @corp.com to the accepted domain list. Questions:
1) Must I add corp.com and the other domains that exist in office 365 to the local exchange before I go through with the hybrid wizard?
2) If I must add them to exchange, I am provided with three choices:
- Authoritative Domain
- Internal Relay Domain
- External Relay Domain
Given that the domain is currently in office365 and is authoritative there, which of these applies?
3) Most documentation I have found has been about a one way migration from on-prem to the cloud. I have had a hard time finding a step by step guide for cloud to local (new server) and then back to cloud. Does anyone here have any good documentation for this
process? Would love it if it took into consideration multiple UPN/email addresses.

Hi,
Here are my answers you can refer to:
1. Yes, we should select the primary SMTP domain for our organization and any other accepted domains that will be used in the hybrid deployment:
http://technet.microsoft.com/en-us/library/jj200787(v=exchg.150).aspx
2. It depends on the usage of the specific accepted domain. And Exchange version has no influence.
To determine it, you can firstly check the function of the three types in the following article:
http://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx
3. Here are some reference about the migration from on-premise Exchange server to Office 365:
http://www.msexchange.org/articles-tutorials/office-365/exchange-online/configuring-exchange-2013-hybrid-deployment-migrating-office-365-exchange-online-part1.html
Additionally, since the issue is related to Exchange online, I recommend you ask for help on our Exchange online forum to get more professional help:
http://social.technet.microsoft.com/Forums/msonline/en-US/home?forum=onlineservicesexchange
If you have any question, please feel free to let me know.
thanks,
Angela Shi
TechNet Community Support

Update from Exchange 2013 Cu2 to SP1 - Outlook 2010 with SP2 clients disconnected

Hi,
we recently upgraded a standalone Exchange 2013 Server to SP1. Owa works fine, but all internal Outlook 2010 Clients (with SP2) get disconnected. Creating a new Profile, and testing the internal autodiscovery leeds to an Error 12030 (Connection reset) during
the discovery process.
I already checked the Service Point, the discovery URLs, even recreated the autodiscover virtual Directory in iis. But nothing changed.
The self signed certificate, that was used before the update is further used, and well known to all Clients. As I tested, OWA is working well everywhere.
Anyone some new ideas?
Best regards
Bernhard

Hi,
How did you recreate outlook profile? Manually or Automatic?
If automatic failed, please try to recreate manually and check the result.
If manual failed, please refer to the following methods to troubleshoot the issue:
1>Try to open the following link and check the result:
https://CASName/autodiscover/autodiscover.xml
2>Try to use RCA to test outlook autodiscover and check the result.
https://testconnectivity.microsoft.com/
Thansk.
Niko Cheng
TechNet Community Support

Exchange 2013 Server Migration

Hello,
We are in the process of migrating from an Exchange 2003 server to an Exchange 2013 SP1 server. The EXCH2003 server is in a separate domain environment than the new EXCH2013 server. We plan to export all mail from the EXCH2003 server and import to the EXCH2013
server.
At this time we are seeing an issue with the new EXCH2013 SP1 server. When we test creating a new profile in Outlook 2010 SP2 on a client machine we receive the following errors:
1) The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
- also -
2) The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action.
We are able to access OWA both internally and externally and can login under multiple user accounts. Also while logged into OWA, mail flow is working, able to send and receive.
We installed and configured a new SSL trusted certificate on the Exchange 2013 SP1 server as well.
At this time our main issue is with Outlook 2010 SP2 and Exchange 2013 SP1 not communicating with each other properly.
Please let us know what other information is needed to help resolve this issue.
Thank you,
Jason Ringholz
Regards, Jason

As commented by ED please make sure autodiscover is pointed to exchange2013.
Please try to restart the services, restart "MS exchange active directory topology services" It will restart the dependent services. Please restart "Microsoft Exchange System Attendant" service also and try
After this try creating a test mailbox in exchange2013 and try to configure the newly created mailbox in outlook2010.
http://support.sherweb.com/Faqs/Show/manual-configuration-guide-for-outlook-2010-exchange-2013
Test OutlookAnywhere using
https://www.testexchangeconnectivity.com/ and check for any error.
Make sure you can ping exchange2013 server by it's name(Netbiosname and FQDN)
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.

Replace Exchange 2013 Server

Hi All,
Hopefully this is somewhat of an easy process.
I have a single Exchange 2013 server running on Windows Server 2012 R2. The server itself is a decent server; however, it was built with a poor design to it so we keep running out of resources.
I now have a newer system and I'd like to replace our current Exchange Server with this one. I've tried searching the web and the only results I seem to find is upgrading/migrating from an older version of Exchange.
How easy would this be to just replace hardware?

Couple of options:
- You can stand up a new 2013 server, move mailboxes.
- You could create a DAG, add 2nd server, seed DB's, make DB's active on new server, remove DB's from first server, decommission first server.
Mike
NOTICE: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2013 Sp1 Coexistence with Exchange 2010 SP3 CU5 HTTP 500

I`m trying to make working OWA coexistence between Exchange 2013 SP1 and Exchange 2010 SP3 CU5.
When user login in to OWA where his mailbox is located on Exchange 2013 server it logon successful and owa opened. When i try to login to the same url with user whose mailbox is located on Exchange 2010 server i get Error http 50
The website cannot display the page : HTTP 500 »https://URLEXCHANGE2013/owa/auth.owa«
The same is, when i use https:// URLEXCHANGE2013/ecp?ExchClientVer=14
URL on Exchange 2013 are different as fro Exchange 2010.
I even tried to setup Internal URL for Exchange 2010 to bi set to »null ,Saem error
Exchange server 2013 Sp1 is installed on Windows server 2012 R2.

Assumption is correct. I have even enable verbose logging, and i can see MSExchange Front End HTTP Proxy , that successfully connect to Exchange 2010 server.
But remember Exchange 2013 is fresh installation on Windows server 2012 R2.
IIS LOG
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=391fd8b3-2b98-494a-8812-d38feda2e5a0&cafeReqId=391fd8b3-2b98-494a-8812-d38feda2e5a0;
443 companyNT\SM_9c071c4922fd420fb fe80::99d1:f542:a4d3:b469%12 MSRPC - 200 0 0 5484
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_IN_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=27cfafa2-8224-4563-918b-0b228c6ee8d4&cafeReqId=27cfafa2-8224-4563-918b-0b228c6ee8d4;
443 - fe80::99d1:f542:a4d3:b469%12 MSRPC - 401 1 2148074254 0
2014-03-04 08:52:53 fe80::99d1:f542:a4d3:b469%12 RPC_OUT_DATA /rpc/rpcproxy.dll [email protected]:6001&CorrelationID=<empty>;&RequestId=6d930bcd-7bbc-415a-a25a-8d6488e91401&cafeReqId=6d930bcd-7bbc-415a-a25a-8d6488e91401;
443 - fe80::99d1:f542:a4d3:b469%12 MSRPC - 401 1 2148074254 15
2014-03-04 08:52:55 10.1.0.36 GET /owa/ &CorrelationID=<empty>;&cafeReqId=551cfdd9-18ac-42d8-aea3-cbb546c9d9fb; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C) https://OWA.company.com/
302 0 0 9937
2014-03-04 08:52:56 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fOWA.company.com%2fowa%2f&reason=0&CorrelationID=<empty>;&cafeReqId=c1b97df9-ec56-4906-b2f5-965551b720ae; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C)
https://OWA.company.com/ 200 0 0 1015
2014-03-04 08:52:56 10.1.0.36 GET /owa/auth/logon.aspx replaceCurrent=1&url=https%3a%2f%2fOWA.company.com%2fowa%2f&CorrelationID=<empty>;&cafeReqId=b92ca682-04f4-4d4f-931e-9a95680ab9ea; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C)
- 200 0 0 671
2014-03-04 08:52:58 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=093bd01a-de59-4519-80f6-067484122091; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 302 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fEXCH2013%2fecp%2f&reason=0&CorrelationID=<empty>;&cafeReqId=c2f7565d-ee6a-48f8-8d86-16d5d3ca65c1; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=ba633030-2376-4bad-a32f-8f160bd87bd4; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING) - 302 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx url=https%3a%2f%2fEXCH2013%2fecp%2f&reason=0&CorrelationID=<empty>;&cafeReqId=5e94172c-d97c-46a9-a602-6030d6f7da2c; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/logon.aspx replaceCurrent=1&url=https%3a%2f%2fEXCH2013%2fecp%2f&CorrelationID=<empty>;&cafeReqId=9ba2caf3-2a03-44a2-8477-2724689e139c; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 46
2014-03-04 08:52:58 10.1.0.36 GET /owa/auth/15.0.847/scripts/premium/flogon.js &CorrelationID=<empty>;&cafeReqId=62bb4655-3bfa-4e07-aa62-27c93e7e8b4d; 443 - 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 0
2014-03-04 08:52:59 10.1.0.36 POST /owa/auth.owa &CorrelationID=<empty>;&cafeReqId=9d52ec1a-2ee1-4954-85e6-89e7e5df407a; 443 [email protected] 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 302 0 0 812
2014-03-04 08:52:59 ::1 GET /OWA/Calendar/[email protected]/calendar/calendar.html &CorrelationID=<empty>;&cafeReqId=4ea66475-9a47-41a4-81cb-6b569715d0d6; 443 - ::1 AMProbe/Local/ClientAccess - 200 0 0 8859
2014-03-04 08:53:01 10.1.0.36 POST /owa/auth.owa &CorrelationID=<empty>;&cafeReqId=b3db7480-2192-436c-b01d-29d0e528cfec; 443 UseronEX2010 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+6.3;+WOW64;+Trident/7.0;+.NET4.0E;+.NET4.0C) https://OWA.company.com/owa/auth/logon.aspx?replaceCurrent=1&url=https%3a%2f%2fOWA.company.com%2fowa%2f
500 0 0 187
2014-03-04 08:53:04 127.0.0.1 GET /Microsoft-Server-ActiveSync/default.eas &CorrelationID=<empty>;&cafeReqId=2e2a655b-00b9-42ae-8789-1e452e6579c3; 443 [email protected] 127.0.0.1 AMProbe/Local/ClientAccess
- 200 0 0 8265
2014-03-04 08:53:14 10.1.0.36 GET /ecp/ &CorrelationID=<empty>;&cafeReqId=8741886f-b9b1-46f9-8c15-baf35809a12c; 443 [email protected] 10.1.0.36 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING)
- 200 0 0 15265
2014-03-04 08:53:14 127.0.0.1 GET /OWA/auth.owa &CorrelationID=<empty>;&cafeReqId=8ad938fb-f2c3-42bf-8718-da62b122422c; 443 - 127.0.0.1 AMProbe/Local/ClientAccess - 302 0 0 15
HTTPERR LOG :
2014-03-04 08:51:48 10.1.0.36 13937 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:51:48 fe80::99d1:f542:a4d3:b469%12 13872 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:52:25 10.1.0.36 13937 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:52:25 fe80::99d1:f542:a4d3:b469%12 13872 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:52:30 127.0.0.1 14122 127.0.0.1 443 HTTP/1.1 GET /RPC/[email protected] 404 - NotFound -
2014-03-04 08:52:30 ::1%0 14121 ::1%0 443 HTTP/1.1 GET /ecp/ReportingWebService/ 404 - NotFound -
2014-03-04 08:54:42 ::1%0 14117 ::1%0 444 - - - - - Timer_ConnectionIdle -
2014-03-04 08:54:48 10.1.0.36 14211 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:54:48 fe80::99d1:f542:a4d3:b469%12 14285 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 BadRequest MSExchangeRpcProxyAppPool
2014-03-04 08:55:35 10.1.0.36 14211 10.1.0.36 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
2014-03-04 08:55:35 fe80::99d1:f542:a4d3:b469%12 14285 fe80::99d1:f542:a4d3:b469%12 444 HTTP/1.1 RPC_IN_DATA /rpc/rpcproxy.dll?EXCH2013.companyNT.local:6001 400 2 Connection_Dropped MSExchangeRpcProxyAppPool
Trace login, ok it is xml, so print is..
-Request Summary
Site
1
Process
8232
Failure Reason
STATUS_CODE
Trigger Status
500
Final Status
500
Time Taken
500 msec
Url
http://EXCH2013.companyNT.local:80/powershell?clientApplication=ActiveMonitor;PSVersion=4.0&sessionID=Version_15.0_(Build_846.0)=rJqNiZqNgZuQkpqT0pqH0ZuQkpqTkYvRk5CcnpOBzsbLzsbGyczJyIHPzNDPy9DNz87L38/Gxc/KxcrJ
App Pool
MSExchangePowerShellFrontEndAppPool
Authentication
Kerberos
User from token
companyNT\SM_9c071c4922fd420fb
Activity ID
{8000134C-0001-E300-B63F-84710C7967BB}
-Errors & Warnings
No.↓
Severity
Event
Module Name
157. view trace
Warning
-MODULE_SET_RESPONSE_ERROR_STATUS
ModuleName
ManagedPipelineHandler
Notification
EXECUTE_REQUEST_HANDLER
HttpStatus
500
HttpReason
Request Failed
HttpSubStatus
0
ErrorCode
The operation completed successfully.
(0x0)
ConfigExceptionInfo
ManagedPipelineHandler
See all events for the request

Second Exchange 2013 server in remote site

Just finished migrating from 2007 to 2013 and decommissioned 2007. Exchange 2013 is running in site A with 350 mailboxes on it. However, almost half of those users reside in site B so the plan is to introduce a second Exchange 2013 server to
this site and migrating mailboxes to it. There already exists a DC & GC in both sites.
My question is, immediately after I introduce Exchange 2013 into site B with CAS & MBX role, client computers from that site will start to receive certificate errors. Will updating the SCP on the new exchange server to point to the SCP on the exchange
server in site A be enough to mitigate that problem? What other precautions will I need to take? Has anybody been down this road?

Hi
You can introduce the second exchange server in the remote site and also setup a DAG. If you are using the same name on your certificate like mail.domain.com then you can use the cert for your second server as well. You need to make sure you have autodiscover
records setup correctly.
Hope this helps. Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

First Exchange 2013 server in an Exchange 2010 SP3 organization

Similar Messages

Maybe you are looking for