<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Exchange hotfix for kernel memory exhaustion issues is now released</title><link>http://blogs.technet.com/exchange/archive/2006/02/27/420684.aspx</link><description>EXECUTIVE SUMMARY A few weeks ago, we released three CXP flashes on the subject of Windows 2003 kernel memory issues and Exchange 2003. This is a promised follow-up to those flashes. We are happy to announce that a new Exchange 2003 SP2 hotfix has been</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Is your Exchange 2003 server running low on kernel paged pool ram? Read this.</title><link>http://blogs.technet.com/exchange/archive/2006/02/27/420684.aspx#420691</link><pubDate>Mon, 27 Feb 2006 22:26:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:420691</guid><dc:creator>Aaron Tiensivu's Blog</dc:creator><description>There is a hotfix released that will reduce the amount of kernel paged pool RAM used, typically by 1/3rd. I'm guessing they changed the internal structure of the client access tokens so that they only use 2 pages (8k on ia32) instead of 3 pages (12k on</description></item><item><title>migrate from GroupWise 6.5 to Exchange Server 2003</title><link>http://blogs.technet.com/exchange/archive/2006/02/27/420684.aspx#420788</link><pubDate>Tue, 28 Feb 2006 16:05:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:420788</guid><dc:creator>mohiuddinminhas</dc:creator><description>We have to migrate from GroupWise 6.5 to Exchange Server 2003, and as per Microsoft, this migration is now supported with Exchange 2003 SP2. For example, &lt;a rel="nofollow" target="_new" href="http://support.microsoft.com/?kbid=329041"&gt;http://support.microsoft.com/?kbid=329041&lt;/a&gt; &lt;br&gt;&lt;br&gt;we r running an e-Directory and GroupWise 6.5 on Microsoft Windows Server 2000. There is a lot of information available online for older GroupWise versions like 5.x, but specifically not enough for GroupWise 6.5.&lt;br&gt;&lt;br&gt;Any Help will be greatly appreciated&lt;br&gt;Thx! in Advance&lt;br&gt;Mohi&lt;br&gt;mohi@amkhorafi.com</description></item><item><title>re: Exchange hotfix for kernel memory exhaustion issues is now released</title><link>http://blogs.technet.com/exchange/archive/2006/02/27/420684.aspx#420849</link><pubDate>Wed, 01 Mar 2006 03:43:06 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:420849</guid><dc:creator>Tim H</dc:creator><description>Will this hotfix be back-ported to Exchange 2000?</description></item><item><title>re: Exchange hotfix for kernel memory exhaustion issues is now released</title><link>http://blogs.technet.com/exchange/archive/2006/02/27/420684.aspx#420853</link><pubDate>Wed, 01 Mar 2006 05:15:05 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:420853</guid><dc:creator>Mike Lee</dc:creator><description>Tim asked: Will this hotfix be back-ported to Exchange 2000? &lt;br&gt;&lt;br&gt;No, I'm sorry to say that there are no plans for this. Exchange 2000 is past its extended support lifecycle. The only fixes from now on for Exchange 2000 will be if security issues are discovered.&lt;br&gt;&lt;br&gt;You do raise an interesting point: while this problem has existed for a minority of Exchange 2000 customers, most of them haven't had kernel memory issues. Why are people suddenly running into this after upgrading? &lt;br&gt;&lt;br&gt;The reason is that a flood of new features, hardware and clients have come along in the last couple of years. Multiple upgrades tend to happen all at once: new drivers, more memory, bigger disks, more users, additional client applications...all of it adds up to more memory pressure.&lt;br&gt;</description></item><item><title>Weekend reading</title><link>http://blogs.technet.com/exchange/archive/2006/02/27/420684.aspx#421291</link><pubDate>Mon, 06 Mar 2006 15:30:01 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:421291</guid><dc:creator>subject: exchange</dc:creator><description>Sorry for the delay...&amp;amp;amp;nbsp;&lt;br&gt;&lt;br&gt;Hands on with Hosted Exchange&lt;br&gt;Step-by-Step Guide: How to repair Exchange-related...</description></item><item><title>Exchange Newsletter April 2006</title><link>http://blogs.technet.com/exchange/archive/2006/02/27/420684.aspx#425950</link><pubDate>Fri, 21 Apr 2006 21:53:12 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:425950</guid><dc:creator>Messaging - Education</dc:creator><description>Snapping a Database in Exchange 2003 (Brick Level Backups)&lt;br&gt;VSS is a set of COM APIs that implements...</description></item><item><title>Optimizing # of client connections in Exchange 2003</title><link>http://blogs.technet.com/exchange/archive/2006/02/27/420684.aspx#457511</link><pubDate>Tue, 19 Sep 2006 17:33:46 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:457511</guid><dc:creator>Microsoft Higher Education Tech</dc:creator><description>One of the reasons to move to 64Bit in Exchange 12 is for more memory space. We are reaching a limit...</description></item></channel></rss>