Release Notes
SmartSystems Server v4.50
Version Information .................................................................................................... 2
Installation .................................................................................................................. 2
2.1. System Requirements for installing the SmartSystems Server ......................... 2
2.2. Before Installing Version 4.50 ............................................................................. 3
2.3. To Install:.............................................................................................................. 4
3. SmartSystems Management License ......................................................................... 4
4. Supported Hardware .................................................................................................. 6
5. New Functionality Available in SmartSystems Server Version 4.50 ......................... 6
5.1. Installation ............................................................................................................... 6
5.1.1. Installation Diagnostic ......................................................................................... 6
5.1.2. Use of local system account ................................................................................ 6
5.1.3. Reporting Services ............................................................................................... 6
5.2. Performance ............................................................................................................ 6
5.2.1. Asset Messages processing ................................................................................. 6
5.2.2. Device connections .............................................................................................. 6
5.2.3. Tracking of available memory ............................................................................. 6
5.3. Properties Viewer.................................................................................................... 7
5.4. Managing SmartSystems Users .............................................................................. 7
5.5. Bundle Wizard enhancements ................................................................................ 7
5.6. Peripherals Panel and Support for Bluetooth PR2/PR3 printers .......................... 7
5.7. Support for Wi-Fi PR2/PR3 printers ....................................................................... 7
5.8. Support for PC23/PC43, and PM43 printers .......................................................... 8
6. Best Practices .............................................................................................................. 9
6.1. One-Step Provisioning............................................................................................. 9
6.2. Device Discovery ................................................................................................... 10
7. Issues Fixed In This Version ...................................................................................... 10
8. Known Issues in This Version ................................................................................... 12
1.
2.
1. Version Information
Release notes describe the updates available in SmartSystems Server 4.50.
Prior to Installing, review section 2.2.
Please reference the online help for complete user information. The online help is accessible
from the SmartSystems Server by selecting Help from the menu.
Release Version
Version Date
SmartSystems Server
05/18/2012
4.50.00.0193
Release
4.02.06.0646
Date Available
9/13/2011
4.01.05.0406
1/17/2011
3.51.04.1225
1/18/2010
3.50.04.1120
9/17/2009
3.42.03.0667
3.41.03.0659
3.22.02.0403
3.21.02.0394
3.20.00.0341
3.11.01.0094
3.10.00.0076
3.00.00.0051
2.20
2.01
2.00
4/14/2009
10/29/2008
3/27/2008
1/22/2008
11/19/2007
6/15/2007
12/21/2006
10/26/2006
5/2/2006
10/19/2005
5/27/2005
2. Installation
2.1.
System Requirements for installing the SmartSystems Server
Processor:
Memory / RAM:
Disk Space:
Operating
System:
Intermec Technologies

2 GHz is recommended for optimum performance

2 GB is required







60 MB is required for SmartSystems Server
Additional space required for pre-requisite software.
Windows XP Pro with SP3 and all related updates
Windows Server 2003 R2 or SP2, 32-bit only
Windows Server 2008 Enterprise
Windows Server 2008 R2 with SP1
Windows 7 Professional, Enterprise and Ultimate, 32-bit or 64-bit
o 64-bit Windows 7 will not support Cisco AP discovery.
o Windows 7 requires SQL Server 2008 R2 (full version or Express)
Review http://msdn.microsoft.com/en-us/library/ms143506.aspx for
complete hardware and software requirements for SQL Server 2008 R2
2
4/9/2020
Other
Requirements:





2.2.

