HP Web Jetadmin - Supported Printer Features in HP Web Jetadmin

4
TROUBLESHOOTING PLUG-INS
During device discoveries, Web Jetadmin attempts to determine the model name of a device. It then
maps the model name to the appropriate device plug-in (either discreet or UPI) to display a proper
bitmap and offer the desired amount of configuration items. Typically the interrogation of model name
involves SNMP, but for FutureSmart devices Web Jetadmin may use web services (WS*). This means
that WS Discovery will need to be enabled on FutureSmart devices in order for Web Jetadmin to use
the appropriate device plug-ins.
If Web Jetadmin either fails to map a device to the correct plug-in or does not contain a matching
plug-in (such as with discreet plug-ins), only very limited support is provided through a generic plug-in.
For example, on a FutureSmart device, if Web Jetadmin fails to be able to map it to the correct plug-
in, only generic support is available which uses SNMP to interrogate the device. Since very few items
are defined to use SNMP for FutureSmart devices in Web Jetadmin, very little information is provided.
Notice that the picture is that of a very old Laserjet II model, the front panel display claims <Not
Supported>, only the Tray gauges are present as they are defined to use SNMP. The Config tab offers
very few configuration categories. This is a sure sign of generic support. For some reason Web
Jetadmin was not able to match the model name to the correct plug-in. It might be credentials related.
It could be a newer device and an older version of Web Jetadmin that doesn’t have a discreet plug-
in. In the case of UPIs, if the device was discovered initially with an older version of Web Jetadmin
that didn’t have a UPI, and Web Jetadmin was subsequently upgraded, the older plug-in is still being
used.
When this scenario occurs, perform the following steps to attempt to force Web Jetadmin to use the
correct device plug-in:
1. Right-click on the device in the device list and select Refresh Selection.
2. Right-click on the device in the device list and select Refresh Selection (Full).
3. Right-click on the device in the device list and select Delete. Choose Delete again, then
rediscover the device.
4. Run a new full discovery from the navigation tree.
5. Make sure WS Discovery is enabled using EWS.
6. Make sure Web Jetadmin has the proper credentials either for the device or in the global
credential store to be able to read all pertinent information.
Most of the time this will be enough to force Web Jetadmin to assign the proper device plug-in to the
device. In very rare cases, the device may need to be flashed again with firmware from a USB stick,
especially if it was an early evaluation unit with suspect firmware.
In the case of FutureSmart devices where Web Jetadmin is using WS* to retrieve most of the
information, an EWS password set on the device can drastically limit the information that Web
Jetadmin can display as even retrieving information without proper credentials is blocked. For
example, if after right-clicking the device and selecting Refresh Selection (Full), the device improves to