<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>michaelcolson.com &#187; office</title>
	<atom:link href="http://www.michaelcolson.com/category/microsoft/office/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.michaelcolson.com</link>
	<description></description>
	<lastBuildDate>Sat, 06 Mar 2010 14:54:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Office Suite Scalability on Terminal Services</title>
		<link>http://www.michaelcolson.com/2009/10/02/office-suite-scalability-on-terminal-services/</link>
		<comments>http://www.michaelcolson.com/2009/10/02/office-suite-scalability-on-terminal-services/#comments</comments>
		<pubDate>Fri, 02 Oct 2009 14:22:06 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[microsoft]]></category>
		<category><![CDATA[office]]></category>
		<category><![CDATA[terminal services]]></category>

		<guid isPermaLink="false">http://www.michaelcolson.com/?p=328</guid>
		<description><![CDATA[A colleague of mine recently pointed me to this great article on the scalability of office productivity suites on terminal services. The tests reviewed OpenOffice 2.1, Microsoft Office 2003, and Microsoft Office 2007.

The testers also put the 32-bit and 64-bit versions of Windows to the test to see if there was any difference.  You can [...]]]></description>
			<content:encoded><![CDATA[<p>A colleague of mine recently pointed me to this great article on the scalability of office productivity suites on terminal services. The tests reviewed OpenOffice 2.1, Microsoft Office 2003, and Microsoft Office 2007.</p>
<p><span id="more-328"></span></p>
<p>The testers also put the 32-bit and 64-bit versions of Windows to the test to see if there was any difference.  You can view the study in its <a href="http://wtstek.com/articles/20070510-01-scalability-of-office-suites-on-terminal-servers.htm">entirety</a> or you can just skip ahead to the <a href="http://wtstek.com/articles/20070510-05-scalability-of-office-suites-on-terminal-servers.htm">results</a>.</p>
<p>The bottom line of the tests show that you will get the highest number of active sessions with Microsoft Office 2003.  Suprisingly Microsoft Office 2007 isn&#8217;t all that far behind.  I ususally hear rumblings of how Microsoft Office 2007 is a memory hog but this test seems to debunk that myth.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2009/10/02/office-suite-scalability-on-terminal-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Outlook 2007 Deployment</title>
		<link>http://www.michaelcolson.com/2008/07/25/outlook-2007-deployment/</link>
		<comments>http://www.michaelcolson.com/2008/07/25/outlook-2007-deployment/#comments</comments>
		<pubDate>Fri, 25 Jul 2008 14:37:43 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[microsoft]]></category>
		<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://www.michaelcolson.com/?p=84</guid>
		<description><![CDATA[For some unknown reason, Microsoft removed the ability to apply transform files to the Office 2007 suite when installing via MSI.  On the flip side they made it much easier to deploy patches in MSP format to Office 2007 when installing via the traditional setup.exe.  Give and take I suppose.  Why is [...]]]></description>
			<content:encoded><![CDATA[<p>For some unknown reason, Microsoft removed the ability to apply transform files to the Office 2007 suite when installing via <abbr title="Windows Installer">MSI</abbr>.  On the flip side they made it much easier to deploy patches in <abbr title="Windows Installer Patch">MSP</abbr> format to Office 2007 when installing via the traditional setup.exe.  Give and take I suppose.  Why is this a problem?  Well if you want to deploy any or all of the Office 2007 suite via Active Directory Group Policy you will need to get a little creative.</p>
<p><span id="more-84"></span></p>
<p>To be fair, Microsoft still allows you to customize <em>SOME</em> settings when deploying using an <abbr title="Windows Installer">MSI</abbr>.  There is a config.xml file that is contained in the same directory as the <abbr title="Windows Installer">MSI</abbr> that allows you to specify things like product key, organization name, and a few other basic items.  If you don&#8217;t have a need to specify any configuration options and just want a plain vanilla install then you can still deploy Office 2007 using the tried and true <abbr title="Windows Installer">MSI</abbr> installation via Group Policy.</p>
<p>Keep in mind that if you do chose to use the <abbr title="Windows Installer">MSI</abbr> installation method, any patches you place in the Updates folder will be ignored!  This is important for things like service packs or critical security updates.</p>
<p>To overcome this Microsoft recommends creating a script that will perform the install, then using Group Policy, apply this script as a computer startup script.  I have taken that approach and modified it slightly to achieve a more controllable method whereby an end user can run the install or administrators can place this script into an already existing logon script.  The advantage here is that the user will NOT have to wait for the installation to complete prior to logon.</p>
<p>So here goes:<br />
<code>@ECHO OFF</code></p>
<p><code>ECHO Detecting Outlook 2007...</code><br />
<code>IF EXIST "C:\Program Files\Microsoft Office\Office12\OUTLOOK.EXE" GOTO End ELSE GOTO InstallOutlook</code></p>
<p><code>:InstallOutlook</code><br />
<code>ECHO Outlook 2007 not found.</code><br />
<code>ECHO Please wait while the Outlook 2007 installation initializes...</code><br />
<code>START \\SERVER\Share\OL2007\setup.exe /adminfile \\SERVER\Share\OL2007\Updates\OL2007.MSP</code><br />
<code>ECHO Initialization complete.</code><br />
<code>GOTO End</code></p>
<p><code>:End</code><br />
<code>EXIT</code></p>
<p>Before you go trying to run this puppy, you will need to have already created a share, copied the installation to the share, and finally created a transform file that contains your desired configuration options.  I won&#8217;t go into a bunch of detail on how to do all of this other than to say the command to enter the Office Configuration Wizard is <code>setup.exe /admin</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2008/07/25/outlook-2007-deployment/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Change Outlook Cached Mode Through Registry</title>
		<link>http://www.michaelcolson.com/2008/07/10/change-outlook-cached-mode-through-registry/</link>
		<comments>http://www.michaelcolson.com/2008/07/10/change-outlook-cached-mode-through-registry/#comments</comments>
		<pubDate>Thu, 10 Jul 2008 19:54:46 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[microsoft]]></category>
		<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://www.michaelcolson.com/?p=72</guid>
		<description><![CDATA[This little script and associated registry file can help avoid lots of support calls about how to enable or disable cached mode in Outlook.  To make this work you will need to do some manual testing which will give you the ideal values for your environment. 

This registry file assumes that you are trying to modify a [...]]]></description>
			<content:encoded><![CDATA[<p>This little script and associated registry file can help avoid lots of support calls about how to enable or disable cached mode in Outlook.  To make this work you will need to do some manual testing which will give you the ideal values for your environment. </p>
<p><span id="more-72"></span></p>
<p>This registry file assumes that you are trying to modify a profile named <strong>Test</strong>:</p>
<p><strong>Create the registry file:</strong><code><br />
Windows Registry Editor Version 5.00<br />
[HKCU\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles\Test\13dbb0c8aa05101a9bb000aa002fc45a]<br />
"00036601"=hex:84,19,00,00'</code></p>
<p>The value above will need to be adjusted for your environment and desired setting.  Here are a few of the standard values:</p>
<table border="0" cellspacing="0" cellpadding="0">
<tbody>
<tr>
<td>Cached Mode Disabled</td>
<td>04 00 00 00</td>
</tr>
<tr>
<td>Cached Mode Enabled</td>
<td>84 01 00 00</td>
</tr>
<tr>
<td>Cached Mode w/Public Folder</td>
<td>84 05 00 00</td>
</tr>
</tbody>
</table>
<p>Once you have the value narrowed down, save the above entry to a .REG file and you can easily apply this registry entry through a logon script by adding:</p>
<p><code>REGEDIT /S OutlookCachedMode.REG</code></p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2008/07/10/change-outlook-cached-mode-through-registry/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Network Stored PST Files</title>
		<link>http://www.michaelcolson.com/2007/06/01/network-stored-pst-files/</link>
		<comments>http://www.michaelcolson.com/2007/06/01/network-stored-pst-files/#comments</comments>
		<pubDate>Fri, 01 Jun 2007 18:29:35 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[exchange]]></category>
		<category><![CDATA[microsoft]]></category>
		<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://www.michaelcolson.com/?p=57</guid>
		<description><![CDATA[Officially Microsoft does not support the storage of PST files on file shares whether they are on a LAN or WAN.  They have a knowledge base article specifically regarding this http://support.microsoft.com/kb/297019 but there is also a good commentary on the subject on the Microsoft Enterprise Platforms Windows Server Performance Team blog Network Stored PST files &#8230; [...]]]></description>
			<content:encoded><![CDATA[<p>Officially Microsoft does not support the storage of PST files on file shares whether they are on a LAN or WAN.  They have a knowledge base article specifically regarding this <a href="http://support.microsoft.com/kb/297019">http://support.microsoft.com/kb/297019</a> but there is also a good commentary on the subject on the Microsoft Enterprise Platforms Windows Server Performance Team blog <a href="http://blogs.technet.com/askperf/archive/2007/01/21/network-stored-pst-files-don-t-do-it.aspx">Network Stored PST files &#8230; don&#8217;t do it!</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2007/06/01/network-stored-pst-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Missing Outlook Contacts</title>
		<link>http://www.michaelcolson.com/2007/05/01/missing-outlook-contacts/</link>
		<comments>http://www.michaelcolson.com/2007/05/01/missing-outlook-contacts/#comments</comments>
		<pubDate>Tue, 01 May 2007 21:29:41 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[microsoft]]></category>
		<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://www.michaelcolson.com/?p=79</guid>
		<description><![CDATA[If the user cannot access their local contacts when attempting to send an email message the problem may be that their Outlook Address Book account has been removed.

To resolve this issue:
Within Outlook go to Tools &#62; E-Mail Accounts
Under Directory select View or change existing directories or address books, click Next
If you do not see any [...]]]></description>
			<content:encoded><![CDATA[<p>If the user cannot access their local contacts when attempting to send an email message the problem may be that their Outlook Address Book account has been removed.</p>
<p><span id="more-79"></span></p>
<p><strong>To resolve this issue:</strong><br />
Within Outlook go to <strong>Tools</strong> &gt; <strong>E-Mail Accounts</strong><br />
Under Directory select <strong>View or change existing directories or address books</strong>, click <strong>Next</strong><br />
If you do not see any address books listed on the Directories and Address Books screen you will need to add one</p>
<p><strong>To add the local contacts as an Outlook address book:</strong><br />
Within Outlook go to <strong>Tools</strong> &gt; <strong>E-Mail Accounts</strong><br />
Under Directory select <strong>Add a new directory or address book</strong>, click <strong>Next</strong><br />
Select <strong>Additional Address Books</strong><br />
<strong>Outlook Address Book</strong><br />
You will have to restart Outlook before the change you will be able to see the address list.  (It may take a few minutes for it to full appear)</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2007/05/01/missing-outlook-contacts/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Send a Smile Program for Office 2007 Beta</title>
		<link>http://www.michaelcolson.com/2006/08/15/send-a-smile-office-2007-beta/</link>
		<comments>http://www.michaelcolson.com/2006/08/15/send-a-smile-office-2007-beta/#comments</comments>
		<pubDate>Tue, 15 Aug 2006 17:57:16 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[microsoft]]></category>
		<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://mcolson.wordpress.com/?p=32</guid>
		<description><![CDATA[Send a Smile (SaS) is a feedback tool that enables 2007 Microsoft Office system Beta participants to easily send Microsoft positive and negative comments about the Beta on an ad hoc basis.

http://www.microsoft.com/downloads/details.aspx?familyid=A2E1F4E2-BC0F-4403-B09F-7A677D55F274&#38;displaylang=en
]]></description>
			<content:encoded><![CDATA[<p>Send a Smile (SaS) is a feedback tool that enables 2007 Microsoft Office system Beta participants to easily send Microsoft positive and negative comments about the Beta on an ad hoc basis.</p>
<p><span id="more-10"></span></p>
<p><a href="http://www.microsoft.com/downloads/details.aspx?familyid=A2E1F4E2-BC0F-4403-B09F-7A677D55F274&amp;displaylang=en">http://www.microsoft.com/downloads/details.aspx?familyid=A2E1F4E2-BC0F-4403-B09F-7A677D55F274&amp;displaylang=en</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2006/08/15/send-a-smile-office-2007-beta/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Outlook Prints Outside Margins</title>
		<link>http://www.michaelcolson.com/2006/06/01/outlook-prints-outside-margins/</link>
		<comments>http://www.michaelcolson.com/2006/06/01/outlook-prints-outside-margins/#comments</comments>
		<pubDate>Thu, 01 Jun 2006 13:36:11 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[microsoft]]></category>
		<category><![CDATA[office]]></category>

		<guid isPermaLink="false">http://mcolson.wordpress.com/?p=26</guid>
		<description><![CDATA[Outlook 2003 uses Internet Explorer to display HTML messages. This can cause problems when attempting to print these messages from within Outlook.

If there are problems where Outlook is trying to print outside the printable margins and you the print setup within Outlooks are properly configured then consider adjusting the print setup for Internet Explorer.
]]></description>
			<content:encoded><![CDATA[<p>Outlook 2003 uses Internet Explorer to display <abbr title="HyperText Markup Language">HTML</abbr> messages. This can cause problems when attempting to print these messages from within Outlook.</p>
<p><span id="more-6"></span></p>
<p>If there are problems where Outlook is trying to print outside the printable margins and you the print setup within Outlooks are properly configured then consider adjusting the print setup for Internet Explorer.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.michaelcolson.com/2006/06/01/outlook-prints-outside-margins/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
