Deployment Overview (Installation):

(1)

Deployment Overview (Installation):

Truck Tracker software is compiled as a 32-bit windows application, but it will run on both 32-bit and 64-bit operating systems. It is intended to run on Windows XP SP3, Windows Vista, Windows 7 and 8, Windows Server 2003 or 2008 and higher operating systems. The minimum RAM required is 512 MB for SQL Server, but more is recommended. Also a 1.0 GHz or faster processor is needed.

The software is required to use Microsoft SQL Server 2005, 2008, or 2008 R2 database backend, which is compiled as both 32-bit and 64-bit windows services. You can run the program using your own

installation of SQL Server, or you can choose to have the setup program download and install a new instance of SQL Server Express automatically. SQL Express cannot automatically be installed on a domain controller. For more information about system requirements or SQL Server downloads, click here http://www.microsoft.com/en-us/download/details.aspx?id=30438.

Truck Tracker software installation is designed to be as streamlined as possible. If you do not have required components, such as .NET Framework 3.5 or SQL Server native client driver, they will be downloaded and installed automatically for you.

Truck Tracker software requires all users to share one instance of the database. Customers with multiple users will normally deploy the network server installation onto one computer, and then deploy the client only installation to the other workstations. Customers with a single user will typically deploy as a standalone system on one workstation. You can share the program over a local area network using UNC path or a mapped drive. If you are using a shortcut to launch the program, make sure the “Start In” path is the same folder as the program.

If you are using the program over the internet with a remote site or remote users, you should use a remote desktop service such as Terminal Server or Citrix server. The installation will prompt you to point to your SQL Server to install the database. Local settings will be stored per user account in roaming storage folders.

Installing Minor Updates:

The software can automatically (or manually) check the internet or a shared folder on your network for minor updates. These settings can be changed under File->Settings->Auto-Updates.

If an update is available the program will ask the user if they want to download and run the installation file. If the program is not already installed on the computer running the update, for example when running from a network drive, the update will notify the user and the installation will be cancelled. If the program is installed on another computer (server) then you will need to log into that computer with administrator rights to install the update. Once the server installation is updated, each client installation will need to be updated as soon as possible. The database will still be accessible to older client versions, but there will be warning about possible errors when using the program.

Downloading the installation and latest update files:

 Send customer the direct link or a link to our website  Fill out the download form

(3)

 wait for email with download links

o could take up to 15 minutes for web host to send the email  download software

o Depending on OS and permissions, they could get different messages about saving or running the file

 Usually at this point they should answer “Yes” to windows security messages, and choose “Save As” when prompted

Installing the software:

 Download the software (save to computer)  Run the installation file

 Press Next to begin

 Choose Yes to accept the license agreement

 Choose “Network Server” if you plan on using your own SQL Server installation, otherwise choose “Standalone System”

 Choose “Client Only” to install just the client program files (usually on a client workstation)  Press Next and review the installation options

 Press Install to begin the installation process  If there is an error running the installation:  If there is an error during the installation process

o Could be security issue, try running installer as Administrator user o Could be a corrupt download file, try downloading the setup again

o Could be a system requirements issue, check for minimum OS XP SP3, 512 RAM, hard drive free space

o Could be a prerequisite issue (.NET Framework 3.5, Windows Installer 4, SQL Native Client), try manually downloading and installing these first to resolve the issue, then install TT software

o Could be issue installing SQL Server 2008 R2 Express, check SQL install log files. Most common causes are “Waiting for Computer Restart” and “Cannot Install on Domain Controller”.

o Otherwise create a tech support ticket

Uninstalling the software:

 Always make a full database backup file before uninstallation and store it in a safe place.  Using the installation file (recommended)

o Run the original installation file o When prompted, choose “Remove”

o If asked to uninstall the SQL Server instance associated with this program, choose “Yes” o After the SQL Server is uninstalled, the program and services will be uninstalled

o Once the uninstallation is complete, you should delete the SQL data files folder  Using Control Panel

o Find the Truck Tracker program in the list and choose “Uninstall”. o When prompted, choose “Remove” and complete the uninstall wizard

(4)

o Once the uninstallation is complete, you need to uninstall the SQL Server instance associated with the program.

o In the Programs list, find SQL Server 2005 or 2008 R2 and choose “Uninstall”. o Find the instance named (TRUCKTRACKER) and uninstall the database engine o Press Next until you finish the uninstall wizard.

o Once the uninstallation is complete, you should delete the SQL data files folder

