We created a fascade to the uniprint package page, end users will never see this page directly. This is where we have links to the Mac popup or the PC Installer. I posted the link below to give you an idea.
We do the same at SMU, we host an internal site that we modify for our environment and include step by step instructions for our students to download. Would like to know how you built your Mac package for multiple printers, though.. we are still building one for each queue.
We build a "department" queue that is setup as a compatible queue to all of their printers. Then we package either the Mac built in generic.ppd or genericPCL.ppd as the driver. This seems to work well for areas that do not need maximum functionality from their drivers. For these areas we do build printer specific queues.
We also create our own web page with links to installers for laptop users:
Because of our large Mac population, we don't use the Pharos map system. If we were to, we would simply link to it from our primary page above.
I feel your pain with regard to creating Mac installers. We extract the popup bits and integrate them into our own installers too. The installers are pretty simple once you embrace CUPS. Printers are added with lpdamin.
A sample lpadmin command to build a printer with a popup URI:
/usr/sbin/lpadmin -p 'Mc9Hall_ColorLaser_PrintQ' -v popup://10.72.18.11/MI901_Canon2880_PrintQ -P /Library/Printers/PPDs/Contents/Resources/en.lproj/CNRC288X1_SAIC.PPD.gz -E -D 'Mc9Hall_ColorLaser_PrintQ' -o printer-is-shared=false
We found that managing large numbers of desktop Mac computers and their printers/profiles with package installers under uniprint was a huge chore, so we developed an in-house system for delivering printer sets that works within our inventory system. It uses lpadmin commands too. We're looking into using Active directory to deliver printers to Windows machines (not installers.) Users don't have admin rights on the Windows machines and things need to 'just work.'
We create a separate Mac Packages HTML file using the standard packages.asp file as a template. We also modify the default.asp page to indicate that there are Mac packages.
- You could try to copy the mac packages to "C:\Inetpub\wwwroot\Uniprint" location
- Modify the manifest.xml in "C:\Inetpub\wwwroot\Uniprint" location to include the mac packages (if you are confident in xml - this is another work around)
The manifest can be partially updated to include the Mac Package using Pharos Administrator.
The following steps need to be done to avoid the Manifest being overwritten whenever a package is built/rebuilt:
1. Create a Package in Administrator called 'Mac Package'
2. Don't select any queues.
3. In Description field: DO NOT REBUILD
4. Build the package - this creates an entry in the Database, and also in the manifest. (The database entry is important to stop the manifest being overwritten)
5. On the IIS server, locate the files: MacPackage_for_W2K.exe; MacPackage_for_x64.exe; MacPackage_for_Lte.exe. These can be deleted.
In the manifest, three new <package> sections will be added for the new package, each with : <name>Mac Package</name>
Delete the first two, but retain the final one , identified by the line <environment>Lte</environment> - as below
<lastbuild>15 Nov 2011 16:15</lastbuild>
<supportedenvironments>W2K x64 Lte</supportedenvironments>
This entry in the manifest ensures the package displays on the Packages page of the website.
The <fileurl> line needs to be updated as follows:
1. replace //SERVERNAME with the IIS Server name hosting the Uniprint website.
2. replace 'MacPackage_for_Lte.exe' with the name of the package to be run on the Mac client.
3. ensure that the package to be run on the Mac client is in the Uniprint website location along with the other packages - usually C:\Inetpub\wwwroot\Uniprint on IIS Server
If there are any problems, this can be tested (on a windows client) by copying Notepad.exe into the Uniprint website location with the packages and update the <fileurl> to call notepad.exe - eg:
Note: if the package is rebuilt from the Administrator, the file name to run will be overwritten in the Manifest. That is the reason, suggested to add the description to the Package inside the Administrator as 'DO NOT REBUILD'.
Hope this helps...
Thanks a ton for the very descriptive information. I followed your instructions and I now see a MAC Package. Here is my XML entry as it is now.
<description>DO NOT REBUILD!</description>
<lastbuild>14 Nov 2011 17:13</lastbuild>
A few questions:
- Am I using the correct MAC file ? When I click on the link on the Package website it gives me a page not found. I have put the "Popup.dmg" file in the C:\inetpub\wwwroot\uniprint directories, of course I'm trying this from a MAC.
- When I go through the instructions and add the printers to my MAC it doesn't prompt me for authentication information.
- Is there anything more I have to do in the Administrator to make this work? Queue's, printers, groups...etc? As far as making this part work, I already have accounting and the windows side working?
Thanks again. AJ
FYI, with some help from a co-worker I got the website to work and ask to download or run the *.dmg package when I click on MAC Packages.
The solution is to add the .dmp MIME Type to your IIS server. IIS does not know what to do with a .dmg file so we had to add the following.
I still need to know which MAC file to use. Notify.dmg or Popup.dmg.
I have an old Pharos Tech Note which describes how to build a custom installer for multiple Pharos print queues on Mac OS X. I wish they would put a newer updated tech note on the website. I got the document from someone in our IT department, so I don't know
where they got it. This document tells exactly how to modify the Popup Client Installer, put your drivers and queue names in the Configuration file.
We have also used Absolute Manage/Install Ease to make custom installers of all types, and I think that would be a good option to construct a full custom installer.
Automatic_Popup_Installer.pdf 280.1 KB
Here is a link to the latest instructions posted: