Software Release Notes. SmartSystems Server v3.51

Transcription

1 Software Release Notes SmartSystems Server v Version Information Installation Notes and Compatibility System Requirements for installing the SmartSystems Server Before Installing Supported Hardware New Functionality Available in Version Best Practices Best Practices for One-Step Provisioning Best Practices for Device Discovery Compatible Utilities Issues Fixed In This Version Known Issues... 8

2 1. Version Information These release notes describes the updates available in SmartSystems Server Software is available for download from the Intermec software downloads site at Please reference the online help for complete user information. The online help is accessible from the SmartSystems Server by selecting Help from the menu. Current Version Version Date SmartSystems Server /18/2010 This version replaces all prior releases of SmartSystems Server. Users of beta versions of v3.51 should upgrade to the released version. Prior releases are listed below. Release Date Available /17/ /14/ /29/ /27/ /22/ /19/ /15/ /21/ /26/ /2/ /19/ /27/2005 Intermec Technologies 2 2/8/2010

3 2. Installation 2.1. System Requirements for installing the SmartSystems Server Processor: 2 GHz is recommended for optimum performance Memory / RAM: 2 GB is required Disk Space: 60 MB is required for SmartSystems Server Additional space required for pre-requisite software. Operating System: Other Requirements: Windows XP Pro with SP3 and all related updates Windows Vista 32-bit Business and Ultimate Windows Server 2003 SP2 R2 Windows Server bit Enterprise Microsoft Internet Explorer 6.0 SP1 or later Microsoft ActiveSync 4.5 or later required for Windows Mobile 6.1 devices.net Framework 3.5 SP1 ** 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 2005 Express Edition, SQL Server 2005, SQL Server 2008 Express Edition, or SQL Server 2008 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 Upgrading to SmartSystems Server v3.50 from a prior version is supported for versions v3.21 and above. If you are upgrading from a version earlier than v3.21, uninstall that version before installing SmartSystems Server v3.50. Make sure you have installed required software before installing SmartSystems Server. Ensure that you have administrator rights on your computer. Administrator rights are required to install SmartSystems Server. If operating in an Active Directory environment, your system administrator may have set network policies or restrictions that prevent products like SmartSystems Server from installing successfully. Verify with your System Administrator that your account has the appropriate administrative permissions to: create local user accounts that can be added to the Administrators Group, create local groups, and that the security policies (Group Policy Objects. GPOs ) allow a user to log on as a service. For occasional use, SmartSystems Server may be installed on an administrator s desktop/laptop alongside other applications. For optimal operation in a production 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. Intermec Technologies 3 2/8/2010

4 Uninstall any beta versions of Microsoft products. When upgrading from a prior version of SmartSystems Server, contents of the Software Vault (back-up settings, software bundles) will be preserved. 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 Install 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 UDP TCP UDP UDP 8792 UDP 8791 TCP 8789 UDP 161 UDP 162 UDP 1434 Description required for discovery if device is not associated with a known server required for communication between server and associated devices required for multicast communications used with AutoDeploy feature Upgrade Monitor Online Status Upgrade Progress HTTP SNMP Trap Port Required to connect to a remote database Note: If using Windows Firewall, SmartSystems attempts to close the ports automatically during uninstall. UDP 8791 and UDP 8792 ports will be still be open after uninstall. TCP 8789 port will also be open after uninstall on Windows XP or Windows Server If using another firewall, you will need to configure the firewall manually after uninstall. To Install: Download and run the installation file (SmartSystemsFoundationInstall.exe). Follow the on-screen instructions to complete the installation. After Installing: In Windows Vista, the tray icon for SmartSystems Console must run in Windows XP compatibility mode. The SmartSystems installer automatically enables this mode for the current user who installs SmartSystems. If other users share the same computer, Windows XP compatibility mode will need to be set manually after installation for each user. To set Windows XP compatibility mode for the tray icon for other users, see item 2138 in the Known Issues section. Intermec Technologies 4 2/8/2010

