<?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 for Angelo's blog</title>
	<atom:link href="http://blog.hongens.nl/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hongens.nl</link>
	<description>A systems administrator's diary</description>
	<lastBuildDate>Wed, 26 Oct 2011 21:58:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.5</generator>
	<item>
		<title>Comment on Adding drivers to WDS boot images by vl-sher</title>
		<link>http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/comment-page-1/#comment-49926</link>
		<dc:creator>vl-sher</dc:creator>
		<pubDate>Wed, 26 Oct 2011 21:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=65#comment-49926</guid>
		<description>Adding drivers can be done easily using Windows Deployment Services role in 2008 R2 server. Just add this role in Server Manager, run WDS server setup wizard in WDS MMC snap-in (keep your installation DVD nearby!), finally you&#039;ll have WDS server with boot and install images up and running.
Prepare driver packages (.inf+.cat+.sys + ...), right click on Drivers node of your WDS in WDS MMC, select &quot;Add driver package&quot;, browse for location of prepared package. Finally you&#039;ll have drivers installed to WDS server.
Next locate your boot image in WDS MMC, right-click it, select &quot;Add driver packages to image&quot;, &quot;Next&quot;, &quot;Search for packages&quot;. Check recently added packages, &quot;Next&quot; - and Bingo! - you can PXE boot with the drivers you&#039;ve added.</description>
		<content:encoded><![CDATA[<p>Adding drivers can be done easily using Windows Deployment Services role in 2008 R2 server. Just add this role in Server Manager, run WDS server setup wizard in WDS MMC snap-in (keep your installation DVD nearby!), finally you&#8217;ll have WDS server with boot and install images up and running.<br />
Prepare driver packages (.inf+.cat+.sys + &#8230;), right click on Drivers node of your WDS in WDS MMC, select &#8220;Add driver package&#8221;, browse for location of prepared package. Finally you&#8217;ll have drivers installed to WDS server.<br />
Next locate your boot image in WDS MMC, right-click it, select &#8220;Add driver packages to image&#8221;, &#8220;Next&#8221;, &#8220;Search for packages&#8221;. Check recently added packages, &#8220;Next&#8221; &#8211; and Bingo! &#8211; you can PXE boot with the drivers you&#8217;ve added.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Setting up OpenVPN using radius on FreeBSD by acdmail</title>
		<link>http://blog.hongens.nl/guides/setting-up-openvpn-using-radius-on-freebsd/comment-page-1/#comment-49347</link>
		<dc:creator>acdmail</dc:creator>
		<pubDate>Wed, 28 Sep 2011 12:41:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?page_id=42#comment-49347</guid>
		<description>Hi Rain,
If you are using OpenVPN with default settings proto: UDP 1194 try to add explicit-exit-notify in in client config, this will assure the client notifies the server as soon as it is disconnecting, otherwise server will disconnect the client a bit later after the default keepalive expires.</description>
		<content:encoded><![CDATA[<p>Hi Rain,<br />
If you are using OpenVPN with default settings proto: UDP 1194 try to add explicit-exit-notify in in client config, this will assure the client notifies the server as soon as it is disconnecting, otherwise server will disconnect the client a bit later after the default keepalive expires.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Setting up OpenVPN using radius on FreeBSD by Rain</title>
		<link>http://blog.hongens.nl/guides/setting-up-openvpn-using-radius-on-freebsd/comment-page-1/#comment-48502</link>
		<dc:creator>Rain</dc:creator>
		<pubDate>Thu, 25 Aug 2011 14:14:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?page_id=42#comment-48502</guid>
		<description>Hi everyone,
I am facing a problem when user disconnected openvpn.
I am using openvpn + freeradius on Debian 6.0 to authenticate user. To disable duplicate  login(connect) to openvpn  server I configure freeradius user parameter &quot;Simultaneous-Use&quot; to 1. I can successfully connect by freeradius. However, I can not reconnect after disconnect. 
The problem is user are still logged in. So I can not &#039;duplicate&#039; log in since user login session limited to 1. I found the problem by executing &quot;radwho&quot; after user disconnect.
The user should be log off after I disconnect.
  Is there any one have the same problem? How to fix this?</description>
		<content:encoded><![CDATA[<p>Hi everyone,<br />
I am facing a problem when user disconnected openvpn.<br />
I am using openvpn + freeradius on Debian 6.0 to authenticate user. To disable duplicate  login(connect) to openvpn  server I configure freeradius user parameter &#8220;Simultaneous-Use&#8221; to 1. I can successfully connect by freeradius. However, I can not reconnect after disconnect.<br />
The problem is user are still logged in. So I can not &#8216;duplicate&#8217; log in since user login session limited to 1. I found the problem by executing &#8220;radwho&#8221; after user disconnect.<br />
The user should be log off after I disconnect.<br />
  Is there any one have the same problem? How to fix this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adding drivers to WDS boot images by some problems with wds/mdt &#171; IT Info</title>
		<link>http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/comment-page-1/#comment-47928</link>
		<dc:creator>some problems with wds/mdt &#171; IT Info</dc:creator>
		<pubDate>Thu, 04 Aug 2011 11:53:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=65#comment-47928</guid>
		<description>[...] some problems with&#160;wds/mdt by voytas on 13 Wrzesie? 2010   1. &#8216;unable to find SETUP &#8230;&#8217; when mdt deploy? check this out: http://social.technet.microsoft.com/Forums/en-US/mdt/thread/82dc8e5e-5d0f-43d6-b1de-4afa708df086 2. reserved system partition has letter in OS? probably you deployed from WDS? check this out: http://social.technet.microsoft.com/Forums/en-GB/winservergen/thread/ad9928f1-c51b-4f22-ab5e-2210497d57e0 3. need some drivers in boot.wim? check this out: http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/ [...]</description>
		<content:encoded><![CDATA[<p>[...] some problems with&nbsp;wds/mdt by voytas on 13 Wrzesie? 2010   1. &#8216;unable to find SETUP &#8230;&#8217; when mdt deploy? check this out: http://social.technet.microsoft.com/Forums/en-US/mdt/thread/82dc8e5e-5d0f-43d6-b1de-4afa708df086 2. reserved system partition has letter in OS? probably you deployed from WDS? check this out: http://social.technet.microsoft.com/Forums/en-GB/winservergen/thread/ad9928f1-c51b-4f22-ab5e-2210497d57e0 3. need some drivers in boot.wim? check this out: http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/ [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adding drivers to WDS boot images by mukesh jagani</title>
		<link>http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/comment-page-1/#comment-45228</link>
		<dc:creator>mukesh jagani</dc:creator>
		<pubDate>Tue, 12 Apr 2011 08:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=65#comment-45228</guid>
		<description>HI,
     When i  try to add driver to boot image using Peing is not working i chaked that path is valid
    help me to solve this issue</description>
		<content:encoded><![CDATA[<p>HI,<br />
     When i  try to add driver to boot image using Peing is not working i chaked that path is valid<br />
    help me to solve this issue</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adding drivers to WDS boot images by Thom</title>
		<link>http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/comment-page-1/#comment-44724</link>
		<dc:creator>Thom</dc:creator>
		<pubDate>Mon, 21 Mar 2011 17:24:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=65#comment-44724</guid>
		<description>In the latest version of WAIK, PEimg has been removed. Instead you can use DISM with this command
&lt;code&gt;Dism /image: /Add-Driver /Driver:c:\winpe_x86\mount\Windows\driver.inf&lt;/code&gt;
So, for your example, replace the peimg line with 
 &lt;code&gt;Dism /image:c:\ff /Add-Driver /Driver:c:\bc\b06nd.inf&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>In the latest version of WAIK, PEimg has been removed. Instead you can use DISM with this command<br />
<code>Dism /image: /Add-Driver /Driver:c:\winpe_x86\mount\Windows\driver.inf</code><br />
So, for your example, replace the peimg line with<br />
 <code>Dism /image:c:\ff /Add-Driver /Driver:c:\bc\b06nd.inf</code></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adding drivers to WDS boot images by Gary</title>
		<link>http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/comment-page-1/#comment-40395</link>
		<dc:creator>Gary</dc:creator>
		<pubDate>Mon, 30 Aug 2010 14:18:46 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=65#comment-40395</guid>
		<description>Hi folks,

Thanks to both of you for your valuable and clear instructions! Works a charm!

Cheers</description>
		<content:encoded><![CDATA[<p>Hi folks,</p>
<p>Thanks to both of you for your valuable and clear instructions! Works a charm!</p>
<p>Cheers</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adding drivers to WDS boot images by angelo</title>
		<link>http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/comment-page-1/#comment-40349</link>
		<dc:creator>angelo</dc:creator>
		<pubDate>Wed, 25 Aug 2010 13:28:28 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=65#comment-40349</guid>
		<description>Nice Pete!</description>
		<content:encoded><![CDATA[<p>Nice Pete!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Adding drivers to WDS boot images by PeteLong</title>
		<link>http://blog.hongens.nl/2008/02/18/adding-drivers-to-wds-boot-images/comment-page-1/#comment-40341</link>
		<dc:creator>PeteLong</dc:creator>
		<pubDate>Tue, 24 Aug 2010 21:28:05 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=65#comment-40341</guid>
		<description>Follow Up - with WDS on 2008 R2 you can use this procedure http://www.petenetlive.com/KB/Article/0000314.htm</description>
		<content:encoded><![CDATA[<p>Follow Up &#8211; with WDS on 2008 R2 you can use this procedure <a href="http://www.petenetlive.com/KB/Article/0000314.htm" rel="nofollow">http://www.petenetlive.com/KB/Article/0000314.htm</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Graphing requests per second out of apache log files by Andrew</title>
		<link>http://blog.hongens.nl/2009/03/19/graphing-requests-per-second-out-of-apache-log-files/comment-page-1/#comment-39998</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Thu, 22 Jul 2010 01:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hongens.nl/?p=86#comment-39998</guid>
		<description>You&#039;re right, the timestamps being out of order is because of the difference between the time at which a request starts (the timestamp on the log line) and when it finishes (which is when it&#039;s written into the log line).

This is very useful information.  It may not be something you want for your current purpose, but it would be a shame to throw this information away.

It&#039;s very useful to be able to identify the log lines where the timestamp recorded is significantly behind the latest timestamp seen by that point in the logs, as this identifies the long running requests, which are likely to be performance issues on your site.</description>
		<content:encoded><![CDATA[<p>You&#8217;re right, the timestamps being out of order is because of the difference between the time at which a request starts (the timestamp on the log line) and when it finishes (which is when it&#8217;s written into the log line).</p>
<p>This is very useful information.  It may not be something you want for your current purpose, but it would be a shame to throw this information away.</p>
<p>It&#8217;s very useful to be able to identify the log lines where the timestamp recorded is significantly behind the latest timestamp seen by that point in the logs, as this identifies the long running requests, which are likely to be performance issues on your site.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

