Thursday, January 29, 2015

how to activate Office365


Please find Office 365 Activation Process and customer support detail for india.

Please find process to activate Office 365 through the tab Online Service Activation. 
Once you have acquire the OSA key, you may proceed to click below link for your Office 365 activation:
Microsoft Volume Licensing Services Support Center
India: 000800 440 1555 (Toll-Free Number) / 1 (212) 444 0497 (Toll Number)
For more information on Volume Licensing/Software Assurance:
Kindly be informed that Office 365 is a license that gives a user the right to access for Cloud services. Hence you are unable to get any setup or media to download from the VLSC web page.
You may contact our CPC team at 1800 200 2052 for Office 365 configuration and further assistance.

Thank you for your continued support towards Microsoft products and services.

Gaurang Patel

Office 365 Lync Online SRV settings in Plesk DNS Control Panel


Office 365 Lync Online SRV Records are not getting verified by Office 365 DNS.

Symptoms :

 Rest of all Records are getting verified without any issue like "CNAME", "MX" , "A" Records, but when you set SRV Records for Lync Online in Plesk DNS control penal it is not allow you to set WEIGHT to "0" and priority to "100"

Resolution :

After so many diagnose I found that removing the _ from the sip and tls setting and setting the priority and weight to 0 allow it to verify.

UNIX or Linux OS servers that host DNS don’t require the underscore (_) when you add SRV records to the DNS host. If your DNS host is running UNIX or Linux and the SRV records aren’t resolving correctly, remove the underscore from the host name of the SRV record.

After setting above value please wait for at least 10 minutes to reflect DNS records changes, it may also depend on your internet speed and DNS Propagation Speed.

now open Office 365 Admin page and change DNS settings, Select Verify domain button to verify DNS changes and hurrayyyyy!!!!! Congratulations you have successfully configured Office 365 DNS records. Now your Lync will be up and running.

hope this may help.

Gaurang Patel

Thursday, November 20, 2014

Exchange 2013 Outlook and OWA Search Does Not Work

Exchange 2013 Outlook and OWA Search Does Not Work

As with all previous versions of OWA, Exchange 2013 has a search function that is above the mail column as seen below.
Exchange 2013 owa search
I came across an issue recently where if you did a search in OWA 2013, no results would be show, no matter what information I used as the search keywords. No matter what no search results where found. In Exchange 2013 , the search index is stored with the Mailbox store where the users are located. To resolve this issue and build the OWA 2013  and the Exchange search index again we needed to do the following. This error may also occur withOutlook clients that are not in cached mode.
1) Stop Service
 navigate to services stop the Microsoft Exchange Search Microsoft Exchange Search Host Controller service.
2) Locate User Mailbox Database.
Once done locate the folder on your server where the Mailbox database is where the user is trying  to search from. For example mine is here.
C:\Program Files >Microsoft > Exchange Server > V15 > Mailbox > Mailbox Database 1403936621

Exchange 2013 Search database
If you are unsure where the the mailbox database is use the command below from power-shell.

Get-MailboxDatabase "yourmailboxdatabase" |fl name,*path*
Once the path is located you will find a folder name with a long “GUID” and the word Single on the end.
exchange 2013 search guid
3) Rename this folder .old.
We then need to start the Microsoft Exchange Search service again, The server will now begin to rebuild its search index.
Give it plenty of time to rebuild then issue the command below and make sure the status of Content Index Status is seen as healthy.
As seen below, if it says healthy try your search and you should see that your search results now appear in Outlook and OWA 2013.
Exchange 2013 rebuild search index

Wednesday, November 12, 2014

Setting up Vtiger CRM PBX Manager with Asterisk

Setting up PBX Manager with Asterisk

For official configuration Guide please login to here.

After going through Official configuration guide then I realise that there should be one step by step guide with snapshots for newcomers or who are not familiar with Asterisk PBX and Linux.

I tried to make this step by step very simple and more understandable for all, so please give me any suggestion from your side to make this documentation better.

I have separated configuration parts in different steps.

