Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Team,
I have successfully integrated adfs 3.0 and Exchange 2013 owa and ecp. However, we have a coexistence environment with exchange 2007. When you access owa, which then redirects you to adfs, sign-in, and then get redirected back to owa. If your
mailbox is still within exchange 2007, you get a blank login page. If you mailbox is in exchange 2013 then you successfully get the owa page for 2013. The problem is that all exchange 2007 mailbox users get blank pages at login. So I have determined
that exchange 2013 cas is not doing the service location lookup on the mailbox to determine if a redirect to the legacy owa address is needed. Is there a configuration setting that I might be missing? Or does the integration with adfs and owa not support
the much needed mailbox lookup for a coexistance environment? A side note: if we enable FBA with owa, both login scenarios work just fine (legacy and new 2013). The legacy namespace has been created, and applied to the exchange 2007 urls.

Hi,
Try using AD FS claims-based authentication with Outlook Web App and EAC
http://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx
Thanks,
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Simon Wu
TechNet Community Support

Similar Messages

Acrobat Reader integration with SharePoint 2007

Hi,
We have been having some major issues with people opening PDF files from document libraries in MOSS 2007.
Firstly in v9.x we find that only one user can access a PDF file at a time because it automatically opens the file as editable. This isn't a problem, however when another user tries to open it instead of being asked to open a read only\local copy, they just get an access violation error. We have found that sometimes even though a user has closed the file, the access violation errors continue and the only way round it is to copy the file locally, delete the original and then copy it back up to the document library.
I see that version X has been written to include much better integration with SharePoint. However our company policy is that we do not use check in\check out, so i'd like to disable this prompt. I've found this article which seems to have instructions on how to do it, however the registry change does not seem to have made any difference. I notice that on that article is says "DO NOT PUBLISH THE DOCUMENT EXTERNALLY UNTIL 10.1 SHIP". I'm unsure whether this is a typo and it's meant to be 10.01 which has recently been released or whether this article should not yet be available.
Has anyone managed to get the registry change working?
Cheers
James

Hi,
I was going to move this to a more appropriate forum but I'm not clear on where to try. Can you repost this under the Reader forum as well as on http://answers.acrobatusers.com/?
thanks,
Ben

Set Exchange 2013 calendar permissions with Outlook 2007

Hi,
I have a new install of Exchange 2013 with ~30 Win 7, Office 2007 clients. Setting permissions on calendars doesn't work properly from Outlook 2007 (a known MS issue). Does anyone know if there is a fix or work around to assign permissions to the calendar?
i.e. where you right click the Calendar folder and set different levels of permission. There is a 'permission' option in OWA but this doesnt appear to work for calendars.
I have tried Outlook 2013 and that works ok. Is there alternate way to save having to move to Outlook 2013?
Thanks.

Hi,
The above issue occurs because of a limitation in how Exchange Server 2013 set Free/Busy permissions. The workaround is to use OWA to set up calendar permissions.
Here is a helpful article about setting up calendar permissions in OWA for your reference.
Sharing your calendar in Outlook Web App
https://support.office.com/en-us/article/Sharing-your-calendar-in-Outlook-Web-App-7ecef8ae-139c-40d9-bae2-a23977ee58d5?CorrelationId=7fe34d54-c3e4-4ca4-a83d-450dbd8075a5&ui=en-US&rs=en-US&ad=US#_Toc342645965
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

SAP 7.20 CRM Integration with Outlook 2007

Hopefully you guys can help me seeing how i'm pretty illiterate on the workings of SAP. I work on a User Support team and we are undergoing tests for certain parts of our organization with deploying Windows 7. I bring this up because we currently use the MAPI driver that is offered with RightFax to integrate SAP and Outlook to send billing and transaction forms that is not available to use with Windows 7.
Does anyone know the work around for this?
(sorry if i sound uneducated in the workings of SAP, we have very little support for it past deploying the program. But i am looking to learn more)

