IMPORTANT: The following steps outline changes to a configuration file used by the BlackBerry Mobile Data Service. Please ensure you have a backup copy before making any changes to the original file.

In order for PINpoint to determine from which BlackBerry device a request is originating, the Mobile Data Service of your BlackBerry Enterprise Server must be configured to include the email address and PIN number with each HTTP request from the BlackBerry Browser. Follow these steps:

1. On the BlackBerry Enterprise Server, browse to MDS config subdirectory:
   • For Microsoft Exchange or Novell GroupWise, browse to: c:\program files\research in motion\blackberry enterprise server\MDS\servers\<server_name>\config\
   • For IBM Lotus Domino, browse to: c:\program files\research in motion\blackberry enterprise server\MDS\servers\instance\config\
2. Create a backup copy of the rimpublic.property file.
3. Open the rimpublic.property file with Notepad or a similar text editor.
4. Add the following lines to the end of the file:
   [HTTP HANDLER]
   application.handler.http.header=email,pin
5. Save the file.
6. Restart the BlackBerry Mobile Data Service from the BlackBerry Manager or Services control panel.

PINpoint v2.x (versions below v3.0) require Microsoft .Net Framework v1.1, which is only available in 32-bit mode.

Please refer to our Technical Note, to enable 32-bit operation in a 64-bit server.

An ASP.net application deployed on a IIS6/IIS7 server runs under the identity defined at application pool level unless the current logged in user is impersonated programmatically. PINpoint never impersonates the current logged in user.

Microsoft's recommendation is to set the application pool to point to the built-in Network Service account. This account is a low privileged account that satisfies the rights required by a web application to function.

Because the Network Service account is a low privileged account it does not have rights to create/update any files on the file system. At run time PINpoint needs to be able to update application specific files that are stored in the Logs and Resources folders. At installation time PINpoint grants full rights to the Network Service account to the above mentioned folders in the file system (PINpointRootFolder\Logs and PINpointRootFolder\Resources).

The PINpoint application will open connections to the BES SQL Server every time:

• When data is pushed to BlackBerry devices
• When the PINpoint list is refreshed from the device side
• When the PINpoint Administrator is using the PINpoint management Console.

Please see below a description of how PINpoint interfaces with the BES SQL server:

1. PINpoint relies only on SQL authentication. Because of this the BES SQL server should be set-up to support Mixed Authentication.
2. At installation time PINpoint Standard Edition creates the following objects in the BESMgmt database:
   • A role called PINpoint_DataReader
   • Three in-line functions: USR_PINPOINT_GET_BLACKBERRY_USER, USR_PINPOINT_GET_BLACKBERRY_USERS, USR_PINPOINT_GET_CONTENT_LIST
   • The installer will grant SELECT rights to the above In-line functions to the PINpoint_DataReader role. [NB. in a more restricted environment this step could be skipped at installation time: the application ships with the actual SQL scripts that could be handed on to a DBA to run them manually.]
3. Our recommendation is to create a SQL Login that will be used by the PINpoint application to open connections to the BESMgmt database. This login at server level should be member of the public role and at BESmgmt database level should be mapped to a User that is member of the Public role and PINpoint_DataReader.
4. At PINpoint level at configuration time, the above login should be used to set-up the SQL Connection to the BESMgmt Database. This will limit the capabilities the PINpoint application has at SQL level to the three in-line functions specific to the PINpoint application.

1. PINpoint application needs to be able to reach the BES/MDS Server by name or IP Address over HTTP.
2. The server(s) where BES and MDS are hosted need(s) to be able to reach the web server where PINpoint is installed by Name.
3. PINpoint needs to be able to send a SQL Ping to the SQL Server (only applies to the Enterprise version for the secondary BES Database Servers).
4. Our recommendation is to host PINpoint on an internal server, not an external one.

[NB. a SQL Ping, as opposed to a normal ICMP Ping, will actually test if anything listens to port 1434 on the machine where the SQL Server is hosted].

Do the following:

1. Go to the Blackberry Manager.
2. Click Servers.
3. Select BlackBerry MDS connection service.
4. In the right pane, set as a push server or check if it is not already configured as such.
5. Stop and restart the service.

Do the following:

1. Go to BlackBerry Manager.
2. Go to the Connection Service tab.
3. Click Edit Properties.
4. Click Push/PAP and on the drop down list, select True.
5. Click Ok.
6. Click Restart Service.

At installation time, PINpoint attempts to create a local group called PINpointManagers and makes the current user (the installer's) account a member of this group.

The PINpoint installation automatically grants access rights to the local PINpointManagers group. This can be easily reconfigured through the applications's Web.config file (search for "authorization").

Please check if the group PINpointManagers was created on the local machine and the user you are trying to use is a member of it.

The steps required to upgrade the license are as follows:

1. Back-up the file called PINpoint.ini stored within the Resources folder under the root of the PINpoint application. 
2. Uninstall the current PINpoint version using the Add/Remove feature (the PINpoint configuration settings are not removed during this step).
3. Install the new PINpoint version with the new license key provided and it should pick up all the existing configuration settings.

[Note: you must have an active maintenance agreement to receive support and upgrades to PINpoint.]