Forefront and Windows 2000 Installations

Got nailed with two odd install error while pushing out Forefront to old 2000 systems

Odd Problem One

The dreaded GDI+ error:

This product requires GDI+. Please load the Windows 2000 Security Software PreRequisite Pack.

gdiplus+ error on Windows 2000

gdiplus+ error on Windows 2000

But I have! and the GDIPLUSS.DLL is in the %systemroot%\system32 directory too!

So after attempting a bunch of things got this to work (yes, using the magic of batch file!)

Download and extracted gdiplus.dll to the forefront distribtion point and created this batch file to create the directory “C:\Program Files\Microsoft Forefront\Client Security\Client\Antimalware” and copy the gdiplus.dll there. Forefront installed without further issue!

Example

REM
REM Create GDIPLUS.DLL path
MD “C:\Program Files\Microsoft Forefront\Client Security\Client\Antimalware”
REM
REM Copy GDIPLUS.DLL locally
copy .\GDIPLUS.DLL “C:\Program Files\Microsoft Forefront\Client Security\Client\Antimalware”
REM

Odd problem two

Attempting to install on an old 2000 server and Forefront continued to fail. Check the log and it was failing at the MOM agent install. All that was there was momagent.msi 3: -2147287037

Helpful.

So eventually copied all the Forefront install files to the C drive and re-ran the install locally. Worked without issues.

I know look forward to deleting that server and attempting to get back the hour of my life searching the internet with out any luck.

5 thoughts on “Forefront and Windows 2000 Installations

  1. THANK YOU VERY MUCH!!!

    Three days I’ve wasted searching for the answer to this, copy the same damn file in and out of system32, loaded updates and patches….

    Maybe microsoft should actually release this so called “Pre-Requisite Pack” or here’s an idea throw that dll into the setup file so it can copy it if needed lol

    I guess I should be happy they even bothered including 2000 support on this app.

    Anyway enough of my rant. This fix definitely works and thank you very much.

    -Kenny

  2. Same here, thank you so much for this!

    I’ve been looking for days as well doing the same thing, copying to sys32 etc, this worked like a champ!

  3. Thanks! I had read somewhere else how to fix this same error for Windows Defender (i.e. copy to local installation directory) so tried copying the file directly to the Forefront “client” folder. Didn’t work obviously but I nearly had it ;)

Leave a Reply

Your email address will not be published. Required fields are marked *

*

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>