Jan 302014

In Denmark, the telephone operator TDC provides voice over IP subscriptions to business customers using the Broadworks platform by Broadsoft. The call the product TDC Scale or TDC One depending on the subscription type.

Broadworks has the ability to create voice response menus, hunt groups (they call them call centers), and other nice stuff to manage calls to and from the company.

I had a bit of a problem figuring out which file format to use when uploading voice prompts to the IVR and message boxes.

Continue reading »

Jan 242014

My company is an Exchange shop – amongst other things, we develop software that integrate with Exchange server for calendar synchronization purposes.

As we “eat our own dog food” – or “drink our own champagne” if you will – we run Exchange server. We are a small shop, so we only have one server, with no redundancy etc.

In case of server downtime, we need a backup MX hosted somewhere other than our datacenter, so incoming mail isn’t lost while the Exchange server is down.

We used to have a VM with a traditional hosting provider, but that setup became too complicated (the “best” way for us to pay them was with Paypal, and there were problems with them not being able to verify our VAT number after we were merged with our parent company).

Continue reading »

May 032013

I can’t believe its already been three years since I installed our first Lync 2010 edge server, but the certificate expiry is in the near future, so the time has passed quickly.

The documentation for the certificate request, generation and assignment was flaky, so I had to dig deep in my mind to drag out what to do when installing a certificate in Lync, especially the Lync edge server. If you are also having problems remembering what to do, or you have never tried it before, then this blog post is for you.

Continue reading »

Mar 082013

After the Lync 2013 upgrade I made at my company in December, we have been having problems with multiparty IM and voice calls, as well as with the Lync whiteboard feature and other stuff.

We develop software that integrates with Lync (http://www.blueposition.com/lync and http://www.busylight.com/), so our production Lync installation should really be working properly, but I haven’t had the time to look into the problem in details, and no amount of googling the error messages helped.

Today however, my colleague had to debug a problem to one of our software products, that only occurred when the user was in a voice conference, so the Lync issue had to be solved – otherwise he had no way of reproducing the software problem.

Continue reading »

Mar 082013

I recently installed the monitoring database for my company Lync Server 2013 infrastructure.

Following the guide at http://technet.microsoft.com/en-us/library/jj205271.aspx was straight forward, but as often happens, something went wrong.

When it wanted to create the SQL server database, the topology publish process failed with an error message: “The network path was not found”.

Continue reading »

Feb 052013

If you need to debug Lync Server 2013 on Windows Server 2012, you are best of running it on a full server UI (not Server Core or the minimal UI).

I have experienced that without it, the Snooper tool won’t be able to show you a parsed view of the log files, only the raw logs.

Continue reading »

Jan 102013

I have recently updated my company’s Lync infrastructure from 2010 to 2013.

The process went fairly well (see my original post for the problems I encountered during the installation).

I moved some users to the Lync 2013 pool, and added a 2013 edge server. Everything seemed to work fine, so I moved all users to the new pool, and thought all was good.

But then I noticed that Whiteboards and Polls in IM sessions and meetings were not working. Application and desktop sharing was working fine. I haven’t tried Powerpoint sharing, because that requires an Office Web Apps server, which I haven’t installed yet.

Neither internal nor external users were able to use Whiteboard or Polls.

Continue reading »

Dec 142012

I have recently begun the process of migrating my workplace’s Lync infrastructure from Lync 2010 to Lync 2013. It is not a trivial process, but easier than my previous upgrade from OCS 2007 R2 to Lync 2010. That involved a number of calls to Microsoft Premier support, and using ADSI Edit to delete some old entries left by a previous installation of Live Communications Server 2005.

The tools to configure and deploy Lync 2013 are very similar to the Lync 2010 tools, so at least the interface is familiar if you know Lync 2010.

As before, it’s not possible to upgrade in-place, you must install the Lync 2013 servers side-by-side and then move users from Lync 2010 to 2013.

During the upgrade I ran into a few problems.

Continue reading »

Aug 162012

Update 2015-08-19: This also applies to Windows 10.

I installed Windows 8 last night when it came out. I used the Enterprise edition available through my company’s MSDN subscription.

Windows installed in about 20 minutes which was quite good I think. Boot time has also improved – but that is really only something that can be determined after a while, when all programs have been installed.

The Windows activation failed. It kept coming with an error code 0x8007007B “The filename, directory name, or volume label syntax is incorrect.”.

I figured that couldn’t be right. And “Why wasn’t I prompted for a product key during installation?”. The Windows Activation control panel applet showed the last five characters of a product key which didn’t match the one I had retrieved from MSDN. After searching for somewhere in the GUI to enter a product key, I gave up and reverted to the command prompt.

The “slmgr.vbs” tool is your friend for Windows activation issues. It lets you display detailed information on the activation state, clear a product key, change the product key, reset/rearm the licensing state to extend the activation grace period, and more. Just type “slmgr” from a command prompt to see the command line options:


There are several more options displayed after you hit OK.

I tried to activate from the command line using”slmgr /ato”, but that failed with the same error code as the GUI applet.

Then I decided to change the product key to the one I got from MSDN using the command “slmgr /ipk <Product Key>” (substitute with your own key). – This requires running slmgr from an elevated prompt.

After changing the key, I was able to activate Windows using “slmgr /ato”.