5 3. Licensing No license is required to use the basic features included in SmartSystems Server. A SmartSystems AutoDeploy license is required to activate advanced functionality: Deploy or Upgrade a group of Intermec devices all at once to save significant time. Tests showed that it required over an hour to upgrade the OS and SSPB on 10 Intermec computers using SD cards. That same activity was completed in less than 10 minutes using SmartSystems AutoDeploy. Note: AutoDeploy licenses are sold in groups of 15, 50 or 200 licenses. A group of licenses is for use with one SmartSystems Server. (I.e. a 50-count device license cannot be split between multiple SmartSystems Servers.) Automatically deploy a provisioning bundle to a device upon connection to the SmartSystems Server (this feature only supported on device with a minimum SmartSystems client of 3.30). Print Scan-to-Connect barcodes. Scan-to-Connect is a separate software download and installation that allows you to quickly generate configuration bar codes to connect your mobile computer to your SmartSystems server and network. In addition to allowing you to quickly connect to your SmartSystems Server and network, the Scanto-Connect utility also allows you to load software files from a web server onto your mobile computer by scanning a bar code. Install and use SmartSystems Reporting Services Licenses are available for purchase through your Intermec representative. To determine if a pre-existing AutoDeploy license is valid for use with SmartSystems Server v3.51: a. Right-click SS_LIC_MNGR (License Manager Server) under SmartSystems Services and select License Summary. b. Review the Maintenance Expiration date or the Maintenance Status column for the ss.autodeploy license. c. If the Maintenance Expiration date is 9/17/2009 or later, AutoDeploy features are still active no additional license is required. If the maintenance expiration date is prior to 1/18/2010, your license is not valid for use with version You must obtain a new license or renew your maintenance plan. For additional assistance, contact Intermec Support ( ) 4. Supported Hardware SmartSystems Server v3.51 supports any device loaded with the SmartSystems client. The following device and software configurations have known compatibility with SmartSystems Server v3.51: Device Type Model OS/Firmware Latest SmartSystems Client Computer 7xx WM Computer 7xx WM Computer CK3 WM Computer CK30, CK31 CE Computer CK32 WM Intermec Technologies 5 2/8/2010

6 Device Type Model OS/Firmware Latest SmartSystems Client Computer CK60 WM5.0, CE Computer CN3 WM5.0, WM Computer CN4 WM Computer CN50 WM Computer CV30 WM5.0, CE Computer CV60 CE Computer CV60 XP/XPe 3.43 Printer PB50 Fingerprint, IPL 3.20 Printer PB51 (Wireless Option Only) Fingerprint, IPL 3.20 Printer PF2i Fingerprint, IPL 3.20 Printer PF4i Fingerprint, IPL 3.20 Printer PM4i Fingerprint, IPL 3.20 Printer PX4i Fingerprint, IPL 3.20 Printer PX6i Fingerprint, IPL 3.20 RFID Reader IF61 Linux 3.20 RFID Reader IF30 Linux New Functionality Available in Version 3.51 None this is a maintenance release. 6. Best Practices 6.1. One-Step Provisioning Broadcast Interval should be set to a 1 or 2 for faster discovery of devices that are not associated with a server. If you are provisioning across a subnet, enable the subnet broadcasting in the SmartSystems Core Messaging. Don't change your wireless settings while you are provisioning your device, unless you also set the Associated SmartSystems Server IP address. Depending on your network setup, changing the wireless settings may result in the device not being discovered by SmartSystems to continue the provisioning sequence. If your provisioning bundle contains an Operating System, and the Operating System is expected to update on your device, you cannot use Wireless. Wireless settings will be dropped during the OS upgrade, and that could result in the device not being discovered to continue provisioning. For higher success rate in provisioning, check the version of SmartSystems Client in your device s operating system. The recommended version is v3.46 or greater. To determine which SmartSystems Client is installed on your device, open Intermec Settings and navigate to Device Settings -> System Component Versions -> SSRef Client. If the version is not v3.46 or greater, it is recommended to download SmartSystems Client Bundle from and install into your SmartSystems Server. Intermec Technologies 6 2/8/2010

7 o o For provisioning bundles that include an Operating System, place the SmartSystems Client Bundle in the provisioning bundle immediately after the Operating System. For provisioning bundles that do not include an Operating System, make the SmartSystems Client Bundle the first item in your provisioning bundle 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, but if you want to broadcast to a remote subnet, Subnet Broadcasts is preferable because the network traffic is reduced. 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. Compatible Utilities The versions listed below are compatible with SmartSystems Server v3.51. SmartSystems Utility Updated Version (Compatible with v3.51) SmartSystems Scan-to-Connect SmartSystems Bundle Wizard SmartSystems Remote Display SmartSystems Remote File Explorer SmartSystems Reporting Services New versions can be found using the following link: Intermec Technologies 7 2/8/2010

