Local Security Policy broken

[Muppet Hunter]

I'm using 1.3 final and opted to keep Local Security settings, yet when clicking on Local Security Policies in Administrative Tools the window comes up with the message 'MMC could not create the snap-in'. I've never had this mess up before, so I'm guessing that something's gone wrong between version 1.0.1 and 1.3 (1.2 never worked for me and I didn't try the 1.3 betas). I'm using W2K3 SP2, last session.ini attached.

BTW keep up the good work!

Last_Session.ini

Edited March 31, 2007 by Muppet Hunter

[Muppet Hunter]

I've done a bit of Googling and have come across a couple of sites that mention that certain dll's need to be registered if you're getting the above problem. Here http://briandesmond.com/blog/archive/2006/...g-on-Vista.aspx talks about getting Win 2K3 Admin Tools working on Vista, so I copied all dll's to System32 and registered them all. This didn't fix the problem.

I later found this page http://groups.google.co.uk/group/microsoft...um=17&hl=en and did the same as before. This worked and Local Security Policy is as before. Missing/unregistered dll's appear to be at fault, probably the ones listed on the second site (below). This might possibly be an nLite problem and if so would be a fairly major problem if anyone else were affected.

appmgmts.dll

appmgr.dll

certmgr.dll

dskquota.dll

fdeploy.dll

fde.dll

gpedit.dll

gptext.dll

iedkcs32.dll

ieaksie.dll

ipsecsnp.dll

rigpsnap.dll

scecli.dll

wsecedit.dll

Of these files the following were completely missing from my (nLited) install CD (not even in any of the CAB's) :-

appmgr.dll

certmgr.dll

dskquota.dll

gpedit.dll

gptext.dll

ieaksie.dll

iedkcs32.dll

After copying and registering, the files below were under mmc.exe in Process Explorer (after running secpol.msc).

certmgr.dll

gpedit.dll

gptext.dll

ipsecsnp.dll

scecli.dll

wsecedit.dll

Edited March 27, 2007 by Muppet Hunter

[Muppet Hunter]

The problem is solved if you copy gpedit.dll and gptext.dll into the system32 folder and run regsvr32 on them. It seems that if you remove the Group Policy Management Console then these two files get removed, and this breaks Local Security Policy.

[nuhi]

Ok, going to add that dependency info into the description, thanks.

[Muppet Hunter]

This problem is still here in 1.4 beta, but the solution is the same. I'm not sure of how to automate the solution, but I'd guess you'd put them in the keepbox or a $oem$\$$\system32 folder on the root of your cd and run a command/batch file or something at first boot.

Is there any way that gpedit.dll and gptext.dll could be left in even if you removed group policy editor to keep compatibility? Could the option to remove local security policy editor be configured to remove these files instead?

Edited June 18, 2007 by Muppet Hunter