1) Scenario with Network Diagram.
2) Required Software’s.
3) Vtiger Side Configuration.
4) Asterisk Side Configuration.
5) Troubleshooting.

Network Diagram

Vtiger Server:
                                Windows 7 32 bit , Dual Core CPU , 4 GB RAM , 40 GB HDD.
                                Vtiger 6.1
                                Zoiper SIP Soft Client with 2009 Extension Configured.

Asterisk Server:

Dual Core CPU , 4 GB RAM , 40 GB HDD
AsteriskNOW 5.211.65 (User Any Asterisk Based PBX like FreePBX , Elastix etc..)
Java Jetty Installed.

Note : this scenario has been developed in Virtual Environment ( Vmware Workstation 10 ) in my case.

Configure your Asterisk credentials in Vtiger

After installing Vtiger Asterisk Connector, please follow few simple steps to configure your Asterisk Server information in Vtiger CRM :

1. Login to your CRM instance and click on Setting.png icon on the top right corner of the CRM.

2. Click CRM Settings.

3. Click PBX Manager under Integration in Settings sidebar.

4. Edit Asterisk Server Details.

Vtiger Asterisk App URL - configure server name where Vtiger Asterisk Connector is installed as shown:

Syntax : Protocol://Asterisk_Server_IP:Port

Your Asterisk Server IP
Server Port configured in Vtiger Asterisk Connector config file.

Outbound Context - Vtiger specific context configured in your Asterisk Server

Outbound Trunk - Trunk configured in your Asterisk server for Outgoing Calls.

Vtiger Secret Key - Unique key generated for authentication, which has to be configured in Vtiger Asterisk Connector.

5. Click Save button.

Note : in my case I am not using any trunk for Outgoing Calls, I just want to test internal Calls only in my LAB. So please Add your Outbound trunk Name which is configured in Asterisk GUI -> Connectivity -> Trunks. ( Name is Case Sensitive so be careful ).

 Configure the extension number for each user

For each user who is allowed to handle incoming and outgoing calls from the CRM, the extension number should be configured in the User preferences page.

1. Open My Preferences.

2. Configure user number in CRM Phone Extension field under “More Information” block.

Number format:

Extension: [Extension_number]

e.g., 2001

Once configuration is completed on both sides i.e., Vtiger and Asterisk, you are now ready to make and receive calls in the CRM.

Vtiger Asterisk Connector Installation on Asterisk Server

Vtiger Asterisk application acts a gateway to connect to Vtiger CRM from the Asterisk Server. It makes it easy for Vtiger and Asterisk interaction over HTTP when incoming or outgoing calls need to be handled.

Vtiger Asterisk Connector provides following features:

1. Connect to Vtiger and notify the incoming call.

2. Accept commands from Vtiger and forward it to Asterisk (Click-to-Call).

3. Call recording file management.


1.       Download Asterisk Connector ( PBXMagager )Add-on from Official Website.

2.       Download WinSCP and connect to Asterisk server .

3.       Transfer to root folder ( / ).

4.       Login to Asterisk Server by using putty.exe or ssh terminal and unzip VtigerAsteriskConnector with “unzip” Command.

5.       Open /VtigerAsteriskConnector/conf/ and update information as below.

6.       Copy and Paste the Vtiger Secret Key that is generated in your Vtiger Instance.
You can find this under Vtiger CRM > Settings > Integration > PBXManager > Asterisk Server Details.

7.       Copy Vtiger URL exact the same because it is case sensitive so better to copy and paste from web browser.

8.       Cd /VtigerAsteriskConnector/Bin

9.       ./

10.    Test Vtiger Connector website is working or not the result should be as below.

11.   If you find above result then you are ready with VtigerAsteriskConnector Configuration.

Asterisk Configuration File Changes

1)      Change In extensions.conf ( /etc/Asterisk/extensions_custom.conf )

Create Vtiger SIP Extension

1)      Open Asterisk GUI -> Applications -> Extensions.

2)      Create SIP Extensions.

Configure Asterisk Manager User

1)      Open Asterisk GUI -> Settings -> Asterisk Manager Users

2)      Create “vtiger” User with ALL Permission.

