Coldfusion and Exchange 2010 CAS

I have a windows 2008 R2 server. I have the default web site with exchange 2010 client access server installed. When I install cold fusion 9 it breaks outlook web access. If I remove coldfusion it works fine again. If I put in the old applicationhost.config file owa will work again but not coldfusion. After coldfusion I get owa/&reason=0. I tried installing coldfusion first but get the same results. Any ideas?

Ended up splitting the two sites.

Similar Messages

Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence?

Hi Team,
I am in the phase of upgrading Exchange 2010 to 2013, and introduced 4 MBX and 2 CAS of 2013 servers in co-existence.
Only one production mailbox of 2010 moved to 2013. The owa of the mailbox moved to 2013, is working OK internally coz only internally configured, but when I configure outlook using 2010 settings, it got configured but when I open outlook it doesn't
open and throws an error of some "cannot open set of folders".
Is it supported to connect Exchange 2013 Mailbox using Exchange 2010 CAS in Co-existence? because I havnt configured 2013 CAS servers yet.
Kindly share some KB or tip. Any help is appreciated. Thank You.
Muhammad Nadeem Ahmed Sr System Support Engineer Premier Systems (Pvt) Ltd T. +9221-2429051 Ext-226 F. +9221-2428777 M. +92300-8262627 Web. www.premier.com.pk

I'll change Adam's wording slightly - you *MUST* install a CAS 13 server into every site where there is a MBX 13 server.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
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.

Exchange 2007 and exchange 2010 Federation

Hi all I am trying to federate between Three organisations
org A exchange 2007 with exchange 2010 cas
org B exchange 2010.
org C exchange 2010.
I cannot share my calendar from org A to Org B
I can share Org B to Org A and Org B to Org C.
when I try from Org A to Org B or Org C
When I try to share free/busy fro the exchange 2007 with exchange 2010 cas. The user gets an error
"calendar sharing is not available with the following entries because of permission settings on your network."
-availabilityaddressspace. Autodiscover works TXT works. I have added a user from Org B as a contact in exchange.
The exchange 2010 server is not the CAS server for the exchange environment and I is not a proxy for exchange 2007. Is this where I am failing ?
Heeeelp

Hi Nigel,
How is the impact, just one user or all users, Outlook or OWA?
If just one user, it seems like an issue on the Outlook Client side.
Please trying to re-create new profile to fresh the caches.
Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
Found a similar thread for your reference:
Calendar Sharing not available error message
http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Catalyst SLB - Exchange 2010 CAS RPC

Hi.
We're currently testing out SLB for load balancing a pair of Exchange 2010 CAS servers. The config seems straightforward enough for single port services like 'Outlook Anywhere' or 'Outlook Web Access' (all on https).
Does anyone have real life experience with getting straight MAPI Outlook load balancing to work? According to Microsoft, there's only 3 ports to be concerned with - endpoint mapper, rpc.clientaccess, and address.book. I've got the latter two set for static across both of these servers, and have 3 appropriate vservers in place pointing to the serverfarm, but a capture shows the process getting hung up on tcp135. It's as if whatever server the endpoint request is landing on doesn't know what to do with the request.
Thanks in advance for any replies.

Hello Jay!
Take a look at this doc:
http://www.cisco.com/en/US/docs/solutions/Verticals/mstdcmsftex.html#wp609677
RPC requires source ip sticky in order to operate correctly through a loadbalancer. In the doc, they also walk through doing RPC over http/https - however, I have seen configurations where ACE is not L5-L7 that use RPC on port 135 as a L4 rule with sticky and it appears to work ok.
Regards,
Chris Higgins

Best practice SSL End-to-End in Exchange 2010 CAS loadbalancing

Hi,
I was wondering if there is a best practice for deploying SSL End-to-End in Exchange 2010 CAS loadbalancing.
We have ACE modules A5(1.1) and ANM 5.1(0), although there seems to be a template available in ANM it doesn't work. It throws a error when deploying, i believe the template is corrupt.
As I am undersome pressure to deploy this asap I am looking for a sample config. I found one for SSL offloading, but I need one for End-to-End SSL.
Thanks in advance,
Dion

