<?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-9119070131542105632</id><updated>2011-11-27T16:03:58.911-08:00</updated><category term='OpenDNS Web filtering'/><title type='text'>Greg's IT Blog</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>8</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-9119070131542105632.post-6258654732148314172</id><published>2011-10-06T06:18:00.000-07:00</published><updated>2011-10-06T06:18:17.764-07:00</updated><title type='text'>Symantec AntiVirus Client Uninstall</title><content type='html'>When removing Symantec anti virus you often need to supply a password for the uninstall the application. This can be a hassle if you've forgotten the password. As usual, there is a work around. &lt;br /&gt;&lt;br /&gt;Here's how to remove SAV without supplying a password: &lt;br /&gt;&lt;br /&gt;- Click on Start&amp;gt;Run&lt;br /&gt;&lt;br /&gt;- Type regedit and press Enter (This will open the Registry editor) &lt;br /&gt;&lt;br /&gt;- Navigate to the following registry: &lt;br /&gt;HKEY_LOCAL_MACHINE\SOFTWARE\Intel\LANDesk\VirusProtect6\CurrentVersion\AdministratorOnly\Security &lt;br /&gt;&lt;br /&gt;- Look for a DWORD value called UseVPUninstallPassword. Once you find it, double click it. &lt;br /&gt;&lt;br /&gt;- Change the value of UseVPUninstallPassword to 0 (zero) and click OK [See pic below] &lt;br /&gt;&lt;br /&gt;&lt;div class="separator" style="clear: both; text-align: center;"&gt;&lt;a href="http://1.bp.blogspot.com/--_4getXEfrQ/To2ow1i-apI/AAAAAAAAAAQ/NbPBvJt_dvQ/s1600/regedit6.PNG" imageanchor="1" style="clear: left; float: left; margin-bottom: 1em; margin-right: 1em;"&gt;&lt;img border="0" height="240" src="http://1.bp.blogspot.com/--_4getXEfrQ/To2ow1i-apI/AAAAAAAAAAQ/NbPBvJt_dvQ/s320/regedit6.PNG" width="320" /&gt;&lt;/a&gt;&lt;/div&gt;&lt;br /&gt;- You can now close the Registry Editor window and uninstall Symantec anti virus without the a password request.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9119070131542105632-6258654732148314172?l=greg67.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/6258654732148314172/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://greg67.blogspot.com/2011/10/symantec-antivirus-client-uninstall.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/6258654732148314172'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/6258654732148314172'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/2011/10/symantec-antivirus-client-uninstall.html' title='Symantec AntiVirus Client Uninstall'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://1.bp.blogspot.com/--_4getXEfrQ/To2ow1i-apI/AAAAAAAAAAQ/NbPBvJt_dvQ/s72-c/regedit6.PNG' height='72' width='72'/><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9119070131542105632.post-6561513877471724798</id><published>2011-09-22T06:52:00.000-07:00</published><updated>2011-09-22T06:56:39.328-07:00</updated><title type='text'>Iphone iOS 4 calendar sync issues with Exchange</title><content type='html'>After updating to iOS 4, you might have encountered issues when syncing your Microsoft Exchange account. I know I did. Immediately after setting up Google Sync on my iPhone iOS 4, the sync took forever to complete. I ended up deleting and adding the account several times but it didn’t really fix the issue as it would still take forever to sync new contacts or new events in the calendar.&lt;br /&gt;&lt;br /&gt;According to this Apple Support &lt;a href="http://support.apple.com/kb/TS3398"&gt;ticket&lt;/a&gt;. Here are the symptoms: immediately after updating to iOS 4, some users may notice that Exchange ActiveSync Mail, Contacts, or Calendars do not sync, or sync very slowly. In addition, some Exchange Server administrators may notice their servers running slowly.&lt;br /&gt;&lt;br /&gt;Here is the fix offered by Apple:&lt;br /&gt;&lt;br /&gt;To work around this issue, users should install a configuration profile from Apple that increases the amount of time the iOS 4 device will wait for the Exchange Server to respond to its sync requests. For best results, the profile should be installed on as many iOS 4 devices at your company as possible.&lt;br /&gt;&lt;br /&gt;To install the profile:&lt;br /&gt;&lt;br /&gt;Use Safari on your iOS 4 device to download the &lt;a href="http://km.support.apple.com/library/APPLE/APPLECARE_ALLGEOS/TS3398/SignedDefaultEASTaskTimeout.mobileconfig"&gt;configuration profile&lt;/a&gt;. It may be easiest to read this article with your iPhone or iPod touch and tap the download link there, but you may also email the attachment to another email account on your iOS 4 device, and tap the attachment to open it.&lt;br /&gt;Tap Install to install the profile, and enter your passcode if prompted.&lt;br /&gt;A warning message will appear because the profile is not signed. Tap Install Now.&lt;br /&gt;Tap Done to complete the installation, then power off your device and power it back on.&lt;br /&gt;Wait for your Exchange data to finish syncing.&lt;br /&gt;After installation, the profile will be listed under Settings &gt; General &gt; Profile.&lt;br /&gt;&lt;br /&gt;The above configuration profile sets the iOS 4 sync timeout value to 240 seconds. This is now the default in iOS 4.0.1.&lt;br /&gt;&lt;br /&gt;Some institutions may wish to increase the sync timeout value beyond 240 seconds. To do so, download the unsigned configuration profile and open it in a text editor. Search for the value "240.0" (without the quotes) and change this to the desired number of seconds. Deploy the profile using the instructions above, noting that the configuration profile has not been signed by Apple.&lt;br /&gt;&lt;br /&gt;Have you had this issue? If so, did this fix work for you?&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9119070131542105632-6561513877471724798?l=greg67.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/6561513877471724798/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://greg67.blogspot.com/2011/09/iphone-ios-4-calendar-sync-issues-with.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/6561513877471724798'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/6561513877471724798'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/2011/09/iphone-ios-4-calendar-sync-issues-with.html' title='Iphone iOS 4 calendar sync issues with Exchange'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9119070131542105632.post-5503524855440638043</id><published>2011-09-18T18:49:00.000-07:00</published><updated>2011-09-22T06:59:31.845-07:00</updated><title type='text'>Moving your WSUS database</title><content type='html'>At times the WSUS database can grow large on your server. It is possible to move the database to a larger drive. To accomplish this just perform the following task.&lt;br /&gt;&lt;br /&gt;net stop "update services"&lt;br /&gt;net stop w3svc&lt;br /&gt;cd "C:\Program Files\Microsoft SQL Server\MSSQL$WSUS\Binn"&lt;br /&gt;osql -E -S %computername%\wsus -Q "exec sp_detach_db 'SUSDB'"&lt;br /&gt;md d:\WSUSDB&lt;br /&gt;move "C:\Program Files\Microsoft SQL Server\MSSQL$WSUS\Data\SUS*.*" d:\wsusdb&lt;br /&gt;osql -E -S %computername%\wsus -Q "exec sp_attach_db @dbname=N'SUSDB', @filename1=N'D:\WSUSDB\SUSDB.mdf', @filename2=N'D:\WSUSDB\SUSDB_log.ldf'"&lt;br /&gt;net start "update services"&lt;br /&gt;net start w3svc&lt;br /&gt;&lt;br /&gt;Thanks&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9119070131542105632-5503524855440638043?l=greg67.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/5503524855440638043/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://greg67.blogspot.com/2010/05/moving-your-wsus-database.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/5503524855440638043'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/5503524855440638043'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/2010/05/moving-your-wsus-database.html' title='Moving your WSUS database'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9119070131542105632.post-4026663312443443927</id><published>2010-05-03T19:33:00.000-07:00</published><updated>2010-05-03T19:34:39.103-07:00</updated><title type='text'>Volume Shadow Copy Service Failes with error 0xffffffff</title><content type='html'>Note This article is not for use with Windows Vista, with Windows Server 2008, or with later operating systems. Starting with Windows Vista and with Windows Server 2008, Windows component installation is manifest based. If you try to manually register specific components, such as those that are described in this "Resolution" section, in the operating systems that are mentioned in this note, unexpected results may occur that may require reinstalling Windows to resolve. &lt;br /&gt;&lt;br /&gt;To resolve this issue, follow these steps: &lt;br /&gt;Click Start, click Run, type cmd, and then click OK. &lt;br /&gt;Type the following commands at a command prompt. Press ENTER after you type each command.&lt;br /&gt;cd /d %windir%\system32&lt;br /&gt;Net stop vss &lt;br /&gt;Net stop swprv &lt;br /&gt;regsvr32 ole32.dll&lt;br /&gt;regsvr32 oleaut32.dll&lt;br /&gt;regsvr32 vss_ps.dll &lt;br /&gt;vssvc /register &lt;br /&gt;regsvr32 /i swprv.dll &lt;br /&gt;regsvr32 /i eventcls.dll &lt;br /&gt;regsvr32 es.dll&lt;br /&gt;regsvr32 stdprov.dll&lt;br /&gt;regsvr32 vssui.dll&lt;br /&gt;regsvr32 msxml.dll&lt;br /&gt;regsvr32 msxml3.dll&lt;br /&gt;regsvr32 msxml4.dll&lt;br /&gt;Note The last command may not run successfully.&lt;br /&gt;Perform a backup operation to verify that the issue is resolved.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9119070131542105632-4026663312443443927?l=greg67.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/4026663312443443927/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://greg67.blogspot.com/2010/05/volume-shadow-copy-service-failes-with.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/4026663312443443927'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/4026663312443443927'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/2010/05/volume-shadow-copy-service-failes-with.html' title='Volume Shadow Copy Service Failes with error 0xffffffff'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9119070131542105632.post-4777003402558263111</id><published>2010-01-14T09:54:00.001-08:00</published><updated>2010-01-25T08:15:28.237-08:00</updated><title type='text'>Outlook does not show embedded images</title><content type='html'>There are times when users can not view images embedded in the body of their emails. This is usually caused by items in the Cached outlook file. Here are the steps to resolving this issue.&lt;br /&gt;&lt;br /&gt;Go into registry (Start -&gt; Run -&gt; regedit)&lt;br /&gt;1. Locate the Outlook Temporary Items folder by opening the Registry and locating&lt;br /&gt;HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security\OutlookSecureTempFolder&lt;br /&gt;2. Navigate to the value of this Key. It should be something like: %USERPROFILE%\LocalSettings\Temporary Internet Files\OLK...\ (the OLK.. is a randomly generated file that is created. &lt;br /&gt;4. Copy and paste the string to your explorer address bar..&lt;br /&gt;3. Quit Outlook&lt;br /&gt;4. Delete the contents of the folder&lt;br /&gt;5. Launch Outlook&lt;br /&gt;&lt;br /&gt;Unfortunately, this issue keeps reoccurring on some pc's so you need to move the temp folder to a seperate location, and that should fix the issue permanently.  &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;Go into registry (Start -&gt; Run -&gt; regedit)&lt;br /&gt;1. Locate the Outlook Temporary Items folder by opening the Registry and locating&lt;br /&gt;HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Outlook\Security\OutlookSecureTempFolder&lt;br /&gt;2. Change the 'OutlookSecureTempFolder' key DATA value to a location that you would like to use.&lt;br /&gt;&lt;br /&gt;If your are using outlook 2007 then the registry key would be the following:&lt;br /&gt;&lt;br /&gt;HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Security\OutlookSecureTempFolder&lt;strong&gt;&lt;/strong&gt;&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9119070131542105632-4777003402558263111?l=greg67.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/4777003402558263111/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://greg67.blogspot.com/2010/01/outlook-does-not-show-embedded-images.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/4777003402558263111'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/4777003402558263111'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/2010/01/outlook-does-not-show-embedded-images.html' title='Outlook does not show embedded images'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9119070131542105632.post-6960624783662660794</id><published>2010-01-05T06:50:00.001-08:00</published><updated>2010-01-05T07:16:07.109-08:00</updated><title type='text'>Renewing 1024Bit SSL Certificates to 2046 or 4096 bit length.</title><content type='html'>I currently ran into a issue when attempting to renew an SSL Certificate that was issued using a CSR with a length 1024 Basically, new CSR's need to be either 2048 or 4096 in length. What does this mean???&lt;br /&gt;&lt;br /&gt;It means that you can not renew the certificate using conventional methods although this should be simple...&lt;br /&gt;&lt;br /&gt;At this point there are 2 options.&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;1. Recreate your certificate from scratch.. Yes, this means you will need to remove the current certificate and create a new CSR with either a 2048 or 4069 bit length. Once this has been done you can add that CSR to the request and receive the new certificate. Remember that this option would cause downtime if you have any secure pages or any shopping carts as those secure pages will not work while you are regenerating the certificate.&lt;br /&gt;&lt;br /&gt;2. Option 2 is to create a new temporary website and create a new SSL Certificate using the same information as the one created for the existing site. Remembering to change the Key length to either 2048 or 4096. Once you have created the new CSR, ensuring that it was done correctly, then you should be able to process the renewal and add the certificate to the live site.&lt;br /&gt;&lt;br /&gt;Remember, if you opt to use option 2 then it is extremely important that you enter the correct information when generating the CSR or you will get errors when processing the certificate.&lt;br /&gt;&lt;br /&gt;These is just an overview of how to correct this issue, a guide on creating or renewing an SSL Certificate on IIS will be coming soon...&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9119070131542105632-6960624783662660794?l=greg67.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/6960624783662660794/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://greg67.blogspot.com/2010/01/renewing-1024bit-ssl-certificates-to.html#comment-form' title='2 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/6960624783662660794'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/6960624783662660794'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/2010/01/renewing-1024bit-ssl-certificates-to.html' title='Renewing 1024Bit SSL Certificates to 2046 or 4096 bit length.'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>2</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9119070131542105632.post-173120193905009782</id><published>2009-11-11T10:50:00.000-08:00</published><updated>2011-09-22T07:03:58.164-07:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='OpenDNS Web filtering'/><title type='text'>OpenDNS</title><content type='html'>Looking for a good DNS or Web filter to secure your network. Looking to stop users from access inappropriate sites???&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.opendns.com/"&gt;www.opendns.com&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;&lt;br /&gt;I've used and configured most products such as websence and other filtering applications on the network side. Although all have their good points and are more than adequate. They all cost a lot of money.&lt;br /&gt;&lt;br /&gt;Opendns.com is a DNS/Web filter that allows you to be as open or as strict as you want. You can use it's general rules, which are already robust or you can add rules to become even more granular. Reporting capabilities are already built in and provide general reports on usage which are more than adequate for management reviews.&lt;br /&gt;&lt;br /&gt;The best thing of this is that it is either free (for home users) or a fraction of the price compared to those other in-house applications and there is little or no maintenance. Just add them as you DNS servers and viola!!! your in business.&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9119070131542105632-173120193905009782?l=greg67.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/173120193905009782/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://greg67.blogspot.com/2009/11/opendns.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/173120193905009782'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/173120193905009782'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/2009/11/opendns.html' title='OpenDNS'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry><entry><id>tag:blogger.com,1999:blog-9119070131542105632.post-1724172439754198969</id><published>2009-07-07T11:07:00.000-07:00</published><updated>2009-07-07T11:11:08.752-07:00</updated><title type='text'>Hello</title><content type='html'>Good afternoon everyone...&lt;br /&gt;&lt;br /&gt;Well this is my first blog..&lt;br /&gt;&lt;br /&gt;Just got back from a great family trip at Miami beach.. 5 days at the beach with my family was so much fun.. Samantha has learned to swim under water and Jonathan is trying to immitate her. You should see it a 4 year old boy with arm floats trying to swim under water.. funny...&lt;br /&gt;&lt;br /&gt;Hope you come back..&lt;br /&gt;&lt;br /&gt;Play on the field an not on the Bench....&lt;div class="blogger-post-footer"&gt;&lt;img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/9119070131542105632-1724172439754198969?l=greg67.blogspot.com' alt='' /&gt;&lt;/div&gt;</content><link rel='replies' type='application/atom+xml' href='http://greg67.blogspot.com/feeds/1724172439754198969/comments/default' title='Post Comments'/><link rel='replies' type='text/html' href='http://greg67.blogspot.com/2009/07/hello.html#comment-form' title='0 Comments'/><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/1724172439754198969'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/9119070131542105632/posts/default/1724172439754198969'/><link rel='alternate' type='text/html' href='http://greg67.blogspot.com/2009/07/hello.html' title='Hello'/><author><name>Greg</name><uri>http://www.blogger.com/profile/05532374271544340188</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='16' height='16' src='http://img2.blogblog.com/img/b16-rounded.gif'/></author><thr:total>0</thr:total></entry></feed>
