This page contains answers to common questions handled by our support
staff, along with some tips and tricks that we have found useful and presented here as
questions.
Note: In these answers we will follow a few shorthand conventions for
describing user-interface procedures. Key combinations will be presented like this: Ctrl+Alt+Delete,
which means that you should press and hold down the Control key, the Alt key, and the
Delete key at the same time. Menu selections will be presented like this: File->Open,
which means that you should open the File menu, and then make the Open selection.
- Does it work with Windows XP?
- Does it work with Windows 2000?
- Does it work with Windows Server
2003?
- When changing Registry Security on a large number of keys, MRRC seems to
just sit there, why is this?
- What are the requirements for me to edit a remote registry?
- What if I need to change several keys/values scattered throughout the
remote registries?
- How do I know if an attempted change fails?
- Does the remote machine have to be on?
- Does a user have to be logged in on the remote machine?
- What if a change requires that the machine be rebooted to take effect?
- Is there a way to read information from the remote machine, and use this
information when changing the registry?
- Can I run the program from a batch file, or schedule from the AT command?
Yes! Version 3.5 and greater works with Windows
XP. It is the fastest
platform yet for running Multi-Remote Registry Change.
Yes! Version 3.1 and greater works with Windows 2000.
Yes! Version 3.6 and greater works with Windows
Server 2003.
Changing registry security on a large number of keys takes some time. By default,
MRRC doesn't show every single key change in the status window. To see what the
program is really doing, select Options->Verbose Log Entries.
NT/2000/XP: You must be an administrator on the remote machine, and the remote
machines must be running the "server" service, and Windows 2000/XP machines
must be running the Remote Registry Service (both services are installed and run by
default). For best results, the machines should be part of a domain in which
you are a member of the Domain Admins group.
95/98: The Microsoft Remote Registry Service must be installed and properly
configured for remote registry access. Basically, if you can access the Windows
95/98 registry from RegEdit on another machine, Multi-Remote Registry Change will work.
Multi-Remote Registry Change includes several options for manipulating multiple keys.
You may create a REGEDIT4 formatted file containing all of the changes, or
you can create an "Apply from" file. Either way, you can change as many
keys as you wish in a single run.
Multi-Remote Registry Change has extensive logging output, if any change fails it is
automatically added to the Operation Failure Log. If the remote computer is not
available, the failure will be added to the "Failure to Connect" log.
In addition, there is a "Retry Log" where all (logical) failed changes are
placed along with all information required to retry them. Trying them again is
as simple as a couple of mouse clicks.
Yes.
No, but you will not be able to make changes to the HKEY_CURRENT_USER key if there is
no user logged on.
Update! You can use the *EVERY_USER*
option available in nearly all operations to update the user portion of the
registry of ALL users on each machine, whether they are logged in or not.
Back to Top
Multi-Remote Registry Change includes a method for forcing the remote machine to
reboot. You have the option to send a message, set
the amount of time to wait before rebooting, force applications to close, and to
restart the system after reboot.
Back to Top
Yes! Substitutions provide a way for you to read the information from any value,
and use it in any other key, value name or value.
Back to Top
The command line options offer the opportunity to run repetitive
operations from a batch file or to schedule high bandwidth or lengthy tasks
to run overnight or on weekends when the impact on the network will be
reduced.
The feature requires you to complete two steps in advance of running the
task from the command line or as a scheduled task in Windows Task
Scheduler:
1) Create a group (Edit->Save Group) that contains the computers that
should receive the operation (remember the name of the group!).
2) Create a Quick Entry with the operation settings to be applied
(remember the name of the Quick Entry!).
Once these two items are in place they are used as arguments on the
command line of the program in this format:
MREGCHG "Group Name" "Quick Entry Name" RUN
Where:
· "Group Name" is the name of the group you created in step (1)
above (or “*ALL*” to select all computers in the computer names
list)
· "Quick Entry Name" is the name of the Quick Entry you created in
step (2) above
· RUN is an optional parameter that tells the program to really
execute. If you do not include this parameter then the computer
names will be selected and the Quick Entry will be loaded and
ready to go, but the operation WILL NOT EXECUTE.
Within about 60 seconds of when the last thread finishes, the program
will
exit on its own. Even if you did not included the RUN parameter the
program will still exit after about 60 seconds! This should give sufficient
time to check the entries to confirm they are the ones desired.
If you decide to schedule multiple consecutive tasks or run them from a
batch file, please allow ample time for the prior task to complete before
the next task begins, the program still only allows a single copy of itself
to
execute at one time. Additionally, if you are scheduling the program as a
task, it must run under the credentials of a user authorized to make the
changes and it also may be necessary to allow it to interact with the
desktop.
Back to Top
