Event IDs 1085 and 1202

Discussion in 'Windows Desktop Systems' started by kcnychief, Dec 29, 2005.

  1. kcnychief

    kcnychief █▄█ ▀█▄ █ Political User Folding Team

    Messages:
    16,948
    Location:
    Massachusetts
    Although this is a domain environment, it's occuring on the desktop level so I assume this is the correct place to post.

    A lot of our machines are receiving the following errors in Application Event Viewer
    I am currently searching everything I can find on Google, was just wondering if anyone had come across this before.
     
    Last edited: Dec 29, 2005
  2. mlakrid

    mlakrid OSNN BASSMASTER Political User Folding Team

    Im not a system admin but maybe a local vs domain policy problem?
     
  3. kcnychief

    kcnychief █▄█ ▀█▄ █ Political User Folding Team

    Messages:
    16,948
    Location:
    Massachusetts
    It is security related.

    This was a new image that was deployed, the difference being the mini-setup wizard regarding sysprep. If you have a machine that adds a PC to a domain within the mini-setup wizard, it's fine. In this new, or different image, the mini-setup wizard is more automated and that option is not available in hopes to deal with a USB driver lockup problem.
     
  4. kcnychief

    kcnychief █▄█ ▀█▄ █ Political User Folding Team

    Messages:
    16,948
    Location:
    Massachusetts
    I actually got this fixed, what I ended up doing was removing the security database and templates located at:

    C:\WINDOWS\security\templates\compatws.inf
    C:\WINDOWS\security\templates\hisecdc.inf
    C:\WINDOWS\security\templates\hisecws.inf
    C:\WINDOWS\security\templates\rootsec.inf
    C:\WINDOWS\security\templates\securedc.inf
    C:\WINDOWS\security\templates\securews.inf
    C:\WINDOWS\security\templates\setup security.inf

    C:\WINDOWS\security\Database\secedit.sdb

    After those were removed, a "gpupdate /force" produced a 1704, woo :)

    Only the secedit.sdb file gets re-created after the refresh, but I don't need the templates since I am not implementing local security. The point of this was for the DC to take care of it, and now it does :)