<?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 Re: Version Control Repository in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883103#M44877</link>
    <description>see previous post.</description>
    <pubDate>Tue, 01 Feb 2005 10:58:35 GMT</pubDate>
    <dc:creator>Vincent Roodenburg</dc:creator>
    <dc:date>2005-02-01T10:58:35Z</dc:date>
    <item>
      <title>Version Control Repository</title>
      <link>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883100#M44874</link>
      <description>I've installed HP SIM today. During the install i've configured a path for the repository. When I want to deploy a Proliant Support Pack to a server (which i've unzipped to the specified "repository" folder) it says "There are no Support Packs in this catalog." &lt;BR /&gt;How do I "fill" the repository with support packs ?</description>
      <pubDate>Mon, 31 Jan 2005 11:37:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883100#M44874</guid>
      <dc:creator>Vincent Roodenburg</dc:creator>
      <dc:date>2005-01-31T11:37:15Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control Repository</title>
      <link>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883101#M44875</link>
      <description>You shouldn't need to but you can "Scan" the catalogue.&lt;BR /&gt;From the Links Tab of the Server that has the VCRM go to the VCRM and there's a Scan Option.&lt;BR /&gt;But check the Repository structure.&lt;BR /&gt;I point my VCRM to d:\VCRM and then have a number of sub-direstories that contain different Softpaqs etc. below that. It just makes Management a bit easier.&lt;BR /&gt;You should see a corresponding .mnf file for each cpxxxxx.exe file when VCRM correctly scans and catalogues the repository.</description>
      <pubDate>Mon, 31 Jan 2005 13:59:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883101#M44875</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2005-01-31T13:59:04Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control Repository</title>
      <link>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883102#M44876</link>
      <description>It worked out all by itself. It might took some time for the system to create an index (i think) Thanks anyway !</description>
      <pubDate>Tue, 01 Feb 2005 10:57:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883102#M44876</guid>
      <dc:creator>Vincent Roodenburg</dc:creator>
      <dc:date>2005-02-01T10:57:33Z</dc:date>
    </item>
    <item>
      <title>Re: Version Control Repository</title>
      <link>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883103#M44877</link>
      <description>see previous post.</description>
      <pubDate>Tue, 01 Feb 2005 10:58:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/version-control-repository/m-p/4883103#M44877</guid>
      <dc:creator>Vincent Roodenburg</dc:creator>
      <dc:date>2005-02-01T10:58:35Z</dc:date>
    </item>
  </channel>
</rss>

