Users do not receive the correct default printer within ICA sessions. Instead of the default printer being set to the autocreated one which corresponds to the default on the client device, another printer within the session is set as the default. Additionally, changing the default printer within a session to the autocreated printer that corresponds to the default on the client device, is not being retained for future sessions.
To allow the default printer on the client device to correctly carry into ICA sessions when using the session printers policy, set the Choose client’s default printer option to Set default printer to the client’s main printer.
When multiple policies containing session printers are involved, the policy with the highest priority (lowest number) wins with regard to this default printer setting.
The problem occurs when a session printer’s policy is enabled in the management console and the Choose client’s default printer option is set to Do not adjust the user’s default printer.
The default printer selection behavior is controlled in the following two places:
The Default To Main Client Printer (selected by default) setting located under Client Settings for the server's ICA listener. It is important to remember that this setting is per-server and can be overridden by policies set in the management console.
The Choose client's default printer setting under the Session printers node in a policy configured in the management console. By default, the Do not adjust the user’s default printer setting is enabled.
Configuring the Choose client's default printer setting to Do not adjust the user’s default printer overrides the Default To Main Client Printer setting on the server's ICA listener. This causes each user to receive the incorrect default printer within their ICA session unless they manually select a non-autocreated/non-autoconnected printer (such as a network printer or local printer on the server) as their default, if this is desired. Otherwise, the default printer is selected from the pool of printers configured for the user on the client device at random every time a session is established on the server.
Note: Policies can have various scopes depending on what they are filtered on (such as servers, users, client name, client IP address, or access control). Take care when configuring multiple filters and/or multiple policies.