Exchange Server 2013: Internal Certificate Issue

Dear All,
I have MS Exchange 2013 with domain name: Exchange.local (fqdn: ex001.exchange.local).
I had created the accepted domain for xyz.com. I bought the Wildcard Certificate for *xyz.com. I had issued the certificate to my MS Exchange server.
External/Internet users: they can setting up and connected with MS Outlook
but I had problem with internal. when I setup account to MS Outlook. it failed and cannot connected to MS Exchange server because invalid ex001.exchange.local.
Do you have best solution and commend on this issue for internal users?
BR,
KH
[email protected]

Hi khemarin,
Did you set correctly the internal url´s for the services?
For Autodiscover URL:
If you are using a single server or all servers are in the same AD site, then the following commands can be used:
Get-ClientAccessServer | Set-ClientAccessServer -AutodiscoverServiceInternalUri https://mail.example.net/autodiscover/autodiscover.xml
However if you are using multiple servers in multiple AD sites, then you need to set the commands as per the box below, replacing "CAS-Server" with the real name of the server that holds the CAS role.
Set-ClientAccessServer -Identity "CAS-Server" -AutodiscoverServiceInternalUri https://mail.example.net/autodiscover/autodiscover.xml
For Webservices URL:
As with Autodiscover, if you are using a single server then the following commands can be used:
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory -InternalUrl https://mail.example.net/ews/exchange.asmx -ExternalUrl https://mail.example.net/ews/exchange.asmx
However if you are using multiple servers, then you need to set the commands as per the box below, replacing "CAS-Server" with the real name of the server that holds the CAS role.
Set-WebServicesVirtualDirectory -Identity "CAS-Server\EWS (Default Web Site)" -InternalUrl https://mail.example.net/ews/exchange.asmx -ExternalUrl https://mail.example.net/ews/exchange.asmx
For Outlook Anywhere URL:
Right click on the Client Access Server and choose Properties. Click on the tab Outlook Anywhere and adjust the URL to match the external name on the SSL certificate.
You should also need to check OAB Virtual Directory on IIS and see if it is enabled for SSL.
And you should have a Split DNS in this case.
I hope it helps.
David Paris Vicente

Similar Messages

Exchange Server 2013 OWA Related Issue

Hi everyone,
we installed exchange server 2013 for our new organisation.
Everything works fine except OWA Version, it shows as 2010.
Any suggestion to resolve this issue.
Regards
Kart26

Could be that you are still running an early build of Exchange 2013
and are using IE11 - That would load OWA Light that looks exactly the way it did in Exchange 2010.
Resolution: Install Exchange 2013
CU3
or as a workaround, add the domain to the compatibility view in IE.
Martina Miskovic

Exchange Server 2013 internal and external DNS records

I recently installed Exchange Server 2013 and I've register a pubic ip too for exchange server. How can I create internal DNS as well MX record for my Exchange server to send and receive internet mails. It's my first time configuring exchange for a organization.
registered domain name=====np.bbcmediaaction.org
public ip=====202.166.212.221

Hi,
For external mail flow, we need the following DNS records: MX records for the domain part of the external recipient, A records for the destination messaging servers. For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/bb676467(v=exchg.150).aspx
Additionally, to ensure external mail flow works well, we also need to configure send connector.
For more information, you can refer to the following article:
http://technet.microsoft.com/en-us/library/jj218640(v=exchg.150).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Exchange Server 2013 Outlook Anywhere issue

