<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>dag</title><link>https://evotec.xyz/es/tags/dag/</link><description>Evotec</description><atom:link href="https://evotec.xyz/es/tags/dag/index.xml" rel="self" type="application/rss+xml" /><item><title>GFI MailEssentials – License counting explained</title><link>https://evotec.xyz/es/blog/gfi-mail-essentials-license-counting-explained/</link><description>If you follow our Technical Hub you may have seen our earlier entry about counting GFI licenses. At that time…</description><pubDate>Mon, 08 Aug 2016 20:06:38 GMT</pubDate><guid>https://evotec.xyz/es/blog/gfi-mail-essentials-license-counting-explained/</guid><category>dag</category><category>Exchange</category><category>exchange 2010</category><category>exchange 2013</category><category>exchange 2016</category><category>gfi</category><category>gfi antispam</category><category>gfi mail essentials 20</category><category>license</category><category>licenses</category></item><item><title>The Microsoft Exchange Replication service does not appear to be running on Exchange Server</title><link>https://evotec.xyz/es/blog/the-microsoft-exchange-replication-service-does-not-appear-to-be-running-on-exchange-server/</link><description>This Exchange DAG error can appear even when the replication service is running, so it is worth checking Exchange permissions and group membership instead of stopping at service state alone.</description><pubDate>Sun, 22 Mar 2015 21:22:20 GMT</pubDate><guid>https://evotec.xyz/es/blog/the-microsoft-exchange-replication-service-does-not-appear-to-be-running-on-exchange-server/</guid><category>dag</category><category>evotec</category><category>Exchange</category><category>exchange 2010</category><category>exchange 2013</category><category>exchange dag</category><category>exchange replication</category></item><item><title>Exchange 2013 SP1 – The fully qualified domain name for node ‘DAG-EX2013’ could not be found.</title><link>https://evotec.xyz/es/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/</link><description>If Exchange DAG operations fail because the fully qualified domain name for a DAG node cannot be found, check the DAG computer object and its dNSHostName attribute in Active Directory.</description><pubDate>Sat, 14 Mar 2015 17:11:28 GMT</pubDate><guid>https://evotec.xyz/es/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/</guid><category>dag</category><category>dag problem</category><category>evotec</category><category>Exchange</category><category>exchange 2013</category><category>exchange 2013 dag</category><category>exchange 2013 sp1</category><category>microsoft</category><category>microsoft exchange server</category></item></channel></rss>