TrackAbout System Requirements

 

TrackAbout Web

TrackAbout Mobile 6 (Windows Mobile)

Handheld Devices

Internet Connectivity Speed

Firewall and Proxy Requirements

Content Distribution Network (CDN)

How To Test the CDN

TrackAbout Web

The TrackAbout Application Web site runs in a web browser. The following browsers are acceptable.

  • Microsoft Edge — Latest version.

  • Google Chrome — Latest version is generally assumed as the software auto-updates.

  • Mozilla Firefox — Latest version is generally assumed as the software auto-updates.

NOTE

Due to the amount of information available on the TrackAbout website, we recommend it not be used via a smartphone device. It is not optimized for mobile use. By default on mobile devices, the left pane navigation menu is collapsed.

TrackAbout Mobile 6 (Windows Mobile)

Handheld device synchronization requires a computer running Microsoft Windows 7 or above. Windows XP and Vista are no longer supported by Microsoft or TrackAbout.

An available USB port is required for installing TrackAbout Mobile 6 on a mobile handheld computer and for syncing with a handheld cradle.

WARNING

Windows Mobile Device Center stopped working with Windows 10 version 1709 (Fall 2017 Creator's Update). Installation on a new PC will fail. An existing installation will not run following an upgrade to this version or greater.

Several vendors of rugged mobile computers have provided workarounds. The best we've seen is from a reputable device vendor named Juniper. We have had success connecting with WMDC on a Windows 10 PC using the instructions found here.

Be advised that TrackAbout cannot and will not take responsibility for any problems caused by following the Juniper instructions. That having been said, we have tested their process ourselves to prove that it works. We've also looked inside their installers to see what they do, and as of December 15, 2017, we believe them to be safe for use. Please let us know if you encounter any problems.

Handheld Devices

For details on supported Windows Rugged devices, see TrackAbout Certified Devices.

For details on iOS or Android devices, see TrackAbout Mobile 7 .

Internet Connectivity Speed

Download speed 768 Kbps minimum.

Firewall and Proxy Requirements

Your IT department may need to permit OUTBOUND access to the following URLs/ports before you can access TrackAbout through your corporate firewall.

Can we get IP addresses?

Our customers sometimes request that we provide them with a list of IP addresses we own so they can add them to their "allow" list or within their firewalls. Due to today's modern cloud architectures, we cannot provide a static list of IP addresses. If you query the Domain Naming System (DNS) for the host names below, you will find many, if not all, of the host names resolve to CNAME alias DNS records. This is because in a cloud environment, resources are free to be redeployed without notice and are assigned new public IP addresses. While every host name will ultimately resolve to one or more IP addresses, there is no guarantee those addresses will remain the same over time.

NOTE

TrackAbout does not require specific ports be open for INBOUND traffic.

TrackAbout Web

www.trackabout.com
corp.trackabout.com
supportkb.trackabout.com
auth.trackabout.com
prod-cache.trackabout.com
ssl.google-analytics.com
dc.services.visualstudio.com/v2/track
test.trackabout.com (if using the Test environment)
trackabout-test.us.auth0.com (if using the Test environment)
test-cache.trackabout.com (if using the Test environment)

TrackAbout Mobile 7

www.trackabout.com
auth.trackabout.com
corp.trackabout.com
cdn.auth0.com
trackabout.servicebus.windows.net
in.appcenter.ms
sdk-api.scandit.com
firebaseinstallations.googleapis.com (only if using TAM7 Android)
android.apis.google.com (only if using TAM7 Android)
google.com (only if using TAM7 Android)
test.trackabout.com (if using the Test environment)
trackabout-test.us.auth0.com (if using the Test environment)

TrackAbout Mobile 6

www.trackabout.com
test.trackabout.com (if using the Test environment)

HTTP/HTTPS Ports (Outbound)

HTTP — TCP/80

HTTPS — TCP/443

Content Distribution Network (CDN)

See below.

Content Distribution Network (CDN)

TrackAbout uses a Content Distribution Network (CDN) to speed up delivery of web page parts. If your IT department enforces white-listing of specific web sites, please direct them to this page which lists the endpoints that need to be white-listed.

Every web page you load in a browser is actually made up of dozens (sometimes hundreds) of other files. These can be images, fonts, JavaScript, style sheets, and more. Most of these kinds of files do not change from page to page as you navigate a site like TrackAbout.

All those parts need to be downloaded to the browser. Requesting them all from a single server creates a bottleneck.

Instead of fetching these parts from TrackAbout’s web server, the browser will now fetch them from server caches all over the globe.

The result should be that pages load more quickly, as certain parts of every page will be served from servers as close to you as possible.

For Production, whitelist prod-cache.trackabout.com ports 80 and 443

For Test, whitelist test-cache.trackabout.com ports 80 and 443

How To Test the CDN

Use your corporate standard browser, whether it's Chrome, Firefox, Microsoft Edge, etc.

  • Open your browser

  • Navigate to https://test.trackabout.com

  • Open your browser's Dev Tools (usually F12, or find it in the menu)

  • Switch to the Network tab.

  • Do a "force refresh" of the web page ( or ). This forces the browser to request every object inside the page fresh, rather than loading it from your browser's local cache as it normally would.

The Network tab should fill with requests, showing all the components of the login page.

You should see all requests completing successfully with a status code in the 200s.

You should see many requests being served from the domain mentioned above, such as prod-cache.trackabout.com or test-cache.trackabout. That is the CDN server.

If you see any requests with statuses in the 300-range, then you did not force refresh the page. Try again.

If you see any requests in the 400s or 500s for CDN-served resources, then there's a problem. Your network or workstation may be set up to block certain web endpoints on which TrackAbout depends.

If you are unsure how to resolve errors in the 400-599 range, please email support@trackabout.com and open a ticket.