More Pieces

When your computer hardware appears to power up okay, but the Windows XP operating system won’t boot properly, you have to begin a troubleshooting expedition that includes getting into the operating system, determining the problem, and then fixing it. To help you get started on this expedition, here are some things you can do when Windows XP won’t boot.

Use a Windows startup disk

One of the first things you should reach for when troubleshooting a Windows XP boot problem is a Windows startup disk. This floppy disk can come in handy if the problem is being caused when either the startup record for the active partition or the files that the operating system uses to start Windows have become corrupted.

To create a Windows startup disk, insert a floppy disk into the drive of a similarly configured, working Windows XP system, launch My Computer, right-click the floppy disk icon, and select the Format command from the context menu. When you see the Format dialog box, leave all the default settings as they are and click the Start button. Once the format operation is complete, close the Format dialog box to return to My Computer, double-click the drive C icon to access the root directory, and copy the following three files to the floppy disk:

• Boot.ini

• NTLDR

• Ntdetect.com

After you create the Windows startup disk, insert it into the floppy drive on the afflicted system and press [Ctrl][Alt][Delete] to reboot the computer. When you boot from the Windows startup disk, the computer will bypass the active partition and boot files on the hard disk and attempt to start Windows XP normally.

Use Last Known Good Configuration

You can also try to boot the operating system with the Last Known Good Configuration feature. This feature will allow you to undo any changes that caused problems in the CurrentControlSet registry key, which defines hardware and driver settings. The Last Known Good Configuration feature replaces the contents of the CurrentControlSet registry key with a backup copy that was last used to successfully start up the operating system.

To use the Last Known Good Configuration feature, first restart the computer by pressing [Ctrl][Alt][Delete]. When you see the message Please select the operating system to start or hear the single beep, press [F8] to display the Windows Advanced Options menu. Select the Last Known Good Configuration item from the menu and press [Enter].

Keep in mind that you get only one shot with the Last Known Good Configuration feature. In other words, if it fails to revive your Windows XP on the first attempt, the backup copy is also corrupt.

Use System Restore

Another tool that might be helpful when Windows XP won’t boot is System Restore. System Restore runs in the background as a service and continually monitors system-critical components for changes. When it detects an impending change, System Restore immediately makes backup copies, called restore points, of these critical components before the change occurs. In addition, System Restore is configured by default to create restore points every 24 hours.

Use Recovery Console

When a Windows XP boot problem is severe, you’ll need to use a more drastic approach. The Windows XP CD is bootable and will provide you with access to a tool called Recovery Console.

To boot from the Windows XP CD, insert it into the CD-ROM drive on the problem system and press [Ctrl][Alt][Delete] to reboot the computer. Once the system begins booting from the CD, simply follow the prompts that will allow the loading of the basic files needed to run Setup. When you see the Welcome To Setup screen, press R to start the Recovery Console.

You’ll then see a Recovery Console menu. It displays the folder containing the operating system’s files and prompts you to choose the operating system you want to log on to. Just press the menu number on the keyboard, and you’ll be prompted to enter the Administrator’s password. You’ll then find yourself at the main Recovery Console prompt.

Fix a corrupt boot.ini

As the Windows XP operating system begins to load, the Ntldr program refers to the Boot.ini file to determine where the operating system files reside and which options to enable as the operating system continues to load. So if there’s a problem rooted in the Boot.ini file, it can render Windows XP incapable of booting correctly.

If you suspect that Windows XP won’t boot because Boot.ini has been corrupted, you can use the special Recovery Console version of the Bootcfg tool to fix it. Of course, you must first boot the system with the Windows XP CD and access the Recovery Console.

To use the Bootcfg tool, from the Recovery Console command prompt, type

Bootcfg /parameter

Where /parameter is one of the required parameters listed in the table below.

Parameter

Description

/Add

Scans the disk for all Windows installations and allows you to add any new ones to the Boot.ini file.

/Scan

Scans the disk for all Windows installations.

/List

Lists each entry in the Boot.ini file.

/Default

Sets the default operating system as the main boot entry.

/Rebuild

Completely re-creates the Boot.ini file. The user must confirm each step.

/Redirect

Allows the boot operation to be redirected to a specific port when using the Headless Administration feature. The Redirect parameter takes two parameters of its own:

[Port Baudrate ] | [UseBiosSettings].

/Disableredirect

Disables the redirection.

Fix a corrupt partition boot sector

