<?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 Java on Windows Clients. in Insight Remote Support</title>
    <link>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891795#M3400</link>
    <description>Is it essential to have Java loaded on Windows 2000/2003 servers, or is it only needed if you want to access the ISEE client WEB page from that specific server.&lt;BR /&gt;Thanks&lt;BR /&gt;Marius</description>
    <pubDate>Fri, 18 Mar 2005 07:05:06 GMT</pubDate>
    <dc:creator>Marius Bower</dc:creator>
    <dc:date>2005-03-18T07:05:06Z</dc:date>
    <item>
      <title>Java on Windows Clients.</title>
      <link>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891795#M3400</link>
      <description>Is it essential to have Java loaded on Windows 2000/2003 servers, or is it only needed if you want to access the ISEE client WEB page from that specific server.&lt;BR /&gt;Thanks&lt;BR /&gt;Marius</description>
      <pubDate>Fri, 18 Mar 2005 07:05:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891795#M3400</guid>
      <dc:creator>Marius Bower</dc:creator>
      <dc:date>2005-03-18T07:05:06Z</dc:date>
    </item>
    <item>
      <title>Re: Java on Windows Clients.</title>
      <link>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891796#M3401</link>
      <description>I thought it was only needed at the client side, unless it is specifically needed by the server.</description>
      <pubDate>Fri, 18 Mar 2005 07:29:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891796#M3401</guid>
      <dc:creator>The Real MD</dc:creator>
      <dc:date>2005-03-18T07:29:38Z</dc:date>
    </item>
    <item>
      <title>Re: Java on Windows Clients.</title>
      <link>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891797#M3402</link>
      <description>Hi Martin,&lt;BR /&gt;Thanks for your response. Just to clear up. Are you saying that I do need to load the Java software on the client side to get the ISEE client to work?&lt;BR /&gt;The issue with loading the Java on windows clients is that the server needs a reboot. If the ISEE client can function without loading Java too it will mean less downtime on production servers.&lt;BR /&gt;&lt;BR /&gt;Marius</description>
      <pubDate>Fri, 18 Mar 2005 07:38:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891797#M3402</guid>
      <dc:creator>Marius Bower</dc:creator>
      <dc:date>2005-03-18T07:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: Java on Windows Clients.</title>
      <link>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891798#M3403</link>
      <description>I am saying you will need to install java on the client side.&lt;BR /&gt;&lt;BR /&gt;Regards&lt;BR /&gt;&lt;BR /&gt;Martin.</description>
      <pubDate>Fri, 18 Mar 2005 09:49:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891798#M3403</guid>
      <dc:creator>The Real MD</dc:creator>
      <dc:date>2005-03-18T09:49:00Z</dc:date>
    </item>
    <item>
      <title>Re: Java on Windows Clients.</title>
      <link>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891799#M3404</link>
      <description>Thanks</description>
      <pubDate>Sun, 29 May 2005 00:52:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/insight-remote-support/java-on-windows-clients/m-p/4891799#M3404</guid>
      <dc:creator>Marius Bower</dc:creator>
      <dc:date>2005-05-29T00:52:11Z</dc:date>
    </item>
  </channel>
</rss>

