New Exchange 2010 installation. HUB and CAS on two seperate servers, need two certificates?

Title says it all. I have already completed the Exchange server installation with 2010 R1 on 2008 R2 sp1 servers in HyperV
I have two physical servers in one rack. HVHost1 one holds EXCHHUB and EXCHMB1 HVHOST2 holds EXCHCAS and EXCHMB2
do I have to generate and request two seperate SAN certificates one for the CAS and one for the HUB? or will one certificate do the trick?
If I can use one certificate, do i need to do anything special to apply it to both servers or just let the wizard do its thing?
Thanks,

Make sure you are selecting the correct server in EMC when installing the Cert.
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.

Similar Messages

Exchange 2010, UCC SSL, and the "new" CA/BROWSER Forum not issuing for .local

I don't know how many people have run into this yet, but the CA/BROSWER Forum, the "standards" authority for SSL issuing, has mandated that CA's can no longer issue a certificate using a FQDN "intranet" name for new or renewal SSL certificates effective
Nov 1, 2012. i.e. the Microsoft standard of mydomain.local will no longer be accepted as a SAN on a UCC for Exchange 2010. I've looked thru the KBs and Social forums, but haven't really found any guidance on how to solve this. I'm presuming
that the certs will have to be split and the "external" domain name of server.mydomain.net will just become a single server SSL, and the internal name of server.mydomain.local will become a Self-Signed certificate. With the increasing prevalence of OA
and ActiveSync devices, is there any baseline guidance yet on how to make this happen without completely fouling up production servers and killing access to the user community?

On the same topic, though likely different environment...
Against recommended deployment, I have a number of clients running all their services on one box. Windows Server 2008, Active Directoy, DNS, Exchange 2010 ...and so on. These servers all have .local addresses, which means of course that the SAN
certificates have .local addresses as one of the SANs.
I've read alot online about this issue, and am trying to find the most cost effective solution to switch numerous production servers running this configuration.
The best solution I've come up with so far is...
1. Virtual AD with new external domain, 2. Migrate Exchange CAS to this domain, 3. Reconfigure network through the box.
Obviously these steps will contain alot more details, but this is just the outline atm. At best, I see me having to take a second box with me to each location to perform these steps, and I can't see it happening without disruption to the work flow
of employees.
Thankfully, all of these businesses are relatively smal...under 25 employees. Still, I'd like to find the smoothest transition solution possible.
Any suggestions would be greatly appreciated!
Regards

Exchange 2010 server (Mail,HUB and CAS) installation in new site.

We are planned to install Exchange 2010 servers(MAIL,HUB and CAS) server in new Active director site in existing exchange organization.
Kindly share best practice link for exchange server installation in new site.

The best practice for installing into a new Active Directory site is the same as installing into a new organization, except you don't need to prepare the organization or domains (unless you are also installing into a new domain that hasn't been prepared).
Install the CAS then hub, then mailbox roles, or install a multi-role server, then define your CAS Array name and IP address, and set your CAS behind a load balancer (if needed). Add your external certificate to both the CAS and the load balancer (and the
hub if you use TLS for mail transfer), and you should be golden. Also, if you intend to proxy your CAS connections, here's a link that may help:
https://technet.microsoft.com/en-us/library/bb310763.aspx?f=255&MSPPError=-2147217396
For completeness, here's a thread on the msexchange.org forums that specifically mentions adding Exchange into a second site:
http://forums.msexchange.org/New_Exchange_2010_at_another_Site/m_1800557445/tm.htm

Redundant Hub and CAS roles for exchange server

Hello ,
currently we have 2 mailbox servers , 1 DAG server and 1 HUB,CAS server ( hub and cas roles in same server )
i am looking to have a backup server incase the hub CAS server goes down .. or to have a redundant server for HUBCAS incase if it goes down the other one will go up and the users will use the second one automatically
how can i achieve that ?
appreciated your help

