Exchange, IIS and WNLB issues

Hello everyone. I have a strange IIS/Exchange issue that I am stuggling to solve and could use some assistance with.
Our site setup:
2 * Exchange 2010 CAS servers running in a CAS array with WNLB on subnet A
2 * Exchange 2010 CAS servers running in a CAS array with WNLB on subnet B
Multiple Exchange 2010 MBX servers in both sites running as DAG members.
All servers running 2010 SP3 Update Rollup 6
Some of the problems we having:
All servers from subnet A can access the default website on subnet A CAS servers - ie http:/subnetacasserver (which redirects them onto the OWA page)
All servers from subnet A can also access the default website on subnet B CAS servers
All servers from subnet B can access the default website on subnet B CAS servers.
A selection of servers on subnet B are consistently unable to access the subnet A CAS servers from web browsers. They are able to ping, telnet on port 80 and in general have no other issues other than accessing via web browser. I have tried restarts, IIS
resets, checking permissions, resetting IE without any luck.
When I take subnet A CAS server 1 out of NLB, all servers on all sites are able to access the root website on both subnet A CAS servers without issue.
When I take subnet A CAS server 2 out of NLB, it appears that no subnet B servers can access either of the subnet A CAS server root websites
This issue has been going on for over a week and despite trying everything I can think of I am still unable to solve the issue. I’d greatly appreciate any ideas or advice.

Hi,
I am not quite sure about the question, let me confirm with the followings:
Suppose:
CASArrary1 in site 1 includes: CAS1 and CAS2
CASArrary2 in site 2 includes: CAS3 and CAS4
The issue happens when the users in site 2 access the default web site on CAS1. If there are any misunderstanding, please ket me know. Do you mean the user accss Https://CAS1.domain.com but it failed? What's the
error code? Why you access the default web site instead of it's virtual directory, such as OWA, ECP..
Some important points in this issue:
1. CASArray are designed for load balance MAPI traffic. It doesnot work for HTTP.
2. Check whether the proxy and redirection settings are configured properly.
Thanks,
Simon Wu
TechNet Community Support

Similar Messages

Exchange 2007 and iCal issue

Today I set up my MacBook Pro to my work email. We run Exchange 2007. My mail works great. My contacts also works great. For some reason iCal does not work. I get the following error:
"iCal needs a valid email address to connect to the Exchange account "mike (at) worktankseattle (dot) com".
The email address "mike (at) worktankseattle (dot) com" isn't a valid address for your Exchange account. Enter the email address for your Exchange account, and then click OK. "
mike (at) worktankseattle (dot) com is my email. It is valid. This same email works for ical and contacts. Why does it not work with iCal? Any ideas?
Thanks!

I was having this problem as well, but other users in my company were not (Mail and Address Book synced fine, but iCal would not - kept stating that I did not have a valid e-mail address). So, I looked through the Exchange 2007 Management Console on the server, and tried to find inconsistencies between my e-mail account and the users who had no problem with iCal.
It turned out that, for some unknown reason, a check box on my e-mail account ("Hide from Exchange address lists") was checked on mine but not the others. Once I unchecked that option, iCal synced up fine.
So, I would suggest that you speak to your Exchange Admin person and ask them to check your specific E-mail Account Properties Page and have them make sure that this box is not checked. I hope that this helps some of you...

Gmail/Exchange email and calendar syncing issues

I have wiped my email accounts several times and entered in my data in the various ways as shown through the forums but my email accounts do no sync properly whether it is manual or active synced.
I read my emails in my gmail and my Microsoft exchange account and will delete or file them away but then when I check my accounts on my desktop, they are not synced as I've done so on my phone. I've also noticed that my calendars are not synced correctly either.
Could someone help me understand why and how these issues can be fixed? I'm in meetings for most of the day so I rely on my phone to keep me mobile. Was this a bad purchase?!?!

Hi JadeyMU,
How do you have your Microsoft Exchange account configured on your BlackBerry Z10? Are you using ActiveSync, BlackBerry Enterprise Server (BES), IMAP or POP?
Thanks.
-CptS
Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

Droid Razr Maxx/Issues with Exchange Sync and Texting

I have a Droid Razr Maxx. Since the KitKat update to 4.4 in May 2014, my Exchange email account will not sync. My Comcast account does. If I power cycle the phone, it will sync the Exchange account for a short time until I receive the following error message: 'couldn't open connection to server due to sec..." When I touch the error message, it just goes away. If there is more of the error message, I'm unable to see it. I have removed the Exchange account and added it back in three times. My IT department indicates they have not made any changes to the security levels, but have fielded several questions from other Android users with the KitKat update. My text messaging service also stopped. I've been reviewing all forums and tried different things, but to no avail. I went to the Verizon store, who just said that there have been 'lots' of complaints about KitKat and that I should buy a different phone. This $200+ phone is only 7 months old. Please help!!

After deleting and adding my Corporate account, visiting the local Verizon store several times, visiting my IT department, and now wiping the phone and re installing all software, the Corporate email still only syncs when I power cycle the phone. We are a BYOD company which means every other phone works with the Exchange account. My phone also worked up until the KitKat update in May 2014. The only recommendation I have received from Verizon is to replace my 8 month old Motorola Razr Maxx with a entirely different phone at full price. The tech I spoke with at Verizon made the statement that she has avoided updating to KitKat given all the customer issues she has had to deal with.
I'm in a technology field and understand when glitches occur, but also expect functionality issues to be addressed. I've been with both Verizon and Motorola for a long time, but very doubtful I will continue this relationship when contract time is up for renewal. I'm carrying my iPad around to get the Corporate emails and the Razr Maxx has been relegated to just being a very expensive phone.

