Tuesday, August 27, 2013

Resilient Branch Appliance (RBA), New Lync Survivable Branch Option

As businesses examine their options for migrating to Unified Communications with Microsoft Lync, many are looking at cloud-based solution for reduce capital expenditures and shift to a pay-as-you-go subscription model. With Lync 2013, there are numbers of options such as hosted cloud, dedicated cloud and hybrid cloud.
However, moving to the cloud does put a significantly greater dependency on the WAN, and without a survivability strategy, a simple firewall miss-configuration or network interruption can put  even basic voice communications out of service.
Survivable Branch Appliance (SBA)
For mid-sized cloud customers or branch sites with between 25 and 1000 seats, Microsoft recommends use of a Survivable Branch Appliance (SBA), a hybrid server/gateway network element that includes a server to host local copies of Lync Server Registrar and Mediation Server along with a local media gateway for access to PSTN circuits. SBAs allow mid-size cloud customers to continue business operations in situations when the wide-area network or Lync server pool in the cloud were to be unavailable.
  • Branch office resiliency for up medium to large branch offices with up to 1,000 users
  • Maintains Lync voice services during WAN or central Lync server outages
  • Integrated, highly scalable media gateway and session border controller
  • Ability to host additional value-added enterprise applications

Resilient Branch Appliance (RBA)
There is a new Lync Survivable Branch option called the “Resilient Branch Appliance” or RBA. The RBA brings branch survivability via 3G/4G wireless mobile broadband to keep the signalling and data layers operational during WAN outage.
RBA essentially takes the Survivable Branch Appliance and extends its capabilities with WAN resiliency with either redundant wire line WAN connectivity or wireless 4G to facilitate alternate routes for data connectivity, control and messaging while using local PSTN connectivity to carry voice during a WAN outages.   Designed for small offices, RBAs are ideal for retail, financial services, insurance and other businesses that have many small branch offices and a requirement for business continuity during extended network interruptions.
It appears that 3G/4G keeps signalling, presence, address book and web conferencing going during an outage of WAN. Voice is handled via PSTN breakout.

  • Cost-effective Lync survivability for small branch offices
  • Uses redundant WAN links to ensure uninterrupted connectivity with the central Lync servers
  • Fully compliant with Microsoft SBAv2 specification
  • Integrated router, firewall, VPN, media gateway and session border controller
  • Can be used in conjunction with SBA to add IM and presence in resiliency mode

Reference; http://blog.lyncmigration.com/2013/08/the-cloud-and-lync-survivability.html

Sunday, August 18, 2013

Lync Client 2013 and 2010 Log File Paths

Every Lync professional facing daily multiple issues and providing solution to the customer one of the most important in Lync troubleshooting part is Lync client logs. Lync client logs are very useful in troubleshooting. In 2010 and 2013 the log paths are different, one of the best way to get the log fil:

1. Click on Start.
2. Click on Run
3. Type  %LOCALAPPDATA%\Microsoft\Office\15.0\Lync\Tracing\ (for Lync 2013) and %UserProfile%\Tracing (for Lync 2010 client)

Typically, if user profiles are on the C:\ drive these take you to


Friday, August 16, 2013

Moving Blackberry Enterprise Server SQL database from one server to another

To move SQL database from one blackberry Server to another:

The process is very simple:(BES and SQL 2005)

1. Take backup of BES database by using sql management studio
2.  Copy the data base folder from BES installer to NEW SQL server, in my case it was extracted in path C:\Research In Motion\BlackBerry Enterprise Server 4.1.7\Database
3.  Edit the BESMGMT.cfg file & enter the BES data base name you want to create on New SQL server
DATABASE_NAME=BESMgmt (in case of SQL instances you ahve to mention instance name\database name)
4. Open command prompt on New Sql server browse to databse path & run createDB.exe with the user that has permissions.
5. Now restore the  database from backup to this newly create database on New SQL Server.
6. Now go to Blackberry enterprise server & open blackberry server configuration from start–>programs menu
7.  Click Change database & wizard will start which will guide you to a smooth process. (blackberry services will stop & start in the process)

