New exchange 2013 setup

my existing 2010 environment:
EXCH1 - datacenter 1
EXCH2 - datacenter 2
DAG, both Internet Facing.
Today I installed 3 Exchange 2013 CAS/Mail servers.
EXCH3 - datacenter 1
EXCH4 - datacenter 2
EXCH5 - DR site
I haven't setup mailboxes or anything yet, just external and internal URL's, a wildcard cert and internally OWA successfully proxy's via 2013 then redirect back to 2010 OWA as it should. All 3 2013 servers setup identical... :-)
However, and here is the problem - when EXCH5 is turned on users get prompted for the EXCH5 server cert, when I turn EXCH5 off they do not get prompted.
Any ideas where I should look?
info update -------------------------------------------
while the cert prompt is for the exch5 server cert when I view the cert its actually the correct wildcard public cert I'm using and want.
I have verified that all the virtual directories (via EAC) have the correct internal and external URL's and that the cert is bound to the SMTP and IIS services. One other clue, when I try to launch ecp from exch5 it redirects and logs me into OWA.
Not doing this on any other exch server.
open to suggestions :-)

Hi,
According to your description, it’s wildcard certificate in your environment. And I recommend you check the Outlook provider configuration: get-outlookprovider |fl identity, CertPrincipalName
Additionally, I’d like to confirm the name in the security alert.
If you have any question, please feel free to let me know.
Thanks,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Angela Shi
TechNet Community Support

Similar Messages

New Exchange 2013 CAS server in existing Exchange 2007 Organization

Dear Friends,
We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
https://servername/ecp/?ExchClientVer=15
Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
Thanks in advance!!

Dear Friends,
We have exchange 2007 SP3 with CU13 installed with single copy cluster for database and 1 OWA server for CAS/HT. We will migrate from current to Exchange 2013SP1. As we want to have HA, we have installed 2 new Exchange 2013 SP1 CAS server on widnows 2012
R2 after preparing our organisation for Exchange 2013. The setup went smooth without any error and successfully installed CAS with management tools. After installation it ask to reboot the server which we did. Now after reboot, we are not able to run Exchange
Management Sell. It never connects to the new server. In our old 2007 EMS also doesn't list any exchange 2013 server. We are also not able to connect to new CAS servers with below URL:
https://servername/ecp/?ExchClientVer=15
Its says site under maintenance. Please advise what to check. We were thinking of deploying CAS 1st and make it co-exist with Exchange 2007 before deploying Exchange 2013 mailbox server which will be setup in DAG. What are we doing wrong.
Thanks in advance!!
If you have only the 2013 CAS installed and not the mailbox role, then nothing will really work. Remember, in 2013, the mailbox role does all the work, the CAS is simply a proxy for the most part.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

New Exchange 2013 SP1 install, can't get ECP to display

Hi all,
I stood up a new exchange 2013 environment in my lab running on Server 2012. Everything looks like it should be working. All services running, no errors in the event log, I'm able to get into ECS. When I try and launch the ECP, it spins
for a little bit then I get a page can't be displayed. I've checked that exchange sees it:
I'm stumped. I've been scouring forums and can't pinpoint the issue. I know I could just blow my lab away and try to re-install from scratch but I'm so close to getting this stood up and don't want to just give up. Plus, I'm curious as
to what the cause is and how it's tied into Exchange functionality.
Also, when I try to browse to OWA, the page can't be displayed as well. I've tried to disable Enhanced IE security to no avail.
Any suggestions are appreciated.
Thanks.

Hi,
Please use the https://localhost/ecp URL to logon from the local CAS server and check if you can access EAC.
What's more, I have a test in my environment using Exchange 2013, when I use
https://exc2013cas.contoso.com/ecp to logon EAC, the same error occurs. But when I use
https://exc2013cas/ecp to logon, EAC works well. In your case, I recommend you use the
https://skunkms1/ecp URL to logon EAC and check the result.
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

ActiveSync is not working properly after migrating to new Exchange 2013 SP1 server?!

Few weeks ago we have added new Exchange 2013 SP1 onto our existing Exchange 2007 environment. I have migrated my mailbox to the new Ex2013 server. Everything (send/receive - internally/externally, OWA, OutlookAnywhere) for me and the existing Ex2007
users works fine. The only thing I have trouble with is the ActiveSync! After migrating to the new Ex2013 server my phone stops getting new emails…, existing Ex2007 users don’t have any problems with their mobile phones.
I did ActiveSync test for my user account with ActiveSync Tester and here is what I have:
As you can see from the error above ActiveSync Tester detects ActiveSync on Ex2013 server however something wrong there with form-based auth?! I can’t see any differences in settings for ActiveSync virtual folders in Ex2007 and Ex2013
virtual folders?!
What I’m missing here?! Please help.

