<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Configuring DHCP option 60 for PXE clients</title>
	<atom:link href="http://www.markwilson.co.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm/feed" rel="self" type="application/rss+xml" />
	<link>http://www.markwilson.co.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm</link>
	<description>get-info -class technology &#124; write-output > /dev/web</description>
	<lastBuildDate>Fri, 03 Sep 2010 15:47:46 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Wilson</title>
		<link>http://www.markwilson.co.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-142813</link>
		<dc:creator>Mark Wilson</dc:creator>
		<pubDate>Fri, 09 Jul 2010 14:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://markwilson.me.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-142813</guid>
		<description>It&#039;s not really a bug - just something that&#039;s not exposed via the GUI. Haven&#039;t tried it with Windows Server 2008 R2 though.</description>
		<content:encoded><![CDATA[<p>It&#8217;s not really a bug &#8211; just something that&#8217;s not exposed via the GUI. Haven&#8217;t tried it with Windows Server 2008 R2 though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.markwilson.co.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-142154</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Fri, 02 Jul 2010 11:23:46 +0000</pubDate>
		<guid isPermaLink="false">http://markwilson.me.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-142154</guid>
		<description>Great stuff thanks... this Bug is relly crappy... I wonder if W2k8x64 R2 is supported at all... couldnt find a clear statement. could you?</description>
		<content:encoded><![CDATA[<p>Great stuff thanks&#8230; this Bug is relly crappy&#8230; I wonder if W2k8&#215;64 R2 is supported at all&#8230; couldnt find a clear statement. could you?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: markwilson.it &#187; Configuring a Cisco IP phone for VoIP using SIP</title>
		<link>http://www.markwilson.co.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-109605</link>
		<dc:creator>markwilson.it &#187; Configuring a Cisco IP phone for VoIP using SIP</dc:creator>
		<pubDate>Thu, 10 Sep 2009 21:31:26 +0000</pubDate>
		<guid isPermaLink="false">http://markwilson.me.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-109605</guid>
		<description>[...] Configuration files are provided to the phone by TFTP. I used Philippe Jounin&#8217;s excellent TFTP32 and set my DHCP server to provide a TFTP server address to client devices (DHCP option 66). [...]</description>
		<content:encoded><![CDATA[<p>[...] Configuration files are provided to the phone by TFTP. I used Philippe Jounin&#8217;s excellent TFTP32 and set my DHCP server to provide a TFTP server address to client devices (DHCP option 66). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.markwilson.co.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-293</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Fri, 27 Jan 2006 17:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://markwilson.me.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-293</guid>
		<description>Two more DHCP options which might come in useful are 66 (Boot Server Host Name) and 67 (Bootfile Name).  In a RIS environment, 67 would be set to OSChooser\i386\startrom.com.  &lt;A HREF=&quot;https://www.freebsd.uwaterloo.ca/twiki/bin/view/Main/TimFarrell&quot; REL=&quot;nofollow&quot;&gt;Tim Farrell&lt;/A&gt; has posted more details on &lt;A HREF=&quot;https://www.freebsd.uwaterloo.ca/twiki/bin/view/NexusDocumentation/EnablingWindowsRemoteInstallationServicesOnARemoteSubnet&quot; REL=&quot;nofollow&quot;&gt;enabling RIS on a remote subnet&lt;/A&gt; although it should also be noted that &lt;A HREF=&quot;http://support.microsoft.com/?kbid=259670&quot; REL=&quot;nofollow&quot;&gt;Microsoft knowledge base article 259670&lt;/A&gt; states that this method of identifying servers is unsupported.&lt;BR/&gt;&lt;BR/&gt;I&#039;m currently working on a solution where I have centralised DHCP services and about 160 remote servers upon which I would like to install RIS.  Because I want to force clients to use their local server (and DHCP Discover packets could theoretically be picked up by any RIS server), I will probably use option 66.</description>
		<content:encoded><![CDATA[<p>Two more DHCP options which might come in useful are 66 (Boot Server Host Name) and 67 (Bootfile Name).  In a RIS environment, 67 would be set to OSChooser\i386\startrom.com.  <a HREF="https://www.freebsd.uwaterloo.ca/twiki/bin/view/Main/TimFarrell">Tim Farrell</a> has posted more details on <a HREF="https://www.freebsd.uwaterloo.ca/twiki/bin/view/NexusDocumentation/EnablingWindowsRemoteInstallationServicesOnARemoteSubnet">enabling RIS on a remote subnet</a> although it should also be noted that <a HREF="http://support.microsoft.com/?kbid=259670">Microsoft knowledge base article 259670</a> states that this method of identifying servers is unsupported.</p>
<p>I&#8217;m currently working on a solution where I have centralised DHCP services and about 160 remote servers upon which I would like to install RIS.  Because I want to force clients to use their local server (and DHCP Discover packets could theoretically be picked up by any RIS server), I will probably use option 66.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark&#8217;s (we)Blog &#187; Best practices for managing automatic IP addressing with DHCP</title>
		<link>http://www.markwilson.co.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-34311</link>
		<dc:creator>Mark&#8217;s (we)Blog &#187; Best practices for managing automatic IP addressing with DHCP</dc:creator>
		<pubDate>Thu, 21 Jul 2005 08:57:54 +0000</pubDate>
		<guid isPermaLink="false">http://markwilson.me.uk/blog/2004/03/configuring-dhcp-option-60-for-pxe.htm#comment-34311</guid>
		<description>[...] it may be necessary to configure custom options - e.g. 060 for a pre-boot execution environment (PXE) client or 252 for web proxy auto-discovery [...]</description>
		<content:encoded><![CDATA[<p>[...] it may be necessary to configure custom options &#8211; e.g. 060 for a pre-boot execution environment (PXE) client or 252 for web proxy auto-discovery [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
