How to Remove Active Sync Devices Manually

Open Exchange Management Shell

Get the device stats with the below command

Get-ActiveSyncDeviceStatistics -Mailbox “user name”

A list of devices would be shown associated with the user


Note: Enter the user name without quotes. Copy the Identity of the device you want to remove.

Run the cmdlet

Remove-active sync device


Copy the identity and paste when asked for an identity as shown above.

Press Y to remove the device.

See Ya till Next Post….

How to Push Applications on a Blackberry 10 device

In this guide I will explain how to push application on a BB 10 device using Blackberry 10 Administration console. This would explain application push by choosing .bar file which is a custom or in-house app or Publishing an App from Blackberry World.

First and Foremost.

1. Login to the BES admin console page with the service account or an administratorr account assigned for BES 10.

2. Under Blackberry solution management, Expand Software—–Applications and click Add or update applications.

3. Click choose file.


4. Browse to the location where you have stored you .bar file.

5. Once the File is selected click on Next


Also remember the folder on which the application is ketp should be added on Blackberry Administration Service shared Network drive

The folder path should be in a UNC format //servername/share and the besadmin should have full rights on the folder.



6. Click on Publish Application



7. Next step is to create a software configuration and assign the newly created Application to it.


8. Click on Manage Software configurations and then on the Name of the application.


9. Click on Applications tab and then Edit Software Configuration


10. Next step is to click on Add applications to software configuration


11. Select the Application name that we just added and select the Disposition as Optional. Optional would have the application listed under Blackberry App world- Work. Click on Add to software configuration


12. Click on Save All


13. At this point we have Published and in-house enterprise Application and have assigned a software configuration to it. Next we would create a Group and add the software configuration to it so the users needed access to this application can be added simply to the group.


14. Click on Name of the Group you created.


15. Click on Software Configuration and Edit Group.


16. Select the Application Software configuration name and Click on Add. This will list the Application on the Current Software Configuration as shown belo. Hit Save All


17. At this point we have created a New Group and assigned the software configuration to it.

To Publish an Application from Blackberry World

1. Click on Add Blackberry World applications and enter the url of the Application


2. The url can be found on the Blackberry app world store. In the below example we will be taking Enterprise IM as an example to push via BES admin console. Copy the link from the browser.


3. Paste the link on Blackberry World URL and click Next


4. In case you get the below error you are not selecting 1 Blackberry 10 supported Application. Go to the Blackberry app world and select the correct app.


5. Once the correct application link is pated you will see the Application name. Click on Publish Application


Repeat the Steps from point 7 on the above guide and follow the exact same steps as we did for publishing an in-house

Enjoy and feel free to post your comments and suggestions.

Exchange 2010 Public Folder Replication Issues

Hello World

This post is to explain on how to resolve Public folder replication issues between databases in different locations across data centers. Lately in my organization we faced a problem where public folder in One site was not getting replicated to other site after the transition from Exchange 2003. The newly folders added /deleted were only seen in the Data Center hosting the public folder database.

For this example I would take Public folder residing in UK replicating to US and viceversa.

To Start off and see what’s going on I enabled the Advance Diagnostic Logging for the exchange Management console.

Open Exchange Management Console, Expand and select Server Configuration.
On the right you will find all the servers, Select the Exchange Server where public Folder Database is residing.
Right click on the Server and select Manage Diagnostic Logging.
Expand to reach MSexchangeIS-> Public and then set the components Replication AD Updates, Replication Incoming Messages, Replication Outgoing Messages, Non-Delivery Reports, Replication Backfill, Replication General to expert and then click Configure. Do this on both the Public Folders.

This would enable Advance level diagnostics and would raise event in Event viewer when you try to replicate the Public folder Database Manually by doing an Update hierarchy in Exchange management Public folder toolbox.

Although when you’d a update hierarchy manually the best way would be to Open Log Viewer in Exchange management Console and look for failed events as shown below. In the below example it clearly shows that the folder content fails upon receiving changes from the Public folder hosted on the other Site.


We have to check if the registry key replication flags was set to disabled in registry. As per Microsoft this was a result of 2003 Exchange public folder database not being migrated correctly.

Changed the registry key value “Replication Flags” to 1 in –HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\MSExchnageIS\Exchange Server Name\Public-8fecc579-fd3e-48e5-b3d1-191c39df28d5 on Exchange Server Name.

Note : Exchange server name has to be your server hosting the Public folder database. Make the Above change also to the Exchange server where public folder is replicating to

Open adsitedit.msc and connect to Configuration


Expand CN=Services CN= Microsoft Exchange—CN= Organization name (replace it with your Organization name listed) CN=Administrative Groups——Legacy Exchange Server Names.

Remove server objects from within the Old legacy 2003 attributes. In Below Example under my case it was London and North America.


After this change dismount and remount the public folder databases and Try to make a Test folder by going to Exchange Management console and Public Folder Console.

Update the hierarchy manually and wait for 10-15 minutes for having it replicated on the US node.


Also you can open log viewer and see the events that are been logged after doing an update hierarchy.


As you can the Public folders are now replicating and delivers the changes correctly to the other site in US.


Feel free to post up questions and comments.