Hello,
If you use exchange 2010 server, I recommend you deploy multiple CAS servers as member of CAS array.
As your requirement, you need to deploy CAS NLB, the failover will occurs automatically.
Here is an article for your reference.
http://technet.microsoft.com/en-us/library/ff625247(v=exchg.141).aspx
Cara Chen
TechNet Community Support

Exchange 2010 management tools and others

Win2k8 domain, Exchange 2010 servers
We want to move to Win8.1 but we, the admins, are preventing it because our tools like the Exchange 2010 Management tool doesn't work with Win8.0 so we're stuck with Win7.
I've googled around and most suggestion never worked.
Does Microsoft have any plans at all to have Exchange 2010 management tools and other tools we use to manage our domain work with Win8.1?

Hi Rino,
Thanks for your sharing and efforts put on this issue.
This will benefit others who encounter the similar scenario as yours.
Happy holiday~
Kate Li
TechNet Community Support

Real-world experience with Exchange 2010 SP3 RU5+ and Powershell 4?

The support-ability matrix for Exchange (http://technet.microsoft.com/en-us/library/ff728623(v=exchg.150).aspx) says Exchange
2010 SP3 RU5+ and Powershell 4 are compatible. But, there is very little actual discussion about how well that works.
I use Powershell extensively for mission critical and somewhat complex processes, with Exchange 2010 on 2008 R2 and AD access/reads/updates.
Can I get a summary of the caveats and benefits from someone who has actually done this in a
real-world/production scenario (more than one server, managing from a separate non-Exchange server), and who has scripting experience with this configuration?
Also, how has this affected EMC operations?
As always thank you in advance!

I believe the matrix states that its supported to install Exchange into an environment where __ version of WMF is present. Exchange 2010, launched from a Win 2012 server, reports version 2.0 when you call $host. For example, calling the ActiveDirectory
module from EMS on an Win 2012 server (ps 3.0) fails.
I'll double check the extent of this scenario and get back to you.
Mike Crowley | MVP
My Blog --
Planet Technologies

Exchange 2010 Installation error

Hi All,
I'm at my over 10th installation of Exchange 2010 server and it is the first time I have to admit that I can't resolve the issue i'm faced off ;-)
Here is some info about my issue. The installation is on a Windows 2008 R2 (Virtual) sit on a Windows 2012 R2 server with Hyper-V and it is a fresh vanilla installation that I'm trying to install for the 3rd time. Each attempts returned me the same error
at the same steps.
The Exchange installation is a typical, common, CAS, Mailbox and HUB installation without any particular configuration in the setup.
Here is the error I get:
Client Access Role
Failed
Error:
The following error was generated when "$error.Clear();
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.".
An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSMessageEncoderSoap11Element'
could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.1.218.11&e=ms.exch.err.Ex88D115&l=0&cl=cp
I Googled every single point of failure indication and I didn't get reliable fix or work around.
I used ADSI edit to see if the IIS folders are there and yes they are except the EWS one which is mentioned in
the error message. Forest, Domain and AD have been prepared as it should, DCDIAG doesn't return any problem and the security has been set
properly for Legacy migration with an Exchange 2003 organisation.
Here is the par of the Exchange setup log where it stopped:
[03-06-2014 16:15:26.0488] [1] Processing component 'Client Access Services Configuration' (Configuring Client Access services.).
[03-06-2014 16:15:26.0488] [1] Executing:
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
[03-06-2014 16:15:26.0503] [2] Active Directory session settings for 'New-WebServicesVirtualDirectory' are: View Entire Forest: 'True', Configuration Domain Controller: 'powerhouse.parasuco.com', Preferred Global Catalog: 'powerhouse.parasuco.com', Preferred
Domain Controllers: '{ powerhouse.parasuco.com }'
[03-06-2014 16:15:26.0503] [2] Beginning processing new-WebServicesVirtualDirectory -WindowsAuthentication:'True' -WSSecurityAuthentication:'True' -InternalNLBBypassUrl:'https://mtl1ex01.parasuco.com/ews/exchange.asmx' -DomainController:'powerhouse.parasuco.com'
-Force:'True' -GzipLevel:'High'
[03-06-2014 16:15:26.0636] [2] Searching objects "MTL1EX01.parasuco.com" of type "Server" under the root "$null".
[03-06-2014 16:15:26.0649] [2] Previous operation run on domain controller 'powerhouse.parasuco.com'.
[03-06-2014 16:15:26.0650] [2] Processing object "MTL1EX01\EWS".
[03-06-2014 16:15:29.0130] [2] [ERROR] Unexpected Error
[03-06-2014 16:15:29.0130] [2] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0131] [2] [ERROR] The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension
'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
[03-06-2014 16:15:29.0138] [2] Ending processing new-WebServicesVirtualDirectory
[03-06-2014 16:15:29.0139] [1] The following 1 error(s) occurred during task execution:
[03-06-2014 16:15:29.0139] [1] 0. ErrorRecord: An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0139] [1] 0. ErrorRecord: System.InvalidOperationException: An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'. ---> System.Configuration.ConfigurationErrorsException:
The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension,
Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension 'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config
line 2373)
at System.Configuration.BaseConfigurationRecord.EvaluateOne(String[] keys, SectionInput input, Boolean isTrusted, FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult)
at System.Configuration.BaseConfigurationRecord.Evaluate(FactoryRecord factoryRecord, SectionRecord sectionRecord, Object parentResult, Boolean getLkg, Boolean getRuntimeObject, Object& result, Object& resultRuntimeObject)
at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
at System.Configuration.Configuration.GetSection(String sectionName)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.WebConfigReflectionHelper.CommitToWebConfig(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task, String path, String site, String server, Boolean isTokenCheckingSpecified,
Boolean isSpnListSpecified)
at Microsoft.Exchange.Management.SystemConfigurationTasks.ExtendedProtection.CommitToMetabase(ExchangeVirtualDirectory exchangeVirtualDirectory, Task task)
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessMetabase()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewWebServicesVirtualDirectory.InternalProcessMetabase()
at Microsoft.Exchange.Management.SystemConfigurationTasks.NewExchangeVirtualDirectory`1.InternalProcessRecord()
--- End of inner exception stack trace ---
[03-06-2014 16:15:29.0139] [1] [ERROR] The following error was generated when "$error.Clear();
$urlToUse = "https://" + $RoleFqdnOrName + "/ews/exchange.asmx";
new-WebServicesVirtualDirectory -windowsAuthentication:$true -WSSecurityAuthentication:$true -InternalNLBBypassUrl $urlToUse -DomainController $RoleDomainController -Force -GzipLevel High;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.".
[03-06-2014 16:15:29.0139] [1] [ERROR] An error occurred while creating the IIS virtual directory 'IIS://MTL1EX01.parasuco.com/W3SVC/1/ROOT/EWS' on 'MTL1EX01'.
[03-06-2014 16:15:29.0139] [1] [ERROR] The type 'Microsoft.Exchange.Services.Wcf.MessageEncoderWithXmlDeclarationSoap11BindingElementExtension, Microsoft.Exchange.Services, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' registered for extension
'EWSMessageEncoderSoap11Element' could not be loaded. (C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\exchweb\EWS\web.config line 2373)
[03-06-2014 16:15:29.0140] [1] [ERROR-REFERENCE] Id=ServicesComponent___ca981854eaa74c1ca684178d9ea52fff Component=EXCHANGE14:\Current\Release\Shared\Datacenter\Setup
[03-06-2014 16:15:29.0140] [1] Setup is stopping now because of one or more critical errors.
I appreciate the time anybody would spend to help me with my issue

Well, here is a status of what I did.
After running the Cleanup tool, I ran the Exchange server setup again without re installing anything and I got the same error and I have found .NET issue in the application's event logs (Event ID 1111 .NET runtime optimization service with this error code:
- Error code 0x80029c4a =
Cannot Load Library); . Why that? because there still Windows Kernel Mode and User Mode .NET 1.11.
So I uninstalled them and ran the exchange setup again. It failed a the same point but nothing in the application log that time.
Going further to see if it is a .NET issue, I re installed from Windows Update the .NET
1.11 packages (Which are required prior to reinstall .NET 4.5) restart the server + re install version 4.5.1 and ran the setup again without the two available security patches for .NET 4.5.1. Guess what, same issue. No .NET error and no specific or related
log except the Exchange setup installation error.
From the MSExchange Management log, i have found that 2 errors are logged each time I run the setup:
Cmdlet failed. Cmdlet Install-ClientAccessRole, parameters {DomainController=powerhouse.parasuco.com, UpdatesDir=E:\Updates, ExternalCASServerDomain=webmail.parasuco.com}.
Cmdlet failed. Cmdlet New-WebServicesVirtualDirectory, parameters {WindowsAuthentication=True, WSSecurityAuthentication=True, InternalNLBBypassUrl=https://mtl1ex01.parasuco.com/ews/exchange.asmx, DomainController=powerhouse.parasuco.com, Force=True, GzipLevel=High}.
So it seems to me to be a IIS and security issue. Again, All other IIS virtual folders have been created without any problem. Why does the setup can't create the EWS one???

Upgrading from Exchange 2003 Bridgehead servers to Exchange 2010 Transport Hub servers for routing SMTP only

Our company moved from on-premises Exchange 2003 to Office365 and only have 4 Exchange 2003 servers on-prem that we use for Routing email from application servers to Office365. We need to migrate these servers to Exchange 2010 then to Exchange 2013 and
only route email only. Is it possible to upgrade to Exchange 2010 by installing the transport Hub & Mailbox server options only? Our OAB and EWS services come from the CAS servers located on Office365 so we should not need a CAS server to set up Transport
rules or route mail would we? Any assistance with this would be greatly appreciated! - Thanks, DWB
Dave

Since it is not internet facing we will not have to worry about configuring an Internet Domain Name when installing the first server, correct? in my planning I was going to
install the Exchange 2010 CAS/Mailbox/Transport Hub roles on one server, then upgrade it to Exchange 2013. Once this is completed I'll then install the 2 mailbox role servers in one Datacenter, and 3 more in our DRP DC. If something happens to the
primary Datacenter I would want it to fail over to the other site. For this I would have to install another CAS/mailbox server in the secondary DC. Would this plan sound about right? Since we moved to Office365 in 2010 I have not had a chance to deal with
actual servers except for the Exchange 2003 servers we still have on-premises. Each of these are located in 4 Regional offices along with single Windows 2008 R2 servers using only the IIS SMTP service for routing mail from on-prem application servers
and print/scanners which email back to the users. The plan is to move to a routing system which will provide both MTA and redundancy if one has an issue.
Dave

Error Code 8224 Ldifde Exchange 2010 installation failure

Hi, here is a problem I have been bashing my head with for about a week. I am transitioning to Exchange 2010 from 2003. I have two DC's running Windows Server 2003 Sp2, one of which is the Exchange 2003 server. I have just brought online a windows 2008R2
member server, which I am attempting to install exchange 2010 on. I get the following error message during installation.
Organization Preparation
Failed
Error:
The following error was generated when "$error.Clear(); install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema1.ldf")" was run: "There was an error while running 'ldifde.exe' to
import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema1.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\administrator.CFN\AppData\Local\Temp\2\ldif.err'".
There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema1.ldf'. The error code is: 8224. More details can be found in the error file: 'C:\Users\administrator.CFN\AppData\Local\Temp\2\ldif.err'
Elapsed Time: 00:00:22
And from the ldif.err:
The connection cannot be established
The error code is 8224
Now I have checked dns, all is good. I can resolve the DC without issue.
I have done dcdiag and netdiag and passes all tests. I have even written a hosts file, all this to no avail.
Any help would be appreciated.
Thanks
B

I had a same and I fixed this........
Solution
1. The error is happening at the "Organization Preparation" stage, so let's go 'old school' and do that manually.
2. Locate the server on your network that is the schema master (Locate FSMO Servers).
3. Put the Exchange 2010 DVD in the schema master (Or share it over the network and connect to it from the schema master server).
4. Drop to command line and change to the DVD Drive/Directory with the Exchange 2010 setup files in it.
5. ONLY do this if you have Exchange 2003 already! Run the following command, (If no Exchange 2003 present, skip to the next step).
X:\Setup /PrepareLegacyExchangePermissions (Where "X" is CD ROM derive letter)
6. Run the following command:
X:\Setup /PrepareSchema
7.
Run the following command:
X:\Setup /PrepareAD
Note: At this point it may fail, and say it requires an organization name, (it will do this if it finds no existing container in Active Directory).
Error
Exchange organization name is required for this mode. To specify an organization name, use the /organizationName parameter.
If that is the case, then run the following command:
X:\Setup /PrepareAD /OrganizationName:"Your required org name"
Reboot your server and try to install exchange 2010.
Jotiba Patil

Configure new exchange 2010 while old exchange 2003 running ?

Hello,
I'm in the process of deploying a new fresh installation of SBS 2011/Exchange 2010 server. Currently
I have SBS2003/Exchange 2003 running. I want to retired the server and replace with the new server. No migration. By doing that, I am setting up the new server SBS2011 name/domain/ip everything the same as the old server and will replace once all the configuration
is completed.
1. Since they both using the same domainname/ip, can I setup the new server Exchange 2011 while the old
server is alive? If yes, how's the process?
2. If I export and import users email in .pst (on user outlook client) and when the new server is put in place alive does it will regenerate the database
in new Exchange 2011?
Thanks in advance =)

For the 1st question, both servers are in different/isolated network. So you were saying yes i can do that correct? will not going to have any issue running both servers having all the same configuration while configuring the new server up?
the 2nd. since i am not migrating, i am planing to export/import user email from outlook client and when i replace the old server with the new server, i setup the user email client and import the .pst back.

Exchange 2010 - Errors 4002 and Errors 4010

I have two CAS and two Mailbox servers. All are running Server 2008 R2 with Exchange 2010 SP3 RollUp 5.
On one of my mailbox servers i am getting the error every 5 minutes, MSExchange Availability 4002.
Process 4904: ProxyWebRequest CrossSite from S-1-1-0 to https://server.domain.org:443/ews/exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException:
System.Web.Services.Protocols.SoapException: The authenticated user doesn't have sufficient privileges to issue this request.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling(). The request information is ProxyWebRequest type = CrossSite, url = https://server.domain:443/ews/exchange.asmx
Mailbox list = <lastname, firstname>SMTP:user@Domain, Parameters: windowStart = 2/1/2014 12:00:00 AM, windowEnd = 4/1/2014 12:00:00 AM, MergedFBInterval = 30, RequestedView = FreeBusy
. ---> System.Web.Services.Protocols.SoapException: The authenticated user doesn't have sufficient privileges to issue this request.
   at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.Proxy.Service.EndGetUserAvailability(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.FreeBusyApplication.EndProxyWebRequest(ProxyWebRequest proxyWebRequest, QueryList queryList, Service service, IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequest.EndInvoke(IAsyncResult asyncResult)
   at Microsoft.Exchange.InfoWorker.Common.Availability.AsyncWebRequest.EndInvokeWithErrorHandling()
   --- End of inner exception stack trace ---
. Name of the server where exception originated: Server. Make sure that the Active Directory site/forest that contain the user's mailbox has at least one local Exchange 2010 server running the Availability service. Turn up logging for the Availability
service and test basic network connectivity.
Every 10 minutes on my CAS servers i am getting the error MSExchange Availability 4010.
Process Microsoft.Exchange.InfoWorker.Common.Delayed`1[System.String]: Request from S-1-5-21-562707881-1060713641-168829947-11538 failed security checks.
I have adjusted the registry setting HKLM\System\CurrentControlSet\services\MSExchange Availability\Diagnostics from 0 to 5 on the CAS servers. I don't have an Availability Service under Services.
The errors keep occurring.