I am working on an issue with Outlook Anywhere in Exchange 2013 where external users cannot connect. This is a new server co-existing with an Exchange
2010 server that will soon be decommissioned.
When I run an Outlook Connectivity test on testexchangeconnectivity.com I get the following error. I am not seeing anything in the application or system logs.
I already applied CU 6 (which was released today) and am seeing the same results. Port 443 is exposed directly to the web (no TMG, load balancer, proxy server, or SSL accelerator). Any help would be greatly appreciated!
Attempting to ping RPC proxy <external Exchange URL>.
RPC Proxy can't be pinged.
Additional Details
An unexpected network-level exception was encountered. Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
Type: Microsoft.Exchange.Tools.ExRca.Extensions.MapiTransportException
Stack trace:
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
at Microsoft.Exchange.Tools.ExRca.Tests.MapiPingProxyTest.PerformTestReally()
Exception details:
Message: The remote server returned an error: (500) Internal Server Error.
Type: System.Net.WebException
Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at RpcPingLib.RpcPing.PingProxy(String internalServerFqdn, String endpoint)
at Microsoft.Exchange.Tools.ExRca.Extensions.MapiRpcTestClient.PingProtocolProxy(String endpointIdentifier)
Elapsed Time: 290 ms.

Hi,
Does the issue only happen to your Exchange 2013 external users? How about Exchange 2010 users?
Please make sure the external host name in your external Exchange URL is pointed to your Exchange 2013 in public DNS. For your coexistence environment, please make sure the Outlook Anywhere configurations are correct in both Exchange 2010 and Exchange 2013.
We can run the following command to check it:
Get-OutlookAnywhere | FL
If the configuration is not correct, we can run the following command to set it(supposing the mail.domain.com is your External host name):
For Exchange 2010:
Set-OutlookAnywhere -Identity “E14-01\Rpc (Default Web Site)” -ClientAuthenticationMethod Basic -SSLOffloading $False -ExternalHostName mail.domain.com -IISAuthenticationMethods NTLM, Basic
For Exchange 2013:
Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalHostname mail.domain.com -ExternalHostname mail.domain.com -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl
$True -InternalClientsRequireSsl $true
After all settings, please recycle MS Exchange RPCProxy AppPools and Default AppPools on both Exchange 2013 and Exchange 2010. Then restart IIS service by running IISReset /noforce from a command prompt window.
Regards,
Winnie Liang
TechNet Community Support

Exchange Server 2013 CU7 Installation Issue

Error:
The following error was generated when "$error.Clear();
            if ($RoleProductPlatform -eq "amd64")
                try
                    # Need to configure the ETL traces before the fast service is installed. This will ensure that when the service comes up
                    # it will have the necessary trace session setting available to read from the registry
                    $fastPerfEtlTraceFolderPath = Join-Path -Path $RoleBinPath -ChildPath "\Search\Ceres\Diagnostics\ETLTraces"
                    $fastDiagnosticTracingRegKeyPath = 'HKLM:\SOFTWARE\Microsoft\Office Server\16.0\Search\Diagnostics\Tracing'
                    if(-not(Test-Path -Path $fastPerfEtlTraceFolderPath))
                        $null = New-Item $fastPerfEtlTraceFolderPath -Type 'Directory' -Force
                    if (-not(Test-Path -Path $fastDiagnosticTracingRegKeyPath))
                        $null = New-Item -Path $fastDiagnosticTracingRegKeyPath -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'TracingPath' -PropertyType 'string' -Value $fastPerfEtlTraceFolderPath
-Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'TracingFileName' -PropertyType 'string' -Value 'DocumentProcessingTrace'
-Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'DocumentParserSuccessLogMessage' -PropertyType 'Dword' -Value 1 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'DocumentParserLoggingNoInitialisation' -PropertyType 'Dword' -Value 1 -Force
                    # Max trace folder size 50 * 100 = 5GB
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'MaxTraceFileSize' -PropertyType 'Dword' -Value 50 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'MaxTraceFileCount' -PropertyType 'Dword' -Value 100 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'UseGeneralSwitch' -PropertyType 'Dword' -Value 1 -Force
                    $null = New-ItemProperty -Path $fastDiagnosticTracingRegKeyPath -Name 'GeneralSwitch' -PropertyType 'Dword' -Value 1 -Force
                catch
                    # ETl tracing is not critical. Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while trying to Configure the FAST ETL traces. Exception: " + $_.Exception.Message);
                try
                    $fastFusionRegKeyPath = 'HKLM:\SOFTWARE\Microsoft\Office Server\16.0\Search\FlightControl'
                    if (Test-Path -Path $fastFusionRegKeyPath)
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_new_enabled' -Force -ErrorAction SilentlyContinue
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_old_enabled' -Force -ErrorAction SilentlyContinue
                        Remove-ItemProperty -Path $fastFusionRegKeyPath -Name 'fusion_compare_outputs' -Force -ErrorAction SilentlyContinue
                catch
                    # Removing new fusion keys is not critical. Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while trying to remove the fast new fusion reg keys. Exception: " + $_.Exception.Message);
                $fastInstallConfigPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\Installer";
                $command = Join-Path -Path $fastInstallConfigPath -ChildPath "InstallConfig.ps1";
                $dataFolderPath = Join-Path -Path $RoleBinPath -ChildPath "Search\Ceres\HostController\Data";
                # Remove previous SearchFoundation configuration
                &$command -action u -silent;
                try
                    if ([System.IO.Directory]::Exists($dataFolderPath))
                        [System.IO.Directory]::Delete($dataFolderPath, $true);
                catch
                    $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + " - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $deleteErrorMsg;
                # Re-add the SearchFoundation configuration
                try
                    # the BasePort value MUST be kept in sync with dev\Search\src\OperatorSchema\SearchConfig.cs
                    &$command -action i -baseport 3800 -dataFolder $dataFolderPath -silent;
                catch
                    $errorMsg = "Failure configuring SearchFoundation through installconfig.ps1 - " + $_.Exception.Message;
                    Write-ExchangeSetupLog -Error $errorMsg;
                    # Clean up the failed configuration attempt.
                    &$command -action u -silent;
                    try
                        if ([System.IO.Directory]::Exists($dataFolderPath))
                            [System.IO.Directory]::Delete($dataFolderPath, $true);
                    catch
                        $deleteErrorMsg = "Failure cleaning up SearchFoundation Data folder. - " + $dataFolderPath + "
- " + $_.Exception.Message;
                        Write-ExchangeSetupLog -Error $deleteErrorMsg;
                # Set the PowerShell Snap-in's public key tokens
                try
                    $PowerShellSnapinsPath = "HKLM:\SOFTWARE\Microsoft\PowerShell\1\PowerShellSnapIns\";
                    $FastSnapinNames = @("EnginePSSnapin", "HostControllerPSSnapIn", "InteractionEnginePSSnapIn", "JunoPSSnapin",
"SearchCorePSSnapIn");
                    $officePublicKey = "71E9BCE111E9429C";
                    $exchangePublicKey = "31bf3856ad364e35";
                    foreach ($fastSnapinName in $FastSnapinNames)
                        $fastSnapinPath = $PowerShellSnapinsPath + $fastSnapinName;
                        $assemblyNameProperty = Get-ItemProperty -Path $fastSnapinPath -Name "AssemblyName" -ErrorAction SilentlyContinue;
                        if ($assemblyNameProperty -ne $null -and (-not [string]::IsNullOrEmpty($assemblyNameProperty.AssemblyName)))
                            $newAssemblyName = $assemblyNameProperty.AssemblyName -ireplace ($officePublicKey, $exchangePublicKey);
                            Set-ItemProperty -Path $fastSnapinPath -Name "AssemblyName" -Value $newAssemblyName;
                catch
                    # Info only log
                    Write-ExchangeSetupLog -Info ("An exception ocurred while configuring Search Foundation PowerShell Snapin. Exception: " + $_.Exception.Message);
        " was run: "System.Exception: Failure configuring SearchFoundation through installconfig.ps1 - Error occurred while configuring Search Foundation for Exchange.System.ServiceModel.EndpointNotFoundException:
Could not connect to net.tcp://exchange.domain.com:3803/Management/InteractionEngine. The connection attempt lasted for a time span of 00:00:02.0470060. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.0.0:3803.
---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 192.168.0.0:3803
   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   --- End of inner exception stack trace ---
Server stack trace:
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   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.INodeOperationsManagementAgent.AddNamedNode(String node)
   at Microsoft.Ceres.Exchange.PostSetup.NodeManager.DeployInterationEngineNode()
   at Microsoft.Ceres.Exchange.PostSetup.DeploymentManager.Install(String installDirectory, String dataDirectoryPath, Int32 basePort, String logFile, Boolean singleNode, String systemName, Boolean attachedMode)
   at CallSite.Target(Closure , CallSite , RuntimeType , Object , Object , Object , Object , Object , Object , Boolean )
   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.Deployment.WriteExchangeSetupLog.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".
Al

Hi,
Agree with ED.
The key message is “Could not connect to net.tcp://exchange.domain.com:3803/Management/InteractionEngine.
The connection attempt lasted for a time span of 00:00:02.0470060. TCP error code 10061: No connection could be made because the target machine actively refused it 192.168.0.0:3803”
You need to check why it’s block. Any firewall or the port is listened by other processes.
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

CANNOT ACCES EXCHANGE ADMIN CENTER (ECP) ON EXCHANGE SERVER 2013. GOT HTTP 500 INTERNAL SERVER ERROR

HI, I just installed Exchange server 2013 Standar SP1 on a windows server 2012. I have 3 servers one is a Domain Controller, the other one has the MBX role, and the last one the CAS role, first i installed the MBX and after the CAS role, i passed
prerequisite check without any issue. However when I tried access Exchange Admin Centre (ECP) at https:\\servername\ecp
I got HTTP 500 Internal Server Error saying "This website cannot display the page. Most likely causes: 1. The website is under maintenance. 2. The website has a programming error." I tried access ECP at https://localhost/ecp and
I got the same problem. Under either cases I was able to see the logon page of ECP and I was able to enter my credential (e.g. domain\user name, password). However I got HTTP 500 Internal Server Error at the next page.
I appreciate your help, on my case.

Hi,
The link that Jatin points to should be this.
https://social.technet.microsoft.com/Forums/en-US/2f64d305-e9e2-4f48-a5b4-4f72d7bca801/exchange-2013-owaecp-http-500-internal-server-error?forum=exchangesvrclients
Please view the Application Pool to check whether the version of .NET Framework is 4.0 and try the following command.
%windir%\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe –i.
If this does not help then please check if there is any warnings or errors in Event Log and take your time to post them for my further troubleshooting.
Thanks.

Exchange Server 2013 SP1 - Internal Email Flow slowness

Hi Fellows,
I have a brand new implementation of Exchange Server 2013 SP1 with three mailbox servers and 3 CAS servers.
I am facing a considerable slow transportation of email internally. although there are just 3 mailboxes on the infrastructure at the moment.
When a user sends email to himself or other two accounts, delivery takes from 15 seconds to 35 seconds to be delivered.
Experience is same even if the email is sent from OWA, ActiveSync or Outlook.
Header analysis shows the message exchange between mailbox servers is taking time. any clue?
Decreasing Tarpit interval on Mailbox server receive connectors will be helpful?
Network communication, Storage performance, Server performance are all as good as we love to.
Thanks.
J.A

Hello,
When a user send message to a internal user in a AD site, the connector will not be used. I recommend you use message tracking to check the issue occur on server side or transport process. Please use queue viewer to check if there is mail traffic.
Cara Chen
TechNet Community Support

Exchange server 2013 - cannot send / receive external emails - we can access owa -we can send/receive internal emails