Logging into the Software

 If the user gets the “SQL Server does not exist or access denied” message, then either: o The full SQL Server name in incorrect

 <ComputerName>\TRUCKTRACKER, or <IPAddress>\TRUCKTRACKER  192.168.12.100\TRUCKTRACKER

 SERVER1\TRUCKTRACKER

 if you are using a custom sql port (any port other than default 1433), make sure to add a comma and the port number after the full sql server name

 SERVER2\TRUCKTRACKER,5432

o SQL Server not installed properly, not running, or networking not enabled?  Login to the SQL Server machine (or standalone machine)

 Open the SQL Configuration Manager under the Start Menu-All Programs-Microsoft SQL Server folder

 Check that the SQL instance is installed (TRUCKTRACKER)

 Verify SQL Server service is running and SQL Browser service is running

 The SQL Browser service is only required when multiple instance of sql installed  If networking, make sure the TCP/IP protocol is enabled for the SQL instance o Windows Firewall or other firewall software is blocking inbound connections.

 First turn off firewall completely and try to connect again. If it works after turning the firewall off, then the firewall is the problem. If it still doesn’t work then the firewall is not the problem.

 If the firewall is the problem, turn it back on, and add exceptions for the SQL Server and Browser ports. The default ports (unless manually changed) to allow incoming traffic are TCP port 1433, and UDP port 1443. Make sure the scope is wide enough and all advanced settings are allowing traffic through these 2 ports.

o Make sure the SQL Native Client library is installed on the client machine attempting to connect.

 If the client gets the “Login failed for user TruckTrackerUser” message, then:

o Run the server installation again and choose Repair. This will re-map the sql server logins to the database users.

o This can happen when they have SA module, or when they move to a new SQL Server without running the built-in restore function.

o Enter custom SQL authentication credentials on the login screen. The custom SQL login requires VIEW SERVER STATE permission and full control of TruckTracker database.  If user can’t get in because they lost the admin password:

o First try Manager/pass, try likely potential passwords, and see if another user has admin access.

(5)

o Otherwise, they need to stop sql service and send (email, upload) the TruckTracker.mdf and TruckTracker_log.ldf files from the SQL Server data folder.

o Using SQL management studio, attach database to a local instance of SQL 2005 or 2008 (match the customer)

o To reset the password for a user account, open SSECUser table and clear out the password column and enter 0 in password size column.

o Now you can send the files back to the customer, they copy them into the SQL data directory, overwriting the existing files, and restart the SQL Service

 If the client gets an error about Active Directory, then:

o Fix the AD path (query) under the user security settings.

Using the Trial Version

 When the user enters the software for the first time, they will see a “Welcome to Trial Version” splash screen and the program will run in Trial mode with record and feature limits.

 To get rid of demo data you must manually delete each record, register the full version, or reinstall the program.

Activating a Full License

 Login to software

 Choose Help menu, then select “Register Product”  Drag and drop the license.txt file onto the screen, OR:

 Enter the license details (case-sensitive) and activate software  If you receive a “failure” message, either:

o Activation code expired

 Reactivate license and try again o They entered something wrong

 Try registering the same license in-house

 if it works, email a screenshot to the user o There is a bug in the program

 Create a tech support ticket, inform customer, and escalate to next level

Downloading the latest minor version update

 If auto-updates are set to check at startup (default) then it will check automatically when the login screen is launched

 Otherwise, if you can login to the program, then you can have the program automatically check for, download and install the latest update

o Under File Menu choose “Settings”, select Auto-Updates and press “Check Now” o Under Help Menu choose “Check for Updates”

(6)

Connecting to SQL Server over network

 Is the SQL Server accessible by other client computers over the network? o Make sure SQL Server is installed and the service is running

o Make sure TCP/IP protocol is enabled on the instance of SQL (using SQL Configuration Manager)

o Make sure the SQL Server service and SQL Browser service have inbound access through the local windows firewall

 SQL Server Engine, TCP 1433  SQL Browser, UDP 1434

o If multiple SQL Servers are installed on one machine, make sure SQL Browser service is running. This is required to avoid using dynamic ports.

o Check if the service is using dynamic ports

Connecting over RDP

 Local Resources tab, select “Ports”, “Printers”, “Drives” and “Clipboard” to redirect these resources to your remote connection.

 Local Resources tab, enable “Apply Windows Key Combinations (for example ALT+TAB)” on the local computer

Deployment Overview (Installation):

Contents