http://blogs.technet.com/fixit4me/archive/tags/Windows+Server/default.aspxTags: Windows Serveren-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/fixit4me/archive/2009/04/29/printer-redirection-for-rdp-2003-terminal-server-side.aspxThu, 30 Apr 2009 02:00:00 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3232850davecal_ms1http://blogs.technet.com/fixit4me/comments/3232850.aspxhttp://blogs.technet.com/fixit4me/commentrss.aspx?PostID=3232850http://blogs.technet.com/fixit4me/rsscomments.aspx?PostID=3232850<p><a href="http://support.microsoft.com/library/images/support/en-US/Fixit_16x16.png"><img title="clip_image002" border="0" alt="clip_image002" src="http://blogs.technet.com/blogfiles/fixit4me/WindowsLiveWriter/MicrosoftFixitSolutionforResettingWindow_CA3D/clip_image002_3.gif" width="16" height="16" /></a> <strong><em><a href="http://support.microsoft.com/kb/268065" target="_blank">Terminal Services event messages 1100 or 1114 in Windows 2000 Server or Windows Server 2003</a></em></strong></p> <p><strong><em>Problem description <br /></em></strong>An event ID 1100 message is logged in the Event Viewer on a Microsoft Windows 2000 Server-based computer, or an event ID 1114 message is logged in the Event Viewer on a Microsoft Windows Server 2003-based computer.</p> <p></p> <p><strong><em>Solution Information</em></strong></p> <p>This Fix it Solution automates disables <strong>fEnablePrintRDR</strong>.</p><img src="http://blogs.technet.com/aggbug.aspx?PostID=3232850" width="1" height="1">fixitWindows Serverhttp://blogs.technet.com/fixit4me/archive/2009/04/22/microsoft-fix-it-solution-to-enable-content-indexer-to-use-ipropertysetstorage-is-live.aspxThu, 23 Apr 2009 05:00:00 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:3229522davecal_ms2http://blogs.technet.com/fixit4me/comments/3229522.aspxhttp://blogs.technet.com/fixit4me/commentrss.aspx?PostID=3229522http://blogs.technet.com/fixit4me/rsscomments.aspx?PostID=3229522<p><a href="http://support.microsoft.com/library/images/support/en-US/Fixit_16x16.png"><img title="clip_image002" border="0" alt="clip_image002" src="http://blogs.technet.com/blogfiles/fixit4me/WindowsLiveWriter/MicrosoftFixitSolutionforRegisteringInte_D444/clip_image002_3.gif" width="16" height="16" /></a>&#160;<strong><em><a href="http://support.microsoft.com/kb/947265">In Windows Vista and Windows Server 2008, the Content Indexer service cannot index the custom properties of a document</a></em></strong></p> <p>We just released another Fix it Knowledge Base (KB) article. This Fix it addresses the following scenario:</p> <p>In Windows XP or in any pre-Windows XP operating system when you have a document that contains custom properties. the Content Indexer service can index these custom properties. In Windows Vista and Windows Server 2008, the Content Indexer service cannot index these custom properties as expected.</p><img src="http://blogs.technet.com/aggbug.aspx?PostID=3229522" width="1" height="1">fixitVistaWindows Server