Exchange server 2013 in Windows server 2012 VM
It was working fine then start the issue.
Firewall is managed externally and the last report said:
"I checked the firewall logs, which shows traffic being allowed through port 25 from 10.10.10.10 to 4.28.237.225: Log Number 116 Last Activity 2014-08-28 23:48:33 Status [accept] Src 10.10.10.10 Dst 4.28.237.225 Service SMTP Policy ID 1 Src Port 64081
Dst Port 25 While I showed one log, there were multiple log entries showing the same: traffic being accepted through port 25 from 10.10.10.10 to 4.28.237.225.
Can you verify that the mail server is set up so as to allow port 25? "
Today I was able to telnet the server from home: successfully
220 DTALL-EXCSRV002.DTC.dualtemp.com Microsoft ESMTP MAIL Service ready at Sat, 30 Aug 2014 16:31:16 -0400 ehlo 250-DTALL-EXCSRV002.DTC.dualtemp.com Hello [70.44.124.141] 250-SIZE 37748736 250-PIPELINING 250-DSN 250-ENHANCEDSTATUSCODES 250-STARTTLS 250-X-ANONYMOUSTLS
250-AUTH NTLM 250-X-EXPS GSSAPI NTLM 250-8BITMIME 250-BINARYMIME 250-CHUNKING 250 XRDST
Also the receive - send connectors seems ok
Mx record point to Microsoft protection:
dualtemp-com.mail.protection.outlook.com.
Again, OWA is able to access and send/receive emails internal but never external even no bounceback just it never arrive.
Help me please. This is my first admin chaos...

Hi,
Is there any update with your issue?
If the CAS and Mailbox servers are collocated on the same server, the SMTP Receive connection for the Transport service will listen on 2525 instead of 25. If you install the CAS and Mailbox on the same server, please make sure that port 2525 is open.
For more information about Exchange 2013 mail flow, here is a blog for your reference.
Exchange 2013 Mail Flow Demystified…Hopefully
http://blogs.technet.com/b/rischwen/archive/2013/03/13/exchange-2013-mail-flow-demystified-hopefully.aspx
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

Exchange Server 2013 with 3rd party wild Card Certificate shows Invalid

Hi Team,
I've Exchange Server 2013 SP1. Imported a valid 3rd party wild Card Certificate but the status is continuously showing "Invalid" on all my 2013 servers. Any help?
Thank you.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

Hello,
Can you enable it on the Exchange Services like, IIS, SMTP without any issues?
If the certificate is for OWA, is there any certificate issue when you accessing OWA?
Run the following command to get the Exchange Certificate information and post them for researching:
Get-ExchangeCertificate |FL
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Issues with setting up Exchange Server 2013