Check if the Exchange Servers group does not have the appropriate permission to the mailbox object in Active Directory.
To check whether inheritance is disabled on the user:
1.Open Active Directory Users and Computers.
2.On the menu at the top of the console, click View > Advanced Features.
3.Locate and right-click the mailbox account in the console, and then click Properties.
4.Click the Security tab.
5.Click Advanced.
6.Make sure that the check box for "Include inheritable permissions from this object's parent" is selected.
Ref:
http://technet.microsoft.com/en-us/library/dd439375(v=exchg.80).aspx
Also check the Virtual directory authentication
Microsoft-Server-ActiveSync
•Basic authentication
•SSL required
•Requires 128-bit encryption
Ref:
http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
Check the IIS log if you are able to find any error message on it
Exchange Queries

Error reported after Exchange 2013 Setup (initialize-ExchangeUniversalGroups)

My Exchange 2013 setup reported the error below. Just wondering if someone has experienced this and how easy it was to fix.
Error:
The following error was generated when "$error.Clear();
initialize-ExchangeUniversalGroups -DomainController $RoleDomainController -ActiveDirectorySplitPermissions $RoleActiveDirectorySplitPermissions
" was run: "Microsoft.Exchange.Management.Tasks.InvalidWKObjectException: The well-known object entry B:32:C262A929D691B74A9E068728F8F842EA:CN=Organization Management\0ADEL:81ee6b49-29e5-41ff-93d4-30c547de15b1,CN=Deleted Objects,DC=ad,DC=mydomain,DC=co
on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=ad,DC=mydomain,DC=co points to an invalid DN or a deleted object. Remove the entry, and then rerun the task.
at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
at Microsoft.Exchange.Configuration.Tasks.Task.WriteError(Exception exception, ErrorCategory category, Object target)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateGroup(ADOrganizationalUnit usgContainer, String groupName, Int32 groupId, Guid wkGuid, String groupDescription, GroupTypeFlags groupType, Boolean createAsRoleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateRoleGroup(ADOrganizationalUnit usgContainer, RoleGroupDefinition roleGroup)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.CreateAndValidateRoleGroups(ADOrganizationalUnit usgContainer, RoleGroupCollection roleGroups)
at Microsoft.Exchange.Management.Tasks.InitializeExchangeUniversalGroups.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Roger

Thanks for replying.
My domain is actually routable (I just renamed it thinking that perhaps its more secure to withhold the info).
I had previously installed Es2013 and had to delete the VM. So this is a re-install on the Active Directory. I'm wondering if there isn't something in the "deleted folder" that is causing hassles.
Roger

Which exchange 2013 setup file should I use ?

I am seeing exchange 2013 RTM setup file for download from microsoft, as well as exchange 2013 CU3 setup file. This is my first exchange 2013 box. which file should I use to install exchange ?
Anand_N

Hi,
For new installs you should usethe most current build, CU3: http://www.microsoft.com/en-us/download/details.aspx?id=41175
Cumulative Update builds are full Exchange server installers so there is no need to install RTM version and then apply CU.
Robert Mandziarz | IT Administrator:
CodeTwo
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.

Problem with Fresh/New Exchange 2013 - Exchange Account, Unable to verify account information

hi!
For a client, i just setup AD (windows 2012 R2), and Exchange 2013 installed on Windows 2012 R2.
The AD is brand new, the exchange is installed correctly, i setup send connectors, and i could send and receive emails succefully.
But, when i want to use mobile devices like iphone, i receive the error as in title.
I've not changed anything from the default policies of Mobile devices policy...
What could be the problem?
how can i fix?
Regards!
Lasandro Lopez

Hi Lasandro,
Agree with Dare, Exchange 2013 is not supported to run on Windows Server 2012 R2.
Exchange 2013 SP1 will add Windows Server 2012 R2 as a supported operating system for Exchange Server 2013 with SP1.
For more information, here is a blog for your reference.
Exchange Server 2013 Service Pack 1 Coming in Early 2014
http://blogs.technet.com/b/exchange/archive/2013/11/20/exchange-server-2013-service-pack-1-coming-in-early-2014.aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

EXCHANGE 2013 - setup.exe schema prep error

Trying to install exchange 2013 sp1 (downloaded from here:
http://www.microsoft.com/en-us/download/details.aspx?id=41994).
on 2012 r2 server.
After I run (with domain admins affcourse): Setup.exe /prepareschema /IAcceptExchangeserverlicenseterms
I recieve an error that user is not a member of schema admins and enterprise admins but I have double checked that account is in those groups. So, what am I missing there?
bostjanc

Hi Joe,
since we can make sure the user account is a member of Domain Admins, Schema Admins and Enterprise Admins groups, please also add the user to be a member of Organization Management group, don’t
just add the Domain admin to the Organization Management group, please directly add the account to the member of Organization Management group.
Then check if the account inherit permission form its parent level. To do this, please refer to the following steps:
Open ADUC, select “View->Advanced Features”;
Navigate to the user account you used, check its
Properties;
On the
Security tab, click Advanced, please make sure the inherited permission is enabled in the lower left corner. If not, please click “Enable Inheritance” to enable it.
Then use this account to login the server;
Right click “Command Prompt” and choose “Run as administrator”, then navigate to the setup file location, try to prepare schema by command:
Setup.exe /prepareschema /IAcceptExchangeserverlicenseterms
6. If issue persists, please try Mavis’s suggestion to create a new user account, use above steps add the sufficient permission, then check the issue again.
Meanwhile, what do you mean by “single label domain”? Do we have a single domain and prepared DC/GC, or have parent/child domain configuration.
Regards, Eric Zou

Unable to access ECP on a new Exchange 2013 Install

I have a standalone exchange 2010 server (setup with all roles) and yesterday went ahead to setup an Exchange 2013 Server. Installed both CAS and mailbox roles for Exchange 2013 but after the install, I am unable to access the Exchange Admin Center.
If i try to access to https://EXCHANGE 2013 FQDN\ecp , after inserting my login information, it asks for the login information again and redirects to webmail. I have read all posts of users experiencing similar issues and tried all possible measures.
As the 2013 coexists with Exchange 2010 and mailboxes still reside on 2010, I have tried the URL
https://EXCHANGE 2013 FQDN/ecp?ExchClientVer=15 but got the same result.
Also, the CAS is installed on the server and i see the ECP virtual directory and URL.
please see below the output for Get-ExchangeServer | FL and Get-EcpVirtualDirectory | FL
[PS] C:\Windows\system32>Get-ExchangeServer | FL
RunspaceId : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
Name : NYC-HQXCH-02
DataPath : C:\Program Files\Microsoft\Exchange Server\V14\Mailbox
Domain : company.loc
Edition : Enterprise
ExchangeLegacyDN : /o=company/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=NYC-HQXCH-02
ExchangeLegacyServerRole : 0
Fqdn : NYC-HQXCH-02.company.loc
CustomerFeedbackEnabled :
InternetWebProxy :
IsHubTransportServer : True
IsClientAccessServer : True
IsExchange2007OrLater : True
IsEdgeServer : False
IsMailboxServer : True
IsE14OrLater : True
IsE15OrLater : False
IsProvisionedServer : False
IsUnifiedMessagingServer : False
IsFrontendTransportServer : False
NetworkAddress : {ncacn_vns_spp:NYC-HQXCH-02, netbios:NYC-HQXCH-02, ncacn_np:NYC-HQXCH-02,
ncacn_spx:NYC-HQXCH-02, ncacn_ip_tcp:NYC-HQXCH-02.company.loc, ncalrpc:NYC-HQXCH-02}
OrganizationalUnit : company.loc/NYC-HQXCH-02
AdminDisplayVersion : Version 14.3 (Build 123.4)
Site : company.loc/Configuration/Sites/NewYorkHQ
ServerRole : Mailbox, ClientAccess, HubTransport
ErrorReportingEnabled :
StaticDomainControllers : {}
StaticGlobalCatalogs : {}
StaticConfigDomainController :
StaticExcludedDomainControllers : {}
MonitoringGroup :
WorkloadManagementPolicy :
CurrentDomainControllers : {}
CurrentGlobalCatalogs : {}
CurrentConfigDomainController :
ProductID : 02064-110-8022196-75756
IsExchangeTrialEdition : False
IsExpiredExchangeTrialEdition : False
MailboxProvisioningAttributes :
RemainingTrialPeriod : 00:00:00
Identity : NYC-HQXCH-02
IsValid : True
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=NYC-HQXCH-02,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
Guid : 1745c93f-419d-402c-b832-708958fc502c
ObjectCategory : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 4/2/2014 1:50:56 PM
WhenCreated : 8/25/2013 11:12:43 AM
WhenChangedUTC : 4/2/2014 6:50:56 PM
WhenCreatedUTC : 8/25/2013 4:12:43 PM
OrganizationId :
OriginatingServer : SVR-DC-01.company.loc
ObjectState : Unchanged
RunspaceId : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
Name : NYC-HQARC-02
DataPath : C:\Program Files\Microsoft\Exchange Server\V14\Mailbox
Domain : company.loc
Edition : Enterprise
ExchangeLegacyDN : /o=company/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=NYC-HQARC-02
ExchangeLegacyServerRole : 0
Fqdn : NYC-HQARC-02.company.loc
CustomerFeedbackEnabled :
InternetWebProxy :
IsHubTransportServer : False
IsClientAccessServer : False
IsExchange2007OrLater : True
IsEdgeServer : False
IsMailboxServer : True
IsE14OrLater : True
IsE15OrLater : False
IsProvisionedServer : False
IsUnifiedMessagingServer : False
IsFrontendTransportServer : False
NetworkAddress : {ncacn_vns_spp:NYC-HQARC-02, netbios:NYC-HQARC-02, ncacn_np:NYC-HQARC-02,
ncacn_spx:NYC-HQARC-02, ncacn_ip_tcp:NYC-HQARC-02.company.loc, ncalrpc:NYC-HQARC-02}
OrganizationalUnit : company.loc/NYC-HQARC-02
AdminDisplayVersion : Version 14.3 (Build 123.4)
Site : company.loc/Configuration/Sites/NewYorkHQ
ServerRole : Mailbox
ErrorReportingEnabled :
StaticDomainControllers : {}
StaticGlobalCatalogs : {}
StaticConfigDomainController :
StaticExcludedDomainControllers : {}
MonitoringGroup :
WorkloadManagementPolicy :
CurrentDomainControllers : {}
CurrentGlobalCatalogs : {}
CurrentConfigDomainController :
ProductID : 02064-110-8022196-75187
IsExchangeTrialEdition : False
IsExpiredExchangeTrialEdition : False
MailboxProvisioningAttributes :
RemainingTrialPeriod : 00:00:00
Identity : NYC-HQARC-02
IsValid : True
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=NYC-HQARC-02,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
Guid : c07f34f4-92f1-49f0-a412-d7094eaaba3b
ObjectCategory : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 4/2/2014 1:50:57 PM
WhenCreated : 9/9/2013 3:27:16 PM
WhenChangedUTC : 4/2/2014 6:50:57 PM
WhenCreatedUTC : 9/9/2013 8:27:16 PM
OrganizationId :
OriginatingServer : SVR-DC-01.company.loc
ObjectState : Unchanged
RunspaceId : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
Name : SVR-EXCH-01
DataPath : C:\Program Files\Microsoft\Exchange Server\V15\Mailbox
Domain : company.loc
Edition : StandardEvaluation
ExchangeLegacyDN : /o=company/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=SVR-EXCH-01
ExchangeLegacyServerRole : 0
Fqdn : SVR-EXCH-01.company.loc
CustomerFeedbackEnabled :
InternetWebProxy :
IsHubTransportServer : True
IsClientAccessServer : True
IsExchange2007OrLater : True
IsEdgeServer : False
IsMailboxServer : True
IsE14OrLater : True
IsE15OrLater : True
IsProvisionedServer : False
IsUnifiedMessagingServer : True
IsFrontendTransportServer : True
NetworkAddress : {ncacn_vns_spp:SVR-EXCH-01, netbios:SVR-EXCH-01, ncacn_np:SVR-EXCH-01,
ncacn_spx:SVR-EXCH-01, ncacn_ip_tcp:SVR-EXCH-01.company.loc, ncalrpc:SVR-EXCH-01}
OrganizationalUnit : company.loc/SVR-EXCH-01
AdminDisplayVersion : Version 15.0 (Build 847.32)
Site : company.loc/Configuration/Sites/Chicago-COLO1
ServerRole : Mailbox, ClientAccess
ErrorReportingEnabled :
StaticDomainControllers : {}
StaticGlobalCatalogs : {}
StaticConfigDomainController :
StaticExcludedDomainControllers : {}
MonitoringGroup :
WorkloadManagementPolicy : DefaultWorkloadManagementPolicy_15.0.825.0
CurrentDomainControllers : {}
CurrentGlobalCatalogs : {}
CurrentConfigDomainController :
ProductID :
IsExchangeTrialEdition : True
IsExpiredExchangeTrialEdition : False
MailboxProvisioningAttributes :
RemainingTrialPeriod : 179.06:13:25.2449639
Identity : SVR-EXCH-01
IsValid : True
ExchangeVersion : 0.1 (8.0.535.0)
DistinguishedName : CN=SVR-EXCH-01,CN=Servers,CN=Exchange Administrative Group
(FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
Guid : 91eb6d6b-bfd0-4ce0-80ce-67585e7cbeae
ObjectCategory : company.loc/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass : {top, server, msExchExchangeServer}
WhenChanged : 5/13/2014 6:54:13 PM
WhenCreated : 5/13/2014 6:41:08 PM
WhenChangedUTC : 5/13/2014 11:54:13 PM
WhenCreatedUTC : 5/13/2014 11:41:08 PM
OrganizationId :
OriginatingServer : SVR-DC-01.company.loc
ObjectState : Unchanged
[PS] C:\Windows\system32>Get-EcpVirtualDirectory | FL
RunspaceId : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
AdminEnabled : True
OwaOptionsEnabled : True
Name : ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Ntlm, WindowsIntegrated}
MetabasePath : IIS://NYC-HQXCH-02.company.loc/W3SVC/1/ROOT/ecp
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
DefaultDomain : company.loc
GzipLevel : High
WebSite : Default Web Site
DisplayName : ecp
Path : C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\ecp
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 14.3 (Build 123.4)
Server : NYC-HQXCH-02
InternalUrl : https://webmail.companytravel.com/ecp
ExternalUrl :
ExternalAuthenticationMethods : {Fba}
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=ecp (Default Web
Site),CN=HTTP,CN=Protocols,CN=NYC-HQXCH-02,CN=Servers,CN=Exchange Administrative
Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=company,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
Identity : NYC-HQXCH-02\ecp (Default Web Site)
Guid : 0963f097-ff86-4d8f-a98a-8be409068eae
ObjectCategory : company.loc/Configuration/Schema/ms-Exch-ECP-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchECPVirtualDirectory}
WhenChanged : 4/2/2014 1:50:57 PM
WhenCreated : 8/30/2013 1:06:50 PM
WhenChangedUTC : 4/2/2014 6:50:57 PM
WhenCreatedUTC : 8/30/2013 6:06:50 PM
OrganizationId :
OriginatingServer : SVR-DC-01.company.loc
IsValid : True
ObjectState : Changed
RunspaceId : bdd191f7-2d42-4930-88b6-0b61f0a4e95d
AdminEnabled : True
OwaOptionsEnabled : True
Name : ecp (Default Web Site)
InternalAuthenticationMethods : {Basic, Fba}
MetabasePath : IIS://SVR-EXCH-01.company.loc/W3SVC/1/ROOT/ecp
BasicAuthentication : True
WindowsAuthentication : False
DigestAuthentication : False
FormsAuthentication : True
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
DefaultDomain :
GzipLevel : Low
WebSite : Default Web Site
DisplayName : ecp
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\ecp
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 847.32)
Server : SVR-EXCH-01
InternalUrl : https://svr-exch-01.company.loc/ecp
ExternalUrl :
ExternalAuthenticationMethods : {Fba}
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
DistinguishedName : CN=ecp (Default Web Site),CN=HTTP,CN=Protocols,CN=SVR-EXCH-01,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=company,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=company,DC=loc
Identity : SVR-EXCH-01\ecp (Default Web Site)
Guid : 052fdd05-42f4-471b-8759-525e93d6b97d
ObjectCategory : company.loc/Configuration/Schema/ms-Exch-ECP-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchECPVirtualDirectory}
WhenChanged : 5/13/2014 6:52:11 PM
WhenCreated : 5/13/2014 6:52:11 PM
WhenChangedUTC : 5/13/2014 11:52:11 PM
WhenCreatedUTC : 5/13/2014 11:52:11 PM
OrganizationId :
OriginatingServer : SVR-DC-01.company.loc
IsValid : True
ObjectState : Changed

