Developers guide
Windows Management Instrumentation (WMI) Com-
Quick Reference Guide    17
Registry
Windows Management Instrumentation (WMI) Compatible
Datalogic OPOS Service Objects provide WMI-compatible Remote Management for 
certain scanners when properly configured. For those scanners that support this data 
gathering capability, the Service Objects must be configured via registry settings to 
provide scanner data to the WMI data store. There are two registry settings that must be 
active to pull data from the scanner and provide it to the WMI data store: 
“CheckIHSOnClaim” and “WMIOnClaim” must both be set = 1. When these settings 
are active, each time the scanner is “claimed” by an OPOS application, the service will 
query the scanner and send the information to the WMI data store. Any WMI-data 
gathering application will then have access to the data. As noted in the registry section 
below, these settings are defaulted to “active” upon installation. Note that this process 
may have a small impact upon system performance.
The data provided to the WMI database follows the format as specified in the UPOS 
specification, Appendix I, “Systems Management Information”, which is modeled on 
the Common Information Model (CIM) from the DMTF. This standard provides a 
means of Remote Management of Datalogic scanner/scales under the Windows 
Management Instrumentation process.
OPOS Registry
Datalogic OPOS Service Objects use the Windows registry for configuration of the 
OPOS software. When the OPOS package is installed, the installer creates registry 
entries under HKEY_LOCAL_MACHINE\SOFTWARE\OLEforRetail\ServiceOPOS; 
Scale and Scanner.
 Under each UPOS category, there are named entries for each 
device. Under each name, there are some user-configurable entries that control the 
operation of the OPOS Service Objects. 
Scanner
Under SCANNER in the registry, there are a number of named entities: HandScanner, 
MagellanSC, QS6000, and so forth. Note that some of these are duplicates that have 
been maintained for legacy purposes: for example, “
HandScanner” and 
“
USBHHScanner” refer to the same device (a handheld scanner running OEM USB 
interface); “MagellanSC” is the same as “SCRS232Scanner”; “TableScanner” 
and “
USBScanner” are equivalent; QS6000 and RS232Scanner are equivalent, 
QSLScanner is a unique entry. The following screen shots cover the important user-
configurable registry settings for each category of scanner.
Changing items in the registry does not change corresponding items in the 
scanner. For example, baud rate can be changed in the RS232Scanner regis-
try, but the baud rate in the scanner must be changed via programming label 
to match the registry entry, or the Service Object will be unable to communi-
cate to the scanner.










