http://technet.microsoft.com/en-us/library/bb332342(EXCHG.80).aspx

Backup Exec by default will report a failed backup if corrupt files are encountered. Backup Exec also sees open files ie. QuickBooks databases that are open when the backup is running as a corrupt file. If you want to disable this in Backup Exec, go to regedit and modify the following registry entry from 1 to 0: Fail Jobs on Corrupt Files

HKEY_LOCAL_MACHINE\SOFTWARE\VERITAS\Backup Exec\Engine\Backup

http://seer.entsupport.symantec.com/docs/193940.htm

Situation: Exchange 2007 has a contact (not a mailbox) within the GAL that end-user uses to email instead of using the actual non-exchange email address. The non-exchange (network solutions) user does not get attachment sent (Word, Excel, etc.), but does get a winmail.dat file attached.

Fix: Launch Exchange Management Console, goto Recipient Configuration/Mail Contact container, open up contact you’re having the issue with, on the ‘general’ tab change the ‘Use MAPI rich text format’ drop-down to ‘Never’ and test.

Compatibility and requirements:

• The capacity of the removable media must be at least 256 MB (250 after formatting)
• Devices larger than 4 GB will have only 4 GB used for ReadyBoost
• The device should have an access time of 1 ms or less
• The device must be capable of 2.5 MB/s read speeds for 4 KB random reads spread uniformly across the entire device and 1.75 MB/s write speeds for 512 KB random writes spread uniformly across the device
• The device must have at least 235 MB of free space
• NTFS, FAT16 and FAT32 are supported
• The initial release of ReadyBoost supports one device
• The recommended amount of flash memory to use for Windows ReadyBoost acceleration is one to three times the amount of random access memory (RAM) installed in your computer

I recently came across a client’s backup that was completing successfully daily but not flushing the transaction logs for Exchange as it should.  In the job properties of Backup Exec, the Exchange section declares that it will perform a full backup and flush the comitted logs but it simply never happens.

After some research, Veritas article 280659 had the answer…and it was a simple one.  In the job properties, review the options under Advanced Open File and make sure the option “Process Logical Volumes for backup one at a time” is not checked.   As its explained in the article, if this is unchecked, Backup Exec will use a different open file option (VSS) for the Exchange logs to allow it to flush them afterwards. 

I recently came across a PC that prompted me for the SKU011.CAB file everytime I ran an Office application.  The verions of Office it listed was Office Professional 2003 so I popped in my Office 2003 Pro CD and tried to use that to replace the file.  I was unable to find SKU011.CAB on the CD and after checking the CD Key in use discovered that Office 2003 Pro Enterprise was the actual version installed.  Not having an Enterprise CD, I thought I was stuck.

Then I found the Local Installation Source Tool from Microsoft and was saved.  I downloaded the tool and used the “Delete and disable LIS” option to remove the local installation source and after the next attempt to start and Office App I was off and running.

You can get the tool here:
http://www.microsoft.com/downloads/details.aspx?familyid=10fa7aa3-695b-42c3-9045-b812ba0fed3e&displaylang=en

Some spyware may create a desktop background to replace your own.  After doing this, I’ve seen the display properties tabs for modifying the screensaver and wallpaper disappear to prevent the user from getting rid of the malicious wallpaper.  To bring these tabs back, navigate to the following Registry string:

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\System

Here, you will find the keys responsible.  They are:

NoDispBackgroundPage
NoDispAppearancePage

These will likely be set to 1.  Set them to 0 or delete them to get your tabs back. 

Microsoft Forefront Security for Exchange Server is the cause of this messsage:

The original contents of this file have been replaced with
this message because of its characteristics.
File name: ‘winmail.dat’
Virus name: ‘CorruptedCompressedFile’

====================

Quick fix:

Goto Forefront Server Security Administrator > Settings> General Options > Scanning
Goto checkbox name “Delete Corrupted Compressed File”
Uncheck the box and test

To find the product version in Exchange 2007, execute the following command in PowerShell:

Get-ExchangeServer | fl name,edition,admindisplayversion

Refer to the article below to find out how the build number corresponds to a product version:

http://blog.kazmarek.com/2008/07/04/exchange-server-version-and-build-numbers/

This microsoft article details the various Exchange Server versions, including service packs.

http://support.microsoft.com/kb/158530

Some recent ones:

Microsoft Exchange Server  2003                       6.5.6944                             October 2003
Microsoft Exchange Server  2003 SP1                 6.5.7226                             May 2004
Microsoft Exchange Server  2003 SP2                 6.5.7638                             October 2005

Microsoft Exchange Server  2007                       8.0.685.24 or 8.0.685.25    December 2006
Microsoft Exchange Server  2007 SP1                 8.1.0240.006                      November 2007