DNS Requirements in Exchange 2013: Which RR's to create & what do they do?

Hi Experts, I had been primarily a RHEL guy in the past. Currently, I have 3 Node (All-in-one) Exchange 2013 DAG (all 3 nodes are virtualized in Hyper-V 2012 and are a part of HyperV2012
Cluster). In DNS, I have created 3 A records for mail.domain.com which resolve to to the Public IP addresses (MAPI IP address) of all 3 CAS servers. And I have also enabled Outlook anywhere. OWA internally is working fine.
I would like to know: what else do I need to do in DNS (& elsewhere in EAC) to get Outlook 2013 (MAPI/CDO client) & OWA work from both within & outside the corporate network (via
the internet). I mean, in terms of additional Resource records in DNS, SRV records, MX records, new zones, URL settings of each server for each service, virtual directory changes etc. I am not sure which all RR's in DNS would be needed, how they should be
set & what purpose each of them would server.
A simplified (but detailed) explanation would be better because I have never dealt with Outlook anywhere before. Would be great if experts could point me to relevant blogs & online
resources that contain valid examples of accomplishing the same. Thanks in advance.
Regs,
Rahul

Yes Steve, that is how all Load Balancers are supposed to work but somehow it is not working for me.
However, could you please help me understand if my DNS settings are perfect:
DNS
A records:
100.10.10.200 (LB VIP): mail.domain.com
100.10.10.200 autodiscover.mail.com
100.10.10.20   email.domain.com
(1st Exchange MAPI IP address)
100.10.10.21   email.domain.com (2nd
Exchange MAPI IP address)
100.10.10.22   email.domain.com (3rd
Exchange MAPI IP address)
There is 1 MX record : mail.domain.com & there is no SRV record.
The virtual directories are set to email.domain.com (internal
URL) & mail.domain.com (external URL) for Outlook Anywhere to work. So, right now I am able to access email.domain.com (virtual directories Internal URL) but not mail.domain.com (virtual directories external URL) because 100.10.10.200
as a VIP service is DOWN in Kemp.
Please suggest.
Regards, Rahul

Similar Messages

Exchange 2013 public folder can not create folder

hello,
we have migrate public folders to20102013.
we can not createfolders / files inpublic folders.Access Rights seems to be
ok on the control panel
in Outlook, we can not apply change permissions
what can i do to fix that ?
all the public folder have migrate on the secondary mailbox public folder like the technet KB
Please, help us !
thank you

Could you please have a look at below mentioned links ? May be, it will help you to sort-out the issue which you are getting right now while moving public folder :
http://redmondmag.com/articles/2013/07/15/exchange-2013-cu2.aspx
http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-preview-public-folders-part1.html
Carlo

Exchange 2013 - Removing a database and deleting folders but they still reappear!!

Hi
I created a new database and moved all the user mailbox's plus discovery mailbox;s over and all went well, i then unmounted and deleted the old database in ECP and stopped all the exchange services and deleted the old database files and folders from the
C:, i noticed i was still getting some errors with windows backup and after looking around i notice for some reason under program files/microsoft/exchange server/v15/mailbox the old db folder appears with the sub folders 'indexmeta', 'journal' and 'ms', it
seems that the last trace of the old databases is still being used because the date is always todays date! everytime i delete these foldersers they come back!!
I think this is the reason why the windows backup is failing with 'this application will not be available from this backup'
any help would be appreciated!

Hello,
If you want to remove the old database, you can follow this document to do that:
Manage Mailbox Databases in Exchange 2013
http://technet.microsoft.com/en-us/library/jj150580.aspx
Did you enable journal on the old database?
Thanks,
Evan Liu
TechNet Subscriber Support
in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

DNS Configuration for Exchange 2013