If you are using MDS services database then you have to follow some additional steps that are mentioned in below link.

In my case we are not using MDS services.

OCS/ Lync Client address Book Update

Some time we are getting old address book in lync client, below batch script that we use when address book gets out of sync, some times user complains in our environment that he or she is not able to see new titles of the user although it is populated in outlook GAL.
1.      Exit user’s communicator.
2.      Run the following file from an admin/elevated command prompt: (Batch file)
@echo off
echo Clearing Address Books…
reg add HKCU\Software\Policies\Microsoft\Communicator /v GALDownloadInitialDelay /t REG_DWORD /d 0 /f
If %errorlevel%==1 goto Error
if “%LOCALAPPDATA%”==”" Set LOCALAPPDATA=%USERPROFILE%\Local Settings\Application Data
dir “%LOCALAPPDATA%\Microsoft\Communicator\sip_*” /b > list.txt
FOR /F “tokens=1″ %%i in (list.txt) do del “%LOCALAPPDATA%\Microsoft\Communicator\%%i\gal*.*”
echo Sign out of Lync and sign back in to download the current address book.
goto End
echo You must run this command from an elevated Command Prompt.
3.      Launch communicator and ask user to sign in.
4.      Check whether the Galcontacts.db file has been downloaded.
Galcontacts.db path:
  • ·         In XP:- C:\Documents and Settings\\Local Settings\Application Data\Microsoft\Communicator\\
  • ·         In Win 7:- C:\Users\\AppData\Local\Microsoft\ Communicator\\
5.      Run the following file from an admin/elevated command prompt:(This step is so that Gal is not downloaded everytime)
@echo off
echo Clearing Communicator Address Books…
reg delete HKCU\Software\Policies\Microsoft\Communicator /v GALDownloadInitialDelay /f
If %errorlevel%==1 goto Error
goto End
echo You must run this command from an elevated Command Prompt.
found on Some where on Net but modified a bit & included second batch file so that Gal is not downloaded again & again.

How to decommission a Blackberry Enterprise server (5.0.3)

Step 1
  1. Logon to the BlackBerry Enterprise Server using the BlackBerry Enterprise Server service account.
  2. Click Start > Programs > Administrative Tools > Services.
  3. Stop all BlackBerry Enterprise Server services by clicking Stop Service for each service.
  4. Click Start > Settings > Control Panel.
  5. Double-click Add/Remove Programs.
  6. Click BlackBerry Enterprise Server and click Remove (If the Remove option does not exist, select Change to launch the installer and then select Remove).
  7. Delete the Research In Motion folder located in the C:\Program Files(x86) directory.
  8. Delete the Research In Motion folder located in the C:\Program Files(x86)\Common Files directory.
 Step 2
  1. In the BlackBerry Administration Service console, navigate to Servers and components > BlackBerry Solution topology > BlackBerry Domain > Component View (Select it, not expand).
  2. In the Component View, locate the appropriate BlackBerry Enterprise Server component section, click the trash can icon next to the component to be removed.
  3. The BlackBerry Administration Service console asks ‘Are you sure you want to delete this instance?’ and a summary including key information points is displayed. To confirm the deletion, select the ‘Yes – Delete the instance’ link below the summary.
  4. The BlackBerry Administration Service then performs a series of checks to ensure the BlackBerry Enterprise Server component can be deleted. If all conditions have been met, a final notification is displayed: ‘All conditions have been met for the instance to be deleted. Are you sure you want to delete this instance?’
  5. Select the ‘Yes – Delete the instance’ link to delete the BlackBerry Enterprise Server component.
  6. The deletion is confirmed by the message. The instance has been deleted.
  7. Repeat these steps for each component of the decommissioned BlackBerry Enterprise Server to be removed. (Note: It is important not to remove components that still are in use. Review the summary page before confirming deletion to ensure that active components are not removed.)
Note: -   Reboot the server once the both steps are complete.
               Complete both steps for all the servers to be decommissioned.