Monday, January 28, 2013

Lync Audio/Video Disabled in batch

If you want to disable Audio/Video for batch and only want to allow basic Lync features then following will be the command for this;

Import-Csv C:\LyncBatch.csv| ForEach-Object{$varUserId=$_.userid;set-CsUser -Identity $varUserid -AudioVideoDisabled $True}

In order to run this command, there should be a CSV file present in C:\ drive named as lyncbatch.csv. This file should have aliases of all the users accounts needs to disable Audio/video in following format(List should always start with userid) ;






After running this command the user can do chat and web conferencing but there will be no Audio/Video/Enterprise voice service available for user.

Batch Command for enabling Lync Users

Following is a very useful command for enabling Lync users in batches;

Import-Csv C:\LyncBatch.csv | ForEach-Object{$varUserId=$_.userid; Enable-CsUser -Identity $varUserid -RegistrarPool –SipAddressType EmailAddress -SipDomain}

In order to run this command, there should be a CSV file present in C:\ drive named as lyncbatch.csv. This file should have aliases of all the users accounts needs to migrate in following format(List should always start with userid) ;





Sunday, July 15, 2012

Windows Live Audio/video Federation with Lync

was aware that we can federate with windows live for instant messaging integration but was not sure about Audio/Video. After some research i found following blog post which is confirming this type of federation;

Please be aware that in order to federate with windows live you have to change Lync encryption settings

Tuesday, July 10, 2012

Lync 2010 Mobility in Split-brain DNS setup

After reading Mobility guide from Microsoft, it is not very clear that how users will connect to Lync auto discover service externally and internally in split brain DNS Setup and it requires reading again and again and troubleshooting again and again to find out the correct setup, in summary following should be the DNS configuration in split-brain DNs setup (Note: Split-brain DNS refers to the DNS setup where your DNS zone is split between your Internal Network and your external network for example zone is also present in internal AD forest DNS servers and also published outside publish DNS servers);

1. Lync Auto discover URL should be in external and internal DNS servers pointing to Lync external web services URL.

2. Lync Auto discover internal URL should be present in your internal DNS server pointing to Lync internal web services URL.

3. There should be a entry for Lync external web services URL in your internal DNS servers pointing to lync external web services IP for “Hair-pining” Lync mobile traffic to Reverse proxy servers.

4. Reverse proxy Rule for lync auto discover service should have lync discover internal URL added for mobile clients connecting from internal network through lync external web service public IP.

Lync 2010 Blogging

I have recently implemented Lync services in our organization and came across lots of problems mainly due to the guides which Microsoft has published is not clear and have lots of questions unanswered. The only way to do a correct configuration is to to a trial and error and then check if the problem is solved or not or engage Microsoft professional services.

I will be blogging on some of the issues I have faced and resolved for the benefits of other implementers.

Wednesday, November 10, 2010

Exchange 2007 unable to mount database

Recently we had a power failure which caused an improper shutdown to our exchange servers. After recovered from power failure we restarted all servers and fixed some cluster issues but there is one database which is showing failed in cluster manager. I had tried to mount the database but it was not successful and showing that there are some log files missing due to which database cannot mount.

For checking what log files are missing I ran following commands against the database which was not mounting. For running this command we have to go to the log drive of the database first and then run this command.

eseutil /mh

The output of this command is showing that the database is in dirty shutdown state and also showing that what log files are missing. I have checked these log files and luckily I have all log files present in the log drives folder.

Now recovery is easy, I have just renamed the check point file to any other name and try to mount it again and this time it mounts successfully without any issues and new checkpoint file is created.

MOSS "trial period for this product has expired"

Recently I faced an strange issue related to MOSS. One of my content admin is complaining that he is unable to add any link or page in his site anymore. whenever he is trying to create any page he is getting this error

"trial period for this product has expired"

Our MOSS farm has correct license and we haven't upgraded MOSS from trial version. After thorough analysis and research, I found that there is a bug in MOSS SP2 which reinitializes the license file and turns MOSS normal license to 180 days trial  license.

For fixing this issue, you can go to MOSS central admin->operations->Convert license type->Enter product key and add the key again or apply the hotfix mentioned in the below KB article.