Hi Dion,
You can open up a case with TAC to have that template reviewed and confirm if the problem is at the ACE or ANM side.
In the meantime here is a nice example for End-To-End SSL that can help you to get that working:
http://www.cisco.com/en/US/products/hw/modules/ps2706/products_configuration_example09186a00809c6f37.shtml
For CAS load balancing there's nothing special other than opening the right ports, I'd advise you to get SSL working first and take it from there, if any problem comes up you can post it here and we'll give you a hand.
HTH
Pablo

Exchange 2013 and Exchange 2010 coexistense

We have a and exchange 2010 organization with SP3 on most servers except for one 2010 CAS server that still requires SP1 for the purpose of legacy application compatibility. Can we introduce exchange 2013 in the org or will the setup detect
that there is an exchange 2010 server still with SP1 and fails to continue?

Hi,
For Exchange 2013 coexistence with Exchange 2010, the mininum version of Exchange server is Exchange 2010 SP3 on all Exchange 2010 servers in the organization. For more information about it, please refer to the Coexistence of Exchange 2013 and earlier versions
of Exchange server part in the article below:
http://technet.microsoft.com/en-us/library/jj898583(v=exchg.150).aspx
Personal suggestion, please upgrade your legacy application to the latest version which is supported with Exchange 2010 SP3 or higher Exchange version.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 EAC will not run with Exchange 2010 CAS\HT servers shut down.

Hi Folks,
A little background - We have just migrated all our user mailboxes and public folders to Office 365 using a hybrid configuration. Now that the migration is essentially finished, I'd like to decommission our on-prem Exchange infrastructure and remove the
hybrid config. We are using dirsync with password sync to replicate our AD to the cloud.
I've read that even if you remove your hybrid configuration, it's a good idea to keep one on-prem Exchange server around so you can edit Exchange attribs (such as email addresses) in a supported manner, rather than using ASDI edit, etc.
To this end, I installed a single Exchange 2013 CA\MBX server. After installation, the EAC worked fine, and I was able to view our on-prem users, groups, etc. Last week, I shut down our two Exchange 2010 CAS\HT servers as a test to see if anything broke
prior to decommissioning them (these were the hybrid servers as well). After doing so, the Exchange 2013 EAC no longer works for some reason, and behaves in a very bizarre fashion. About once every 20 times or so, it will actually start and run. The other
times, it just has you enter your creds, then generates an HTTP 500 internal server error after entering them. It seems to make no difference if you attempt to access it by the fqdn, hostname, or localhost right on the box itself. Same behavior on Chrome or
IE.
Today as a test, I started up one of the 2010 CAS servers and lo and behold, the 2013 EAC ran without difficulty again. Any idea why this might be so? Thanks for any help,
Ian

Hi,
From your description, I recommend you use the following URL to check if you can access EAC. I see it works for several people about this issue.
https://<Exchange 2013 CAS FQDN>/ecp?ExchClientVer=15
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2013 CAS functionality in coexistence with Exchange 2010 CAS

Hi,
I am planning to migrate Exchange 2010 to Exchange 2013 for 15000 users. We have a pool of 6 CAS 2010 servers added in a single CAS array. So my question is if we introduce a new CAS 2013 server in same site then will it affect CAS traffic anyway ? If we
point our HLB to all CAS servers including CAS 2010 and CAS 2013 so will the CAS 2010 servers wil take traffic or is it only CAS 2013 servers who will take traffic. We will be putting same URLs in CAS 2013 same as CAS 2010. I have read lot of MS articles and
all say that CAS 2013 should be enabled for CAS traffic and it will proxy request to CAS 2010. But I am not sure if we will face any CAS traffic issue whenever we will introduce CAS 2013 servers in same site and traffic will be pointed to CAS 2010 and CAS
2013 both. Is it possible to add CAS 2013 in Exchange 2010 CAS array ? Please guide. Thanks in advance.

