ForeFront Protection for Exchange (FPE) is the Microsoft solution to secure Exchange 2010 On Premise servers. ForeFront Online Protection for Exchange (FOPE) is the FPE implementation to secure Exchange Online mailboxes. If your already have already deployed Exchange 2010 and FPE within your organization, and are starting Office 365 evaluation with mailboxes hosted Online, you
As there are many question on ‘How can I use Office 365 for hosting email as I have another web hosting provider?’, here is a quick step by step. The first thing is to logon onto the Office 365 administration portal (https://portal.microsoftonline.com/) On the left part, go to Management\Domains Then click on the Add domain
Office 365 – Use Office 365 for email hosting only Read More »
As part of the Microsoft Online Services, you have ForeFront Online Protection for Exchange to secure your Exchange Online mailboxes. As Online Services is going to move to 2010 products version, FOPE is going to be updated too. The new version (in beta as well as Office 365) is FOPE 1.1 released on March 2011.
With Exchange Online 2010 (Office 365) you can create and manage Unified Messaging (UM) by creating UM dial plan, configuring ‘on premise’ UM gateway…. Unfortunately, you can’t delete the UM dial plan even if it has not been associated or used.
Office 365 – Exchange – Be careful with UM Read More »
Recently, I started to configure my Exchange 2010 Server as UM server. To do that, I’m using Trixbox as a software IPBX. I successfully configured my IPBX as well the Exchange UM role (dial plan, user UM enabled…). During my test I was able to reach the Exchange auto attendant or leave voice message, but
Exchange – Voice message are not delivered into user mailbox Read More »
If you published your Exchange 2010 services (OWA, Outlook Anywhere, EAS…) using ForeFront Unified Access Gateway (ForeFront UAG), you may have trouble with Outlook Anywhere after you deployed the Service Pack 1 for Exchange. Indeed, Exchange Web Services and Autodiscover Service may not work anymore when connected remotely. The first thing is to check if
Exchange / UAG – Exchange publication using ForeFront UAG Read More »
If you are using Outlook 2010 and Exchange 2010, you may have experimented this. Your mailbox name show on top of your mailbox folders tree is showing your email address instead of your display name. After doing some research, I found nothing which could explain that, except maybe the autodiscover process. Indeed, the autodiscover process
Exchange 2010 / Outlook 2010 – Mailbox name show the email address Read More »
to continue my series about publishing internal resources with ForeFront UAG, here is a post about publishing Exchange 2010 – more specifically publishing Exchange Autodiscover and Exchange Web Services. This has been already covered by Microsoft through TechNet and a White Paper BUT details provided are not true or not complete. Indeed, if you follow
Exchange / ForeFront UAG – Publishing Exchange 2010 with UAG Read More »
With Exchange 2010, users are able to get POP and IMAP settings from OWA. But to provide these information, you have to publish it. To publish POP/IMAP settings on OWA, you have to run the following Exchange CMDLets: get-receiveconnector set-popsettings –ExternalConnectionSettings “<POP address>:110:TLS” set-receiveconnector –identity “<SMTP client settings>” -AdvertiseClientSettings:$true Where <POP address> has to
Exchange – Publish POP/IMAP settings on OWA Read More »
After publishing Exchange Server 2010 SP1 (particularly Outlook Anywhere), you may have the following event logged on the Application event log in your UAG server: Log Name: Application Source: Microsoft Forefront UAG Date: 21/11/2010 20:24:14 Event ID: 24 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: <UAG Server> Description: The request from user
UAG – Exchange 2010 SP1 publication Read More »