http://forums.msexchange.org/m_1800549466/printable.htm
Refer This Link
DushYant'

Exchange 2010 calendar(free and busy) cannot work

Hi All
We have a new setup exchange 2010 server.
Everything(Webmail, outlook, autodiscover, out_of_office) is working fine.
When the user check other user calendar, it is not work(no matter in Outlook 2010 or OWA), is there any idea?
Thanks

Hi there
All the user is located in the same site.
The most weird problem is the user using the OWA for checking their own free and busy, it is show no information.
I have tried o use remote connectivity analyzer and the test-outlookwebservice
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1011
Type : Error
Message : When querying Availability for the recipient e-mail address abc@xxx, the following error code and
message were received: ErrorServiceDiscoveryFailed:Unable to find a Client Access server that can serve a
request for an intraforest mailbox <abc>SMTP:abc@xxx.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1025
Type : Error
Message : [EXCH] Error contacting the AS service at https://xxx/EWS/Exchange.asmx. Elapsed time was
12 milliseconds.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1013
Type : Error
Message : When contacting https://xxx/EWS/Exchange.asmx received the error The request failed with a
n empty response.
RunspaceId : b08124f2-b525-4e34-93f0-ca3c6c7134a9
Id : 1025
Type : Error
Message : [EXPR] Error contacting the AS service at https://xxx/EWS/Exchange.asmx. Elapsed time was
249 milliseconds.
But those ews path can be reach when using the browser
Thanks

