I installed the software, selected the Printer checkbox for install.

The registry keys are getting installed, but I cannot see the printer in "Devices and Printers", nor in the application printing options.

I am testing this app on VDI. Would that be the reason?

 

Any help would be greatly appreciated.

 

Thanks!!

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

1
Is it Pooled VDI or Dedicated VDI?
How are you pushing packages to VDI? App-V/XenApp/SCCM
If it is pooled VDI then
* What is the mechanism you are using to push HKCU registries/userprofile files to the Users when they login to the VDI?
* Self-healing, ActiveSetup, Advertisedment should not be used, it happens for every login.
Answered 08/02/2015 by: jagadeish
Red Belt

Please log in to comment
1

>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.

Answered 03/13/2015 by: VBScab
Red Belt

  • Thanks for the quick response. The registry settings being populated are in HKLM. And the MslSI installs the regsitry through the regsitry table.
Please log in to comment
0
The software tips for Snag IT mention a deployment tool that assists in creating an MST - did you use that?
Answered 03/13/2015 by: dunnpy
Red Belt

  • Forgive me. I forgot to mention that the same behavior wih the vsndor MSI. And yes, I created the MST using that toolkit.
Please log in to comment
0
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
Answered 03/13/2015 by: dunnpy
Red Belt

  • I'll check the custom action thing. Yes, tried the restart of spooler service and even the reboot. Didn't work. I believe it has got to do something with the VDI. I'll update the thread with my findings and hopefully a solution on Monday.
Please log in to comment
0
> 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.
Answered 03/14/2015 by: VBScab
Red Belt

Please log in to comment
-1
Thanks guys. It was the VDI. Tested it on a physical machine and it installed the printer driver and the printer.
Answered 03/16/2015 by: mmudre
Senior White Belt

Please log in to comment
Answer this question or Comment on this question for clarity