I have a stand alone server 2012 with AD, DHCP, DNS and Exchange on it and started getting DDoS attacks
I installed a firewall had to change the subnet of the server from 10.0.0.0/24 to 192.168.1.0/24 and after re-configuring the Servers IP, DHCP and DNS found that I had no incoming email. (invalid Security Certificate)
I found that mail traffic was directed to the Router instead of Exchange and being rejected with the routers security certificate. I have since fiddled with the DNS so many times I don't know what is right and wrong
Anyone have any ideas where I have gone wrong what is in the tables that shouldn't be there and what is missing.
email address is user.mail.domain.com
Geotrust SSL Security Certificate is mail.domain.com autodiscover.domain.com server01.domain.com
**Forward lookup for domain.com
Same as parent SOA
[28]server01.domain.com, hostmaster.domain.com
Same as parent NS
server01.domain.com
Same as parent NS
ns1.domain.com
Same as parent NS
ns2.domain.com
Same as parent MX
[10]mail.domain.com
Same as parent MX
[20]mail.domain.com
server01 MX [10]mail.domain.com
Same as parent HostA
192.168.1.10
Same as parent HostA
139.130.XXX.YYY
server01 HostA
192.168.1.10
mail HostA 192.168.1.10
mail HostA 139.130.XXX.YYY
localhost HostA
127.0.0.0
Properties SOA ns1.domain.com 139.130.XXX.YYY
ns2.domain.com 139.130.XXX.YYY
server01.domain.com 192.168.1.10
**Forward lookup for mail.domain.com
Same as parent SOA
[1]server01.domain.com, hostmaster.domain.com
Same as parent NS
server01.domain.com
Same as parent HostA
192.168.1.10
Same as parent HostA
139.130.XXX.YYY
Properties of SOA server01.domain.com
192.168.1.10
**Reverse Lookup
1.168.192.in-addr.arpa
Same as parent SOA
[1]server01.domain.com, hostmaster.domain.com
Same as parent NS
server01.domain.com
Same as parent NS
ns1.domain.com
192.168.1.10 PTR
domain.com
192.168.1.10 PTR
mail.domain.com
OWA and Outlook 2013 work incoming and outgoing from within the subnet, both internal emails and external emails
But users off site can't log in to outlook 2013 and get blocked with OWA by invalid security certificate.
**Testconnectivity.microsoft.com results
autodiscover failed
resolved host domain.com successful with both correct IP addresses returned
Port 443 open
SSL Certificate incorrect it is the routers Certificate not the Geotrust certificate.
**This is the real issue, and I can't figure out why
Thanks Alan

Thanks Luke
Yes you are right , I get alternate WAN and LAN Ip addresses when I flushdns
I suspected I had additional entries ans/or wrong entries in the DNS Zones
i reformatted to show up in columns in the post
I hope you can point out which are wrong
**Forward lookup for domain.com
Same as parent----- SOA----[28]server01.domain.com, hostmaster.domain.com
Same as parent----- NS -----server01.domain.com
Same as parent----- NS -----ns1.domain.com
Same as parent----- NS -----ns2.domain.com
Same as parent----- MX -----[10]mail.domain.com
Same as parent----- MX -----[20]mail.domain.com
server01-------------- MX----- [10]mail.domain.com
Same as parent----- HostA --192.168.1.10
Same as parent----- HostA --139.130.XXX.YYY
server01-------------- HostA --192.168.1.10
mail --------------------HostA-- 192.168.1.10
mail --------------------HostA-- 139.130.XXX.YYY
localhost-------------- HostA --127.0.0.0
Properties SOA --ns1.domain.com 139.130.XXX.YYY
----------------------ns2.domain.com 139.130.XXX.YYY
----------------------server01.domain.com 192.168.1.10
**Forward lookup for mail.domain.com
Same as parent----- SOA------[1]server01.domain.com, hostmaster.domain.com
Same as parent----- NS--------server01.domain.com
Same as parent -----HostA---192.168.1.10
Same as parent -----HostA---139.130.XXX.YYY
Properties of SOA server01.domain.com
192.168.1.10
**Reverse Lookup
1.168.192.in-addr.arpa
Same as parent----- SOA-----[1]server01.domain.com, hostmaster.domain.com
Same as parent----- NS-------server01.domain.com
Same as parent----- NS-------ns1.domain.com
192.168.1.10-------- PTR------domain.com
192.168.1.10-------- PTR------mail.domain.com
do I need an autodiscover record?
I setup 2 forward lookup zones domain.com and mail.domain.com
From memory the mail.domain.com was for external access but I don't think that was how it turned out
Thanks

My 2nd hand phone was recently restored by a repairer due to issues beyond my control and now since the restoration the phone asked me for an icloud username and password of which I have never created. what can I do???

Activation help!
I need to activate my 2nd hand Iphone by entering the apple iD and password used to set up icloud. My problem is that I have never set up icloud. I purchased the phone off the original owner almost 12 months ago and have recently experienced problems which required repairing.
The repairer apparently had to delete my iD I used to login to itunes and now is asking for icloud email and password.
Can someone help me please?

The only solution is to contact the original owner. He will need to give you the info required. Apple will not help you circumvent the activation lock.

Configuring IIS and DNS for Exchange 2013 running on Second Win2012 R2 Server

Hi Folks,
I have a Windows 2012 R2 Server with Essentials role and I'm running a Hyper-V instance of Windows 2012 R2 with Exchange 2013 installed joined to domain. I have been through the wizards and the Exchange Server deployment wizard but I'm stuck with configuring
DNS records correctly.
Currently I can browse to https://remote.contoso.com externally and internally which works as expected but not https://remote.contoso.com/owa or any other Exchange pages. All I get is 404 - File or directory not found. However if I browse
internally to https://exchangeserver.domain.local/owa it works. So I'm guessing 404 is coming from the DC server not the exchange server. Hence I think its DNS.
Although I have noticed that IIS is on the DC and the Exchange server, showing different Sites. Does this have anything to do with the issue at hand. Also the guides are not perfectly clear on how to add the DNS CNAME records.
Would someone be so kind as to point me in the right direction.
Thank you

Hi Jatin,
It turned out to be a little more involved in the end. I had to call Microsoft in the end. ARRconfig wasn't running correctly and after creating a new certificate it was able to run successfully. I'm waiting for the detailed report which
will hopefully explain the issue with Bindings between the two IIS on Essentials and Exchange 2013 which was also and issue.
Then I had an issue trying to connect Outlook clients to Exchange. The resolution for this was:
Created new SAN certificate with issued to name as “mail.pinewoodonline.co.uk” using the CA server
OutlookProvider EXCH and EXPR value was not set
Set OutlookProvider EXCH and EXPR value as “msstd:mail.pinewoodonline.co.uk” by running the below command
Set-OutlookProvider EXPR -Certprincipalname msstd:mail.pinewoodonline.co.uk
Set-OutlookProvider EXCH -CertPrincipalName msstd:mail.pinewoodonline.co.uk
All seems good now. I will post the report as soon as I get it. This took 6 hours on the phone to Microsoft. Wasn't easy.
Thanks
Brandan

Exchange 2013 Domain Prep Fails: Setup /prepareschema, setup /PrepareAD, Setup /PrepareDomain

Whenever I try to prep for a 2013 exchange install I always get:
"earlier versions of the server roles that are installed were detected"
whenever I try to run Setup /prepareschema OR setup /PrepareAD OR Setup /PrepareDomain
I am working on a Server 2012 standard machine with Exchange 2010 currently installed. This server is a DC (bad I know), DNS, DHCP.
I am trying to prep the domain so that I can install Exchange 2013 on a VM and eventually remove Exchange 2010 from the organization altogether.
There are no other domain controlelrs in the domain. The domain started life as a SBS 2003 machine which was demoted and removed once the server 2012 box was up with exchange 2010 running.
Any help would be greatly appreciated.
Here is some info that may help:
1. PrePare Schema
Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
Ran setup /PrepareSchema
This command should perform the following tasks:
A: Connects to the schema master and imports LDAP Data Interchange Format (LDIF) files to update the schema with
Exchange 2013 specific attributes. The LDIF files are copied to the Temp directory and then deleted after they are imported
into the schema.
B: Sets the schema version (ms-Exch-Schema-Verision-Pt) to a Exchange 2013 value.
This command fails with: Earlier versions of server roles that were installed were detected.
First I confirmed that administrator account for domain is a member of schema admins and enterprise admins.
Next I ran asdiedit.
I navigated to: "CN=ms-Exch-Schema-Version-Pt,CN=Schema,CN=Configuration,DC=BDA,DC=LAN"
and reviewed the current "rangeUpper" attribute.
The ms-Exch-Schema-Verision-Pt is not updated to CU3 range Upper setting.
The current range upper 14734 which means its still at Exchange 2010 SP3 settings.
In short, updaing the schema fails.
2. Prepare Active Directory
Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
setup /PrepareAD [/OrganizationName:<organization name>]
This command fails with: Earlier versions of server roles that were installed were detected.
schema update version 56
I began reviewing the long, long list of the following containers and objects under
CN=<Organization Name>,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=<root domain>
which are required for Exchange 2013:
missing cn=Auth Configuration
missing CN=ExchangeAssistance
missing CN=Monitoring Settings
missing CN=Monitoring Settings
missing CN=Monitoring Settings
missing CN=Workload Management Settings
Checked Management role groups within the Microsoft Exchange Security Groups OU
missing Compliance Management group --- Manually created this entry
Step 3 Prepare Domain:
Navigated an elevated command prompt to the folder with Exchange 2013 CU3.
Ran setup /PrepareDomain
This command fails with: Earlier versions of server roles that were installed were detected.
confirmed the following:
ObjectVersion property fails as it is still set to Echange 2010 sp3 - 13040
You have a new global group in the Microsoft Exchange System Objects container called Exchange Install Domain Servers-DONE
The Exchange Install Domain Servers group is a member of the Exchange Servers USG in the root domain.-DONE
On each domain controller in a domain in which you will install Exchange 2013, the Exchange Servers USG has permissions
on the Domain Controller Security Policy\Local Policies\User Rights Assignment\Manage Auditing and Security Log policy.-DONE
Thanks.