The partition boot sector is a small section of the hard disk partition that contains information about the operating system’s file system (NTFS or FAT32), as well as a very small machine language program that is crucial in assisting the operating system as it loads.

If you suspect that Windows XP won’t boot because the partition boot sector has been corrupted, you can use a special Recovery Console tool called Fixboot to fix it. Start by booting the system with the Windows XP CD and accessing the Recovery Console.

To use the Fixboot tool, from the Recovery Console command prompt, type

Fixboot [drive]:

Where [drive] is the letter of the drive to which you want to write a new partition boot sector.

Fix a corrupt master boot record

The master boot record occupies the first sector on the hard disk and is responsible for initiating the Windows boot procedure. The master boot record contains the partition table for the disk as well as a small program called the master boot code, which is responsible for locating the active, or bootable, partition, in the partition table. Once this occurs, the partition boot sector takes over and begins loading Windows. If the master boot record is corrupt, the partition boot sector can’t do its job and Windows won’t boot.

If you suspect Windows XP won’t boot because the master boot record has been corrupted, you can use the Recovery Console tool Fixmbr to fix it. First, boot the system with the Windows XP CD and access the Recovery Console.

To use the Fixmbr tool, from the Recovery Console command prompt, type

Fixmbr [device_name]

Where [device_name] is the device pathname of the drive to which you want to write a new master boot record. For example, the device pathname format for a standard bootable drive C configuration would look like this:

\Device\HardDisk0

Disable automatic restart

When Windows XP encounters a fatal error, the default setting for handling such an error is to automatically reboot the system. If the error occurs while Windows XP is booting, the operating system will become stuck in a reboot cycle—rebooting over and over instead of starting up normally. In that case, you’ll need to disable the option for automatically restarting on system failure.

When Windows XP begins to boot up and you see the message Please select the operating system to start or hear the single beep, press [F8] to display the Windows Advanced Options Menu. Then, select the Disable The Automatic Restart On System Failure item and press [Enter]. Now, Windows XP will hang up when it encounters the error and with any luck, it will display a stop message you can use to diagnose the problem.

Restore from a backup

If you can’t seem to repair a Windows XP system that won’t boot and you have a recent backup, you can restore the system from the backup media. The method you use to restore the system will depend on what backup utility you used, so you’ll need to follow the utility’s instructions on how to perform a restore operation.

Perform an in-place upgrade

If you can’t repair a Windows XP system that won’t boot and you don’t have a recent backup, you can perform an in-place upgrade. Doing so reinstalls the operating system into the same folder, just as if you were upgrading from one version of Windows to another. An in-place upgrade will usually solve most, if not all, Windows boot problems.

Performing a Windows XP in-place upgrade is pretty straightforward. To begin, insert the Windows XP CD into the drive, restart your system, and boot from the CD. Once the initial preparation is complete, you’ll see the Windows XP Setup screen (shown earlier in Figure A). Press [Enter] to launch the Windows XP Setup procedure. In a moment, you’ll see the License Agreement page and will need to press [F8] to acknowledge that you agree. Setup will then search the hard disk looking for a previous installation of Windows XP. When it finds the previous installation, you’ll see a second Windows XP Setup screen.

This screen will prompt you to press R to repair the selected installation or to press [Esc] to install a fresh copy of Windows XP. In this case, initiating a repair operation is synonymous with performing an in-place upgrade, so you’ll need to press R. When you do so, Setup will examine the disk drives in the system. It will then begin performing the in-place upgrade.

Keep in mind that after you perform an in-place upgrade or repair installation, you must reinstall all updates to Windows.

Published: September 17, 2004

This guide describes how to create the first domain controller for a new child domain and how to configure an additional domain controller for replication within a child domain.

Overview

The following sections demonstrate the procedures required for configuring a computer running Windows Server 2003 as the first domain controller in a child domain. An additional domain controller within the child domain will be configured to function as a replication partner.

An Active Directory service deployment consists of one or more forests with each forest having one or more domains. Creating the initial domain controller (DC) in a network creates the first domain in a forest—you cannot have a domain without at least one domain controller. The first domain created is the root domain of the first forest. Additional domains in the same domain forest may be child domains or tree root domains. A domain immediately above another domain in the same domain tree is considered its parent.

Domains are used to accomplish network management goals, such as structuring the network, delimiting security, applying Group Policy, and replicating information.

