NXPowerLite Deployment Guide

System requirements for deployment

NXPowerLite is compatible with PCs running Microsoft® Windows® (Windows® Vista onwards).

Deploying NXPowerLite Desktop 7

NXPowerLite Desktop 7 is available as a Windows® Installer .MSI file. This makes it easy to install automatically. For example, NXPowerLite Desktop 7 can be deployed via Group Policy.

Once NXPowerLite Desktop 7 has been installed on a machine, it must be registered in order to prevent it running in “evaluation”mode. The software can be registered on either a per-user or per-machine basis.

The latest .MSI file for the x86 architecture (32-bit) can be downloaded from www.neuxpower.com/latest/msi32

The latest .MSI file for the x64 architecture (64-bit) can be downloaded from www.neuxpower.com/latest/msi64

 Deploying NXPowerLite in bulk only applies to the Windows version. Mac OS X versions of NXPowerLite cannot currently be bulk deployed.

Registering at install time

It is possible to register NXPowerLite Desktop Edition on a per-machine basis at the point of installation.

This is achieved using the MSI properties NXNAME and NXCODE, as in the following example (assuming “Filename” “Some User” and “XXXXX-XXXXX-XXXXX-XXXXX-XXXXX” are replaced with the filename of the current NXPowerLite installer, user name and registration code):

Filename.msi NXNAME="Some User" NXCODE="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

For more information about Windows® Installer options, visit the following page on Microsoft’s MSDN website: http://msdn2.microsoft.com/En-US/library/aa367988.aspx

Where the registration details are stored

Registration details for NXPowerLite are stored under one of the following Registry keys, depending on whether NXPowerLite is being registered on a per-user or per-machine basis:

HKEY_CURRENT_USER\Software\Neuxpower\NXPowerLite\7.0

HKEY_LOCAL_MACHINE\Software\Neuxpower\NXPowerLite\7.0

or on 64-bit systems:

HKEY_LOCAL_MACHINE\Software\Wow6432Node\Neuxpower\NXPowerLite\7.0

Under those keys, NXPowerLite looks for the string values “Registered Name” and “Registered Code”. For example, the following Registry script can be used to register NXPowerLite Desktop Edition on a per-machine basis:

REGEDIT4

[HKEY_LOCAL_MACHINE\Software\Neuxpower\NXPowerLite\7.0]

"Registered Name"="Some User"

"Registered Code"="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"

Selectively installing features

MSI properties can be specified at installation time to select the features to be installed. For example, the following msiexec command line will silently install everything except PowerPoint, Word and Excel integration:

msiexec /i NXPowerLite32Setup70_0.msi /quiet ADDLOCAL=ALL REMOVE=PowerPointIntFeature, WordIntFeature,ExcelIntFeature

The REMOVE property is a comma-separated list of identifiers of the features that should not be installed. The current feature identifiers for NXPowerLite are:

  • OutlookIntFeature (integration with Microsoft® Outlook®)
  • OutlookExpressIntFeature (integration with Microsoft® Outlook® Express / Windows® Mail)
  • LotusNotesIntFeature (integration with Lotus® Notes®)
  • ExplorerIntFeature (“NXPowerLite” submenu in Windows Explorer’s context menu)
  • PowerPointIntFeature (“Optimize with NXPowerLite” button in Microsoft® PowerPoint®)
  • WordIntFeature (“Optimize with NXPowerLite” button in Microsoft® Word®)
  • ExcelIntFeature (“Optimize with NXPowerLite” button in Microsoft® Excel®)
  • DesktopShortcut  [added in 7.1.14] (Controls creation of the desktop shortcut icon) [added in 7.1.14] 

Email integration options

NXPowerLite can integrate* with Microsoft® Outlook® and Outlook® Express, Lotus® Notes® and Windows® Mail. Once integrated, NXPowerLite can automatically optimize and zip mail attachments, reducing the size of the sender’s sent mail and the recipient’s Inbox.

It is possible to force different default behaviours in NXPowerLite’s email integration when deploying using the MSI file. For example, an administrator may want to force NXPowerLite’s integration to be enabled for all users’ new emails, while still allowing the user to disable per email.

The following MSI properties can be used to modify the behaviour of NXPowerLite’s email integration:

  • NXOLFORCE (Microsoft® Outlook®)
  • NXOEFORCE (Microsoft® Outlook® Express / Windows® Mail)
  • NXLNFORCE (Lotus® Notes®)

Each one of the above can have three possible values – 0, 1 and 2. These options are detailed below:

Option 0 or no setting: NXPowerLite remembers the last setting (default)

If a user disables NXPowerLite email integration, it will remain disabled for all new emails** until the user enables it. NXPowerLite email integration will then remain enabled until changed again. This behaviour applies in the same or next session.

Option 1: NXPowerLite email integration always initially ENABLED

All new emails will have NXPowerLite email integration enabled regardless of any previous setting. Users can disable on a per-email basis.

