 




<?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: Interesting Windows 7 Driver Signing Issue</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/interesting-windows-7-driver-signing-issue/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/interesting-windows-7-driver-signing-issue/</link>
	<description></description>
	<lastBuildDate>Mon, 13 May 2013 06:09:17 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Edtittel</title>
		<link>http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/interesting-windows-7-driver-signing-issue/#comment-90</link>
		<dc:creator>Edtittel</dc:creator>
		<pubDate>Wed, 21 Dec 2011 20:10:26 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/?p=1731#comment-90</guid>
		<description><![CDATA[Dear ApexWm:

Thanks for a great follow-up, and some terrific comments and suggestions. Drivers are particularly sticky and do pose interesting problems. You might want to talk to the people at Prowess Software (I&#039;d suggest starting with Aaron Suzuki, the CEO of the company who seems pretty technically astute to me). They&#039;ve come up with some interesting way to merge drivers with Windows images that you should find particuarly compelling, given the circumstances you recount in your posting here.

Best wishes, and happy holidays to you and your family.
--Ed--]]></description>
		<content:encoded><![CDATA[<p>Dear ApexWm:</p>
<p>Thanks for a great follow-up, and some terrific comments and suggestions. Drivers are particularly sticky and do pose interesting problems. You might want to talk to the people at Prowess Software (I&#8217;d suggest starting with Aaron Suzuki, the CEO of the company who seems pretty technically astute to me). They&#8217;ve come up with some interesting way to merge drivers with Windows images that you should find particuarly compelling, given the circumstances you recount in your posting here.</p>
<p>Best wishes, and happy holidays to you and your family.<br />
&#8211;Ed&#8211;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Apexwm</title>
		<link>http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/interesting-windows-7-driver-signing-issue/#comment-89</link>
		<dc:creator>Apexwm</dc:creator>
		<pubDate>Wed, 21 Dec 2011 18:31:24 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/vista-enterprise-desktop/?p=1731#comment-89</guid>
		<description><![CDATA[Hi Ed and thanks for the reference to my blog article.  I do agree with you that post-installation tasks could be set up to handle this.  In this case, we ended up looking at using a post-installation task to handle this issue.  But, I&#039;ve found mixed results going with this method; some items install fine with post-installation tasks, and others do not and must be included in the regular Windows unattended installation steps.  In the end the installations end up being a little cobbled because we are using scripts to perform tasks that should work out of the box.  And, scripting items for post-installation is always a challenge to figure out what the silent switches are so that no technician intervention is needed.  We&#039;ve found a few that are undocumented.  And, we&#039;ve also found that when trying to install a number of these post-installation items at once, that problems come up where they completely fail because they desire a reboot from something that was installed previously since the last reboot (sometimes mixing around the order seems to help).  Again, GNU/Linux excels over Windows in regards to all of this, due to the kernel design of drivers and modules being compiled directly or as modules to the kernel itself, along with the superior packaging system that most distributions have now (I like Red Hat&#039;s RPM system).]]></description>
		<content:encoded><![CDATA[<p>Hi Ed and thanks for the reference to my blog article.  I do agree with you that post-installation tasks could be set up to handle this.  In this case, we ended up looking at using a post-installation task to handle this issue.  But, I&#8217;ve found mixed results going with this method; some items install fine with post-installation tasks, and others do not and must be included in the regular Windows unattended installation steps.  In the end the installations end up being a little cobbled because we are using scripts to perform tasks that should work out of the box.  And, scripting items for post-installation is always a challenge to figure out what the silent switches are so that no technician intervention is needed.  We&#8217;ve found a few that are undocumented.  And, we&#8217;ve also found that when trying to install a number of these post-installation items at once, that problems come up where they completely fail because they desire a reboot from something that was installed previously since the last reboot (sometimes mixing around the order seems to help).  Again, GNU/Linux excels over Windows in regards to all of this, due to the kernel design of drivers and modules being compiled directly or as modules to the kernel itself, along with the superior packaging system that most distributions have now (I like Red Hat&#8217;s RPM system).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