Microsoft Internet Explorer 6.0 SP1 or later
Microsoft ActiveSync 4.5 or later required.
.NET Framework v3.5 SP1 and v4 Full install are both required
** If not detected, automatically installed from internet. If installing on a PC that
does not have internet access, download and install prior to installing
SmartSystems Server.
SQL Server - SQL Server 2008 R2 with latest SP is highly recommended
o SQL Server 2008 with SP1 or later, SQL Server 2008 R2 Express Edition,
and SQL Server 2008 Express Edition with SP1 or later are supported
o Remote database is only supported in a domain environment (not
supported in workgroup environment)
Microsoft Windows Installer 4.5
* SQL Server and Microsoft Windows Installer must be installed prior to installing
SmartSystems Server. The SmartSystems Server installer provides a Help link to
obtain an installation guide and a download containing all prerequisites.
Before Installing Version 4.50
If an earlier version of SmartSystems is installed, the recommendation is to perform an
upgrade rather than uninstalling and reinstalling. Uninstalling a previous version of
SmartSystems and then reinstalling:
o
Will purge any Asset History collected by the current SmartSystems.
o
Will remove custom console settings like Broadcast Interval (automatic
discovery)
o
Will preserve Software Bundles and Backup Settings.

If you are currently using SQL 2005, you can perform a SQL upgrade and then upgrade
SmartSystems server

Migrating SmartSystems data (bundles, rules, etc.) from one machine to another is not
fully supported.

o
Licenses can be migrated by “Returning” them using the Intermec License Utility
on the old machine and then “Adding” them using the Intermec License Utility
on the new machine
o
Software bundles can be migrated by copying the bundle installers from the old
machine to the new machine and installing them
Only these upgrade paths are supported:
o
v3.51 to v4.50
o
v4.02 and above to v4.50
o
In other cases, you will need to do an intermediate upgrade or uninstall

Recommendation is to uninstall Reporting Services prior to installing SmartSystems
Foundation 4.50.

Review SmartSystems Foundation Installation Guide
o

http://epsfiles.intermec.com/eps_files/eps_man/932-015.pdf
For occasional use, SmartSystems Server may be installed on an administrator’s
desktop/laptop alongside other applications. For optimal operation in a production
Intermec Technologies
3
4/9/2020
environment, install SmartSystems Server on a dedicated machine connected to a DHCP
network.

Do not install SmartSystems Server on a machine that is used as a Domain Controller.

Do not install SmartSystems Server on a compressed drive.

When initially installing SmartSystems Server, you must connect to an existing SQL
Server database. When upgrading from a prior version, the data from the prior database
will be transferred into the new database automatically.

Microsoft Windows Installer 4.5 and SQL Server must be installed prior to installing
SmartSystems Server. You may obtain a download containing all prerequisites using the
Help link when you run the installer.

The SQL Server installation process authenticates your user account. If your user
account is a network account, you must be logged into the network in order for
authentication to occur. If the user account cannot be authenticated because you are
not connected (or on a VPN connection), the database will not be created.

SmartSystems Server uses the following ports. SmartSystems attempts to open these
ports in Windows Firewall automatically during an install. If you are using another
firewall, you will need to configure the firewall manually for the ports:
Port
Description
UDP 52316
Remote Viewer
TCP 1901
Remote Viewer
TCP 8789
HTTP (Intermec SmartSystems)
UDP 8791
Upgrade Progress (Intermec SmartSystems)
UDP 8792
Upgrade Monitor Online Status (Intermec SmartSystems)
UDP 49111
IQueue Discovery (Intermec SmartSystems)
TCP 62241
IQueue Messaging (Intermec SmartSystems)
UDP 1434
SQL Database Discovery
UDP 1758-1768
Multicast Files Transfer Protocol
TCP 27000-27009
License Server
Note: If using Windows Firewall, SmartSystems attempts to close the ports
automatically during uninstall. If using another firewall, you will need to configure the
firewall manually after uninstall.
2.3.
To Install:
Download and run the installation file (SmartSystemsFoundationInstall.exe).
Follow the on-screen instructions to verify requirements and complete the installation.
3. SmartSystems Management License

For devices with a v4.0 or above client, a management license allows:
o
Drag-N-Drop to a folder of devices

Intermec Technologies
Deploy or upgrade a group of Intermec devices all at once or in
batches of 50 to save significant time. This procedure is error-proof,
4
4/9/2020
scalable and saves significant effort over manual procedures which
utilize SD cards.
o
Activate Provisioning Bundles on a Folder