Issues with Exchange Account and Q10

Well, I hate to be writing this, but I'm hoping that there might be someone out there that can help get past some first day issues I am experiencing.
The background: I have a long history with legacy BlackBerry devices, and almost as much history with iOS devices. My most recent phone was an iPhone 4S, and I make extensive use of iCloud to keep my iMacs, iPhone, and iPad connected in real-time. The setup worked. It wasn't perfect, but it worked. However, because I used to have a BlackBerry device (most recent the 9930) and because I don't use the iPhone for more than e-mail, iMessage, and phone calls (generally speaking), I decided to give the newest BlackBerry device a shot. So I bought a Q10.
At this point I feel compelled to say that the hardware is everything I had hoped it to be. It's solid, has a good weight, and appears to be made very well. I have no complaints with the hardware, including the keyboard (a big selling factor for me), so I won't really get into the hardware as the issues I am experiencing all have to do with the OS. Let me also say that I am very familiar with the iCloud integration issues (missing Contact photos and disabled Calendar sync), so I'm not voicing a complaint over those issues in this thread.
I have connected my Exchange account. I used to have everything in Exchange before I moved my entire computing world over to Apple, and now I keep Exchange around for e-mail. Therefore, I have no contacts, no tasks, no notes, very limited calendar entries, and a massive amount of e-mail on the Exchange server. However, to test everything out, I have added a single contact record so I can see it show up on the phone and be able to test two-way sync between the Q10 and Exchange. And here is where the first issues crop up. It looks like Exchange connects and then disconnects at random. For example, if I open my Contacts on the phone, I see the one contact (called John Doe). Then, as the phone is sitting there with the screen on, the contact will disappear and I will see a "Start adding contact to your contact list" notice on the screen. Then, after a short period of time, the single contact will return. It is important to note that the entire time this is happening, the All Contacts option is selected in the list so that all available contacts are shown. Additionally, I have SIM card contacts turned off, but if I alter the selection in the view list (All Contacts, Favorites, etc.), the SIM contacts will re-appear when I return to the All Contacts view. At the same time, even though I have turned off SIM Contacts in the settings, the setting has reverted to show SIM Contacts. If I turn off the setting again, SIM Contacts still show up. Possibly related: I can't delete contacts on the SIM card, no matter how many times I try, and it now it seems that I can't get SIM Contacts to go away in the Contacts app.
Likewise, Exchange seems to connect and disconnect from Calendar. I go to the calendar and move day by day to June 15th. I see an entry that I know is from Exchange (I have no other connected calendars at this time), and it is in blue. I change the calendar color to green and the entry changes color, as expected. However, if I jump back to today and then scroll day by day to get to June 15th again, the calendar entry is missing. After a few seconds, the entry re-appears, but it is, once again, in blue. The setting has reverted itself, and it seems like Exchange is completely disconnecting and automatically reconnecting to the phone like I am setting it up again for the first time. Very odd. As I'm typing this, I just saw something odd. I swiped to wake up the phone, and the active frames screen was the visible screen. The calendar app is still running (since I left it running, minimized, when the phone went to sleep) and the date shown in the active card was Jan 1, not Jun 8. Why? The date (and time) on the phone is correct and is set automatically by the cellular system.
Nevertheless, looking at BlackBerry Hub, I see only two e-mails in my Inbox from Exchange, even though I have roughly a dozen in my Inbox. The rest are filed in sub-folders. And bam! Just like that... I get the "Add Accounts" screen while looking at the Hub. In other words, as I was typing this, I first saw two Exchange e-mails and then, out of nowhere, the e-mails disappear and I see the "Add Accounts" screen as if no account has been connected.
So... first question: Is anyone else experiencing this issue? This is very strange, and very frustrating. Second: could this be related to the large amount of e-mails I have stored on Exchange, some of which have large attachments? I selected "Forever" as the sync history length. I have my concerns, however, if this is related to loading historical e-mails onto the phone (in other words, the first sync with Exchange) because there is no reason that I can understand that the phone would blank out as if no account was connected at all. I can understand lag and stuttering while the history is syncing, but not a complete disconnect and reconnect. Considering all of the issues with the one and only contact record disappearing, the calendar entry for Jun 15th disappearing and then reappearing with the wrong calendar color, and e-mail in my Inbox incomplete (two of a dozen e-mails) and ultimately disappearing, I feel like this OS just has some real, significant issues.
Full disclosure: I do want iCloud to work and am a fan of Apple products, but the lack of full iCloud sync support is not a big enough issue for me to want to send back this phone and/or see it fail so miserably. I will happily move my info from iCloud into Exchange, Google, and/or set up a new Exchange account for personal use (Office 365) because I am not wedded to iCloud per se. But, I won't go through that trouble if I can't even get my first account to work properly. It should also be noted that I do have a basic Google account (non-paid) and I had previously attempted to connect to it. However, I was experiencing the exact same issues with contacts disappearing, e-mail disappearing, etc. So I deleted that account. Truth be told, I deleted the Exchange account as well, and then re-connected to Exchange only to test one account at a time. Unfortunately, even with Exchange only, I am seeing very strange and frustrating behavior as described above.
Help... please. I want this to work but the frustration I am feeling is growing worse by the hour.
Model: SQN100-2
OS Release: 10.1.0.2011
OS Version: 10.1.0.2038
Build ID: 525050
Ian

