Opportunistic TLS between our Exchange 2010 SP3 on Premise (WIth Edge) and Exchange Online Protection.

Hi,
We would like to configure Opportunistic TLS between our Exchange 2010 SP3 On Premise Systems (with Edge) and EOP.
I can see that Opportunist TLS is enabled on both the send and receive connectors in EOP. SO I think no change required here.
The On premise Send Connector (Configured by EdgeSync) does not have the option for Opportunistic TLS. Under "Configure Smart Host Authentication Settings" it is currently set to "None". I have the option for "Basic Authentication
over TLS" but this requires a Username and Password. No option for Opportunistic TLS. When I look at the properties of the send connector (get-sendconnector "sendconnector_name" | fl) I
can see that the IgnoreSTARTTLS parameter is set to FALSE - so I think that means it is enabled. So I think no changes required here- right?
The receive connector on the Edge Server has the TLS option on the Authentication tab - so I guess I just check that option right?
The Edge servers also run TMG and the two are integrated. I don't think this changes anything but thought I would include it in case it does.
Anything I have missed?
Thanks very much.
Geoff
ilmuro69

Similar Messages

Exchange 2010 SP3 - Delayed emails with XLSM attachments...

Running Exchange 2010 SP3 Rollup 5. Clients running Windows 7 and Office 2010 Pro Plus SP2. Have one specific user / client that when sending emails with an XLSM attachment around 5:30AM, the email is delayed getting to the Exchange server and
is delayed up to 16 hours. Unfortunately, this is a random occurrence, and not necessarily easy to duplicate.
The Sent Items on the Outlook client reflect the correct sent time, but the Message Tracking Log on the Exchange server shows the server did not receive the email until approximately 12 to 16 hours later.
The desktop is a shared system and this issue appears to be isolated to the user's profile, AD account, or Exchange. I've literally blown away the users local profile and reconfigured it with no resolution.
Any suggestions are greatly appreciated.
Fuel

Hi,
Please verify whether there is any error/warning/information message left in App log. If yes, please paste the details without sensitive information.
I suggest re-send a .xlsm attachment for testing to verify whether it delays.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Exchange 2010 SP2: Different problems with E_ACCESSDENIED on exchange servers

Hello All,
I'm observing a strange problem in an AD 2008 R2 / Exchange 2010 SP2 environment:
When creating a DAG and adding 1 or more servers to the DAG, the following error occurs:
Summary: 2 item(s). 0 succeeded, 2 failed.
Elapsed time: 00:00:05
<MAILBOX SERVER 1> Failed
Error:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer '<MAILBOX SERVER 1>' -Identity '<NAME DAG>'
Elapsed Time: 00:00:02
<MAILBOX SERVER 2> Failed
Error:
Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer '<MAILBOX SERVER 2>' -Identity '<NAME DAG>'
Elapsed Time: 00:00:02
There are no logs created on the Mailservers, so I have no more detailed information. Where to start with troubleshooting this issue?
Edit: BTW I already checked the local admin membership of the "Exchange Trusted Subsystem" domain group.
Also commands like get-owavirtualdirectory give the Access Denied error (except on the CAS servers themselves).
You know you're an engineer when you have no life and can prove it mathematically

