[THIN] Re: Suggested Registry size

I have confirmation, it was the W2K3 SMS agent hanging the profiles on my
machines, that was causing the registry to explode.

  _____  

From: Landin, Mark [mailto:Mark.Landin@xxxxxxxxxxxxxxxx] 
Sent: Thursday, July 22, 2004 5:03 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Suggested Registry size


One note:
 
On Windows 2000, although you can set a registry size to >128MB, you can
experience problems when the registry hits 128 MB. There will be an error in
the Event Log with ID 1000 from Userenv, with a text similar to "Windows
cannot log you on because the profile cannot be loaded. Contact your network
administrator. DETAIL - Insufficient system resources exist to complete the
requested service."
 
It has to do with Paged Pool memory issues. There is a KB article describing
the fix to this: 

 <http://support.microsoft.com/?id=312362>
http://support.microsoft.com/?id=312362

It happened to us, and this fixed it.

Apparently Windows 2003 does not suffer from this problem.


  _____  

From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Rick Mack
Sent: Thursday, July 22, 2004 4:46 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Suggested Registry size


Hi,
 
Let's not confuse the profile file/directory size with the profiles registry
size footprint. Prifiles stored in the local documents and settings folder
do NOT contribute to registry size. Only logged on sessions do that.
 
The registry can get bloated if the machine software hive gets too big
(fragmentation, registry key gowth), you have too many users (each logged on
user's ntuser.dat size gets added to the total registry size) or the users
registry profile (ntuser.dat on disk) gets too big because of registry key
growth, eg per-user file associations.
 
On win2k you don't want a software hive over about 35 MB, and individual
ntuser.dat file sizes over about 1.2-1.5 MB. If they're bigger then you've
got some work to do.
 
regards,
 
Rick

Ulrich Mack
Volante Systems Ltd
18 Heussler Terrace, Milton 4064
Queensland Australia.
Ph: +61 7 3246 7704
email: rmack@xxxxxxxxxxxxxx
web: www.volante.com.au




-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] On Behalf
Of Schneider, Chad M
Sent: Friday, 23 July 2004 3:17 AM
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Suggested Registry size


I do not have the profiles set to delete at logoff, periodically I use
delprof to clean them up.  I ran that on some servers, cleaned out a lot of
roaming profiles, but still the registry remains large.  Will it require a
reboot to fix?

  _____  

From: Angus Macdonald [mailto:Angus.Macdonald@xxxxxxxxxxxxxxxxxxx] 
Sent: Thursday, July 22, 2004 3:32 AM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Suggested Registry size


I wouldn't have thought that files in the profile would contribute to the
registry size. Isn't ntuser.dat the registry component? My profile went up
to 2.5GB once, thanks to an overzealous database admin. It took a while to
load but got there in the end.
 
Are your profiles unloading properly? If the profiles are staying on the
machine at logoff, perhaps they are staying in the registry as well.

-----Original Message-----
From: Schneider, Chad M [mailto:CMSchneider@xxxxxxxxx]
Sent: 21 July 2004 21:21
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Re: Suggested Registry size


I thought 100 would be fine, and it was....
 
Now searching and finding someone turned up some log files, which copy to
the %system32%\winnt folder, in this case, the users windows
folder.....finding several hundred K extra per user....  Typical roaming
profile is between 300-600K.  Now several in the 3+ MB.

  _____  

From: Angus Macdonald [mailto:Angus.Macdonald@xxxxxxxxxxxxxxxxxxx] 
Sent: Wednesday, July 21, 2004 3:11 PM
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Suggested Registry size


I thought I was being generous at 120MB. It never normally breaches 60MB
with 50 users.

-----Original Message-----
From: Schneider, Chad M [mailto:CMSchneider@xxxxxxxxx]
Sent: 21 July 2004 20:53
To: 'thin@xxxxxxxxxxxxx'
Subject: [THIN] Suggested Registry size



Suddenly my registry on my servers is becoming full.  It is set to 100MB.  

What is the suggested size? 

DL360, 2+ GIG physical Ram. 

Gallai'r e-bost yma gynnwys gwybodaeth gyfrinachol a/neu ddeunydd
hawlfraint. Os ydych chi'n meddwl eich bod wedi derbyn yr e-bost yma drwy
gamgymeriad rydym yn ymddiheuro am hyn; peidiwch os gwelwch yn dda â
datgelu, anfon ymlaen, printio, copïo na dosbarthu gwybodaeth yn yr e-bost
yma na gweithredu mewn unrhyw fodd drwy ddibynnu ar ei gynnwys: gwaherddir
gwneud hynny'n gyfan gwbl a gallai fod yn anghyfreithlon. Rhowch wybod i'r
anfonwr fod y neges yma wedi mynd ar goll cyn ei dileu.



Mae unrhyw safbwynt neu farn a gyflwynir yn eiddo i'r awdur ac nid ydynt o
anghenraid yn cynrychioli safbwynt neu farn Ymddiriedolaeth GIG Gogledd
Orllewin Cymru.

Gallai cynnwys yr e-bost yma gael ei ddatgelu i'r cyhoedd o dan Gôd Bod yn
Agored y GIG neu Ddeddf Rhyddid Gwybodaeth 2000. Nid oes modd gwarantu
cyfrinachedd y neges ac unrhyw ateb. 

Bydd y neges yma ac unrhyw ffeiliau cysylltiedig wedi cael eu gwirio gan
feddalwedd canfod firws cyn eu trosglwyddo. Ond rhaid i'r sawl sy'n derbyn
wirio rhag firws ei hun cyn agor unrhyw ymgysylltiad. Nid yw'r
Ymddiriedolaeth yn derbyn unrhyw gyfrifoldeb am unrhyw golled neu niwed a
allai gael ei achosi gan firws meddalwedd.


 

This e-mail may contain confidential information and/or copyright material.
If you believe that you have received this e-mail in error please accept our
apologies; please do not disclose, forward, print, copy or distribute
information in this e-mail or take any action in reliance on its contents:
to do so is strictly prohibited and may be unlawful. Please inform the
sender that this message has gone astray before deleting it.

Any views or opinions presented are to be understood as those of the author
and do not necessarily represent those of the North West Wales NHS Trust.

The contents of this e-mail may be subject to public disclosure under the
NHS Code of Openness or the Freedom of Information Act 2000. The
confidentiality of the message and any reply cannot be guaranteed.

This message and any attached files will have been checked with virus
detection software before transmission. However, recipients must carry out
their own virus checks before opening any attachment. The Trust accepts no
liability for any loss or damage, which may be caused by software viruses.

  _____  

This e-mail, including all attachments, may be confidential or privileged.
Confidentiality or privilege is not waived or lost because this email has
been sent to you in error.  If you are not the intended recipient any use,
disclosure or copying of this email is prohibited.  If you have received it
in error please notify the sender immediately by reply email and destroy all
copies of this email and any attachments.  All liability for direct and
indirect loss arising from this email and any attachments is hereby
disclaimed to the extent permitted by law.
  _____  


Other related posts: