A supported Windows 11 Enterprise multi-session pool uses version 22H2 or later and FSLogix. A user’s Universal Print preferences roam, but machine printer properties such as drivers and ports do not. How should the administrator handle this distinction?

✓ Correct answer

• Keep the required machine printer configuration on each host and roam the supported user preferences.

Universal Print user preferences can roam in the supported AVD configuration. Printer properties such as driver and port information are machine settings and do not roam with the user. Option explanations: A. Copy the vendor driver binaries into each user profile as a substitute for host printer configuration.: Copying binaries into profiles is not the documented way to configure host printer properties. B. Assume FSLogix must roam all machine printer properties and replace the whole profile.: The observed distinction is expected; replacing a healthy profile does not turn machine properties into user settings. C. Keep the required machine printer configuration on each host and roam the supported user preferences.: This respects the machine-versus-user boundary while preserving the roaming settings that are supported. D. Disable profile persistence so the printer settings become machine-wide.: Disabling persistence removes useful user state without configuring the required host properties. Sources: Printing on AVD using Universal Print — https://learn.microsoft.com/universal-print/fundamentals/universal-print-avd

Read the source reference