When I dug into this issue here at ASU, it was a function of the network configurations. On your 'non domain' machine, go into the network settings and add 'auto append suffix' information for your domain. I.E. for me, the foriegn laptop didn't have a auto append for asu.edu so the installer couldn't find it way back to the web service hosting the install files. Hope it is that easy!
The installer appears to be getting the error back from the Windows API call "AddPrinter".
Is there anything logged to the Windows Event Viewer?
Everytime the installer is run and fails, the Event Viewer shows only 1 error:
Faulting application name: spoolsv.exe, version: 6.1.7601.17514, time stamp: 0x4ce7aa85
Faulting module name: HPBMINI.DLL, version: 188.8.131.52, time stamp: 0x400d90c9
Exception code: 0xc0000005
Fault offset: 0x0000173f
Faulting process id: 0x5e8
Faulting application start time: 0x01cc3d6b85bdd566
Faulting application path: C:\Windows\System32\spoolsv.exe
Faulting module path: C:\WINDOWS\SYSTEM32\SPOOL\DRIVERS\W32X86\3\HPBMINI.DLL
Report Id: 9fb48d85-a96a-11e0-862a-0019b96b603f
Interesting. This DLL appears to have known issues in the past: http://support.microsoft.com/kb/946394. The article mentions a RPC failure, which is exactly the error we are receiving back from ::AddPrinter.
I would recommend searching a "fresh" machine for instances of the HPBMINI.DLL file. Note the version of these instance.
Then connect to a network printer as per your original description above. Search for the HPBMINI.DLL instances again. Did any of the instances change versions or did a new instance with a newer version appear?
Were you able to collect any information about the HPBMINI.dll versions on the machine?
I apologize for the late response.
We ended up solving the issue that we were having and now we have working installers for our printers for Windows 7 systems. Initially we figured out that if we installed the HP Laserjet 9050 PS drivers (downloaded from the HP website) before trying to run the Pharos Installer, then it would work. From this we gathered that the installer seemed to not be installing the driver for the printer. On the installer it stated that it was installing the HP Laserjet 9050 PS drivers and succeeded but we figured that this was not the case based on our experiences.
It turns out that our installers were set to use specific HP Laserjet 9050 drivers. We set the installers and the printers to use Universal HP drivers and it solved our issue.
My guess would be that the error was being triggered by the print processor on the driver. If you find a need to use the specific driver in the future, try changing the print processor to WinPrint RAW prior to building a package.