<?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: RDP imaging problem in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625155#M2289</link>
    <description>The PXE files?  You'll need to edit 2 files.  Did you also re-create the PXE images?  What steps did you take?</description>
    <pubDate>Wed, 14 Sep 2005 08:47:30 GMT</pubDate>
    <dc:creator>Gordon Leonard</dc:creator>
    <dc:date>2005-09-14T08:47:30Z</dc:date>
    <item>
      <title>RDP imaging problem</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625150#M2284</link>
      <description>I have a new RDP server set up, v 2.1.  After creating a bootworks boot disk, I get the error shown in the attached file.  We have no PXE server setup.  Client is not in the same domain.  I have talked with Compaq on the phone, and we pretty much just figured out, after 2 hours, that "we are using the correct driver." Any help on this would be greatly appreciated.</description>
      <pubDate>Tue, 13 Sep 2005 15:34:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625150#M2284</guid>
      <dc:creator>Torrey_1</dc:creator>
      <dc:date>2005-09-13T15:34:03Z</dc:date>
    </item>
    <item>
      <title>Re: RDP imaging problem</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625151#M2285</link>
      <description>Torrey:&lt;BR /&gt;&lt;BR /&gt;It looks like either a Name Resolution problem or a type in your boot image.&lt;BR /&gt;&lt;BR /&gt;AT that point in the boot process, I believe the server is tryign to attach to the source server, ans as you can see.. it can not find the NETBIOS name on the network.  Eoither the name has a typo in it (somehow), or perhaps you can edit your boot files to try to attach to the IP address of the image server instead of the NETBIOS name...&lt;BR /&gt;&lt;BR /&gt;I.E..&lt;BR /&gt;&lt;BR /&gt;\\IMAGESERVER\SHARENAME&lt;BR /&gt;vs.&lt;BR /&gt;\\192.168.182.13\SHARENAME (making believe that the IP address stated is your RDP or Image server.&lt;BR /&gt;&lt;BR /&gt;Look for the NET USE command in your autoexec.bat file in the boot image.&lt;BR /&gt;&lt;BR /&gt;Could be DNS related as well.  Is the DNS server the client using the same as the RDP/Image server?  If not, you can try specifying in your DHCP server scope options, the DNS server that RDP is using.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Steven</description>
      <pubDate>Tue, 13 Sep 2005 16:56:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625151#M2285</guid>
      <dc:creator>Steven Clementi</dc:creator>
      <dc:date>2005-09-13T16:56:10Z</dc:date>
    </item>
    <item>
      <title>Re: RDP imaging problem</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625152#M2286</link>
      <description>Steven,&lt;BR /&gt;&lt;BR /&gt;Thanks for your response. I'll try these out.&lt;BR /&gt;&lt;BR /&gt;The DNS server is a different server. A this point, I have only tried using the IP address, not the NETBIOS name.&lt;BR /&gt;&lt;BR /&gt;I am also trying to set up an additional RDP server in the environment the client servers are located.  Do you think this will help?</description>
      <pubDate>Tue, 13 Sep 2005 18:35:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625152#M2286</guid>
      <dc:creator>Torrey_1</dc:creator>
      <dc:date>2005-09-13T18:35:43Z</dc:date>
    </item>
    <item>
      <title>Re: RDP imaging problem</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625153#M2287</link>
      <description>Modify the LMHOST file on both PXE images by adding an entry for the RDP server.  Then re-create the PXE images.  MS-DOS drive mapping understands NETBIOS names and WINS.</description>
      <pubDate>Wed, 14 Sep 2005 08:37:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625153#M2287</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2005-09-14T08:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: RDP imaging problem</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625154#M2288</link>
      <description>I've tried adding in the RDP server to the lmhost file with no success.  Still erroring out.</description>
      <pubDate>Wed, 14 Sep 2005 08:41:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625154#M2288</guid>
      <dc:creator>Torrey_1</dc:creator>
      <dc:date>2005-09-14T08:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: RDP imaging problem</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625155#M2289</link>
      <description>The PXE files?  You'll need to edit 2 files.  Did you also re-create the PXE images?  What steps did you take?</description>
      <pubDate>Wed, 14 Sep 2005 08:47:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/rdp-imaging-problem/m-p/3625155#M2289</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2005-09-14T08:47:30Z</dc:date>
    </item>
  </channel>
</rss>