Active Directory allows domain controllers to function as peers—therefore, clients can update Active Directory on any of the Windows Server 2003 domain controllers in the domain. This is a significant change from the read-write/read-only roles played by Windows NT^® Server Primary Domain Controllers (PDCs) and Backup Domain Controllers (BDCs). The Windows NT Server domain system supports single-master replication requiring all changes to be made on the PDC.

The Windows Server 2003 operating system supports multi-master replication—all of a domain’s domain controllers can receive changes made to objects and can replicate those changes to all other domain controllers in that domain. By default, the first domain controller created in a forest is a global catalog server, which contains a full replica of all objects in the directory for its domain and a partial replica of all objects stored in the directory of every other domain in the forest.

Replicating Active Directory data among domain controllers provides benefits for information availability, fault tolerance, load balancing, and performance. In this step-by-step guide, you can take advantage of the greater fault tolerance provided in the multi-master model by installing multiple domain controllers. In the event a domain controller stops working, the availability of Active Directory is not compromised.

Creating Additional Domain Controllers

The following steps should be performed on a computer that has Windows Server 2003 installed and is connected to the common network infrastructure created in Prerequisites in this guide.

Best Practice: While not strictly required, Microsoft highly recommends that all domain controllers, DNS and Dynamic Host Configuration Protocol (DHCP) servers, routers, and printers within the common infrastructure be assigned static Internet Protocol (IP) addresses.

Configuring Static IP addresses

Configuring a Child Domain

Configuring a Replication Partner

The Role of Sites in Active Directory Replication

Sites enable the replication of directory data both within and among sites. Active Directory replicates information within a site more frequently than across sites, implying that better connected domain controllers receive updates first. The domain controllers in other sites will receive all updates to the directory, although, to reduce the bandwidth requirements for slower network connections, updates are scheduled to occur less frequently.

A site is delimited by a subnet and is usually geographically bound. Sites differ in concept from Windows Server 2003–based domains in that sites can span multiple domains, and a domain can span multiple sites. Sites are not part of the domain namespace but they do control replication of domain information and help determine resource proximity. For example, a workstation will select a domain controller within its site against which to authenticate.

Directory information can be exchanged using the following replication transports: Remote Procedure Call (RPC) over Transmission Control Protocol/Internet Protocol (TCP/IP) and Simple Mail Transfer Protocol (SMTP). For information about configuring sites, subnets, and IP-based replication, see the Step-by-Step Guide to Active Directory Sites and Services.

To take advantage of multi-master replication, you can set up another domain controller to serve as a replication partner for the first domain controller in the Vancouver child domain.

Configuring an Additional Domain Controller as a Replication Partner

To configure an additional domain controller as a replication partner

12.

Once the Active Directory Installation Wizard completes, click Finish, and then click Restart Now to reboot your system.

SYMPTOMS

When users try to log on the Microsoft Outlook Web Access (OWA), they may receive one of the following error messages:

401.3 Access Denied by ACL on Resource - Internet Information Services

-or-

A Runtime Error has occurred.
Do you wish to Debug?
Line: 350

-or-

Error: Access is denied.

CAUSE

This issue occurs if the Authenticated Users group does not have access permissions to the Exchsrvr\exchweb folder.

RESOLUTION

To resolve this issue, follow these steps:

1. Start Windows Explorer, right-click the drive:\Program Files\Exchsrvr folder, and then click Properties, where drive refers to the drive letter of your system drive (typically it is C).

2. Click the Security tab, and then click to select the Allow inheritable permissions from parent to propagate to this object check box.

3. Click Apply.

4. Make sure that the Authenticated Users group has the following permissions in the Exchsrvr\exchweb folder:

• Read & execute
• List Folder Contents
• Read

If the Authenticated Users group does not have these permissions, set these permissions manually. Close the exchweb Properties dialog box.

5. Repeat steps 1-4 on the C:\Program Files\Common Files\Microsoft Shared folder.

6. Click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.

7. Right-click your server, and then click Restart IIS.

8. In the What do you want IIS to do list, click Restart Internet Services on Server Name, and then click OK.

9. Click Start, point to Programs, point to Administrative Tools, and then click Services to open the Services dialog box.

10. Restart all Exchange services.

11. Close the Services dialog box.

Found this useful article from Jim Aspinwall.

To perform this hack you will need:

• A #1 or #2 Phillips-head screwdriver, or (less likely) a T-15 TORX driver or a 1/4″ hex nutdriver, to open the case