Hi Sunil,
Could you please check with the below link from SAP Help Portal, which explains about the Integrated Communication Interface, its customizing, etc., which I feel will be a useful tip for you in your process ?
http://help.sap.com/saphelp_crm70/helpdata/EN/97/ffebc55b84f745b368865e9314fa44/frameset.htm
Thanks & Best Regards,
Vinod

Lync Server Integration with Exchange 2013

Hello,
I have Exchange 2013 standard edition server installed and running successfully on a Windows 2012 machine. Now, I would like to have a Lync 2013 server integrated with it. I came across some links telling that its not possible to integrate Unified Messaging
in the Exchange standard edition and would need an Enterprise edition license. But, when I checked my ECP, I could see that UM is already there and its enabled.
So, Is it possible to integrate Lync 2013 with Exchange 2013 standard edition? What all things I need to take care of while Integrating? If someone could shed some light on this, that would be greatly appreciated.
Thanks and Regards,
Nash Burns

Yes you can integrate Lync 2013 with Exchange 2013 Standard, the only big difference between Exchange 2013 Standard vs Enterprise is the number of mailbox databases (5 vs 50).
Follow this link for information on integrating the two: http://technet.microsoft.com/en-us/library/jj688098.aspx (specifically integrating Lync with Exchange for Voicemail http://technet.microsoft.com/en-us/library/jj687983.aspx)
Having said that, the confusion may be related to User CALs. You need Exchange Enterprise User CALs to use the Unified Messaging components. (I believe they still work regardless, but
to be properly licensed and compliant you need to have the correct number of Enterprise CALs for the number of users that use UM)
If this helped you please click "Vote As Helpful" if it answered your question please click "Mark As Answer" | Blog
www.lynced.com.au | Twitter
@imlynced

Issue with connection SSRS reportviewer control to SSRS 2012 integrated with SharePoint 2010...

Hi,
I have a .NET application that uses SSRS ReportViewer 2012 control to render reports deployed on SSRS 2012 integrated with SharePoint 2010. I am getting error "the report execution '' has expired or not found". The same code works when I connect
to SSRS 2008 R2 integrated with SharePoint 2007. I investigated the issue and it seems the JavaScript that pings the SSRS server before it expires is missing from rendered HTML.
Let me know if there is a way to fix this issue.
following is the code:
ASPX:
<formid="form1"runat="server">
<rsweb:ReportViewerAsyncRendering="true"
KeepSessionAlive="true"ID="test"runat="server"></rsweb:ReportViewer>
<asp:scriptmanagerrunat="server"></asp:scriptmanager>
</form>
Code Behind:
if(!IsPostBack)
this.Session.Clear();
        test.Reset();
        test.ProcessingMode =
ProcessingMode.Remote;
        test.KeepSessionAlive =
true;
        test.ServerReport.ReportServerUrl =
newSystem.Uri("https://webappname/_vti_bin/reportserver/");
        test.ServerReport.ReportPath =
https://webappname/RS_Reports/REportEngineTest.rdl;
ReportServerCredentialscred =
newReportServerCredentials();
            test.ServerReport.ReportServerCredentials = cred;
report server credentials:
publicICredentialsNetworkCredentials
get
// Use default identity.
returnnewNetworkCredential("user",
"pwd",
"domain");

What's the meaning of webappname, are you mean the sharepoint site?
I think this issue can be caused by the incorrect url. You can refer to the following link:
http://msdn.microsoft.com/en-us/library/ms154497(v=sql.110).aspx
Familyabc

AD RMS 2012 integration with exchange server 2013

AD RMS 2012 integration with exchange server 2013
I would like to have a knowledge About this Topic
1.what is differrent if we use internal SSL certificate with Public Certificate and in this case i would like to use Mobile Phone I eed to import Root Certificate ?
2.Do I have problem? If I start to install AD RMS 2012 with SQL EXpress after that I want to chage it to SQL Server ?
3.when I use SQL Expres what I can do after Disk is full (10 GB)?
4.If AD RMS is down It will affect with email that it is already sent ?
5. Which Edition of outlook can produce IRM protected documents
6. To Use AD RMS Server 2012 through OWA, Outlook and Moblie Phone ,a CAL is required or not ?

Could you post the list of sites:
appcmd list site
The ones listening on port 80:
appcmd list site /bindings:http/*:80:
And on port 443:
appcmd list site /bindings:https/*:443:
Step by Step Screencasts and Video Tutorials

Lync 2013\Exchange 2010 OWA Integration Problem

Hi there,
I've got a vexing issue that I haven't had much luck in researching. I am running Lync 2013 on Server 2008 R2 and Exchange 2010 SP3 on Server 2008 R2. I followed Jeff Schertz's instructions (http://blog.schertz.name/2010/11/lync-and-exchange-im-integration/)
and Lync\OWA integration is working--sort of.
We currently have a central pool (we'll call it lyncpool.contoso.com) and three pools housed on SBAs-- lyncsba-loc1, lyncsba-loc2,lyncsba-loc3. Users in our main location are housed on the central pool, whereas users in our remote locations are housed
on their respective SBA.
Following the instructions, I pointed my OWA virtual directories at lyncpool.contoso.com, and everything seemed fine at first. I could see presence in OWA, initiate an instant message...the works. However, when I asked a user homed on one of the SBAs,
he said that he could only see presence for other users in his pool\location. Everyone else had a white "unknown" presence chiclet. To verify, I temporarily moved my lync account to that branch pool, and sure enough--I saw the same thing. As
a troubleshooting measure, I re-ran the OWA configuration portion and instead of using the central pool as the instantmessagingserver value, I pointed it directly at that branch pool. At that point, he and I, being homed in that branch pool, could see
presence for EVERYONE. Problem solved, right? Well, no...because now, the central pool users could only see presence for other central pool users, and the other branches could still only see presence for their poolmates.
I've run Wireshark, CLS logging, you name it--I haven't seen anything fishy, and I'm starting to wonder if this perhaps a bug or an unsupported use-case(I hope not, since Microsoft otherwise endorses such a configuration). I've been beating my head
against this wall for almost two weeks with no change...someone, help! :)

This is the only thing that seems of interest in the CLS Log:
TL_WARN(TF_DIAG) [lyncpool01\VGTLYNCFE-01]1B70.4184::06/17/2014-20:47:03.028.00001F75 (SIPStack,SIPAdminLog::WriteDiagnosticEvent:SIPAdminLog.cpp(805))
[1781536493] $$begin_record
Severity: warning
Text: Cannot process Route headers from a non-trusted source, or with first Route field in the set not matching the connection on which the request arrived
Result-Code: 0xc3e93c5e SIPPROXY_E_ROUTING
SIP-Start-Line: SUBSCRIBE sip:LyncPool01.xxx.net:5061;transport=tls;ms-fe=VGTLYNCFE-01.xxx.net SIP/2.0
SIP-Call-ID: 45c62e9edaee4252908914b37ca5ef23
SIP-CSeq: 1895 SUBSCRIBE
Source: mail.xxx.net:47892
$$end_record
The "source" here is our OWA server. I have issued a certificate from our local CA(the same one that issued the Lync certs), making sure the CN of the certificate matches the OWA url. Any ideas?

Exchange 2013, multiple IIS OWA sites with different authentication

Hi
I have an exchange 2013 server with Client Access and Mailbox server installed. The server has an second ip address which I have bound an additional IIS site to. The additional IIS site is named ExchangeExternalFBA.
The default web site is configured for basic and windows authentication with:
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
Then a new ECP and OWA are configured with:
New-ecpVirtualDirectory -WebSiteName "ExchangeExternalFBA"
New-OwaVirtualDirectory -WebSiteName "ExchangeExternalFBA"
Set-owavirtualdirectory -identity "owa (ExchangeExternalFBA)" -LogonFormat FullDomain -FormsAuthentication:$true -WindowsAuthentication:$false -BasicAuthentication:$true
Set-EcpVirtualDirectory -identity "ecp (ExchangeExternalFBA)" -FormsAuthentication:$true
Then I perform an iisreset.
My problem is that then when I try to access the ECP or OWA on the default website, it loads forms authentication! The ECP or OWA on the ExchangeExternalFBA web site works correctly and also loads forms authentication.
If I run...
get-owavirtualdirectory "owa (ExchangeExternalFBA)"
then it returns:
InternalAuthenticationMethods : {Basic, Ntlm,
WindowsIntegrated}
BasicAuthentication : True
WindowsAuthentication : True
DigestAuthentication : False
FormsAuthentication : False
LiveIdAuthentication : False
AdfsAuthentication : False
OAuthAuthentication : False
If I then run
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
and perform another iisreset then when I try to access the ECP or OWA on the default website it loads correctly. But then the forms based authentication on the ExchangeExternalFBA website can no longer log in, it does not accept the user name and password.
If I then disable and enable FBA on the ExchangeExternalFBA website then it works but forms based authentication takes over the default web site again!
Whether I perform the above from the gui or from powershell it does not make a difference, the same behaviour is observed. Changing the logontype on the FBA does not make a difference.
This has been tested on exchange 2013 cu1 and cu2.
Similar(if not identical until they get sidetracked) issue reported in http://social.technet.microsoft.com/Forums/exchange/en-US/9fcd360f-6658-4940-add7-2f13265cf86b/multiple-owa-sites-on-a-single-server-2012-with-exchange-2013-mailbox-cas.
This worked fine in outlook 2007 and 2010, why now do my virtual directories break each other?
I can reproduce the issue on a test exchange 2013 I built in dev.
Is this a bug or are you no longer meant to host different forms of authentication on a single cas?
I'm mostly interested to see if this works for other people and why it no longer seems to work in 2013, so please no questions; 'why do you want 2 different forms of authentication'.
Much appreciated, Thanks!

Based off of your feedback I have run the following:
Remove-OwaVirtualDirectory "owa (ExchangeExternalFBA)"
Remove-EcpVirtualDirectory "ecp (ExchangeExternalFBA)"
iisreset
Set-EcpVirtualDirectory -identity "ecp (default web site)" -FormsAuthentication:$false
Set-owavirtualdirectory -identity "owa (Default Web Site)" -FormsAuthentication:$false -WindowsAuthentication:$true -BasicAuthentication:$true
New-ecpVirtualDirectory -WebSiteName "ExchangeExternalFBA" -Role ClientAccess
New-OwaVirtualDirectory -WebSiteName "ExchangeExternalFBA" -Role ClientAccess
Set-owavirtualdirectory -identity "owa (ExchangeExternalFBA)" -LogonFormat FullDomain -FormsAuthentication:$true -WindowsAuthentication:$false -BasicAuthentication:$true
Set-EcpVirtualDirectory -identity "ecp (ExchangeExternalFBA)" -FormsAuthentication:$true
iisreset
After this there has been no change in behaviour. After the iisreset, forms have again hijacked the default web site and re-setting the authentication on the default web site removes the forms but breaks the ability to sign in to the forms based page on the
ExchangeExternalFBA web site again.
Note. '-Role Frontend' did not work. It showed the error:
Cannot process argument transformation on parameter 'Role'. Cannot convertvalue "frontend" to type
"Microsoft.Exchange.Management.SystemConfigurationTasks.VirtualDirectoryRole".
Error: "Unable to match the identifier name frontend to a valid enumerator name. Specify one of the following enumerator names and try again:
ClientAccess, Mailbox"
+ CategoryInfo : InvalidData: (:) [New-OwaVirtualDirectory], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,New-OwaVirtualDirectory
Running get-help New-OwaVirtualDirectory -detailed shows the correct usage would be '-Role ClientAccess'?
-Role <ClientAccess | Mailbox>
The Role parameter specifies the configuration that should be used
when the virtual directory is created. The following are the values
that can be used with this parameter:
* FrontEnd Configures the virtual directory for use on a Client Access
server.
* BackEnd Configures the virtual directory for use on a Mailbox server.

Exchange 2013 MB/CAS integration with legacy Exchange 2007 CAS/MB/Trans server

Hi All,
I have an existing running Exchange 2007 SP3 RU13 server acting as MB,CAS,Transport using a Barracuda SPAM for SMTP (MX Record is assigned to here), and a TMG2010 server performing all ActiveSync, Outlook Anywhere, and OWA connectivity.
I have built a new Exchange 2013 SP1 server that will (for the meantime) act as a MB & CAS server only.
I successfully migrated a testuser mailbox to the new EX2013 server from the EX2007 server. The problem is that once migrated, OWA and Outlook can't access the mailbox.
OWA form our URL gives the message: Outlook Web Access is currently unavailable. If the problem continues, contact technical support for your organization and tell them the following: No Client Access servers of the appropriate version can be accessed from
the Internet
If I run OWA from the EX2013 URL it works ok, but not for MBs on the EX2007 server.
I tested this configuration in a VM lab and it worked ok. All I had to do was move the mailbox, then run Outlook. Outlook automatically found the new server and opened the MB.
Basically what I need to do is move all our existing MBs from the old 2007 server to the new 2013 server. I want to continue to use the exisiting transport/CAS/EDGE services on 2007 without having to rebuild both the internal and external comunications
infrastructure at the present time.
How can I get the EX2013 server to act as the MB server for the EX2007 communications infrastructure?

Hi,
Please try to create a new user on Exchange 2013, and send/receive email via both Outlook and OWA to test whether the Exchange 2013 mail flow well.
If Exchange 2013 works well, please try to bypass the TMG on Exchange 2007 for a little while for testing.
Additionally, we can use CAS 2013 URL to proxy/redirect previous CAS, or publish both CAS 2007 and CAS 2013 to be internet facing server with separate URLs, as Ed suggested.
Thanks
Mavis Huang
TechNet Community Support

Exchange 2013 : OWA failing after login with error "HTTPS 400"

Greetings,
I am in phase of Upgrading my existing Exchange 2007 Infra to Exchange 2013.
The environment is as mentioned below:
4 Mailbox Server (DAG)
4 CAS Servers (NLB)
Everything has been configured and working properly, except Only one CAS server is able to pass the login request
https://servername/owa
Rest of all the CAS servers are failing with error "HTTPS 400" while accessing OWA
https://localhost/owa
Its happening only while accessing OWA, ECP works fine.
Please let me know the fix to counter this strange issue.
Thanks in advance.
Regards

Hi,
Please check if IIS log is enabled on the CAS server, if not, please enable it.
Then check the detailed error code from IIS logs (Path: inetpub\logs\Logfiles\W3SVC1 ) , some code like 400.1, 400.2 ect.
Refer to this KB for more details
http://support.microsoft.com/kb/943891
After that, please post the OWA related login entry with error code shows 400.
Thanks for your time and patience.
Meanwhile, please check the OWA authentication method by command
Get-OWAVirtualDirectory –Server “Ex2013 CAS server” | fl *authentication*
We should set the authentication as the below:
Get-OWAvirtualdirectory -Server “Ex2013_CAS_server” | set-OWAvirtualdirectory -windowsAuthentication $False -BasicAuthentication $True -FormsAuthentication $True
Then perform iisreset and try to access OWA again.
Best Regards.

Coexistence Exchange 2007 and 2013 - Clients on 2013 cant connect to Outlook, OWA works fine

Hi
We are currently running all our users on Exchange 2007. I've installed Exchange 2013 on another hardware following several guides on coexistence between 2007 and 2013.
I'm now testing with a few test users I've migrated from 2007 to 2013.
Everything was working fine until I messed up with something. It's either the certificates and/or Exchange Web Services and/or activating Outlook Anywhere.
Now, all my tests users on Exchange 2013 can connect and send/receive emails on OWA, but Outlook clients cannot connect to Exchange server.
When I start Outlook, I get the error Unable to open the default mail folders
When I try to create a new Outlook profile, I get the error: "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
When I click on Check Name, I get: "The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action"
Thanks for any help you could provide
Martin

Changed the
ExternalClientAuthenticationMethod for the 2007 server.
Output for Get-OutlookAnywhere | fl *method*
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
Now everytime I try to create an Outlook profile whose mailbox is on Exchange 2013 it's
asking for credentials.
If I dig further and try to manually configure server settings:
If I specify the Exchange 2013 server and try a 'Check
Name', it says: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
If I specify the Exchange 2007 server and try a 'Check
Name', the server changes for the fqdn of the 2013 server and it does resolve 'Check Name' process. Clicking on Next at this point completes the 'Add new e-mail account wizard". But is I try to start Outlook, I got an error saying "Microsoft Exchange is unavailable"
Any other thoughts on this issue?
Thanks,
Martin

Can Exchange 2007 to be integrated with SharePoint 2013

Can Exchange 2007 to be integrated with SharePoint 2013?

In the sense of using Incoming and Outgoing email, absolutely. But not for other things, like Site Mailboxes, which require Exchange 2013.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

OWA functionality in Exchange 2007 coexistance with 2013

I have conexistance environment with Exchange 2007 and Exchange 2013. Out of about 1200 users we have 25 test users in the 2013 environment. The problem we are seeing is when a 2013 mailbox has "Full Access" to a 2007 mailbox and tries to connect
to that mailbox through OWA 2013 the connection always fail. I can attach the mailbox in Outlook with no problems but cannot open that mailbox through OWA 2013. Any thought?

See if this helps. It's not an exact match for your versions, but I think it's what you need to look at.
http://support.microsoft.com/kb/981541
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2013 OWA,Async,And OA error MsExchange BackEndRehydration event id 3002

Hi team,
I had issue in My Exchange system.
I had two Exchange 2013 muli role with CAS and MBX
Server A had no problem connection when client access OWA directly (https://servernamefqdn/owa)
but, theres issue when I pointing to server B OWA (https://serverBfqdn/owa). its same when outlook connect (using OA ),and Aysnc connection.
when I failed to connect OWA, theres event id 3002 MsExchange BackEndRehydration event id 3002.
the error show at Server A ( server at a good condition )
heres the error
Thanks

Hello Team,
I have a similar issue with Event ID 3002 filling up the App log on both Mailbox servers. Here is a snippet of the error. Any help is greatly appreciated. Thank you.
"Protocol /EWS failed to process request from identity DOMAIN\CASServer. Exception: Microsoft.Exchange.Security.OAuth.InvalidOAuthTokenException: The user specified by the user-context in the token is ambiguous.
   at Microsoft.Exchange.Security.OAuth.OAuthActAsUser.InternalCreateFromAttributes(OrganizationId organizationId, Boolean calledAtFrontEnd, Dictionary`2 rawAttributes, Dictionary`2 verifiedAttributes)
   at Microsoft.Exchange.Security.Authentication.BackendAuthenticator.OAuthAuthenticator.ExtractActAsUser(OrganizationId organizationId, CommonAccessToken token)
   at Microsoft.Exchange.Security.Authentication.BackendAuthenticator.OAuthAuthenticator.InternalRehydrate(CommonAccessToken token, Boolean wantAuthIdentifier, String& authIdentifier, IPrincipal& principal)
   at Microsoft.Exchange.Security.Authentication.BackendAuthenticator.Rehydrate(CommonAccessToken token, BackendAuthenticator& authenticator, Boolean wantAuthIdentifier, String& authIdentifier, IPrincipal& principal, IAccountValidationContext&
accountValidationContext)
   at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.ProcessRequest(HttpContext httpContext)
   at Microsoft.Exchange.Security.Authentication.BackendRehydrationModule.OnAuthenticateRequest(Object source, EventArgs args).

Exchange 2013 owa integration with ADFS and cooexistance with exchange 2007

Similar Messages

Maybe you are looking for