RDP issue rdpcorekmts.dll Application error Event id 1000, Windows Server 2008 R2

One of the Win2k8R2 running client access Exchange as upgraded to SP1. Did the same for other servers. Only one came up with issue. Checked the version of rdpcorekmts.dll version on the server with issue
with issue: version 6.1.7600.16952
without issue with sp1 version: 6.1.7601.17514

Followed the solution from here:

http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/f5855b60-f29c-4c90-b364-e364589e5267

Just a quick note the file is update by Windows Update KB2667402 not KB2621440. Please see http://support.microsoft.com/kb/2667402 for more details.
1) Connect remotely to affected server using the Computer Management Console
2) Stop the Remote Desktop Services
3) Take Ownership of file C:\Windows\System32\rdpcorekmts.dll and assign full NTFS permissions to your account
4) Rename file to rdpcorekmts.old
5) Copy file rdpcorekmts.dll from a non-patched server. I used another one of our domain controllers just to be safe.
6) Start the Remote Desktop Services
7) Test RDP login to server

WORKED FINE.

Trying to restore folders and files from Tape backup using Netbackup

Trying to restore folders and files from Tape backup using Netbackup causes the file server to hang or crash when the restore folders contain Enterprise Vault placeholder files.

Every time we try to do a restore of a folder that contains Enterprise vault Placeholder files, the file server was  crashing.

Came across this link.

http://www.symantec.com/business/support/index?page=content&id=TECH62001

File server running the File System Archiving (FSA) Agent for Enterprise Vault 2007 can hang during NetBackup Restore operations.

Problem

File server running the File System Archiving (FSA) Agent for Enterprise Vault 2007 can hang during NetBackup Restore operations.

Solution

Legacy placeholders (7.0 SP1, 7.0 and 6.0 SP4 and earlier) for files smaller than 4kb can cause system hangs due to an issue with the Master File Table in NTFS.

Workaround:
This issue can be worked around by unloading the evfilter driver with the fltmc command during the restore operation. (See Related Documents article 293389)

This issue can be avoided by recalling all placeholders created with older versions of Enterprise Vault (7.0 SP1, 7.0 and 6.0 SP4 and earlier), then allowing Enterprise Vault to re-archive and create new placeholders. Additionally, such small files can be excluded from being archived at all with a policy rule based on file size.

Symantec is planning on enhancing the evupdateplaceholder.exe tool to rectify legacy placeholders in the next major release for Enterprise Vault 2007.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

THE FIX is.. NOTE: this will make archived files inaccessible during the restore.

http://www.symantec.com/business/support/index?page=content&id=TECH54993

How to use FLTMC.exe to load and unload the evfilter mini-filter driver for Enterprise Vault (EV) for File System Archiving (FSA)

Problem

How to use FLTMC.exe to load and unload the evfilter mini-filter driver for Enterprise Vault (EV) for File System Archiving (FSA).

Solution

The FLTMC.exe command is run from a cmd prompt on the Windows file server.  The syntax is as follows:

To unload the EvFilter driver:

Fltmc unload EvFilter 
 

To load the EvFilter driver:

Fltmc load EvFilter 

To view all instances of loaded drivers:

Fltmc instances
 

To attach the driver to a specific volume:

Fltmc attach EvFilter C:
 

To detach the driver from a specific volume:

Fltmc detach EvFilter C:
 

NOTE:   The EV services on the file server should be restarted after unloading and reloading the filter driver.
For troubleshooting purposes the results can be saved to a text file. The syntax would be the same as above but adding > [File name and path]
ie: Fltmc instances > C:\FilterInstance.log