Tag Archives: enabled

Rpcrt4.dll – Revision History for Windows Vista SP2, Windows Server 2008 SP2 and Windows Small Business Server 2008 (SBS 2008)

Rpcrt4.dll – Revision History for Windows Vista SP2, Windows Server 2008 SP2 and Windows Small Business Server 2008 (SBS 2008)

10-Jul-2013 – 6.0.6002.23155 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2849470 – MS13-062: Vulnerability in remote procedure call could allow elevation of privilege: August 13, 2013

10-Jul-2013 – 6.0.6002.18882 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2849470 – MS13-062: Vulnerability in remote procedure call could allow elevation of privilege: August 13, 2013

13-Mar-2011 – 6.0.6002.22611 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2521448 – RPC returns an out-of-memory error incorrectly when you use an RPC over HTTP client to connect to an RPC over HTTP server in Windows Server 2008 or in Windows Vista

04-May-2010 – 6.0.6002.22398 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/2023170 – An access violation exception occurs in the “NdrClientCall2” function in Windows Vista or in Windows Server 2008

18-Jul-2009 – 6.0.6002.22180 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/973780 – Some TCP connections between an NLB server that is running Windows Server 2008 and its clients are broken after the Port Scalability feature is enabled on the NLB server

23-Apr-2009 – 6.0.6002.22120 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/970238 – MS09-026: Vulnerability in RPC could allow elevation of privilege

23-Apr-2009 – 6.0.6002.18024 – Rpcrt4.dll – x86/x64 – http://support.microsoft.com/kb/970238 – MS09-026: Vulnerability in RPC could allow elevation of privilege

Microsoft Outlook 2007 and Microsoft Outlook 2010 do not archive messages as expected based on the received date instead it uses the modified date by default

Microsoft Outlook 2007 and Microsoft Outlook 2010 do not archive messages as expected based on the received date instead it uses the modified date by default

The archiving features with Microsoft Outlook 2007 and Microsoft Outlook 2010 use the last modified date of an item rather than the sent or recieved date to determine if it should be archived.  This can become a real problem if you have recently moved some old messages to a new outlook folder or you have had to export and import messages using a PST file during a Microsoft Exchange Migration or when a user changes desktop computer or laptop.

To work around this issue you need to fully patch Microsoft Office 2007 or Microsoft Office 2010 and then apply the latest hotfixes for Outlook ased upon the service pack level, for example if you have Microsoft Office 2010 Service Pack 1 installed then please check that you apply Outlook 2010 hotfixes desinged for Office 2010 – Service Pack 1.

Once you have patched Outlook 2007 and Outlook 2010 you will have enabled support for the ArchiveIgnoreLastModifiedTime DWORD Registry value, which in turn lets you switch from archive by last modified date to archive by received date.

To enable the switch in behaviour you simply need to add the following registry value dependant upon your version of Microsoft Outlook

Microsoft Outlook 2007

Navigate using regedit.exe to the following location: HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Preferences

Select to create a new DWORD Value and call it ArchiveIgnoreLastModifiedTime

The value data of ArchiveIgnoreLastModifiedTime should be set to 1 (This enables it)

Microsoft Outlook 2010

Navigate using regedit.exe to the following location: HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\Preferences

Select to create a new DWORD Value and call it ArchiveIgnoreLastModifiedTime

The value data of ArchiveIgnoreLastModifiedTime should be set to 1 (This enables it)

You have now turned on archiving by received date in Outlook 2007 or 2010 for the user that you are logged in as, please note that you will need to repeat this process whilst logged in as each user that requires archive by received date on this computer.

Ipmidrv.sys – Pre Service Pack 2 Revision History for Windows Server 2008 R2 SP1, Windows 7 SP1 and Windows Small Business Server 2011 SP1 (SBS 2011)

Ipmidrv.sys – Pre Service Pack 2 Revision History for Windows Server 2008 R2 SP1, Windows 7 SP1 and Windows Small Business Server 2011 SP1 (SBS 2011)

20-Feb-2014 – 6.1.7601.22607 – Ipmidrv.sys – x86/x64 – http://support.microsoft.com/kb/2931129 – “0x0000007E” Stop error on IPMIDrv!KCSRequestResponseEngine in Windows Server

20-Feb-2014 – 6.1.7601.18401 – Ipmidrv.sys – x86/x64 – http://support.microsoft.com/kb/2931129 – “0x0000007E” Stop error on IPMIDrv!KCSRequestResponseEngine in Windows Server

10-Feb-2012 – 6.1.7601.21920 – Ipmidrv.sys – x86/x64 – http://support.microsoft.com/kb/2674913 – IPMI subsystem cannot obtain power information when the BMC interrupt is enabled on a computer that is running Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2

27-Oct-2011 – 6.1.7601.21848 – Ipmidrv.sys – x86/x64 – http://support.microsoft.com/kb/2632472 – IPMI driver incorrectly returns time-out errors during KCS communication in Windows Server 2008 R2

24-Feb-2011 – 6.1.7601.21667 – Ipmidrv.sys – x86/x64 – http://support.microsoft.com/kb/2494816 – An IPMI-supported computer stops responding in the shutdown process in Windows Server 2008 R2