Can force a server to
generate a memory dump from the session or when a keyboard is not available or
non-standard. Command line options allow to generate a dump from command files and/or remotely when a console
session is not available (for example, IBM blade servers).
Note: Whether the complete memory or a kernel memory
dump is saved depends on the Control Panel settings.
Features:
A customer can type a
message/text (or copy it from clipboard) before forcing a memory dump. This
message is saved in a dump and a support engineer can read it after loading the dump in WinDbg.exe. This
is implemented to encourage writing the symptoms and conditions explaining why
the dump has to be
forced.
The tool can stay on
top of any window (if you need this to quickly dump the server after a repro
or during the process of an activity).
The bug check clearly
shows that the dump is manually generated.
The tool can force a
memory dump on both 32-bit and 64-bit platforms.
Before forcing a
fatal error on a server, the tool warns about potential damaging consequences:
Users are disconnected and all the data which is not saved will be lost. It asks for a confirmation.
A customer can
specify a period of time (in minutes) when to force a memory dump.