• Needle-nosed pliers if you are working with jumpers

• A small flashlight or headlamp

With tools at hand, perform the following steps:

1. Turn the PC off (this means a total shutdown, not merely standby or hibernate mode) and disconnect the AC power cord.

2. Remove the cover from your system (this step may require tools, undoing a thumbscrew, or flipping a latch or two).

3. Refer to the user manual for the motherboard to find out how to “reset CMOS” memory. You may also find a label for specific jumper or switch settings marked on the system board.

4. Change the switch setting or jumper position to a specific position or remove the jumper entirely as prescribed in the manual to clear or reset the CMOS memory.

5. Wait 20–30 seconds for the memory to clear out from lack of power.

6. After 20–30 seconds put the switch or jumper the way it was before for normal use.

7. Reconnect the power cord and start up the system to see if the settings have changed to defaults.

8. Shut the PC down, disconnect the power cord, replace the cover, reconnect the power, and power up the PC.

9. Enter the BIOS setup program to configure the system as needed. This may include setting the date and time, selecting disk drive parameters and selecting which devices the system uses to boot up with first.

If your system does not have a “reset CMOS” jumper or switch , the only option is to locate and remove the coin-style battery cell (or on some very old PCs, the battery pack), that provides the power to the CMOS memory.

Follow Steps 1 and 2 above, locate the battery, and remove it.

Leave the battery out of the system for 20–30 seconds, replace it, and start up the system.

The CMOS memory in some systems may retain settings longer than others.

If the CMOS memory does not clear and you’re still stuck, you may need to leave the battery out for several hours before reinstalling it. Once the system is able to perform P.O.S.T. and to start booting up the system, you will need to get into the Setup program for the BIOS and make a few basic adjustments, such as:

• Setting the date and time

• Selecting auto-detect or manually setting specific parameters for IDE hard drives

/A open file as ansi
/W open file as unicode
/P print filename
/PT

Blackberry Support KB12487

Environment

• BlackBerry® device
• BlackBerry Enterprise Server software version 4.0 and later

Procedure

Before making any significant configuration changes to a BlackBerry device (for example, installing or downloading applications, or loading new BlackBerry Device Software), BlackBerry device users should back up the data on the BlackBerry device. In the event of any problems, this will make sure the data (that is as current as of the last backup) can be restored.

BlackBerry device users can perform a full or selective backup of the data using the Backup and Restore tool in BlackBerry Desktop Manager by completing the following steps:

1) Connect the BlackBerry device to the computer running BlackBerry Desktop Manager.
2) Open BlackBerry Desktop Manager.
3) Double-click Backup and Restore.
4) Select Backup to perform a full backup or select Advanced to perform a backup of specific databases.
5) Choose a location to save the backup file, then click Save.

If you are running BlackBerry Device Software 4.0 or later and the BlackBerry device is connected to a BlackBerry Enterprise Server running software version 4.0 or later, there is a wireless backup process that can archive certain information for BlackBerry device users. Depending on the BlackBerry Device Software version, the following information cannot be archived:

BlackBerry Device Software 4.2

• Email messages
• Multimedia Message Service (MMS) messages

Note: In BlackBerry Enterprise Server software version 4.1, there is an option for archiving personal information number (PIN) messages and Short Message Service (SMS) messages using an IT policy.

• Content Store (for example, ring tones and pictures)
• Group addresses

BlackBerry Device Software 4.1

• Email messages
• MMS messages

Note: In BlackBerry Enterprise Server software version 4.1, there is an option for archiving PIN messages and SMS messages using an IT policy.

• BlackBerry Messenger Contacts
• Content Store (for example, ring tones and pictures)
• Group addresses

BlackBerry Device Software 4.0 to 4.0 Service Pack 2

• All message types
• Saved messages
• BlackBerry Messenger Contacts
• Content Store (for example, ring tones and pictures)
• Group addresses
• SureType® Learning Date (through the Learning Data Manager)

Refer to RIM’s KB12487 for full details.

Blackberry Support KB12128

Environment

• BlackBerry® 8800 smartphone

Procedure

To locate the Global Positioning System (GPS) screen, complete the following steps:

On the BlackBerry smartphone Homescreen, go to Options > Advanced Options > GPS.

To refresh your GPS location, complete the following steps:

1) Verify that your BlackBerry smartphone is exposed to open sky.
2) In the GPS screen, click the Menu key and then Refresh GPS. The longitude and latitude coordinates for your current location appear.

Refer to RIM’s KB12128 for full details.

Blackberry Support KB10437

Environment

• BlackBerry® Enterprise Server software version 4.0 Service Pack 1 (4.0.1)
• Microsoft® Exchange

Problem

The wireless calendar synchronization process is not working both ways from the BlackBerry device to the email client after the Microsoft Exchange database was restored.

Cause

The Microsoft Exchange database crashed and the BlackBerry device user’s mailbox was restored using the eseutil/p command.

Resolution

To resolve this issue, use the DBClean utility to remove all data and settings from the BlackBerry device user’s mailbox. Contact the wireless service provider for instructions on how to use the DBClean utility.

Refer to RIM’s KB10437 for full details.

Blackberry Support KB05270

Environment

• BlackBerry® Enterprise Server software version 2.1 through 4.1
• BlackBerry® Mobile Data System (BlackBerry MDS)
• Microsoft® Exchange 5.5, Microsoft Exchange 2000, and Microsoft Exchange 2003
• Microsoft Windows® 2000
• Microsoft Windows Server® 2003

Problem

Wireless calendar synchronization occurs one-way only, from the Microsoft Outlook® Calendar to the BlackBerry device Calendar. The initial wireless calendar synchronization process was successful.

Cause

This issue may be caused by one of the following:

1) The BlackBerry Enterprise Server services are not running under the BlackBerry Enterprise Server service account.
2) The BlackBerry Enterprise Server service account does not have the appropriate permissions.
3) The Collaboration Data Object (CDO) is not present or supported with the Microsoft Exchange environment.
4) The BlackBerry Enterprise Server service account is a Domain Administrator.

Resolution

Complete the appropriate resolution for your cause:

Cause 1

The BlackBerry Enterprise Server services are not running under the BlackBerry Enterprise Server service account.

Resolution

Verify that all BlackBerry Enterprise Server services are running under the appropriate BlackBerry Enterprise Server service account.

Note: Several BlackBerry Enterprise Server services run under the Local System account (for example, the BlackBerry Attachment Service or the BlackBerry MDS Services - Apache Tomcat™ Service).

To confirm that the correct account is specified, complete the following steps:

1) In Administrative Tools, select Services and double-click BlackBerry Service.
2) From the Log On tab, verify that the correct BlackBerry Enterprise Server service account name is specified.
3) If a different BlackBerry Enterprise Server service account name is specified, complete one of the following steps:

• If the BlackBerry Enterprise Server was installed using the administrator account or another administrative account, switch the service account to the BlackBerry Enterprise Server service account.

For instructions, see the following article:

• For BlackBerry Enterprise Server software versions 4.0 and 4.1, see KB04293.

OR

• If the BlackBerry Enterprise Server was installed using the BlackBerry Enterprise Server service account, switch the service account to the one that corresponds to the BlackBerry Enterprise Server services.

Note: This occurs if a BlackBerry Enterprise Server service pack or hotfix was not installed using the BlackBerry Enterprise Server service account.

Cause 2

The BlackBerry Enterprise Server service account does not have the appropriate permissions.

Resolution

To update BlackBerry device users’ mailboxes, the appropriate permissions are needed. Modify the BlackBerry Enterprise Server service account permissions by completing the following steps:

Microsoft Exchange Server 2000 and Microsoft Exchange Server 2003

1) In the Exchange System Manager, right-click the Exchange administrative group name and click Delegate Control.
2) Click Next, then click Add to open the Delegate Control window.
3) Click Browse to open the Select Users, Computers or Groups window, and select the new service account.
4) From the Role drop-down list, select Exchange View Only Administrator and click OK.
5) Click Next, then click Finish.
6) Open Exchange System Manager, and go to Administrative Groups/First Administrative Group/Servers.
7) Right-click the Microsoft Exchange Server name, click Properties, then click the Security tab.
8) Verify the Allow inheritable permissions from parent to propagate to this object check box is selected.
9) Choose the service account name and select the appropriate check boxes to allow Administer information store,Receive As, and Send As permissions.
10) Verify that no denied permissions are selected for the service account.
11) Click Apply, then clickOK.
12) In Administrative Tools, select Active Directory Users and Computers.
13) Right-click the BlackBerry Enterprise Server service account, then click Properties.
14) On the Member of tab, verify that Domain Users is displayed in the list.
15) If the BlackBerry Enteprise Server is installed on a domain controller, verify that Administrators is listed.

