So first, before you flame me, this is in QA!

We installed 2013 into a 2007 environment, then due to shifting business demand, cleanly removed 2013. Now we are trying to install 2010 CAS servers and it goes in fine, reports no errors, but I do not have 'server configuration' on the left pane of EMC, but I can run any related EMS cmdlet (so not permissions).  On the org health page all the info is listed as 'unavailable'. I'm thinking something is left over in AD's config container, but I can't find it. Help?

i have a server running server standard 2012 r2 recently upgraded from server standard 2003

it is a dc,dchp,dns.

i am trying to install exchange server 2013 standard during the installation i get the following error message.

and am unable to continue.

The following error was generated when "$error.Clear();
    install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema0.ldf")

" was run: "There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostWindows2003_schema0.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\Administrator.example\AppData\Local\Temp\ldif.err'".

We had an problem with the database where the mailbox of the admin user is located. I have fixed the mailbox, run the checks and received no errors.

Then i started a migrationbatch again and this was running so i started 3 more. Then the first batch i started hangs on completing. with the following error:
Error:MigrationTransientException: An error caused a change in the current set of domain controllers. --> An error caused a change in the current set of domain controllers.

I cannot find how i can stop this batch or give it a kickstart so it will complete the batch.

Kind regards,
Ben

P.S. Sorry for the poor English I'm Dutch.

After succesfull moving mailboxes from Exchange 2010 to Exchange 2013 (single all role servers in same Forest/AD) error messages are displayed in the eventviewer:

source: MSExchange Management Application
id: 5000

I do have installed a valid 3rd party certificate, all works well on both servers (2010 and 2013). How to fix this before I migrate all other mailboxes from 2010 to 2013?

Thnx Remco

Hello,

I have a new Exchange 2013 installation on a small corporate network. We us an external web and email hosting company.  We would like to continue receiving our incoming email through the external email host for SPAM, antivirus, and intrusion protection. In the past we have used the MAPI Labs mail connector to poll the external mail server for email and deliver it to our internal exchange system. Previously, outgoing email was sent via SMTP directly from the client PC. I would like it so the outgoing mail was routed through Exchange and ideally, only those with external email accounts count send outside the organization.

What I have done so far is have the external email host setup a secondary MX record on the external domain (ourserver.domain.com, which differs from their mail.domain.com). ourserver.domain.com points to our public network IP address.  I then had our internet ISP create a PTR for our IP that pointed back to ourserver.domain.com. In ECP I have send connector set to use MX records with a FQDN of ourserver.domain.com; however outgoing mail is slow to deliver and is identified as SPAM using my outlook.com personal mail.

How can I get my outgoing mail to stop getting flagged as spam?  I am still using a self signed certificate for testing and get certificate errors locally, but I do not think that is related. Am I going about this correctly?

Mike Orlando

Hello,

Running exchange 2013 in coexistence with 2010 SP3. When running best practive analyzer I get the following. I am unable to find documentation on this. Can anyone help?

Hello,

I have an issue regarding the OWA 2013.

When I want to open a message in a popup Windows in OWA 2013, randomly and suddenly, the icon "Starting" freezes and I have to wait 90 seconds to get access to the message.

When I launch the debug mode just as well with IE and Firefox, I'm seeing that request taking almost 90 seconds to complete

GET /owa/userspecificresourceinjector.ashx

Has anyone else faced that issue ?

My setup is one server HUB+CAS Echange 2013 Version 15.0 (Build 847.32)

Thanks for you time and your help,

PYD.

In my setup, I already have a exchange 2007 server and we are planning to migrate to exchange 2013.

On my first attempt to install exchange 2013 I had several issues and finally created a new server and managed to install exchange 2013 on it usingSetup /m:RecoverServer.

Since the first attempt of exchange 2013 installation had issues we want to uninstall exchange 2013 completely from our organization and start from scratch.

What would be the best way to uninstall this particular exchange 2013 completely so that it will also remove all the objects it has created within Active Directory?

Hello,

I wish all contents(Send,Receive,..etc) older than '06/21/2014' from all mailboxes should be exported to pst.

What to include additional to this cmdlet -

New-MailboxExportRequest -Mailbox <alias> -FilePath"\\Server\ShareFolder\<alias>.pst"

Please Guide.

Few details-

Name of Test mailbox - Demo

Mailbox Created on 06/10/2014

1) When I use the normal cmdlet,

New-MailboxExportReuqest -Mailbox Demo -FilePath "\\Server's IP\ShareFolder\Demo.pst it generates a pst of1505 KB.

2) When I use the cmdlet specifying today's date (For maximum output)

New-MailboxExportReuqest -Mailbox Demo -ContentFilter {(Received -lt "07/23/2014")} -FilePath "\\Server's IP\ShareFolder\Demo.pstit generates a pst only of 265 KB. (It means something is wrong somewhere)

3) Now the Strange thing is, the mailbox is created on 06/10/2014 (1.5 months old), when I use the cmdlet specifying the far previous date (3 months old)

New-MailboxExportReuqest -Mailbox Demo -ContentFilter {(Received -lt "04/23/2014")} -FilePath "\\Server's IP\ShareFolder\Demo.pstit again generates a pst of 265 KB. (It means something is wrong somewhere again)

Please Guide.

Thanks, Divyaprakash Koli

Hi,

after read the article 'http://technet.microsoft.com/en-us/library/dd638158.aspx', we already have MBX and CAS 2007 running the lastest spk version and the SSL on the CAS 2007 is already working as 'LEGACY.DOMAIN.COM.BR' + 'Autodiscover.domain.com.br'+ 'mail.domain.com.br'.

