<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-7656056675700026432</id><updated>2012-02-02T11:04:23.200-08:00</updated><category term='install'/><category term='terminal service'/><category term='kb'/><category term='weak'/><category term='bsod'/><category term='av'/><category term='legacy'/><category term='symmetra'/><category term='retail'/><category term='trendmicro'/><category term='mx5000'/><category term='directory'/><category term='wal-mart'/><category term='bandwith'/><category term='youtube'/><category term='officescan'/><category term='webhits'/><category term='command'/><category term='upgrade'/><category term='dell'/><category term='firefox'/><category term='cisco'/><category term='acid'/><category term='encoder'/><category term='radmin'/><category term='fbl'/><category term='webhits.dll'/><category term='spam'/><category term='qwest'/><category term='firmware'/><category term='cmd'/><category term='arf'/><category term='xp'/><category term='rant'/><category term='RDP'/><category term='patch'/><category term='speed'/><category term='iis'/><category term='wme'/><category term='wrt54'/><category term='whs'/><category term='knowledge base'/><category term='aol'/><category term='feed back loop'/><category term='ts'/><category term='smartcell'/><category term='security'/><category term='version 8'/><category term='battery'/><category term='memory'/><category term='version'/><category term='symetra'/><category term='rfc822'/><category term='htw'/><category term='sans'/><category term='blank password'/><category term='linksys'/><category term='isp'/><category term='ups'/><category term='alert'/><category term='matrix'/><category term='expired'/><category term='runtime'/><category term='tuesday'/><category term='kb328832'/><category term='trend'/><category term='session'/><category term='microsoft'/><category term='xr'/><category term='routing'/><category term='sp3'/><category term='remote desktop'/><category term='poweredge'/><category term='pre-release'/><category term='squidoo'/><category term='command line'/><category term='apc'/><category term='exploit'/><category term='kbalertz'/><category term='lockdown'/><category term='vista'/><category term='keepalive'/><title type='text'>Technically Inclined</title><subtitle type='html'>Dean's IT Ramblings</subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>33</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-6804563969145592451</id><published>2010-10-04T17:25:00.001-07:00</published><updated>2010-10-04T17:35:48.209-07:00</updated><title type='text'>Cisco VPN Client and Network connection issues</title><content type='html'>If you are having network connection issues and you have Cisco VPN client installed, try stopping the Cisco Systems, Inc. VPN Services.  This service seems to conflict with certain LAN protocols.&lt;br /&gt;&lt;br /&gt;Specifically, the ongoing issue I have experienced is with EMC Retrospect backup client and the Cisco VPN service.  The workaround is to simply stop the Cisco VPN service, allow the backup to complete, then restart Cisco VPN.  I believe it has to do with the Piton network protocol that Retrospect client uses because I don't have any other issues except for Retrospect backups.&lt;br /&gt;Here are the specifics:&lt;br /&gt;&lt;ul&gt;&lt;li&gt;OS Windows XP Pro SP3&lt;/li&gt;&lt;li&gt;Retrospect Client version 7.0.107 (more recent versions have the same issue)&lt;/li&gt;&lt;li&gt;Cisco VPN Client version 4.8.01.0300 (more recent version have the same issue)&lt;/li&gt;&lt;/ul&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-6804563969145592451?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/6804563969145592451/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=6804563969145592451' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/6804563969145592451'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/6804563969145592451'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2010/10/cisco-vpn-client-and-network-connection.html' title='Cisco VPN Client and Network connection issues'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-4994888480186027274</id><published>2010-09-08T10:55:00.000-07:00</published><updated>2010-09-08T11:06:34.849-07:00</updated><title type='text'>ESET NOD32 and blocked HTTP requests</title><content type='html'>Users complaining they do not have internet access and cannot POP their email from server. Turns out network connections are fine (can ping, telnet, ftp etc) but all HTTP and SMTP requests were blocked. First thought, there is a nasty virus or malware lurking around the network. But no... turns out NOD32 (our virus and spyware protection software) was the culprit itself.  In order to provide it's "Web access protection" and "Email client protection" it creates a local proxy to filter all requests. Well, somehow (yet to be determined) the proxy was hung or crashed in some way that blocked all Http and SMTP requests.  For most machines, this was fixed with a simple restart of the computer, others, NOD32 had to be reinstalled.&lt;br /&gt;While I dont yet have a firm solution to the problem or a determination as to what triggered it, I do know that at the time of the NOD32 issues, our central NOD32 server was very slow and nearly non-responsive. Why that would cause clients to hand, idk, but at this point, it is the only indication of a possible trigger.&lt;br /&gt;&lt;br /&gt;I will follow up with any new solutions.  Please post here if you have more info. Thanks.&lt;br /&gt;&lt;br /&gt;We are currently running ESET NOD32   4.2.40.0  on Windows XP sp3 clients.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-4994888480186027274?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/4994888480186027274/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=4994888480186027274' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/4994888480186027274'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/4994888480186027274'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2010/09/eset-nod32-and-blocked-http-requests.html' title='ESET NOD32 and blocked HTTP requests'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-4359469447075484506</id><published>2009-01-22T17:50:00.000-08:00</published><updated>2009-01-22T18:16:23.613-08:00</updated><title type='text'>Audio CD playback problem on Sony DVD RW drives</title><content type='html'>&lt;span style="font-family:arial;"&gt;My Dell Optiplex 620 has two oem installed Sony DVD RW drives. Everything works fine with the exception of playing audio CDs. One of the drives plays music very choppy so I set out to fix the issue. Here is the setup:&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:arial;"&gt;    IDE 0 is a SONY DVD RW DRU-180A    (plays OK... "good drive")&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:arial;"&gt;    IDE 1 is a SONY DVD RW DRU-835A   (problem drive)&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:arial;"&gt;These are the only IDE devices in the machine. The hard drives are SATA. In the original factory configuration, both drives were set to cable select and only the IDE 0 drive would play audio properly, but IDE 1 would be choppy. So I tried a number of configurations as follows:&lt;br /&gt;&lt;/span&gt;&lt;ol style="font-family: arial;"&gt;&lt;li&gt;I tried setting the jumper to force IDE 0 as master and IDE 1 as secondary... no change. &lt;/li&gt;&lt;li&gt;I tried swapping the jumpers to reverse the order (DRU-835A now IDE 0 master) and now the "good drive, bad drive" problem is reversed... the DRU-835A plays ok.&lt;/li&gt;&lt;li&gt;Only connect one drive at a time with jumper on cable select and at the end cable connector. In this config, either drive would play properly (as IDE 0).&lt;/li&gt;&lt;/ol&gt;&lt;span style="font-family:arial;"&gt;So, I sumized that these drives do not like to be secodary drives, at least not for audio playback purposes. I have done disk copies and many burns without issue on either drive. &lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:arial;"&gt;Notes:&lt;/span&gt;&lt;br /&gt;&lt;ol style="font-family: arial;"&gt;&lt;li&gt;I checked firmware versions on both drives and the DRU-180A is on the most recent firmware, and the DRU-835A is assumed to be on the latest firmware as Sony has not post a firware update on their site for this drive. &lt;/li&gt;&lt;li&gt;Audio playback was tried with both Windows Media 11 and Nero Media Player 1.4.0.22&lt;/li&gt;&lt;/ol&gt;&lt;span style="font-family:arial;"&gt;I don't have a solution here except to simply always playback on the IDE 0 drive.&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-family:arial;"&gt;Helpful comments always welcome :)&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-4359469447075484506?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/4359469447075484506/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=4359469447075484506' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/4359469447075484506'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/4359469447075484506'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2009/01/audio-cd-playback-problem-on-sony-dvd.html' title='Audio CD playback problem on Sony DVD RW drives'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-1099211174294570965</id><published>2008-04-07T15:26:00.000-07:00</published><updated>2008-04-07T15:48:47.129-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='sp3'/><category scheme='http://www.blogger.com/atom/ns#' term='version'/><category scheme='http://www.blogger.com/atom/ns#' term='remote desktop'/><category scheme='http://www.blogger.com/atom/ns#' term='whs'/><category scheme='http://www.blogger.com/atom/ns#' term='expired'/><category scheme='http://www.blogger.com/atom/ns#' term='xp'/><category scheme='http://www.blogger.com/atom/ns#' term='pre-release'/><category scheme='http://www.blogger.com/atom/ns#' term='RDP'/><title type='text'>Remote Desktop Connection has Expired (Pre-Release Version)</title><content type='html'>&lt;span style="font-weight: bold;font-family:arial;" &gt;MICRO$OFT STRIKES AGAIN...&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:arial;"&gt;Today, many Remote Desktop users were struck with the following message:&lt;/span&gt;&lt;br /&gt;&lt;span id="_ctl0_MainContent_PostFlatView"  style="font-family:arial;"&gt;&lt;span&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;"The &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_0"&gt;Pre&lt;/span&gt;-Release Version of Remote Desktop Connection has expired. To download the full version of Remote Desktop Connection, Go to Windows update or  contact your system administrator"&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;This is a result of installing the recently released &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_1"&gt;XP&lt;/span&gt; SP3 RC2 from Microsoft. Apparently they packaged the new Remote Desktop Connection in SP3 with an expiration date (assuming 4/7/2008).  Thanks so much for the warning Microsoft! This came on as a big Monday morning surprise to many IT pros as well as home server users (&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_2"&gt;WHS&lt;/span&gt;).&lt;br /&gt;&lt;br /&gt;The fix?&lt;br /&gt;I have seen many posts where people are &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_3"&gt;uninstalling&lt;/span&gt; SP3, which works however rather extreme.&lt;br /&gt;&lt;br /&gt;As a temporary workaround, you can simply copy the previous version of the following two files into your windows System32 folder. You can copy these files from another &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_4"&gt;pre&lt;/span&gt;-SP3 &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_5"&gt;XP&lt;/span&gt; machine or simply search your local hard drive and use a previous version which will be in a previous $&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_6"&gt;NtServicePackUninstall&lt;/span&gt;$ folder or in the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_7"&gt;DLLCACHE&lt;/span&gt; folder:&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;    &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_8"&gt;mstscax&lt;/span&gt;.&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_9"&gt;dll&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;span style="font-family:courier new;"&gt;    &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_10"&gt;mstsc&lt;/span&gt;.&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_11"&gt;exe&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;Then execute the &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_12"&gt;mstsc&lt;/span&gt;.&lt;span class="blsp-spelling-error" id="SPELLING_ERROR_13"&gt;exe&lt;/span&gt; (which is the same &lt;span class="blsp-spelling-error" id="SPELLING_ERROR_14"&gt;exe&lt;/span&gt; name as the expired version). This effectively rolls back your Remote Desktop version to the previous version.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-1099211174294570965?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/1099211174294570965/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=1099211174294570965' title='32 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/1099211174294570965'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/1099211174294570965'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2008/04/remote-desktop-connection-has-expired.html' title='Remote Desktop Connection has Expired (Pre-Release Version)'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>32</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-7648028900515402869</id><published>2007-11-07T12:17:00.000-08:00</published><updated>2007-11-07T12:31:30.493-08:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='firefox'/><category scheme='http://www.blogger.com/atom/ns#' term='memory'/><title type='text'>Firefox 2.0.0.9 - Have they Tamed the Animal?</title><content type='html'>I have written a couple of times about Firefox 2.0+ issues mostly regarding memory usage and memory leaks. Recently Mozilla released 2.0.0.9 which is intended to primarily be a stability (not security this time) release. Well, I am pleased to say that after about a week of use, the memory leak problem seems to have been resolved.&lt;br /&gt;Thank You Mozilla!&lt;br /&gt;&lt;br /&gt;In addition, I have determined that one of the extentions I &lt;span style="font-weight: bold;"&gt;was&lt;/span&gt; using was a big memory hog. The extension was ANSWERS 2.2.27&lt;br /&gt;It would use nearly 100mb of ram upon Firefox startup. I expect that they were using some sort of memory resident database of common words. Well, it was not worth the 100mb to me, so goodby Answers 2.2.27.&lt;br /&gt;&lt;br /&gt;Now without Answers and with the resolved Firefox memory leaks, I am happy to report that Firefox is back to the "lean mean browsing machine" that I once loved.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-7648028900515402869?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/7648028900515402869/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=7648028900515402869' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7648028900515402869'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7648028900515402869'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/11/firefox-2009-have-they-tamed-animal.html' title='Firefox 2.0.0.9 - Have they Tamed the Animal?'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-3843009457385697132</id><published>2007-09-17T13:04:00.000-07:00</published><updated>2007-09-17T13:35:22.192-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='rant'/><category scheme='http://www.blogger.com/atom/ns#' term='microsoft'/><title type='text'>Microsoft Forces Stealth Updates Even without Automatic Updates On</title><content type='html'>Here is another one from the &lt;span style="font-weight: bold;"&gt;"Microsoft is smarter than you are"&lt;/span&gt; file.&lt;br /&gt;&lt;br /&gt;Microsoft was recently exposed for pushing out updates to your computer even if you don't have Automatic Updates turned on. Their position is that they need to continue to update the Windows Update Service components in order to notify you of updates and "maintain the quality of the service".&lt;br /&gt;&lt;br /&gt;This presents a huge trust issue for many, especially IT support personnel, myself included. The reasons that Microsoft has announced on this issue are somewhat valid, but still cause a trust issue.  If they are doing this unilaterally with some components, what keeps them from updating other components that &lt;span style="font-weight: bold;"&gt;they choose&lt;/span&gt; to update at will? The fact that Microsoft tried to do this behind the scenes is quite alarming.&lt;br /&gt;&lt;br /&gt;Partnering with &lt;span style="font-weight: bold;"&gt;BIG BROTHER&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;There are many that are totally outraged by this Microsoft trust issue. My take on it is that you knew what you were getting into when purchasing and choosing to run Microsoft products, so deal with it. If you don't trust Microsoft to write your OS and write patches for your OS, then go play with someone else's OS.  Granted, there are not many choices that most corporate average desktop users can deal with and with that, many IT support personnel are stuck with Microsoft desktops.  If Microsoft screws this up and some compromised code gets pushed out to your desktops, yes, it will hurt and screw you up for a few days, but think about the pain you would endure to attempt to convert those desktop users to Ubuntu, or any other Unix like environment.  Ultimately, Microsoft would be at fault for leaving the back door open.&lt;br /&gt;&lt;br /&gt;For more detail on the MS stealth updates:&lt;br /&gt;&lt;p&gt;&lt;span style=";font-family:Arial;font-size:85%;"  &gt;&lt;span style=";font-family:Arial;font-size:10;"  &gt;&lt;a title="blocked::http://blogs.technet.com/mu/archive/2007/09/13/how-windows-update-keeps-itself-up-to-date.aspx" href="http://blogs.technet.com/mu/archive/2007/09/13/how-windows-update-keeps-itself-up-to-date.aspx"&gt;http://blogs.technet.com/mu/archive/2007/09/13/how-windows-update-keeps-itself-up-to-date.aspx&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;  &lt;o:p&gt;&lt;/o:p&gt;&lt;/p&gt;&lt;span style=";font-family:Arial;font-size:85%;"  &gt;&lt;span style=";font-family:Arial;font-size:10;"  &gt;&lt;a title="blocked::http://windowssecrets.com/comp/070913/#story1" href="http://windowssecrets.com/comp/070913/#story1"&gt;http://windowssecrets.com/comp/070913/#story1&lt;/a&gt;&lt;/span&gt;&lt;/span&gt;  &lt;o:p&gt;&lt;/o:p&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-3843009457385697132?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/3843009457385697132/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=3843009457385697132' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/3843009457385697132'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/3843009457385697132'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/09/microsoft-forces-stealth-updates-even.html' title='Microsoft Forces Stealth Updates Even without Automatic Updates On'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-7146138705076507645</id><published>2007-08-15T11:13:00.000-07:00</published><updated>2007-08-31T10:21:09.401-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='routing'/><category scheme='http://www.blogger.com/atom/ns#' term='isp'/><category scheme='http://www.blogger.com/atom/ns#' term='qwest'/><title type='text'>Does Qwest still do Cold-Potato Routing?</title><content type='html'>This is somewhat of a rhetorical question, but I do question it.  Qwest has always (AFAIK) advertised and bragged about this feature with their DIA services.&lt;br /&gt;&lt;br /&gt;First, some may be wondering, what the heck is Cold-Potato Routing?  The best explanation may be that it is the opposite of Hot-Potato routing in which an ISP will hand off it packets to a peer or downstream ISP as soon as possible to get it off of their system. So, in Cold-Potato routing, the well intentioned ISP will hold onto the traffic and haul it across a geographic region as far as possible before handing it over to the downstream provider. This provides a best end-to-end quality of service for the ISP customers, assuming the ISP has the backbone to handle it.&lt;br /&gt;&lt;br /&gt;The reason I question weather Qwest is still providing Cold-potato routing is that if I trace routes from my Los Angeles based POP (Qwest provided) to my co-lo in Chicago, IL the traffic gets handed off in Los Angeles to Level 3. net.  Level3 then hauls it across the country to it's Chicago facility.   Now, I know that Qwest has a big OC-192 backbone direct from their Burbank, CA TeraPOP direct to Chicago, IL TeraPOP. So, what the heck?  Can anyone shine some light on this issue?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-7146138705076507645?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/7146138705076507645/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=7146138705076507645' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7146138705076507645'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7146138705076507645'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/08/does-qwest-still-do-cold-potato-routing.html' title='Does Qwest still do Cold-Potato Routing?'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-8227025792912955669</id><published>2007-08-15T10:49:00.000-07:00</published><updated>2007-08-15T11:13:18.040-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='firefox'/><category scheme='http://www.blogger.com/atom/ns#' term='memory'/><title type='text'>Firefox memory leak revisited</title><content type='html'>I recently wrote about Firefox 2 becoming a pig, meaning that it consumes huge amounts of memory and slows down. This of course is a memory leak as expected.  During the course of research of the problem I have discovered a couple of things that are short term work arounds.&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Restart Firefox every day. It consumes memory over time (NSS!) so by restarting it, the memory will be released&lt;/li&gt;&lt;li&gt;uninstall any add-ons (extensions) that you don't use.&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Uninstall extra themes&lt;br /&gt;&lt;/li&gt;&lt;li&gt;Run Firefox in Safe Mode&lt;/li&gt;&lt;li&gt;Keep unused browser tabs closed&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;I found this list of known problematic extensions that you should check out to make sure you are not running them:&lt;br /&gt;&lt;a href="http://kb.mozillazine.org/Problematic_extensions"&gt;http://kb.mozillazine.org/Problematic_extensions&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;There are claims that the extensions (especially the problematic ones) are causing the memory leaks. However, I only run about 4 lightweight extensions that I keep updated and only the default Firefox theme and I still have the memory leak problem. In fact, today Firefox on my desktop is comsuming over 163mb after restarting it about 18 hours ago. Guess it's about time for another restart.&lt;br /&gt;&lt;br /&gt;Come On Mozilla Foundation!  Get this fixed or I fear that many will resort back to IE.  Oh the guilt...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-8227025792912955669?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/8227025792912955669/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=8227025792912955669' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8227025792912955669'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8227025792912955669'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/08/firefox-memory-leak-revisited.html' title='Firefox memory leak revisited'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-7981007038690382038</id><published>2007-08-09T11:42:00.000-07:00</published><updated>2007-08-09T11:50:36.175-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='cisco'/><category scheme='http://www.blogger.com/atom/ns#' term='speed'/><category scheme='http://www.blogger.com/atom/ns#' term='bandwith'/><title type='text'>Check Your Network Switch Speed Negotiation</title><content type='html'>In dealing with a recent bandwidth issue, we discovered that it was a speed negotiation issue between a Cisco 3845 router and a Cisco PIX Firewall. You would think that these two interfaces would do a better job of speed negotiation. There were no errors recorded on either side but we experienced horrible throughput... like 500kpbs.  The issue was resolved by setting both sides to AUTO and reset the interfaces.&lt;br /&gt;&lt;br /&gt;I have had many issues in the past with Cisco interfaces to other manufacturer interfaces (Netgear and Linksys to name a couple). They don't do auto negotiate well, so I have learned to fix the Cisco interface to the max speed of the other side. But, in the case of Cisco to Cisco, it seems that AUTO is the best choice... at least in this case.&lt;br /&gt;&lt;br /&gt;The moral to the story is that when troubleshooting bandwidth issues, alway check your speed setting settings on interfaces... even when no errors are recorded.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-7981007038690382038?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/7981007038690382038/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=7981007038690382038' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7981007038690382038'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7981007038690382038'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/08/check-your-network-switch-speed.html' title='Check Your Network Switch Speed Negotiation'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-5331186769545439091</id><published>2007-07-25T14:51:00.001-07:00</published><updated>2007-07-25T15:01:42.004-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='battery'/><category scheme='http://www.blogger.com/atom/ns#' term='ups'/><category scheme='http://www.blogger.com/atom/ns#' term='apc'/><category scheme='http://www.blogger.com/atom/ns#' term='runtime'/><category scheme='http://www.blogger.com/atom/ns#' term='symmetra'/><category scheme='http://www.blogger.com/atom/ns#' term='symetra'/><title type='text'>Rotate Your Spare UPS Batteries</title><content type='html'>If you keep spare UPS batteries on the shelf, make sure you rotate them into your running UPS unit every month or so to keep them fresh and charged. &lt;br /&gt;I am mostly speaking of data center level user replaceable UPS batteries like a APC Symmetra or similar. Keeping spare batteries is a good idea for replacement of a failed battery and for extra runtime when the lights do go out. In the case of extra runtime needed, you can keep extra batteries on the shelf and swap them in if your runtime gets low due to a power outage and you don't have a generator on standby. Just make sure you rotate them into the unit every month or so. The approximate shelf life of a Symmetra battery is 6 months. After that, they are considered dead or at least reduced efficiency.&lt;br /&gt;&lt;br /&gt;Another UPS battery tip is to date stamp the battery when you buy it. This will help control the shelf life as well as overall life as the life expectancy of one of these is usually about 2 years.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-5331186769545439091?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/5331186769545439091/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=5331186769545439091' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/5331186769545439091'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/5331186769545439091'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/07/rotate-your-spare-ups-batteries.html' title='Rotate Your Spare UPS Batteries'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-3852479377994987229</id><published>2007-07-20T11:25:00.000-07:00</published><updated>2007-07-20T11:36:22.226-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='version 8'/><category scheme='http://www.blogger.com/atom/ns#' term='av'/><category scheme='http://www.blogger.com/atom/ns#' term='upgrade'/><category scheme='http://www.blogger.com/atom/ns#' term='trendmicro'/><category scheme='http://www.blogger.com/atom/ns#' term='officescan'/><title type='text'>TrendMicro OfficeScan Upgrade</title><content type='html'>Kudos to Trend Micro for providing a very seamless upgrade from OfficeScan/ServerProtect 7.3 to 8.0.  To my surprise, it was as simple as validating the new license key, downloading version 8, and install on our central TrendMicro AV server. Our AV server then seamlessly and quickly pushed out the client updates without user interruption. In addition, there are some nice features in the new version that we can take advantage of.&lt;br /&gt;&lt;br /&gt;I was anticipating a nightmare of uninstalling clients and re-installing (similar to the nightmare Symantec caused us a couple of years ago... arrrggg, curse you Symantec!), but it was actually very pleasant.&lt;br /&gt;&lt;br /&gt;Thanks to Trend Micro!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-3852479377994987229?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/3852479377994987229/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=3852479377994987229' title='8 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/3852479377994987229'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/3852479377994987229'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/07/trendmicro-officescan-upgrade.html' title='TrendMicro OfficeScan Upgrade'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>8</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-5594461283053803345</id><published>2007-07-16T10:32:00.000-07:00</published><updated>2007-07-16T10:39:34.724-07:00</updated><title type='text'>Beware of Black Market Network Hardware</title><content type='html'>Black Market Network Equipment?  Oh yes, and something to watch out for.&lt;br /&gt;It only recently came to my attention that this even existed. There is a growing problem of counterfeit, imitation, fake and the like of Cisco and other high end network equipment. When recently shopping around for a couple of Cisco boxes is when I was made aware of this problem through a couple of trusted used network hardware resellers.&lt;br /&gt;&lt;br /&gt;There is an organization called &lt;a href="http://www.uneda.com"&gt;UNEDA &lt;/a&gt;that has taken the lead on bringing attention to the problem using an alliance of more than 300 of the top used network equipment dealers worldwide. Check them out and be aware!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-5594461283053803345?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/5594461283053803345/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=5594461283053803345' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/5594461283053803345'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/5594461283053803345'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/07/beware-of-black-market-network-hardware.html' title='Beware of Black Market Network Hardware'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-780439098703732284</id><published>2007-07-11T12:01:00.001-07:00</published><updated>2007-07-11T12:21:06.950-07:00</updated><title type='text'>Working in IT Hazardous to your Health?</title><content type='html'>Most would say no, and for the most part, IT work is a pretty safe profession. But, what about the IT guy or girl that sits in one place with their hands on the keyboard most of the day? Or, the IT person that lifts servers or desktop computers often? Are you plagued with shoulder pain, headaches and backaches? Here are a few tips to keep your body pain free (or at least, less pain):&lt;br /&gt;&lt;ul&gt;&lt;li&gt;Keep your chair adjusted properly. In time most chairs will move out of adjustment through daily use. Check it on a regular basis.&lt;/li&gt;&lt;li&gt;Get up and Move!  Walk to lunch, walk around the building or up a few flights of stairs during your break time.&lt;/li&gt;&lt;li&gt;Use a phone headset. If you spend a reasonable amount of time on the phone, get a headset instead of straining your shoulder and neck.&lt;/li&gt;&lt;li&gt;Use the buddy system for lifting and moving equipment.  Don't try to be the hero by racking up equipment by yourself. You also run the risk of dropping a very expensive piece of equipment... that would not be good!&lt;/li&gt;&lt;li&gt;Don't strain your eyes. Adjust your monitors and wear the proper eye correction.&lt;/li&gt;&lt;/ul&gt;For me, I suffer from frequent neck strain and headaches when I don't pay attention to these details.&lt;br /&gt;&lt;br /&gt;Take Care.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-780439098703732284?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/780439098703732284/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=780439098703732284' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/780439098703732284'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/780439098703732284'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/07/working-in-it-hazardous-to-your-health.html' title='Working in IT Hazardous to your Health?'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-6755492805300417332</id><published>2007-07-10T15:01:00.000-07:00</published><updated>2007-07-10T15:06:43.538-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='tuesday'/><category scheme='http://www.blogger.com/atom/ns#' term='sans'/><category scheme='http://www.blogger.com/atom/ns#' term='patch'/><category scheme='http://www.blogger.com/atom/ns#' term='microsoft'/><title type='text'>M$ Patch Tuesday Overview Report</title><content type='html'>SANS released a very useful "&lt;a href="http://isc.sans.org/diary.html?storyid=3120"&gt;July 'Black Tuesday' overview&lt;/a&gt;" report. I don't know if they do this for every patch release Tuesday, but it is a nice report and I suggest you check it out at:&lt;br /&gt;&lt;a href="http://isc.sans.org/diary.html?storyid=3120&amp;rss"&gt;http://isc.sans.org/diary.html?storyid=3120&amp;amp;rss&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;They have columns for level of importance for Servers and Desktops (ISC rating) which is a nice feature. I like getting the second opinion from SANS!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-6755492805300417332?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/6755492805300417332/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=6755492805300417332' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/6755492805300417332'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/6755492805300417332'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/07/m-patch-tuesday-overview-report.html' title='M$ Patch Tuesday Overview Report'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-1669480202493436654</id><published>2007-07-09T09:32:00.000-07:00</published><updated>2007-07-09T09:43:22.754-07:00</updated><title type='text'>Company eMail Privacy</title><content type='html'>Company email Privacy? Not so much.&lt;br /&gt;&lt;br /&gt;When it comes to sending email from your employers company email address, there is no such thing as privacy. Company email users need to be reminded of this. It should start with an Acceptable Use Policy (AUP) that is signed upon employment and then employees need to be reminded of this through training or occasional memos.&lt;br /&gt;&lt;br /&gt;Many people do not understand that any email communication via a company email account is company property.  These message are typically stored in a long term archive and can be recalled upon by court order in a legal case. It could be a law suit with a client, competitor, employment, sex harassment etc.  Any email that is even remotely related to the case can be presented as evidence. As a result, employees need to be trained to think about every email message that they compose.&lt;br /&gt;&lt;br /&gt;These policies and training many times falls in the hands of your IT department... we get to be the bad guys... again! It's no wonder that they hate us.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-1669480202493436654?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/1669480202493436654/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=1669480202493436654' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/1669480202493436654'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/1669480202493436654'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/07/company-email-privacy.html' title='Company eMail Privacy'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-8790546124217887499</id><published>2007-06-27T12:09:00.000-07:00</published><updated>2007-06-27T12:18:50.209-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='spam'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><category scheme='http://www.blogger.com/atom/ns#' term='microsoft'/><title type='text'>Beware of Fake Microsoft Patch</title><content type='html'>&lt;span style="font-size:100%;"&gt;&lt;span style="font-family: arial;"&gt;The spam will have a subject of:&lt;/span&gt;&lt;br /&gt;&lt;/span&gt;&lt;span style="font-family: arial;font-family:&amp;quot;;font-size:100%;"  &gt;&lt;span style="font-size:85%;"&gt;&lt;span style="font-family: courier new;"&gt;Microsoft Security Bulletin MS07-0065 - Critical Update&lt;/span&gt;&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;The body claims to have a patch for a zero day vulnerability, but contains &lt;/span&gt;&lt;span style="font-family: arial;font-family:&amp;quot;;font-size:100%;"  &gt;malware&lt;/span&gt;&lt;span style="font-family: arial;font-family:&amp;quot;;font-size:100%;"  &gt;.&lt;br /&gt;&lt;br /&gt;For more detail, please see this SANS alert:&lt;br /&gt;&lt;a href="http://isc.sans.org/diary.html?storyid=3054&amp;rss"&gt;http://isc.sans.org/diary.html?storyid=3054&amp;amp;rss&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;A real, legitimate Microsoft Security Bulletin will be a PGP Signed text message.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-8790546124217887499?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/8790546124217887499/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=8790546124217887499' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8790546124217887499'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8790546124217887499'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/beware-of-fake-microsoft-patch.html' title='Beware of Fake Microsoft Patch'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-8010585428582721378</id><published>2007-06-26T13:41:00.000-07:00</published><updated>2007-06-26T13:44:38.625-07:00</updated><title type='text'>Busy with SAS70</title><content type='html'>I have not kept up with this blog for the last week or so because I am very busy with SAS70 security auditors.  If you want to know what this is SAS70 thing is all about, drop me a comment.  Now, back to the hot seat =)&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-8010585428582721378?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/8010585428582721378/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=8010585428582721378' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8010585428582721378'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8010585428582721378'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/busy-with-sas70.html' title='Busy with SAS70'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-744422188955777922</id><published>2007-06-19T09:56:00.000-07:00</published><updated>2007-06-19T10:12:01.862-07:00</updated><title type='text'>Firefox 2.0 becoming a PIG ?</title><content type='html'>Recently Firefox 2.0 (I am on 2.0.0.4 to be exact) seems to either have a memory leak or is simply becoming a resource hog.  It is currently using over 200mb or memory with just three tabs open.  Also, it seems that in time the auto complete features of both the address box and the search box use more and more CPU and become slower and slower.   I get the old typing one character at a time response in these boxes. &lt;br /&gt;&lt;br /&gt;I mention the slower over time because I will leave Firefox open for days because I have network monitor tools running in a couple of tabs.  If I restart Firefox it will start back up using about 36mb of memory with my initial two tabs open. Looks like a mem leak to me! I guess the short term fix is to restart Firefox daily.&lt;br /&gt;&lt;br /&gt;Also, as a side note... I had used Fasterfox a few weeks ago and with Fasterfox it seemed to chew up memory much faster and performance degraded within hours. So much for &lt;span style="font-weight: bold;"&gt;Faster&lt;/span&gt;fox.  I uninstalled Fasterfox and to get back to original Firefox (Slowerfox ???) and now it is back to taking a couple days to getting back to a crawl.&lt;br /&gt;&lt;br /&gt;Anyone have more info or a fix for this out there?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-744422188955777922?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/744422188955777922/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=744422188955777922' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/744422188955777922'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/744422188955777922'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/firefox-20-becoming-pig.html' title='Firefox 2.0 becoming a PIG ?'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-8827942841824859084</id><published>2007-06-18T11:02:00.000-07:00</published><updated>2007-06-18T11:10:41.461-07:00</updated><title type='text'>.hk TLD attack warning</title><content type='html'>I came into the office today and noticed a flood of email with subject lines like:&lt;br /&gt;&lt;br /&gt;[name] sent you a [domain].hk! Greeting&lt;br /&gt;&lt;br /&gt;Inside, the message invites you to view a greeting card within 30 days. This URL contains malicious code that attempts to exploit Internet Explorer vulnerabilities among other Windows vulnerabilities.&lt;br /&gt;&lt;br /&gt;Email server administrators should take action immediately to filter and kill these messages.&lt;br /&gt;&lt;br /&gt;See more here from SANS:&lt;br /&gt;&lt;a href="http://isc.sans.org/diary.html?storyid=2985"&gt;http://isc.sans.org/diary.html?storyid=2985&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-8827942841824859084?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/8827942841824859084/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=8827942841824859084' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8827942841824859084'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8827942841824859084'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/hk-tld-attack-warning.html' title='.hk TLD attack warning'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-7970076143387414694</id><published>2007-06-12T14:15:00.000-07:00</published><updated>2007-06-12T14:51:51.013-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='mx5000'/><category scheme='http://www.blogger.com/atom/ns#' term='smartcell'/><category scheme='http://www.blogger.com/atom/ns#' term='apc'/><category scheme='http://www.blogger.com/atom/ns#' term='acid'/><category scheme='http://www.blogger.com/atom/ns#' term='xr'/><category scheme='http://www.blogger.com/atom/ns#' term='matrix'/><title type='text'>APC MX5000 Battery Acid</title><content type='html'>In the past, we have had several battery acid spills from the old APC Matrix 5000 Smartcell XR battery units.  These units essentially use  automotive type batteries in the XR cabinet that are sealed and set on their side. If one of these batteries fails, they often overheat and will leak acid from the sealed caps. In fact, we have had a couple that blew the caps out and created a serious spill.&lt;br /&gt;&lt;br /&gt;The best way to prevent a serious acid spill is to check these units at least once per day for excess heat.  A quick check can be done by simply running your hand over the front of each unit to detect any raise in temperature.  The temperature raise is quite obvious from the "normal" room temp.  It is important to disconnect a overheating battery as soon as possible to prevent an acid spill. The bad battery led indicator on the front of these units is pretty much useless as they do not detect most of the battery problems so don't rely on it.&lt;br /&gt;&lt;br /&gt;If you detect heat, do the following:&lt;br /&gt;&lt;ol&gt;&lt;li&gt;Unplug the input and output cables from the back of the unit to  drop it off line from the main electronics therefore removing the load.&lt;/li&gt;&lt;li&gt;Do not open the front cover until the unit temperature returns to room temp.&lt;/li&gt;&lt;li&gt;Replace all 4 batteries - Replacement battery set - APC Part# RBC14 which costs around $500.&lt;br /&gt;&lt;/li&gt;&lt;/ol&gt;If one of your battery units has started leaking, do the same procedure, except make sure that you use eye and hand protection when removing the old batteries.&lt;br /&gt;&lt;br /&gt;If you open the front cover of a unit with suspected bad battery, you can identify which of the four batteries is bad by it's bulging sides and/or leakage from the caps on  the connector side.&lt;br /&gt;&lt;br /&gt;So if you detect a battery acid smell in your data center, check those old XR battery units!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-7970076143387414694?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/7970076143387414694/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=7970076143387414694' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7970076143387414694'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7970076143387414694'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/apc-mx5000-battery-acid.html' title='APC MX5000 Battery Acid'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-5459465381833487184</id><published>2007-06-11T14:50:00.000-07:00</published><updated>2007-06-11T16:04:05.819-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='install'/><category scheme='http://www.blogger.com/atom/ns#' term='vista'/><category scheme='http://www.blogger.com/atom/ns#' term='legacy'/><category scheme='http://www.blogger.com/atom/ns#' term='bsod'/><title type='text'>Vista Trials - Legacy Hardware</title><content type='html'>I set out to see what Vista would do if attempted to install on an old(er) generic "white box" machine. You might say Why? it's just going to fail. Yes, I expect it to fail but how would it fail and how well (or bad) would Vista handle it?&lt;br /&gt;&lt;br /&gt;Time to hit the computer lab.&lt;br /&gt;&lt;br /&gt;So I took a older machine (see specs below) to the computer lab, slapped a DVD drive in it and booted the Vista CD. To make a long story short, it actually installed but failed to start up. The most amusing thing was that there was the old Blue Screen Of Death during startup that flashed over the screen so fast that I could not read it, but it was certainly there. So much for Vista doing away with the old BSOD!&lt;br /&gt;End of short story...&lt;br /&gt;&lt;br /&gt;The BSOD caused it to crash and force a reboot, then upon booting from the CD again I was presented with the "Vista failed to start, what do you want to do" with the repair installation option. I tried the repair and of course, was presented with the same BSOD reboot "feature".&lt;br /&gt;Next I removed all PCI cards and replaced the AGP graphics card with another and tried again.  The net result was that I tried a number of format and re-install with an empty PCI bus and three different graphics cards and replacement RAM and had the same result every time. This leads me to believe that it simply did not like something on the mother board. My bet would the the chip set, but who knows?&lt;br /&gt;&lt;br /&gt;Machine specs:&lt;br /&gt;Motherboard:  ABIT-TH7&lt;br /&gt;Processor:  Intel P4 1.7ghz&lt;br /&gt;RAM:  2 x 512mb RAMBUS  (also tried a 2 x 256mb set)&lt;br /&gt;HDD: IBM 60gig IDE&lt;br /&gt;DVDROM:  Sony&lt;br /&gt;Graphic:  Nvidia AGP, ATI AGP, S7 chip PCI&lt;br /&gt;&lt;br /&gt;Moral of the story... don't waste your time with Vista on old retired hardware.&lt;br /&gt;&lt;br /&gt;If someone has had success with Visa on legacy hardware, I'd like to hear your story here.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-5459465381833487184?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/5459465381833487184/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=5459465381833487184' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/5459465381833487184'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/5459465381833487184'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/vista-trials-legacy-hardware.html' title='Vista Trials - Legacy Hardware'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-3193087130225984292</id><published>2007-06-07T15:15:00.000-07:00</published><updated>2007-06-07T16:20:24.883-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='directory'/><category scheme='http://www.blogger.com/atom/ns#' term='command line'/><category scheme='http://www.blogger.com/atom/ns#' term='command'/><category scheme='http://www.blogger.com/atom/ns#' term='cmd'/><title type='text'>Killer Command Line Tips Part 1</title><content type='html'>I am going to throw out a series of my favorite Windows Command Line shortcuts and tips.&lt;br /&gt;Part 1 - Navigating directories.&lt;br /&gt;&lt;br /&gt;One of the most clumsy aspects of using the Windows command line is traversing the file system directories. Here are a few tips to save some keystrokes and time.&lt;br /&gt;&lt;br /&gt;1) Use directory name masking. Did you know that you can use * as a mask in the CD command?&lt;br /&gt; Example: &lt;span style="font-weight: bold;"&gt;cd \brainstrain &lt;/span&gt;&lt;br /&gt; This can be shortened to &lt;span style="font-weight: bold;"&gt;cd \br*&lt;/span&gt;&lt;br /&gt; The typed out portion must be unique or it will change to the first directory name that matches the mask.&lt;br /&gt;&lt;br /&gt;2) When you CD to a long directory name with spaces in it where you would quote the name like "program files" you can leave out the last quote.&lt;br /&gt; Example: &lt;span style="font-weight: bold;"&gt;cd "\program files"&lt;/span&gt;&lt;br /&gt; can be shortened to &lt;span style="font-weight: bold;"&gt;cd "\program files&lt;/span&gt;&lt;br /&gt; and... using tip 1 and 2, you can do this&lt;br /&gt; &lt;span style="font-weight: bold;"&gt;cd "\prog*&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;3) You can drag and drop a folder from Explorer into a CMD window. Windows will paste in the full directory path including quotes. Once the path is in the CMD window, change focus to the CMD window, hit &lt;span style="font-weight: bold;"&gt;HOME&lt;/span&gt; to get to the beginning of the cmd line, then type &lt;span style="font-weight: bold;"&gt;cd /d &lt;/span&gt;(with insert on), then hit enter.&lt;br /&gt;Note: the &lt;span style="font-weight: bold;"&gt;/d&lt;/span&gt; option of the &lt;span style="font-weight: bold;"&gt;cd&lt;/span&gt; command is only required if you included the drive letter in the path AND the drive is different than the current drive.&lt;br /&gt;&lt;br /&gt;4) Use the "Open Command Window Here" power toy found here:&lt;br /&gt;&lt;a href="http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx"&gt;http://www.microsoft.com/windowsxp/downloads/powertoys/xppowertoys.mspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;This is the XP version that also works in Windows 2000 (afaik).  With this power toy, you simply right click on a folder name in Explorer, then click Open Command Window Here.  A new CMD window will be opened with the folder being the current directory.&lt;br /&gt;&lt;br /&gt;5) Use environment variables. The following changes to the temp directory:&lt;br /&gt;    &lt;span style="font-weight: bold;"&gt;cd %temp%&lt;br /&gt;    &lt;/span&gt;or, change to the user profile directory:&lt;br /&gt;    &lt;span style="font-weight: bold;"&gt;cd %userprofile%&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Note&lt;/span&gt; - Don't use the masking methods in batch files because as directories are added or changed, the mask may not change to the directory name you would expect. Always spell everything out in full in batch files.&lt;br /&gt;&lt;br /&gt;These methods work in Windows 2000 and later operating systems (however... not tested with Vista).&lt;br /&gt;&lt;br /&gt;Enjoy!&lt;br /&gt;&lt;br /&gt;Look for more Killer Command Line Tips in the near future.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-3193087130225984292?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/3193087130225984292/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=3193087130225984292' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/3193087130225984292'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/3193087130225984292'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/killer-command-line-tips-part-1.html' title='Killer Command Line Tips Part 1'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-8012352598698429009</id><published>2007-06-04T10:56:00.000-07:00</published><updated>2007-06-04T11:46:16.636-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='webhits'/><category scheme='http://www.blogger.com/atom/ns#' term='lockdown'/><category scheme='http://www.blogger.com/atom/ns#' term='webhits.dll'/><category scheme='http://www.blogger.com/atom/ns#' term='exploit'/><category scheme='http://www.blogger.com/atom/ns#' term='kb328832'/><category scheme='http://www.blogger.com/atom/ns#' term='iis'/><category scheme='http://www.blogger.com/atom/ns#' term='htw'/><title type='text'>IIS 5.0 authentication bypass exploit</title><content type='html'>A recently discovered (Dec 2006) IIS 5.0 exploit raises the bar for you to secure your web servers.&lt;br /&gt;&lt;br /&gt;Actually, the most interesting aspect to this issue is that Microsoft has not released a patch to correct the exploit, but instead is showing the world how the exploit works and using it as a scare tactic to get you to upgrade to IIS6 (Windows 2003 server).  Check this out:&lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/328832"&gt;http://support.microsoft.com/kb/328832&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;IMHO, this is yet another shameless cheap shot by Microsoft to push you into an upgrade.  They actually show you how to use the exploit but offer no solution except to strongly recommend upgrading.&lt;br /&gt;&lt;br /&gt;The cheap fix for those running IIS5 is to use URLSCAN and make sure you are blocking the .htw extension.&lt;br /&gt;.htw is the webhits extension which is not widely used so unless you have a specific need for it, block it by running the IIS LockDown Tool and make sure you enable URLScan during install.  I believe that .htw is blocked in most template installs but you should check the urlscan.ini after install to make sure.&lt;br /&gt;&lt;br /&gt;For more info on the exploit, see the SAN alert here:&lt;br /&gt;&lt;a href="http://isc.sans.org/diary.html?storyid=2915&amp;rss"&gt;http://isc.sans.org/diary.html?storyid=2915&amp;amp;rss&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-8012352598698429009?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/8012352598698429009/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=8012352598698429009' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8012352598698429009'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8012352598698429009'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/iis-50-authentication-bypass-exploit.html' title='IIS 5.0 authentication bypass exploit'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-8319517980750291092</id><published>2007-06-01T11:36:00.000-07:00</published><updated>2007-06-01T11:46:21.242-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='kb'/><category scheme='http://www.blogger.com/atom/ns#' term='kbalertz'/><category scheme='http://www.blogger.com/atom/ns#' term='knowledge base'/><category scheme='http://www.blogger.com/atom/ns#' term='microsoft'/><category scheme='http://www.blogger.com/atom/ns#' term='alert'/><title type='text'>Knowledge Base Alertz Notification</title><content type='html'>For those of you that need to keep up on Microsoft bug fixes (read security issues!) the task can be a real pain in your backside... to say the least.&lt;br /&gt;&lt;br /&gt;To help ease the pain there is a service by Scott Cate at &lt;a href="http://www.kbalertz.com/Default.aspx"&gt;www.kbalertz.com &lt;/a&gt;&lt;br /&gt;This free service will send you daily email alerts when a new KB article is posted for each KB area that you select.&lt;br /&gt;Check it out, and Thank You Scott for creating this service!&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-8319517980750291092?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/8319517980750291092/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=8319517980750291092' title='1 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8319517980750291092'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/8319517980750291092'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/knowledge-base-alertz-notification.html' title='Knowledge Base Alertz Notification'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>1</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-2047720152055395986</id><published>2007-06-01T11:16:00.000-07:00</published><updated>2007-06-01T11:31:47.441-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='squidoo'/><category scheme='http://www.blogger.com/atom/ns#' term='encoder'/><category scheme='http://www.blogger.com/atom/ns#' term='wme'/><category scheme='http://www.blogger.com/atom/ns#' term='youtube'/><title type='text'>YouTube Virgin</title><content type='html'>YouTube Virgin no more.&lt;br /&gt;&lt;br /&gt;Just published my first YouTube video and I must say that I am somewhat hooked.&lt;br /&gt;Found a great tutorial for making great looking YouTube videos here:&lt;br /&gt;&lt;a href="http://www.squidoo.com/youtuberight/"&gt;http://www.squidoo.com/youtuberight&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;The process was of course time consuming but these days, even the free tools do a good job, even for a media dummy like me as I have always been more of a data guy. One thing that I didn't realize is that Microsoft actually has a nice free encoder that did a nice job. Windows Media Encoder WME:&lt;br /&gt;&lt;a href="http://www.microsoft.com/windows/windowsmedia/forpros/encoder/default.mspx"&gt;http://www.microsoft.com/windows/windowsmedia/forpros/encoder/default.mspx&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;Check out my first video here:&lt;br /&gt;&lt;a href="http://www.youtube.com/watch?v=0cIVsi0iYi8"&gt;http://www.youtube.com/watch?v=0cIVsi0iYi8&lt;/a&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-2047720152055395986?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/2047720152055395986/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=2047720152055395986' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/2047720152055395986'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/2047720152055395986'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/06/youtube-virgin.html' title='YouTube Virgin'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-9195053188282784665</id><published>2007-05-31T12:21:00.000-07:00</published><updated>2007-06-01T11:33:10.776-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='arf'/><category scheme='http://www.blogger.com/atom/ns#' term='aol'/><category scheme='http://www.blogger.com/atom/ns#' term='fbl'/><category scheme='http://www.blogger.com/atom/ns#' term='rfc822'/><category scheme='http://www.blogger.com/atom/ns#' term='feed back loop'/><title type='text'>FBL Hell</title><content type='html'>If you are in the business of parsing and processing email Feed Back Loop (FBL) messages, you may want to read this about the AOL proposed standardized format.&lt;br /&gt;&lt;a href="http://postmaster-us.info.aol.com/fbl/arfinfo.html"&gt;http://postmaster-us.info.aol.com/fbl/arfinfo.html&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;I guess this is good news in the way that hopefully a standard will emerge, but I'm not sure that AOLs proposal is best. My main problem with it is that they intend to &lt;a href="http://en.wikipedia.org/wiki/Redaction"&gt;redact &lt;/a&gt;the email address. That just further complicates the process of flagging the account in your database (time to re-examine the X-Header drawing board). I mean, they are ONLY sending these FBL messages back to a whitelisted sender so what is the paranoia of an email address or screen name getting hijacked?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-9195053188282784665?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/9195053188282784665/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=9195053188282784665' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/9195053188282784665'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/9195053188282784665'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/05/fbl-hell.html' title='FBL Hell'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-5043698733471970042</id><published>2007-05-30T13:51:00.000-07:00</published><updated>2007-05-30T14:02:29.247-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='dell'/><category scheme='http://www.blogger.com/atom/ns#' term='retail'/><category scheme='http://www.blogger.com/atom/ns#' term='poweredge'/><category scheme='http://www.blogger.com/atom/ns#' term='wal-mart'/><title type='text'>Buy your new Dell at Wal-Mart ?</title><content type='html'>A recent announcement that Dell will be selling it's consumer based PC products  through Wal-Mart is an interesting move... and IMHO, very risky.  How can they maintain that they are high-end and at the same time, sell through the low-end retailer?&lt;br /&gt;&lt;br /&gt;Dean to Dell... are you sure about this?&lt;br /&gt;&lt;br /&gt;What's next? Will I be buying a Dell PowerEdge at Home Depot or Lowes? And would I go to the "Information Desk" for support?&lt;br /&gt;&lt;br /&gt;Some would argue that Dell is already low-end and they belong in Wal-Mart.&lt;br /&gt;&lt;br /&gt;What do you think?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-5043698733471970042?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/5043698733471970042/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=5043698733471970042' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/5043698733471970042'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/5043698733471970042'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/05/buy-your-new-dell-at-wal-mart.html' title='Buy your new Dell at Wal-Mart ?'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-2182675669880755367</id><published>2007-05-25T11:29:00.000-07:00</published><updated>2007-05-25T11:38:04.977-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='keepalive'/><category scheme='http://www.blogger.com/atom/ns#' term='session'/><category scheme='http://www.blogger.com/atom/ns#' term='ts'/><category scheme='http://www.blogger.com/atom/ns#' term='terminal service'/><title type='text'>Tip - Terminal Service session reconnect problem</title><content type='html'>TS Server Admins -&lt;br /&gt;&lt;br /&gt;If your users have problems in reconnecting to a Terminal Service session after a connection drop or intentional disconnect, try the following support article:&lt;br /&gt;&lt;a href="http://support.microsoft.com/kb/216783/en-us"&gt;http://support.microsoft.com/kb/216783/en-us&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;What this does is add a value to the registry that changes the KeepAlive behavior.  It stops the keep alive function after 1 minute so that the session will transition into a disconnect state. Once in the disconnect state, the session can be reconnected by the user. Without this value, the session may remain in an active state (depending on how the disconnect occured) and therefore the user cannot reconnect to it. Instead, the user may get a new session.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-2182675669880755367?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/2182675669880755367/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=2182675669880755367' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/2182675669880755367'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/2182675669880755367'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/05/tip-terminal-service-session-reconnect.html' title='Tip - Terminal Service session reconnect problem'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-4479283469703170878</id><published>2007-05-23T11:24:00.000-07:00</published><updated>2007-06-01T11:28:22.446-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='weak'/><category scheme='http://www.blogger.com/atom/ns#' term='xp'/><category scheme='http://www.blogger.com/atom/ns#' term='blank password'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>Blank Password more Secure than Weak Password</title><content type='html'>This is a new one on me, but according to Microsoft, on Windows XP (and I assume Vista) the use of a blank password on a user account is more secure than the use of a weak password... like "1234" or "aabb".  Why? because if a user account is created without a password, then that account cannot be accessed remotely.  I have not tested this but I have to assume that they set a local security policy that blocks remote access if the account does not have a password.&lt;br /&gt;&lt;br /&gt;Sounds like it's time for a lab test on this one.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-4479283469703170878?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/4479283469703170878/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=4479283469703170878' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/4479283469703170878'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/4479283469703170878'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/05/blank-password-more-secure-than-weak.html' title='Blank Password more Secure than Weak Password'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-7348658160788476626</id><published>2007-05-22T11:21:00.000-07:00</published><updated>2007-06-01T11:33:55.448-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='radmin'/><category scheme='http://www.blogger.com/atom/ns#' term='trendmicro'/><category scheme='http://www.blogger.com/atom/ns#' term='officescan'/><category scheme='http://www.blogger.com/atom/ns#' term='trend'/><title type='text'>TrendMicro OfficeScan Attack</title><content type='html'>Arrived at my office desktop this morning to find that TrendMicro OfficeScan has decided that my Radmin Viewer software is malware and it has quarantined it. Fortunately, it was the older version 2.2 viewer that I don't use anymore so no real harm done... to me. Now we will see how many help desk calls we get from those that were using the old version... thanks for a bad day TrendMicro!  Come on Trend... this is a commercially sold product that has not been widely abused. At lease give me a warning about this before sending it to the dungeon.  This is one reason (of many) that we decided to walk away from Symantec CE version 10.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-7348658160788476626?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/7348658160788476626/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=7348658160788476626' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7348658160788476626'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/7348658160788476626'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/05/trendmicro-officescan-attack.html' title='TrendMicro OfficeScan Attack'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-2896824953553349282</id><published>2007-05-21T14:22:00.000-07:00</published><updated>2007-05-21T14:58:48.968-07:00</updated><title type='text'>Take a Walk - In your Data Center</title><content type='html'>&lt;span style="font-family: arial;"&gt;Every Data Center manager should assign a on-site staff member to walk the data center daily to check for problems. This IT guy should be checking for things like:&lt;br /&gt;&lt;/span&gt;&lt;ul&gt;&lt;li&gt;Those pesky flashing amber lights on raid subsystem and in host machines&lt;/li&gt;&lt;li&gt;The environment - high temp, hot spots, humidity&lt;/li&gt;&lt;li&gt;Audible alarms&lt;/li&gt;&lt;li&gt;UPS systems - move your hand over battery units to sense heat that may indicate a failing or overheating battery&lt;/li&gt;&lt;li&gt;Listen for noisy fans or hard drives that may indicate a impending failure&lt;/li&gt;&lt;/ul&gt;This proactive approach to Data Center management can help to head off disaster.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-2896824953553349282?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/2896824953553349282/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=2896824953553349282' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/2896824953553349282'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/2896824953553349282'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/05/take-walk-in-your-data-center.html' title='Take a Walk - In your Data Center'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-6548056122404526883</id><published>2007-05-21T10:32:00.000-07:00</published><updated>2007-06-01T11:34:29.209-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='version'/><category scheme='http://www.blogger.com/atom/ns#' term='firmware'/><category scheme='http://www.blogger.com/atom/ns#' term='wrt54'/><category scheme='http://www.blogger.com/atom/ns#' term='linksys'/><category scheme='http://www.blogger.com/atom/ns#' term='upgrade'/><title type='text'>Linksys Router Firmware Upgrade - Determine Version</title><content type='html'>&lt;span style="font-family:arial;"&gt;For my first Tech Tip I thought I would help demystify the old Linksys router version problem. The trouble is that you must know the correct version number of your router in order to download and install the correct firmware upgrade. For the most part, there is no issue... just look the serial number / model number sticker usually found on the bottom of the box (sometimes the side) and the version will be listed after the model number. For example "Model No WRT54G v2.2"&lt;br /&gt;&lt;br /&gt;But what if the version is not listed? In that case is it simply v1.0 even though it is not listed (and most of the version 1.0 are not).&lt;br /&gt;&lt;br /&gt;What about just installing the later version firmware even though it is not for my v1.0 router... Don't do it. You will most likely turn it into a paper weight... and not a very good one at that. I know because I have done it.&lt;br /&gt;&lt;br /&gt;Hope this helps someone out there!&lt;br /&gt;&lt;br /&gt;&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-6548056122404526883?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/6548056122404526883/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=6548056122404526883' title='3 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/6548056122404526883'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/6548056122404526883'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/05/linksys-router-firmware-upgrade.html' title='Linksys Router Firmware Upgrade - Determine Version'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>3</thr:total></entry><entry><id>tag:blogger.com,1999:blog-7656056675700026432.post-869076942382876000</id><published>2007-05-21T09:54:00.000-07:00</published><updated>2007-06-04T12:54:54.015-07:00</updated><title type='text'>Pop of the Starter's Gun</title><content type='html'>The race has begun. Blogging is a new venture for me, one that I hope to be able to keep up with. I am one of a somewhat reticent nature, so this will challenge me.&lt;br /&gt;&lt;br /&gt;&lt;span style="font-weight: bold;"&gt;Preamble&lt;/span&gt;&lt;br /&gt;&lt;br /&gt;My goal here is to make a daily post of "tales from the IT world"... sometimes the dark side of IT, sometimes a helpful tip, sometimes a rant or rage about something (look out Micro$oft).  Since I spend about 50 hours of every week in the IT trenches, there must be something to post on a regular basis... right?&lt;br /&gt;&lt;br /&gt;&lt;span style="font-style: italic;"&gt;I'll keep you posted !&lt;/span&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/7656056675700026432-869076942382876000?l=dchafee.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://dchafee.blogspot.com/feeds/869076942382876000/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://www.blogger.com/comment.g?blogID=7656056675700026432&amp;postID=869076942382876000' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/869076942382876000'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/7656056675700026432/posts/default/869076942382876000'/><link rel='alternate' type='text/html' href='http://dchafee.blogspot.com/2007/05/pop-of-starters-gun.html' title='Pop of the Starter&apos;s Gun'/><author><name>FixingStuff</name><uri>http://www.blogger.com/profile/15618730837122385167</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='32' height='32' src='http://4.bp.blogspot.com/_Q84Q8NaAfXI/TIfN5ExivrI/AAAAAAAAADQ/EyOiZgo7zbc/S220/n1020735517_4508.jpg'/></author><thr:total>0</thr:total></entry></feed>