Important: Make sure that the service account is not a member of any groups which can deny some of these required permissions. For more information, see KB04557.

Cause 3

The Collaboration Data Object (CDO) is not present or supported with the Microsoft Exchange environment.

Resolution

Verify that the CDO.DLL file is supported with the Microsoft Exchange environment.

For Microsoft Exchange 2000 and Microsoft Exchange 2003

1) Go to the Exchsrvr\bin directory to check the version of the CDO.DLL file on your Microsoft Exchange Server.
2) Verify that the CDO.DLL file on the BlackBerry Enterprise Server is the same or later version of the CDO.DLL file on the Microsoft Exchange Server.

Note: If multiple versions of the CDO.DLL file exist, verify that all copies match.

3) At a command prompt, go to the directory where the CDO.DLL file is located.
4) Type regsvr32 cdo.dll, and press ENTER. A confirmation will display indicating that the file registered successfully.

Note: For information on how to obtain and apply the CDO.DLL file, see KB02937.
To verify that the CDO.DLL file is registered, see KB04912.

Cause 4

The BlackBerry Enterprise Server service account is a Domain Administrator.

Resolution

Verify that the BlackBerry Enterprise Server service account is not a Domain Administrator.

Additional Information

If the BlackBerry Enterprise Server service account is a member of the Domain Administrators or Enterprise Administrators groups, the Send As permission will automatically be revoked. Without the Send As permission, the BlackBerry Enterprise Server will not be able to update the BlackBerry device user’s calendar on the Microsoft Exchange Server. Verify that the service account does not inherit this role from Microsoft Active Directory® groups, such as Domain Administrators, or is not a member of this role.

KB02466 provides information on one-way calendar synchronization when connected to BlackBerry Enterprise Server software version 3.5.

KB03784 provides information on the Windows Server 2003 domain controller memory leak that affects wireless calendar synchronization.

Article 821897 on the Microsoft Support Knowledge Base provides additionaly information on how to assign service account access to all mailboxes in Microsoft Exchange Server 2003.

Refer to RIM’s KB05270 for full details.

Blackberry Support KB05130

Environment

• BlackBerry® Desktop Software 4.1
• BlackBerry device
• BlackBerry Enterprise Server
• Microsoft® Outlook®

Background

You can set up BlackBerry Desktop Manager to reconcile the messages on your BlackBerry device with a Microsoft Outlook Personal Stores file (PST) on your computer. The reconciliation process can be performed manually, or it can be performed automatically each time you connect your BlackBerry device to your computer. Additionally, you can set BlackBerry Desktop Manager to reconcile messages from your BlackBerry device.

Procedure

To reconcile messages using BlackBerry Desktop Manager, complete the following steps:

1. Connect your BlackBerry device to your computer.
2. In BlackBerry Desktop Manager, open Intellisync.
3. Click Configure reconciliation.
4. In the Personal Folder section, from the Personal Folder drop-down list, select the PST file you want to reconcile with your BlackBerry device.
5. Click OK.
6. Complete one of these tasks:

• To reconcile manually, select the Reconcile messages check box and click Synchronize Now. Your messages will be reconciled with the selected PST file.

• To reconcile automatically, click Auto Start. Select the Reconcile messages check box, and click OK. Your messages will be reconciled with the selected PST file the next time you connect your BlackBerry device to your computer.

7. Click Close.

To reconcile messages using your BlackBerry device, complete the following steps:

Note: The BlackBerry device user must be on a BlackBerry Enterprise Server or using the BlackBerry Internet Service in order to perform this wirelessly.

1) On the BlackBerry device Home screen, click Messages.
2) Click the trackwheel and select Options.
3) Select Email Reconciliation and set the following features:

• In the Delete On field, select Handheld, Mailbox and Handheld, or Prompt.
• In the Wireless Reconcile field, select On.
• In the On Conflicts field, select either Handheld wins or Mailbox wins.

4) Click the trackwheel and select Save.

Additional Info

When you reconcile messages with a PST file, any folders stored in the PST file are copied to your BlackBerry device. You can use those folders to file the messages you want to reconcile with the PST file.

When you file messages from a Microsoft Exchange folder to a PST file, the messages that are present on the BlackBerry device will also be filed automatically.

Refer to RIM’s KB05130 for full details.