<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:openSearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:georss="http://www.georss.org/georss" xmlns:gd="http://schemas.google.com/g/2005" xmlns:thr="http://purl.org/syndication/thread/1.0" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" gd:etag="W/&quot;CEIDR344fCp7ImA9WhRaFEk.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714</id><updated>2012-02-16T20:36:16.034-05:00</updated><title>Epoxy Journal</title><subtitle type="html" /><link rel="http://schemas.google.com/g/2005#feed" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/posts/default" /><link rel="alternate" type="text/html" href="http://www.epoxyjournal.com/" /><link rel="next" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default?start-index=26&amp;max-results=25&amp;redirect=false&amp;v=2" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><generator version="7.00" uri="http://www.blogger.com">Blogger</generator><openSearch:totalResults>50</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>25</openSearch:itemsPerPage><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/atom+xml" href="http://feeds.feedburner.com/EpoxyJournal" /><feedburner:info uri="epoxyjournal" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><entry gd:etag="W/&quot;DEQFRHY-cCp7ImA9WhZQEk4.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-7799265222536314098</id><published>2011-04-19T14:05:00.000-04:00</published><updated>2011-04-19T14:05:15.858-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-04-19T14:05:15.858-04:00</app:edited><title>Installing the VMware Data Recovery plug in on your workstation</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;You cannot install the VMware Data Recovery plug in the same way you install the Converter or VUM plug ins. You can't just add it through plug in manager. You have to install it directly from the ISO. Would be nice, if that was mentioned in the docs. C'est la vie.&lt;br /&gt;
&lt;br /&gt;
&lt;a href="http://www.vmware.com/pdf/vdr_10_admin.pdf"&gt;http://www.vmware.com/pdf/vdr_10_admin.pdf&lt;/a&gt;&lt;br /&gt;
&lt;a href="http://vmware.com/files/pdf/data-recovery-evaluators-guide.pdf"&gt;http://vmware.com/files/pdf/data-recovery-evaluators-guide.pdf&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-7799265222536314098?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/jqvoUu5P6fumhsj7ysmC3Y4d6oA/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jqvoUu5P6fumhsj7ysmC3Y4d6oA/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/jqvoUu5P6fumhsj7ysmC3Y4d6oA/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/jqvoUu5P6fumhsj7ysmC3Y4d6oA/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/evq7qFtKsWI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/7799265222536314098/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2011/04/installing-vmware-data-recovery-plug-in.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/7799265222536314098?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/7799265222536314098?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/evq7qFtKsWI/installing-vmware-data-recovery-plug-in.html" title="Installing the VMware Data Recovery plug in on your workstation" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2011/04/installing-vmware-data-recovery-plug-in.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D04DQn04fCp7ImA9Wx9aEU0.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-7395540992036217476</id><published>2011-03-02T17:46:00.000-05:00</published><updated>2011-03-02T17:46:13.334-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-03-02T17:46:13.334-05:00</app:edited><title>Why does Java exist?</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;Seriously, what goes into the decision to write an app in Java instead of something else? Is it pure sadism?&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-7395540992036217476?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Yo6fAUmojjfADLX5qSlWKz00td8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Yo6fAUmojjfADLX5qSlWKz00td8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Yo6fAUmojjfADLX5qSlWKz00td8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Yo6fAUmojjfADLX5qSlWKz00td8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/gmtvWYhUcz4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/7395540992036217476/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2011/03/why-does-java-exist.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/7395540992036217476?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/7395540992036217476?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/gmtvWYhUcz4/why-does-java-exist.html" title="Why does Java exist?" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2011/03/why-does-java-exist.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUANSHw7fSp7ImA9Wx9UE0o.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-6710291843149710712</id><published>2011-02-10T16:36:00.000-05:00</published><updated>2011-02-10T16:36:39.205-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-02-10T16:36:39.205-05:00</app:edited><title>God, I hate Oracle</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;Sorry, just had to get that off my chest.&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-6710291843149710712?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/xiC2qsgfsAQJ_vCXXh7PwosZBOY/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xiC2qsgfsAQJ_vCXXh7PwosZBOY/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/xiC2qsgfsAQJ_vCXXh7PwosZBOY/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xiC2qsgfsAQJ_vCXXh7PwosZBOY/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/rqCYGWYxPsE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/6710291843149710712/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2011/02/god-i-hate-oracle.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/6710291843149710712?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/6710291843149710712?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/rqCYGWYxPsE/god-i-hate-oracle.html" title="God, I hate Oracle" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2011/02/god-i-hate-oracle.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Dk4DSHYzeyp7ImA9Wx9WGUo.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-8849109928211592273</id><published>2011-01-25T12:02:00.001-05:00</published><updated>2011-01-25T12:02:59.883-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2011-01-25T12:02:59.883-05:00</app:edited><title>I'll bet you can't guess the password</title><content type="html">&lt;div dir="ltr" style="text-align: left;" trbidi="on"&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://1.bp.blogspot.com/_tAXqxxBxO9E/TT8BjE8tMtI/AAAAAAAAACY/UfilnR_kkSA/s1600/DefaultPassword.PNG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" s5="true" src="http://1.bp.blogspot.com/_tAXqxxBxO9E/TT8BjE8tMtI/AAAAAAAAACY/UfilnR_kkSA/s1600/DefaultPassword.PNG" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-8849109928211592273?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/41lGnNyydDi_2Tml4QLW5xtlfC4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/41lGnNyydDi_2Tml4QLW5xtlfC4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/41lGnNyydDi_2Tml4QLW5xtlfC4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/41lGnNyydDi_2Tml4QLW5xtlfC4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/BG3prm7pcKU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/8849109928211592273/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2011/01/ill-bet-you-cant-guess-password.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8849109928211592273?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8849109928211592273?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/BG3prm7pcKU/ill-bet-you-cant-guess-password.html" title="I'll bet you can't guess the password" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://1.bp.blogspot.com/_tAXqxxBxO9E/TT8BjE8tMtI/AAAAAAAAACY/UfilnR_kkSA/s72-c/DefaultPassword.PNG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2011/01/ill-bet-you-cant-guess-password.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUADQXk8fCp7ImA9Wx9TFkw.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-4025718257707187699</id><published>2010-11-24T10:49:00.002-05:00</published><updated>2010-11-24T10:49:30.774-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-11-24T10:49:30.774-05:00</app:edited><title>Remote control robots with Kinect? Hmm, maybe I should cancel my eBay listing.</title><content type="html">&lt;a href="http://news.softpedia.com/news/Hacked-Microsoft-Kinect-Used-for-Controlling-Robots-168490.shtml"&gt;http://news.softpedia.com/news/Hacked-Microsoft-Kinect-Used-for-Controlling-Robots-168490.shtml&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
Just kidding. Somebody please buy my Kinect.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-4025718257707187699?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/fsRa_SioCnfmi2UN8p98zT79zaE/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/fsRa_SioCnfmi2UN8p98zT79zaE/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/fsRa_SioCnfmi2UN8p98zT79zaE/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/fsRa_SioCnfmi2UN8p98zT79zaE/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/-Cy0QYOj_38" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/4025718257707187699/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/11/remote-control-robots-with-kinect-hmm.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/4025718257707187699?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/4025718257707187699?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/-Cy0QYOj_38/remote-control-robots-with-kinect-hmm.html" title="Remote control robots with Kinect? Hmm, maybe I should cancel my eBay listing." /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/11/remote-control-robots-with-kinect-hmm.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0ABSHY-fSp7ImA9Wx9TFU4.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-4759569549411234370</id><published>2010-11-23T14:15:00.000-05:00</published><updated>2010-11-23T14:15:59.855-05:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-11-23T14:15:59.855-05:00</app:edited><title>Pretty sure this would've pissed off some founding fathers</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://4.bp.blogspot.com/_tAXqxxBxO9E/TOwSbQYEbWI/AAAAAAAAACQ/1wA_PgbxWfk/s1600/PRC.PNG" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"&gt;&lt;img border="0" ox="true" src="http://4.bp.blogspot.com/_tAXqxxBxO9E/TOwSbQYEbWI/AAAAAAAAACQ/1wA_PgbxWfk/s1600/PRC.PNG" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div align="left" class="separator" style="clear: both; text-align: center;"&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-4759569549411234370?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/pHVZhAs7KEgQqu9JMXOei6nfFSg/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/pHVZhAs7KEgQqu9JMXOei6nfFSg/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/pHVZhAs7KEgQqu9JMXOei6nfFSg/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/pHVZhAs7KEgQqu9JMXOei6nfFSg/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/WjmuqDc9L08" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/4759569549411234370/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/11/pretty-sure-this-wouldve-pissed-off.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/4759569549411234370?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/4759569549411234370?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/WjmuqDc9L08/pretty-sure-this-wouldve-pissed-off.html" title="Pretty sure this would've pissed off some founding fathers" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://4.bp.blogspot.com/_tAXqxxBxO9E/TOwSbQYEbWI/AAAAAAAAACQ/1wA_PgbxWfk/s72-c/PRC.PNG" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/11/pretty-sure-this-wouldve-pissed-off.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUUERXk_eCp7ImA9Wx5bGE0.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-7398748950496187312</id><published>2010-11-03T12:53:00.000-04:00</published><updated>2010-11-03T12:53:24.740-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-11-03T12:53:24.740-04:00</app:edited><title>Google wardriving - So what?</title><content type="html">It's not news that Google's streetview trucks have been looking for wireless hotspots, and inadvertently capturing some of the traffic on these networks, including personally identifiable information (PII).&lt;br /&gt;
The news is that today in the UK, the &lt;a href="http://www.pcmag.com/article2/0,2817,2372041,00.asp"&gt;ICO called it a "significant breach".&lt;/a&gt;&lt;br /&gt;
Really? Breach of what? If you transmit your own PII on an unencrypted open network, then that's the breach right there. Now the bits are in the air ready to be sniffed. With the new &lt;a href="http://codebutler.com/firesheep"&gt;firesheep&lt;/a&gt; plugin, it's so easy a script kiddie could do it.&lt;br /&gt;
I feel like I shouldn't have to say this in 2010, but apparently I do. Don't send any PII over an open wireless network.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-7398748950496187312?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/HbLNJH4ZLmsVsWtGjRJLL7ST5Xs/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/HbLNJH4ZLmsVsWtGjRJLL7ST5Xs/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/HbLNJH4ZLmsVsWtGjRJLL7ST5Xs/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/HbLNJH4ZLmsVsWtGjRJLL7ST5Xs/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/j-1Rs8osqBg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/7398748950496187312/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/11/google-wardriving-so-what.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/7398748950496187312?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/7398748950496187312?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/j-1Rs8osqBg/google-wardriving-so-what.html" title="Google wardriving - So what?" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/11/google-wardriving-so-what.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEYCSHY4eip7ImA9Wx5REUk.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-6242739018170737561</id><published>2010-08-18T10:36:00.000-04:00</published><updated>2010-08-18T10:36:09.832-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-18T10:36:09.832-04:00</app:edited><title>To virtualize or not to virtualize</title><content type="html">A friend of mine asked how I feel about virtualizing Domain Controllers. My answer below;&lt;br /&gt;
&lt;br /&gt;
I think they're perfect for virtualization. Most domains have less than a few hundred objects, so we're looking at light utilization. It's almost impossible to provision a server that won't have way more resources than the DC will ever need. You could try to get more bang for you buck by putting other apps on the DC, but who wants to do that? &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
I think the main considerations with virtual DCs are; &lt;br /&gt;
DRS - You can set a rule so that the VMs don't end up on the same host. &lt;br /&gt;
HA - Give the PDC high restart priority, so it'll be one of the first machines powered up in the event of a host failure. &lt;br /&gt;
snapshots - No point taking snapshots of a DC. You can't restore it from a snapshot. &lt;br /&gt;
time - make sure your PDC is syncing with a good time source. VMs drift, a lot.&lt;br /&gt;
&lt;br /&gt;
At this point I think there are only 3 reasons not to virtualize any server. &lt;br /&gt;
1 - Software TOS doesn't fully support it. Thanks, Oracle.&lt;br /&gt;
2 - DMZ servers. I'm still not totally comfortable virtualizing my DMZ. I'll let my counterparts learn the hard lessons here before I venture into it.&lt;br /&gt;
3 - Big Iron. I'm pretty sure most&amp;nbsp;admins hit the physical limitations of their hosts long before the vSphere configuration maximums come into play. Either way, some workloads are still too big to virtualize.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-6242739018170737561?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/mAgoEnDJhtQLk0mXXQZI7ux4qWQ/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mAgoEnDJhtQLk0mXXQZI7ux4qWQ/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/mAgoEnDJhtQLk0mXXQZI7ux4qWQ/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/mAgoEnDJhtQLk0mXXQZI7ux4qWQ/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/nNbE-JAO4no" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/6242739018170737561/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/08/to-virtualize-or-not-to-virtualize.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/6242739018170737561?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/6242739018170737561?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/nNbE-JAO4no/to-virtualize-or-not-to-virtualize.html" title="To virtualize or not to virtualize" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/08/to-virtualize-or-not-to-virtualize.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkIGRnY-eyp7ImA9Wx5SFEo.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-2098863823542091817</id><published>2010-08-10T16:02:00.000-04:00</published><updated>2010-08-10T16:02:07.853-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-08-10T16:02:07.853-04:00</app:edited><title>Siemens End User License Agreement authored by former Stasi agent</title><content type="html">&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://2.bp.blogspot.com/_tAXqxxBxO9E/TGGwEw1vtHI/AAAAAAAAACA/B27Ny-cZWuU/s1600/SSiemens.png" imageanchor="1" style="clear: right; cssfloat: right; float: right; margin-bottom: 1em; margin-left: 1em;"&gt;&lt;img border="0" mx="true" src="http://2.bp.blogspot.com/_tAXqxxBxO9E/TGGwEw1vtHI/AAAAAAAAACA/B27Ny-cZWuU/s320/SSiemens.png" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"&gt;That's how it sounds anyway...&lt;/div&gt;&lt;div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"&gt;&lt;/div&gt;&lt;br /&gt;
&lt;div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"&gt;"Siemens PLM may, during regular business hours and upon reasonable advance notice, conduct an audit to determine Your compliance with the terms and conditions of this Agreement. You will permit Siemens PLM or its authorized agents to access Your facilities, workstations and servers and otherwise cooperate fully with Siemens PLM in any such investigation and will take all commercially reasonable actions to assist Siemens PLM in accurately determining Your compliance with the terms and conditions of this Agreement. Siemens PLM and its authorized agents will comply with Your reasonable security regulations while on Your premises."&lt;/div&gt;&lt;div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"&gt;&lt;br /&gt;
&lt;/div&gt;&lt;div style="border-bottom: medium none; border-left: medium none; border-right: medium none; border-top: medium none;"&gt;&lt;a href="http://www.plm.automation.siemens.com/en_us/products/eula/united_states_eula.shtml"&gt;http://www.plm.automation.siemens.com/en_us/products/eula/united_states_eula.shtml&lt;/a&gt;&lt;/div&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-2098863823542091817?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/p1hiNWqR_rDD0ZUvW563NfCxKu8/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/p1hiNWqR_rDD0ZUvW563NfCxKu8/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/p1hiNWqR_rDD0ZUvW563NfCxKu8/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/p1hiNWqR_rDD0ZUvW563NfCxKu8/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/luYVbEPXSfE" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/2098863823542091817/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/08/siemens-end-user-license-agreement.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/2098863823542091817?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/2098863823542091817?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/luYVbEPXSfE/siemens-end-user-license-agreement.html" title="Siemens End User License Agreement authored by former Stasi agent" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><media:thumbnail xmlns:media="http://search.yahoo.com/mrss/" url="http://2.bp.blogspot.com/_tAXqxxBxO9E/TGGwEw1vtHI/AAAAAAAAACA/B27Ny-cZWuU/s72-c/SSiemens.png" height="72" width="72" /><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/08/siemens-end-user-license-agreement.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CE8FRHs5eCp7ImA9Wx5TFU0.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-2854512315949280488</id><published>2010-07-30T11:13:00.000-04:00</published><updated>2010-07-30T11:13:35.520-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-30T11:13:35.520-04:00</app:edited><title>Happy System Administrator Appreciation day!</title><content type="html">&lt;a href="http://www.sysadminday.com/"&gt;http://www.sysadminday.com/&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-2854512315949280488?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/5mNRLrTHakM8PNi8nihk-5QFd_o/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/5mNRLrTHakM8PNi8nihk-5QFd_o/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/5mNRLrTHakM8PNi8nihk-5QFd_o/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/5mNRLrTHakM8PNi8nihk-5QFd_o/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/5mGpZJF7NOc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/2854512315949280488/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/07/happy-system-administrator-appreciation.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/2854512315949280488?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/2854512315949280488?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/5mGpZJF7NOc/happy-system-administrator-appreciation.html" title="Happy System Administrator Appreciation day!" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/07/happy-system-administrator-appreciation.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUcNSHkyfip7ImA9Wx5TE0k.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-2070154329212003039</id><published>2010-07-28T14:51:00.000-04:00</published><updated>2010-07-28T14:51:39.796-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-28T14:51:39.796-04:00</app:edited><title>Green IT on the cheap</title><content type="html">We've all heard they hype around "Green IT" it usually involves spending a lot of green on SANs, blades and vSphere licenses.Today, I implemented a Green solution requiring no additional purchasing. First some back story.&lt;br /&gt;
&lt;br /&gt;
It's been an unusually hot summer this year. My server room is too hot in February, it's way too hot now. On particularly bad days I turn off my Backup server, since it's basically idle during the day. It occurred to me, that it might be a good idea to only have the server running while it's needed. Backups begin at 7pm, and usually run until almost 3am. So, we're talking about a machine that's completely idle for 2/3 of the day during the week.&lt;br /&gt;
&lt;br /&gt;
So here's what I did. First, I went into the NIC settings in the BIOS, and in Windows and made sure Wake On Lan was enabled in both of those places. I'm already familiar with WolCmd.exe, see my &lt;a href="http://www.epoxyjournal.com/2010/05/powering-on-server-remotely-wolcmd.html"&gt;previous post on WolCmd&lt;/a&gt;. So I know I can turn the server on. I set up a scheduled task on my monitoring server to bring up the backup server 15 minutes before backups are scheduled to begin. So, how do I shut it off? I started looking into the job properties in Backup Exec. There is a Pre/Post commands option in the job properties. This allows me to run windows commands through Backup Exec. So, when the job finishes it will execute the command shutdown /s. Be careful when configuring this, the default for pre/post commands is to run the command "On each server backed up". That would be bad. You must change the option to "On this media server". Voila! Now my backup server will consume 2/3 of the energy it used to consume, and all using software/hardware we already own, and a free utility.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-2070154329212003039?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/1Z__2i45LefEgLAwy8WT8gXrzG4/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1Z__2i45LefEgLAwy8WT8gXrzG4/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/1Z__2i45LefEgLAwy8WT8gXrzG4/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/1Z__2i45LefEgLAwy8WT8gXrzG4/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/Ur-G7qfgPwc" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/2070154329212003039/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/07/green-it-on-cheap.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/2070154329212003039?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/2070154329212003039?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/Ur-G7qfgPwc/green-it-on-cheap.html" title="Green IT on the cheap" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/07/green-it-on-cheap.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DU8BSXs-fip7ImA9WxFaGUw.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-8900977816638911561</id><published>2010-07-23T16:44:00.000-04:00</published><updated>2010-07-23T16:44:18.556-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-23T16:44:18.556-04:00</app:edited><title>Glad my IT mentor told me to always "measure twice, cut once"</title><content type="html">I just finished configuring a router for DMVPN. I'm shipping it offsite on Monday. I decided it would be a good idea to do a show run, and go through the config line-by-line to ensure that it is what it should be.&lt;br /&gt;
Had I not done that I might have forgotten entirely about the Serial interface. They don't need the WIC at this site, but I wouldn't mind having it. It'll come in handy in the CCNP lab I'm building under my desk.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-8900977816638911561?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/hmcRQM8y_R9foi7LzoX9oc6Dkac/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hmcRQM8y_R9foi7LzoX9oc6Dkac/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/hmcRQM8y_R9foi7LzoX9oc6Dkac/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/hmcRQM8y_R9foi7LzoX9oc6Dkac/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/PzrbL7vZ9dI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/8900977816638911561/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/07/glad-my-it-mentor-told-me-to-always.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8900977816638911561?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8900977816638911561?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/PzrbL7vZ9dI/glad-my-it-mentor-told-me-to-always.html" title="Glad my IT mentor told me to always &quot;measure twice, cut once&quot;" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/07/glad-my-it-mentor-told-me-to-always.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEQASHw7eSp7ImA9WxFbFkw.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-1097222680247511325</id><published>2010-07-08T14:05:00.000-04:00</published><updated>2010-07-08T14:05:49.201-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-08T14:05:49.201-04:00</app:edited><title>This might be my funniest Experts Exhange respone.</title><content type="html">&lt;a href="http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_26315984.html#a33165029"&gt;http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_26315984.html#a33165029&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-1097222680247511325?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/SRFZoaYa2d5GGEElZ8o4qlz6EMo/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SRFZoaYa2d5GGEElZ8o4qlz6EMo/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/SRFZoaYa2d5GGEElZ8o4qlz6EMo/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/SRFZoaYa2d5GGEElZ8o4qlz6EMo/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/9CLHe4aGgU0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/1097222680247511325/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/07/this-might-be-my-funniest-experts.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/1097222680247511325?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/1097222680247511325?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/9CLHe4aGgU0/this-might-be-my-funniest-experts.html" title="This might be my funniest Experts Exhange respone." /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/07/this-might-be-my-funniest-experts.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CEcHRHY9eip7ImA9WxFbEEw.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-826790089892290191</id><published>2010-07-01T15:20:00.000-04:00</published><updated>2010-07-01T15:20:35.862-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-07-01T15:20:35.862-04:00</app:edited><title>Google voice transcription</title><content type="html">Want to. I don't know yet. Yeah, thanks very much. I'll wait. Hello, selson hey, I guess like a vehicle dinner. Contraceptives. Alright, well I tried to deliver some stuff but alright. Bye.&lt;br /&gt;
&lt;br /&gt;
Well, they did say bye at the end. Other than that...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-826790089892290191?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/Mzp7V8AIzAaQm-p1-kC7yPnOrV0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Mzp7V8AIzAaQm-p1-kC7yPnOrV0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/Mzp7V8AIzAaQm-p1-kC7yPnOrV0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/Mzp7V8AIzAaQm-p1-kC7yPnOrV0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/1XfOgwmI-bQ" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/826790089892290191/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/07/google-voice-transcription.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/826790089892290191?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/826790089892290191?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/1XfOgwmI-bQ/google-voice-transcription.html" title="Google voice transcription" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/07/google-voice-transcription.html</feedburner:origLink></entry><entry gd:etag="W/&quot;Ck4GQHg9cCp7ImA9WxFVEko.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-8627534553888264781</id><published>2010-06-11T11:42:00.000-04:00</published><updated>2010-06-11T11:42:01.668-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-06-11T11:42:01.668-04:00</app:edited><title>Another happy customer</title><content type="html">Guy had multiple KMS servers. Wanted to turn two of them back into clients. Been there done that. What a pain in the neck. I had multiple admins in multiple sites using KMS keys like they were the old volume license key. Like I said in the EE thread, I don't know if this is the best way to do this, but it worked for me.&lt;br /&gt;
&lt;a href="http://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Q_26251088.html?cid=1131#a32970316"&gt;http://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/Q_26251088.html?cid=1131#a32970316&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-8627534553888264781?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/0cVhILaHOpuv_8ABhVhFGtMxmMI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0cVhILaHOpuv_8ABhVhFGtMxmMI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/0cVhILaHOpuv_8ABhVhFGtMxmMI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0cVhILaHOpuv_8ABhVhFGtMxmMI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/zCiCkJzSqHg" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/8627534553888264781/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/06/another-happy-customer.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8627534553888264781?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8627534553888264781?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/zCiCkJzSqHg/another-happy-customer.html" title="Another happy customer" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/06/another-happy-customer.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CUMHR387fSp7ImA9WxFVEks.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-6892072733582317996</id><published>2010-06-11T09:37:00.000-04:00</published><updated>2010-06-11T09:37:16.105-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-06-11T09:37:16.105-04:00</app:edited><title>Experts Exchange Bragging</title><content type="html">I know, I know. EE has it's share of haters. It used to drive me nuts googling for a solution to a problem and hitting EE's paywall. Then I learned how easy it is to get free access by signing up as an "Expert".&lt;br /&gt;
It's really not that hard to maintain 3,000 points a month. A lot of times there's a super easy question that can be answered with a little googling, and a link to a technet article. You just gotta be quicker than all the other snipers.&lt;br /&gt;
I think EE is good for me professionally, because it gets me thinking about problems that I might not encounter otherwise. Also, it helps my customer service mindset. A lot of times people are asking how to do things that I would recommend against doing at all. Those are my favorites, because I have to think of the best way to achieve what they want to achieve whether is seems like the "right way" to me or not. Sometimes, I tactfully tell them that it might not be the best way to go about things. Sometimes, I'm too lazy to bother. After all, folks are looking for technical advice, not a lecture on the fine art of system administration.&lt;br /&gt;
So here's my accepted or assisted answers from today.&lt;br /&gt;
&lt;a href="http://www.experts-exchange.com/Security/Operating_Systems_Security/Windows/Q_26231118.html?cid=1131#a32901664"&gt;http://www.experts-exchange.com/Security/Operating_Systems_Security/Windows/Q_26231118.html?cid=1131#a32901664&lt;/a&gt;&lt;br /&gt;
&lt;a href="http://www.experts-exchange.com/Hardware/Servers/Q_26251168.html?cid=1133#a32964937"&gt;http://www.experts-exchange.com/Hardware/Servers/Q_26251168.html?cid=1133#a32964937&lt;/a&gt;&lt;br /&gt;
&lt;a href="http://www.experts-exchange.com/Networking/Misc/Q_26162387.html?cid=1133#a32662778"&gt;http://www.experts-exchange.com/Networking/Misc/Q_26162387.html?cid=1133#a32662778&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-6892072733582317996?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/sMFxGgh9wwSxvyFyDQ4o8_WEFRI/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/sMFxGgh9wwSxvyFyDQ4o8_WEFRI/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/sMFxGgh9wwSxvyFyDQ4o8_WEFRI/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/sMFxGgh9wwSxvyFyDQ4o8_WEFRI/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/NlgEGhhxBIk" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/6892072733582317996/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/06/experts-exchange-bragging.html#comment-form" title="1 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/6892072733582317996?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/6892072733582317996?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/NlgEGhhxBIk/experts-exchange-bragging.html" title="Experts Exchange Bragging" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>1</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/06/experts-exchange-bragging.html</feedburner:origLink></entry><entry gd:etag="W/&quot;AkMNQnw_fyp7ImA9WxFVEUo.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-3663134115260781062</id><published>2010-06-10T10:01:00.000-04:00</published><updated>2010-06-10T10:01:33.247-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-06-10T10:01:33.247-04:00</app:edited><title>Excel nested if statement</title><content type="html">My server inventory spreadsheet includes physical and virtual servers. There is a column for total cores, clockrate per core, and a columnt that multiplies the two. This is useful for physical servers, because it gives me an idea of what impact this server might have on my cluster if virtualized. Granted, it only shows me how many total GHz the server has available to it, not how many it actually uses.&lt;br /&gt;
For virtual servers, I don't record the clockrate per core, because that'a a dynamic number. Depends on which host they're currently on. If I record a n/a in that column, my multiplier formula returns #VALUE!. Ugly. If I leave the clockrate per core column blank, the muliplier returns a 0, which isn't accurate.&lt;br /&gt;
So, today I created a simple nested IF statement in my formula. It will look at the clockrate per core column, if the value is less than 1, it'll return n/a, if the value is greater than 0, it'll multiply the two columns. Trust me, it's less complicate than it looks, and you only have to get your formula close to this. Excel will fix it for you.&lt;br /&gt;
=IF(AN2&amp;lt;1,"n/a",IF(AN2&amp;gt;0,(AN2*AM2)))&lt;br /&gt;
AN2 is the clockrate per core column&lt;br /&gt;
AM2 is the total number of cores&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-3663134115260781062?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/xnhrkaCCpCDP_1xr73w3szlewF0/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xnhrkaCCpCDP_1xr73w3szlewF0/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/xnhrkaCCpCDP_1xr73w3szlewF0/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/xnhrkaCCpCDP_1xr73w3szlewF0/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/8Ish8uOqXG0" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/3663134115260781062/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/06/excel-nested-if-statement.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/3663134115260781062?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/3663134115260781062?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/8Ish8uOqXG0/excel-nested-if-statement.html" title="Excel nested if statement" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/06/excel-nested-if-statement.html</feedburner:origLink></entry><entry gd:etag="W/&quot;C0UHRH49fSp7ImA9WxFWEEs.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-3949637270769396587</id><published>2010-05-28T11:40:00.000-04:00</published><updated>2010-05-28T11:40:35.065-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-28T11:40:35.065-04:00</app:edited><title>Powering on a server remotely. wolcmd</title><content type="html">Ok, I know there's actually a lot of ways to skin this cat. Especially, if you're server has ILO, or DRAC. What if it doesn't have that? Or what if it does, but the goober that installed the server never configured it? Or what if you're the goober, and you configured it, but you don't remember the IP or password of your ILO card?&lt;br /&gt;
Enter &lt;a href="http://www.depicus.com/wake-on-lan/wake-on-lan-cmd.aspx"&gt;wolcmd&lt;/a&gt;. It'a tiny little executable, run from the command line. I used it for the first time today, as I'm stuck at home, and I wanted to power up one of my ESX hosts. It was literally this simple.&lt;br /&gt;
wolcmd macaddress ipaddress netmask&lt;br /&gt;
If you don't enter a port number, wolcmd uses the default, port 7. Of course, you have to actually have Wake on Lan configured on the nic already for this to work, most NICs are already set up that way out of the box.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-3949637270769396587?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/roccbpoMONLykfqcSYOG5M3Mezw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/roccbpoMONLykfqcSYOG5M3Mezw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/roccbpoMONLykfqcSYOG5M3Mezw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/roccbpoMONLykfqcSYOG5M3Mezw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/2ehD6G72hys" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/3949637270769396587/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/05/powering-on-server-remotely-wolcmd.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/3949637270769396587?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/3949637270769396587?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/2ehD6G72hys/powering-on-server-remotely-wolcmd.html" title="Powering on a server remotely. wolcmd" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/05/powering-on-server-remotely-wolcmd.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DkADRn86fip7ImA9WxFXGUU.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-8856335278885000579</id><published>2010-05-27T14:26:00.000-04:00</published><updated>2010-05-27T14:26:17.116-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-27T14:26:17.116-04:00</app:edited><title>Disk space vbscript</title><content type="html">I've got to inventory disk usage across a handful of servers for the purpose of evaluating&amp;nbsp;virtualization candidates, and justifying an additional shelf of storage for my ESX SAN.&lt;br /&gt;
So, I could laboriously log into each server and record disk usage, but where's the fun in that?&lt;br /&gt;
Now, I'm no scripting guru. I started out trying to do this with batch, but that just wasn't working. I found &lt;a href="http://blogs.technet.com/b/heyscriptingguy/archive/2004/10/13/how-can-i-determine-the-percentage-of-free-space-on-a-drive.aspx"&gt;this vbscript&lt;/a&gt;, that gave me the percentage of free space. This got me close to what I needed. I hacked around a bit with the script, until I got something that gave me total, free, and percent free. I'm using psexec to run this against all my servers and kick out a text log.&lt;br /&gt;
Blogger might wrap the last 3 lines. They're not supposed to be wrapped, but you know how to fixt that in notepad, right?&lt;br /&gt;
&lt;br /&gt;
strComputer = "."&lt;br /&gt;
Set objWMIService = GetObject("winmgmts:" _&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;amp; "{impersonationLevel=impersonate}!\\" &amp;amp; strComputer &amp;amp; "\root\cimv2")&lt;br /&gt;
Set colDisks = objWMIService.ExecQuery _&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; ("Select * from Win32_LogicalDisk Where DriveType = 3")&lt;br /&gt;
For Each objDisk in colDisks&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; intFreeSpace = objDisk.FreeSpace&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; intTotalSpace = objDisk.Size&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; pctFreeSpace = intFreeSpace / intTotalSpace&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; Wscript.Echo objDisk.DeviceID &amp;amp; " " &amp;amp; FormatNumber(objDisk.Size/1073741824,2) &amp;amp; "GB Total" &amp;amp; vbNewLine&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; Wscript.Echo objDisk.DeviceID &amp;amp; " " &amp;amp; FormatNumber(objDisk.FreeSpace/1073741824,2) &amp;amp; "GB Free" &amp;amp; vbNewLine&lt;br /&gt;
&amp;nbsp;&amp;nbsp;&amp;nbsp; Wscript.Echo objDisk.DeviceID &amp;amp; " " &amp;amp; FormatPercent(pctFreeSpace) &amp;amp; " Percent Free" &amp;amp; vbNewLine&lt;br /&gt;
Next&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-8856335278885000579?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/KuGbxSoAmYGVjubwWKiQSi_8d6o/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/KuGbxSoAmYGVjubwWKiQSi_8d6o/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/KuGbxSoAmYGVjubwWKiQSi_8d6o/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/KuGbxSoAmYGVjubwWKiQSi_8d6o/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/AGEuz6Ap3s4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/8856335278885000579/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/05/disk-space-vbscript.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8856335278885000579?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8856335278885000579?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/AGEuz6Ap3s4/disk-space-vbscript.html" title="Disk space vbscript" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/05/disk-space-vbscript.html</feedburner:origLink></entry><entry gd:etag="W/&quot;CkQGQXo9cSp7ImA9WxFXGUw.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-8834244472470076152</id><published>2010-05-26T17:45:00.000-04:00</published><updated>2010-05-26T17:45:20.469-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-26T17:45:20.469-04:00</app:edited><title>Linking Excel to SQL</title><content type="html">Today I was asked to audit BES accounts. Yay. I need to send a list of BES users to all the subsidiaries and ask their IT folks to confirm or deny whether these folks are still breathing. The standard trick of highlighting all the accounts and choosing Export Asset Summary Data is not going to work for me. I need the Mail Server field to be exported so I can divide the list up by site. So, on to Google. It seemed a lot of people were &lt;a href="http://www.blackberryforums.com/bes-admin-corner/175556-export-user-accounts-information-bes.html"&gt;recommending querying the SQL database directly&lt;/a&gt;. Awesome. I know very little about SQL. I don't know what all these scripts with their joins and selects are going to do do my BES. I do know Excel though. Though I'd never done it, I knew you could use Excel to query SQL directly. So, back to Google. Found &lt;a href="http://office.microsoft.com/en-us/excel/ha100996641033.aspx"&gt;this helpful article&lt;/a&gt;. Did as the article instructs, and Voila! I was connected to the BES SQL database through Excel. Now I just have to choose which db and table I want to look at. For db I went with BESMgmt. Just seemed kind of obvious. There's a lot of tables in that sucker. Hmm, which one do I want? vUserConfigStats looks promising. yUp! That's it. I found myself presented with every field of information related to each BB. Right down to their email signature. Sweet.&lt;br /&gt;
&lt;br /&gt;
btw, there was actually an easier way to do all of this, but I got yelled at for it. I figured, instead of dealing with the potential human error in asking local IT staff to manually verify the account. I'd just disable redirection on every BB that hadn't contacted the BES in a few weeks. More than likely, those are not active accounts anymore. For those that are still active account, easy enough to just re-enable redirection when they complain.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-8834244472470076152?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/B_s1pyexu6dilEGVQ0qw8fHblzw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/B_s1pyexu6dilEGVQ0qw8fHblzw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/B_s1pyexu6dilEGVQ0qw8fHblzw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/B_s1pyexu6dilEGVQ0qw8fHblzw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/meLHuwCYVGU" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/8834244472470076152/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/05/linking-excel-to-sql.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8834244472470076152?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/8834244472470076152?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/meLHuwCYVGU/linking-excel-to-sql.html" title="Linking Excel to SQL" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/05/linking-excel-to-sql.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IGR305eip7ImA9WxFXFEs.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-4199092662669085779</id><published>2010-05-21T14:12:00.000-04:00</published><updated>2010-05-21T14:12:06.322-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-21T14:12:06.322-04:00</app:edited><title>Please, shut up and take a nap.</title><content type="html">In&lt;a href="http://blogs.techrepublic.com.com/hiner/?p=4158&amp;amp;utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed%3A+techrepublic%2Fhiner+%28TechRepublic+Tech+Sanity+Check%29"&gt; this (month old) pos&lt;/a&gt;t, RIM is reported to tout the fact that BlackBerrys will soon be able to make calls over WiFi, enabling travellers on WiFi-enabled planes to make voice calls. Oh, yay. :(&lt;br /&gt;
I think I'm going to avoid WiFi enabled planes for as long as I can. In this ever-connected digital world, 40,000 ft. up is the only refuge we have from ringtones, overheard conversations, and all the beeps, buzzes, and donks announcing incoming texts, emails, IMs and tweets. Is it such a bad thing to have to read a book, or take a nap for a few hours?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-4199092662669085779?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/TzQkL7fLWQXCiJvF8GW2Wo_Nnig/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TzQkL7fLWQXCiJvF8GW2Wo_Nnig/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/TzQkL7fLWQXCiJvF8GW2Wo_Nnig/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/TzQkL7fLWQXCiJvF8GW2Wo_Nnig/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/bruq5nIeuQ4" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/4199092662669085779/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/05/please-shut-up-and-take-nap.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/4199092662669085779?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/4199092662669085779?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/bruq5nIeuQ4/please-shut-up-and-take-nap.html" title="Please, shut up and take a nap." /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/05/please-shut-up-and-take-nap.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0YBRng6cSp7ImA9WxFXE0U.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-2791291500656999498</id><published>2010-05-20T15:52:00.000-04:00</published><updated>2010-05-20T15:52:37.619-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-20T15:52:37.619-04:00</app:edited><title>The optional requirement; Running batch files as a scheduled in Server 2008</title><content type="html">Got a weird one today. Someone in IS was trying to get a scheduled a batch file to run every morning for some Business Intelligence thingy. He could run the batch file manually, and it ran with no problems. The Task Scheduler, however, completely failed to start the batch file. So he turned to his super-cool sysadmin (me) for assistance.&lt;br /&gt;
I spent about 15 minutes banging my head against the wall with this one. I double-checked permissions, looked in the event logs for errors. I didn't see any obvious reasons why this task wouldn't run the batch file.&lt;br /&gt;
So, I once again turned to the Google, the sysadmin's best friend. As I began to type, autosuggest told me that I was not alone in dealing with this issue. I typed server 2008 task, and google suggested scheduler .bat.&lt;br /&gt;
The first link was &lt;a href="http://social.technet.microsoft.com/Forums/en-US/winservermanager/thread/d47d116e-10b9-44f0-9a30-7406c86c2fbe"&gt;this thread&lt;/a&gt; on Technet. Beware, this thread goes round and round, and most of what they suggest sounds like a pita. Being lazy, I went with the easiest suggested solution. "&lt;strong&gt;Make sure that the task is set to "start in" the folder that contains the batch file: open the task properties, click on the "actions" tab, click on the action and then the "edit" button at the bottom. In the "Edit Action" Window there is a field for "start in (optional)" that you set to the path to the batch file&lt;/strong&gt;."&lt;br /&gt;
That was it. So the optional start in field, is required when running batch files. Awesome.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-2791291500656999498?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/3Y9Jw9pnhbwiIP1_w72bmmoX0ww/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3Y9Jw9pnhbwiIP1_w72bmmoX0ww/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/3Y9Jw9pnhbwiIP1_w72bmmoX0ww/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/3Y9Jw9pnhbwiIP1_w72bmmoX0ww/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/k4xc9LHhXEI" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/2791291500656999498/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/05/optional-requirement-running-batch.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/2791291500656999498?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/2791291500656999498?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/k4xc9LHhXEI/optional-requirement-running-batch.html" title="The optional requirement; Running batch files as a scheduled in Server 2008" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/05/optional-requirement-running-batch.html</feedburner:origLink></entry><entry gd:etag="W/&quot;A0YBRn8zfip7ImA9WxFXE0s.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-6660915064863052636</id><published>2010-05-20T11:25:00.000-04:00</published><updated>2010-05-20T11:25:57.186-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-20T11:25:57.186-04:00</app:edited><title>So much for that idea</title><content type="html">To me, the coolest thing about Citrix XenClient is the Citrix Synchronizer. "Synchronizer provisions, enables policy enforcement, backs up and manages images."&lt;br /&gt;
Cool, right?&lt;br /&gt;
Too bad Synchronizer only runs as a XenServer virtual appliance. I don't feel like standing up a XenServer to play with Synchronizer, which leaves me with no reason to play with XenClient.&lt;br /&gt;
Too bad, Citrix. Why couldn't you just make this an installable app, and let me install it wherever I want?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-6660915064863052636?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/tTbpajO5tqO7sXebxjKSmdTjgqc/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tTbpajO5tqO7sXebxjKSmdTjgqc/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/tTbpajO5tqO7sXebxjKSmdTjgqc/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/tTbpajO5tqO7sXebxjKSmdTjgqc/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/nfXufsdzwLo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/6660915064863052636/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/05/so-much-for-that-idea.html#comment-form" title="2 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/6660915064863052636?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/6660915064863052636?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/nfXufsdzwLo/so-much-for-that-idea.html" title="So much for that idea" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>2</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/05/so-much-for-that-idea.html</feedburner:origLink></entry><entry gd:etag="W/&quot;DEUHRHc7fCp7ImA9WxFXE0s.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-685702547701514265</id><published>2010-05-20T10:37:00.000-04:00</published><updated>2010-05-20T10:37:15.904-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-20T10:37:15.904-04:00</app:edited><title>XenClient; Bare metal hypervisor for laptops</title><content type="html">This is really cool. This is exactly what I've been waiting for VMware to come up with. I didn't expect Citrix to be the first out of the gates with it. Guess what I'm going to be installing on my new E6410 today?&lt;br /&gt;
Also, this post mentions Clonezilla, and Linux Mint. Clonezilla sounds like exactly what our helpdesk has been looking for, and I've&amp;nbsp;been hearing good things about Mint for a while. I'm going to give both of them a try.&lt;br /&gt;
http://www.standalone-sysadmin.com/blog/2010/05/xenclient-baremetal-desktop-virtualization/?utm_source=feedburner&amp;amp;utm_medium=feed&amp;amp;utm_campaign=Feed%3A+standalone-sysadmin%2FrWoU+%28Standalone+Sysadmin%29&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-685702547701514265?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/0i8a9U6La2q4q4RGSrksNQpVTyM/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0i8a9U6La2q4q4RGSrksNQpVTyM/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/0i8a9U6La2q4q4RGSrksNQpVTyM/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/0i8a9U6La2q4q4RGSrksNQpVTyM/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/DWKRu0DASDA" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/685702547701514265/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/05/xenclient-bare-metal-hypervisor-for.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/685702547701514265?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/685702547701514265?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/DWKRu0DASDA/xenclient-bare-metal-hypervisor-for.html" title="XenClient; Bare metal hypervisor for laptops" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/05/xenclient-bare-metal-hypervisor-for.html</feedburner:origLink></entry><entry gd:etag="W/&quot;D0IFR3g8fip7ImA9WxFXEkw.&quot;"><id>tag:blogger.com,1999:blog-1610060986113184714.post-7490889331650280398</id><published>2010-05-18T16:45:00.000-04:00</published><updated>2010-05-18T16:45:16.676-04:00</updated><app:edited xmlns:app="http://www.w3.org/2007/app">2010-05-18T16:45:16.676-04:00</app:edited><title>How to defeat Dell Latitude On</title><content type="html">When the Latitude On feature came out last year, I was not into it. Maybe I'm paranoid, but&amp;nbsp;a small linux installation living on each laptop with access to the hard drive, and network interface sounds like it could potentially serve as a foothold for an attacker. I don't want to have to worry about securing two operating systems on each laptop. I was dismayed when Dell told me that there was no way to forgo this feature.&lt;br /&gt;
They told me that it could be turned off in the BIOS, but I didn't want it turned off. I wanted it gone.&lt;br /&gt;
Well, turns out there is a way to make it gone, by just doing what I do all the time anyway.&lt;br /&gt;
Latitude On is available in two ways. Either installed on a piece of flash, or installed to the HDD.&lt;br /&gt;
When speccing out the global standard&amp;nbsp;for the E6410, I went with the HDD version. The flash version costs more, why pay more for something I don't want?&lt;br /&gt;
I received a demo model from Dell "to confirm that this configuration will work for us" (I just wanted a new laptop).&lt;br /&gt;
As I always do, I used killdisk to zero-fill the drive, then re-installed Windows. I always make sure that all partitions are destroyed on new machines, including the MBR. I don't know what country they made this in, or what kind of crapware might have been pre-loaded on it. Plus I hate Dell's ugly wallpapers.&lt;br /&gt;
This, of course, wipes out the partition where Latitude On lives. Latitude On? nOpe!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/1610060986113184714-7490889331650280398?l=www.epoxyjournal.com' alt='' /&gt;&lt;/div&gt;
&lt;p&gt;&lt;a href="http://feedads.g.doubleclick.net/~a/lHdqQgUXO6vNlB751tHnGhlQluw/0/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lHdqQgUXO6vNlB751tHnGhlQluw/0/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;br/&gt;
&lt;a href="http://feedads.g.doubleclick.net/~a/lHdqQgUXO6vNlB751tHnGhlQluw/1/da"&gt;&lt;img src="http://feedads.g.doubleclick.net/~a/lHdqQgUXO6vNlB751tHnGhlQluw/1/di" border="0" ismap="true"&gt;&lt;/img&gt;&lt;/a&gt;&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/EpoxyJournal/~4/iLo7Zl-Zpjo" height="1" width="1"/&gt;</content><link rel="replies" type="application/atom+xml" href="http://www.epoxyjournal.com/feeds/7490889331650280398/comments/default" title="Post Comments" /><link rel="replies" type="text/html" href="http://www.epoxyjournal.com/2010/05/how-to-defeat-dell-latitude-on.html#comment-form" title="0 Comments" /><link rel="edit" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/7490889331650280398?v=2" /><link rel="self" type="application/atom+xml" href="http://www.blogger.com/feeds/1610060986113184714/posts/default/7490889331650280398?v=2" /><link rel="alternate" type="text/html" href="http://feedproxy.google.com/~r/EpoxyJournal/~3/iLo7Zl-Zpjo/how-to-defeat-dell-latitude-on.html" title="How to defeat Dell Latitude On" /><author><name>LowLatency</name><uri>http://www.blogger.com/profile/08729820475665658080</uri><email>noreply@blogger.com</email><gd:image rel="http://schemas.google.com/g/2005#thumbnail" width="16" height="16" src="http://img2.blogblog.com/img/b16-rounded.gif" /></author><thr:total>0</thr:total><feedburner:origLink>http://www.epoxyjournal.com/2010/05/how-to-defeat-dell-latitude-on.html</feedburner:origLink></entry></feed>

