The PPP Suite is broken into two main portions; Admin Tools used by an administrator to migrate printers,
move printers, define new printers, etc, and the Client application that runs on all end-user machines and
peforms whatever changes may be needed as a result.
Admin Tools - PPPAdmin.exe
These allow you to configure the various applications in the PPP Suite. To use the administrative tools, you need read/write access to the directory you are running them from, local admin rights to the computer
running them, and often network admin rights for many of the capabilities of the tools.
Note: The PPPAdmin tools are not intended for multi-user access. Multiple people making changes at the
same time will generally cause each other's changes to be lost, giving preference to the very last person
who made a change. Even if the changes are in different areas or applications, many datafiles are related
to each other and are read and wrote as a single unit. Excessive use by multiple people at once may cause
datafiles to become corrupt entirely.
End-user application - PPPClient.exe
This application is run by every user on the network and is responsible for implementing the
configurations made in the admin tools. There are many ways to configure this application to run and they
are described in the "Client installation" section. It can be setup to run once and exit when a user logs in, or
to stay running indefinately to monitor for changes. In some cases the Client may need more rights than the logged in user has, and in these situations, there are several techniques available to setup the Client
with appropriate access. See the "Client Installation" section for more information.
Which application do I want to use?
Novell Users
I have Novell printers (Queue, NDPS, iPrint) that do not have the correct settings when they get installed, and I want to configure them automatically - PPP Profiler
I need to configure settings on a printer but preserve already existing settings that are different on each end user machine (such as a user identification number that the printer requires for tracking purposes) - PPP Profiler
I am currently using Novell printers, but we are moving to windows print servers -- PPP Migrator
I am currently using Novell printers, but would like to start using Direct TCP/IP printers instead - PPP Migrator (and PPP Installer. See PPP Migrator's guidep for more information)
Active Directory Users (or Windows Networking only)
I have Direct TCP/IP printers installed on end-user machines but want to consolidate them all onto one or more print servers - PPP Mover (using special gathering options. See PPP Mover's guide for more information)
I have windows print servers but wish to move to Direct TCP/IP printers while still managing them centrally. - PPP Installer
I am replacing an existing print server with a new similar one - PPP Mover
I am replacing an existing print server with an incompatible server (such as 32bit to 64bit) - PPP Mover
I want to reorganize printers on existing servers, and/or rename printers on the same server and automatically map end-users to the new names/locations - PPP Mover
I want to push printers, and default settings profiles to end-user machines - PPP Installer
I want users to be able to install printers themselves from a searchable list (including Direct TCP/IP printers) with drivers and settings - PPP Installer
I have printers that do not have drivers compatible with my print server and all the end-users connecting to it and need to specify specific drivers for different operating systems (for example, a new 64bit server may not have drivers available for an older printer, or the 64bit driver may not be compatible with the 32bit driver, etc) - PPP Installer
I do not have Active Directory, but I wish to push printers out to users based on IP address, computer name, etc - PPP Installer
Quickstart
Download the latest version of the PPP Suite from
http://www.printerpropertiespro.com/downloads/PPP.exe
The archive can extracted to any path you wish. It can be moved at a later time, if needed, simply by
copying the files.
Start the program "PPPAdmin.exe"
Choose the component you are interested in, and start making configurations
Once you have tried some sample configurations, you can do a quick test of the client by simply executing
PPPClient.exe directly. Since some features of the Client require local administrative rights, if UAC is
enabled on your system, you may want to use "Run as Administrator" just to ensure desired behavior during
your tests.
Installation Guide
Choosing where to put the PPP Suite's files
The PPP Suite does not require any setup. Simply put the files in a location accessible
to all users. A few techniques are described below.
File Share
The most common technique is to use a single basic file share where everyone has read access, and
administrators have read/write access. This can be on a clustered resource, or any network device that is
compatible with Windows file sharing.
The easiest arrangement is a resource that can be accessed by any end-user using the same UNC address
(\\server\share) or mapped drive letter (t:\), but it is still possible even if the resource can't be
universally referenced by end-users.
Note: If you intend to run the client as a service, you must give read rights to "Everyone", or to the
Active Directory group called "Domain Computers" and the Built-in user "Network service". It is also
difficult to ensure drive mappings for a service so only UNC style addresses should be used.
i) Using a private working/testing area
This common variation uses two file shares. The first file share is an admin only file share. All use of
the administrative tools, and modifications to configurations occur from this share (it can even be a
local directory on a specific computer that isn't shared at all). This provides a working area, where an
admin can make changes to configurations and test them out before 'publishing' the changes to the file
share that end-users use. There is a built-in tool on the [Global] tab of "Client Settings" found in any
of the administrative tools labelled "Distribute Client". This can be used to specify location(s) you
wish to copy all the information needed by clients to, and to initiate the update. You may also use any
sort of file copying or replication techniques to simply copy the PPP directory and all sub directories to
the 'published' share that end-users use.
ii) Multiple file servers
This technique can be useful when you have several regional file servers that will host PPP Client for
end-users in their area. This allows you to use one location as your master location where you
make changes using the admin tools, do any testing, etc, and then 'publish' the settings to all your
regional file servers. There is a built-in tool on the [Global] tab of "Client Settings" found in any of
the administrative tools labelled "Distribute Client". This can be used to specify location(s) you wish
to copy all the information needed by clients to, and to initiate the update to the servers. You may also
use any sort of file copying or replication techniques to simply copy the PPP directory and all sub
directories to the 'published' shares that end-users use.
Note: When using multiple file servers, if end-users cannot all refer to their server by the same drive
letter, or UNC name, you may require additional work when setting up the PPP Client to run on end-user
machines, since different workstations will need different settings in order to point to the correct
server. Also, if the client will be setup to run as a service, drive mappings are generally not
available, so UNC names would be needed.
HTTP Server
This feature allows you to host the datafiles on an internal or external HTTP Server. If you do not
already have an HTTP server available, you will need to set one up which is outside the scope of this
document. The PPP Suite does not require any special configurations or settings and all common HTTP
servers are currently supported (as long as you can access them using FTP to update the PPP data files
being hosted).
To set this up, you will need a local copy of the application where you run the administrative tools from,
for configuring/changing settings to the various applications. Once you have completed your changes, you
publish the settings using the built-in tool on the [Global] tab of "Client Settings" found in any of the
administrative tools labelled "Distribute Client". You simply need to setup a target location specifying
the ftp server such as "FTP://server.com/path/". You will be prompted for a username and password to
connect with. The username and password are stored in a private location for the current user, on that
workstation only (in an encrypted format). If you attempt to publish to the server at a later time from
another machine, or user account, you will be prompted for the login information. You can not simply copy
files up to the server using other techniques. The files put on the server are compressed and have
special header information added for accuracy and efficiency.
Note: Some FTP servers do not support accurate file modification dates. As a result, you may see files
created in your local directory ending in ".ftp". These are special flag files that help the software
know which files are up to date on the server and which are not. If you delete the local files, the
software will assume files are out of date and update the server (even if it didn't need to).
In order for end-users to run the client, they will need PPPClient.exe in a local directory, or on a
fileserver that can be executed specifying the HTTP address as a commandline parameter such as
\\myserver\myshare\PPPClient.exe "workingdirectory=http://www.ourhttpserver.com/ppp/"
Specifying an http address for a working directory automatically implies the commandline parameter
"WorkOffline". For more information, see the command-line options section.
Coming soon... Full online solution for end-users to manually/automatically have printers installed and configured from
browsable web-pages. Contact Printer Properties Pro for more information.
Does the PPP Client need local administrative rights?
Below is a short list of common activities in the
various applications that can help you determine if the Client needs admin rights. If it does, and your end-users do not have sufficient rights, there are several techniques for installation that can help.
PPP Profiler: (Novell)
Configuring per-user iPrint printers does not require local admin rights
All other printer types require local admin rights for full functionality
PPP Migrator: (Novell to Windows)
Migrating Novell printers to AD per-user printers does not require administrative rights.
Deleting anything except per-user iPrint printers after the migration does require administrative rights.
Migrating captured printer ports does not require administrative rights.
Migrating to Direct TCP/IP printers requires administrative rights.
Migrating to per-workstation AD printers requires administrative rights.
PPP Mover: (Windows to Windows)
Moving any printer to AD per-user printer connections does not require administrative rights.
Moving any printer to a per-workstation printer connection requires administrative rights.
Deleting a printer after a move requires administrative rights if its a workstation printer (locally
installed printer with a network printer for the port, or an IP address for the port)
Deleting a printer after a move requires administrative rights if its a per-workstation printer
connection (a command that causes windows to create a per-user printer connection for every user that logs
in)
PPP Installer: (Push printers to end-users)
Pushing a per-user printer connections do not require administrative rights
Pushing direct TCP/IP printers requires administrative rights.
Deleting per-workstation printers, or direct TCP/IP printers requires administrative rights.
Client Installation/Launching the Client
A few simple techniques are described below. There are many possibilities and if you need assistance we would be happy to find a technique that works for you.
Launching from an Active Directory user logon-script
This is a common technique, but has become much more difficult with the introduction of
UAC in windows Vista and up. However, if all end-user are going to be local administrators, you are are
not using UAC, or the features you are using do not require local adminsitrator rights, then this is an
easy option.
To do this, create an Active Directory "Group Policy Object", edit the policy and add a "Logon" script under "User Configuration" -> "Policies" -> "Windows Settings" -> "Scripts". Create a batch file to use for the script (see examples in the
<PPP Suite directory>\tools\scripts\ directory), link the group policy to a computer, user, container, or domain, etc, and then
right-click on the linked policy and select "Enforced". You may wish to apply filters to the policy or to the batch file, to prevent the script from running on special computers like domain controllers, and print servers, etc. With default settings though, the Client wouldn't interfere with any operations on these systems.
This technique will run the client in the security context of the user logging in. If the Client requires local admin rights, and the user logging in does not have local admin rights, this may cause some functionality of the Client to be lost.
Launching from an Active Directory computer startup-script (AD Group Policy)
This technique is a very simple way to setup the client to run with local admin rights. The Client runs on a hidden desktop as the system user (much like a service) and uses a
seperate executable to provide an interface to the end-user when needed. This seperate executable runs in
the context of the user, reducing security risks of users interacting with applications running under the
system account.
To do this, create an Active Directory "Group Policy Object", edit the policy and add a "Startup" script under "Computer Configuration" -> "Policies" -> "Windows Settings" -> "Scripts". Create a batch file to use for the script (see examples in the
<PPP Suite directory>\tools\scripts\ directory), link the group policy to a computer, user, container, or domain, etc, and then right-click on the linked policy and select "Enforced". You may wish to apply filters to the policy or to the batch file, to prevent the script from running on special computers like domain controllers, and print servers, etc. With default settings though, the Client wouldn't interfere with any operations on these systems.
Everytime a computer starts up, PPPClient will be run (even before anyone logs in). The
client will continue running (even if users log in and out) until the computer is shutdown. If for any
reason PPPClient is closed or terminated (including commandline options that can close the client after
certain intervals), PPPClient could not be started again without restarting the computer.
Running as a service
This technique sets the Client to be launched by a service on the end-user's machine. This is very
similar to using a computer startup script to launch the client, but doesn't require Active Directory, and
allows the Client to be restarted without restarting the system. In this mode you can also just launch PPPClient.exe as a regular user, and it will detect the service and have the service launch the Client instead. This allows a restricted user to indirectly start the Client with elevated rights.
For more information see the readme.txt file in <PPP Suite directory>\Tools\PPPClientLauncher\.
Updating the application
When new updates are available the Admin tool will automatically let you know when you start it (or if you have disabled the notices, you can manually check for updates using "Check For Updates..." in the "Help" menu).
When you update through the Admin tools, a backup will automatically be made for the key datafiles and binaries in the event of any problem.
If you experience any issues with the automated updates, or prefer to update software manually, you can always download the newest version of the PPP Suite from http://www.printerpropertiespro.com/downloads/PPP.exe. This is a self extracting archive that you can simply overwrite your existing files with. We always recommend backing up first.
Several different Client installation techniques are possible, some involve copying binaries to end-user machines and running them from there using a 'WorkingDirectory="path"' parameter to point the end-users to the datafiles. When updating the binaries in the "WorkingDirectory", end-user machines will automatically obtain new versions of the binaries and use them. This makes the update process significantly easier in these instances.
PPP Migrator
Starting Printer Migrator
Printer Migrator is included in the default download of the PPP suite. The download comes with a default demo license for 3 printers. If you have a license for Migrator, simply copy the license into the same directory where you extract PPP and it will be found by the application.
After downloading and extracting PPP, run PPPAdmin.exe to start Printer Migrator. Select Printer Migrator from the following menu.
The Printer Migrator application will open, and will connect to your eDirectory and Active Directory trees automatically. eDirectory objects are shown in the left pane, Active Directory on the right. The queue for all printer migrations is shown across the bottom of the window.
Quick Steps to Migrate a Printer from Novell eDirectory to Microsoft Active Directory
1.
Install and start PPP Printer Migrator.
2.
Select the printer agent(s) you wish to migrate from eDirectory in the left pane.
3.
Select the destination Active Directory server in the right pane.
Note: If migrating to a Microsoft Cluster, follow these instructions when selecting the AD server.
4.
Click the red arrow between the panes add the printers to the migration queue.
5.
Start the queue by clicking the Start button above and to the left of the queue window.
6.
Run PPPClient on user workstations to remap installed printers to their new location.
Sets the default context for eDirectory and Active Directory when Printer Migrator opens. Does not affect printer migration in any way.
•
Refresh Active Directory Printers
Used to refresh the Active Directory printer listing, particularly useful after new printer migrations.
PPPClient_Options - Settings
Global Tab
•
Show Client Window on Workstations
Shows the log window to the end-user when running PPPClient. This is used mainly for troubleshooting.
•
Use Short Printer Names When Possible
This setting is for Migrator / Mover / Converter Only. If checked the printers will be installed on the end user machine in "short" format instead of the full server name.
With it checked: printer on server
Without it checked: printer on server.subdomain.domain.com
•
Start-up Delay
Time that PPPClient waits after being started before it begins to configure printers and make other changes.
•
Wait Time After Printer Changes
When a new printer is installed, PPPClient will notice the change and run again to configure the new printer. Adjust this time as necessary to allow the printer to finish installing completely before PPPClient attempts to make changes.
•
Check for Changes
PPPClient will check for changes to the configuration files and will apply the new changes. For example: If you have the it set to 10 minutes and the change "use short printer names when possible" setting, PPPClient will know the change has been made in 10 minutes and start using short names.
* The default of "0" means the PPPClient will run at login and exit.
•
Distribute PPPClient Package
Use this tool to send PPPClient and all necessary files to remote locations so they can run the client from a local server.
Migrator Tab
•
Pause Clients from Migrating Printers
Makes the client stop migrating end-user printers to new printer locations.
•
Delete converted printers on end user workstations
Tells the client to delete the old, end-user printer after migrating to new printer.
•
Change default printer after migrating existing default printer
Tells the client to make new Active Directory printer default, after migrating old eDirectory default printer.
•
Convert iPrint printers to associated Active Directory Printer
When turned off, the iPrint printers will not be Migrated and deleted from end-user workstations.
•
Migrate Captured Printer Ports to New Printers
If LPT ports are associated with the source printer they will be remapped to the new target printer.
•
Prevent Gatherer from gathering network addresses
Tells the PPPGatherer.exe to not ping the local network. This pinging helps resolve IPX print server addresses to IP addresses. Only used for migrating legacy Netware queue objects.
•
Prevent Gatherer from gathering queue printer drivers
Tells PPPGatherer.exe to not gather the drivers from end user machines. You will need to right click on the printers in the migration queue and select "Specify driver" if this option is not used in PPPGatherer.exe. Also PPP Migrator will not know the driver model of the queue to help you in report mode to see the driver models of the printers. This option only applies to migrating legacy Netware queue printers.
•
Show gatherer window on workstation
If this option is checked PPPClient.exe will show a log window when it is ran. Very annoying to the help desk but usefull in troubleshooting. You can also simply use the command line option nominimize to show the log window when running PPPClient.exe. \\server\folder\pppclient.exe nominimize
•
When Converting printer on end user workstations create:
Global Printers or User Printers - If the user running pppclient has rights a global printer will be installed else a user printer will be installed. Global printer note: Global printers make it so every user that logs into the computer will get the printer.
Global Printers Only - PPPClient will attempt to install a global printer and show error in log if it fails. Global printer note: Global printers make it so every user that logs into the computer will get the printer.
User Printers Only - PPPClient will only install user printers.
•
Distribute PPP Client
Use this tool to send PPPClient and all necessary files to remote locations so they can run the client from a local server.
Profiler, Mover, Converter, Tabs - See associated product user guide for explanation of option in these tabs.
Admin Options
•
Automatically Prompt When User Intervention is Required
Stops queue and prompts user when intervention is required. When turned on, queue continues with other printers and adds a notice in the queue window.
•
Include 9x Drivers in Migrations
Copies 9x drivers from eDirectory to Active Directory in migrations.
•
Include NT Drivers in Migrations
Copies NT drivers from eDirectory to Active Directory in migrations.
•
Include 2000 Drivers in Migrations
Copies 2000 drivers from eDirectory to Active Directory in migrations (requires 2000 driver association in eDirectory).
•
Include XP Drivers in Migrations
Copies XP drivers from eDirectory to Active Directory during migration (requires XP driver association in eDirectory).
•
ONly include the newest driver available
Only the newest driver available in eDirectory will be used to install the new printer on the target server. Use XP else 2000.
•
Require New Drivers - Do not use any driver from eDirectory, I will specify new driver
Used to specify new drivers for all printers being migrated. When migration starts, Printer Migrator will retrieve all existing driver assoctions from NDPS and list them in the queue. The queue will pause and wait for you to select the new driver before continuing. Double click a printer in the queue to select the new driver, and you will be given the option to apply the new driver to all other printers of the same model.
For example: If you are migrating 200 HP 5si printers, and they will all get the same new driver, simply start the queue with this option selected. After the printer drivers show up in the queue, double click one of the 5si printers and select the new driver. Click Next and select the option to apply it to all other printers of the same type.
Options for Printers in the Migration Queue
•
Change Windows Printer Name
Click the printer name, or right click the printer line in the queue to access this option. Renames the printer during migration to Active Directory.
•
Choose a different driver
Right click this printer in the queue or in the left pane to access this option. Allows you to associate a different driver for Active Directory than was previously used in eDirectory.
•
Cancel Incomplete Operation
Right click the printer in the queue to access this option. Stops any incomplete migration operations.
•
Retry Incomplete Operation
Right click the printer in the queue to access this option. Retries the current migration operation.
•
Find Migrated/Mapped Printer in Novell Tree
Right click the printer in the right pane to access this option. Allows you to find a previously migrated printer in the left pane.
Symbol Legend
Green Check - Successfully migrated printer.
Green Circle - Printer currently being migrated.
Grey Circle - Printer queued for migration.
Red Circle with Exclamation - Printer failed to migrate. Hover over printer or see printer queue for details.
Additional Features
•
Start/Stop the migrator queue - using the Stop/Start button in the lower left, you can stop and start the migrator queue at any time.
•
Unmigrate/Unmap a printer - after a printer has been migrated, you can right-click the new printer in the right pane and unmigrate it. The printer will be deleted from Active Directory and will not be migrated on any further end-user workstations.
PPPGatherer.exe - Documentation (used only for migrating legacy Netware queue objects)
Find more information at the Printer Migrator Knowledgebase.