Second Exchange 2010 installation

I have one exchange 2010 installed in current forest.
I want to install second exchange 2010 server.
What are the pre-requests for 2nd exchange server 2010 installation.
After installation, if i want to make DAG what are its requirement?
Regards,
Sadanand Velechi

Hi Sadanand,
In addition to Andy's suggestion, I would like to clarify the following things:
1. You need to have Enterprise edition of Windows on all nodes for the DAG.
2. All DAG nodes need to be the same version of Windows and ideally keep as close as possible on patch levels.
What's more, here is an article for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx
Hope it helps.
Best regards,
Amy
Amy Wang
TechNet Community Support

CUC 8.5 MWI with Single Inbox Exchange 2010 seems slow and sometimes unreliable

Hi,
I have some issues with MWI for Single Inbox Exchange 2010 + CUC 8.5-HA (latest). When leaving voicemails, sometimes it takes up to 10-20 seconds for Exchange to deliver MWI message. Sometimes it doesn't work at all. CUC mailbox shows that the MWI should be on, but the Exchange Inbox has no unread voicemails. It's either an issue with Exchange not delivering notification (doubt it), or CUC not working.
The message delivery into Exchange works perfectly fine. MWI ON is fast (but that's because CUC turns it on right away). It's EWS syncing back to CUC is very flaky.
Has anyone else had issues and found a good way to troubleshoot it?
On Exch2010 in event viewer I see events like this:
A notification for subscription [HABzdi1hcHBzMDUucmZ0ZWNobm9sb2dpZXMuY29tEAAAAEXPGeSxS3VJiTdeopQts9diaTpYTOXNCA==] against endpoint [http://10.0.16.11:7080/NotificationService/services/NotificationService?id=7682d009-ad26-4644-a323-eb4f198792bd&pid=8104] couldn't be sent. (Send attempts: 2) Details: WebException: The remote server returned an error: (503) Server Unavailable. StatusCode: ServiceUnavailable javax.servlet.ServletException: org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at Microsoft.Exchange.Services.Core.NotificationServiceClient.HandleResponse(IAsyncResult responseAsyncResult)
After 5 unsuccessful attempts to send a notification for subscription [HABzdi1hcHBzMDUucmZ0ZWNobm9sb2dpZXMuY29tEAAAAL0DSwmaIBVKo+9/O78sdvlCIvCgS+XNCA==] against endpoint [http://10.0.16.11:7080/NotificationService/services/NotificationService?id=d180f943-1401-4a24-9eb0-19f3b1b5b997&pid=8104], the subscription has been removed. Details: WebException: The remote server returned an error: (503) Server Unavailable. StatusCode: ServiceUnavailable javax.servlet.ServletException: org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing    at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at Microsoft.Exchange.Services.Core.NotificationServiceClient.HandleResponse(IAsyncResult responseAsyncResult)
This is the full error that I see when going to that link from the web browser on Exchange server:
HTTP ERROR 503
Problem accessing /NotificationService/services/NotificationService. Reason:
    javax.servlet.ServletException: org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing
Caused by:
javax.servlet.UnavailableException: javax.servlet.ServletException: org.apache.axis2.AxisFault: The system is attempting to engage a module that is not available: addressing
     at org.eclipse.jetty.servlet.ServletHolder.makeUnavailable(ServletHolder.java:394)
     at org.eclipse.jetty.servlet.ServletHolder.initServlet(ServletHolder.java:432)
     at org.eclipse.jetty.servlet.ServletHolder.doStart(ServletHolder.java:245)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:694)
     at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:193)
     at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:913)
     at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:584)
     at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:341)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:164)
     at org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:161)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:164)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:92)
     at org.eclipse.jetty.server.Server.doStart(Server.java:232)
     at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
     at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:990)
     at java.security.AccessController.doPrivileged(Native Method)
     at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:955)