To follow-up with this issue:
I ended up performing a security wipe on my device. The security wipe finished, and I was about to reconnect with Exchange when I decided to visit our host's web site to see if they had any articles covering the issues I was experiencing. While they didn't have anything specific, I did find a step-by-step guide to connecting a BB10 device to Exchange... and right there at the end, it said "Do NOT enable memo sync."
I contacted support, and the rep told me that OS 10 has an issue with memo sync and it can cause all sorts of unpredictable behavior. Now, whether or not this is accurate I can say this: So far, the device is not disconnecting and reconnecting like it was before. Problem is, is this a result of not enabling memo sync, or is this a result of the security wipe?
I may have overlooked it, but I don't recall reading anything about that anywhere else. I'm tempted to try re-enabling the memo sync to see if everything blows up again. At least that way I can see for myself if the memo sync is a real issue. Of course, perhaps it's an issue with SherWeb (our host) specifically. Hm...
Anyway, for those that were interested, and for those that may come along in the future with a similar situation, the strange behavior that I first reported is no longer happening. I just don't know if it was a result of a security wipe or a result of not enabling memo sync with Exchange.
Ian

Outlook Anywhere Loosing connection : Outlook Event id 26 and Exchange IIS HTTPERR Log : Connection_Dropped_List_Full at the same time