e.g. To force NXPowerLite to be enabled for all new mails** in Outlook®, use the MSI property NXOLFORCE=1.

At the beginning of every email client session, NXPowerLite email integration is enabled.

Option 2: NXPowerLite email integration always initially DISABLED

All new emails will have NXPowerLite email integration disabled regardless of any previous setting. Users can enable on a per-email basis.

e.g. To force NXPowerLite to be disabled for all new mails** in Outlook® Express, use the MSI property NXOEFORCE=2.

At the beginning of every email client session, NXPowerLite email integration is disabled.

** Note: Due to the way Lotus® Notes® is designed, it is not possible to set the integration per new email, it can only be implemented per session. However, the state of NXPowerLite can be changed during the session.

Overriding NXPowerLite’s default settings

The following MSI properties allow an administrator to override NXPowerLite’s default settings during deployment. However, these settings only change the default behaviour; users can override all of these defaults by changing the NXPowerLite relevant tab in the settings dialog.

Note for settings where there is a constrained range of valid numbers, if the specified setting is invalid then the application will revert back to the screen setting for that specific setting when the application starts. In the case of screen width and height – where both values have to be both valid and in a valid pair, both numbers must be correct and in a valid combination otherwise the screen setting defaults will be used.

Desktop Application

NXOPTIMIZEDCOPY=1

In NXPowerLite version 5 and earlier, optimizing a file would create an optimized copy of the file under a new name - for example, "Filename (NXPowerLite).ppt". The default behaviour in NXPowerLite versions 6 & 7 is different - it replaces each optimized file with the optimized version, and creates a backup copy of the original file. This change in behaviour can be overridden by setting NXOPTIMIZEDCOPY=1, which causes NXPowerLite to behave as version 5 did, creating optimized copies of files.

NXDTJPEGQUALITYPDF=n
NXDTJPEGQUALITYOFFICE=n
NXDTJPEGQUALITYJPEG=n

Minimum NXPowerLite version: 7.1.8

Type: integer (DWORD)

Valid values for n: 1-9 inclusive, where 9 is a high quality image with minimal reduction and 1 is the smallest, lowest quality image.

Screen setting default: 7 for each

These settings allow a default to be set for the JPEG optimization quality for PDF, Office and JPEG files respectively. In the NXPowerLite settings dialog, these can be edited on the optimize profile tab, using the JPEG Quality edit control for each document type.

NXDTALLOWRESIZINGPDF=[0|1]
NXDTALLOWRESIZINGOFFICE
=[0|1]
NXDTALLOWRESIZINGJPEG
=[0|1]

Minimum NXPowerLite version: 7.1.8

Type: Boolean

Valid values: 0 (false, turning setting off) or 1 (true, turning setting on)

Screen setting default: 1 (Office and PDF), 0 (JPEG)

This setting allows a default to be set for the ‘Resize images’ checkboxes on the settings dialog optimize profile tab.

NXDTSCREENWIDTHPDF=w
NXDTSCREENHEIGHTPDF=h

NXDTSCREENWIDTHOFFICE=w
NXDTSCREENHEIGHTOFFICE=h

NXDTSCREENWIDTHJPEG=w
NXDTSCREENHEIGHTJPEG=h

Minimum NXPowerLite version: 7.1.8

Type: integer (DWORD)

Valid values and combinations (w x h):

  • 3840 x 2160
  • 2880 x 1800
  • 2560 x 1600
  • 2560 x 1440
  • 2560 x 1080
  • 1920 x 1200
  • 1920 x 1080
  • 1680 x 1050
  • 1600 x 1200
  • 1440 x 900
  • 1280 x 1024
  • 1280 x 800
  • 1024 x 768
  • 800 x 600
  • 600 x 480
  • 480 x 480

Screen setting default:

PDF & Office: width 1024 x height 768
JPEG: width 1600 x height 1200

These change the default settings for the screen height and width, as set in the NXPowerLite settings dialog on the optimize profile tab dropdown controls.

Note that for these must be set in pairs, so that the height and width make a valid pair as detailed in the table above, e.g.:

Installer.msi NXDTSCREENWIDTHPDF=2880 NXDTSCREENHEIGHTPDF=1800

NXDTSUBSETEMBEDDEDFONTSPDF=[0|1]

Minimum NXPowerLite version: 7.1.8

Type: Boolean

Valid values: 0 (false, turning setting off) or 1 (true, turning setting on)

Screen setting default: 0 (setting is off).

This allows a default to be specified for the subset embedded fonts feature in PDF files, equivalent to the checkbox on the settings dialog optimize profile tab. In testing we have found this can increase the reduction of files where a font optimization can be achieved, however, due to a bug in the third-party library that we use some files can be corrupted. As such we have turned the option off by default, but you can override this should you wish to do so. We would advise careful checking of your optimized files if you do this prior to deleting the originals.

