<feed xmlns="http://www.w3.org/2005/Atom"><title>dag</title><id>https://evotec.xyz/es/tags/dag/index.atom.xml</id><updated>2016-08-08T20:06:38.0000000Z</updated><subtitle>Evotec</subtitle><link href="https://evotec.xyz/es/tags/dag/" /><link href="https://evotec.xyz/es/tags/dag/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>GFI MailEssentials – License counting explained</title><id>https://evotec.xyz/es/blog/gfi-mail-essentials-license-counting-explained/</id><link href="https://evotec.xyz/es/blog/gfi-mail-essentials-license-counting-explained/" /><updated>2016-08-08T20:06:38.0000000Z</updated><summary>If you follow our Technical Hub you may have seen our earlier entry about counting GFI licenses. At that time…</summary><category term="dag" /><category term="Exchange" /><category term="exchange 2010" /><category term="exchange 2013" /><category term="exchange 2016" /><category term="gfi" /><category term="gfi antispam" /><category term="gfi mail essentials 20" /><category term="license" /><category term="licenses" /></entry><entry><title>The Microsoft Exchange Replication service does not appear to be running on Exchange Server</title><id>https://evotec.xyz/es/blog/the-microsoft-exchange-replication-service-does-not-appear-to-be-running-on-exchange-server/</id><link href="https://evotec.xyz/es/blog/the-microsoft-exchange-replication-service-does-not-appear-to-be-running-on-exchange-server/" /><updated>2015-03-22T21:22:20.0000000Z</updated><summary>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.</summary><category term="dag" /><category term="evotec" /><category term="Exchange" /><category term="exchange 2010" /><category term="exchange 2013" /><category term="exchange dag" /><category term="exchange replication" /></entry><entry><title>Exchange 2013 SP1 – The fully qualified domain name for node ‘DAG-EX2013’ could not be found.</title><id>https://evotec.xyz/es/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/</id><link href="https://evotec.xyz/es/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/" /><updated>2015-03-14T17:11:28.0000000Z</updated><summary>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.</summary><category term="dag" /><category term="dag problem" /><category term="evotec" /><category term="Exchange" /><category term="exchange 2013" /><category term="exchange 2013 dag" /><category term="exchange 2013 sp1" /><category term="microsoft" /><category term="microsoft exchange server" /></entry></feed>