Software

>The registry keys are getting installed
Where? Remember that printer connections are stored in HKCU. How are you populating this?

As always with issues like this, you should test in a "bare bones" scenario first, so execute the installation that you have using an admin account, then log in with an ordinary user account. If that user doesn't see the printer, then you know your package isn't populating HKCU correctly. Once that all works, you can move on to testing the VDI implementation.

The software tips for Snag IT mention a deployment tool that assists in creating an MST - did you use that?

There is a CA called 'TSC_SnagItPrinterInstall' that appears to handle the driver install which runs 'SnagItPI.exe' - but as it isn't working from the vendor MSI alone, there may be something else here that needs looking at.

Previous versions required a reboot (to restart the spool service) - have you rebooted?
If that doesn't yield any results, then try it on a physical machine and see if that makes any difference.

Dunnpy

> The registry settings being populated are in HKLM
I'd wager that, post-installation, if you select to 'Add a printer', all the necessary components will be in place. Wade through the wizard and you'll get the printer appear. You'll then get the required stuff that needs to go into HKCU which you can then add to the MST. Obviously there are no advertised entry-points with a printer so you'll need to use Active Setup to trigger self-healing to get HKCU populated.

Thanks guys. It was the VDI. Tested it on a physical machine and it installed the printer driver and the printer.