Hi Frank,
The DAG is not yet populated. When inserting the first server(s) in the freshly created DAG, the error appeared.
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Get-DatabaseAvailabilityGroup
Name             Member Servers
Operational Servers
IICT-DAG-002     {}
[PS] C:\Program Files\Microsoft\Exchange Server\V14\Scripts>Get-DatabaseAvailabilityGroup IICT-DAG-002 -Status | fl
RunspaceId                             : cc985264-fa89-48f8-8aba-c1b0c89eb097
Name                                   : IICT-DAG-002
Servers                                : {}
WitnessServer                          : iict-srvp00-011.insourceict.local
WitnessDirectory                       : C:\IICT-DAG-002
AlternateWitnessServer                 :
AlternateWitnessDirectory              :
NetworkCompression                     : InterSubnetOnly
NetworkEncryption                      : InterSubnetOnly
DatacenterActivationMode               : Off
StoppedMailboxServers                  : {}
StartedMailboxServers                  : {}
DatabaseAvailabilityGroupIpv4Addresses : {10.100.0.54}
DatabaseAvailabilityGroupIpAddresses   : {10.100.0.54}
AllowCrossSiteRpcClientAccess          : False
OperationalServers                     :
PrimaryActiveManager                   :
ServersInMaintenance                   :
ThirdPartyReplication                  : Disabled
ReplicationPort                        : 0
NetworkNames                           : {}
WitnessShareInUse                      :
AdminDisplayName                       :
ExchangeVersion                        : 0.10 (14.0.100.0)
DistinguishedName                      : CN=IICT-DAG-002,CN=Database Availability Groups,CN=Exchange Administrative Gro
                                         up (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=InsourceICT,CN=Microsoft Exch
                                         ange,CN=Services,CN=Configuration,DC=insourceict,DC=local
Identity                               : IICT-DAG-002
Guid                                   : 71d5d869-03ac-4f8a-8de7-fc15bc6a0ae1
ObjectCategory                         : insourceict.local/Configuration/Schema/ms-Exch-MDB-Availability-Group
ObjectClass                            : {top, msExchMDBAvailabilityGroup}
WhenChanged                            : 8-6-2012 14:35:59
WhenCreated                            : 8-6-2012 13:35:21
WhenChangedUTC                         : 8-6-2012 12:35:59
WhenCreatedUTC                         : 8-6-2012 11:35:21
OrganizationId                         :
OriginatingServer                      : IICT-SRV003.insourceict.local
IsValid                                : True
You know you're an engineer when you have no life and can prove it mathematically

Exchange 2010 SP3 RU6 - Problems with New-MailboxExportRequest

New-MailboxExportRequest seems to ignore -ExcludeFolders and -IncludeFolders and export the entire mailbox. For example:
New-MailboxExportRequest -IncludeFolder TestExport -Mailbox TestUser -FilePath \\SomeUNCPath\test.pst
will exportsthe entire contents of the mailbox. I believe this used to work before, but it is possible I have lost my mind.
The folder TestExport is on the root, as in, if you were to run Get-MailboxFolderStatistics, the FolderPath is /TestExport. I've also tried using -ExcludeFolders to exclude every other folder with no luck.
Any confirmation of an issue or help is appreciated.

Hi,
From your description, I recommend you use the following cmdlet to check the result.
New-MailboxExportRequest -IncludeFolders "#Inbox#" -Mailbox TestUser -FilePath
\\SomeUNCPath\test.pst
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Exchange 2010 SP3 - Can DAG member be on OS 2012 R2 STD?

Hi guys.
We have Exchange 2010 SP3 on 2008 r2 enterprise.
now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
with best regards,
bostjanc

Hi guys.
We have Exchange 2010 SP3 on 2008 r2 enterprise.
now we are thinking about having DAG. I know that recommendations is to have the same OS on 2nd Exchange server but still is it possible to make DAG between: Exchange 2010 SP3 on 2008 r2 enterprise and on other side Exchange 2010 SP3 on 2012 R2 STD?
with best regards,
bostjanc
No. It wont let you do that.
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.141).aspx
DAGs are available in both Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition. In addition, a DAG can contain a mix of servers running Exchange 2010 Standard Edition and Exchange 2010 Enterprise Edition.
Each member of the DAG must also be running the same operating system. Exchange 2010 is supported on both the Windows Server 2008 and Windows Server 2008 R2 operating systems. All members of a DAG must run either Windows Server 2008 or Windows Server 2008
R2. They can't contain a combination of both Windows Server 2008 and Windows Server 2008 R2.
In addition to meeting the prerequisites for installing Exchange 2010, there are operating system requirements that must be met. DAGs use Windows Failover Clustering technology, and as a result, they require the Enterprise version of Windows.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 SP3 RU8

I am trying to rollback Exchange 2010 SP3 RU8. When I uninstall the update the installer asks for exchangeserver.msi for Exchange 2010 SP3 RU7. I downloaded RU7 from the Microsoft website. It did not accept it as the correct msi. I ran the Exchange 2010
SP3 RU7 update I download and it comes up as RU8. I need the exchangeserver.msi from Exchange 2010 SP3 RU7. Thank you for your help.

You may need the original SP3 binaries located here:
http://www.microsoft.com/en-us/download/details.aspx?id=36768
See this thread for more ideas about rolling back:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8
Update:Microsoft has released version 2 of SP3 RU8 today. The link should be live soon.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2010 SP3 startdagservermaintenance.ps1 issues

My Environment is as follows:
Production
Server 1 - CAS, Hub Transport (DAG witness server)
Server 2 - Mailbox (3 databases - DAG with Server 3) - Currently at SP1
DR Site
Server 3 - Mailbox, Hub Transport
I have Exchange 2010 SP3 applied to server 1 and 3. I have not been able to successfully run
StartDagServerMaintenance.ps1 on Server 2. If I am ok with downtime, is there any risk in upgrading my server without running this script? If so, would I need to power off Server 1 and 3 first? I believe my issue with the script may
be due to a journal mailbox.

I assume you are talking about Updating Mailbox Server or you are just testing the script?
No you don't have to shutdown the server.
About the script, its suggestion to run it, but even if you are not running its ok.
By the way, how you are running the script? Are you running from the location where the script is residing.
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.

Rollup 6 for Exchange 2010 SP3

Does anyone know when Microsoft is going to release either Rollup 6 or a patch for Exchange 2010 SP3? Rollup 3 for SP3 introduced the following issues:
“Some users (not all of them) report that they don't see new emails in their Outlook 2010 box on Shared folders, even though they got the new email message envelope. When they change folder and back to the Inbox the new mail is suddenly visible. Same sort
of "delay" happens when users mark a message for follow-up or try to change a message from unread to read.”
We have installed Rollup 5 but it did not address the issue.
Thanks
Dave

Hi,
Currently, there is no official document about the release of RU6 for Exchange 2010 SP3. If the RU6 for Exchange 2010 SP3 will be coming, you can find this information in the Exchange Team Blog.
http://blogs.technet.com/b/exchange/
Thanks for your understanding.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 Free/Busy Federation with vendor's Office 365 tenant

Here the situation,
ORG A
====
Exchange 2010 SP3 On-premise. No externally accessible CAS available/published (we are very secure and require VPN for Outlook/OWA from home/outside network)
ORG B
====
Office 365
ASK
===
ORG B is a vendor for ORG A and we would like to have federated free/busy sharing between the two organizations. I have read the steps about setting up a federation trust, configuring org relationships both ways, configuring autodiscover on our end.
My specific questions are,
1. Currently we don't have any externally published CAS servers. My assumption is we need atleast one (and probably more for fault tolerance) for federated free/busy sharing correct? We obviously don't want to place this in the DMZ/externally...so what are
the recommended configuration? Publish the CAS externally? Any other more secure recommendations? We don't have TMG or any other Microsoft solution for that purpose...are there any other options? We use Cisco IronPorts for inbound/outbound email.
2. Does this coexistence server have to be Exchange 2013 or will Exchange 2010 sp3 suffice?
3. Are there any other methods of accomplishing this ask? We don't want users to have to individually share calendars...so internet calendar sharing is out of the question.

Hi,
If the organization receives or sends Internet e-mail for the domain, we need to
configure an
internet facing CAS server.
For your reference, here are some articles that may be helpful to you:
Exchange 2010 SP1 and Exchange Online (Office 365) Calendaring:
http://blogs.technet.com/b/exchange/archive/2011/02/16/3412010.aspx
Federation in Office 365 and Exchange
http://community.office365.com/en-us/wikis/exchange/federation-in-office-365-and-exchange.aspx
Create a Federation Trust
http://technet.microsoft.com/en-us/library/dd335198.aspx
Thanks,
Winnie Liang
TechNet Community Support

Outlook 2013 Category view not updating after Exchange 2010 SP3 RU3

After updating to Exchange 2010 SP3 RU3 last night, users who use categories view in Outlook 2013 are complaining that the view does not update. The alert is received in the notification area and the unread message count next to Inbox updates appropriately.
The view can be force updated by switching between All and Unread, by using Reset View, or closing and opening Outlook. It seems anything that forces a 'redraw' of the view will update it - except for the actual reception of email. I easily replicated
this issue. For reference:
Exchange 2010 SP3 RU3
Windows 7 x64 Ent
Outlook 2013 (15.0.4551.1004) 32-bit
I do see that SP3 RU4 has been released, however the only change listed is a security patch.
Thank you for any ideas.

Hi, Everyone –
This has been a known issue for a very long time – we have people at our workplace that are very disappointed since a feature as great as categorizing email (not using tasks) has become broken and has not even been considered to be fixed for
over half a year. It was not fixed in the updates for Patch Tuesday this week.
I would like to confirm that this is an issue with Outlook 2010 and 2013 when running the latest Exchange 2010 and there is NO FIX
– I have scoured the internet for a solution – all proposed "textbook" solutions do not work and I am positive that the issue can be recreated; however, everyone from Microsoft does not mention trying to recreate the issue at all.
The workaround of creating a rule to send new emails to a category could break other pre-existing rules and cause more frustration and wasted time for users/IT before and after the issue is fixed.
Please fix this issue sooner than later, as the Categories view is completely broken and unusable at this point in time.
Regards,
IT Helper

After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

Hi,
We have an issue with our OWA page. We are currently publishing OWA via UAG.
We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7. Since the upgrade, we are keep getting the following error after entering our credentials on the login page. I've tried with every possible browser.
You do not have permissions to view this folder or page
Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues. I can see this on the Active Sessions screen
on Web Monitor.
I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running.
No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer.
Any insight would be helpful? I'm assuming something changed on the Exchange side after the upgrade.
Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
UAG > SP4
TMG > SP2 Rollup 5

I've found a solution; UAG requires Basic Authentication over OWA. For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
http://technet.microsoft.com/en-us/library/ee921443.aspx
Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue. Though beware, you
have do this on all your Client Access servers.

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Is WMF3 or WMF4 supported in Exchange 2010 SP3 UR5 installed on Server 2008 R2 SP1?

