<?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 F4 key through iLO on PXE configuration does not work in Server Management - Remote Server Management</title>
    <link>https://community.hpe.com/t5/server-management-remote-server/f4-key-through-ilo-on-pxe-configuration-does-not-work/m-p/4947929#M6123</link>
    <description>When going into the PXE (HP Ethernet Boot Agent) configuration through iLO (hit Ctrl-S during startup) I can change values, but the F4 key is not being recognized to save the changes.&lt;BR /&gt;&lt;BR /&gt;I have tried this on a couple of different servers (DL585, DL360, DL380) with no luck.  All the firmware for the servers and iLOs have been updated, I even tried changing the character set for the console, and it's still no good.&lt;BR /&gt;&lt;BR /&gt;The generic/universal NDIS (UNDI) driver used by PXE does not have the ability to set linkspeed/duplexing within the protocol.ini.&lt;BR /&gt;&lt;BR /&gt;I have to change this to match our switches (100/Full) or else RDP deployment is horribly slow.  We are trying to move away from ever having to attach a keyboard and monitor, and this is the last sticking point.  If anybody had any ideas, I'd appreciate it.  Thanks,&lt;BR /&gt;&lt;BR /&gt;Ian</description>
    <pubDate>Tue, 20 Dec 2005 12:48:32 GMT</pubDate>
    <dc:creator>Ian J Schwamberger</dc:creator>
    <dc:date>2005-12-20T12:48:32Z</dc:date>
    <item>
      <title>F4 key through iLO on PXE configuration does not work</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/f4-key-through-ilo-on-pxe-configuration-does-not-work/m-p/4947929#M6123</link>
      <description>When going into the PXE (HP Ethernet Boot Agent) configuration through iLO (hit Ctrl-S during startup) I can change values, but the F4 key is not being recognized to save the changes.&lt;BR /&gt;&lt;BR /&gt;I have tried this on a couple of different servers (DL585, DL360, DL380) with no luck.  All the firmware for the servers and iLOs have been updated, I even tried changing the character set for the console, and it's still no good.&lt;BR /&gt;&lt;BR /&gt;The generic/universal NDIS (UNDI) driver used by PXE does not have the ability to set linkspeed/duplexing within the protocol.ini.&lt;BR /&gt;&lt;BR /&gt;I have to change this to match our switches (100/Full) or else RDP deployment is horribly slow.  We are trying to move away from ever having to attach a keyboard and monitor, and this is the last sticking point.  If anybody had any ideas, I'd appreciate it.  Thanks,&lt;BR /&gt;&lt;BR /&gt;Ian</description>
      <pubDate>Tue, 20 Dec 2005 12:48:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/f4-key-through-ilo-on-pxe-configuration-does-not-work/m-p/4947929#M6123</guid>
      <dc:creator>Ian J Schwamberger</dc:creator>
      <dc:date>2005-12-20T12:48:32Z</dc:date>
    </item>
    <item>
      <title>Re: F4 key through iLO on PXE configuration does not work</title>
      <link>https://community.hpe.com/t5/server-management-remote-server/f4-key-through-ilo-on-pxe-configuration-does-not-work/m-p/4947930#M6124</link>
      <description>Sorry to take up space, but I found this is NOT an iLO issue per se.  The problem lies within Microsoft's JVM (Java Virtual Machine).  On a whim I downloaded and installed Sun's JRE, and configuring IE use the plugin instead of M$'s JVM closes this issue.  Maybe this can help somebody else from running in tight little circles.</description>
      <pubDate>Tue, 20 Dec 2005 14:12:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-remote-server/f4-key-through-ilo-on-pxe-configuration-does-not-work/m-p/4947930#M6124</guid>
      <dc:creator>Ian J Schwamberger</dc:creator>
      <dc:date>2005-12-20T14:12:02Z</dc:date>
    </item>
  </channel>
</rss>

