none
FEP 2010 Update Rollup 1 - Deployment to Windows 7 Fails (Deployment Pending).

    Вопрос

  • FEP 2010 Update Rollup 1 - Deployment to Windows 7 Fails...

    Dear Brothers,

    I came up, to an issue after the successful installation of "FEP 2010 Update Rollup 1" in our environment.

    Settings:

    1. (Server1) SCCM 2007 Central Site Physical Server with FEP 2010 Server Installed including FEP Necessary Roles.

    2. (Server2) WSUS installed in a Separate Computer.

    Issue Description:

    Everything seems working fine, for 3 consecutive weeks of "Re-Deploying the FEP Client" and set it to "Always Rerun" I have found out that the there are Several Clients around 100+ Windows 7 specifically I can find the computers under "Deployment Pending".

    Previously before applying the Update Rollup 1, the Windows 7 Clients are all reporting perfectly, since applying the Update Rollup 1 also requires re-deploying the FEP Clients with the Rollup 1 Client version. Unfortunately those Windows 7 which previously successfully deployed was now under "Deployment Pending”.

    The question is how can I resolve this issue strategically.

    "

      

    8 июля 2012 г. 11:55

Ответы

Все ответы

  • Hi,

    Thank you for the post.

    1.Re-run all FEP deployment advertisements and they are set to correct clients collections.
    2.Check client exemgr.log (%Windir%\SysWOW64\CCM\Logs) and eppsetup.log (C:\programdata\Microsoft\Microsoft Security Client\Support\).
    3.Open FEP client UI to check the version if show  2.1.1116.0.

    If there are more inquiries on this issue, please feel free to let us know.
     
    Regards


    Rick Tan

    TechNet Community Support


    Модератор
  • Ricky,

    Thanks for the time and response, below are the outcome of your instructions.

    1.Re-run all FEP deployment advertisements and they are set to correct clients collections.

    ---->Advertisement Re-Runs on the Computers Targetted.

    Avertisement Report: on one of the Succeded Deployment Status, the Avertisement runs but the previous Forefront Client needs to be uninstalled first before being a Installed with the Updated Client.

    The program for advertisement "USA2454EC" completed successfully ("USA2454EC" - "Install"). The success description was "Microsoft Forefront Endpoint Protection is already installed. Only one copy of Forefront Endpoint Protection can be installed on your computer at a time. To reinstall Forefront Endpoint Protection on this computer, first uninstall the current version, and then try installing Forefront Endpoint Protection again. Error code:0x4FF02. ". User context: NT AUTHORITY\SYSTEM The program generated an installation status Management Information Format (MIF) file with a status value of Success. For more information, see the documentation for the program you are distributing.

    Note: I though it can perform an "Upgrade" from the Existing/Previous to ver. 2.1.1116.0.?

    2.Check client exemgr.log (%Windir%\SysWOW64\CCM\Logs) and eppsetup.log (C:\programdata\Microsoft\Microsoft Security Client\Support\).

    ---->On Execmgr.log the logs has been showned:

    Mandatory execution requested for program Install and advertisement USA2454EC 7/10/2012 10:50:47 AM 344 (0x0158)
    Creating mandatory request for advert USA2454EC, program Install, package USA000E6 7/10/2012 10:50:47 AM 344 (0x0158)
    Policy is updated for Program: KB977384 - Advanced Client Patch Install, Package: USA000A5, Advert: USA20219 7/10/2012 10:50:47 AM 4048 (0x0FD0)
    CExecutionRequest::Overriding Service Windows as per policy. 7/10/2012 10:50:47 AM 344 (0x0158)
    Executing program cscript.exe Policies\ApplyPolicy.vbs "FEPInstall.exe /s /q " in Admin context 7/10/2012 10:50:47 AM 344 (0x0158)
    Execution Request for package USA000E6 program Install state change from WaitingDependency to NotifyExecution 7/10/2012 10:50:47 AM 344 (0x0158)
    Execution Manager timer has been fired. 7/10/2012 10:50:47 AM 4124 (0x101C)
    Checking content location C:\Windows\system32\CCM\Cache\USA000E6.12.System for use 7/10/2012 10:50:47 AM 344 (0x0158)
    Successfully selected content location C:\Windows\system32\CCM\Cache\USA000E6.12.System 7/10/2012 10:50:47 AM 344 (0x0158)
    GetFileVersionInfoSize failed for file C:\Windows\system32\CCM\Cache\USA000E6.12.System\cscript.exe, error 2 7/10/2012 10:50:47 AM 344 (0x0158)
    Executing program as a script 7/10/2012 10:50:47 AM 344 (0x0158)
    Found executable file cscript.exe with complete path C:\Windows\system32\cscript.exe 7/10/2012 10:50:47 AM 344 (0x0158)
    Successfully prepared command line "C:\Windows\system32\cscript.exe" Policies\ApplyPolicy.vbs "FEPInstall.exe /s /q " 7/10/2012 10:50:47 AM 344 (0x0158)
    Command line = "C:\Windows\system32\cscript.exe" Policies\ApplyPolicy.vbs "FEPInstall.exe /s /q ", Working Directory = C:\Windows\system32\CCM\Cache\USA000E6.12.System\ 7/10/2012 10:50:47 AM 344 (0x0158)
    Created Process for the passed command line 7/10/2012 10:50:47 AM 344 (0x0158)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramStartedEvent
    {
     AdvertisementId = "USA2454EC";
     ClientID = "GUID:66B1F68A-49A5-4F69-B1EF-76641B273871";
     CommandLine = "\"C:\\Windows\\system32\\cscript.exe\" Policies\\ApplyPolicy.vbs \"FEPInstall.exe /s /q \"";
     DateTime = "20120710075047.594000+000";
     MachineName = "USA145-19P464";
     PackageName = "USA000E6";
     ProcessID = 1952;
     ProgramName = "Install";
     SiteCode = "USA";
     ThreadID = 344;
     UserContext = "NT AUTHORITY\\SYSTEM";
     WorkingDirectory = "C:\\Windows\\system32\\CCM\\Cache\\USA000E6.12.System\\";
    };
     7/10/2012 10:50:47 AM 344 (0x0158)
    Raised Program Started Event for Ad:USA2454EC, Package:USA000E6, Program: Install 7/10/2012 10:50:47 AM 344 (0x0158)
    Policy is updated for Program: KB977384 - Advanced Client Patch Install, Package: USA000A5, Advert: USA2033D 7/10/2012 10:50:47 AM 4048 (0x0FD0)
    Policy arrived for parent package USA000E6 program Install 7/10/2012 10:50:47 AM 4048 (0x0FD0)
    Raising event:
    [SMS_CodePage(437), SMS_LocaleID(1033)]
    instance of SoftDistProgramOfferReceivedEvent
    {
     AdvertisementId = "USA2454EC";
     ClientID = "GUID:66B1F68A-49A5-4F69-B1EF-76641B273871";
     DateTime = "20120710075047.719000+000";
     MachineName = "USA145-19P464";
     ProcessID = 1952;
     SiteCode = "USA";
     ThreadID = 4048;
    };
     7/10/2012 10:50:47 AM 4048 (0x0FD0)
    Program exit code 327426 7/10/2012 10:50:51 AM 2588 (0x0A1C)

    ---->eppsetup.log Error has been detected:

    Setup ended successfully with result: Microsoft Forefront Endpoint Protection is already installed. Only one copy of Forefront Endpoint Protection can be installed on your computer at a time. To reinstall Forefront Endpoint Protection on this computer, first uninstall the current version, and then try installing Forefront Endpoint Protection again. Error code:0x4FF02. [0004FF02]

    3.Open FEP client UI to check the version if show  2.1.1116.0.

    ---->It is showing version 2.1.1116.0. Even thought the computer is under the collection "Deployment Pending".

    SCCM with Forefront is good but complicated technology.

     

    10 июля 2012 г. 8:45
  • Hi,

    So FEP clients have updated to Rollup 1 but not reported to SCCM server.
    Please read my post in thread below to narrow down the issue cause.
    http://social.technet.microsoft.com/Forums/en-US/FCSNext/thread/785bce14-003d-4c33-9f16-4d20730c6614

    Regards


    Rick Tan

    TechNet Community Support

    • Помечено в качестве ответа Rick TanModerator 20 июля 2012 г. 1:13
    11 июля 2012 г. 3:14
    Модератор