locked
Microsoft forefront clients are updated but in report showing as not updated RRS feed

  • Question

  • Cleints are getting updated however in report still it has old definition.
    Wednesday, December 7, 2011 11:37 AM

All replies

  • Hi,

    Thank you for your post.

    1. Run "Scan Now" on your FCS console
    2. In MOM Admin Console, verify your FCS client computers under Agent-managed Computers/ or computers show Agent-managed in All computers
    3. Check your clients if installed MOM or reinstall MOM client on your computers
    4. All your clients report old definition? Please provide any event log errors from clients or MOM Operator Console

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

    Regards


    Rick Tan

    TechNet Community Support

    • Marked as answer by Rick Tan Friday, December 16, 2011 2:11 AM
    • Unmarked as answer by kiran1472001 Friday, December 16, 2011 9:23 AM
    Friday, December 9, 2011 7:02 AM
  • hi RIck,

    we are generating Report throght SCCM, we have Advertisment set for pushing updates to FCS client.


    Kiran.d.patel
    Friday, December 16, 2011 9:23 AM
  • it has been ovserved that at location C:\WINDOWS\SysWOW64\CCM\Inventory\noidmifs, file called MSFCS.mif, which is not getting updated when we run update on client and due to which SCCM pulls up report with old definiation. any idea how to make this work. need help as we have audit in some time.
    Kiran.d.patel
    Monday, December 19, 2011 4:04 AM
  • Hi,
     
    Clients are getting updated however in report still it has old definition.

    I understand that your report data just show the definition version several days before.

    we are generating Report throught SCCM.

    Try to configure the DCM Client Agent settings in SCCM.
    About Forefront Client Security Integration with Configuration Manager 2007 R2

    it has been ovserved that at location C:\WINDOWS\SysWOW64\CCM\Inventory\noidmifs

    Try to run Hardware Inventory Cycle on your SCCM client.

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

    Regards,


    Rick Tan

    TechNet Community Support

    Monday, December 19, 2011 7:46 AM
  • Hi Rick,

    DCM is already enable on the server as i am getting configuration tab, issues with only few servers not with all servers  i ve 14 servers out of 200 which are not getting updated, please suggest me any specific logs if i can see it to get exact error.

     

    thanks


    Kiran.d.patel
    Saturday, December 24, 2011 8:27 PM
  • Hi Kiran,

    i am getting configuration tab, issues
    Please click "repair" in components tab, wait 10 minutes then check the configuration tab.

    please suggest me any specific logs if i can see it to get exact error
    DCM issues need to look at C:\Windows\SysWOW64\CCM\Logs\DCMAgent.log.

    Regards,


    Rick Tan

    TechNet Community Support

    Monday, December 26, 2011 2:59 AM
  • hi Rick,

    as per my observation, when advertisment gets pushed, it copies three files in Cache folder of sccm. Def_deploy (which deploys MPFEx64.exe), Def_status (which updates registry value and msfcs.mif file at \inventory\noidmifs location) and MPFEx64.exe.

    as per my trouble shooting i came to know that this scripts runs with my accoount, however it doesn't run with System account which is configured for advertisement.

    when i run this script with my account it creates .mif file at location i needed, however it gets deleted automatcally when i see after 30 to 40 minutes.

    this scripts runs on another server without any issue, i ve an issue with 5 servers.

    please let me know any suggestion for this.


    Kiran.d.patel
    Wednesday, December 28, 2011 12:48 PM
  • these are the logs which i ve received.

    DCM Agent shutting down... DCMAgent 12/28/2011 6:12:52 PM 3060 (0x0BF4)
    CDCMAgent::Uninitialize succeeded. DCMAgent 12/28/2011 6:12:52 PM 3060 (0x0BF4)
    DCM Agent starting up... DCMAgent 12/28/2011 6:19:39 PM 2500 (0x09C4)
    Updated DCM agent configuration Enabled='true', PerProviderTimeout='120', PerScanTimeout='360', PerScanTTL='15', PerScanDefaultPriority='0' DCMAgent 12/28/2011 6:19:39 PM 2500 (0x09C4)
    CDCMAgent::Initialize succeeded. DCMAgent 12/28/2011 6:19:39 PM 2500 (0x09C4)
    DCM Agent successfully started up. DCMAgent 12/28/2011 6:19:39 PM 2500 (0x09C4)


    Kiran.d.patel
    Wednesday, December 28, 2011 12:50 PM