locked
Forefront client refuses to install on Server Core 2008R2 RRS feed

  • Question

  • We have a few core servers, and one of these is refusing to install the Forefront client.

    This is the command line we run: x64\clientsetup.exe /cg ForefrontClientSecurity /MS NP1

    (NP1 is the FCS/MOM server).

    In the clientsetup.log file I see 

    2011-07-12 13:13:10 Microsoft Forefront Client Security (1.0.1703.0) -- Installation started
    2011-07-12 13:13:10 Hardware requirement check passed.
    2011-07-12 13:13:10 Warning: This version of Vista is not supported.
    2011-07-12 13:13:10 OS requirement check passed.
    2011-07-12 13:13:10 Software requirement check passed.
    2011-07-12 13:13:19 MOM Installation Completed Successfully.
    2011-07-12 13:13:21 SSA Installation Completed Successfully.
    2011-07-12 13:13:22 AM Installation Failed. See FCSAM.log for details.
    2011-07-12 13:13:22 Microsoft Forefront Client Security -- Installation failed.
    


    So apparently it thinks the server is running Vista and it fails to install the antimalware component. the FCSAM.log file says a lot of stuff and then near the end...

    MSI (s) (08:2C) [13:13:22:255]: Doing action: MsiProcessDrivers
    Action ended 13:13:22: InstallFiles. Return value 1.
    MSI (s) (08:2C) [13:13:22:255]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'MsiProcessDrivers' 
    MSI (s) (08:D0) [13:13:22:255]: Invoking remote custom action. DLL: C:\Windows\Installer\MSIBB28.tmp, Entrypoint: ProcessDriverPackages
    Action start 13:13:22: MsiProcessDrivers.
    DIFXAPP: ENTER: ProcessDriverPackages()
    DIFXAPP: ERROR - The operating system you are running on is not supported. Only Windows 2000, Windows XP, Windows Server 2003 and Windows codenamed Longhorn are supported.
    CustomAction MsiProcessDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (08:2C) [13:13:22:270]: Machine policy value 'DisableRollback' is 0
    MSI (s) (08:2C) [13:13:22:270]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    Action ended 13:13:22: MsiProcessDrivers. Return value 3.
    MSI (s) (08:2C) [13:13:22:270]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 
    MSI (s) (08:2C) [13:13:22:270]: No System Restore sequence number for this installation.
    MSI (s) (08:2C) [13:13:22:270]: Unlocking Server
    Action ended 13:13:22: INSTALL. Return value 3.
    MSI (s) (08:2C) [13:13:22:286]: Note: 1: 1708 
    MSI (s) (08:2C) [13:13:22:286]: Product: Microsoft Forefront Client Security Antimalware Service -- Installation failed.
    
    MSI (s) (08:2C) [13:13:22:286]: Windows Installer installed the product. Product Name: Microsoft Forefront Client Security Antimalware Service. Product Version: 1.5.1937.3. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
    

    Any ideas? help? (I could post full log files if needed). The funny thing is this works just fine on other core servers... where the only real difference I can see is that this is a domain controller whereas the others are member servers. (The client installed just fine on a Standard Server 2008R2 domain controller though...)

     

    Tuesday, July 12, 2011 11:21 AM

Answers

All replies

  • DIFXAPP: ERROR - The operating system you are running on is not supported. Only Windows 2000, Windows XP, Windows Server 2003 and Windows codenamed Longhorn are supported.

     


    Hi,

    Have a look here http://support.microsoft.com/kb/976668 ; http://support.microsoft.com/kb/976669


    Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/ | Time zone : GMT+1
    Wednesday, July 13, 2011 7:06 AM
  • Hm, yes they acknowledge there's a problem. Kind of curious as to why this don't happen to all of our core servers though...

    Still, the first link was a hotfix (only), and the second just says it's available from Windows Update. My question then... how can I apply a hotfix or update to a product that I can't install??

    (I'm a bit confused as I don't have that much experience with Core servers to be honest...)

    Wednesday, July 13, 2011 8:18 AM
  • the second link is an new FCS client which supports Windows core and it is only available from WSUS. So, if you've WSUS you can download and install the package otherwise you can install WSUS on a test machine, download the file locally and install it manually on the server.
    Bechir Gharbi | http://myitforum.com/cs2/blogs/bgharbi/ | Time zone : GMT+1
    Wednesday, July 13, 2011 9:00 AM
  • Ah, okay. We have WSUS so I went digging around... turns out there's a newer update rollup of the client at http://support.microsoft.com/kb/2508824 ... Of course, that had downloaded 4 files with the same name so I had to go around extracting and comparing to figure out which one was the x64. Once I did however, it worked just fine apparently :D

    So, thanks! I still wish MS had made a new updated installer available a bit more easily for it's enterprise customers... :D

     

    Wednesday, July 13, 2011 10:19 AM