after patch we still encaounter one or two but it's accpetable to use eboot..
maybe it's really SBFS issue..
before dll patch we have more than 20 machine having this issue..
Did you notice that migrated client (from previous version) does not check SBFS on startup? Only fresh client install?
SCM.INI file needs an upgrade too. That is missed if you do only typical client file set change.
we're not doing any fresh install
the issue encountered is for existing installation.
next time we will look on SCM.INI ..if we found any.. so far no new issue on this..
Running 188.8.131.52 on 20,000 clients, ran into this issue on 20+ clients so far, and I expect more. Opened ticket w/ Gold Support, and implemented fix for broken machines this way:
Created new Client File set.
Added MergeINI file with the settings posted above
Added sbchkdsk.dll from v5.2.5 file set.
Created new machine group.
Assigned common settings/users like regular groups.
Assigned the Client File set created above.
Per Machine fix:
Move the machine to the new machine group and force sync (pulls down the new fileset)
Reboot client (logon with *existing* alternative EEPC credentials)
Sync at least once (check log for chkdsk activity and for correct user assignment)
Thanks for posting this!
Download the new ePolicy Orchestrator (ePO) Support Center Extension which simplifies ePO management and provides support resources directly in the console. Learn more about ePO Support Center
2821 Mission College Blvd.
Santa Clara, CA 95054 USA
Consumer Support | Enterprise Support | McAfee.com
Legal | Privacy | Copyright © 2019 McAfee, LLC