We'd like to upgrade WMF (aka powershell) on our Exchange 2010 servers but I haven't been able to find any updated information on support with the most recent servicepack/update rollup.
Is installing WMF3 or WMF4 supported on Server 2008 R2 SP1 w/ Exchange 2010 SP3 UR5?

WindowsPowerShell 3.0 is supported. Haven't seen 4.0 running for exchange 2010 on 2008 R2
http://blogs.technet.com/b/heyscriptingguy/archive/2013/11/30/weekend-scripter-wmf-powershell-and-exchange-server-compatibility.aspx
http://blog.crayon.no/blogs/janegil/archive/2013/11/17/how_2D00_to_2D00_install_2D00_windows_2D00_powershell_2D00_4_2D00_0.aspx
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.
Gulab,
Where did you read that WMF3 is supported on Exchange 2010 SP3 on Server 2008 R2?
Neither of the links you pasted suggest that and in fact explicitly say "There has been no testing with ExchangeServer 2010 SP3 and WMF 3.0 installed on Windows Server 2008 R2."
My Bad, that was TYPO...
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.

Exchange 2010 SP1 Update Rollup 6 to Exchange 2010 SP3

Hi there,
I am planning to install Exchange 2010 SP3 next week and after reading some of the related comments on this site I got a little worried.
Our current Exchange environment consists of the following:
1 x CAS/HT Server
2 x Mailbox Server (members of a DAG)
The OS of the 3 servers is Windows Server 2008 R2 SP1. All servers are running Exchange 2010 SP1 Update Rollup 6.
The Execution Policies on our Exchange servers are set as follows:
– CAS/HT Server:
Scope ExecutionPolicy
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined
CurrentUser Undefined
LocalMachine Unrestricted
– Mailbox Servers:
Scope ExecutionPolicy
MachinePolicy Undefined
UserPolicy Undefined
Process Undefined
CurrentUser Undefined
LocalMachine RemoteSigned
Please note that we do not have any Group Policies that defined the PowerShell script execution policy.
I would be very grateful if you (or any of the kind readers) could help me with following questions:
1- Do I have to change the execution policy on our Exchange servers before installing SP3? If I have to change a policy, what should I change? And how would you recommend I should do this?
2- After installing SP3 on a server, can I install the latest rollup update on this server before moving to the next server? For example, can I do the following:
i. Install SP3 followed by RU 5 on the CAS/HT server -> Apply the our custom settings
ii. Install SP3 followed by RU 5 on the first mailbox server
iii. Install SP3 followed by RU 5 on the second mailbox server
Many thanks,
M

Hi Amit,
Many thanks for the swift reply.
That's correct. We didn't set the Powershell execution policy via Group Policy. We only configured the execution policy of "LocalMachine" to "Unrestricted" on the CAS/HT server using the "Set-ExecutionPolicy" command on the server.
The mailbox servers' execution policies have not been changed and are set to those values by default.
I must admit, I go event more confused when I read the "http://support.microsoft.com/kb/2668686" and "http://support.microsoft.com/kb/2810617" articles.
But it looks like I shouldn't worry as our current Powershell execution policies shouldn't affect the upgrade. Right?

Exchange 2010 SP3 Rollup Update 6

Our Exchange environment is currently on Exchange 2010 SP3 RU3 and the Forefront Protection 2010 for Exchange server version is 11.0.713.0 (Rollup 3).
We planning to upgrade Exchange servers and install Exchange 2010 SP3 RU6, question which I have is it Mandatory to upgrade the Forefront Protection 2010 for Exchange server version is 11.0.727.0 (Rollup 4) before we install Exchange 2010 SP3 RU6 on the
Exchange servers.
Thanks,
AJ

Thanks Adam for the prompt response and yes I recall these cmdlets to disable and there is a similar cmdlet to enable it. Also after Exchange 2010 SP2 after some RU there is no need to disable FPE before installing RU however it is recommended to disable
it.
If you refer the comments section mentioned in the blog below it talks about it:-
http://blogs.technet.com/b/exchange/archive/2014/05/27/released-update-rollup-6-for-exchange-2010-service-pack-3.aspx
If you read the comment posted by James Knoch posted on this blog which is as below,
SP3 & the Rollup Updates are not supposed to require you to disable Forefront anymore, but it doesn't hurt to be safe and disable/enable it anyways. Make sure you are running Forefront Rollup 4 (http://support.microsoft.com/kb/2619883)
& the latest security update (http://www.microsoft.com/en-us/download/details.aspx?id=41836).
Above stated confused me a bit, is it mandatory to upgrade Forefront or it is NOT.
Thanks,
AJ

Opportunistic TLS between our Exchange 2010 SP3 on Premise (WIth Edge) and Exchange Online Protection.

Similar Messages

Maybe you are looking for