Whenever I try to prep for a 2013 exchange install I always get:
"earlier versions of the server roles that are installed were detected"
Hi,
That tells us that you are trying to run the prep on your combined DC and Exchange 2010 Server - That will not work. Run it on the Server where you plan to install Exchange 2013.
It is not mandatory to run this before the actuall Exchange install - It will run automatically for you, if it hasn't been done already and if you are logged on with an account with the proper permissions.
Martina Miskovic

Exchange 2013 ECP/OWA Error 503 Service Unavailable

Hi,
Hoping that someone can clarify or assist with an issue relating to Exchange 2013 CU3..
Both roles installed on a single 2012 server, mailboxes created, able to login to ECP/OWA using ht tps://servername.int.domain.com/ecp using the out of the box internally generated SSL certificate.
Virtual directory internal and external settings for all directories were configured to be ht tps://mail.domain.com/owa /ecp /EWS etc and a UCC certificate (containing mail.domain.com, autodiscover.domain.com)from GoDaddy was imported and assigned to
IIS and SMTP, internal DNS records were setup internally and externally for mail.domain.com and full propagated, Outlook Anywhere enabled and configured to mail.domain.com, external access configured for all virtual directories
The issue is that ECP and OWA can only be accessed internally by the full internal server FQDN URL ht tps:// serverame.int.domain.com/ecp whereas it should be accessible at this point by ht tps:// mail.domain.com/ecp
Error received both internal and external when trying ht tps://mail.domain.com / owa / rpc etc is error 503 Service Unavailable
I know that the ECP and OWA sites are up and running as I can login and do anything by internal servername URL but no joy at all using the external (which is to be used for internal clients aswell for seamless access)
The only way it works is by adding a host name to the 2 x 443 bindings in IIS for the front end website and set it to mail.domain.com but this means autodiscover.domain.com internally and externally wont work
Is this normal and required for Exchange 2013 or is there a way to resolve this?
Thanks in advance!

Hi,
I found a article might help you, for you reference:
http://support.microsoft.com/kb/2619402
Generally, this error occurs if the application pool that is associated with the web application doesn't start.
To troubleshoot this issue, follow these steps:
In Event Viewer, view the System log to find errors from the Microsoft-Windows-WAS source. An event is frequently logged in the System log if the application pool fails to start.
If you don't find any relevant events in the System log, search for relevant entries in the HTTPERR log file. The httperr1.log file is located in the following system folder:
c:\windows\system32\logfiles
In the file, search on "503" to locate any relevant information about why the application pool failed. For example, you may see an entry that resembles the following:
2011-12-08 18:26:42 ::1%0 6721 ::1%0 443 HTTP/1.1 GET /owa 503 3 N/A SharePoint+Web+Services+Root
Thanks.
Niko Cheng
TechNet Community Support

Cannot install Windows Exchange 2013 SP1 64x non-checked build

