<?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>topic VCRM Communications in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/vcrm-communications/m-p/3514677#M11004</link>
    <description>What is the basic communications scheme utilized by VCRM when pushing firmware updates to managed servers?</description>
    <pubDate>Wed, 30 Mar 2005 14:56:24 GMT</pubDate>
    <dc:creator>Fabrice Corbatto</dc:creator>
    <dc:date>2005-03-30T14:56:24Z</dc:date>
    <item>
      <title>VCRM Communications</title>
      <link>https://community.hpe.com/t5/server-management-systems/vcrm-communications/m-p/3514677#M11004</link>
      <description>What is the basic communications scheme utilized by VCRM when pushing firmware updates to managed servers?</description>
      <pubDate>Wed, 30 Mar 2005 14:56:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/vcrm-communications/m-p/3514677#M11004</guid>
      <dc:creator>Fabrice Corbatto</dc:creator>
      <dc:date>2005-03-30T14:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: VCRM Communications</title>
      <link>https://community.hpe.com/t5/server-management-systems/vcrm-communications/m-p/3514678#M11005</link>
      <description>The transfer is done via HTTPS and is actually a pull (HTTP GET) done by the VCA, acting as a client.</description>
      <pubDate>Wed, 30 Mar 2005 16:59:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/vcrm-communications/m-p/3514678#M11005</guid>
      <dc:creator>Keith Rogers</dc:creator>
      <dc:date>2005-03-30T16:59:27Z</dc:date>
    </item>
  </channel>
</rss>