Ok. Went ahead and tried https://<EX2013_FQDN/ecp/?ExchClientVer=15
Still took me to the webmail.
I also tried creating a user on 2013 mailbox database. gave all permissions. Still no luck.

Outlook prompting for password with new Exchange 2013

I have Exchange 2007 and 2013. I want to migrate to 2013 but I'm having issues in the testing phase. I have a test account that I moved the mailbox to the new server. I have a test PC with a modified hosts file that points to the new Exch
2013 server IP address.
When I log in with this test user, Outlook appears to connect and download the mailbox. However a Windows Security dialog box pops up saying Microsoft Outlook Connecting to [email protected] and it has a username and password field. No matter what
is entered here, it is NOT accepted, nor if forcefully entering the wrong information is the account locked out.
I can click cancel here and it proceeds to update the inbox and then says All folders are up to date. But at the bottom in Outlook 2013 it says Need password and Outlook's icon in the taskbar has a yellow triangle on it. I can send myself a test
email and I get it (I personally am on the 2007 server), but after it sends Outlook 2013 prompts again for the password, and since it does not accept anything, I have to click cancel.
I have done ALL the windows updates available on this test PC. Exchange 2013 is on CU6 which is the latest at the time of this writing.
Another thing is in the Lync 2013 client it says "Exchange needs your credentials". No matter what is entered here, it will not make this message go away unless you click the X on this warning bar. Lync itself appears to work regardless.
Any ideas?
I just changed the ExternalClientAuthenticationMethod from Ntlm to Negotiage. Now the Outlook prompt does accept the domain password, but I don't want anyone to have to enter any type of credentials just to get on. Note, this test is on the same
LAN as the servers, so I haven't even tackled an external test yet, though last time I tried it was the same results.

