Items related to messaging services with a focus on Exchange Online (EXO) and Exchange server (on-premises)
The session recordings from last weeks Microsoft Ignite conference are available for download. The recorded videos and slides (where applicable) are to be found on the Ignite page. Some recommended Exchange sessions are below and a tool to assist with downloading multiple sessions is noted at the end.
The list below are some of the sessions that I&r… Read the rest “Microsoft Ignite 2015 Sessions Now Available”
Since Exchange servers are now storing an ever increasing amount of data, it is imperative that people can quickly search and retrieve the content from their mailbox. This may have been possible without search capabilities in the past with a 20 MB mailbox quota (remember those days ?!?), but as quotas move to double gigabyte figures effective search is a hard requirement.
Exchange Search is a diffe… Read the rest “Troubleshooting Exchange 2010 Search”
Upon launching Outlook and trying to connect to an Office 365 mailbox you may be greeted with an error message which states that “Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened”. The error then continues to state that ”Microsoft Exchange is not available. Either there are network problems or the Exchange… Read the rest “Office 365 Error – Cannot Start Microsoft Outlook–Quick Check”
Deploying an Exchange Hybrid solution offers many opportunities to extend messaging services into the cloud. This is one of the biggest strengths of the Microsoft offering. We can provide on-premises, cloud only and hybrid solutions.
One capability is cloud based archives. This allows either:
This p… Read the rest “Enable Remote Archive With Exchange Hybrid”
Update 12-1-2022 Please see this post which covers the newer Outlook client logic. Content below will be left as-is for a historical perspective.
This is a post for reference purposes. The intent is to look at how Outlook will locate the correct Autodiscover endpoint in a hybrid environment. This Exchange 2010 SP3 lab has a hybrid configuration with Office 365. The tenant is called TailspinToysC… Read the rest “Office 365 Autodiscover Lookup Process”
This is in response to a engagement where the admins were puzzled that they could not create a public folder calendar in Exchange 2013. That is something that we should be able to do.
Why were they not able to do so?
To creating the public folder calendar, we need to use Outlook. This is the same as Exchange 2010, so no differences there.
What was stumping them was, when they went to Outl… Read the rest “How To Create Public Folder Calendar In Exchange 2013”
In the Tailspintoys environment, the administrator (moi) was a bit slack. They let the AD FS 2012 R2 proxy get into a bad state. The AD FS Proxy was not contacting the AD FS server on the internal network, and this allowed the short lived authentication certificate to expire. At this point the AD FS Proxy was “dead to me” as far as the AD FS server was concerned. The internal AD FS server was … Read the rest “AD FS 2012 R2 Web Application Proxy – Re-Establish Proxy Trust”
For users and devices that need to use DNS to locate their Exchange Autodiscover endpoint, should I use a SRV record?
The above is a fairly common question, and it almost warrants the consultant’s answer. It depends...
As discussed by Ross Smith IV in his introduction to Exchange 2013 CAS post, Exchange 2010 CAS Namespace planning typically requires multiple nam… Read the rest “DNS or SRV Record For DNS Based Exchange Autodiscover”
On an Exchange 2007 SP3 RU15 server, experienced an issue where the path statement on the Import-ExchangeCertificate cmdlet seemed to ignore what it was told to do….
The below PowerShell commands were used:
$Creds = Get-Credential
Import-ExchangeCertificate -Path .cert.pfx -Password $Creds.Password
Which generated an error stating “Import-ExchangeCertificate : The import file name .cert.pfx was not fo… Read the rest “Import-Exchange Certificate Ignores Path Provided”
We are now at the end of the Exchange 2013 RTM support lifecycle phase. Yes, it really has been two years since Exchange 2013 was released…..
At this time Exchange 2013 RTM, CU1, CU2 and CU3 are no longer supported. Customers should be on a recent Exchange 2013 build. Exchange 2013 CU4 is also known as SP1.
Whilst the servicing strategy for Exchange 2013 changed compared to E… Read the rest “End Of Exchange 2013 RTM Support”