With the AEB Cloud Device Service

The primary function of the AEB Cloud Device Service is to prepare the locally installed printers on the host system so that they are available as output devices (printers) to the application. The AEB Service Agent functions here as a service on a print server or on a separate server where the printers are installed or mapped.

You can print using the AEB Cloud Device Service as an alternative to the AEB Service Agent:

• When you print using the AEB Service Agent, a launcher installed on each client is started and initialized by the browser.
• In contrast, when you print using the AEB Cloud Device Service, a Windows service on the server keeps an agent running at all times, and this agent launches a special cloud agent instance.

Communication with the AEB Engine goes through the usual http/https connection and works internally with the AEB Service Agent.

Printing with the AEB Cloud Device Service is a good solution in Citrix environments where the AEB Service Agent is not allowed to write to temporary directories.

More information: Using the AEB Cloud Device Service

Advantages of printing with the AEB Cloud Device Service

• All printers are managed centrally and should be mapped to an AEB Engine.
• Setup and testing are generally simpler, since each printer is only configured once and no further setup is typically needed for additional workstations or users.
• This option is a good solution in Citrix environments where the AEB Service Agent is not allowed to write to temporary directories.

Disadvantages of printing with the AEB Cloud Device Service

• Printers connected locally to a workstation via USB still require local installation.