<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>vmEck Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>vmEck Tracker</description>
    <pubDate>Thu, 23 Nov 2023 16:54:32 GMT</pubDate>
    <dc:date>2023-11-23T16:54:32Z</dc:date>
    <item>
      <title>Re: How do I split two vCenter Servers in Enhanced Linked Mode?</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-do-I-split-two-vCenter-Servers-in-Enhanced-Linked-Mode/m-p/1764656#M57672</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You would use cmsso-util domain-repoint that we introduced in vSphere 6.7 to split the vCenter Servers apart - &lt;A href="https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vcenter.install.doc/GUID-C021F1DB-551A-4F73-8A38-437AE6D5CFEF.html" title="https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vcenter.install.doc/GUID-C021F1DB-551A-4F73-8A38-437AE6D5CFEF.html"&gt;Syntax of the Domain Repoint Command&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 14 Jul 2020 17:33:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-do-I-split-two-vCenter-Servers-in-Enhanced-Linked-Mode/m-p/1764656#M57672</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2020-07-14T17:33:24Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade &amp; Migrate from External PSC to Embedded</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Upgrade-Migrate-from-External-PSC-to-Embedded/m-p/468485#M5066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only thing I can really say is that the intention is to provide a path from external to embedded. So, do what makes sense for you now. Hopefully there is a migration path in the future.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Jul 2018 12:55:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Upgrade-Migrate-from-External-PSC-to-Embedded/m-p/468485#M5066</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2018-07-03T12:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade &amp; Migrate from External PSC to Embedded</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Upgrade-Migrate-from-External-PSC-to-Embedded/m-p/468481#M5062</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The only way to do this currently is to deploy a new vCenter Server. There is no way to migrate from external PSC to embedded PSC. But this is something we're working on so my recommendation is to upgrade to 6.7 and keep your external PSC rather then starting over with a new vCenter Server. The goal is to provide a migration path in the future.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 28 Apr 2018 15:19:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Upgrade-Migrate-from-External-PSC-to-Embedded/m-p/468481#M5062</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2018-04-28T15:19:29Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Server Appliance 6.7 Backup Solution</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-Server-Appliance-6-7-Backup-Solution/m-p/1385693#M44025</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;For just backing up vCenter Server, the built-in file-based backup is a simple way to maintain backups of your VCSA. For backing up other VMs you'll need something else.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 27 Apr 2018 14:14:33 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-Server-Appliance-6-7-Backup-Solution/m-p/1385693#M44025</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2018-04-27T14:14:33Z</dc:date>
    </item>
    <item>
      <title>Re: Validity Period of VMCA Certificates</title>
      <link>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Validity-Period-of-VMCA-Certificates/m-p/939648#M11077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure, the parameter is vpxd.certmgmt.certs.daysValid under vCenter Server &amp;gt; Configure &amp;gt; Advanced Settings&lt;span class="lia-inline-image-display-wrapper" image-alt="2018-04-26_15-08-35.png"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/81424i97B6D755CCF72299/image-size/large?v=v2&amp;amp;px=999" role="button" title="2018-04-26_15-08-35.png" alt="2018-04-26_15-08-35.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 19:10:15 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vSphere-Discussions/Validity-Period-of-VMCA-Certificates/m-p/939648#M11077</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2018-04-26T19:10:15Z</dc:date>
    </item>
    <item>
      <title>Re: VCSA 6.5 to VCSA 6.7 Upgrade Flex quits working</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-6-5-to-VCSA-6-7-Upgrade-Flex-quits-working/m-p/2727061#M39044</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What 3rd party plugins do you have installed? It is possible a plugin is incompatible and causing this issue. Are you able to access the HTML5 vSphere Client?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 19:01:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/VCSA-6-5-to-VCSA-6-7-Upgrade-Flex-quits-working/m-p/2727061#M39044</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2018-04-26T19:01:42Z</dc:date>
    </item>
    <item>
      <title>Re: Upgrade &amp; Migrate from External PSC to Embedded</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Upgrade-Migrate-from-External-PSC-to-Embedded/m-p/468479#M5060</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no way currently to migrate from external PSC to embedded PSC. This is something that is being worked on, though. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 26 Apr 2018 18:58:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Upgrade-Migrate-from-External-PSC-to-Embedded/m-p/468479#M5060</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2018-04-26T18:58:24Z</dc:date>
    </item>
    <item>
      <title>Re: VMmark 3 causing vCenter HA to fail over?</title>
      <link>https://communities.vmware.com/t5/VMware-VMmark-Discussions/VMmark-3-causing-vCenter-HA-to-fail-over/m-p/978357#M848</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What account is shutting down the vCenter Server VM? Could there be a configuration within VMmark that is set to automatically shut it down once testing is complete? If you destroy the VCHA cluster does it behave the same way (VC get's&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Feb 2018 18:21:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-VMmark-Discussions/VMmark-3-causing-vCenter-HA-to-fail-over/m-p/978357#M848</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2018-02-22T18:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: How do I split two vCenter Servers in Enhanced Linked Mode?</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-do-I-split-two-vCenter-Servers-in-Enhanced-Linked-Mode/m-p/1764646#M57662</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;William, is this fully supported by GSS and tested by QE?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Mar 2017 15:53:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-do-I-split-two-vCenter-Servers-in-Enhanced-Linked-Mode/m-p/1764646#M57662</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2017-03-13T15:53:14Z</dc:date>
    </item>
    <item>
      <title>Re: How do I split two vCenter Servers in Enhanced Linked Mode?</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-do-I-split-two-vCenter-Servers-in-Enhanced-Linked-Mode/m-p/1764642#M57658</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;No, backing up the VCDB and restoring it on its own is not supported in 6.x. The only supported way to backup/restore a vCenter Server is through an image-based backup.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Mar 2017 13:27:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-do-I-split-two-vCenter-Servers-in-Enhanced-Linked-Mode/m-p/1764642#M57658</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2017-03-13T13:27:08Z</dc:date>
    </item>
    <item>
      <title>Re: How do I split two vCenter Servers in Enhanced Linked Mode?</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-do-I-split-two-vCenter-Servers-in-Enhanced-Linked-Mode/m-p/1764640#M57656</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;There is no way to do this today without deploying a fresh vCenter Server in a new SSO Domain and then manually migrating the hosts and workloads. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Mar 2017 12:09:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/How-do-I-split-two-vCenter-Servers-in-Enhanced-Linked-Mode/m-p/1764640#M57656</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2017-03-13T12:09:10Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Upload ESXi image to VUM 6.5 (VCSA)</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-Upload-ESXi-image-to-VUM-6-5-VCSA/m-p/1397644#M19346</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Eric, I'm sharing this internally with some folks to see if we can get you an answer. Stay tuned and thanks for tagging us!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 06 Mar 2017 16:11:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Unable-to-Upload-ESXi-image-to-VUM-6-5-VCSA/m-p/1397644#M19346</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2017-03-06T16:11:50Z</dc:date>
    </item>
    <item>
      <title>Re: Failing: Migrating Windows vCenter 5.5 to vCSA 6.0U2 using 6.0U2M</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Failing-Migrating-Windows-vCenter-5-5-to-vCSA-6-0U2-using-6-0U2M/m-p/1365221#M17024</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You didn't mention your 5.5 SSO Instance was already in HA behind a LB so I'm not sure my thoughts are correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The Lookup Service now runs through the reverse proxy on 443 so 7444 is no longer a required port.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2017 03:08:08 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Failing-Migrating-Windows-vCenter-5-5-to-vCSA-6-0U2-using-6-0U2M/m-p/1365221#M17024</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2017-01-16T03:08:08Z</dc:date>
    </item>
    <item>
      <title>Re: Failing: Migrating Windows vCenter 5.5 to vCSA 6.0U2 using 6.0U2M</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Failing-Migrating-Windows-vCenter-5-5-to-vCSA-6-0U2-using-6-0U2M/m-p/1365219#M17022</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My guess is that this has to do with you reconfiguring the PSC into an HA pair behind a load balancer. vCenter still things it's SSO is the original converted PSC but you've configured that PSC to respond via the VIP of the load balancer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You may have to break the HA pair in order to get this to work.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2017 02:41:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/Failing-Migrating-Windows-vCenter-5-5-to-vCSA-6-0U2-using-6-0U2M/m-p/1365219#M17022</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2017-01-16T02:41:29Z</dc:date>
    </item>
    <item>
      <title>Re: how many esxi hosts need for run VCHA</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/how-many-esxi-hosts-need-for-run-VCHA/m-p/2739261#M39904</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can run it all on a single host but it is unsupported. A minimum of 3 hosts is required. If this was for production, running all 3 nodes on a single host would defeat the purpose of an HA solution. But, if this is just to test it in a lab environment Willam's post shows you how to do it with limited resources.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2017 02:36:10 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/how-many-esxi-hosts-need-for-run-VCHA/m-p/2739261#M39904</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2017-01-16T02:36:10Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter Server Appliance 6 HOSTNAME CHANGE</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Server-Appliance-6-HOSTNAME-CHANGE/m-p/2220166#M31000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We still don't have the ability to change the name of a vCenter Server or Platform Services Controller. It is being considered, though. This isn't as easy as it would seem and has many implications to not only vSphere but also anything else that is communicating to vCenter Server and PSCs. But many customers are asking for this and the team is aware of it.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jan 2017 13:53:22 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-Server-Appliance-6-HOSTNAME-CHANGE/m-p/2220166#M31000</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2017-01-05T13:53:22Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 6 Embedded PSC Question</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-Embedded-PSC-Question/m-p/490700#M6903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can always reconfigure from an embedded PSC to an external PSC if your DR site comes to fruition. With SRM, I believe an external PSC is recommended but I'd have to defer to the SRM folks for confirmation.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Dec 2016 18:11:51 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-Embedded-PSC-Question/m-p/490700#M6903</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2016-12-27T18:11:51Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 6 Embedded PSC Question</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-Embedded-PSC-Question/m-p/490699#M6902</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We don't know when exactly, but we do want to deprecate the Windows-based vCenter. In 6.0, the VCSA has feature and scale parity with Windows. The only exception is that VUM still requires&amp;nbsp; Windows. However, in 6.5, the VCSA has surpassed Windows in features and performance while VUM has been integrated into the appliance. I would not invest any more time in the Windows-installabel. The appliance model is the future.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 27 Dec 2016 18:10:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-Embedded-PSC-Question/m-p/490699#M6902</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2016-12-27T18:10:45Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 6 Embedded PSC Question</title>
      <link>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-Embedded-PSC-Question/m-p/490696#M6899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the decision tree doesn't answer you question let me know. I'm working on the 6.5 update and would certainly like to incorporate any feedback.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It really boils down to 1 question - Do you need Enhanced Linked Mode? It sounds like you don't right now but might in the future. The thing is, there's no way to merge or otherwise combine two different SSO Domains (at least not as of today). So, I wouldn't add the complexity of an external PSC if you don't need it today. So, with the limited information we have, I'd say stick with embedded PSC.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Dec 2016 17:13:46 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-vCenter-Discussions/vCenter-6-Embedded-PSC-Question/m-p/490696#M6899</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2016-12-26T17:13:46Z</dc:date>
    </item>
    <item>
      <title>Re: vCenter 6.0 U2 appliance - PostgreSQL 'concerns'</title>
      <link>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-6-0-U2-appliance-PostgreSQL-concerns/m-p/2234798#M73601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You might start with a couple of my recent blog articles:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://blogs.vmware.com/vsphere/2016/03/getting-comfortable-with-vpostgres-and-the-vcenter-server-appliance-part-1.html" title="http://blogs.vmware.com/vsphere/2016/03/getting-comfortable-with-vpostgres-and-the-vcenter-server-appliance-part-1.html"&gt;Getting Comfortable with vPostgres and the vCenter Server Appliance - Part 1 - VMware vSphere Blog&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://blogs.vmware.com/vsphere/2016/05/getting-comfortable-with-vpostgres-and-the-vcenter-server-appliance-part-2.html" title="http://blogs.vmware.com/vsphere/2016/05/getting-comfortable-with-vpostgres-and-the-vcenter-server-appliance-part-2.html"&gt;Getting Comfortable with vPostgres and the vCenter Server Appliance – Part 2 - VMware vSphere Blog&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have follow up questions after starting with that let me know.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jun 2016 06:58:04 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/vCenter-Server-Discussions/vCenter-6-0-U2-appliance-PostgreSQL-concerns/m-p/2234798#M73601</guid>
      <dc:creator>vmEck</dc:creator>
      <dc:date>2016-06-08T06:58:04Z</dc:date>
    </item>
  </channel>
</rss>

