More on Registry...

Load order must be factored when attempting to apply policies through reg hacks from within the logon script.  Policies are loaded before the logon script runs so reg hacks may not take effect until the next logon.  RunLogonScriptSync is another.  For that, see the FAQ:

Topic: W2k+ - Keep the Window visible on login?

If you want to see/manipulate registry permissions, then use RegEdt32.

If you want to export portions of the registry for later importation, both RegEdt32 and RegEdit will do it but in different formats.  RegEdt32 saves in binary format while RegEdit saves in ASCII (see note).  They are not interchangable.

Note: RegEdit for Win2k saves in unicode format and therefor is not compatible with older (Win9x) RegEdit.  That means that if you export a .REG file from Win2k, you will not be able to merge it into Win9x systems with RegEdit.

Tools and Resources
http://www.microsoft.com/windows2000/techinfo/reskit/en-us/w2rkbook/regentry.asp

http://www.microsoft.com/technet/prodtechnol/winntas/tips/winntmag/inreg.asp

http://www.winguides.com/registry

http://www.sysinternals.com/ntw2k/source/regmon.shtml

The Windows 2000 Professional Resource Kit includes a registry reference (regentry.chm) as well.  Also, a good understanding of how policies are applied in the registry can be had by taking apart the .ADM files.

<small>[ 22 June 2002, 17:25: Message edited by: LLigetfa ]</small>

Edited by kdyer (2004-06-30 03:02 PM)
_________________________
Give a man a fish and he will be back for more. Slap him with a fish and he will go away forever.