Profiles/Policies: Beware the Registry Size (fwd)

[Luke Kenneth Casson Leighton]

<a href="mailto:lkcl at samba.org" > Luke Kenneth Casson Leighton    </a>
<a href="http://cb1.com/~lkcl"  > Samba and Network Development   </a>
<a href="http://samba.org"      > Samba Web site                  </a>
<a href="http://www.iss.net"    > Internet Security Systems, Inc. </a>
<a href="http://mcp.com"        > Macmillan Technical Publishing  </a>
 
ISBN1578701503 DCE/RPC over SMB: Samba and Windows NT Domain Internals

---------- Forwarded message ----------
Date: Fri, 18 Feb 2000 11:57:02 -0600
From: R. Michael Williams <RMW_MCSE at Acelink.net>
To: NTBUGTRAQ at LISTSERV.NTBUGTRAQ.COM
Cc: 'Luke Kenneth Casson Leighton' <lkcl at SAMBA.ORG>
Subject: RE: Profiles/Policies: Beware the Registry Size (fwd)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

It is a known issue, but I believe it is no different than a "disk
full" situation. NT places limits on the registry size one can
reasonably assume to prevent the registry from growing too large for
the OS to manage (there are functional and absolute limits on the
registry size relative to system resources and OS requirements). I
have encountered this problem before, most notably the inability to
do certain things on Citrix servers. This has been documented by
Citrix technical support staff.

It appears that, allowing for some inconsistent language in the
below-referenced KB articles, the settings noted by Mr. Kuit and the
registry settings are directly related. However, my registry does not
shop the referenced RSL entry to support the size indicated in the
referenced dialog. 

In Q176083, note that the popup dialog to warn of impending limit
only appears *once per boot cycle*. If the machine has been running
for some time in a marginal state, someone may have cleared the popup
and told no one. Running performance monitor would be in order.

For more relevant or helpful information on registry size limits:

Q176083: System Is Running Low on Registry Quota
http://support.microsoft.com/support/kb/articles/Q176/0/83.ASP

Q124594: Understanding and Configuring Registry Size Limit (RSL)
http://support.microsoft.com/support/kb/articles/Q124/5/94.asp

Q126402: PagedPoolSize and NonPagedPoolSize Values in Windows NT
http://support.microsoft.com/support/kb/articles/Q126/4/02.ASP

Q189119: UserEnv Returns Corrupted Profile for All Failures Including
RSL Exceeded 
http://support.microsoft.com/support/kb/articles/Q189/1/19.ASP

Q152721: Low on Registry Quota Error Gives Wrong Steps for Resolution
http://support.microsoft.com/support/kb/articles/Q152/7/21.asp

Q171793: Information on Application Use of 4GT RAM Tuning
http://support.microsoft.com/support/kb/articles/Q171/7/93.ASP

Hope this helps.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

R. Michael Williams
Network Consultant
Inacom Networks
Nashville, TN  

- -----Original Message-----
From: Windows NTBugtraq Mailing List
[mailto:NTBUGTRAQ at LISTSERV.NTBUGTRAQ.COM]On Behalf Of Luke Kenneth
Casson Leighton
Sent: Thursday, February 17, 2000 5:59 PM
To: NTBUGTRAQ at LISTSERV.NTBUGTRAQ.COM
Subject: Profiles/Policies: Beware the Registry Size (fwd)


does anyone know if this is a known problem on nt or not?  it's
actually
not related to samba, it could happen in a pure nt-only environment.

<snip>

- ---------- Forwarded message ----------
Date: Fri, 18 Feb 2000 10:49:53 +1100
From: Benjamin Kuit <bj at mcs.uts.edu.au>
To: Multiple recipients of list SAMBA-NTDOM <samba-ntdom at samba.org>
Subject: Profiles/Policies: Beware the Registry Size


Disclaimer: This is not a problem or feature of Samba as a PDC, but
is
of interest to people setting up domains.

<snip>

The problem seems to fall to a registry size limit on the NT
workstation,
which can be accessed by
Control Panel -> System -> Performance -> (Virt. Mem)Change

This brings up the Virtual Memory properties dialog box, and at the
bottom
of it shows current and maximum registry sizes.

The problem was the maximum registry size was set to the same value
as the
current registry size, so once the profile was loaded, there simply
wasn't
any more room for the policy to be loaded into the registry, so the
policies
dont take any effect, and because it doesn't give any warning
messages for
not having enough room, it remains a mystery to most people.

This could be a source of alot of 'my policies dont work' type
problems.

The moral of the story is: Check the maximum registry size.

Just trying to help =)

caio

Bj

<snip>

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.1 for non-commercial use <http://www.pgp.com>

iQA/AwUBOK2H7leNe+8UfuD4EQKxsACg0LkJ7AbCKXtTFRkki93xEFxbQ2gAn1SK
3I700X5Tfg2pkj+25M2+KezO
=cOwW
-----END PGP SIGNATURE-----