Ok besides LYNC 2013 asking for exchange credentials, I cannot get Outlook to work externally.
Externally to the NEW Exch2013 server, we are trying something different this time around. Instead of poking port 443 straight to the Exchange server from the outside world, we are trying what we did with LYNC. We are poking port 443 to an IIS
AAR reverse proxy to it's DMZ interface. It has another nic on DMZ 2 which allows port 443 to the Exchange 2013 server.
So I can use this with no problem for OWA if using an account on the new 2013 Exchange server. But if using an account on the old Exchange server, after I click sign in I get "The webpage at https://legacy.domain.com/owa/auth/owaauth.dll might
be temporarily down or it may have moved permanently to a new web address. ERR_RESPONSE_HEADERS_TRUNCATED.
Then of course Outlook Anywhere does not work. After I put in my password it sits there trying to connect with nothing.
Here is part of the IIS log on the AAR server.
#Software: Microsoft Internet Information Services 7.5
#Version: 1.0
#Date: 2014-10-24 20:00:02
#Fields: date time s-ip cs-method cs-uri-stem cs-uri-query s-port cs-username c-ip cs(User-Agent) sc-status sc-substatus sc-win32-status time-taken
2014-10-24 20:00:02 192.168.1.13 OPTIONS /Microsoft-Server-ActiveSync User=exchange2007user&DeviceId=BAEEF5AE6A1CE1C61A2E62E992691FE2&DeviceType=WindowsMail&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=6301e6ce-7827-42cd-91a4-7eaa47ac659c 443 - 192.168.50.240 WindowsMail/17.5.9600.20605 500 0 0 19390
2014-10-24 20:00:02 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=36d2360b-79c5-4ca0-a250-08b892cd5b70 443 - 192.168.50.240 WindowsMail/17.5.9600.20605 401 0 0 0
2014-10-24 20:00:08 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6002&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=7615e512-4e58-424b-8ce1-654ba86bfe2e 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:00:08 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6002 443 - 192.168.50.240 MSRPC 404 13 0 0
2014-10-24 20:00:08 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6002&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=c3f94f7d-b408-4ff9-9de0-3e4577829b97 443 - 192.168.50.240 MSRPC 401 0 0 46
2014-10-24 20:00:22 192.168.1.13 POST /Microsoft-Server-ActiveSync eQAJBBC67vWuahzhxhouYumSaR/iBK6gyiwLV2luZG93c01haWw=&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=0b1ef554-5b08-4e0a-a9bd-294601364f4a 443 - 192.168.50.240 WindowsMail/17.5.9600.20605 500 0 0 19047
2014-10-24 20:00:22 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=b1fa8dde-9c16-40b9-9932-f49e7dc971c4 443 - 192.168.50.240 WindowsMail/17.5.9600.20605 401 0 0 0
2014-10-24 20:00:41 192.168.1.13 OPTIONS /Microsoft-Server-ActiveSync User=exchange2007user&DeviceId=BAEEF5AE6A1CE1C61A2E62E992691FE2&DeviceType=WindowsMail&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=8b94ec84-08dc-43e3-aeae-d00b1e4c9837 443 - 192.168.50.240 WindowsMail/17.5.9600.20605 500 0 0 19047
2014-10-24 20:00:41 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=1412decf-d570-440a-9ac4-8a6347b18bbd 443 - 192.168.50.240 WindowsMail/17.5.9600.20605 401 0 0 0
2014-10-24 20:01:00 192.168.1.13 POST /Microsoft-Server-ActiveSync eQAJBBC67vWuahzhxhouYumSaR/iBK6gyiwLV2luZG93c01haWw=&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=5d1754fc-cc71-43fe-876d-2eff7ba1efbf 443 - 192.168.50.240 WindowsMail/17.5.9600.20605 500 0 0 19032
2014-10-24 20:01:00 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=a8609c9a-6fc3-43d1-b961-74e95dc53bf1 443 - 192.168.50.240 WindowsMail/17.5.9600.20605 401 0 0 0
2014-10-24 20:01:09 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6002&X-ARR-LOG-ID=cdcb7486-bdad-4f66-a300-3d1262be606a 443 - 192.168.50.240 MSRPC 200 0 0 60138
2014-10-24 20:01:11 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6001&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=3ac5ff66-5ad1-495d-9293-5bc3540b481c 443 - 192.168.50.240 MSRPC 401 0 0 46
2014-10-24 20:01:11 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6001 443 - 192.168.50.240 MSRPC 404 13 0 0
2014-10-24 20:01:11 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6001&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=b8b39056-6c89-48ec-98d9-0456aad716f1 443 - 192.168.50.240 MSRPC 401 0 0 78
2014-10-24 20:02:11 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6001&X-ARR-LOG-ID=44351254-c944-45ab-9b6f-e020358b993b 443 - 192.168.50.240 MSRPC 200 0 0 60184
2014-10-24 20:02:11 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll MAIL:6002&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=20e05c35-5b55-461f-9b9e-7e85b2266269 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:02:11 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll MAIL:6002 443 - 192.168.50.240 MSRPC 404 13 0 15
2014-10-24 20:02:11 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll MAIL:6002&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=079dc1e7-6edf-43d9-8d92-67229c259c93 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:03:11 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll MAIL:6002&X-ARR-LOG-ID=9cef3d08-4052-45f5-8806-3a6729818138 443 - 192.168.50.240 MSRPC 200 0 0 60169
2014-10-24 20:03:13 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6002&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=4bdb9a31-c8bc-4174-9958-4daaea796edb 443 - 192.168.50.240 MSRPC 401 0 0 46
2014-10-24 20:03:13 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6002 443 - 192.168.50.240 MSRPC 404 13 0 0
2014-10-24 20:03:13 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6002&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=d1489811-2925-458f-910d-702746329d0c 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:04:13 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6002&X-ARR-LOG-ID=545f6dff-9eff-4353-939d-20b3caf50d3f 443 - 192.168.50.240 MSRPC 200 0 0 60169
2014-10-24 20:04:13 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll DC1.domain.com:6004&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=86b53049-82f2-44b8-9135-bb54d02fbaae 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:04:13 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll DC1.domain.com:6004 443 - 192.168.50.240 MSRPC 404 13 0 15
2014-10-24 20:04:13 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll DC1.domain.com:6004&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=1a4eefbd-de59-4fac-b7de-8df5fb2e323b 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:04:13 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll DC1.domain.com:6004&X-ARR-LOG-ID=83dac450-4479-40d4-8cb9-e82e36085dbe 443 - 192.168.50.240 MSRPC 404 0 0 31
2014-10-24 20:04:15 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll MAIL:6001&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=b3fd8e85-122e-47b8-85e8-cfbc1281aa1d 443 - 192.168.50.240 MSRPC 401 0 0 62
2014-10-24 20:04:15 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll MAIL:6001 443 - 192.168.50.240 MSRPC 404 13 0 0
2014-10-24 20:04:15 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll MAIL:6001&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=eaee2bf9-cc0e-4805-b715-befb335ed25c 443 - 192.168.50.240 MSRPC 401 0 0 46
2014-10-24 20:05:15 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll MAIL:6001&X-ARR-LOG-ID=535cdb59-c23f-44ae-ada8-9f07bca29f92 443 - 192.168.50.240 MSRPC 200 0 0 60169
2014-10-24 20:05:15 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6004&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=f2d73aad-ba0e-413d-bff0-713bc830f028 443 - 192.168.50.240 MSRPC 401 0 0 46
2014-10-24 20:05:15 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6004 443 - 192.168.50.240 MSRPC 404 13 0 15
2014-10-24 20:05:15 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6004&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=93219c6c-bbab-49ae-b12a-4c8f7939368c 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:05:46 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=a9d7e8b9-6f0e-4036-b6ff-298fb483dffc 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 62
2014-10-24 20:06:07 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=a79a1894-554c-496f-98b5-8935644f286b 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 46
2014-10-24 20:06:07 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=6dab43de-a34f-426f-ba56-a7b589c8a5c9 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 15
2014-10-24 20:06:07 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=d7323b0f-5af4-4741-88ac-07e51675feaf 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 15
2014-10-24 20:06:07 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=d27bd9f8-2292-4710-b1ce-1f613733af8b 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 0
2014-10-24 20:06:07 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=c9a1d015-6ec5-469b-b6f0-1e2532b36b54 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 62
2014-10-24 20:06:16 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6004&X-ARR-LOG-ID=29d563b7-b6b9-4600-8344-5afd6af2e1d7 443 - 192.168.50.240 MSRPC 200 0 0 60184
2014-10-24 20:07:36 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=2af97edd-0e95-41d9-b55f-84f0b98d9a8d 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 46
2014-10-24 20:07:36 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-LOG-ID=4524480e-1bca-4e48-b807-ba39a1c5c934 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 200 0 0 468
2014-10-24 20:07:37 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll MAIL:6004&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=7d07ec9d-7d0b-4d2a-a742-7c3552b267f9 443 - 192.168.50.240 MSRPC 401 0 0 78
2014-10-24 20:07:37 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll MAIL:6004 443 - 192.168.50.240 MSRPC 404 13 0 0
2014-10-24 20:07:37 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll MAIL:6004&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=804dc16d-37a9-44a1-91fc-462336f7ff69 443 - 192.168.50.240 MSRPC 401 0 0 46
2014-10-24 20:08:38 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll MAIL:6004&X-ARR-LOG-ID=95a61f86-fdc2-4868-ae7a-25505f4c131c 443 - 192.168.50.240 MSRPC 200 0 0 60138
2014-10-24 20:08:40 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6001&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=e7007c02-bc0a-4b04-906e-29c653796099 443 - 192.168.50.240 MSRPC 401 0 0 46
2014-10-24 20:08:40 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6001 443 - 192.168.50.240 MSRPC 404 13 0 0
2014-10-24 20:08:40 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6001&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=2495013e-d003-4dcd-8dc4-b5756acf0618 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:08:46 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=fc7f2ec4-3af1-4059-997e-fd18680c6f94 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 46
2014-10-24 20:08:46 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-LOG-ID=4f75729e-bf92-499c-8dc2-832fddc27582 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 200 0 0 46
2014-10-24 20:08:46 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6002&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=327a2992-2b43-41ff-9ac4-a9960daba60d 443 - 192.168.50.240 MSRPC 401 0 0 31
2014-10-24 20:08:46 192.168.1.13 RPC_IN_DATA /rpc/rpcproxy.dll mail.domain.com:6002 443 - 192.168.50.240 MSRPC 404 13 0 0
2014-10-24 20:08:46 192.168.1.13 RPC_OUT_DATA /rpc/rpcproxy.dll mail.domain.com:6002&X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=784171c0-def0-4369-a9ad-374a25a21801 443 - 192.168.50.240 MSRPC 401 0 0 46
2014-10-24 20:09:10 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=2399c7d5-50e2-4c0f-85ed-ffeb92f411a8 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 31
2014-10-24 20:09:10 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=0156ccf0-043c-4c45-83db-f62cde770079 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 0
2014-10-24 20:09:10 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=40934ba2-41f8-435f-b62e-ababb51e00e2 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 31
2014-10-24 20:09:10 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=049938a4-cc8a-4476-b123-2d2a2dbcbcf7 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 0
2014-10-24 20:09:10 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=232d57a3-e1e3-43eb-8f04-ffc8f57c9359 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 0
2014-10-24 20:09:10 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-CACHE-HIT=0&X-ARR-LOG-ID=186a6668-8ce2-415b-8b1c-a2a2cb246617 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 401 0 0 46
2014-10-24 20:09:10 192.168.1.13 POST /autodiscover/autodiscover.xml X-ARR-LOG-ID=a5697f0e-972e-4e2f-8149-667cc7c4cee5 443 - 192.168.50.240 Microsoft+Office/15.0+(Windows+NT+6.2;+Microsoft+Outlook+15.0.4659;+Pro) 200 0 0 31

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

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

