I want to distribute PDF-XChange across a network using a Group Policy.
Distributing Software via a Group Policy requires some planning and deploying PDF-XChange is no different. The following is an overview of the steps required to deploy an MSI installer, for PDF-XChange Pro, via Group Policy.
MSI installers, both x86 and x64, are available for the following PDF XChange Products:
Choose a Method of Deployment.
There are two main ways you can distribute software using a Group Policy, by assigning it or publishing it:
·Assigning Software You can assign a program distribution to users or computers. If you assign the program to a user, it is installed when the user logs on to the computer. When the user first runs the program, the installation is completed. If you assign the program to a computer, it is installed when the computer starts, and is available to all users who log on to the computer.
·Publishing Software You can publish a program distribution to users. When the user logs on to the computer, the published program is displayed in the Add or Remove Programs dialog box, and it can be installed from there.
Create a Distribution Point
To distribute the software through a GPO it must be made available on a Windows Server called a ‘Publishing Server’ in this context. This is called a ‘distribution point’.
Log on to the server as an administrator.
Create a shared network folder where you will put the Microsoft Installer package (.msi file) that you want to distribute.
Set permissions on the share to allow access to the distribution package.
Copy or install the package to the distribution point. For example, to distribute PDF-XChange Editor, copy the files EditorV9.x86.msi and/or EditorV9.x64.msi to the distribution point. Note that these installers are architecture discrete. You will need to manage your target systems accordingly. Depending on your Domain infrastructure this could be a simple as having an OU (Organizational Unit) for each class of target machine.
Create a Group Policy Object
To create a Group Policy Object (GPO) to distribute the software package, follow these steps:
From within the Active Directory Group Policy Management Consol.
Right click the OU to which you wish to apply the policy and "Create a GPO in this domain, and link it here..."
Give it name:
Right click the link to your new policy and select "Edit"
The Policy opens in the Group Policy Management Editor. It is here that we actually define what the policy will do.
Under Computer Configuration, then Policies, expand Software Settings.
Right-click Software installation, point to New, and then click Package.
In the Open dialog box, type or browse for the full UNC (Universal Naming Convention) path of the installer package that you want. It must be a location accessible to your users. For example, \\file server\share\file name.msi. Make sure that you use the UNC path of the shared installer package.
On choosing a valid MSI installer package you will be prompted to assign the package, or to select "Advanced" option:
If you are deploying an unlicensed instance with all defaults this is all that is required here, however if you wish to customize the installation and/or provide a license key during install then you will need to use the "Advanced" option here to pass and MST Transform file.
You should now have a functional policy to deliver the package next appropriate GPUpdate and for most devices this will be done only during machine start up.
PDF XChange MSI Options
Each of the PDF XChange MSI installers have a list of options and switches that can be applied when installing the software. These include choosing features, passing serial keys and user information, the level of user interaction during the install and more.
It is always prudent to check these for the build you are installing. To get the switches and options for your package start it in a GUI environment and on the first screen click the Help button and you can read there or print the options and know they are correct for the installer build you are using.
Note! The command line switches cannot be applied directly when Publishing or Assigning software through a GPO. You must create and apply a transform.