Help Center


Installing Forefront Endpoint Protection (FEP) Returns Error 327426 or 327424

Error 327426 means that the Program is already installed. In cases like this, you can simply add this code to your Success Codes field. This way when a deployment is attempted and the program is already installed it won't return as a failed deployment. 

Error 327424 seems to be similar to the standard success code of 3010. This code simply means "Successful installation and a reboot is required". I'm not sure why Microsoft didn't just have this return 3010 but there you go. I haven't found definitive documentation from Microsoft about this error but I have seen many references online stating that it simply means a reboot is needed.


Was this article helpful?
1 out of 1 found this helpful
Have more questions? Submit a request


  • 0

    Ran through the deployment on !7x64sp1, fully patched as of 1/30/12 and received 327426. It didn't appear installed, and on reboot I confirmed that it did not install. Control Panel showed no software installed. Event logs showed no errors. I'm wondering if this is because of the built in Windows Defender service... 

  • 0

    Hi Joseph,

    Do you see any Forefront files or directories on the target system? How long did the deployment run before returning 327426? Try running the installation manually using the same command line parameters that are used in the deploy package. What is the result of the manual install?

  • 0

    Wow, awesome response time! Thanks.

    I checked the directories after the redeploy and there was the Defender folder, but no System Center, Security Client or Forefront directories. Luckily I'm working in a lab with golden images, so I can restore at any time to a pristine state. After bringing the image back up, I disabled UAC, redployed, and got the same error. I restored and ran the command \server\share\folder\SCEPInstall.exe /s /q. It installed successfully and created directory c:\program files (x86)\Microsoft Security Client.

  • 0

    Defender could be the issue I suppose. When a deployment is initiated the deployment files get copied down to the target machine's Windows\PDQDeployRunner directory.


    If Defender (or another service) prevents files from being copied or executed from this directory the installation will fail. It usually fails with a 1603 error, however.

    Will you export your deploy package for Forefront? You can either email it to support at or attach it here. Please remove any confidential info (such as server names or shares) and then send it. I'd like to take a peek.

  • 0

    Sure thing - 

  • 0

    Found a solution - checked the Include entire directory box and it worked.

    I'm not sure why that makes a difference, since the network share install works manually, but I'll take it!

  • 0

    Its because pdq deploy copies the files to the target computer and executes it locally.

  • 0

    Ah, got it. I assumed it ran the install from the repository location unless you checked the box. Makes sense.

    That means, if I follow, if I had wrapped the command inside a batch script, it would have worked without the upload.

  • 0

    this batch file should let you install even if already there.


    @echo off

    TITLE Forefront Protection Install


    ECHO Forefront...

    start /wait \[server]\share]\FEP.exe /s /runwgacheck /o


    ECHO Definition Updates...

    start /wait [server]\share]\FEP_Update.exe /q

Article is closed for comments.