Table of Contents
Advertisement
To recover a large number of machines, use the right-click menu option
Discover at the Microsoft network domain or Microsoft Windows Network
level.
Recovering the Name Provider database
If the database has been accidentally deleted or corrupted, or the machine has
suffered a hardware failure preventing the recovery of the up-to-date
database, it is possible to regenerate the database from the information stored
on each Windows 3.1 machine.
Once a computer name has been assigned to a Windows 3.1 machine, every
time the Management Agent on that machine starts, it communicates with the
Name Provider to inform the Management Agent of the machine's currently
assigned name.
If the database is empty, or some records are missing, the Name Provider
automatically adds these back to the database when the Windows 3.1 machine
is restarted and contacts the machine. This means that, for a while, the Name
Provider expanded view in the Management Console will not display all of
your Windows 3.1 workstations, and will only be accurate after all
Windows 3.1 machines are restarted.
If the database is lost and you do not intend to add any new Windows 3.1
machines, you don't need to take further action because the database is rebuilt
automatically.
You have two options to add other Windows 3.1 machines:
• Ensure you restart all your existing Windows 3.1 machines that have been
allocated computer names. This lets the database be rebuilt correctly.
• Change the default partial name that is assigned to new machines. The
default name is the first ten (or fewer) characters of the domain name. This
is stored in the NAMEPROV.INI file in WINDOWS\NTME on each
Windows 3.1 machine, under the NP_PARTIAL key. Existing machines
can override this setting by specifying their own value in the
NP_PARTIAL key of NAMEPROV.INI in their Windows directory. Any
machine using this option that has yet to receive a computer name will also
need to be changed.
È
IMPORTANT: You must ensure that the new partial name you select is
unique throughout your network. Otherwise, duplicate names are
generated, causing communication failures within the Management
Edition software.
Advanced Configuration and Troubleshooting
Administrator's Guide
269
Advertisement
Table of Contents
