NXPowerLite Deployment Guide

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

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. If you are deploying on a terminal server please see Installing NXPowerLite Desktop on a per-machine basis (including Terminal Server deployments)

Deployment options

Click the links below to jump to the section

Registering NXPowerLite at install time

Select which NXPowerLite features to install

Override default email integration settings

Deploy NXPowerLite with a custom optimization settings profile

Customize Microsoft Outlook Integration settings at install time

Customize NXPowerLite Office add-in at install time [v8.0.4 or later]

Registering NXPowerLite at install time

Once NXPowerLite Desktop 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. 

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, username 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" 

Select which NXPowerLite features to install

On installation by default NXPowerLite will be integrated with the following operating system and applications if present on the system:

  • Windows Explorer
  • Microsoft Outlook 
  • Microsoft PowerPoint
  • Microsoft Word
  • Microsoft Excel
  • Lotus Notes
  • Desktop Shortcut

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 NXPowerLite32Setup80_3.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:

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

Override default email integration settings

NXPowerLite can integrate with Microsoft Outlook and Lotus Notes (Outlook Express and Windows Mail available in version 7 and earlier). 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)
  • 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 emails** 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 emails** in Outlook, use the MSI property NXOLFORCE=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.

Deploy NXPowerLite with a custom optimization settings profile

The following MSI properties allow an administrator to create a custom NXPowerLite optimization settings profile. The custom profile will be created at install and be set as the user's setting profile, however, users can still change the settings by using the desktop application. Where settings are not specified or are invalid Default values will be applied.

 Currently Microsoft Office file format settings (PowerPoint, Word & Excel) can only be set to the same values. 

Profile settings

PDF-nos.png

PowerPoint-nos.png

Word-nos.png

excel-noa.png

JPEG-noa.png

Ref Property name Type Valid values Default value
1 NXDTSETTINGSPROFILENAME=n String Characters up to 255 characters in length Custom
2 NXDTJPEGQUALITYPDF=n Integer(DWORD) 1-9 7
3 NXDTALLOWRESIZINGPDF=[0|1] Boolean 0(false) or 1(true) 1
4 NXDTSCREENWIDTHPDF=w NXDTSCREENHEIGHTPDF=h Integer (DWORD) See below 1200 x 800 
5 NXDTREMOVEHIDDENCONTENTPDF=[0|1] Boolean 0(false) or 1(true) 1
6 NXDTSUBSETEMBEDDEDFONTSPDF=[0|1] Boolean 0(false) or 1(true) 0
7,13,18 NXDTJPEGQUALITYOFFICE=n Integer(DWORD) 1-9 7
8,14,19 NXDTALLOWRESIZINGOFFICE=[0|1] Boolean 0(false) or 1(true) 1
9,15,20 NXDTSCREENWIDTHOFFICE=w NXDTSCREENHEIGHTOFFICE=h Integer (DWORD) See below 1200 x 800 
10, 16, 21  NXDTALLOWCROPPINGOFFICE=[0|1] Boolean 0(false) or 1(true) 1
11, 17, 22 NXDTREMOVEHIDDENCONTENTOFFICE=[0|1] Boolean 0(false) or 1(true) 1
23 NXDTJPEGQUALITYJPEG=n Integer(DWORD) 1-9 7
24 NXDTALLOWRESIZINGJPEG=[0|1] Boolean 0(false) or 1(true) 0
25 NXDTSCREENWIDTHJPEG=w NXDTSCREENHEIGHTJPEG=h Integer (DWORD) See below 1200 x 800 
26 NXDTPRESERVEMETADATAJPEG=[0|1] Boolean 0(false) or 1(true) 1

Screen width and height valid values:

  • 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

 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 Default setting for that specific setting when the application starts. In the case of Default 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 Default settings will be used.

Customize Microsoft Outlook Integration settings at install time

It is possible to customize the default email settings at install time. Users will always be able to change the settings once deployed.

Outlook_settings-nos.pngEnhanced_outlook.png

Ref  Property name Type Valid values Default value
A NXOLMINEMAILSIZE=(size in KB) Integer 0-No max 500
B NXOLNOASKFLATTEN=[0|1] Boolean 0(false) or 1(true) 1
C NXOLNOZIP=[0|1] Boolean 0(false) or 1(true) 1
D NXOLMINZIPSIZE=(size in KB) Integer  0-No max 1000
E NXOLMINZIPREDUCTION=(percentage) Integer  0-100 10
F NXOLNOASKZIP=[0|1] Boolean 0(false) or 1(true) 1
G NXOLDISABLEENHANCEDOUTLOOK=[0|1] Boolean 0(false) or 1(true) 0

 

Customize NXPowerLite Office add-in at install time
[v8.0.4 or later]

It is possible to customize some of the attributes of the NXPowerLite Add-in when deploying NXPowerLite. By default, the NXPowerLite group will be installed after the Font group on the Home tab of PowerPoint, Word and Excel.

PowerPointNXPAddin.png

Working with standard elements

Ref Description Property Name Valid values
1 Customize tab on which NXPowerlite appears
(Inserted in Microsoft standard tabs only)

NXDTOFFICERIBBONTAB="idMso=TAB-Id"

See below
2 Use large icon NXDTOFFICERIBBONLARGEICON=1 1
3 Customize button label  NXDTOFFICEBUTTONLABEL="String"  Any characters
4 Customize Screen tip NXDTOFFICEBUTTONSCREENTIP="String" Any characters
5 Customize Super tip NXDTOFFICEBUTTONSUPERTIP="String" Any characters
6 Customize group position
(Inserted after the specified group in Microsoft standard tabs only)

NXDTOFFICERIBBONINSERTAFTERGROUP="insertAfterMso=GROUP-Id"

 

See below

Microsoft TAB-Id and GROUP-Id's can be found by downloading the Office Fluent User Interface Control Identifiers.  

Working with custom elements

When working with customised ribbon, group and tab layouts or you wish to customize some XML attributes use the following properties.

If you intend to use the following properties, you have to set the namespace first.

Description Property Name Examples

Set the namespace for custom elements

 

NXDTOFFICERIBBONNAMESPACE="NAMESPACE"

 

NAMESPACE value could be xmlns:nx=""http://neuxpower.com/customuixml""
Add NXPowerLite to a custom group NXDTOFFICERIBBONGROUP="idQ=CUSTOM-GROUP-Id"

 CUSTOM-GROUP-Id value could be "nx:CustomGroup" 

Insert NXPowerLite into a custom Tab NXDTOFFICERIBBONTAB="idQ=TAB-Id"

CUSTOM-GROUP-Id value could be "nx:CustomTab" 

Insert after custom group NXDTOFFICERIBBONINSERTAFTERGROUP="insertAfterQ=GROUP-Id"

CUSTOM-GROUP-Id value could be "nx:CustomGroup" 

Additional XML attributes to add to the NXPowerLite <button/> element  NXDTOFFICECUSTOMXML="CUSTOMXMLATTRIBUTE" CUSTOMXMLATTRIBUTE could be insertAfterQ=""nx:Label1""
Neuxpower Support Article Logo
Have more questions? Submit a request