{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "dag",
  "home_page_url": "https://evotec.xyz/es/tags/dag/",
  "feed_url": "https://evotec.xyz/es/tags/dag/index.feed.json",
  "description": "Evotec",
  "items": [
    {
      "id": "https://evotec.xyz/es/blog/gfi-mail-essentials-license-counting-explained/",
      "url": "https://evotec.xyz/es/blog/gfi-mail-essentials-license-counting-explained/",
      "title": "GFI MailEssentials \u2013 License counting explained",
      "summary": "If you follow our Technical Hub you may have seen our earlier entry about counting GFI licenses. At that time\u2026",
      "date_published": "2016-08-08T20:06:38.0000000Z",
      "tags": [
        "dag",
        "Exchange",
        "exchange 2010",
        "exchange 2013",
        "exchange 2016",
        "gfi",
        "gfi antispam",
        "gfi mail essentials 20",
        "license",
        "licenses"
      ]
    },
    {
      "id": "https://evotec.xyz/es/blog/the-microsoft-exchange-replication-service-does-not-appear-to-be-running-on-exchange-server/",
      "url": "https://evotec.xyz/es/blog/the-microsoft-exchange-replication-service-does-not-appear-to-be-running-on-exchange-server/",
      "title": "The Microsoft Exchange Replication service does not appear to be running on Exchange Server",
      "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.",
      "date_published": "2015-03-22T21:22:20.0000000Z",
      "tags": [
        "dag",
        "evotec",
        "Exchange",
        "exchange 2010",
        "exchange 2013",
        "exchange dag",
        "exchange replication"
      ]
    },
    {
      "id": "https://evotec.xyz/es/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/",
      "url": "https://evotec.xyz/es/blog/exchange-2013-sp1-the-fully-qualified-domain-name-for-node-dag-ex2013-could-not-be-found/",
      "title": "Exchange 2013 SP1 \u2013 The fully qualified domain name for node \u2018DAG-EX2013\u2019 could not be found.",
      "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.",
      "date_published": "2015-03-14T17:11:28.0000000Z",
      "tags": [
        "dag",
        "dag problem",
        "evotec",
        "Exchange",
        "exchange 2013",
        "exchange 2013 dag",
        "exchange 2013 sp1",
        "microsoft",
        "microsoft exchange server"
      ]
    }
  ]
}