Hi,
I have a Windows 2008R2 Updated / Exchange 2010 SP3 Rollup 7 (Role CAS,HUB,MBX) with only external users connection : ActiveSync, EWS, OWA, Outlook Anywhere.
4 processors and 24Go of memory are allocated to the Exchange server VM (VMWare).
Netscaller is used as reverse proxy in DMZ.
There is around 500 users connecting with Outlook Anywhere to Exchange. Users are using Outlook 2010 or 2013 with last updates and cache mode enabled (owner mailbox and delegations). Users are location all around the world (around 50 sites). So no users
is domain integrated.
Users are complaining about disconnection, and Outlook freeze (Outlook is not responding). This happened at any point of time during the day, and for different kind of actions (Outlook is just open, Try to press Send button, try to press Transfer button).
The freeze happened randomly for users. I have seen the problem, and Outlook sometimes freeze during few seconds, sometimes during 5 minutes without any reason. (no file copy, no action asked...)
I noticed that freeze are matching with the Outlook event id 26 on the workstation (Connection to the Microsoft Exchange Server has been lost. Outlook will restore the connection when possible). Also, at the same time, I can see around 200 lines in
the IIS HTTPERR Log (Exchange Server : C:\Windows\System32\LogFiles\HTTPERR) the following lines:
2014-11-20 10:39:43 NETSCALLERIP PORT EXCHANGEIP 443 HTTP/1.1 RPC_OUT_DATA /rpc/rpcproxy.dll?EXCHANGEFQDN:6004 - 1 Connection_Dropped_List_Full MSExchangeOutlookAnyWhere
2014-11-20 10:39:43 NETSCALLERIP PORT EXCHANGEIP 443 HTTP/1.1 RPC_OUT_DATA /rpc/rpcproxy.dll?EXCHANGEFQDN:6001 - 1 Connection_Dropped_List_Full MSExchangeOutlookAnyWhere
What has been already checked :
Check IOPS: seems to be normal
Check Processor consumption: seems to be normal
Netscaller TimeOut = 8h
Bandwidth where the server is hosted : more than enough
Bandwidth of client internet connection : Traffic do not increase when the problem happen
Firewall TimeOut : seems to be ok
Firewall Protocol Filter : seem to be ok
Workstation MTU : Ok : ping -l -f 1472 = Ok, so best MTU = 1500 (1472+28)
Outlook Profile : Clean Up OST, sync of all folders, download address book.
wireshark on workstation : nothing seems to be wrong but difficult to analyse, so I maybe missed something.
Configuration change on Exchange :
HKLM\Software\Policies\Microsoft\Windows NT\RPC\MinimumConnectionTimeout = 120
Disable throttling Policy
Adsiedit, change Max Memory alloc for ESE : msExchESEParamCacheSizeMax = 327680 (around 10GB) msExchESEParamCacheSizeMin = 131072 (around 4GB
Adsiedit, change Min Memory alloc for ESE : msExchESEParamCacheSizeMin = 131072 (around 4GB)
Host file : add hostname and FQDN of Exchange Server
Disable IPV6 : HKLM\System\CurrentControlSet\services\TCPIP6\Parameters\DisabledComponents = HEX 0xffffffff
IIS : system.applicationHost : webLimits : minBytesPerSecond = 0
Create dedicated IIS AppPool MSExchangeOutlookAnyWhere for /RPC and /RPCWithCert
AppPool MSExchangeOutlookAnyWhere : Regular Time Interval (minutes) : 0
AppPool MSExchangeOutlookAnyWhere : Queue Length : 20000 (Should be the solution but not working)
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\MaxUserPort = 65534
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime : 300000
HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\MaxConcurrentAPI = 150
IIS machine.config : <system.web> : requestQueueLimit="65535"
Microsoft.Exchange.RpcClientAccess.Service.exe.config <add key=”LoggingTag” value=”ConnectDisconnect, Logon, Failures, ApplicationData, Warnings, Throttling”/>
Uninstall All agents (except Backup Agent)
Uninstall Antivirus
Will be done tonight :
Exchange and DCs : HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\MaxConcurrentAPI = 100
Exchange IIS : Increase AppPool MSExchangeOutlookAnyWhere Queue Length to 40000
Exchange : decrease HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime to 60000
You're welcome if you have any idea.
Thanks.
Jo.

Hi,
Thanks for your answer. Here are my comments :
1. Disable IPv6 then restart your Exchange server
Already done since the install of Exchange.
2. Confirm if there is any NLB device in your environment, please remove NLB firm client server
There is only one Exchange server in the Org. So no NLB installed on the server (NLB is used on the Netscaller used as a reverse proxy). In Addition, the article apply for Windows 2008, or the server is installed with Windows 2008 R2.
3. If there is a proxy server configured in IE, please uncheck it
I guess you are talking on the client side. There is no proxy on the client side, Outlook Anywhere connect directly to the internet.
4. Collect more error logs in Event Viewer in Exchange and collect the IIS logs in
folder “c:\inetpub\logs\logfiles\W3SVC1”
the error I reported in the description is from IIS, and always appear when end users report a problem. In W3SVC1 file, there is also errors, but those one appear even if Outlook clients are working fine. So I cannot isolate any specific
error. The most common from W3SVC1 log are :
2014-11-25 08:02:17 EXCHANGEIP POST /autodiscover/autodiscover.xml - 443 - NETSCALLERIP Microsoft+Office/15.0+(Windows+NT+6.1;+Microsoft+Outlook+15.0.4667;+Pro)
401 1 2148074254 0
2014-11-25 08:02:17 EXCHANGEIP POST /EWS/Exchange.asmx - 443 - NETSCALLERIP Mac_OS_X/10.9.5+(13F34)+CalendarAgent/176.2
401 1 2148074254 0
2014-11-25 08:02:18 EXCHANGEIP POST /EWS/Exchange.asmx - 443 - NETSCALLERIP Microsoft+Office/14.0+(Windows+NT+6.1;+Microsoft+Outlook+14.0.7128;+Pro)
401 1 2148074254 0
Regards,
Jo.

Local domain, IIS Hosting and SMTP issues.

I have a local domain on Windows server 2012 with dns, dhcp, iis and smtp. (Yes, I am aware of the dangers of these combinations) it is for learning purposes only and not my main pc.
My local domain is willow.run and I am hosting a website, the domain for that is machinerylubricant.com I have IIS 8 installed (6.0 also for smtp)
My original issue was getting IIS to send an email to localhost through a php script for a contact form hosted on the website. I finally got to where it appears to be sending the contact form info to my drop folder but I ahve no idea how to get that .EML
file to actually forward to gmail account or even outlook on my computer/server.
In the email file (.eml in drop folder) it says "To: *******@gmail.com" as it is supposed to but that email is not making it to the specified gmail account. Also no error messages in the ph logs or the log files for smtp. How would I go about setting
up a email program to work on the lan with the acual www domain name I own?
I am learning everything at once basically, windows server, coding, protocols etc. Please bare with me.

Rather than answer your specific question, how about I give you the best way to achieve what you're looking for?
For inbound messages, you want to use the "aliasdetourhost" keyword. Check the documentation for how this is set up.
For outbound messages, you want to use the "alternate conversion channel"
When used together, this will achieve what you're looking for, without the looping that you have generated....
The alternate conversion channel was written up here:
http://ims.balius.com/resources/downloads/files/AlternateConversion.pdf

Exchange 2010 and iphone calendar sync issues

Hey,
I know this question has been asked plenty of times before and just need a straight resolution. We have just migrated our environment to Exchange 2010 and the major issue is that when an event is created in Outlook 2011 it is not always showing up on their iphone and also vis versa. Is their a resolution to this problem so I can implement it in an emergency change. Thank you for all your help!

Here let me explain the scenario again any user who logs in to exchange from outlook working fine password not expired and he has iphone active sync working no issues , now while all devices are working when he starts his ipad after a week or so when he
opens his email on ipad it prompts the password on ipad and same time on iPhone , he does not want to enter the password and wants a technical justification , I told the user something to do with Exchange 2010 sp2 and ios 7 ,but that is invalid justification
. if you have any other valid justification please let me know. or a solution to this issue. user wants to login without any password prompt while the password is saved in device and not expired , is there any feature in Exchange 2010 sp2 that would recognize
how many days device has not logged it and would force to enter the password.

Issue with Exchange Anywhere and TMG

Hello
Users work with Outlook 2010 and connect with Exchange Anywhere to my Exchange Server and get an error: They cant connect to the exchange server, some can't even access Outlook.
9 out of 14 clients can access Outlook, the last 5 who are trying to connect cant.
I have a TMG which reports the following at the same timestamp :
Failed Connection Attempt
Log Type: Webproxy (Reverse)
Status: 64 The specified network name is no longer available.
Rule: Exchange Anywhere (443), CC178 ->exht01
Source: Extern (IP)
Destination: Local Host (IP)
Request: RPC_IN_DATA http://autodiscover.domain.com/rpc/rpcproxy.dll?exht01.domain.com:6001
Filter information: Req ID: 03e0eeb2; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=yes, logged off=no, client type=unknown, user activity=yes
Protocol: https
User: domain.com\[email protected]
Log Type: Webproxy (Reverse)
Status: 200 OK
Rule: Exchange Anywhere (443), CC178 ->exht01
Source: Extern (IP)
Destination: Local Host (IP)
Request: RPC_OUT_DATA http://autodiscover.domain.com/rpc/rpcproxy.dll?exht01.domain.com:6001
Filter information: Req ID: 03e0eeb4; Compression: client=No, server=No, compress rate=0% decompress rate=0% ; FBA cookie: exists=no, valid=no, updated=yes, logged off=no, client type=unknown, user activity=yes
Protocol: https
user: domain\[email protected]
OWA works
I set a correct external URL for VD
So i thought maybe Exchange has a restriction because there are 14 clients who are trying to connect with the same user on Exchange.
I set a new Throttling Policy and assigned it to the specific user, still didnt work. My settings in Outlook should be ok because some other users can connect!
Other companies also connect with Exchange Anywhere, they can connect with different users (Mailboxes) so connection should be all right.
Do you guys have any ideas? Thanks

Hi,
Firstly, I’d like to explain, we can block Outlook Anywhere for specific users in Exchange 2010:
Get-CASMailbox -Identity <MailboxIdParameter> -mapiblockoutlookrpchttp $true
Thus, we can check the property of the 5 problematic users.
Additionally, the error 64 is very generic and there can be multiple reasons which would translate to this error code. The most common one is when the backend server is performing a dirty TCP connection reset.
For more information, you can refer to the following information:
http://blogs.technet.com/b/isablog/archive/2013/05/29/error-64-the-specified-network-name-is-no-longer-available-while-accessing-a-https-site-through-isa-2006.aspx
Best regards,
Angela Shi
TechNet Community Support

Single name space in between Exchange 2010 and 2013

Hi,
In my current environment I have 2 Exchange 2010 servers with DAG no CAS NLB. I installed Exchange 2013 with 2 CAS with WNLB and 2 Mailboxes with DAG. The main requirement is to configure Single name space to access in between Exchange 2010 and Exchange
2013. On Exchange 2010 DAG there is a URL using is owa.domain.com and I also configured in Exchange 2013 all the virtual directories with this name owa.domain.com but having an issue that when I open explorer and use the owa.domain.com URL the user on Exchange
2013 gets their mailbox but user on Exchange 2010 gets error HTTP 403 blank page.
I observed that in Exchange Organization settings CAS settings one server OWA, ECP etc shows their internal external URL but the other server unable to open the OWA, ECP URL and give error message that "An IIS directory entry
couldn't be created. The error message is Access is denied. HResult = -2147024891"
Please guide how to resolve this issue and use the same name URL in Exchange 2010 and Exchange 2013
Thanks,

Hi,
See the below brief:
User will connect to mail.contoso.com as his namespace endpoint. CAS2013 in Site1 will authenticate the user, do a service discovery, and determine that the mailbox version is 2010 and is located within the local AD site. CAS2013 will proxy the
request to an Exchange 2010 Client Access server which will retrieve the necessary data from the Exchange 2010 Mailbox server
Go through the full blog for better understanding of the redirection.
Client Connectivity with Exchange 2013
Hope you have changed your DNS records to direct connections only to your new Exchange 2013 server. You'll move the host names (for example, mail.contoso.com) users have been using to connect to Outlook Web Access, Autodiscover, and so on, from your
Exchange 2010 server to your Exchange 2013 server. When an Exchange 2010 user tries to open their mailbox, the Exchange 2013 server will proxy their request and communicate with the Exchange 2010 server on their behalf.
Configuring DNS includes the following:
Change the primary host names, such as mail.contoso.com, autodiscover.contoso.com, and owa.contoso.com (if used) to point to the external, publically-accessible, IP address of the Exchange 2013 Client Access server with your public DNS provider.
Change the primary host names, such as mail.contoso.com (or internal.contoso.com if you're using different internal host names) and owa.contoso.com (if used) to point to the internal machine name of the Exchange 2013 Client Access server on your internal
DNS servers.
NOTE- Go through the Exchange Deployemnt Assitant - Configure DNS Records section
Regards,
Satyajit
Please“Vote As Helpful”
if you find my contribution useful or “MarkAs Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Introduction of New OAB Architecture in Exchange 2013 and Some General Troubleshooting methods

Exchange 2013 is different from previous versions of Exchange server on architecture, some of the old features have been changed. In this FAQ, I will demonstrate the changes on OAB and list a common issue for your reference.
[Agenda]
1. Differences between Exchange 2007/2010 OAB and Exchange 2013 OAB
a. Generation
b. Distribution
c. Download
2. Common issue and troubleshooting
3. More information
[Difference between Exchange 2007/2010 and Exchange 2013 on OAB]
As we know, OAB in Exchange 2007/2010 has 3 points, OAB files generated from MBX server, distributed to CAS server and downloaded to Outlook client. However in Exchange 2013, these 3 points have a little different from previous servers. For example, the OAB
Distribution process doesn’t depend on Microsoft Exchange File Distribution service anymore. Now let me show you the changes of OAB in Exchange 2013.
[OAB Generation]
====================
Exchange 2007/2010:
1. OAB generation server is the specific MBX server which has –server property.
2. If MBX01 is down, OAB generation will be affected.
3. Previous Server using Microsoft Exchange System Attendant service for OAB generation.
4. OAB generation is a scheduled process. By default, OAB files generated at 5:00AM every day.
5. The OAB files which generated from MBX server are located in following path:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
Exchange 2013:
1. OAB generation server is the MBX server that hosts a special type of arbitration mailbox, called organization mailbox. Thus, the same OAB files could be generated from multiple
MBX servers.
2. If one of the MBX server down, other MBX server still have the ability to generate the specific OAB files.
3. Exchange 2013 server using OABGeneratorAssistant for OAB Generation.
4. OAB generation is a throttled process. It depend on the Server workload.
5. The OAB files which generated from MBX server are located in following path:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
[OAB Distribution]
====================
Exchange 2007/2010:
Previous Servers use Microsoft Exchange File Distribution service to distribute OAB files from MBX server to CAS server. The distributed oab files stored in CAS server.
Exchange 2013:
The OAB files doesn’t distributed to CAS server. The OAB files only stored in MBX server.
[OAB Download]
====================
Exchange 2007/2010:
If Autodiscover works fine, Outlook should use OAB URL to get the OAB files and download it.
If Autodiscvoer doesn’t work, authenticated users can also get the OAB from the CAS server local disk.
Exchange 2013:
Microsoft Exchange File Distribution service has been removed from Exchange 2013 and the OAB files stored in MBX server. CAS server will proxy all OAB download requests to the appropriate MBX server.
Outlook also use Autodiscover to get the OAB URL and download it.
[Common issue and Troubleshooting]
Issue: Outlook doesn’t download OAB files automatically. When I try to manually download OAB, get this error: Task xxx reported error (0x80190194): The operation failed.
Troubleshooting:
1. First, please run following command to check the information of OAB Generation Server.
Get-Mailbox -Arbitration | where {$_.PersistedCapabilities -like “*OAB*”} | ft Name, Servername, Database
Example result as below:
2. Please make sure the authentication settings and URLs are set properly.
3. Try to verify whether the OAB files generated from MBX server successfully. Path as below:
C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\OAB\GUID folder
4. If all of the settings above set correctly, please try to check Autodiscover. Run “Test E-mail Autoconfiguration” to check whether there is anything abnormal on OAB. If has, please search the error code on MS official documents.
5. If this issue is related to local cache, please try to delete the OAB caches from local PC and re-download OAB for testing. Path as below:
C:\Users\Administrator.CU1(different)\AppData\Local\Microsoft\Outlook\Offline Address Books
[More information]
http://blogs.technet.com/b/exchange/archive/2012/10/26/oab-in-exchange-server-2013.aspx
http://blogs.technet.com/b/exchange/archive/2013/01/14/managing-oab-in-exchange-server-2013.aspx
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi Techy,
According to your description, I am still not quite sure about your environment. Could you please provide more information about it, such as:
1. How many Exchange servers in your coexistence environment? One Exchange 2010 with all roles and one Exchange 2013 with all roles? Or several Exchange 2010 and multiple Exchange 2013?
2. Are there two sites in your environment? What’s the Exchange deployment in different sites?
3. Please confirm if both Exchange 2010 and Exchange 2013 are Internet-facing.
Additionally, if you are using different namespaces for different services for internal access and external accessing, we need to include all service namespaces in your certificate with IIS service. Personal suggestion, we can follow ED Crowley’s suggestion
to use split-brain DNS in your environment and only use the same namespace for Exchange service URLs.
The following article described the details about how to configure different namespace for Exchange services by using Load Balance in Exchange 2013:
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/introducing-load-balancing-exchange-server-2013-part2.html
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 Mail Receiving Issues

Hi everybody,
Yesterday I configured a new DC and Exchange on Hyper-V (Server 2012 and Exchange 2013)
All functions and rolls are configured and installed but i am having issues receiving external e-mails.
Almost all of the external mails are being deliverd a half hour to a hour after being sent.
To start of on the first level.
I got a Siemens Fiber modem with an external address connected to the WAN of my Draytek 2995 router.
Alle the needed ports are forwarded to the Draytek (80,443,25,1723).
The Draytek DHCP function is set to off.
192.168.168.2 (DC) -> 80 (HTTP IIS)
192.168.168.2 (DC) -> 1723 (RRAS)
192.168.168.3 (Exchange) -> 25 (SMTP)
192.168.168.3 (Exchange) -> 443 (SSL)
My Draytek router is connected through LAN1 to a HP switch (unmanaged).
The physical server has 3 NIC's, all of these are connected to the HP Switch
I Disabled Hyper-V Queuing on the NIC's because this causes an issue with slow network connections.
The network has been configured as following.
I configured the Server 2012 R2 on the hardware(physical server) with only the Hyper-V roll.
NIC1is setup for the physical server,
IP Address: 192.168.168.1
Subnet: 255.255.255.0
Gateway: 192.168.168.254 (Draytek address)
DNS: 192.168.168.254 (Draytek address)
The Server software firewall has been set to a private network through the local security policy.
I have setup 2 VM's through the Hyper-V roll.
The first VM is the Server 2012 R2 Domain controller.
For this VM I created a virtual switch connected to my second NIC(2).
I unchecked the box where my host can communicate with the NIC(2).
The DC has been configured as following:
Hostname: SERVER
IP Address: 192.168.168.2
Subnet: 255.255.255.0
Gateway: 192.168.168.254
DNS: 127.0.0.1
I can ping to all the adresses from this server (internal and external).
The server has been promoted to domain controller with the following rolls.
ActiveDirectory, Certificate Autohority, DHCP, DNS, RRAS, RDP.
Alle these rolls have been set and working. (all have been tested)
DHCP has all options configured (scope, router-192.168.168.254, dns-192.168.168.2)
A DNS simple and recursive test work fine.
I did no configuration on the DNS after the DC PROMO.
So i created users in the AD.
After that I created a second VM, this one is used for the Exchange.
I setup a second virtual switch connected to NIC3 and installed Server 2012 R2 with the following config.
Hostname: SERVER
IP Address: 192.168.168.3
Subnet: 255.255.255.0
Gateway: 192.168.168.254
DNS: 192.168.168.2 (pointing to the DC)
I joined this server to the domain, everything is working fine.
Both servers have internet and network.
Running portscans on 1723 and 80 all work like a charm.
No its time to install Exchange.
I ran all the prerequisits and PowerShell commands (IAcceptLicense. etc.)
Installed de needed API and filters.
Installed Frameworks 3.5 on both servers.
And the Exchange installation was succesfull.
CU3 is also installed.
I configured the send connector, accepted domains etc.
Created all needed certificates (self signed)
Did a portscan on 433 and 25 and they work.
All the hosting records are set mail.domain.nl etc. and MX records.
I created inboxes for the users and was able to connect them to the users in the Active Directory on the DC without any problems.
Connecting through the internet to OWA works perfect and i can login with users.
Sending e-mail internally works perfect, the messages are being deliverd in an instant.
Sending e-mail externally also works perfect, i receive mails in a few seconds on a person email address.
But when i reply or send e-mail to my new Exchange it can take up to hours to receive the mails!
I did online SMTP checks and e-mail checks, the all come out like it should.
One message from MX TOOLBOX on the SMTP:
SMTP Transaction Time
8.408 seconds - Not good! on Transaction Time
I have nog other receive connectors setup, just the standard connectors.
So i got into the Exchange ECP and under "server" i setup the DNS to listen to 192.168.168.2 (DC).
I've read that when this is set to all ip addresses it can cause mail delay, but no luck.
I ran the best practices analyzer and get about 23 errors and 20 warnings.
A lot of services are unhealt like the "ExchangeTransport).
I have no idea what is causing the issues and read almost every forum.
Does anyone have a clue what is going on?
Did i miss something, is there a misconfiguration?
Best regards,
Tim

The mailserver did not receive any e-mails in this timespan, it was not an issue with the connector to the user mailboxes.
The internal e-mail also works flawless.
The entire Exchange server just not received this mail in time.
I sent an e-mail from my personal accout with the option in my outlook to receive a delivery-reply.
I got the reply as soon as the mail was deliverd, this took about a half hour to a hour.
After you asked me about the firewall, i got a hunch..
It had to be on the incomming connection, so i checked every single firewall on the network and disabled them.
Still the same problem...
But there was still one ethernet device that could have a firewall, the internet modem!
This ATM modem receives multiple external IP's from the ISP, so I figured there was no firewall on this device. (Just like all the cable modems that are deliverd in our area by Ziggo(ISP).
But I was wrong, there was a firewall enabled on the modem!
All the ports in the modem had been forwarded but somehow the modem-firewall filtered the traffic,
creating the issue on the incomming e-mail.
I disabled the firewall and all the external e-mails are being received in an instant!
Re-enabled all the software firewalls on the servers and re-enabled the malware filter through powershell, after these steps I did another test, and everything still works like a charm!
Many thanks for your help Kjartan!

My ActiveSync and OMA issues

I had a couple of ActiveSync issues that I was able to solve by going to the server URL that is used to access the exchange server. My exchange server uses SSL so the URL is https://office.domain.com/oma.
The first error I had was because I promoted this server to a Domain Controller after ASP.net was installed, see http://support.microsoft.com/kb/818486.
The second problem was the OMA virtual directory was configured to use .net 2.0 but it needs to be .net 1.1. That is easy to change in IIS manager.
The third issue was because I am using SSL and OMA needs to access the /Exchange virtual directory without SSL, see http://support.microsoft.com/kb/817379/EN-US/
Once I made those changes the https://office.domain.com/oma worked and ActiveSync on my iphone worked as well.
If /oma is working for you but ActiveSync on the iphone is not, I am not sure what else could be the issue.
Regards,
Justin

Ok I am pulling my hair out.
I've set and reset up my IIS and it's accepting my Exchange settings and NOT syncing.
Anyone who has access to their server, could you compare your settings to mine? Please.
Microsoft Windows Server 2003
for Small Business Server
Service Pack 2
-IIS Manager
-Server
-Web Sites
*-Default Web Site
(Properties - Directory Security)
Authentication & access control
Enable anonymous access - OFF
Integrated Windows Authentication- OFF
Basic Authentication- ON
Default Domain- \
Server Communications:
Require secure channel (SSL): ON
Regire 128-bit encryption: ON
Ignore Client Certificates: ON
*-Exchange
(Properties - Directory Security)
Authentication & access control
Enable anonymous access - OFF
Integrated Windows Authentication- ON
Basic Authentication- ON
Default Domain- \
Server Communications:
Require secure channel (SSL): ON
Regire 128-bit encryption: ON
Ignore Client Certificates: ON
*-exchange-oma
(Properties - Directory Security)
Authentication & access control
Enable anonymous access - OFF
Integrated Windows Authentication- ON
Basic Authentication- ON
Default Domain- \
Server Communications:
Require secure channel (SSL): OFF
Regire 128-bit encryption: OFF
Ignore Client Certificates: ON
*-Microsoft-Server-Active-Sync
(Properties - Directory Security)
Authentication & access control
Enable anonymous access - OFF
Integrated Windows Authentication- OFF
Basic Authentication- ON
Default Domain- (BLANK)
Server Communications:
Require secure channel (SSL): ON
Regire 128-bit encryption: ON
Ignore Client Certificates: ON
*-OMA
(Properties - Directory Security)
Authentication & access control
Enable anonymous access - OFF
Integrated Windows Authentication- OFF
Basic Authentication- ON
Default Domain- (BLANK)
Server Communications:
Require secure channel (SSL): ON
Regire 128-bit encryption: ON
Ignore Client Certificates: ON
Any help will be much appreciated!

Free/Busy not working Exchange 2007 and 2013 co-existence

Hi,
I'm migrating our Exchange 2007 environment to Exchange 2013. Now I am in a co-existence environment where all the mailboxes except some test-users resides on Exchange 2007. Between Users on the same Exchange MBX Server athe FREE/BUSY Information sharing
works correctly, but between Exchange 2007 and 2013 it's not working.
I verified my settings and also the EWS virtual directory on 2007 CAS Servers using Get-WebServicesVirtualDirectory.
The internal and the external URLs are set to https://legacy.mydomain.com/....
What am I missing?
Thanks & Kind Regards,
Jürgen

Hi,
According to your description, I understand that the free/busy information between Exchange 2007 and Exchange 2013 is not available for your coexistence environment. To narrow down the issue, please check the following points:
1. Does the issue happen to all users or specific users?
2. Although a user on Exchange 2013 can't get free/busy information from a user on Exchange 2007, please confirm whether Exchange 2007 user can get free/busy information from Exchange 2013 users.
3. Close Outlook and only access user mailbox from OWA to check whether the issue persists. For Outlook client,
create a new Outlook profile
to have a try.
4. Please make sure the virtual directories settings are configured correctly in both Exchange 2013 and Exchange 2007.
Virtual directories settings in Exchange 2007:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-3-step-by-step-exchange-2007-to-2013-migration.aspx
Certificate and Virtual directories settings in Exchange 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-2-step-by-step-exchange-2007-to-2013-migration.aspx
5. Restart IIS service in Exchange server by running iisreset /noforce from a command prompt window.
If possible, please run Test E-mail AutoConfiguration in Outlook to check whether the autodiscover service can get correct Availability service URL in the results. If there is any event logs, please collect some for further analysis.
Regards,
Winnie Liang
TechNet Community Support

Mail For Exchange - Interesting and Challenging Pr...

Hi all,
We've been running Mail For Exchange in our organisation for around 6 months now without a problem. And now we have a problem I cannot seem to father out. Searched forums, checked and double checked things and no further, so I post on here hoping one of you guru's can assist!
We have 5 offices - all of which have their own Exchange Server. Users in each office all use MfE. Our biggest office (Glasgow) has 3 Exchange Servers due to the size - so that is 8 Exchange Servers in total.
We use a Front End Exchange Server at our data centre (set up with a Verisign SSL Certificate) and backend Exchange Servers at each of our sites.
So far so good :-)
All of a sudden, one of the Glasgow Servers has stopped allowing Mobile Phones to receive their e-mail. The other two Glasgow servers are fine and dandy, as are the rest of the offices - so the FE/BE setup must be fine.
Concentrating now on the server that is not working, I have went through every Permission setting on IIS and cross checked it with some articles on the internet. Everything fine. I have even cross checked the settings with working Exchange Servers in our organisation - again everything fine.
If I look on the IIS logs on the Front End server, I get an error 500.
If I look on the logs on the Mobile Phone, I get HTTP error code = 500 / Internal Server Error 500.
Now the interesting part.
Following diagnostics on here and other sites, the first thing i do is browse to http://servername/oma on the Phone's browser. I put in my credentials and get in fine. So that would mean no certificate errors and the path to the BE mailbox works fine.
I can browse to affected users mailboxes on the PC side using OMA and Webmail - so again no issues with comms between FE and BE.
The issue is just MfE connecting to one server in our organisation.
I've been working on this for 2 weeks now, and I have to admit i am struggling what to look at next.
I've ripped out the Exchange bits on IIS, re-started the System Attendant Service and reconfigured the permissions. Nothing.
I've reset the Nokia and installed MfE 2.7. Same - nothing.
As i say, it is just one server affected. Everything else is fine. To make things worse, the server affected is the one which my mailbox is on, along with some of the senior directors.
Does anyone have any ideas what so ever? I'm sitting here with my fingers crossed.
Regards,
Colin.

seems like there are no Exchange server administrators in the forum, retro... sorry. I would love to help, though, but I'm just another MfE user.

Exchange, IIS and WNLB issues

Similar Messages

Maybe you are looking for