My question is regarding the SSL request for the new server:

>>> Can I start the REQUEST for the external Certification Authority using Windows Powershell or IIS console instead to use 'Exchange Management Shell'??

* I´m afraid about the time (days) to install CAS 2010 on the new server, start the request to the CA, do the internal steps to aprove, pay the tax, wait for generation and then install the new SSL on the new server...

Hello together,

having the following problem with Exchange 2013 CU2 and Outlook Anywhere access.

We set up the ExternalHostname same like the InternalHostname and use Split DNS.
But the Authentification Methods are different.

ExternalHostname                   : mail.customer.de
InternalHostname                   : mail.customer.de
ExternalClientAuthenticationMethod : Basic
InternalClientAuthenticationMethod : NTLM

Is this a Problem to use the same ExternalHostname than the Internal ?

I have some Issues connecting Outlook Anywhere to Exchange from external. Seems like it is only using NTLM and thats why it wont work.

We have TMG 2010 for reverse Proxy configured to Basic Authentification. I will get a passwort prompt loop or the autoconfiguration vom external is not going through.

When i configure TMG to delegegate the authentification to the exchange Server it is working. Looks like using NTLM then. (internalauthentificationmethod) ?

We do not want to use NTLM on TMG.

Is this a known issue ? How does outlook recognize which authentication to use when having the same proxyaddress ?

i read in that post (http://support.microsoft.com/kb/2754898/de) that generally the outlook connection information from internal can be seen , so how is this about the authentification method ? how can i check what is used actually ?

thanks for feedback,

best,

martin

Hi,

I need to migrate from Lotus Domino 8.5.3 to Exchange 2013, there's a tool to do it?

Kid Regards

Hello All,

      I am looking for a PDF or a case study on Migration from Exchange 2007 Geo Clustered Environment to O365 and if possible Challenges Faced during the process.

Regards

Sathya

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?

I tried an installation last week on a Windows Server 2008 R2 but was unable to get it to work. With the value of hindsight, I am inclined to think the error was more with the Web Site making EAC unavailable. I subsequently got it installed in my personal lab environment by creating a VM with a fresh install of Windows Server 2008 R2 SP1. 

With this information I then went back to the customer's site and installed a clean version of Windows Server 2008 R2 SP1 in a virtual machine under Hyper-V. After installing all the prerequisites the install appeared to be going just fine but then in failed in Step 7 with the following error:

The following error was generated when "$error.Clear(); 
          if ( ($server -eq $null) -and ($RoleIsDatacenter -ne $true) )
          {
            Update-RmsSharedIdentity -ServerName $RoleNetBIOSName
          }" was run: "Database is mandatory on UserMailbox.".

I know MS Exchange hides most of its information in AD so my suspicion is that the failed install on the real server has left some residual information in AD. Note that the original install on the real machine won't uninstall because the prior install attempt hasn't finished.

The relevant part of the Exchange Setup Log is:

Does anyone have suggestions about what to do with ADSI Edit to fix the problems?

I think I am getting close to having a working Exchange!!

Hello,

We're currently upgrading from Exchange 2007 to 2013 but are having problems with our GALs.  They are not showing up in the 2013 EAC, and running get-GlobalAddressList returns 0 results.  I ran the same command on the exchange 2007 servers, and got results, but noticed they were still in Legacy (exch 2003) mode with LDAP filters instead of OPATH. 

I have since updated the GALs using the ConvertFromLDAPFilter powershell script to OPATH.  Now, when I run get-GlobalAddressList on the Exchange 2007 side, they show the newer version ( 0.1 (8.0.535.0) ) and recipient filters, but I still have the same results on Exchange 2013 side. I don't see them in the EAC or when running Get-globaladdresslist. Also, in the Exchange 2007 side, when I click on the GAL, I don't have any options to edit properties on it, like other Address Lists. I'm not sure if this is expected behaviour, or another symptom of this problem.

Any help is appreciated.

Hello,

I am attempting to migrate a user mailbox currently located on an Exchange 2007 box, over to Exchange 2013 CU5. 

After following the steps outlined as per http://support.microsoft.com/kb/2807668/en-gb, I am still seeing a Content Index State of 'Failed and Suspended' when running the Get-MailboxDatabaseCopyStatus PS cmdlet on my Exchange 2013 server.

AD has replicated correctly, and the Microsoft Exchange Search and Microsoft Exchange Search Host Controller services have been restarted.

Can anyone help me from losing any more hair?!

Many thanks.

Hello,

I don't recall seeing any options during the Exchange 2013 install, to specify an alternate location for either the mailbox database or log files. I've reviewed the commands for moving the mailbox databases, but before reviewing the options for setting a location for the log files, I thought it best to see whether it's still advised to separate log/mailbox databases away from the OS, with our Exchange server being a virtualised instance?

Also, I'm assuming that Exchange still requires the usual backup of transaction logs, for them to be cleared?

Many 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.

Hi Guys,

Most probably I am going to deliver one project in nearest future, which included to move Mailboxes and mail data from Novel Group-wise to Exchange 2013. i want to know what should be the approach and what are the per-requisites that need to be consider to perform Migration steps in above scenario? please let me know how the mail-flow work to/from Group-wise to exchange 2013 and vice-verse. please suggest me some initial steps and URLs for this requirement. i want to be clarified logically before i suggest any solution on this to my customer.

step by step docs will be more helpful to achieve this goal..

Regards,

Aanand Singh