8 8. Issues Fixed In This Version The following issues were reported in prior versions and have been fixed in this version. ID Description Summary Version Systems 2138 Vista Security prevents SS from changing service states for users other than the user who installed SmartSystems Console 3.50 Installation 4665 SmartSystems installation on German Operating Systems 3.50 Installation is not working 4667 After an install or upgrade - no icons will show or show 3.50 Installation Unknown 5168 CPR Installation - Issues with Windows 3.50 Installation XP SP3 Danish Version 3532 Unhandled Exception in Invoke or BeginInvoke in console 3.50 Tray Icon tray icon 3801 Discovery does not work if Windows XP Firewall is enabled, 3.50 Discovery on a new installation of SmartSystems Server v Vista firewall on Virtual PC prevents discovery of devices 3.50 Discovery 4662 CPR PM4i does not reconnect to 3.50 Discovery SmartSystems after a power cycle 3582 Asset Viewer Information in the right hand side pane is not an accurate reflection of the latest asset message Asset Viewer Vista Stopping of services may show a Licensing Error 3.50 Licensing depending on the users security rights 5363 CPR - Smartsystems - CN50 Backup settings shows "- blank-" in the preamble field Backup settings 4068 Provisioning - Allows a reboot of the device to occur while 3.50 Provisioning settings are still being processed 4097 Provisioning Bundle - User Files do not maintain their 3.50 Provisioning position in the bundle list after an edit 4155 Provisioning - cleanboot of device and subsequent load of 3.50 Provisioning sspb can cause provisioning issue 4097 Provisioning Bundle - User Files do not maintain their 3.50 Provisioning position in the bundle list after an edit 4211 CN3 WM5 device upgrades fail if operating system version 3.21 is installed on the device without SSPB 3.50 Upgrade Server 2169 Errors creating avalanche package - missing dlls and 3.50 Avalanche package 5154 Scan to Connect - S2C_Config settings do not allow Association to be changed in Funk Security 3.50 Scan-to- Connect 9. Known Issues ID Description Summary Systems 3559 Vista security flags Intccdp driver during install, Windows can't verify the Installation publisher of this driver software Having multiple CK31 and 7xx bundles causes SmartSystems Console to be unresponsive for an extended period of time Console Workaround: Remove any CK31 or 7xx bundles that are not needed Images missing from Core Messaging Server help in Intermec Settings on Server 2003 Online help Intermec Technologies 8 2/8/2010

9 ID Description Summary Systems Workaround: Right-click inside the Help pane and select "Refresh" 3546 Unable to Discover IF5 Discovery 5947 Discovery server does not broadcast on all enabled interfaces The discovery server sends the broadcast for all interfaces to just one interface. For example, if you have two enabled network interfaces on a machine (e.g x and x.x) the discovery broadcast for both interfaces would be sent to the x network not allowing devices on the x.x network to be discovered (or vice versa). Workaround: Enable each adapter individually and click the discover button Discovery until devices on all networks have been discovered Restore Item defaults in a backup file is not working for some settings on CE devices. The failure only affects the backup settings file. Restore operations work on the device itself and through a live connection with SmartSystems. Settings that exhibit this issue include Preamble and Postamble fields for internal and dock tethered scanners, Enable RFID Service, PB42 Bluetooth device name, Application ITE Session Name, and Core Messaging Service Associated Server IP Provisioning Bundle - Force provisioning of SSREF, Application and Settings not working. The failure only affects provisioning bundles that don't contain an Operating system Server Association Tool Doesn't always accurately reflect the IP address of the associated server. When associating multiple devices in the console to different server IP addresses, one after the other, using the right click Server Association Tool, the tool does not reflect the IP of the currently locked server Avalanche Package Builder fails on Software Bundle Wizard bundles. Workaround: Update ss_info.xml manually to remove the trailing \ and then restart SmartSystems services so SmartSystems processes ss_info.xml again SmartSystems Console - Software Vault may show two icons with same name after installation Workaround: Click Refresh 3136 Bundle install error message lacks information. If the user tries to install a bundle in SmartSystems Server that was already installed with the same name and version, they receive this error message: Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel. Workaround: If you want both bundles to be installed, change the name or version on one of them so that they can co-exist. An alternate way to remove the existing version is to right click on the software item and select Delete to have the SmartSystems Server start the appropriate uninstaller for them. Connect barcodes. An update to CN50 Operating System will resolve this issue, planned release in early Q4. Backup Settings Provisioning Server Association Software Vault Software Vault Software Bundle Wizard 3385 Scan to Connect - S2C_Config template does not work for CN50/Microsoft Security. A S2C_Config template is installed in the software vault with SmartSystems This is an empty backup settings file containing just connectivity settings that can be used in place of a backup settings from a connected device. However, if S2C_Config template is used to prepare connection settings for a CN50 with Microsoft Security, an error is received on the device, setting configuration values failed. Workaround: Connect a CN50 to SmartSystems. Create Backup Settings of the CN50. Edit the Backup Settings with the necessary communication configurations. Right click the Backup Settings, select Print Scan-to- Scan-to- Connect Utility Intermec Technologies 9 2/8/2010

10 Intermec Technologies 10 2/8/2010