February 19, 2015 Dave Stork Exchange 2013, Issue, Lync, Office 365, OWA 3 comments

Issues with Unified Contact Store in combination with Lync on-premises and Exchange Online

I've encountered an issue that popped up while I was testing a move from Exchange On-premises to Exchange Online (EXO) while Lync Server 2013 remained on-premises due to Enterprise Voice. Outlook Web Access (OWA) from Exchange Online can be integrated with on-premises Lync, this way OWA users can see presence and have limited IM functionality just like what's possible if both products are on-premises. For this to work you'll need Lync Edge servers because OWA EXO will act as an

February 13, 2015 Dave Stork Active Directory, Exchange, Issue, Support, Update Leave a comment

Some things to do after leaving Windows Server 2003 (from an Exchange perspective)

Today the Exchange Team blog posted an article about upgrading the Domain Functional (DFL) level of your Active Directory environment away from Windows Server 2003 and the fact that raising the level might have some impact on your Exchange servers (and other applications). It is possible that they might not be able to authenticate. If you do run into issues after raising the DFL, the solution is either restarting the Kerberos Key Distribution Center service on all DC's or restarting all DC's

January 20, 2015 Dave Stork ActiveSync, Events, Exchange, Exchange 2013, OWA, Question of the day, Windows Phone / Mobile Devices Leave a comment

No, Windows Phone ActiveSync is not on par with OWA for Devices

Recently I came across this Twitter exchange: @WayneHRiddle You don't need it for WP. Native app handles all of that functionality. — Ben Rudolph (@BenThePCGuy) January 17, 2015 I've heard this argument before, that the Exchange ActiveSync (EAS) implementation in Windows Phone doesn't require an OWA for Devices app (or MOWA as is the official acronym) like iOS has (for iPad and iPhone) and what is currently in preview for Android. Although the Windows Phone 8 ActiveSync implementation doesn't have the

January 14, 2015 Dave Stork Exchange 2013, Issue, Lync, Management, Question of the day, Update Leave a comment

Do not update your Office Web Apps Server with automatic updates

Although it is not exactly required to deploy with Exchange Server 2013, Office Web Apps Server (OWAS or also referred to as WAC server) provides a more user friendly experience instead of the standard Web Preview. For Lync Server 2013 it's a requirement if you want to be able to present PowerPoint files in a conference. And well, for SharePoint Server it's just a given. So, it's not an uncommon server to encounter when you work with these products. However

December 9, 2014 Dave Stork Exchange, Exchange 2007, Exchange 2010, Exchange 2013, Update Leave a comment

Exchange 2013 CU7, Exchange 2010 SP3 RU8 and Exchange 2007 SP3 RU15 are out!

Update 12 december 2014: The fixed Exchange 2010 SP3 RU8 with v2 is now available. Same location as the plagued v1. Update 10 december 2014: Exchange Server 2010 SP3 RU8 has been pulled due to connectivity issues with Outlook. There is currently not ETA on the fix. Customers are advised to not install this RU8 or remove RU8 if they already installed it. The initial Exchange Team blog post has been amended with this new info. As of now no other

December 7, 2014 Dave Stork Personal Leave a comment

A new blog backend

The past few months Sander Berkouwer (MVP and admin for dirteam.com) worked hard to get our new blogsite up and running. We had an ancient Telligent (now Zimbra) Community Server, which was limited and didn't provide new and interesting features. So, we decided to move towards WordPress 4. Luckily we could migrate most of our blog posts and comments from Community Server to WordPress. Also, the main link to get to this blog has changed from http://blogs.dirteam.com/blogs/davestork to https://dirteam.com/dave, which

November 19, 2014 Dave Stork Exchange, Management, Office 365 One comment

Mail address sieve and Exchange

During a discussion about fighting spam, a coworker mentioned an interesting Gmail feature. As that service doesn't provide aliasses, you can't have a specific mail address alias for your internet services. Some use a different email address for each service they sign up for, a practice which is understandable with some services that (sometimes illegally) opt-in bulk mailings or more nefarious mailings. Whenever a specific alias receives unwanted mails, you can see where it came from and take direct action

August 26, 2014 Dave Stork Exchange 2013, Issue, Update Leave a comment

Mail enabled Public Folders on Exchange 2013 CU6 require action for internet mail to be received

So, CU6 is out. It’s easy to overlook the change mentioned within the Exchange 2013 Release Notes. And you might have missed the Exchange Team blog post about all Public Folder changes with CU6. And it might not be relevant for your situation. But I know certain customers rely on mail enabled Public Folders that are able to receive internet mail and are now on Exchange 2013. Sometimes it’s not practical to change those Public Folders to a Shared Mailbox.

August 26, 2014 Dave Stork Exchange 2007, Exchange 2010, Exchange 2013, Update Leave a comment

Released: Exchange 2013 CU6, Exchange 2010 SP3 RU7 and Exchange 2007 SP3 RU14

Today Microsoft released the 6th update to Exchange Server 2013, aptly named Cumulative Update 6 (CU6), the seventh update to Exchange Server 2010 SP3; Rollup Update 7 (RU7) and the 14th update to Exchange Server 2007 SP3 named Rollup Update 14 (RU14). They mostly contain smaller security fixes and/or bug fixes or DST (Daylight Saving Time) updates. Having said that, the most eagerly awaited and important fixes in Exchange Server 2013 CU6 include: Hybrid Configuration Wizard fix for Exchange 2013

August 15, 2014 Dave Stork Issue, Office 365 11 comments

Fixing Office 365 DirSync account matching issues

Recently I had to fix some issues with DirSync. For some reason (there were some cloud users created before DirSync was enabled) there were duplicate users, because DirSync failed to match the already present cloud user and the corresponding AD (Active Directory) user. There were also accounts that failed to sync and thus failed to sync all attributes properly. If there is already a cloud account and there is need for a synced account, you can create an AD account

« 1 … 3 4 5 6 7 … 20 »