I would expect a seperate XML file with these mappings which you could update if things would have been changed to a point that automatic handling fails...
Is there also another view for checking the mappings?
Loading User Information from Channel 9
Something went wrong getting user information from Channel 9
Loading User Information from MSDN
Something went wrong getting user information from MSDN
Loading Visual Studio Achievements
Something went wrong getting the Visual Studio Achievements
I think you confuse two things:
One thing is the ability to print a document. This is something that PDF also has, not allowing printing. With XPS you can allow only certain people to print.
Second is the ability to send an encrypted job to the printer. The printer should then show a dialog prompting the user to authenticate. This is something that is currently implemented by many printer manufacturers, and is done in the printer driver.
My guess is that the first scenario is handled by the XPS viewer.
The second scenario should be handled by the printer, as with XPS encryption/authentication isn't a driver feature anymore.
My 2 cts
Good luck with your application. If I were you I would contact several printer manufacturers and ask if they could support your use case.
The printer would need a new interpreter for XPS.
However, the print path in Vista should also have optimized conversions to Postscript/PCL, probably in the GDI to EMF conversion area, so you should get better print-out. I wonder however if this will be a Vista-only feature for older drivers... (they are backporting the new print-path to XP/2003, but also these optimalisations?)
Vista would ship XPS drivers out of the box for printers that are going to be released/updated around the time of Vista release, but that's up to the printer manufacturer. In the corporate market customers generally update the printer drivers with the latest ones from the manufacturer. In the consumer market it helps to have a printer working out-of-the-box. Depending on the consumer's technical skills they could still decide to update to the ones from the manufacturer CD/website/windows update.
There are restrictions on the size of the drivers you may inbox in Windows, and you need to share source code, so that Microsoft can also compile your driver against the latest driver development kit at any time and do regression tests.