For mailbox that exist on Exchange 2010, EXCH2013 CAS will proxy the request to an Exchange 2010 Client Access servers that exists within the mailbox’s local site.
For mailboxes that exist on Exchange 2013, EXCH2013 CAS will proxy the request to the Exchange 2013 Mailbox server that is hosting the active copy of the user’s mailbox which will generate the Autodiscover response.
-->Is it possible to add CAS 2013 in Exchange 2010 CAS array ?
No. CAS Array is no longer exits in Exchange 2013. But concept of a single namespace for Outlook connectivity remains. Please check this and this. In
your case you dont need to worry as you have a HLB in place it will do the job
When a new exchange2013 is deployed Outlook Anywhere has been enabled on all Client Access servers within the infrastructure and the mail.contoso.com and autodiscover.contoso.com namespaces have been moved to resolve to Exchange 2013 Client Access server
infrastructure. In your case it is pointed to both as you have a load balancer in place but the same URL should be configured in exch2013
Make sure you have exchange2010-SP3 minimum as it is the prerequisite requirement for upgarding EXCh2010 to 2013.
Please check the exchange server deployment assistant
tool for moving mailboxes
After moving a mailbox check the URLs. Configure autodiscover,EWS,OAB URLs on exchange2013. Please check this as
well for checking URLs.
I hope you know MAPI/RPC (RPC over TCP) traffic is now replaced with RPC over HTTP/s instead in exch2013.
Thanks
MAS
Please don't forget to mark an answer if it answers your question or mark as helpful if it helps

Problems with a shared calendar using Outlook 2007 and Exchange 2010

Hello all,
We are having a problem with sharing a calendar using Outlook 2007 and Exchange 2010.
I will start with some background. I have just started my position with this company. I have been working with networks for awhile at the small business level. I have not had much production experience with exchange. There is only myself and my supervisor
who has inherited a midsized network which was built by five previous techs that are no longer with the company. Of course, the previous techs did not leave much documentation, so the original hows and whys for our system setup has been lost.
One of the managers has a calendar she shares with some of our users. I believe this calendar has been in use since sometime in 2006. A mailbox was created to hold this calendar to keep it separate from the managers calendar. I am not sure what version
of exchange they were using at that time, but I assume there was one or two migrations of it getting to its current state on our exchange 2010 server. At some point it was observed that the other workers she was sharing with were not able to access it correctly.
I am not fully sure what the original problem was (possibly some people not being able to see or connect to the calendar), but it was decided to give everyone who needed access to this calendar full access permissions through exchange. Correct me if I
am wrong, but I believe that gave everyone connected the ability to do anything with the calendar. Of course the manager was not happy about that. This is where I started working on the problem.
I removed everyone, except the manager who wants to control the calendar, from having "Full Access Permissions". This did have the effect of making some people just able to see the calendar and not make changes. Though there were others that were
able to connect to the calendar who I thought would not be able to. The manager that originally created the calendar did try to manage access to it through the Outlook interface, though it currently does not seem to be fully in effect.
So, to get to the point of what we are trying to do, is there a way to get the original manager back into control of the calendar though Outlook? It would be preferred to be able to keep the history of what they tracked of this calendar, so starting a new
one would be something we would rather avoid. After that, getting all of the users that need to connect to the calendar reconnected with the correct access permissions and making sure they are all synchronized.
I realize this is a big mess, and your help would be greatly appreciated.

Hi Nigel,
How is the impact, just one user or all users, Outlook or OWA?
If just one user, it seems like an issue on the Outlook Client side.
Please trying to re-create new profile to fresh the caches.
Please runing Outlook under safe mode to avoid some AVs, add-ins and firewall.
Found a similar thread for your reference:
Calendar Sharing not available error message
http://social.technet.microsoft.com/Forums/exchange/en-US/d9b33281-d7bb-4608-8025-16fb26643d0d/calendar-sharing-not-available-error-message?forum=exchangesvrclientslegacy
Hope it is helpful
Thanks
Mavis
Mavis Huang
TechNet Community Support

Outlook 2010 and Exchange 2010 SP3

Hello,
we are planning to upgrade from Exchange 2010 sp1 to SP3, most of client PCs has Windows XP sp3 and Oultook 2010 with VSTO addins working with mapi properties.
I need to know if there are any known issues between this client environment and Exchange 2010 SP3 ??
thanks a lot,
Mauricio.
Mauricio