Powered by Jetty://
Update:
I'm running 8.5.1ES16.11900-16
They are apparently up to ES44 now, TAC will provide me with it, and I'll let you know if it solves the problem.

Hi David,
When you mentioned "I installed the unrestricted version the service responsible for turing off the MWI is not installed.", this service is actually the Connection Notifier service, which exists on all systems. This is the service I was under the impression you were referring to with regards to MWI. Now that you're referring to something else, it changes the situation a bit.
The Connection Jetty and Connection Exchange Notification Web Service both should exist regardless of Restricted/Unrestricted. Something must have happened with your installation if the Connection Exchange Notification Web Service does not exist. If you're in the US, you should be running the Restricted version of the software, so it's still in your best interest to move to the proper version of the software.
Brad

SME 7.1 not working with Exchange 2010 SP3 UR8v2 and OnTap 8.2.3 7mode

Followed IMT and installed software that NetApp said would work.Ontap 8.2.3 7-modevmWare 5.0 SP3Microsoft Windows Server 2008 R2 SP1Exchange 2010 SP3 UR8v2NetApp Host Tools 6.0.2SnapDrive 7.1.1SME 7.1 Everything connects fine. SnapDrive sees my drives. SME connects to Exchange Server. However in the process of configuring SME, I get the following error. I have followed knowledge base article and increased the timeout of DFM connection in registry, but that has not solved the problem. Has anyone run into this before? SME 6.1 works fine, but is not compatible with SnapDrive 7.1.1 (causes verifications to fail because server can't mount clone) and lower SnapDrive versions are not compatible with Ontap 8.2.3. I am in a real bind here. Thanks in advance.

the following configuration for SME 7.1 is no longer supported: Windows Server 2008 R2Exchange 2010 SP3 RU1 – RU5WMF/PowerShell 3.0SME 7.1 The supported configuration will now be: Windows Server 2008 R2Exchange 2010 SP3 RU5WMF/PowerShell 4.0SME 7.1 this is because Microsoft does not support WMF 3.0 on Server 2008 R2 running Exchange 2010 SP3, with any RU version.SME 7.1 requires a minimum of PowerShell 3.0 (part of WMF 3.0) in order to run. Feel free to review the Exchange Server Supportability Matrix located here: https://technet.microsoft.com/en-us/library/ff728623%28v=exchg.150%29.aspx. All existing documentation (ISG, Admin Guide, IMT) will be updated shortly to reflect this change in requirements. hope that helps,Domenico.

New Exchange 2010 installation. HUB and CAS on two seperate servers, need two certificates?

Similar Messages

Maybe you are looking for