Hi All
Not sure what im doing wrong yet i am having issues with exchange server 2013.
Currently I have got general SMTP Mail flow working. as long as i log onto the local servers OWA (https://10.x.x.x/owa) i can log into a users mailbox. i have tested sending and recieving mail using this and it works.
My main issue now is with accessing the OWA externally via our website. (owa.xx.xx.au/owa) or connecting ANY Outlook to the server.
When i connect to the exchange server via outlook it asks for the password again multiple times never authenticating it then time's out and says:
" the action cannot be completed. the connection to microsoft exchange is unavailable, outlook must be online or
connected to complete this action "
then when i click on OK it goes to the General Tab and under microsoft exchange server: the name for it appears as
[email protected]
with mailbox set as:
=SMTP:[email protected]
Currantly on our DNS i have
mx= 10 mail.xx.xx.au
CNAME= autodiscover = mail.xx.xx.au
CNAME= OWA = mail.xx.xx.au
A = mail = 12.34.56.78
On our modem/router i have set one-to-one nat to our firewall IP
On our firewall i have
SMTP SAT and NAT to Exchange server
HTTPS Sat and NAT to exchange Server
HTTP Sat and Nat to exchange Server
Port 587 SAT and Nat to exchange server
pop SAT and NAt to exchange server
Im willing to bet its something stupid i have overlooked but i was wondering if anyone would be able to help me out
Regards
Sibsy

Hello,
Firstly, please follow the Shadab's suggestion to check related virtual directory settings.
Please make sure you use certificate that's created by a CA that's trusted by the client computer's operating system.
Please use get-outlookanywhere | fl cmdlet to check ExternalClientAuthenticationMethod. By default, the authentication is Negotiate.
Cara Chen
TechNet Community Support

Outlook 2013 not connect with Exchange server 2013 in internal network

Hello All,
I Have two Exchange server 2013 in our environment. Both server install mailbox and CAS role. After configure exchange server 2013, Outlook 2013 not connect in internal network. I have configure outlook manually. i tried by using the suggestion from blog
but not work. Outlook show that Server cannot connect/ server name could not be resolved. in outlook setting i also put exchange proxy setting. In exchange admin center i have changed the OWA, OAB, Auto discover name. But still not work.
I know that outlook can be connect from external by using ssl certificate and publish outlook anywhere but i did my configure from internal network.
Can you please suggest as soon as possible.
Thanks,
Parvez

Hi,
Firstly, I’d like to explain, same with external users, internal users use Outlook Anywhere to connect with Exchange server and use Autodiscover get all settings.
Thus, let’s try the following resolutions:
1. run the following command: get-clientaccessservice |fl autodiscoverserviceinternaluri
2. check if the host name in the above URL is in the DNS server and there is a DNS entry about the host name points to the proper IP address.
3. Check if the above host name is in your certificate.
Thanks,
Angela
Angela Shi
TechNet Community Support

Issues connecting Outlook 2011 for Mac to Exchange Server 2013

Could someone help me with the bellow please:
I have a Mac with outlook 2011 on it.
We have recently set up Exchange Server 2013, and all of the Windows Workstation just required the trusted root certificate to be installed and they were working.
However I have spent hours reading different forums trying to get this working on the Mac and no luck.
The auto discover does not work when setting up the exchange email, therefore I have also tried setting up manually but it still will not connect to the server.

Hi,
Please check if the links below help:
How the Autodiscover service works with Outlook for Mac 2011:
http://technet.microsoft.com/en-us/library/jj984202(v=office.14).aspx
A great tool for troubleshooting Autodiscover and Outlook 2011 for Mac connectivity issue:
http://blogs.technet.com/b/johnmak/archive/2012/04/01/a-great-tool-for-troubleshooting-autodiscover-and-outlook-2011-for-mac-connectivity-issue.aspx
Since this forum is for general questions and feedback related to Outlook for Windows, it's better to post your question to the forum for Exchange or for Mac:
Exchange forum:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
Office for Mac forum:
http://answers.microsoft.com/en-us/mac/forum/macoffice2011?tab=Threads
The reason why we recommend posting appropriately is you will get the most qualified pool of respondents, and other partners who read the forums regularly
can either share their knowledge or learn from your interaction with us. Thank you for your understanding.
Steve Fan
TechNet Community Support

Exchange Server 2013 - Lab setup with internal emails only

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

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

Http 500 internal server error exchange server 2013

Hello Everyone
Here is my little scenario.
i have a domain named contoso.com
i then installed exchange server 2013 in my environment. cas and mailbox server are on seperate box.
switched of my exchange servers for a week, during that period i changed the netbios name of my domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
a week later i switched on my exchange servers. during the same time i created two new servers one cas and the other mailbox
i now have 2 cas server and 2 mailbox server
problem now is that when i log into my ecp on one of my cas server using https://servername/ecp. after inserting my username and password i get http 500 internal error
although with exchange management shell i can connect to all the servers

-->switched of my exchange servers for a week, during that period i changed the netbios name of my
domain to toso from contos. although my domain name still remain contoso.com. the only change i made was the netbios name
Did you change your domain to toso.com? If yes then your first/previously installed exchange is broken. Exchange server is fully integrated with domain.
Renaming of domain is not supported in Exchange2007/2010/2013. (Even in Exchange2000/2003 you need some netbios name resolution. Check this for an info)
Anyway did you try login to the newly installed exchange (i.e. Exchange installed after Netbios rename)?
Try that first https://newserverip/ECP and https://newserverip/OWA (that is supposed to work), If
that works I suggest you try to uninstall the previously installed Exchange after moving the database using database portabilityand install again as new
server.
Please get back with the result.
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.

Issues trying to recover failed Exchange Server 2013 in a DAG

Having several issues attempting to recover a failed Exchange Server 2013. To start out, the failed server was mounted on a virtual server using hyper-v. The virtual server failed due to some hard drive partition issues and would no longer boot. As there
really was no purpose to having Exchange on a Virtual Server I decided to rename the host to the same name as the virtual server. I reset the name in AD and proceeded to rename the server. Then made sure all the necessary things were installed and proceeded
to do a recovery installation. I neglected to properly delete the old databases belonging to that server. I simply deleted the files off the hard drive instead of doing it properly. I should mention this is a two node plus witness server installation.Now,
it seems I cannot delete the former server in either ECP or command line. I have attempted to clean up the mess with the old databases but there is one that was mounted only on the failed server that I cannot remove. It seems until I can remove that, I cannot
remove the failed server from the DAG and do a recovery install. The steps shown in the tech net articles to remove a failed database have also failed. At this point I am wondering if I should just give up on the server name and do an install on a new server
name or if someone can give me some information on how to clean up the mess, that would be better I am sure. Here is a list of the things I have tried.
https://technet.microsoft.com/en-us/library/dd876880(v=exchg.150).aspx and in this article, the item mentioned is not in ADSIedit.
http://exchangeserverpro.com/unable-remove-failed-server-dag-exchange-server-2010/
http://exchangeserverpro.com/exchange-2013-how-to-remove-dag-member/ This
article describes one of the problems I am having but the solution is not there.
Thanks to any and all who can offer advice.
Ronald C. Pope

Thank you for your answer. Running that command results in the following:
[PS] C:\Windows\system32>Remove-MailboxDatabase "Mailbox Database 0939719168"
This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, public folder mailboxes or
arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database"Mailbox Database 0939719168". To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of
archive mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Archive. To get a list of all
public folder mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -PublicFolder. To get a
list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database "Mailbox Database 0939719168" -Arbitration.
To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox
<Mailbox ID> -Archive. To disable a public folder mailbox so that you can delete the mailbox database, run the command
Disable-Mailbox <Mailbox ID> -PublicFolder. Arbitration mailboxes should be moved to another server; to do this, run
the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command
Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox.
Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID>
-Database "Mailbox Database 0939719168".
    + CategoryInfo          : InvalidOperation: (Mailbox Database 0939719168:DatabaseIdParameter) [Remove-MailboxDatab
   ase], AssociatedUserMailboxExistException
    + FullyQualifiedErrorId : [Server=EX01,RequestId=69b60793-fc4f-4dac-beb9-8c9afe381a36,TimeStamp=1/26/2015 6:28:34
   PM] 2BA41E0C,Microsoft.Exchange.Management.SystemConfigurationTasks.RemoveMailboxDatabase
    + PSComputerName        : ex01.<domain>com
I was able to disable the one mailbox that was listed for the database. I got the following error when attempting the command Get-Mailbox -Database"Mailbox Database 0939719168"
[PS] C:\Windows\system32>Get-MailboxPlan Database "Mailbox Database 0939719168"
Get-MailboxPlan : The term 'Get-MailboxPlan' 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.
At line:1 char:1
+ Get-MailboxPlan Database "Mailbox Database 0939719168"
+ ~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Get-MailboxPlan:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
the public folder and archive switch simply return a command prompt leading me to believe that there are no public or archive boxes on that database.
Ron

Exchange Server 2013: Internal Certificate Issue

Similar Messages

Maybe you are looking for