NXDTALLOWCROPPINGOFFICE=[0|1]

Minimum NXPowerLite version: 7.1.8

Type: Boolean

Valid values: 0 (false, turning setting off) or 1 (true, turning setting on)

Screen setting default: 1 (setting is on).

This sets a default value for the ‘Delete cropped areas of pictures’ option on the settings dialog optimize profile tab.

NXDTREMOVEHIDDENCONTENTPDF=[0|1]

Minimum NXPowerLite version: 7.1.8

Type: Boolean

Valid values: 0 (false, turning setting off) or 1 (true, turning setting on)

Screen setting default: 1 (setting is on).

This sets a default for the ‘Delete private application data’ checkbox on the Optimize Profile tab of the settings dialog.

NXDTREMOVEHIDDENCONTENTOFFICE=[0|1]

Minimum NXPowerLite version: 7.1.8

Type: Boolean

Valid values: 0 (false, turning setting off) or 1 (true, turning setting on)

Screen setting default: 1 (setting is on).

This sets a default for the ‘Flatten embedded objects’ checkbox on the Optimize Profile tab of the settings dialog.

NXDTPRESERVEMETADATAJPEG=[0|1]

Minimum NXPowerLite version: 7.1.8

Type: Boolean

Valid values: 0 (false, which removes JPEG metadata) or 1 (true, leaving JPEG metadata intact)

Screen setting default: 1 (setting is on).

This sets a default for the ‘Remove EXIF data’ checkbox on the Optimize Profile tab of the settings dialog.

Microsoft® Outlook® Integration

NXOLNOASKFLATTEN=1

Changes the default setting of the “Ask me when flattening embedded objects” option in Outlook from “on” to “off”.

When sending an email attachment containing embedded objects, if NXPowerLite is configured with a profile that flattens such objects (e.g. "Screen"), users will by default be asked whether they want to flatten them or not. Setting NXOLNOASKFLATTEN=1 means that this prompt will be suppressed by default.

NXOLMINEMAILSIZE=(size in KB)

Changes the default setting of the “Ignore emails below” option under “Optimize settings” in Outlook from 500 KB to the specified value in KB.

NXPowerLite will not optimize attachments if the total size of all attachments is less than 500 KB. Setting NXOLMINEMAILSIZE=N changes this default threshold to N KB. For example, NXOLMINEMAILSIZE=1024 changes the minimum size to 1 MB, or NXOLMINEMAILSIZE=0 means that attachments will always be optimized regardless of size.

NXOLNOZIP=1

Changes the default setting of the “Enable zip compression” option in Outlook from “on” to “off”.

When sending an email message with large attachments, NXPowerLite will try to compress the attachments into a single zip file. Setting NXOLNOZIP=1 means that this behaviour will be disabled by default.

NXOLMINZIPSIZE=(size in KB)

Changes the default setting of the “Ignore emails below” option under “Zip settings” in Outlook from 4,000 KB to the specified value in KB.

If zip compression is enabled and the total size of email attachments, after optimization, is greater than 4,000 KB, NXPowerLite will try to compress the attachments into a single zip file. Setting NXOLMINZIPSIZE=N changes this threshold to N KB. For example, NXOLMINZIPSIZE=1024 changes the minimum size to 1 MB, or NXOLMINZIPSIZE=0 means that NXPowerLite will always try to zip attachments, regardless of size.

NXOLMINZIPREDUCTION=(percentage)

Changes the default setting of the “Minimum reduction” option under “Zip settings” in Outlook from 10% to the specified percentage.

If zip compression of attachments is enabled and NXPowerLite cannot reduce the size of email attachments by more than 10% by zipping, it will not zip the attachments. Setting NXOLMINZIPREDUCTION=N changes this threshold to N%. For example, NXOLMINZIPREDUCTION=20 means that attachments won't be zipped unless they compress by more than 20%, or NXOLMINZIPREDUCTION=0 means that attachments will always be zipped if zip compression is enabled, even if they don't compress at all.

NXOLNOASKZIP=1

Changes the default setting of the “Ask me before sending zip attachments” option under “Zip settings” in Outlook from “on” to “off”.

If zip compression of attachments is enabled and the criteria described above are met, NXPowerLite will prompt the user before zipping attachments. Setting NXOLNOASKZIP=1 means that this behaviour will be disabled by default

NXOLDISABLEENHANCEDOUTLOOK=1

Minimum NXPowerLite version: 7.1.5

The key 'Disable Enhanced Outlook Integration' disables NXPowerLite’s ability to reduce emails in a user’s outlook inbox.

By default, users can reduce existing emails in Outlook by right-clicking and selecting the NXPowerLite option to optimize. Setting NXOLDISABLEENHANCEDOUTLOOK =1 means that this behaviour will be disabled for all users. The feature is still installed, and can be re-enabled by switching the setting to 0.

 

 

Neuxpower Support Article Logo
Have more questions? Submit a request