We have 8.1 still and I put together a batch file that installs silently for pushing out to our labs via SCCM. The package created by Uniprint includes the driver and popup, and runs fine with a -quiet switch. Then I use a reg file to set that queue as the default - check out HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows after you have installed it, whatever is in the Device value is what you need to set the default. I load up the ntuser.dat from the default user profile and poke it in there too, because of how our labs work, but you may not need to bother with that if it's mostly single-user machines and will be run from the user's context.
1 of 1 people found this helpful
I have managed to do this ….. but not in a traditional manner …..
What I did was to make the install in two steps …..
- Step one, copy the package from a share over to the local computer
- Step two, using the silent install options, execute the package with a script
Hope this helps
Associate Director of Computing Services
The client installer has built in command line functions that enable you to script the installation silently. Just run the installer .exe file with -quiet as an option. ###Printer_for_x64.exe -quiet format should work for you.
Hope this helps.
When I said Dashboard, I meant "Server Configuration"
we are trying to do the same thing but use DesktopCentral instead of SCCM.
Do you happen to know why you have to copy locally. I've tried via DC and manually using PSEXEC /s /e to see how it behaves as the SYSTEM account. According to the ControllerLog file it gets all the way to CheckModule portion in both instances and errors out with:
1Error: Failed to initalize PsInst32 DLL
We are moving to 8.4 from 8.1, a completely new server so we have to uninstall the old. I've had to build an Uninstall script we can push which we've finally got to work (although its a pain in Win8 because of the print subsystem changes), but we're hung up here. I'll add the method to copy, I just wish I understood the why (since it can be ran via the user remotely in non-quiet mode).
Scratch that, just confirmed successfully copying locally either via script or directly or running from PSEXEC produces the same results.
Cannot find out why, but we seem to get a failure on Win7 x64 (haven't moved on to other OS/Arch yet) with this PsInst32.dll which is in the %windir%\temp\Pharos folder... part of the pharos package extraction. Something has a hold of this file and folder as you cannot delete them. Logging out and back in does not seem to close the process/thread. Rebooting seems to.
Process Explorer (v16) doesn't seem to find any handle with either the PsInst32.dll or the folder. However, rebooting, deleting the %windir%\temp\Pharos and re-running the package seems to resolve... so I guess I'll write that check and deletion attempt into the script.