You need to run BPS.vbs under an account that has enough rights to let the script access and update contacts in any account as well as read from the BESAdmin mailbox. The simplest way to make sure the script has the necessary rights is to run the script under the same service account that you use for your BlackBerry services. Alternatively, you can create a separate service account. However, creating a separate service account also creates a separate opportunity for compromise, so using the BES account is safer.
If you choose to create a separate service account, you need to grant the account rights in Exchange. The Microsoft article "XADM: How to Get Service Account Access to All Mailboxes in Exchange 2000" (http://support.microsoft.com/?kbid=262054) describes two methods to create a service account. You should use the second method. You can also follow the steps detailed in Chapter 2 of the BES Installation and Getting Started Guide. The steps are in the "Assigning further Microsoft Exchange permissions to service accounts" section.
You control the script through parameters you supply in a configuration (.cfg) file. As Figure 2 shows, the .cfg file consists of key-value pairs separated by an equal sign (=). Web Table 1 (http://www.winnetmag.com/microsoftexchangeoutlook, InstantDoc ID 41955) describes in detail the keys and the types of values to specify. The case and order of the key-value pairs in the .cfg file isn't important, but you must include all the parameters. If you omit any parameter, the script will report an error and abort. You can include comments in the .cfg file by starting the line with a semicolon.
You need to use cscript.exe to run the script. After specifying the CScript command, type the script's name followed by the .cfg file's name. For example, the command might look like
cscript BPS.vbs bes01.cfg
Alternatively, you can create a batch file that launches BPS.vbs and run the batch file as a scheduled task on the BES server, with the BES account specified as the Run As account. The script only processes one BES instance at a time. If you have more than one BES server, you need to create a .cfg file for each server and include multiple CScript commands specifying a different .cfg file each time.
A Handy Script
BPS.vbs has proved to be a handy tool for my BES deployments and has made my customer's emergency and COOP plans much more solid. Take a close look at the code in this script and see how you can incorporate or adapt it for use in your environment.