I usually don’t do this, but since not all the information seems to be in a single spot I’m compiling a bit.

Adobe released the following:
http://www.adobe.com/support/security/advisories/apsa09-01.html

A critical vulnerability has been identified in Adobe Reader 9 and Acrobat 9 and earlier versions. This vulnerability would cause the application to crash and could potentially allow an attacker to take control of the affected system. There are reports that this issue is being exploited.

Adobe is planning to release updates to Adobe Reader and Acrobat to resolve the relevant security issue. Adobe expects to make available an update for Adobe Reader 9 and Acrobat 9 by March 11th, 2009. Updates for Adobe Reader 8 and Acrobat 8 will follow soon after, with Adobe Reader 7 and Acrobat 7 updates to follow. In the meantime, Adobe is in contact with anti-virus vendors, including McAfee and Symantec, on this issue in order to ensure the security of our mutual customers. A security bulletin will be published on http://www.adobe.com/support/security as soon as product updates are available.

All documented security vulnerabilities and their solutions are distributed through the Adobe security notification service. You can sign up for the service at the following URL: http://www.adobe.com/cfusion/entitlement/index.cfm?e=szalert

It affects all versions of Adobe’s Acrobat (Pro, Standard, and Reader) version 9, 8, 7, and potentially 6/5. Currently the exploit uses JavaScript to call on memory that hasn’t been allocated properly and causes exceptions and an application failure. So, at a minimum, this exploit will crash out your Adobe Acrobat. At a maximum, it can open up your entire system to “bad things”. The exploit in the wild, as of right now, only uses javascript. Therefore, one can simply follow these steps:

Open Adobe Acrobat Reader (version 8 or 9)
Click Edit >> Preferences
Scroll down to JavaScript and uncheck Enable Acrobat JavaScript
Click OK

Or if you would prefer to use registry keys (and if you’re like me and use GPO’s to deploy the registry key imports at startup) here they are:

Add the key HKCU\software\adobe\acrobat reader\x.0\JSPrefs
Add a DWORD "bEnableJS", set value to 0
also make sure you look in HKCU\software\adobe\adobe acrobat\.. as well. The same thing applies to all versions.

It should be noted that JavaScript is merely used as the compiling tool in this case. Without JS enabled, the exploit STILL EXISTS, it’ll just be harder (in theory) to write for.

If anyone has done disk backups using the DOS Ghost client (or other DOS based clients) you have probably had some issues with NTFS. Don’t get me wrong, NTFS is a pretty decent file system, but FAT32 is noticeably more compatible.

Getting a drive that’s NTFS to work on DOS/MAC/Pre-Windows 98/Linux is sometimes a PITA.

Most external drives come preformatted as FAT32 for this very reason. If you need it NTFS that’s no big deal – just open up the disk manager in Windows and blast away (diskmgmt.msc). Windows, however, has a limit on formatting for FAT partitions: 32GB. Whoopie.

The easiest way is to use a disk formatting utility (Hiren’s has some good ones on there). The second easiest is to use DOS style commands.

Start
Run
CMD
format /FS:FAT32 G:
Y

The command can be broken down as follows:
Format – this is the actual command
/FS:FAT32 – Filesystem Fat32
G: – the drive letter of the drive you want to reformat

***EDIT***
Apparently you can also use several freeware programs. One that was given to me is called Swissknife.

When people install programs without fully realizing what they are doing, bad things tend to happen. Installing Exchange can be a tedious process – it has so many prerequisites that it can take several hours just to get to the point that exchange actually starts to install.

As we all know, Exchange 2007 requires a 64bit operating system. At least it’s required in a production environment since Microsoft will not support 32bit 2007 servers. We also know that Exchange 2007 does not read from the Global Catalog if the GC is running on a Windows 2000 Server. The newest Exchange requires a minimum of 2003 standard in order to read fully from Active Directory. And we all know that AD is required for Exchange to be happy. These are things we know.

If you open the Exchange Management Console and navigate to Server Configuration. In the main reading pane you should see your Exchange Server(s). Right click on your Exchange Server and select properties. The bottom two text boxes will show you the current Domain Controller(s) and Global Catalog(s). If you have more than one Domain controller and Exchange is only showing one, you have a problem.

First thing to check is always the Eventviewer. Check the eventvwr!!!
Second thing to check is if you can ping your DC from the Exchange Server, and that you can ping your Exchange Server from your DC.
Third thing is to run the command “dcdiag” on the DC not showing up in Exchange:
Start - Run - CMD - dcdiag - press enter
IF all of those pass with flying colors, you can add the DC and GC manually to Exchange using the PowerShell.

PowerShell Fix Steps:

On the Exchange Server, open the Exchange Management Shell.
set-exchangeserver -identity Name_Of_Server -staticDomainControllers ‘dc.domain.com’, ‘dc2.domain.com’
set-exchangeserver -identity Name_Of_Server -staticglobalcatalogs ‘dc.domain.com’, ‘dc2.domain.com’

IMPORTANT NOTE!!!
the Name_Of_Server MUST BE the name of your server. If you named it exchange07, use that name!
the ‘dc.domain.com’ MUST BE the FQDN Fully Qualified Domain Name of your server. If the servername is exchange07, the FQDN would be something like exchange07.mydomain.local!

Then recheck in the Exchange Management Console to verify that the GC and DCs are properly imported.

If you ever need to remove the additions:
get-exchangeserver -identity Name_of_server -staticdomaincontrollers $NULL
get-exchangeserver -identity Name_of_server -staticglobalcatalogs $NULL
After roughly 15 minutes, the “real” GC and DC’s should be populating. If not, check the eventviewer!