Has anyone seen this issue?
Using EEM and updating a single file in the file group. The file gets updated on the client but then after a client restart the file reverts back to prior version.
Running EEPC 5.2.9 on Win7 X64 SP1. the file is updated while the machine is being deployed and logged on as local admin when it syncs with the EEM server. This maybe a OS 'feature' but trying to figure out how to deal with it.
it usually means you have two files with the same name in two groups assigned to the same machine - check sbfiles41.lst for duplicates, and if possible post that and the client log here...
ok. which file is it - there's nothing I can see in the log indicating anything's changing? What's the BP510 log file from?Message was edited by: SafeBoot on 11/26/11 11:00:34 AM EST
It would be file sbcredprov.dll line # 182 in the client log. The bp510 log is from a script i wrote to check the file version during a machine deployment after the sync. . Trying to update this dll from 5.2.9 to 5.2.10. the process is works for existing 5.2.9 macihnes but not during our deplyment of a new macihne with 5.2.9 installed.
Why not rebuild your install set so the current file is deployed as part of the package?
I think you are right - the problem is the Windows file update service regressing the file.
I wish modifying a gold install image was quick and simple.... its great that encryption is being installed on 100% of the machines but it comes at a cost.
not sure I have a solution for you unfortunately - upgrade during activation is not really supported, neither is mixing 5.2.10 files and 5.2.9 files