<?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: Automatically set Version Control Support Pack in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048354#M28648</link>
    <description>I'm struggling try to accomplish the same objective but I don't think it's possible.  There a lot of positing on this subject but none so far resulted in automating VCA agents setting distribution.  If anyone has had different results I would love to hear about that.  Not using HPâ  s RDP forces me to waste a lot of time clicking in SIM to roll out each server, quite counter-productive overall</description>
    <pubDate>Mon, 13 Aug 2007 09:50:21 GMT</pubDate>
    <dc:creator>Andrew Kwiecien</dc:creator>
    <dc:date>2007-08-13T09:50:21Z</dc:date>
    <item>
      <title>Automatically set Version Control Support Pack</title>
      <link>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048351#M28645</link>
      <description>I'm not sure if this is possible, however thought I would ask.&lt;BR /&gt;&lt;BR /&gt;At my firm we automate our server build process using Altiris. I have created a custom Support Pack and all this during the build process using \\server\share\setupc.exe /target:%computername% bcpaXXX.xml which correctly installs all the relevant bits on my servers.&lt;BR /&gt;&lt;BR /&gt;However after the build process is completed, I still have to manually open up Insight Manager, into the HP Version Control agent -&amp;gt; Change Agent Settings -&amp;gt; and then configure the "Reference Support Pack" to match my firm's standard one.&lt;BR /&gt;&lt;BR /&gt;Does anyone know a way of automating this? &lt;BR /&gt;&lt;BR /&gt;Any help appreciated.&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 02 Aug 2007 04:43:14 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048351#M28645</guid>
      <dc:creator>Fraser Dickson</dc:creator>
      <dc:date>2007-08-02T04:43:14Z</dc:date>
    </item>
    <item>
      <title>Re: Automatically set Version Control Support Pack</title>
      <link>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048352#M28646</link>
      <description>In hpsim you can choose configure then replicate agent settings. this will replicate the settings of a configured server to you new servers.&lt;BR /&gt;&lt;BR /&gt;In the new PSP 7.90 there is an option to configure certain installs. Hopefully if you configure and then run the setup then this should use the configured settings.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;seven</description>
      <pubDate>Thu, 02 Aug 2007 10:05:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048352#M28646</guid>
      <dc:creator>Steven Baillie</dc:creator>
      <dc:date>2007-08-02T10:05:57Z</dc:date>
    </item>
    <item>
      <title>Re: Automatically set Version Control Support Pack</title>
      <link>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048353#M28647</link>
      <description>You can pre-configure VCA component's settings before deploying to any target system using setupc.exe.&lt;BR /&gt;&lt;BR /&gt;you can pre-configure VCA Component,&lt;BR /&gt;1) Using VCRM's "configure a component" option.&lt;BR /&gt;or&lt;BR /&gt;2) Using HP Remote Deployment utility (setup.exe in SS 7.70 or less)</description>
      <pubDate>Mon, 06 Aug 2007 11:56:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048353#M28647</guid>
      <dc:creator>TechGuru</dc:creator>
      <dc:date>2007-08-06T11:56:46Z</dc:date>
    </item>
    <item>
      <title>Re: Automatically set Version Control Support Pack</title>
      <link>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048354#M28648</link>
      <description>I'm struggling try to accomplish the same objective but I don't think it's possible.  There a lot of positing on this subject but none so far resulted in automating VCA agents setting distribution.  If anyone has had different results I would love to hear about that.  Not using HPâ  s RDP forces me to waste a lot of time clicking in SIM to roll out each server, quite counter-productive overall</description>
      <pubDate>Mon, 13 Aug 2007 09:50:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048354#M28648</guid>
      <dc:creator>Andrew Kwiecien</dc:creator>
      <dc:date>2007-08-13T09:50:21Z</dc:date>
    </item>
    <item>
      <title>Re: Automatically set Version Control Support Pack</title>
      <link>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048355#M28649</link>
      <description>Looking for an answer on this myself. It is possible to configure the VCA agent to point at the VCRM and also provide it a password (i.e. using hpsum_config.exe to pre-configure the PSP prior to install) but i would also like to not have to run automated taks in HP SIM 5.2SP2 to set the VCA reference support pack! It's a pity HP haven't addressed this.&lt;BR /&gt;&lt;BR /&gt;:(</description>
      <pubDate>Tue, 21 Apr 2009 14:22:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048355#M28649</guid>
      <dc:creator>shocko</dc:creator>
      <dc:date>2009-04-21T14:22:18Z</dc:date>
    </item>
    <item>
      <title>Re: Automatically set Version Control Support Pack</title>
      <link>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048356#M28650</link>
      <description>The version control information is stored in a file called "C:\hp\hpsmh\data\cgi-bin\vcagent\VCAgent.Options".&lt;BR /&gt;&lt;BR /&gt;So what I do is configure a "gold system" with the support pack assignment I want, then copy the Options file to a location where a script grabs it and copies it to each machine I deploy the support pack to.&lt;BR /&gt;&lt;BR /&gt;I don't use Altiris, but I am guessing you can do the same with it.  In my case I just use the HPSUM utility to deploy the support pack silently and then in the same VBS/batch script file, I copy the Options file to the target.&lt;BR /&gt;&lt;BR /&gt;On Error Resume Next&lt;BR /&gt;&lt;BR /&gt;CmdLine1 = "cmd.exe /c DEL /Q"&lt;BR /&gt;CmdLine2 = """C:\Users\Public\Desktop\HP System Management Homepage.lnk"""&lt;BR /&gt;CmdLine = CmdLine1 &amp;amp; " " &amp;amp; CmdLine2&lt;BR /&gt;&lt;BR /&gt;Set WshShell = WScript.CreateObject("WScript.Shell")&lt;BR /&gt;intReturn = WshShell.Run("\\UNC_TO_Source_Files\hpsum.exe /use_latest /allow_non_bundle_components /use_snmp /use_wmi /express_install", 0, TRUE)&lt;BR /&gt;intReturn = WshShell.Run("regedit /S \\UNC_TO_Reg_File\RemoveCPQTEAM.reg", 0, TRUE)&lt;BR /&gt;intReturn = wshShell.Run("cmd.exe /c copy /y \\UNC_TO_Options_File\vcagent.options C:\hp\hpsmh\data\cgi-bin\vcagent", 0, True)&lt;BR /&gt;intReturn = WshShell.Run(CmdLine, 0, TRUE)&lt;BR /&gt;WshShell = NULL&lt;BR /&gt;&lt;BR /&gt;My Reg file removes the Teaming system tray application, which I don't want.&lt;BR /&gt;&lt;BR /&gt;Nelson</description>
      <pubDate>Tue, 21 Apr 2009 17:15:36 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/automatically-set-version-control-support-pack/m-p/4048356#M28650</guid>
      <dc:creator>NJK-Work</dc:creator>
      <dc:date>2009-04-21T17:15:36Z</dc:date>
    </item>
  </channel>
</rss>

