<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Dominik Höfling on blog.atwork.at</title><link>https://blog.atwork.at/tags/dominik-h%C3%B6fling/</link><description>Recent content in Dominik Höfling on blog.atwork.at</description><generator>Hugo -- 0.153.4</generator><language>en-us</language><lastBuildDate>Wed, 10 Jan 2018 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.atwork.at/tags/dominik-h%C3%B6fling/index.xml" rel="self" type="application/rss+xml"/><item><title>Delegated Administration in Exchange Online</title><link>https://blog.atwork.at/post/2018/delegated-administration-in-exchange-online/</link><pubDate>Wed, 10 Jan 2018 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2018/delegated-administration-in-exchange-online/</guid><description>RBAC was introduced in Exchange 2010 to allow precise permission management within the Exchange organization for administrators and users. With RBAC, you can configure and control in a very granular way the administrative tasks that administrators or users can perform. RBAC controls both the administrative tasks that can be performed and the extent to which users can now administer their own mailbox and distribution groups. Understand that, with RBAC, it doesnt matter what Active Directory permissions you have when using Exchange management toolseverything is authorized and controlled via RBAC. You can define precisely which cmdlets and parameters a user can run or modify.</description></item><item><title>Troubleshooting Active Directory Federation Services</title><link>https://blog.atwork.at/post/2018/troubleshooting-active-directory-federation-services/</link><pubDate>Thu, 04 Jan 2018 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2018/troubleshooting-active-directory-federation-services/</guid><description>Keep in mind that your AD FS deployment is essential for your users to access Office 365 applications. Both internal and external users require a stable running AD FS environment. This guide will help you to troubleshoot some well-known AD FS issues.</description></item><item><title>Limitation of Exchange Hybrid Centralized Mail Transport</title><link>https://blog.atwork.at/post/2017/limitation-of-exchange-hybrid-centralized-mail-transport/</link><pubDate>Fri, 31 Mar 2017 00:00:00 +0000</pubDate><guid>https://blog.atwork.at/post/2017/limitation-of-exchange-hybrid-centralized-mail-transport/</guid><description>&lt;p&gt;I recently had a curious behavior in my customers Exchange 2010 SP3 hybrid environment with centralized mail transport for Exchange 2010 SP3 Edge servers enabled.&lt;/p&gt;
&lt;p&gt;Before I describe the topic in more detail I would like to say thank you to the guys from Microsoft: Timothy Heeney, Scott Landry and Tom Kern helped me with my ‘little’ mail flow problem . Appreciate your help. &lt;img loading="lazy" src="../../post/2017/limitation-of-exchange-hybrid-centralized-mail-transport/img_201.png" title="Smile"&gt;&lt;/p&gt;
&lt;p&gt;My customer is using a smtp gateway for external mail flow as usual. Some of the mailboxes have configured smtp forwarding like ForwardingAddress (mail contact) and ForwardingSMTPAddress (external smtp address directly set on the mailbox).&lt;/p&gt;</description></item></channel></rss>