Exchange 2013 setup

Greetings
Currently i am using Exchange 2007 setup (xyz.com) and it is not published to the internet i.e. only the Domain joined users have access to it and mx records are not hosted for xyz.com
And have hosted solution (abc.com)
Now, I am planning to upgrade the Exchange 2007 to Exchange 2013 infra. But here my requirement is to use abc.com as the email address domain.
My plan is to migrate and add abc.com in accepted domain. Please suggest if this can be achieved by doing so and if yes, what other changes i need to plan as i want to have the same email address domain (abc.com) having the virtual directories by the same
name (mail.abc.com)
Please provide yours inputs.
Thanks
K2

Hi,
Thank you for your question.
By my understanding, you want to use Exchange 2013 with domain abc.com to replace domain xyz, right? If I misunderstand, please be free to let me know.
If that, we could refer to the following links to migrate Exchange 2007 to Exchange 2013 by crossing domains:
https://social.technet.microsoft.com/Forums/exchange/en-US/35828bef-3eaa-4540-b2ef-0dc1da0d77ca/cross-forest-migration-from-exchange-2007-to-exchange-2013?forum=exchangesvrgeneral
https://social.technet.microsoft.com/Forums/office/en-US/ccfaf77e-ae0f-47ac-94c4-c122df3efdf0/exchange-2007-to-2013-migrationcoexistance?forum=exchangesvrgeneral
But we suggest you install Exchange 2010 in abc.com domain, then we perform cross domain migration from Exchange 2007 to Exchange 2010, then migrate to Exchange 2013.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
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

SSL for Exchange 2013 with ARR

Hi,
Need advice on the number of SSL i would need to purchase.
I know that I require to have a SSL with example: mail.domain.com & autodiscover.domain.com
How about the ARR server that I will be setting up. Refer to http://social.technet.microsoft.com/Forums/exchange/en-US/fe8d1aae-a3c9-432a-a139-7b770cb07576/new-exchange-2013-setup-vmware?forum=exchangesvrdeploy
do i need to have a SSL cert for the ARR server?
Thanks in advance!

Hi,
Just like all above saying, we do not need to generate a new certificate for IIS ARR server. We can configure
all protocols (OWA, ECP, EWS etc) published with the mail.domain.com
namespace.
When install IIS, we can export the Exchange certificate (from a CAS) and import the certificate to the local machine certificate store on the IIS Reverse Proxy, together with any required root or intermediate certificates. For more information
about it, here is a detailed article we can refer to:
Reverse Proxy for Exchange Server 2013 using IIS ARR
http://blogs.technet.com/b/exchange/archive/2013/07/19/reverse-proxy-for-exchange-server-2013-using-iis-arr-part-1.aspx
Thanks,
Winnie Liang
TechNet Community Support

New exchange 2013 setup

Similar Messages

Maybe you are looking for