|
| Mar 8 |
|
| Mar 3 |
|
| Mar 1 |
|
| Jan 26 |
|
| Jan 22 |
|
| Jan 14 |
|
| Dec 7 |
|
| Dec 7 |
|
| Dec 2 |
|
| Nov 26 |
|
Installation Packages & Licensing
This document is an overview of IADS® installation packages and their licensing.
Ordinarily we provide installation packages in the form of a CD-ROM which will automatically begin the installation when the disk is inserted. However, the contents of the CD can easily be copied to a local or remote storage device prior to installation. To bypass the auto-run feature of your CD drive, hold down the Shift key while inserting the CD. To execute the installation manually, double-click on the IADS.msi file.
All packages are Windows Installer 2.0 compliant. This can provide a variety of end-user options for application management and installation. For more information, I’d recommend taking a look at the Microsoft support center about this service. (http://support.microsoft.com/search/default.aspx?query=windows%20installer) This functionality gives the end user or organization a great deal of flexibility with regard to how to deploy our software by using capabilities such as ‘silent’ installation or even to remotely deploy packages to remote users at their desktops.
Feel free to duplicate installation media for appropriate use and distribution in accordance with your licensing and maintenance agreements with Symvionics, Inc.
Installation Requirements
· The required operating systems supported by the installer are the following Microsoft OSs. Windows 2000, Window XP, Windows Server 2003, Windows Vista, Windows Server 2008. note: at this time IADS® has not yet been officially tested for use with Vista, 2008 or 64bit versions of any of the above. · The account performing the installation must have Administrative Privileges. · Microsoft Internet Explorer 6.0 or greater.
Installation is also possible for Windows NT 4.0 Service Pack 6a by upgrading the Windows Installer Service using instmsiw.exe (provided on the installation CD) However, keep in mind that the only application approved for use with NT4.0 is the Caching Data Server feature.
Disk Labels
Each official installation CD is labeled with its respective part number which corresponds to the different packages available for purchase. · The first line of the label indicates the revision of the software (such as 5.3.2 or 6.0) · You can determine part number of the package you have from the second line which will read IADS-TELEM-xxx where xxx denotes the details of a particular packages capabilities. · The third line of the CD will indicate if the CD contains any facility specific enhancements or modifications. · Each CD also contains the acronym F.O.U.O (For Official Use Only) and the word Unclassified as requested/required by many of our customers.
Some support issues may require that we need to know the name of the installation CD.
Packages
Each part number denotes a distinct set of features and capabilities distinct from one another that fit into distinct categories of usage by the end user. Some disks are provided to customers to fulfill a distinct commitment, but we also often provide additional media as a convenience to our customers to simplify deployment. Feel free to contact us if you would like us to generate additional or different media for your facility.
Here is an overview of the most common packages and their capabilities. If you have any questions about a particular package, or it suitability for specific task don’t hesitate to ask. · IADS-TELEM-BASE This package is the most comprehensive and it provides the ability to individually install nearly all of the individual features available including both Realtime and PostTest Server, Client capabilities and also the Operator’s Console. This package is most typically used for building up Mission Control Room type facilities. · IADS-TELEM-PTSTATION (formerly PTSERVER) This package is similar to the BASE installation in that it has both Client and Server features, but in this package they are targeted towards a group-oriented PostTest environment. · IADS-TELEM-CLIENT This package provides three different ‘flavors’ of Client for installation. Note: there is no Server software provided with a CLIENT, but no server is necessary using a ‘Local Mode’ Client 1. Local Mode Client – for directly interacting with a configuration file and a set of data files at the file level. 2. Post Test Client – used to connect to a PostTest Data Server for interaction with a dataset in a group-based client/server fashion similar to a realtime environment. 3. Realtime Client – for connection to a realtime Caching Data Server. · IADS-TELEM-RTSTATION This package provides capabilities for a comprehensive single point of execution and interaction with a variety of datasources to the display software. It is most often used for onboard or planeside interaction for data validation and monitoring. It is often referred to as a ‘kiosk’ form of IADS® but keep in mind it is also expandable for multiple Realtime Client connections using a CLIENT-RTS package. · IADS-TELEM-BASE-TPP This package is essentially a melding of the BASE and RTSTATION packages. It can be used to provide Mission Control Room services for all supported datasources. It incorporates the capabilities of Realtime and PostTest Servers, Clients and the Operator’s Console. · IADS-TELEM-MAPS This 2-disk installation set contains two-dimensional map files for use with the Moving Map display. If you have an area of interest that is not currently available, please contact Customer Support. Note: this installation package may be co-installed with other IADS® installation packages. · IADS-TELEM-TERRAIN This package contains three-dimensional terrain and texture information for use with the Situational Awareness display. Due to the vast amount of data available we recommend that you install this data onto a network server for general client access (rather then installing it onto individual workstations.) If you have an area of interest which is not currently available, please contact Customer Support. Note: this installation package may be co-installed with other IADS® installation packages.
Some of our installation media may indicate on their labels additional sub-package information such as an IADS-TELEM-CLIENT-5 indicates that the software was procured as a ‘5-pack.’ There are also OEM versions of our installation packages available.
It is important to point out that unless indicated otherwise above, no two packages can be installed on the same machine. For example, it is not possible to install both a PTSTATION and an RTSTATION on the same hardware.
I would also like to point out that not all installation packages of the same name are 100% identical. Many of our packages contain distinct features or capabilities which are only made available to specific facilities.
The Installation Process
If you receive any error indications during the installation process, please contact Customer Support. Keep in mind that individual facilities may have provided different installation procedures for use at their own facilities (such as network distribution using the extensions provided by the Windows Installer framework) The instructions below presume that you have direct access to official installation media.
· Begin the process by executing the IADS.msi via insertion of the CD or by direct execution of the file. · After some housekeeping details and machine configuration information is established you will be presented with the welcome screen. · Next you will be presented with (and must agree to) the software license agreement. · You will now be presented with the Custom Setup screen where you can choose which features to install. The options available to you here are dependant on what package you are currently installing. Click the downward pointing triangles next to the hard disk icons to turn on or off individual features. Make a note of which components you have chosen to install for use when requesting a license. Note: some installation packages do not present this screen. If this is the case, make note of the part number on the CD label.
If you are performing an ‘inplace upgrade’ (installation of a newer version over the top of an existing older installation) of your software the selections on this screen will match the selection from the previous install.
· Presuming you have enough disk space for the installation and there are no errors, you will presented with a Finish dialog indicating completion. Note: you might be required to reboot for complete installation. You will receive indication to reboot if it is required.
Licensing
At this point some customers may need complete a couple additional steps for full activation by installing a license key. Customers with Site Licenses have license keys embedded into their installation media and do not need to individually license the software. If you are performing an ‘inplace upgrade’ (installation of a newer version over the top of an existing older installation) of your software you license information will be maintained from the previous installation.
Licenses have two major components which are accessed by executing the IADS Key Manager from the Start Menu. The first is a machine specific unique System Identifier known as a SysId. The second is a License Activation Key known as a Key.
It is important to note that Keys are provided in accordance with purchases made to Symvionics for the use of particular IADS® features. Simply because you have access to an installation package does not guarantee the ability to procure a Key. Most facilities use a single point of contact for procuring keys. We are happy to interact with multiple points of contact, but it does require additional crosschecking and may increase the time needed to generate Keys.
Keys are issued on a per-machine basis. Keys contain the capability to allow or disallow particular software features. At this time the Key Manager does not indicate which features the Key will activate.
When you execute the Key Manager you will be presented with the interface for viewing the currently installed SysId and Key. This is also the interface used for creation of a new SysId or installation of a new Key. It is important to note that if you execute the Key Manger and receive no errors or warnings in conjunction with a currently registered SysId/Key combination then you already have an activated license.
Generating a Unique System Identifier (SysID)
In order to request a license Key you must first generate a new SysId. 1. Click the Key icon to enable the Create New SysID button.
2. Click the Create New SysID button.
3. Choose Yes at the warning dialog.
Requesting a Key
Please provide the following information for any request (or batch of requests) these items are especially important for the original request for new keys. Although these items are not strictly required, they will help us to service our response faster. 1. The organization and facility for which the license was purchased. Please keep in mind that it can be very difficult to determine this at some facilities which may outsource some aspects of their resources such as a Lockheed employee working at a US Air Force facility. The more detail the better. 2. If you have been provided with a ‘facility id or key family’ please include it. These Ids are of the form letter-number-number.number-number-letter.number-number (A43.12B.05) 3. Please submit the Purchase Order number(s) for which you are requesting licenses. If the software was procured from a 3rd party, please try to obtain the PO number they used to make the purchase.
Retrieve your notes from above about what features you chose to install during the installation process above at the Custom Setup screen. If no Custom Setup screen was available during the installation process you will need to know the part number of the installation package.
Submit the following information for each SysID 1. The SysID 2. The name of the system (its network name) note: this item isn’t required, but it will aid you in tracking and registering your license keys. 3. The list of features you installed and would like to license (Caching Data Server, PostTest Data Server, Client, etc.) or the part number from the installation media if no Custom Setup screen was available.
Please do not send screenshots when requesting keys.
Bundle up the items from above into a text file and email them to Michael Jones: mjonesATsymvionicsDOTcom or mjonesATiads-softDOTcom. My apologies if those email addresses aren’t obvious but I’m trying to avoid as much spam as possible and this is a public document.
Key requests are typically processed within 24 hours, but generally much faster. If you have a keying emergency contact our Palmdale Office at 661-273-7003 (Pacific Time business hours,) use your IADS 24/7 support numbers, or contact Michael Jones directly. If you have a need for extra keys for backup hardware, don’t hesitate to contact Pat Mattingly (patATiads-softDOTcom) note: there are plans in the works to make this transaction available as an automated process via the internet.
Installing a Key
Once you have generated a new SysID and received a key for your request you must install the Key for use. 1. Execute the IADS Key Manager using the Start Menu. 2. Locate the Key which corresponds to your Currently Registered SysID and paste it into the New Key field. 3. Click Register Key.
Transferring a License
As hardware evolves, it is becoming very common to want to transfer a license from old hardware to new hardware. If you ever have the desire to move an activated license from an existing machine to another, please perform the following steps. 1. Uninstall IADS® from the computer with the existing license and collect the file C:\iadsUninstall.txt. 2. Submit this file along with a request for a new key.
Retiring a License If you ever have the need to deactivate a license entirely, please perform the following steps. 1. Uninstall IADS® from the computer with the existing license and collect the file C:\iadsUninstall.txt. 2. Submit this file for retirement of the key.
|
| |||||||||||
| Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy |
| ©2010 Google |