Windows XP is not supported in any scenario, so yes, I'd call that a known issue.
Mike Crowley | MVP
My Blog --
Planet Technologies

CallManager 7.01 and Exchange 2010 UM

We want to integrate CallManager 7.01 and Exchange 2010 UM. The plan is to build two Exchange 2010 UM servers. Who would be resonsible for load balancing (messanging) between the two Exchange 2010 UM servers? CallManager or Exchange? Does anyone know if there is any documentation on this?

I would guess you just make a SIP trunk to both UM servers. From here you can make a circular Route Group which would load balance the calls accross the UM's..
So I guess the answer is call manager!
HTH,
Chad

Help needed with buggy Outlook 2013 and Exchange 2010 trashing profiles

Hi All,
I have a customer who has eschewed MOLP and buys all their Office OEM from Dell. So as a result they are starting to have more and more office 2013 be deployed. They have a SBS 2011 server with Exchange 2010 and it is patched to the latest
rollups and service packs. (SP3, RU2) Their Outlook 2010 and earlier clients are just peachy on this. But the Outlook 2013 clients are having problems.
What is going on is that periodically I'll get a complaint from a user that their Outlook 2013 is randomly crashing. In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default
and going back into Outlook 2013 and letting it rebuild the cached data on the PC. This seems to happen a few times a month with random users on the network.
I told the customer it was probably people not logging out of Outlook 2013 at night and their machines being power spiked but I think that's highly unlikely since it doesen't happen to the Outlook 2010 clients.
I don't know if any Microsoft developers read this but if you do, please take it back to your bug database. Any other suggestions would be appreciated (other than scotch Outlook 2013 - while I'd appreciate that, my customer wouldn't)

In all cases the fix is going into the Outlook Profiles, creating a new profile, then setting the new profile as the default and going back into Outlook 2013 and letting it rebuild the cached data on the PC.
The Outlook 2013 crash problem would be fix after you re-create a new profile and re-sync the data from Exchange, right?
When we meet the same problem in next time, I suggest we run the Outlook Product Stability Diagnostic tool to isolate known causes of crashes in Outlook. The Outlook Product Stability Diagnostic also creates a diagnostic report outlining the data it collected
and recommendations on possible steps you can take to reduce or eliminate Outlook stability issues.
Please click the following link to run the Outlook Product Stability Diagnostic tool in the Microsoft Fix it Center Pro portal:
Outlook Product Stability Diagnostic:
https://wc.ficp.support.microsoft.com/SelfHelp?knowledgebaseArticleFilter=2764035
Other troubleshoot steps for Outlook 2013, please refer to the link below.
Let me know the result.
http://support.microsoft.com/kb/2632425/en-us
Tony Chen
TechNet Community Support

CFExchange and Exchange 2010

Anyone have a solution to or a work around for the issue with cfexchange not talking to Exchange 2010? We are migrating to 2010 within our company and I have several applications reading Exchange 2002 and 2007 calendars.
Ryan

CFExchange in CF server 9 or older will not talk with Exchange 2010 at all, it is promissed to be fixed in CF 10.
As a solution you can use the EWS API. Read the stuff below. I hope my hint is helpfull to you.


<cfobject type="Java" class="microsoft.exchange.webservices.data.ExchangeService" name="service">
<cfset service.init()>


<cfobject type="Java" class="microsoft.exchange.webservices.data.WebCredentials" name="credentials">

<cfset credentials.init("test.account","test.password", "yourdomain.com")>

<cfset service.setCredentials(credentials) />


<cfobject type="Java" class="java.net.URI" name="uri">

<cfset uri.init("https://mail.yourdomain.com/ews/Exchange.asmx")>

<cfset service.setUrl(uri) />



<cfobject type="Java" action="create" class="microsoft.exchange.webservices.data.EmailMessage" name="message">
<cfset message = message.init(service) />
<cfset message.SetSubject("EWSTest")>
<cfset messageBody = CreateObject("java", "microsoft.exchange.webservices.data.MessageBody")>
<cfset messageBody.init("My EWS test message")>
<cfset message.SetBody( messageBody )>
<cfset message.ToRecipients.Add("[email protected]") >
<cfoutput>
    #message.SendAndSaveCopy()#