3)      Make / in Deny Entry.

4)      Permit

5)      Click on Submit.

6)      Save Changes.

Check /etc/Asterisk/manager_additional.conf

Add VtigerAsteriskConnector Script in to startup.

1)      Open Asterisk server terminal and give below command.

2)      Echo sh /VtigerAsteriskConnector/bin/ >> /etc/rc.local


1)      Monitor Logs in /VtigerAsteriskConnector/Logs

a.       nohup.webapp.<date>.out
b.      nohup.agi.<date>.out

2)      Start or restart VtigerAsteriskConnector Scripts /VtigerAsteriskConnector/bin/

3)      Check webapp is running or not by visiting it should show above Scripts in browser.

Saturday, April 26, 2014

how to promote Windows as a terminal server

Hi Folks,

hear i will going to explain how to promote Windows XP and Windows 7 to

Terminal Server, however Microsoft is not recommending to do so because of

Licensing policy violation.

if you promote windows 2008 as a terminal server than you have to procure terminal server licenses, in windows xp / 7 you can completely crack the scenario, however windows xp is no more supported by Microsoft but some people are still prefer to work with XP.

by promoting XP / 7 to terminal services you can run 10 to 15 terminals without any issue but it is depending upon the hardware config, now a day's  SSD / hybrid HDD is available on cheap rate which can give you good IOPS performance.

Ncomputing is also providing Vspace Software for XP and Windows 7 Desktop

operating system to promote client OS to terminal services, ncompuring is

doing the same thing which i will going to discribe below.

1) First of All Install windows XP / 7 Client operating system with Latest

hardware Drivers.

2) Install Required Software.

3) Update the windows with latest updates.

4) Install Antivirus with Latest Signature. ( disable AV at the time of RDP

 Patch Installation )

5) Disable Firewall.

6) Disable UAC ( User Access Controll ) in Control panel.

7) Download WinXP_7_terminal Server.rar file and Extract to the folder.

8) Archive file contain Three files 1) Termiserv_XPSP2-SP3_i386_2.1   2)

Win7_termiserv_Patch-x64     3) Win7_termiserv_Patch-x86

9) Select Respective Patch based on your installed Windows Version and

install with Administrator rights ( Right Click and Select "Run as

Administrator " )

10) Click on "Patch Button " to start patching and restart the Computer, If

problem occurred after installation of Patch than re-run the Patch and click

on "restore" button.

11) Create Local Group " RDP Users "

12) Create Users and make a member of "RDP Usres" Group.

13) Enable remote desktop and Add "RDP Users" group in remote desktop permission.

14) that's it !!!!! Enjoy !!!!

note : you can also install Ncomputing Vspace instead of this for XP / 7 / 8 ( for 2003 , 2008 , 2012 is not working), it will work perfectly with other thinclient also.

Note: if you are using Symantec / Trend Micro / Quick heal than make exception entry of "c:\windows\system32\termsrv.dll" file.

thank you for your time and stay tune !!!!!!

Tuesday, April 22, 2014

Restore missing Standard TCP/IP Port type for Printer

Restore missing Standard TCP/IP Port type for Printer

If the TCP/IP port option is missing you need to re-add it.
First, make sure that the following files are in C:\Windows\System32\:

If they are missing, you will need to copy them there from either the i386 directory (if you have one) or from the original install CD.
Then, copy the following lines to NOTEPAD and save the file to your desktop as “printer.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port]
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Monitors\Standard TCP/IP Port\Ports]

Once it’s saved to your desktop, double-click printer.reg and say “OK” to the warning that you will be adding the keys to your registry.

Reboot the Server and the TCP/IP port option should be back.

Tuesday, November 12, 2013

Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.

Exchange 2010 SP1, SP2 or Sp3 Error: Setup cannot continue with the upgrade because the “beremote()” process has open files.


Setup cannot continue with the upgrade because the “beremote()” process has open files:
The error listed above is not something to really stress about.


If you running Symantec Backup Exec you will need to stop the services and then retry the checks, they should all pass and allow you to carry on with your installation.

Gaurang Patel