<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: What are Outlook PST Files and Why Use Them&#8230; or Not?</title>
	<atom:link href="http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/</link>
	<description>Groovy Technical and How To Articles for New and Advanced Computer Users</description>
	<lastBuildDate>Wed, 10 Mar 2010 19:41:14 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Find Your Microsoft Outlook .PST FILE [How-To]</title>
		<link>http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-11197</link>
		<dc:creator>Find Your Microsoft Outlook .PST FILE [How-To]</dc:creator>
		<pubDate>Thu, 07 Jan 2010 08:05:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-11197</guid>
		<description>[...] or just browse to it to get to them.I hope this has been helpful in aiding you to find the Microsoft Outlook PST file location.&#160; Now that you’ve found the location be sure to backup often!&#160; You can [...]</description>
		<content:encoded><![CDATA[<p>[...] or just browse to it to get to them.I hope this has been helpful in aiding you to find the Microsoft Outlook PST file location.&#160; Now that you’ve found the location be sure to backup often!&#160; You can [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Repair Corrupt Microsoft Outlook PST Files [How-To] &#124; groovypost.com</title>
		<link>http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-10269</link>
		<dc:creator>Repair Corrupt Microsoft Outlook PST Files [How-To] &#124; groovypost.com</dc:creator>
		<pubDate>Fri, 23 Oct 2009 04:39:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-10269</guid>
		<description>[...] in our Free Tech Support Forum is How-To repair or recover email from a corrupt Microsoft Outlook PST file.&#160; I personally use PST files daily with Outlook for email archiving and other workflows I [...]</description>
		<content:encoded><![CDATA[<p>[...] in our Free Tech Support Forum is How-To repair or recover email from a corrupt Microsoft Outlook PST file.&#160; I personally use PST files daily with Outlook for email archiving and other workflows I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MrGroove</title>
		<link>http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-9981</link>
		<dc:creator>MrGroove</dc:creator>
		<pubDate>Fri, 09 Oct 2009 07:57:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-9981</guid>
		<description>@Moog, 
HI Moog and Welcome to the site!  I appreciate your comments and feedback however I can&#039;t say I agree with them.  That being said, I like a thorough discussion which leads me to:
&lt;br/&gt;
Yes I have worked in IT and I would argue that I actually have a very firm grasp around the details of general IT, information security, corporate governance, data classification and data retention.  All of these topics are actually my specialty from a professional level and if you would read my article again, you would see that although I list out the What, How, Why, Pro&#039;s and Con&#039;s, I never actually make any recommendations the reader should take in regards to using PST&#039;s other than Size.  I especially never hint upon data theft which I would argue is a far stretch from creating a PST on a corporate machine and storing corporate email there.  Sending email home or storing it on a personal device (if not allowed per corporate policy) yeah.. different story.
&lt;br/&gt;
In regards to your comment: 
&quot;RE: A competent organization has a process to classify sensitive / confidential email that doesn’t involve risking termination by hiding a resource you don’t own from the place you’re receiving it at.&quot;&lt;br/&gt;
I applaud any Organization who actually takes the time to build a process to classify sensitive / confidential email or any data for that matter.  I&#039;ve written several myself....  The problem however is the &quot;process&quot; is doomed to fail even before it begins.  Why?  Well first, you need to identify all types of corporate data and (not just email) and assign it to your data classification and data retention model.  Depending on the size of the &quot;competent organization&quot; that should only take.... a year or two.... or three...  After all, before you can classify the data you must first identify all the data, the data owners, train them, coordinate them, argue with them, let them argue with legal rebuild your classification and data retention model again after the consultants leave because a new law was just passed with new mandates around data retention then the game starts all over again.    
&lt;br/&gt;
So now that you have all the data identified, owners identified, data classified w/retention now the fun begins.  Now you get to decide if you can enforce the new policy with technology or if you need to get the employees involved or both.  In almost all cases it will be both which means now you need to train HR or some team to do a world wide tour and train the employees (or do CBT.. Hey, how about groovyPost!!!) or some sort of Corporate Policy training software/program/process (which no one will watch or they will but not really...).  Then you will need to interview all the employees to discover all the workflows because Sally in accounting has a Boss who told her she can work from home on Friday but he read on the internet it&#039;s not safe to email work home so she puts it on a USB drive, takes it home and puts it on her home computer where it stays.... and then there&#039;s that guy who uses Microsoft Skydrive you didn&#039;t know about and the other guy with a blog.....   But that&#039;s OK.  You can just tell the auditors your a &quot;Competent Corporation&quot; and you&#039;ve done your due diligence and writing a Policy and communicated the policy and all your employees have checked the box that says they are following the policy (but we all know they aren&#039;t including the auditor)....  ohh.. what a game. 
&lt;br/&gt;
Anyway, so once all the hard work is done, people are trained, Legal or the Records Management Dept. (whatever you name them) will realize that as great as the &quot;process&quot; is, it will be impossible to enforce it so they will just sign a big contract with Iron Mountain to Archive their Soft Copies and Hard Copies of everything, send emails to employees about not sending personal email, communicate the email destruction policies then just archive email and outlaw .pst files (if they get this far) and realize OMG... this is a really expensive waste of time wasn&#039;t it BUT, the Auditors and Legal are happy (I think?).

So yeah, I understand it and no, it&#039;s not as simple as saying just write a policy and follow the process like any good &quot;competent organization&quot; should/does do.  Respect?  I wish it were that easy.  I won&#039;t even get into the Gartner stats that 1 out of ever 3000 (or is it 5000) employees are working for the competition.....  

It&#039;s all about being informed, do your best to follow your corporate guidelines and never let your IT guys push you around.  They work for you, not the other way around.  If using a .PST can help you and it&#039;s not against your corporate policy, great!  That&#039;s what this article is here for.  To educate you.</description>
		<content:encoded><![CDATA[<p>@Moog,<br />
HI Moog and Welcome to the site!  I appreciate your comments and feedback however I can&#8217;t say I agree with them.  That being said, I like a thorough discussion which leads me to:<br />
<br />
Yes I have worked in IT and I would argue that I actually have a very firm grasp around the details of general IT, information security, corporate governance, data classification and data retention.  All of these topics are actually my specialty from a professional level and if you would read my article again, you would see that although I list out the What, How, Why, Pro&#8217;s and Con&#8217;s, I never actually make any recommendations the reader should take in regards to using PST&#8217;s other than Size.  I especially never hint upon data theft which I would argue is a far stretch from creating a PST on a corporate machine and storing corporate email there.  Sending email home or storing it on a personal device (if not allowed per corporate policy) yeah.. different story.<br />
<br />
In regards to your comment:<br />
&#8220;RE: A competent organization has a process to classify sensitive / confidential email that doesn’t involve risking termination by hiding a resource you don’t own from the place you’re receiving it at.&#8221;<br />
I applaud any Organization who actually takes the time to build a process to classify sensitive / confidential email or any data for that matter.  I&#8217;ve written several myself&#8230;.  The problem however is the &#8220;process&#8221; is doomed to fail even before it begins.  Why?  Well first, you need to identify all types of corporate data and (not just email) and assign it to your data classification and data retention model.  Depending on the size of the &#8220;competent organization&#8221; that should only take&#8230;. a year or two&#8230;. or three&#8230;  After all, before you can classify the data you must first identify all the data, the data owners, train them, coordinate them, argue with them, let them argue with legal rebuild your classification and data retention model again after the consultants leave because a new law was just passed with new mandates around data retention then the game starts all over again.<br />
<br />
So now that you have all the data identified, owners identified, data classified w/retention now the fun begins.  Now you get to decide if you can enforce the new policy with technology or if you need to get the employees involved or both.  In almost all cases it will be both which means now you need to train HR or some team to do a world wide tour and train the employees (or do CBT.. Hey, how about groovyPost!!!) or some sort of Corporate Policy training software/program/process (which no one will watch or they will but not really&#8230;).  Then you will need to interview all the employees to discover all the workflows because Sally in accounting has a Boss who told her she can work from home on Friday but he read on the internet it&#8217;s not safe to email work home so she puts it on a USB drive, takes it home and puts it on her home computer where it stays&#8230;. and then there&#8217;s that guy who uses Microsoft Skydrive you didn&#8217;t know about and the other guy with a blog&#8230;..   But that&#8217;s OK.  You can just tell the auditors your a &#8220;Competent Corporation&#8221; and you&#8217;ve done your due diligence and writing a Policy and communicated the policy and all your employees have checked the box that says they are following the policy (but we all know they aren&#8217;t including the auditor)&#8230;.  ohh.. what a game.<br />
<br />
Anyway, so once all the hard work is done, people are trained, Legal or the Records Management Dept. (whatever you name them) will realize that as great as the &#8220;process&#8221; is, it will be impossible to enforce it so they will just sign a big contract with Iron Mountain to Archive their Soft Copies and Hard Copies of everything, send emails to employees about not sending personal email, communicate the email destruction policies then just archive email and outlaw .pst files (if they get this far) and realize OMG&#8230; this is a really expensive waste of time wasn&#8217;t it BUT, the Auditors and Legal are happy (I think?).</p>
<p>So yeah, I understand it and no, it&#8217;s not as simple as saying just write a policy and follow the process like any good &#8220;competent organization&#8221; should/does do.  Respect?  I wish it were that easy.  I won&#8217;t even get into the Gartner stats that 1 out of ever 3000 (or is it 5000) employees are working for the competition&#8230;..  </p>
<p>It&#8217;s all about being informed, do your best to follow your corporate guidelines and never let your IT guys push you around.  They work for you, not the other way around.  If using a .PST can help you and it&#8217;s not against your corporate policy, great!  That&#8217;s what this article is here for.  To educate you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Moog</title>
		<link>http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-9979</link>
		<dc:creator>Moog</dc:creator>
		<pubDate>Fri, 09 Oct 2009 04:46:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-9979</guid>
		<description>Interesting...
&gt;&gt; Did you know it’s almost impossible to track / audit if your IT guy/department is reading your email?  Moving “Sensitive” or “Confidential” email off the Email / Exchange Server to a local .PST file adds a layer of security.

It appears you work in IT but don&#039;t seem to have a good understanding of why organizations have certain flows in place. Page has some great info, helpful .PST ref&#039;s but relaying an opinion advising people to take a resource they don&#039;t own (workplace email) and violate corporate policy for 99.737% of corp USA by making it unfindable does a disservice to people who find your site. A competent organization has a process to classify sensitive / confidential email that doesn&#039;t involve risking termination by hiding a resource you don&#039;t own from the place you&#039;re receiving it at. And no, it&#039;s not about the bourgie&#039;s vs. proles; it is about mutual respect betw. you and your workplace. If you&#039;re not going to give it, please don&#039;t expect it. pax.</description>
		<content:encoded><![CDATA[<p>Interesting&#8230;<br />
&gt;&gt; Did you know it’s almost impossible to track / audit if your IT guy/department is reading your email?  Moving “Sensitive” or “Confidential” email off the Email / Exchange Server to a local .PST file adds a layer of security.</p>
<p>It appears you work in IT but don&#8217;t seem to have a good understanding of why organizations have certain flows in place. Page has some great info, helpful .PST ref&#8217;s but relaying an opinion advising people to take a resource they don&#8217;t own (workplace email) and violate corporate policy for 99.737% of corp USA by making it unfindable does a disservice to people who find your site. A competent organization has a process to classify sensitive / confidential email that doesn&#8217;t involve risking termination by hiding a resource you don&#8217;t own from the place you&#8217;re receiving it at. And no, it&#8217;s not about the bourgie&#8217;s vs. proles; it is about mutual respect betw. you and your workplace. If you&#8217;re not going to give it, please don&#8217;t expect it. pax.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-2624</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Fri, 21 Nov 2008 15:02:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-2624</guid>
		<description>They&#039;re also prone to corruption, requiring a costly &lt;a href=&quot;http://www.pstfilerepair.com/pst_repair_tool.php&quot; rel=&quot;nofollow&quot;&gt;pst repair tool&lt;/a&gt; to fix them.</description>
		<content:encoded><![CDATA[<p>They&#8217;re also prone to corruption, requiring a costly <a href="http://www.pstfilerepair.com/pst_repair_tool.php" rel="nofollow">pst repair tool</a> to fix them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Create PST Files Using Outlook 2003 or 2007 :: groovyPost.com</title>
		<link>http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-1328</link>
		<dc:creator>Create PST Files Using Outlook 2003 or 2007 :: groovyPost.com</dc:creator>
		<pubDate>Mon, 21 Jul 2008 22:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.groovypost.com/howto/microsoft/outlook/what-are-outlook-pst-files-and-why-use-them-or-not/#comment-1328</guid>
		<description>[...] Before we dive into “How-To” create .PST files, you might want to quickly review an article I just wrote which explains the WHAT and WHY surrounding the use Microsoft Outlook .PST files also known as [...]</description>
		<content:encoded><![CDATA[<p>[...] Before we dive into “How-To” create .PST files, you might want to quickly review an article I just wrote which explains the WHAT and WHY surrounding the use Microsoft Outlook .PST files also known as [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