</cfoutput>

Outlook client in different subnet unable to connect to Exchange 2010 CAS using Windows 2008 R2 NLB multicast mode

Hi all,
need urgent assistance on the following issue
this is my Exchange 2010 setup
2 x CAS/Hub servers with HP network teaming, and load balanced using Windows NLB multicast mode. There are 2 VIPs on the NLB, one for outlook anywhere, one for autodiscover
2 DNS records were created for the 2 VIPs
Clients use Outlook Anywhere (HTTPS) to connect to the CAS servers from external segment via a Palo Alto firewall, which also acts as a layer 3 router
static arp was set on the Palo Alto firewall, with both virtual MACs pointing to the primary virtual MAC used by the NLB.
Observations
1. within same segment - no issue accessing Exchange servers, even when one CAS node is offline
2. external segment (via firewall)
a. when both nodes are up
outlook client able to connect to Exchange CAS VIP on 443, but will disconnect after around 30 seconds. Client will retry and the pattern will repeat
Exchange CAS RPC logs shows client connections and disconnections to the outlook anywhere VIP address
Firewall logs shows allowed traffic from client to the VIPs
unable to complete profile creation
b. with only CAS2 (CAS1 stopped/deleted from NLB cluster)
no issues accessing Exchange servers, creating profiles etc
c. with only CAS1
same behaviour as (a)
reinstalled NLB, but doesn't resolve
deleted CAS1 from NLB cluster, and re-add. issue remain
Q1. is teaming supported? Teaming is currently set to automatic mode, instead of specified Fault Tolerant
Q2. are there additional settings we need to set or verify on the Palo Alto firewall, since the issue only happen to external segment? Thanks!

Yes - I've been scarred with this for many years :(
If it is just CAS 1 that is causing issues, then focus in on that. The support statement for Win 2008 R2 is that NLB is still a 3rd party component and support may ask for it to be disabled.
http://support.microsoft.com/kb/278431
Does CAS1 and CAS2 have the same NICs (firmware as well), driver, teaming software, and teaming config?
I also want to ask what the network team did for configuring the switch ports on the servers? This will vary from vendor to vendor - did they do the same config on both?
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
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.
Thanks Rhoderick, issue still persists
can you also help clarify what you meant by "configuring the switch ports on the servers"?
thanks again

Whats the best way to go about load balancing Exchange 2010 CAS

My server guys want to LB the Exchange 2010 client access servers, this will be the 7th Context on my Ace 4710.
see table for ports that are used
Port
Usage
25
smtp
80
http various
110
POP3 clients
135
RPC end point mapper
143
imap4 clients
443
SSL various
993
secure imap 4 clients
995
secure pop3 clients
6001
rpc related outlook anywhere
6002
rpc related outlook anywhere
6003
rpc related outlook anywhere
60200
rpc CAS
60201
exchange address book service
whats the best way of going about this?
do I just LB the IP addresses of the Servers and ignore the ports?
do i have to do anything special for ports 993 and 995 secure imap and pop?
I am sure there are more questions I shold be asking!

OK
so If I have a single serverfarm with all services do I filter on the virtual
address something like below?
class-map match-any EXCH_vip
match virtual-address 172.16.93.2 tcp eq 25
match virtual-address 172.16.93.2 tcp eq 80
match virtual-address 172.16.93.2 tcp eq 110
match virtual-address 172.16.93.2 tcp eq 135
match virtual-address 172.16.93.2 tcp eq 143
match virtual-address 172.16.93.2 tcp eq 443
match virtual-address 172.16.93.2 tcp eq 993
match virtual-address 172.16.93.2 tcp eq 995
match virtual-address 172.16.93.2 tcp eq 6001
match virtual-address 172.16.93.2 tcp eq 6002
match virtual-address 172.16.93.2 tcp eq 6003
match virtual-address 172.16.93.2 tcp eq 60200
match virtual-address 172.16.93.2 tcp eq 60201

Coldfusion and Exchange 2010 CAS

Similar Messages

Maybe you are looking for