Hello every one.
I have a problem to setup a lab asigment for school.
I have 2 Windows 2012 standard server
1e AD, DNS, IIS
2e Exchange 2013 SP1 64x
i prepared AD and installed al the features needed for AD and the Exchange server.
But when i run the readines check before i install Exchange 2013 i get to following warning
Warning:
A checked build of the operating system is installed. This can cause system instability issues including crashes, hangs, and other performance problems. It's highly recommended
that the operating system be reinstalled with a non-checked build.
For more information, visit: http:// technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.OSCheckedBuild.aspx
I cant find out what to do, thear is no Boot.ini file in Windows server 2012, any one any idea's to solve this problem
Thanks for the help,
Greatings,

Hi,
Agree with Ed. A checked build Windows is used for debug. Before installing Exchange 2013, please make sure that you use a free build. I'm afraid that you need to reinstall the OS.
What's more, you can refer the following screenshot to determine which Windows build is running. Generally, it should be Free build.
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

Migrate to Windows 2012 R2 and Exchange 2013 SP1 using database portability

Hi, I'm planning to migrate from Exchange 2013 SP1 running on Windows 2012 to Exchange 2013 SP1 on Windows 2012 R2.
Is it possible to use database portability to move the databases from the exchange installation on win 2012 to the new installation on Win 2012 R2? This would save a great deal of time not doing the mailbox moves.
I've searched similar cases but couldn't find any, all speak about disaster recovery and database portability but I've found no articles that uses the migration scenario.
Would it be possible to do and if so, what would the steps be? Do I need to delete the database from the source server, move the database files to the new server and mount them and relocate the mailboxes? Or should I dismount the database on the source server,
move them to the new server and mount them and relocate the mailboxes?
Frank.

Hi,
According to your description, I recommend you consider using DAG to achieve your requirement.
The following steps for your reference:
1.Prepare a new server which installed windows 2012 R2 for Exchange 2013 mailbox server.
2.After you deploy Exchange 2013 Mailbox servers, you can create a DAG, add Mailbox servers to the DAG, and then replicate mailbox databases between the DAG members.
3.After replication, you can mount all the databases on the new server.
Hope this helps!
Thanks.
Niko Cheng
TechNet Community Support
This no way a resolution. This won't work at all as Both OS will be different and you can't form the Cluster.
Please Unmark it!
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Outlook 2013 cannot connect to local Exchange 2013 server

Server name EXCHANGE: is Domain controller for (domainname.local), DNS server and Exchange 2013
Has UCC CA cert successfully installed for (exchange.domainname.com)
External Outlook connections, Web Outlook and autodiscover work fine.
local DNS points autodiscover.domain.com & exchange.domainname.com to internal IP
I have used the above configuration many time for Exch2010/Outlook 2010 and it works great.
PROBLEM: Outlook 2013 clients on a local domain member autoconfigure (through autodiscover) but report a certificate error that the names do not match. When I force the acceptance for the cert error the outlook13 account setups with an exchange server
of "BIG LONG GUID"@domainname.com which cannot resolve and outlook fails.
Please help..

Hi ,
I have recently installed the exchnage 2013 as follow
one CAS and Two mail box DAG
so I was facing similier issue outlook clients were not able not see the CAS
so here are the magic solution :
1-created SRV recored for autodiscover same as acbrown2010 done
above in his reply
2-created
A record for autodiscover and the IP same as CAS IP
3-created
an internal Certificate in CAS server "create a new certificate request " and
include all names such CAS , MB's , Autodiscover this step to avoid the warning message during outlook setup because self sign certificates in ex2013 not helping
after that I have tested the outlook and was working fine NO GUID and NO certificates warning

1035 Warning Every 15 Minutes on a Multi-Role Exchange 2013 Server

Hello,
I keep getting a 1035 warning every 15 minutes by Exchange 2013 which states:
Inbound authentication failed with error LogonDenied for Receive connector Client Frontend EXCHANGE-SERVER. The authentication mechanism is Login. The source IP address of the client who tried to authenticate to Microsoft Exchange is [127.0.0.1].
This error is produced by MSExchangeFrontEndTransport.
This server is a multirole server and is the only Exchange Server in the organization.
Thank you for your time.

