<?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: BL460c &amp;amp; WS460c memory compatibility in BladeSystem - General</title>
    <link>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6840049#M27252</link>
    <description>&lt;P&gt;Since the hardware is more or less identical, it should be no problem.&lt;/P&gt;&lt;P&gt;Depending on the graphics option you will need an expansion blade, this is unique to the workstation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DIP switch S9 off makes the box a server, S9=on a workstation (see user manual).&lt;/P&gt;</description>
    <pubDate>Tue, 08 Mar 2016 21:01:16 GMT</pubDate>
    <dc:creator>Torsten.</dc:creator>
    <dc:date>2016-03-08T21:01:16Z</dc:date>
    <item>
      <title>BL460c &amp; WS460c memory compatibility</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6839936#M27251</link>
      <description>&lt;P&gt;Hi guys.&lt;/P&gt;&lt;P&gt;We recently bought a bunch of BL460 G9s to replace a bunch of older servers.&amp;nbsp; We decided to use these for a VDI pilot, which went well overall.&amp;nbsp; However, we decided that to get better video performance, we wanted to get some nVidia Grid cards for the servers.&amp;nbsp; Much to our surprise, this would put us in an unsupported configuration!&amp;nbsp; We were told that the WS460 was what we should have bought, but it was too late.!&amp;nbsp; Recently, another group in our organization started planning for a project that will require a few servers for other uses.&amp;nbsp; We're thinking/hoping this will give us the opportunity we need.&amp;nbsp; This project will not be using the servers for virtualization, so they won't need nearly as much RAM as what's in our existing servers.&amp;nbsp; We would like to purchase some WS460s for VDI and repurpose the BL460s for the new project.&lt;/P&gt;&lt;P&gt;Is the RAM in the BL460 compatible with the WS460?&amp;nbsp; More importantly, will HP support us doing this?&lt;/P&gt;&lt;P&gt;Thanks in advancde for any advice!&lt;/P&gt;&lt;P&gt;Derek&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 17:03:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6839936#M27251</guid>
      <dc:creator>MaydayIT</dc:creator>
      <dc:date>2016-03-08T17:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: BL460c &amp; WS460c memory compatibility</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6840049#M27252</link>
      <description>&lt;P&gt;Since the hardware is more or less identical, it should be no problem.&lt;/P&gt;&lt;P&gt;Depending on the graphics option you will need an expansion blade, this is unique to the workstation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;DIP switch S9 off makes the box a server, S9=on a workstation (see user manual).&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2016 21:01:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6840049#M27252</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2016-03-08T21:01:16Z</dc:date>
    </item>
    <item>
      <title>Re: BL460c &amp; WS460c memory compatibility</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6840283#M27253</link>
      <description>&lt;P&gt;I know I sent this yesterday, but I guess it didn't post.&lt;/P&gt;&lt;P&gt;My intention is to run VMWare Horizon desktops on this.&amp;nbsp; To me, this makes it a server.&amp;nbsp; However, HP tends to have their own definitions.&amp;nbsp; Do I need an expansion blade for this type of configuration?&amp;nbsp; If so, is the expansion blade dedicated to a single server?&lt;/P&gt;&lt;P&gt;Thanks again for any help you can offer.&lt;/P&gt;&lt;P&gt;Derek&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 16:11:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6840283#M27253</guid>
      <dc:creator>MaydayIT</dc:creator>
      <dc:date>2016-03-09T16:11:09Z</dc:date>
    </item>
    <item>
      <title>Re: BL460c &amp; WS460c memory compatibility</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6840292#M27254</link>
      <description>&lt;P&gt;see quickspec for details:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www8.hp.com/h20195/v2/GetPDF.aspx/c04440152.pdf" target="_blank"&gt;http://www8.hp.com/h20195/v2/GetPDF.aspx/c04440152.pdf&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;there are&lt;/P&gt;&lt;P&gt;Mezzanine Graphics Adapters for single-width model&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;Full-size PCI Express Graphics Adapters for double-width model (Expansion Blade)&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2016 16:48:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6840292#M27254</guid>
      <dc:creator>Torsten.</dc:creator>
      <dc:date>2016-03-09T16:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: BL460c &amp; WS460c memory compatibility</title>
      <link>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6841382#M27255</link>
      <description>&lt;P&gt;Thanks Torsten!&amp;nbsp; Much appreciated!&lt;/P&gt;</description>
      <pubDate>Mon, 14 Mar 2016 15:35:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/bladesystem-general/bl460c-amp-ws460c-memory-compatibility/m-p/6841382#M27255</guid>
      <dc:creator>MaydayIT</dc:creator>
      <dc:date>2016-03-14T15:35:30Z</dc:date>
    </item>
  </channel>
</rss>

