Scepol.log

D

Diana Smith [MSFT]

Hello Jack,

There are two registry values that control this behavior

1. to stop the debugging, set the "PolicyDebugLevel" value to 0 (may have to
create this value, if not existing)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SecEdit

Value Name: PolicyDebugLevel
Data Type: REG_DWORD
Radix: Decimal/Hex
Value: 0

2. to set the size of the Scepol.log file, set the "PolicyLogSize" value to
0,1 etc
(default is 1MB if set to 0) (may have to create this value, if not
existing)

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SecEdit

Value Name: PolicyLogSize
Data Type: REG_DWORD
Radix: Decimal/Hex
Value: 0

- the above registry values are not functional or do not behave as expected
until you install the Q827684 hotfix. You may obtain this hotfix by
contacting Microsoft at 1-800-936-4900 and reference the article listed
below:

827684 Scepol.log File Size Increases Beyond 1 MB Limit
http://support.microsoft.com/?id=827684

Thank You.

Diana.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Scepol.log 1
scepol.log 3
Scepol.log 1
corrupt local group policy database 1
Files that don't defrag. 5
scepol.log File Size = 226 MEG (What???) 2
SceSrv - 1003 1
error SceSrv 1003 in EventLog 2

Top