Hi,
Please open the Queue Viewer tool from the Toolbox node to check if there are any messages stuck in queue. If yes, then this issue occurs if the Exchange server cannot authenticate with the remote Exchange server. Exchange
servers requires authentication to route internal user messages between servers. The issue can be caused by one of the following reasons:
The Exchange server is experiencing Time synchronization issues
The Exchange server is experiencing Service Principal Name (SPN) issues
The required TCP/UDP ports for the Kerberos protocol are blocked by the firewall.
Please follow these steps to solve this issue:
Check the clock on both servers and domain controllers that might be used to authenticate the servers. All clocks should be synchronized to within 5 minutes of one other.
Verify that the
Service Principal Name (SPN) for SMTPSVC is registered correctly on the target server.
Make sure that the SMTP and SMTPSVC entries are added correctly to the machine account by using the
SetSPN tool. For example:
SetSPN -L <ExchangeServerName>
SMTP/<ExchangeServerName>
SMTP/<ExchangeServerName>.example.com
SMTPSVC/<ExchangeServerName>
SMTPSVC/<ExchangeServerName>.example.com
Check for duplicate SPNs by using the SetSPN tool. There should only be one entry of each:
SetSPN -x
Processing entry 0
found 0 group of duplicate SPNs.
Verify that the ports required for Kerberos are enabled.
If the previous steps do not work, you can turn on logging for Kerberos on the Server that is registering the Event 1035 message, which may provide additional information. To do this, follow these steps:
Click Start, click Run, type Regedit, and then click
OK.
Locate the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters
On the Edit menu, point to New, and then click
DWORD Value.
In the details pane, input the new value LogLevel, and then press Enter.
Right-click LogLevel, and then click Modify.
In the Edit DWORD Value dialog box, under Base, click
Decimal.
In the Value data box, type the value 1, and then click
OK.
Close Registry Editor.
Again check the System Event log for any Kerberos errors.
Best Regards.

Migrate from Exchange 2007 to Exchange 2013.

Hi All,
Need some advised here,
I am about to migrate Exchange 2007 with Windows Server 2003 to Exchange 2013 with Windows Server 2012 R2.
Which one should I migrate first? Windows Server or Exchange?
I tried to search it, i am a bit confuse with some of the answer. If someone can give some ideas, it will be great.
Thanks,

I'm not really sure what you are asking here. If you are asking here. I think you need to upgrade your Domain Controllers AND Exchange to 2012R2 and Exchange 2013.
I'm going to assume that they are going to be different servers. I would probably do the Exchange Migration first (assuming that you already at a supported level for Exchange 2013 https://technet.microsoft.com/en-us/library/aa996719%28v=exchg.150%29.aspx)
Also, before you actually make the change to your Domain Functional level, take a look at this blog post.
http://blogs.technet.com/b/exchange/archive/2015/02/13/considering-updating-your-domain-functional-level-from-windows-2003-read-this.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?

i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

Exchange 2013 - physical cores supported?

Afternoon,
Very specific question that I cannot find an answer to
How many physical (not logical / HT) cores will Exchange 2013 utilise? I need to understand if a 20 core Intel V3 chip for example will be efficiently used (all physical cores). My thought is Exchange 2010 had a recommendation of 24 cores on a
combined role server and 2013 would essentially use 'all the physical cores it can get'
Apologies in advance for offending anyone but for clarity I am aware of the 'performance guides and calculations' so please do not link generic guides. Also any response needs to show evidence / reference for the answer to be valid
in the project I am working on.
If there is no public information then that is fine I will work through my clients internal Microsoft contacts
Thanks all
TC
TC-UK

Hi TC,
How many cores Exchange 2013 will utilize, it will depend on the exchange workload.
I recommend you refer to the following article to understand processor requirements in exchange 2013:
Ask the Perf Guy: Sizing Exchange 2013 Deployments
Processor requirements
Once we have our storage requirements figured out, we can move on to thinking about CPU. CPU sizing for the Mailbox role is done in terms of megacycles. A megacycle is a unit of processing work equal to one million CPU cycles. In very simplistic terms, you
could think of a 1 MHz CPU performing a megacycle of work every second. Given the guidance provided below for megacycles required for active and passive users at peak, you can estimate the required processor configuration to meet the demands of an Exchange
workload. Following are our recommendations on the estimated required megacycles for the various user profiles.
Best regards,
Niko Cheng
TechNet Community Support

DNS Requirements in Exchange 2013: Which RR's to create & what do they do?

Similar Messages

Maybe you are looking for