Wednesday, 10 July 2013

How to get the EAS report

PS C:\Windows\system32> get-casmailbox -resultsize unlimited | where{$_.hasactivesyncdevicepartnership -eq "TRUE"} | foreach-object{Get-ActiveSyncDeviceStatistics -Mailbox $_.name} | Select Identity, FirstSyncTime, LastSyncAttemptTime, LastSuccessSync, DeviceType, DeviceID, DeviceUserAgent, DeviceModel, DeviceOS, DeviceAccessState, DeviceAccessStateReason,
DevicePolicyApplied, DevicePolicyApplicationStatus, DeviceActiveSyncVersion | Export-Csv C:\temp\asdevices.csv

Monday, 8 July 2013

The program can't start because WMVCore.DLL is missing from your computer

From system logs, if you find below event id 26 multiple times

Application popup: BBConvert.exe - System Error : The program can't start because WMVCore.DLL is missing from your computer. Try reinstalling the program to fix this problem. 

To fix the issue, you need to re-install the package

For Windows Server 2008 R2 SP1, the package recommended by Microsoft is the same except for a different version number:

dism.exe /online /norestart /add-package /packagepath:"%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum" /ignorecheck

Refer KB27341 & KB19555

Multimedia Tutorials for BES 10 v10.1

Sunday, 7 July 2013

Unlisted message error on BB handset while sending meeting request

When sending a meeting request from the Blackberry handset which is running on BES 5.0 SP4 MR4 whose mailbox is on Exchange server 2010, getting red X and on the Blackberry Handset for which the message status shows: Unlisted message error

To fix the issue i have followed the below steps

Open Command Prompt
Browse to the tools folder where you have TraitTool

Traittool -server <Server Name> -list

You should be seeing 4 entries as mentioned below:

EWSEnable: True
EWSSCPURL: https://outlookanywhere.domain.com/Autodiscover/Autodiscover.xml
EWSCASURL:https://outlookanywhere.domain.com/EWS/Exchange.asmx
ExchangeDisableConfirmEmailDelivery:0

From the above command, i have confirmed EWS is enabled on the server. 

I have assigned the blackberry account to the static agent 214 and while testing the calendaring functionality by creating a new meeting request, it went without red X. Calendar functionality is working fine on agent 214 without any issue.

Now i went to still deeper level i.e agent level

Traittool -server <Server Name> -agent 1 -list
EWSEnable:true
Traittool -server <Server Name> -agent 2 -list
Traittool -server <Server Name> -agent 3 -list
Traittool -server <Server Name> -agent 4 -list
Traittool -server <Server Name> -agent 5 -list
Traittool -server <Server Name> -agent 212 -list
Traittool -server <Server Name> -agent 214 -list
EWSEnable:true

When i have assigned the blackberry account to static agent 212, the calendar functionality is not working fine i am receiving red X with the message status: unlisted message error. From the above information i got to know as the EWS is not enabled for the agent 212, the calendaring functionality is not working.

To fix the issue at the static agent level, i ran the below command and restarted the BB Controller service.

TraitTool -server <Server Name> -agent 212 -Trait EwsEnable -set true
ewsenable: Added 'true' Server: <Server Name>(2), Agent: 212(212)

Now i have tested the calendar functionality by sending the meeting request now it reached the recipients without any issues i.e red X 

Finally i have fixed the issue :)

Reference KB29946

Thursday, 4 July 2013

How to seamlessly extend the windows server trial to 240 days

The Microsoft evaluation releases of their products are incredibly valuable and useful tools as they allow you to have an unlimited number of test, demo and development environments to work with at no cost. The only catch is evaluation releases are time limited, so the more time you can squeeze out of them, the more useful they can be.

Here we are going to show you how to extend the usage time of the Windows Server 2008 R2 evaluation release to its maximum.

How it Works
Once activated the Windows Server 2008 R2 evaluation (or trial) lasts for 180 days, after which you must either enter a valid license key or the server will shut itself down after one hour of use.

With most every Microsoft product which requires activation, there is a grace period of several days in which the product can be used (unrestricted) before activation is required. In the case of Windows Server 2008 R2 evaluation, this grace period is 10 days which can be reset (or re-armed) 5 times before activation is required. When fully utilized, gives an extra 60 days of usage time.

To put your mind at ease, this practice is completely legal and actually promoted by Microsoft. We are simply approaching this with an automated “set it and forget” it process.

Refer the Blog for complete details

Exchange Server Performance

What are "Device.xml" and "Vendor.xml" files in the Blackberry Enterprise Server

In BlackBerry Enterprise Server 5.0 to 5.0 SP4, the BlackBerry Administration Service automatically downloads the Device.xml and Vendor.xml files from https://www.blackberry.com/Desktop/Download/XML/Device.xml and https://www.blackberry.com/Desktop/Download/XML/Vendor.xml at hourly intervals and updates the files that are present on the BlackBerry Enterprise Server. The files are then used for wireless software installation and wireless software updates.

If the computer hosting BlackBerry Administration Service 5.0 to 5.0 SP2 is unable to access the Internet, either because of firewalls or a proxy server, the BlackBerry Administration Service is unable to download the correct data and the existing XML files might become outdated, as result, BlackBerry Administration Service may be unable to send application to the BlackBerry devices.

BlackBerry Enterprise Server 5.0 SP3 and SP4 have the ability to proxy BlackBerry Administration Service requests properly. Please see KB25252 on information to configure proxy settings to allow appropriate updating of Vendor.xml and Device.xml files for BlackBerry Administration Service 5.0 SP3 or higher.

Note: The URLs for Device.xml and Vendor.xml are case sensitive and if the case is changed, the files will not be accessible.

The exact format for both URLs is as follows:

Device.xml: https://www.blackberry.com/Desktop/Download/XML/Device.xml
Vendor.xml: https://www.blackberry.com/Desktop/Download/XML/Vendor.xml 

If BlackBerry Administration Service doesn't have access to Internet, or if it is unable to download the XML files through proxy or firewall, contact BlackBerry Technical Support.

Reference Articles: KB22777 KB13589