Dear Expert
I have a question, Can Exchange server support on vSphere NFS Datastore (Nutanix)? because user will buy hardware from Nutanix. Can you suggest the solution and support Microsoft reference ?
Support Information : http://www.reddit.com/r/microsoft/comments/1wrquj/virtualizing_ms_exchange_on_vsphere_in_vmdk/
Thank you
This one is driving me absolutely crazy, hours and hours spent on this with no luck. This is 2007/2013 env. The issue is, if I move a mailbox to 2007 then 2013 OWA is fine, then if I move the mailbox back to 2007 I can't access the mailbox via OWA when going through a 2013 CAS server. yes I've read the posts about permissions inheritance etc.. yes I've cranked up AD and OWA logging nothing.. yes I've imported the IIS logs into log parser and I'm seeing various errors mostly 302. Yes, I've ruled out 2007 servers, it's 2013. If I recreate the mailbox it works then when move back and forth from 2007 to 2013 problem re-appears. Yes, I have dumped AD attributes and compared them with working and non working mailbox can't find anything. Yes, I've rebooted servers. Yes this happens with multiple mailboxes.
In fact I have this example right now makes no sense. I have two 2013 servers, if I go through the 2013 servers CAS servers to access the mailbox using OWA that resides on the 2007 server, it works through one server and the other it doesn't with the above errors. I'd love to hear suggestions.. I'm at the end of my rope
I am migrating public folders to exchange 2013. half of them a named in hebrew.
The migration fails, the error is character related.
Is it possible at all to migrate hebrew named public folders?
Let me lay it all out. We are running an Exchange 2007 environment with 2-CAS, 2-HT's and 2-MBX's clustered. We started a migration to Exchange 2010 and after starting the migration it was decided that we would instead got to Exchange 2013. In Exchange 2010 we have 3-CAS, 2-HT's and 2-MBX's. We have moved our external connections over to Exchange 2010 and only have test mailboxes on 2010 and that's where we stopped.
We installed Exchange 2013 3-CAS, 2-MBX's. We are testing out 2013 installation. We can access 2013 Web App with the 2013 test accounts. I can access 2013 test mailbox with outlook 2010 by configuring outlook for rpc/https. I am not getting free/busy form 2007 or 2013 when logged into my 2013 test mailbox. My virtual directories are configured as the following:
Exchange 2007 - mail2007.domain.com\
Exchange 2010 - mail.domain.com\
Exchange 2013 - mail2013.domain.com\
Hello everyone,
I am migrating users from exchange 2010 to 2013, Users migration works perfectly and completes without any issue but after the user migration finishes I try to login to OWA but user goes to OWA exchange 2010 not 2013 as if the mailbox has not been migrated.
I have checked the HomeMDB attribute and I can see the new database on 2013 is located there. how to solve this? I have retransfered the user back to 2010 and 2013 but it didn't work.
I would appreciate your help.
Thanks
Mohammed JH
I did originally tried to migrate public folders from Exchange 2007, but I got stuck on the last step so I completely disabled the migration and deleted all public folders. I exported all the public folder information to a PST and then manually created
the public folders and copied the data in via Outlook. I as an administrator can see the public folders, but non administrative users cannot even see the root folder. Public folders don't even show up in the folder list. My exchange 2007 server
is no longer online and my users cannot see the Public folders in OWA or Outlook. I am sure this is a permissions issue, but I can't seem to find it. I have assigned a test user ownership root rights and restarted the information store service
and this still didn't fix it. As you can see below Default is Author. Any help would be appreicated.
Information:
[PS] C:\WINDOWS\system32>Get-PublicFolderClientPermission \
FolderName User AccessRights
---------- ---- ------------
IPM_SUBTREE Default {Author}
IPM_SUBTREE Anonymous {None}
IPM_SUBTREE Tech {Owner}
[PS] C:\WINDOWS\system32>Get-OrganizationConfig | fl *public*
DefaultPublicFolderAgeLimit :
DefaultPublicFolderIssueWarningQuota : Unlimited
DefaultPublicFolderProhibitPostQuota : Unlimited
DefaultPublicFolderMaxItemSize : Unlimited
DefaultPublicFolderDeletedItemRetention : 7.00:00:00
DefaultPublicFolderMovedItemRetention : 7.00:00:00
PublicFoldersLockedForMigration : False
PublicFolderMigrationComplete : True
PublicFoldersEnabled : Local
PublicComputersDetectionEnabled : False
RootPublicFolderMailbox : 6a6c1ace-ee8e-497e-9884-8b46dc1f0a09
RemotePublicFolderMailboxes : {}
[PS] C:\WINDOWS\system32>Get-Mailbox -PublicFolder | FL Name,ExchangeGuid
Name : PF-Hierarchy
ExchangeGuid : 6a6c1ace-ee8e-497e-9884-8b46dc1f0a09
Name : Public Folders
ExchangeGuid : 4bbbb1cf-c24e-4bb8-b056-bc610bedc390
Thanks,
Ryan
Hi Guys
I have two domains
example.com.au
example-it.com.au
and two wild card certificates
*.example.com.au
*.example-it.com.au
I've used import-certificate to import both of these onto a brand new exchange server 2013 and then changed my host file to point the FQDN at this server.
However, of the two domains only 1 seems to have a valid certificate..
How can I make sure both of them work?
Hey Have a weird one... So I was setting u exchange 2010 in a test environment to see how long all the patches would take to implement as well as see if there might be any gotchas... well all the patches were successfully installed (through SP3 rollup6) in about a days time but now every time I execute any command it completes successful but with the following exception, any ideas would be useful:
New contoso.int
Completed
Warning:
The cmdlet extension agent with the index 1 has thrown an exception in OnComplete(). The exception is: System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Data.Storage.MailboxSession' threw an exception. ---> System.TypeInitializationException:
The type initializer for 'Microsoft.Exchange.Data.Storage.ItemSchema' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Microsoft.Exchange.Data.Storage.CoreItemSchema' threw an exception. ---> System.TypeInitializationException:
The type initializer for 'Microsoft.Exchange.Data.Storage.InternalSchema' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Microsoft.Mapi.WellKnownNamedProperties' threw an exception. ---> System.AccessViolationException:
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at Microsoft.Mapi.WellKnownNamedProperties..cctor()
--- End of inner exception stack trace ---
at Microsoft.Mapi.WellKnownNamedProperties.Find(NamedProp property)
at Microsoft.Exchange.Data.Storage.GuidNamePropertyDefinition.InternalCreate(String displayName, Type propertyType, PropType mapiPropType, Guid propertyGuid, String propertyName, PropertyFlags flags, TypeCheckingFlag typeCheckingFlag, Boolean isCustom,
PropertyDefinitionConstraint[] constraints)
at Microsoft.Exchange.Data.Storage.InternalSchema.CreateGuidNameProperty(String displayName, Type propertyType, Guid propertyGuid, String propertyName)
at Microsoft.Exchange.Data.Storage.InternalSchema..cctor()
--- End of inner exception stack trace ---
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.ItemSchema..cctor()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.MailboxSession..cctor()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Data.Storage.MailboxSession.OpenAsSystemService(ExchangePrincipal mailboxOwner, CultureInfo cultureInfo, String clientInfoString)
at Microsoft.Exchange.ProvisioningAgent.MailboxLoggerFactory.XsoMailer.Log(AdminLogMessageData data, LogMessageDelegate logMessage)
at Microsoft.Exchange.ProvisioningAgent.AdminLogProvisioningHandler.OnComplete(Boolean succeeded, Exception e)
at Microsoft.Exchange.Provisioning.ProvisioningLayer.OnComplete(Task task, Boolean succeeded, Exception exception)
Exchange Management Shell command completed:
new-EmailAddressPolicy -Name 'contoso.int' -IncludedRecipients 'AllRecipients' -Priority 'Lowest' -EnabledEmailAddressTemplates 'SMTP:%m@conoso.int'
Dears,
I'm facing a issue with Exchange 2013 SP1 CU5 "15.00.0913.022" suddenly after 2 month of the migration from Exchange 2010 i get the "Unknown" status for Content Index status on any database hosted on two servers only
my new Exchange 2013 topology is : 3 CAS servers & DAG contains 6 Mailboxes servers and 4 lagged Mailboxes servers
The following is the errors and warnings logs on my effected mailboxes servers:
The indexing of mailbox database DB53 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedException: "Feeding was skipped for '3a5ec474-ea70-42b5-a123-d7ff7e5aadc3 (DB53)' due to the state 'Unknown', error code: 'Unknown'."
at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()
at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)
--- End of inner exception stack trace ---
at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)
at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)
The FastFeeder component received a connection exception from FAST. Error details: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request
at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)
at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.GetItems(Guid flowIdentifier, String outputName)
at SyncInvokeGetItems(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Event 169 (Search) of severity 'Error' occurred 14 more time(s) and was suppressed in the event log
-------------------------------------------------------------------------------------------------------------------------------------
An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.
Server stack trace:
at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Ceres.CoreServices.Admin.IAdminServiceManagementAgent.SystemInfo()
at Microsoft.Exchange.Search.Fast.NodeManagementClient.CheckForAllNodesHealthy(Boolean retry)
at Microsoft.Exchange.Search.Fast.IndexManager.<UpdateConfiguration>b__8()
at Microsoft.Exchange.Search.Fast.FastManagementClient.<>c__DisplayClass1.<PerformFastOperation>b__0()
at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[T](Func`1 function, String eventLogKey)
--- End of inner exception stack trace ---
------------------------------------------------------------------------------------------------------------------------------------
Exchange Server Information Store has encountered an error while executing a full-text index query ("string("ItemWarmUpSearch31febf7b418e44878df6e5623e37c828*", mode="and")"). Error information: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:
Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request
at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)
at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.ExecuteSearchFlow(String flowName, IEnumerable`1 inputData)
at SyncInvokeExecuteSearchFlow(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).
What i have tried to solve the issue with no luck is:
1- Reseed the effected Databases
2- Reset the index manually by stop the Search and Search Host Controller services and delete the index folder and start the services again in order to force it to rebuild the index
3- Restart the mailbox server that has the index issue
4- Create the AD group "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group as the following technet article http://support.microsoft.com/kb/2807668
Any Idea will be much appreciated.
Thanks,
Ayman Saleh
Ayman Saleh
Khemarin333@hotmail.com
Hello All,
I've been asked to plan, design and setup a small exchange server and I thought why not go for the latest one because two years down the line it will still be quite new. As I've not done any such deployment all alone before, I was scared and excited.
I started reading and after quite some basic reading thought to setup the lab first and see a demo. The lab itself has so many issues out of the box, I think shall I install Exch 2010 which seems to be much stable when comes out of the box. All the promises made by Exch 2013 seems to be a vague dream.
I simply don't understand even after following all the steps why EAC/ECP or sometimes EMS or sometimes the OWA doesn't work internally.
I setup a small lab in VMware Workstation, using 5 VM's - AD, 2 CAS, 2 MBX. All running Windows Server 2012 R2 & installed Exchange 2013 SP1. I later upgraded to CU5 as well to see if that fixes the virtual directories and other things. It didn't work as expected.
I can understand that configuring is a major part of exchange deployment but initial deployment should be robust not confusing. I found articles that after you prepare the exchange server with prerequisites, uninstall some Visual Basic c++ installer etc (KB I don't remember).
Is there anyone out there who has successfully installed Exchange 2013 SP1 on Windows Server 2012 R2?
TechNet articles only refer to Exchange 2013 deployment and upgrade.
1. Which is the stable & most suited Operating System - Windows Server 2008 R2 SP1 with fully patched updates or Windows Server 2012 R2 with fully patched updates?
2. Which is the best Active Directory Model - hosted on Win 2008 R2 SP1 with Forest & Domain Functional Level up to the latest available or Win 2012 R2 with Forest & Domain Functional Level up to the latest available?
3. For another New Separate Small Internal deployment of Exchange I was planning to use Virtual Servers (for 50-100 Users). Which is the best solution - Hyper V on Windows Server 2012 R2 or VM's running on ESXi? Which solutions offers more options in terms of HA, Disaster Recovery etc & easy administration.
4. Now I'm planning to reformat all my servers & install Windows Server 2008 R2. Does this at least works fine with Exchange 2013 SP1.
5. Which is more stable - Exchange 2013 or Exchange 2013 SP1 or Exchange 2013 SP1 CU5?
6. What are the port requirements in Exchange 2013 & how to configure windows firewall to work well instead of disabling it.
If any appropriate guidance in the form of URL/Video or blog or whitepaper or deployed solution steps is shared I would highly appreciate. Thanks in advance.
PS: This is an urgent requirement so quick replies will be highly appreciated.
Thanks
Young Blood
Fahad
Hi,
I renewed our Exchange certificate today with GoDaddy. They are pushing a new policy of NOT allowing internal domains in certificates.
Our previous UCC certificate covered the following address
webmail.domain.co.uk
autodiscover.domain.co.uk
exchange1.domain.local
This worked fine. When renewing today, I needed to drop 'exchange1.domain.local' from the UCC cert.
I thought I would create an internal certificate for Exchange1, authorised by my domain's CA, which I have done and disctributed to all clients using group policy.
My UCC renewal with GoDaddy therefore only had webmail.domain.co.uk and autodiscover.domain.co.uk. When this cert was issued, I added to IIS on Exchange1. I set the binding to https for this new certificate and tested by visiting webmail.domain.co.uk, which showed the new certificate.
However, shortly after, my internal clients then called complaining about certificate warnings in Outlook. I see that Outlook is connecting to exchange1.domain.local but being presented with the 'web' certificate I just renewed with GoDaddy. I understand Outlook communicates over HTTP/S now so how do I overcome the problem I have and secure my internal server name (exchange1.domain.local) without using this name in the GoDaddy UCC cert?
Many thanks
Hello ,
what is the BEST scenario ( fastest , most efficient , most secure in terms of data loss ) , to migrate from exchange 2007 ( one server , all exchange roles installed on this server , 1200 mailbox ) , to exchange 2013 ?
knowing my environment needs to be connected to their mailboxes , 24/7 !
it's very frustrating .
and i have no clue even if this is the right place to post about this , if not please refer me as to where to post .
Also , All my domain controllers are 2008 .
Greetings, community!)
I try to Upgrade our Exchange 2007 to Exchange 2013SP1 and have a little troubles:
On the step where we migrate test users from Exchange 2007 to Exchange 2013 MailboxDatabases, when users open Outlook 2013/2010/2007 they asked for password. But if they cancel this window, mailflow work fine.
But they have troubles with Publick Folders (they are still on EX2007) and other users calendar access.
I set all internal outlookanywhere auth methods to NTLM, and check CAS IIS settings with that page: http://technet.microsoft.com/en-us/library/gg247612(v=exchg.150).aspx
If I disable Outlook cached mode, Outlooks works fine.
What could be?
Welcome to Microsoft Exchange Server 2013 Cumulative Update 5 Unattended Setup
Languages
Mailbox role: Transport service
Client Access role: Front End Transport service
Mailbox role: Client Access service
Mailbox role: Unified Messaging service
Mailbox role: Mailbox service
Management tools
Client Access role: Client Access Front End service
Performing Microsoft Exchange Server Prerequisite Check
Configuring Prerequisites
COMPLETED
Prerequisite Analysis
COMPLETED
Configuring Microsoft Exchange Server
Language Files
COMPLETED
Restoring Services
COMPLETED
Language Configuration
COMPLETED
Mailbox role: Transport service
COMPLETED
Client Access role: Front End Transport service
COMPLETED
Mailbox role: Client Access service
FAILED
The following error was generated when "$error.Clear();
Update-AutodiscoverVirtualDirectoryVersion -DomainController $RoleDomainController;
$BEVdirIdentity = $RoleNetBIOSName + "\Autodiscover (Exchange Back End)";
$be = get-AutodiscoverVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainControl
ler $RoleDomainController -ErrorAction SilentlyContinue;
if ($be -eq $null)
{
new-AutodiscoverVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomain
Controller -WSSecurityAuthentication:$true -BasicAuthentication:$false -WindowsAuthentication:$true;
}
else
{
$be | set-AutodiscoverVirtualDirectory -windowsAuthentication:$be.WindowsAuthentication -WSSecurityAuthentic
ation:$be.WSSecurityAuthentication -BasicAuthentication:$be.BasicAuthentication
}
. "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeAutodiscoverApp
Pool" -Version:"v4.0";
" was run: "Microsoft.Exchange.Data.Common.LocalizedException: The Autodiscover service couldn't be found in the
configuration file. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: serviceElement
--- End of inner exception stack trace ---
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.SystemConfigurationTasks.ExchangeServiceVDirHelper.EwsAutodiscMWA.EnableOrDisableWSS
ecurityEndpoint(Configuration configuration, Boolean enableEndpoint, TaskErrorLoggingDelegate errorHandler, Boolean isEW
S)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.EwsAutodiscMWA.OnSetManageWCFEndp
oints(Task task, EndpointProtocol protocol, Boolean enableWSSecurity, ExchangeVirtualDirectory adVirtualDirectory)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetAutodiscoverVirtualDirectory.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePip
elineIfFailed)".
The Exchange Server setup operation didn't complete. More details can be found in ExchangeSetup.log located in the
<SystemDrive>:\ExchangeSetupLogs folder.
Event 1002, MSEcxchangeSetup
Exchange Server component Mailbox role: Client Access service failed.
Error: Error:
The following error was generated when "$error.Clear();
Update-AutodiscoverVirtualDirectoryVersion -DomainController $RoleDomainController;
$BEVdirIdentity = $RoleNetBIOSName + "\Autodiscover (Exchange Back End)";
$be = get-AutodiscoverVirtualDirectory -ShowMailboxVirtualDirectories -Identity $BEVdirIdentity -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
if ($be -eq $null)
{
new-AutodiscoverVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController -WSSecurityAuthentication:$true -BasicAuthentication:$false -WindowsAuthentication:$true;
}
else
{
$be | set-AutodiscoverVirtualDirectory -windowsAuthentication:$be.WindowsAuthentication -WSSecurityAuthentication:$be.WSSecurityAuthentication -BasicAuthentication:$be.BasicAuthentication
}
. "$RoleInstallPath\Scripts\Update-AppPoolManagedFrameworkVersion.ps1" -AppPoolName:"MSExchangeAutodiscoverAppPool" -Version:"v4.0";
" was run: "Microsoft.Exchange.Data.Common.LocalizedException: The Autodiscover service couldn't be found in the configuration file. ---> System.ArgumentNullException: Value cannot be null.
Parameter name: serviceElement
--- End of inner exception stack trace ---
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.SystemConfigurationTasks.ExchangeServiceVDirHelper.EwsAutodiscMWA.EnableOrDisableWSSecurityEndpoint(Configuration configuration, Boolean enableEndpoint, TaskErrorLoggingDelegate errorHandler, Boolean isEWS)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExchangeServiceVDirHelper.EwsAutodiscMWA.OnSetManageWCFEndpoints(Task task, EndpointProtocol protocol, Boolean enableWSSecurity, ExchangeVirtualDirectory adVirtualDirectory)
at Microsoft.Exchange.Management.SystemConfigurationTasks.SetAutodiscoverVirtualDirectory.InternalProcessRecord()
at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Please help, thanks.
Here's my setup:
Mixed environment transitioning:
Exchange 2010 running on Server 2008 in a VM
Exchange 2013 running on Server 2012 in a VM
I have split dns so that autodiscover.domain.com points to my 2013 server internally and my 2010 server externally. When setting up new profiles in outlook internally, autodiscover seems to work fine. However, when I try moving the public autodiscover.domain.com
DNS record over to the 2013, things stop working (like auto profile setup).
I know that the 2013 server is reachable from the outside because mail.domain.com will to go owa and ecp without a problem. I can log in to both without an issue.
If I point public DNS back to my 2010 server, then all is well again with outlook anywhere and mobile connectivity.
I'm not really sure what needs to be tweaked for the 2013 server to be ready to take over the day to day communications so that I can decommission my 2010 server.
Here are the results of the connectivity analyzer:
The Microsoft Connectivity Analyzer is attempting to test Autodiscover for me. Testing Autodiscover failed. Additional Details Elapsed Time: 1774 ms. Test Steps Attempting each method of contacting the Autodiscover service. The Autodiscover service couldn't be contacted successfully by any method. Additional Details Elapsed Time: 1773 ms. Test Steps Attempting to test potential Autodiscover URL https://domain.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed. Additional Details Elapsed Time: 489 ms. Test Steps Attempting to resolve the host name domain.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: 98.129.228.152 Elapsed Time: 165 ms. Testing TCP port 443 on host domain.com to ensure it's listening and open. The port was opened successfully. Additional Details Elapsed Time: 97 ms. Testing the SSL certificate to make sure it's valid. The SSL certificate failed one or more certificate validation checks. Additional Details Elapsed Time: 225 ms. Test Steps The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server domain.com on port 443. The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=www.domain.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)09, OU=2150198723, O=www.domain.com, C=US, Issuer: CN=Equifax Secure Global eBusiness CA-1, O=Equifax Secure Inc., C=US. Elapsed Time: 170 ms. Validating the certificate name. Certificate name validation failed. Tell me more about this issue and how to resolve it Additional Details Host name domain.com doesn't match any name found on the server certificate CN=www.domain.com, OU=Domain Control Validated - RapidSSL(R), OU=See www.rapidssl.com/resources/cps (c)09, OU=2150198723, O=www.domain.com, C=US. Elapsed Time: 1 ms. Attempting to test potential Autodiscover URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml Testing of this potential Autodiscover URL failed. Additional Details Elapsed Time: 1009 ms. Test Steps Attempting to resolve the host name autodiscover.domain.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: x.x.x.x Elapsed Time: 70 ms. Testing TCP port 443 on host autodiscover.domain.com to ensure it's listening and open. The port was opened successfully. Additional Details Elapsed Time: 189 ms. Testing the SSL certificate to make sure it's valid. The certificate passed all validation requirements. Additional Details Elapsed Time: 300 ms. Test Steps The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.domain.com on port 443. The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate. Additional Details Remote Certificate Subject: CN=mail.domain.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated, Issuer: CN=PositiveSSL CA 2, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB. Elapsed Time: 220 ms. Validating the certificate name. The certificate name was validated successfully. Additional Details Host name autodiscover.domain.com was found in the Certificate Subject Alternative Name entry. Elapsed Time: 1 ms. Certificate trust is being validated. The certificate is trusted and all certificates are present in the chain. Test Steps The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.domain.com, OU=PositiveSSL Multi-Domain, OU=Domain Control Validated. One or more certificate chains were constructed successfully. Additional Details A total of 1 chains were built. The highest quality chain ends in root certificate CN=AddTrust External CA Root, OU=AddTrust External TTP Network, O=AddTrust AB, C=SE. Elapsed Time: 34 ms. Analyzing the certificate chains for compatibility problems with versions of Windows. Potential compatibility problems were identified with some versions of Windows. Additional Details The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled. Elapsed Time: 5 ms. Testing the certificate date to confirm the certificate is valid. Date validation passed. The certificate hasn't expired. Additional Details The certificate is valid. NotBefore = 5/19/2014 12:00:00 AM, NotAfter = 5/18/2016 11:59:59 PM Elapsed Time: 0 ms. Checking the IIS configuration for client certificate authentication. Client certificate authentication wasn't detected. Additional Details Accept/Require Client Certificates isn't configured. Elapsed Time: 276 ms. Attempting to send an Autodiscover POST request to potential Autodiscover URLs. Autodiscover settings weren't obtained when the Autodiscover POST request was sent. Additional Details Elapsed Time: 172 ms. Test Steps The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.domain.com:443/Autodiscover/Autodiscover.xml for user me@domain.com. The Microsoft Connectivity Analyzer failed to obtain an Autodiscover XML response. Additional Details A Web exception occurred because an HTTP 404 - NotFound response was received from Unknown.HTTP Response Headers: Connection: close Content-Length: 315 Content-Type: text/html; charset=us-ascii Date: Sat, 19 Jul 2014 03:44:42 GMT Server: Microsoft-HTTPAPI/2.0 Elapsed Time: 171 ms. Attempting to contact the Autodiscover service using the HTTP redirect method. The attempt to contact Autodiscover using the HTTP Redirect method failed. Additional Details Elapsed Time: 207 ms. Test Steps Attempting to resolve the host name autodiscover.domain.com in DNS. The host name resolved successfully. Additional Details IP addresses returned: x.x.x.x Elapsed Time: 15 ms. Testing TCP port 80 on host autodiscover.domain.com to ensure it's listening and open. The port was opened successfully. Additional Details Elapsed Time: 76 ms. The Microsoft Connectivity Analyzer is checking the host autodiscover.domain.com for an HTTP redirect to the Autodiscover service. The Microsoft Connectivity Analyzer failed to get an HTTP redirect response for Autodiscover. Additional Details An HTTP 403 forbidden response was received. The response appears to have come from Unknown. Body of the response: HTTP Response Headers: X-FEServer: SMSE2013 Content-Length: 0 Date: Sat, 19 Jul 2014 03:44:42 GMT Server: Microsoft-IIS/8.0 X-Powered-By: ASP.NET Elapsed Time: 115 ms. Attempting to contact the Autodiscover service using the DNS SRV redirect method. The Microsoft Connectivity Analyzer failed to contact the Autodiscover service using the DNS SRV redirect method. Additional Details Elapsed Time: 39 ms. Test Steps Attempting to locate SRV record _autodiscover._tcp.domain.com in DNS. The Autodiscover SRV record wasn't found in DNS. Tell me more about this issue and how to resolve it Additional Details Elapsed Time: 39 ms. Checking if there is an autodiscover CNAME record in DNS for your domain 'domain.com' for Office 365. Failed to validate autodiscover CNAME record in DNS. If your mailbox isn't in Office 365, you can ignore this warning. Tell me more about this issue and how to resolve it Additional Details There is no Autodiscover CNAME record for your domain 'domain.com'. Elapsed Time: 28 ms.
I just double checked my SSL cert and it has the three typical entries:
DNS Name=mail.domain.com
DNS Name=AutoDiscover.domian.com
DNS Name=domain.com
I have assembled the output for the following commands
HERE
Get-OutlookProvider | fl Get-OutlookAnywhere | fl Get-ActiveSyncVirtualDirectory | fl Get-AutodiscoverVirtualDirectory | fl Get-EcpVirtualDirectory | fl Get-OabVirtualDirectory | fl Get-OwaVirtualDirectory | fl Get-PowerShellVirtualDirectory | fl Get-WebServicesVirtualDirectory | fl
I have gone through the Exchange Server Deployment Assistant. Almost everything was as it should have been. I made some changes in the "Enable and configure Outlook Anywhere" and "Configure service connection point."
I have switched external DNS over to my 2013 server, and the connectivity test is still failing. It is also not proxying the 2010 mailboxes through 2013 as it should (according to the Deployment Assistant).
I have a 2010 test account and a 2013 test account. Both work fine in their respective WebMail's, but the 2010 mailbox will not pull up through the 2013 WebMail.
Just for the heck of it, I have checked my SonicWall and it is configured the same for the 2010 host and the 2013 host. I knew that ports 80 and 443 were passing on both hosts anyway because the port 80 redirect works and https webmail works on both hosts.
If I try to access the xml file directly on both hosts:
https://mail.domain.com/Autodiscover/Autodiscover.xml (2013)
https://webmail.domain.com/Autodiscover/Autodiscover.xml
(2010)
I do get an xml response from both of them after authenticating like this:
<Autodiscover><Response><Error Time="18:17:41.0173284" Id="2526055628"> ErrorCode>600</ErrorCode><Message>Invalid Request</Message><DebugData/></Error></Response></Autodiscover>
Sooo...I'm stuck.
We know this is not recommended, but we are a small office and we bought a very robust server to be our DC and Exchange 2013 Server. We have installed Windows Server 2012 R2 with the AD, DNS, DHCP roles. We are now ready to install Exchange Server 2013 (with SP1) on this DC and have a question about the prerequisites.
Since this is a DC, do we still run this command script (using PowerShell)? (we will be installing both Exchange roles):
Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy,RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth,Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing,Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext45,Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation
Thank you!