Hi All,
Does anyone know if corrupted secedit.sdb database on Windows XP SP3 can impact on a logon speed?
I have noticed that on many of our laptops, logon (especially applying personal settings) takes very long time. On all affected machines there was an error in the log stating an extended error applying a security policy.
I have fixed the database using esentutl and noticed that the logon process is faster.
Does anyone know why?
I need to know this before recommending a fix on over a thousand laptops (all built on the same syspreped image).
Regards,
Michael
Does anyone know if corrupted secedit.sdb database on Windows XP SP3 can impact on a logon speed?
I have noticed that on many of our laptops, logon (especially applying personal settings) takes very long time. On all affected machines there was an error in the log stating an extended error applying a security policy.
I have fixed the database using esentutl and noticed that the logon process is faster.
Does anyone know why?
I need to know this before recommending a fix on over a thousand laptops (all built on the same syspreped image).
Regards,
Michael