cDir persists the configuration data in a file called cDir.ini under the Resources folder.
If insufficient file access rights are granted to the identity under which the cDir application runs, it will fail to persist the data.

Follow these steps to fix the problem:

1. Find the identity under which cDir runs (in IIS Manager, look at application pool level>>Properties>>Identity)
2. At the file system level grant Write rights to the above identity for the Resources and Logs folders.

Yes, do the following to display the corporate logo on the Search page of the mobile devices:

1. Locate the Web.config file stored under the root of the cDir application (the default location is yourDriveLetter:\\inetpub\wwwroot\cDir)
2. Create a back-up of the Web.config file
3. Open the Web.config file using Notepad
4. Locate the key called " Search.Custom.Form.Logo.Image.Path "
5. Change the “value” attribute to point to the absolute URL of your corporate logo image. If desired the image could be stored under the Img folder within the root of cDir application. In that case you could use a relative URL for the “value” attribute (e.g. Img/YourLogo.png)

The following link types are supported:

• Mailto: link this field to create an email
• PIN: links the field with a PIN-to-PIN message.
• Tel: link this field to link to a phone call. Also filters the phone numbers and remove any extra character to make it compatible with device phone numbers call.
• Details: when selected means that this field is linked to the detail screen.
• Subquery: Allows create subquerys that can relate one directory with another.
• Mashup: use this link type when is desired to embed the output of the specified URL within the details page of cDir.
  • Note: cDir ships with a proof of concept example for mashup link, called BESQuery.
• Other: normally used to setup a generic hyperlink associated with a field.

Yes, prefix the Display Label field value with "__" (two underscores).

First check this website to see if we have released an update that supports your new device. We typically release updates for the most popular devices, as we did for Apple iPhone/iTouch, and for BlackBerry's Storm, Odin, Tour and Bold. You can also contact us to check if we are working on an imminent release.

If we have not released an update or you want to "tweak" cDir to do your bidding, you need to add the new device model to the Web.config file stored under the root of the cDir application. The following describes how to update for a new BlackBerry smartphone:

1. Locate the browser capabilities element, called <browserCaps>.
2. Within the browserCaps element go to the first <case> element that matches a BlackBerry device.
3. Within that case element go to the <filter> element.
4. Locate the last <case> element within the filter element. Select, copy and paste it just before the closing tag of the filter element (</filter>).
5. Modify the pasted case element to reflect the settings of the new BlackBerry device.

Yes, this is done by defining User Groups and granting rights to the Directory and LDAP Object, as follows:

1. Launch cDir Management Console.
2. Go to Users & Access tab.
3. Select User Groups tab.
4. Click Add New Group button.
5. Define a new Users Group (see cDir Installation Guide >> Assign User Access Rights section for more details).
6. To change the rights to a Directory go to Directories tab.
7. Edit the corresponding Directory.
8. In the Visible To section, click arrow to move the desired group from Available to Selected.
9. Click Save to persist the settings.
10. To change the rights for a LDAP Object go to LDAP Objects tab.
11. Edit the corresponding LDAP Object.
12. In the Visible to section move the desired group from Available to Selected.
13. Click Save to persist the settings.

The following connectivity is required:

1. The cDir 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 access the web server where cDir is installed by Name over HTTP.
3. cDir 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).

Our recommendation is to host cDir on an internal server, not an external one.

[* 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].

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

• When the cDir shortcut is pushed to BlackBerry devices.
• When the cDir shortcut is pushed to a predefined group of recipients.
• When BESQuery is invoked either from the server side or from the client side.

1. cDir relies only on SQL authentication. Because of this the BES SQL server should be set-up to support Mixed Authentication.
2. At installation time cDir creates the following objects in the BESMgmt database:
   • A role called cDir_DataReader
   • Two in-line functions: USR_CDIR_GET_BLACKBERRY_USER, USR_CDIR_GET_BLACKBERRY_USERS
   • The installer will grant SELECT rights to the above in-line functions to the cDir_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 cDir 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 cDir_DataReader.
4. At cDir 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 cDir application has at SQL level to the three in-line functions specific to the cDir application.

An ASP.net application deployed on a IIS6/IIS7 server runs under the identity defined at application pool level unless the currently logged in user is impersonated programmatically. cDir 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 privilege 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 cDir needs to be able to update application specific files that are stored in the Logs and Resources folders. At installation time cDir grants full rights to the Network Service account to the above mentioned folders in the file system (cDirRootFolder\Logs and cDirRootFolder\Resources).

To display properly, cDir requires HTML, CSS and Javascript to be enabled in the browser.