Automatically deploy a provisioning bundle to a device upon
connection to the SmartSystems Server
(3.46 SmartSystems client required, works best with 3.48
SmartSystems client and above)
o
Folder Right Click Tools
o
Device Health
o
Data from the device is available to Reporting Services

No per-device license is needed for device with pre-4.0 client

A 60 day demo of the Management license is provided on all 4.0 clients and is enabled
at the time the device is powered on.

Perpetual license, no software maintenance agreement required
SmartSystems management license (454-048-001) is available for purchase through your
Intermec representative.
For additional assistance, contact Intermec Support
(http://intermec.custhelp.com )
Intermec Technologies
5
4/9/2020
4. Supported Hardware
SmartSystems 4.50 supports any device loaded with the SmartSystems client.
The following matrix documents device and software configurations that have known
compatibility with SmartSystems: http://www.intermec.com/partner-files/salesresources/misc/en/smartsystems/SmartSystems-Compatibility-Matrix.xls
5. New Functionality Available in SmartSystems Server Version 4.50
Certain new features are only available on devices using the SmartSystems v4.0 or higher
SmartSystems Client. To determine which SmartSystems Client you are using, open Intermec
Settings and navigate to Device Settings -> System Component Versions -> SSRef Client. (If the
entry does not exist, then your device does not include the SmartSystems client.)
5.1.
Installation
5.1.1. Installation Diagnostic
SmartSystems 4.50 includes an installation diagnostic that pre-checks for potential
problems that could affect the installation and operation of SmartSystems.
 The installation diagnostic checks for Intermec software conflicts, system
memory, processor speed, domain group policies, user permissions, SQL
instance, Reporting Services, network, firewalls, and anti-malware products.
 It warns users of potential problems they may wish to address.
 It detects errors that must be correct before installation can continue.
 It can be run at any time after installation, as a cross-check, via
Start > All Programs > Intermec > SmartSystems > Installation Diagnostic
 Diagnostic results are saved in SSTEMP folder under the root directory of the
hard drive to which your operating system is installed (e.g., C:\SSTEMP)
5.1.2. Use of local system account
SmartSystems 4.50 runs all services in the context of the standard Windows local system
account.
5.1.3. Reporting Services
SmartSystems Reporting Services is installed as part of SmartSystems 4.50.
Running SmartSystems Reporting Services requires:
 a compatible version of Microsoft SQL Server 2008
 a properly configured Microsoft SQL Server Reporting Services instance
5.2.
Performance
5.2.1. Asset Messages processing
Asset message processing is 10x faster than in SmartSystems Server 4.02.
5.2.2. Device connections
SmartSystems 4.50 provides more robust support for discovering and managing larger
populations of devices.
5.2.3. Tracking of available memory
Intermec Technologies
6
4/9/2020
SmartSystems 4.50 periodically monitors the available memory, which affects SQL
Server performance. If free memory drops below 50 MB, this is reported dynamically
through the System Monitor service.
5.3.
Properties Viewer
SmartSystems 4.50 Properties Viewer shows only the information applicable to the
selected device’s hardware configuration, eliminating extraneous display panels.
5.4.
Managing SmartSystems Users
SmartSystems 4.50 allows a local user to add a domain user to the SmartSystems
console. If the domain requires authentication, SmartSystems prompts for credentials
to the domain and authenticates the credentials.
5.5.
Bundle Wizard enhancements


5.6.
SmartSystems 4.50 Bundle Wizard supports creating bundles in a special format
for updating peripheral devices (PR2/PR3 printers.)
SmartSystems 4.50 Bundle Wizard supports installing bundles on machines
having 64-bit OS and not having SmartSystems Server installed.
Peripherals Panel
SmartSystems 4.50 provides a new panel that displays peripherals attached to devices in
the currently selected folder and their connection status. All displayed peripherals
support right-click Rename, Delete, Device Note and Properties.
5.7.
Support for Bluetooth PR2/PR3 printers
Bluetooth PR2/PR3 printers are reported via the new peripheral printer. The health
information of a Bluetooth PR2/PR3 printer, including Smart Battery info, is reported to
the console via the printer configlet running on the associated mobile computer.
PR2/PR3 requires Bluetooth connection to a mobile computer having:
 v4.0 or above SmartSystems client
 SmartSystems Management License
 Printer Configlet ver. 2.30.00.0087 or above installed
When a “peripheral” software bundle, created through the Software Bundle Wizard, is
dragged and dropped to a PR2/PR3 icon in the peripherals panel, the printer configlet
running on the associated mobile computer manages the update of the software on the
PR2/PR3 printer. The following file types are supported by the printer configlet:
Bootloader files, Firmware files, Graphic files, Font files, and Alias files.
PR2/PR3 requires Bluetooth connection to a mobile computer having:
 v4.0 or above SmartSystems client
 SmartSystems Management License
 Printer Configlet ver. 2.30.00.0087 or above installed
5.8.
Support for Wi-Fi PR2 and PR3 printers
SmartSystems 4.50 supports right-click Rename, Delete, Default Setup, Print Test Label,
Reboot, Test Feed, Intermec Settings, Directed Discovery, Device Note and Properties
Intermec Technologies
7
4/9/2020
viewer for Wi-Fi PR2/PR3. SmartSystems 4.50 also supports dragging and dropping a
file or a software bundle to this printer.
5.9.
Support for PC23, PC43, and PM43 printers
SmartSystems 4.50 supports a full range of device management features for PC23, PC43,
and PM43, including all the features supported by Wi-Fi PR2/PR3 printer, provisioning
bundle support, licensing support, and the ability to manage server association through
SmartSystems Server
Section 3 lists the features that require a SmartSystems Management License.
Intermec Technologies
8
4/9/2020
6. Best Practices
6.1. Provisioning
Connectivity
Completing a provision depends on the device reporting its status to the console. Refrain from
making changes which leave the device unreachable by the console. Wherever possible, use an
Ethernet connection for provisioning. Any changes to network connectivity, such as an OS
upgrade that resets network settings, may cause the device to disconnect from SS Console and
stop provisioning.
Client Compatibility
SmartSystems Reference Client Version 3.46 is the minimum required version for provisioning,
but version 3.48 or above is recommended. If the version in your device is less than the desired
version, check the Downloads section of www.Intermec.com/SmartSystems for an upgrade.
 A quick way to check the version is to connect the device to the SmartSystems console and
view the SSRef column in details layout. Alternately, open Intermec Settings and navigate to
Device Settings -> System Component Versions -> SSRef Client.
Ordering
The type of file added to a provisioning bundle determines the order it will be installed. Many
file types can be installed in a custom order. The provisioning bundle tool will place the added
files in a preferred order. For stability, some bundle types, like OS, will cause an error message if
they are attempted to be moved later in the installation order.
The SmartSystems Reference client affects the performance and features of provisioning. If your
provisioning bundle includes the SmartSystems Reference Client, place it as early as possible in
the provisioning bundle sequence.
Activating Auto-Deploy
For better control, avoid activating auto-deploy of a provisioning bundle to the Discovered
Devices folder. Instead, create sub-folders with a name that describes the provisioning bundle.
Then you can control which devices are provisioned automatically when they are first placed in
that folder.
Manual Deployment
Manually dropping the provisioning bundle onto a device or a folder of devices is best done
when the bundle is small and consists of mostly user settings.
Monitoring Progress
There are four areas which show the progress of the devices being provisioned.
1. The Status and Reason sections of the device icon give minimal information and are
best viewed in the details layout.
2. The Upgrade Monitor, launched from the right click menu of the Universal Upgrade
Server icon, lists devices as they get provisioned and provides more information than
the main console GUI.
3. The Upgrade Server Event Viewer, accessed from the right click menu of the Universal
Upgrade Server icon, needs to be refreshed to show progress and may become difficult
to follow as the quantity of devices increases.
Intermec Technologies
9
4/9/2020
4. The status window on the device displays the upgrade status as it progresses through
each stage of the provisioning bundle.
Population Sizes
The performance of the provisioning bundle is affected by server performance characteristics
(processor speed and memory), network performance characteristics, size of the bundle, and
quantity of devices being deployed. Smaller bundles, containing mostly configuration settings,
are easily handled in batches of 50 devices at a time. Larger bundles, like OS upgrades, consume
large amounts of bandwidth. The best practices support up to 12 simultaneous OS upgrades
through a provisioning bundle. It is never recommended to attempt more than 24 simultaneous
OS upgrades through a provisioning bundle.
6.2.
Device Discovery
When the SmartSystems services start, they send out a signal to discover all the SmartSystemsenabled devices connected to your local subnet, and an icon representing each discovered
device appears in the console. As the status of the device changes, it will send a message to the
console to communicate its new status.
You can always trigger a broadcast manually by clicking the Discover button again, but there are
several ways to configure your console or device through Intermec Settings to enhance the
device discovery process:
 You can configure SmartSystems to broadcast across subnets or to specific IP addresses
or IP address ranges.
 Configuring IP Address Ranges works well for a small number of devices with
known IP addresses. If you want to broadcast to a remote subnet, Subnet
Broadcasts is preferable because the network traffic is reduced, but routers may
have to be configured to forward SmartSystems broadcast packets. Configuring
both subnet broadcasts and IP address ranges is not recommended. You do not
need to specify the subnet broadcast interval of the SmartSystems server
because SmartSystems automatically broadcasts to that subnet.
 You can configure SmartSystems to periodically initiate device discovery on its own
using the Broadcast Interval timer.
 You can configure an Intermec device to connect to a specific SmartSystems console
using the Server Association property.
Using the Broadcast Interval feature is helpful when working with a large number of devices
because it can reduce network traffic associated with device discovery. Pressing the “Discover”
button causes all devices to identify themselves to the SmartSystems server. When using the
Broadcast Interval to initiate periodic device discovery, only devices which aren’t registered with
the server will identify themselves.
7. Issues Fixed In This Version
ID
12550
Description Summary
Devices having licenses in SmartSystems, then deleted from SmartSystems
by the user before an upgrade, are recreated with partial information
after upgrade
Intermec Technologies
10
Systems
Installation
4/9/2020
10817
13843
14783
Managing devices that have licenses that originated on a different
SmartSystems server results in extraneous event notification in Event
Viewer such as, "Device {insert device uniqueid here} has licenses that
were not licensed from this server. Is this device in the wrong location?"
Ambiguous Scan and Go Folder Creation without "\"
Restarting System Monitor from right-click will shut down Upgrade Server,
but not start it back up
Intermec Technologies
11
Licensing
ScanNGo
Services
4/9/2020
8. Known Issues in This Version
ID
3785
Description Summary
Bundle Wizard prompts to save when there are no changes
Workaround: None
Bundle Wizard doesn't retain destination between advanced and basic
views
Workaround: None
Systems
Bundle Wizard
3766
Subnet Broadcast feature does not work
Workaround: Use IP Address Range or enter Associated Server IP on the
device
Discovery
3732
Multicast doesn't work correctly when more than 1 Network adapter is
enabled on pc
Workaround: Disable one network adapter, restart the SmartSystems
Services, and reinitiate the multicast
Clicking Discover while devices are "busy" causes them to show
"connected"
Workaround: Do not click Discover when devices are upgrading
Discovery
When some (older) bundles installers are executed on a 64-bit OS, bundle
directories are created but bundles do not appear in the Software Vault
Workaround: Request the bundle provider to rebuild the bundle with
the Software Bundle Wizard
Firewall exceptions not being correctly applied to all network profiles
during install
Workaround: Apply firewall exceptions manually to all network profiles
per the table in Section 2.2 above
Missing topic in table of contents for online help: License Center will not
open on Server 2008 R2 without adding it to the trusted sites
Workaround: To add the Intermec License Center to the list of trusted
websites
1. In Internet Explorer, select Tools > Internet Options and select the
Security tab
2. Select Trusted Sites and click the Sites button
3. Type https://license.intermec.com and click Add
4. Close the Internet Options screen
Missing topic in online help: If SQL Server is configured as Default
instance, then "(local)" must be selected on Database Instance Selection
screen
Workaround: None
Can't drag and drop files from mapped network share drive to a device
Workaround: Copy the file to a local folder, and then drag it from the
local folder to the device’s icon in the console
Installation
When peripheral printer battery is swapped, the console still shows the
old battery as connected to the printer
Workaround: None
Console GUI
3792
3751
4418
4804
4395
6038
4951
5516
Intermec Technologies
12
Bundle Wizard
Discovery
Installation
Installation
Installation
Console GUI
4/9/2020
ID
5416
3759
3774
5074
4961
5478
5630
3734
4794
5959
3728
3731
6000
3745
4774
Description Summary
When device moves between SmartSystems consoles, View Device
Licenses only shows licenses deployed from current console
Workaround: Use Intermec Settings on the device to view all device
licenses
Remote Viewer Unhandled Exception when rotating display
Workaround: Change the display to a smaller size before rotating display
Remote Viewer File Explorer doesn't display some foreign characters
Workaround: Use ASCII Characters only for folder and file names
Remote Viewer shows black screen when device is at Windows Login
Prompt
Workaround: Complete login process on device before starting Remote
Viewer
Warning, “problem when downloading,” when trying to download a large
file from device to SS Console
Workaround: Use another method such as ActiveSync to retrieve the
large file from the device
GWES.EXE (Microsoft executable) crashed after scanning a ScanNGo
barcode to download a cab file to CN3 with 3.26.15.0170 firmware
Workaround: None
Systems
Licensing
ScanNGo will not include configuration data that is the same as the
assumed default value
Workaround: None
ScanNGo Code 128 Numbering is off for barcodes with No Start Barcode
Workaround: Include a start barcode
ScanNGo GUI gets deformed with different display settings
Workaround: None
ScanNGo
ScanNGo settings bundle doesn't show correct WWAN configuration fields
for all devices
Best practice: Creating backup settings directly from a device is
preferable to using ScanNGo settings for WWAN configuration
Message Send Tool throws exception when trying to record AUDIO
Workaround: Record audio using some other application and save the
recording as a .wav file to import into the Message Send Tool
ScanNGo
Test Current Settings for Message Send Tool deletes the user file
Workaround: None
Settings backup could not be completed for CS40 with 2.00.18.0045
firmware on server running Win7 64-bit OS (Danish language server OS)
Corrective action: Contact Customer Support to obtain a bundle
containing the 4.03.11.0591 SSREF client
Cisco Discovery no longer working on servers running 64-bit OS
Workaround: None
Printer Properties > Font Information is not updated after drag and drop
of SW bundle containing fonts
Workaround: Rebooting the printer will cause the font information to
be updated in properties
Send Message
Intermec Technologies
13
Remote Viewer
Remote Viewer
Remote Viewer
Remote Viewer
ScanNGo
ScanNGo
ScanNGo
Send Message
Supported
Devices
Supported
Devices
4/9/2020
ID
4720
4691
Description Summary
On Windows 7 64-bit OS, turning on SSAPI logging (for troubleshooting
system issues) and restarting services causes a crash dump
Workaround: None
Tray icon does not always appear after reboot
Workaround: Start tray icon manually via Start > Programs > Intermec >
SmartSystems > ConsoleTray
Intermec Technologies
14
Systems
Troubleshooting
Tray Icon
4/9/2020