Skip to main content
Click here if you are having trouble viewing this site
Older versions of Internet Explorer will not support certain site features. Chrome, Safari, Firefox, and Edge will provide the best experience.
Resources
Spok

Spok Mobile Pre-Implementation Configurations

  1. Last updated
  2. Save as PDF
This page describes the pre-implementation configurations that a Spok PSG representative will perform to set up a shared Asset Directory and configure the Microsoft Distributed Transaction Coordinator Settings for SQL Server mirroring or AlwaysOn (if applicable).

Configure the Microsoft Distributed Transaction Coordinator Settings

This prerequisite is only required for Spok Mobile instances that use a SQL Server mirroring or AlwaysOn configuration. For more details about setting up a mirrored SQL server or an AlwaysOn Spok Mobile implementation, see Configuring SQL Server Redundant Mirroring Sessions, and Preparing for a Spok Mobile Implementation with AlwaysOn.

When configuring Spok Mobile, configure the server to use a static IP address. The server should never use a dynamic host configuration protocol (DHCP) for an IP address assignment.

Reply messages from a Spok Mobile client may be lost in any of the following situations:

  • The connection between the ISF/Mobile Enablement Plugin and Spok Mobile is broken.
  • The network cable is physically disconnected.
  • An administrator disables the server's network card.
  • A physical server suddenly loses power
  • A virtual server is de-provisioned or suspended.

In any of these cases, the Windows operating system on the Spok Mobile server will not be able to detect a break in the TCP connection with the ISF/Mobile Enablement Plugin server.

These risks can be mitigated by properly shutting down the Windows server before changing any necessary physical or virtual components. This allows for failover to occur and operations to function as normal.

Configuring a Shared Location for Assets

Spok Mobile requires a shared location to store and share its uploaded assets, such as profile pictures and message attachments, regardless of whether or not you are setting up a fault-tolerant environment. This shared folder is called the Assets Upload Directory Location. In order to run a fault-tolerant environment, you must make this folder accessible from both the Care Connect Platform server and the Spok Mobile server. The Assets Upload Directory Location cannot be on a local path (for example: c:/folder), and must be configured in a fault-tolerant location. You can create shared folders through the Create a Shared Folder Wizard or by right-clicking on the folder, choosing the Share with menu option, configuring the sharing options by enabling Read/Write or Full rights access, and then clicking Share.

To set up the Assets Upload Directory, do the following:

  1. Add a user or service account with a username such as "CareConnect" to all Windows systems which the Care Connect Suite systems will use. This includes the Primary Platform server, the Spok Mobile server, the Secondary Platform server, the Spok Mobile server, and the system which will host the Assets Upload Directory. When you create this user account, observe the following best practices:
  • Do not set the password for this account to expire.
  • Do set the same password across all systems on which you create this account.
  • Do not disable this account.
  • Do not change the account password when you first log in.
  • Do add this user to a super user or administrators group.
  1. Create the Shared Assets directory in a fault-tolerant location. 
  2. Give the user/service account Read/Write permissions to the shared location.