<?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 Menu in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/menu/m-p/3209972#M550</link>
    <description>I am looking for some advice on best practice to implement a menu based system to deploy OS's to different hardware platforms. &lt;BR /&gt;&lt;BR /&gt;I have created a number of unattended install jobs (based on different hardware) and several modular based configuration, application install and security jobs to modify the default Windows install. &lt;BR /&gt;&lt;BR /&gt;My question: &lt;BR /&gt;&lt;BR /&gt;How can I distribute the unattended install as well as the appropriate jobs to a new server based on the hardware platform. &lt;BR /&gt;&lt;BR /&gt;e.g. New HP BL20p running Windows 2000 - User chooses "BL20p (win2000)" config from a menu system and the appropriate jobs start executing in sequence. &lt;BR /&gt;&lt;BR /&gt;I have seen that Altiris doesn't recommend the "Initial Deployment" method for systems above 10 computers. &lt;BR /&gt;&lt;BR /&gt;I have also had a bit of a play with Virtual PCs but my first attempt seemed to put the client into a infinite reboot cycle after running the first job (unattended install). &lt;BR /&gt;&lt;BR /&gt;Any thoughts/ideas/recommendations? &lt;BR /&gt;&lt;BR /&gt;Regards, &lt;BR /&gt;&lt;BR /&gt;Geoff.</description>
    <pubDate>Thu, 04 Mar 2004 16:14:05 GMT</pubDate>
    <dc:creator>Geoff Durham</dc:creator>
    <dc:date>2004-03-04T16:14:05Z</dc:date>
    <item>
      <title>Menu</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/menu/m-p/3209972#M550</link>
      <description>I am looking for some advice on best practice to implement a menu based system to deploy OS's to different hardware platforms. &lt;BR /&gt;&lt;BR /&gt;I have created a number of unattended install jobs (based on different hardware) and several modular based configuration, application install and security jobs to modify the default Windows install. &lt;BR /&gt;&lt;BR /&gt;My question: &lt;BR /&gt;&lt;BR /&gt;How can I distribute the unattended install as well as the appropriate jobs to a new server based on the hardware platform. &lt;BR /&gt;&lt;BR /&gt;e.g. New HP BL20p running Windows 2000 - User chooses "BL20p (win2000)" config from a menu system and the appropriate jobs start executing in sequence. &lt;BR /&gt;&lt;BR /&gt;I have seen that Altiris doesn't recommend the "Initial Deployment" method for systems above 10 computers. &lt;BR /&gt;&lt;BR /&gt;I have also had a bit of a play with Virtual PCs but my first attempt seemed to put the client into a infinite reboot cycle after running the first job (unattended install). &lt;BR /&gt;&lt;BR /&gt;Any thoughts/ideas/recommendations? &lt;BR /&gt;&lt;BR /&gt;Regards, &lt;BR /&gt;&lt;BR /&gt;Geoff.</description>
      <pubDate>Thu, 04 Mar 2004 16:14:05 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/menu/m-p/3209972#M550</guid>
      <dc:creator>Geoff Durham</dc:creator>
      <dc:date>2004-03-04T16:14:05Z</dc:date>
    </item>
    <item>
      <title>Re: Menu</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/menu/m-p/3209973#M551</link>
      <description>Look at the SYSTYPE utility.  It's documented in ssstkug.pdf in the deploy\tools\ssst directory on your RDP server.</description>
      <pubDate>Fri, 05 Mar 2004 07:09:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/menu/m-p/3209973#M551</guid>
      <dc:creator>Ken Henault</dc:creator>
      <dc:date>2004-03-05T07:09:07Z</dc:date>
    </item>
  </channel>
</rss>

