PDF Architect

The ONLY Customizable PDF Editor

How do I deploy PDF Architect to a large number of machines?

 

How do I deploy PDF Architect to a large number of machines?

In this document, we describe the deployment process of PDF Architect.

General info about PDF Architect packaging and installation properties/features

PDF Architect is a modular PDF solution. An administrator can deploy the application as predefined set of modules gathered into packages. The modules for future deployment should be selected in accordance with the package license key you obtained. The standard package contains startup, create, edit,convert and insert modules. The Pro packet contains all modules except for OCR.

PDF Architect View module (Startup package) has several properties, which modify application options at the installation stage:

Property Type Description
PRODKEY String Product key (all users)
CREATE_DESKTOP_SHORTCUT Switch(1/0) Creates a shortcut for the application on the desktop. (All Users)
ENABLE_AUTOMATIC_UPDATES Switch(1/0) Enables automatic updates of the application (All Users)
SET_AS_DEFAULT_APPLICATION Switch(1/0) Sets the application as the default application to open .pdf files. (Current User)
APPLICATION_LANGUAGE String Specifies the application languages that will be installed (All Users)
HIBERNATE_ON_CLOSE Switch(1/0) Disables the hibernate on close feature (All Users)

The APPLICATION_LANGUAGE parameter is set by assigning language in accordance with the required language. Language codes available:

English en
French fr
German de
Spanish es
Italian it
Japanese ja
Russian ru
Portuguese pt

Please note that the PDF Architect Startup package is the only package that accepts the properties listed above. Rest of packages relies on it. Most detailed (with all the properties are set) msiexec command line may look like:

msiexec /i “C:\Temp\pdf-architectX-startup-X.X.msi” PRODKEY=”XXXXX-XXXXX-XXXXX-XXXXX-XXXXX” CREATE_DESKTOP_SHORTCUT=”1” CREATE_QUICK_LAUNCH_SHORTCUT=”1” ENABLE_AUTOMATIC_UPDATES="1" SET_AS_DEFAULT_APPLICATION=”1” APPLICATION_LANGUAGE="en" /quiet

And in case you created an MSI transform (see the next chapter) the command line may look like: msiexec /i “pdf-architectX-startup-X.X.msi” /quiet TRANSFORMS="name_of_transform_file.mst"

Besides, PDF Architect View (startup-package) module enables you to use the following features:

Feature Description
main_feature Installs the main part of the application (mandatory)
viewer_firefox_feature Installs the PDF Architect Viewer in the Firefox browser
viewer_ie_feature Installs the PDF Architect Viewer in IE
viewer_preview_handler_feature Installs the PDF Architect Viewer in Explorer and Microsoft Outlook
shortcuts_feature Creates a shortcut for the application on the desktop as well as in the current user's QuickLaunch directory. (All Users)

msiexec command line may look like: msiexec /i pdf-architectX-startup-X.X.msi /quiet ADDLOCAL=viewer_firefox_feature,viewer_ie_feature,shortcuts_feature

All the features described above can be used along with PDF Architect properties. For example: msiexec /i “pdf-architectX-startup-X.X.msi” /q CREATE_DESKTOP_SHORTCUT=”1” CREATE_QUICK_LAUNCH_SHORTCUT=”1” ENABLE_AUTOMATIC_UPDATES="1" SET_AS_DEFAULT_APPLICATION=”1” APPLICATION_LANGUAGE="en" ADDLOCAL=viewer_firefox_feature,viewer_ie_feature,shortcuts_feature,viewer_preview_handler_feature

PDF Architect Create module has several features, which modify application options at the installation stage:

Feature Description
plugin_feature Installs the main module part (mandatory)
word_feature Installs the PDF Architect Plug-in in MS Word
excel_feature Installs the PDF Architect Plug-in in MS Excel
powerpoint_feature Installs the PDF Architect Plug-in in MS PowerPoint
publisher_feature Installs the PDF Architect Plug-in in MS Publisher
outlook_feature Installs the PDF Architect Plug-in in MS Outlook
ie_feature Installs the PDF Architect Plug-in in Internet Explorer
firefox_feature Installs the PDF Architect Plug-in in Firefox
context_menu_feature Makes the conversion features available in the Windows Explorer context menu

msiexec command line may look like:

msiexec /i pdf-architect-create-module-x.x.msi /quiet ADDLOCAL=plugin_feature,word_feature,excel_feature,powerpoint_feature

(plugin_feature allways should be added)

Using Orca.exe from Windows SDK to create an MSI transform (MST) for the PDF Architect package

MST file allows incorporating all the installation properties into single file so you don’t need to put them into command line directly. If you prefer to set up the properties through command line you can skip this chapter. Launch the Orca.exe and select the PDF Architect startup package. All the settings make sense for this package only.

From the Transform menu select New Transform.

Select the Property table and add the PRODKEY property.

Edit the rest of properties to make the transform, which meets your requirements. In the picture an automatic updates have been turned on and an application language has been set to English.

From the Transform menu select Generate Transform and save the transform to file.

Using System Center Configuration Manager 2012 (SCCM) to deploy the PDF Architect package

In the Software Library press Create Application:

Process of creating an application is very straightforward. For the moment you should only choose an MSI-file on a network share (basic msiexec switches will be added automatically).

Please note, that all the content of a folder, you have chosen, will be imported into Content Library. Press Next until you see a successful completion screen.

Open the properties of an application you have just created; Application properties window will appear. In the Programs tab, edit theInstallation program string. Add TRANSFORMS="name_of_transform_file.mst" at the end, if you created the transform. Add direct properties (e.g. PRODKEY=" XXXXX-XXXXX-XXXXX-XXXXX-XXXXX” ENABLE_AUTOMATIC_UPDATES="1" APPLICATION_LANGUAGE="en") otherwise.

Now deploy the application using the deploy button from the menu ribbon.

The process of deployment, as is the case with an application creation, looks very simple. Select a content destination, type of action (Install/Uninstall), purpose (Availabe/Required), schedule and other options if you need them. Proceed to the end of deployment wizard to see a successful completion screen.

Now repeat the creation and deployment steps to all the packages which correspond to your license.