Services Required for Using the Device Information Retrieval Function
This section describes the services required for using the device information retrieval function and the installation destination of the device information retrieval function for different usage environments.
Services Required for the Device Information Retrieval Function
If you want to use the device information retrieval function, you need the following services and environments.
Operating System Services
Remote Procedure (RPC)
TCP/IP NetBIOS Helper Service
Workstation
All the above services must be installed in the operating system. A setting other than disabled must be selected for the [Startup type] setting of each service.
Protocols
UDP or TCP (IPv4 or IPv6)
Supported Device Connection Configurations
When connected to a network: TCP/IP
When connected locally (32-bit): USB
Installing the Device Information Retrieval Function in Different Usage Environments
For the device information retrieval function, the device information retrieval path and Canon Driver Information Assist Service installation destination etc. vary according to the following factors.
Type of print queue (local printer or network printer)
Connection method of the device (network connection (LPR etc.) or local connection (USB))
Server environment (terminal server or Virtual Apps/Presentation Server)
The items required for the Canon Driver Information Assist Service installation destination etc. for each combination of the above factors are shown below.
For a local printer:
When connected to a network: device information can be retrieved with the driver alone
When connected locally*: Canon Driver Information Assist Service must be installed on the same computer
* For local connections, you may not be able to use the device information retrieval function, depending on the device and environment you are using.
For a network printer:
When connected to a shared server: Canon Driver Information Assist Service must be installed on the print server
When connected by IPP: device information can be retrieved with the driver alone (when via IIS, configuration information cannot be retrieved)