Just need it for one project?  Click here for Rental Options.

 

Lost Registration Code?  Click here.

Selects the hive for the operation. The hive can be any one of the following:

HKEY_LOCAL_MACHINE
HKEY_USERS
HKEY_CURRENT_USER
HKEY_CLASSES_ROOT
HKEY_CURRENT_CONFIG
*EVERY_USER*

Hives other than HKEY_LOCAL_MACHINE and HKEY_USERS are automatically mapped to their real location in the registry. All hives other than HKEY_LOCAL_MACHINE and HKEY_USERS are in fact subkeys of these two. The other hives that show up in REGEDIT and REGEDT32 are located as shown:

HKEY_CURRENT_USER:

Windows NT/2000: Because Windows NT/2000 can have many "Current Users" (services that log on locally, Terminal Server Clients, etc), Multi-Remote Registry Change uses a complex algorithm to attempt to discover the correct current user of the attached terminal on the remote machine. If it believes it has successfully discovered the correct user, it will map HKEY_CURRENT_USER to the correct S-1* entry under HKEY_USERS.

Windows 9x: Mapped to the first S-1* entry under HKEY_USERS.

HKEY_CURRENT_CONFIG is HKEY_LOCAL_MACHINE\System\CurrentControlSet\Hardware\Profiles\Current

HKEY_CLASSES_ROOT is HKEY_LOCAL_MACHINE\Software\Classes


*EVERY_USER* Where logical, *EVERY_USER* is available as a Hive. Selecting *EVERY_USER* causes the program to perform the selected operation on every user hive on each selected remote machine. If you use roaming profiles, or have many people that share a single machine in shifts, this will allow you to run the operation once and be assured of actually changing the HKEY_CURRENT_USER profile for every user, not just those that happen to be logged in at the time.

Copyright © 1998-2006 Eytcheson Software
All rights reserved.
Last Updated:  Saturday, April 29, 2000