Category Archives: Uncategorized

Uncategorized

Lync 2013 client logging

Leave a comment

When testing your Lync 2013 environment it sometimes happens that you cannot logon to your Lync server. If this happens it can be useful to enable logging in your Lync 2013 client.

In your Lync 2013 client, go to Tools en then to Options. In the General section set Logging in Lync to Full.

image

The log files will be stored in C:\Users\Jaap\AppData\Local\Microsoft\Office\15.0\Lync\Tracing. In there you’ll find a file called Lync-UccApi-0.UccApilog which contains a wealth of troubleshooting information.

Uncategorized

Automated Deployments

Leave a comment

For my lab environment I have to reinstall environment on a regular basis, which of course is quite a lot of work. Of course I know the unattended setup options in Exchange, but you also have to setup your VM’s, DCPromo the VM’s and install all kinds of prerequisite software.

Installing Lync is even worse with the Topology Builder, creating the XML and then install the various server roles.

I found these links on the internet which can certainly help you speed up your lab deployment:

I haven’t tried the unattended Lync setup, but the other two are awesome!

Uncategorized

Possible data corruption in VMware Virtual Machines

Leave a comment

This issue was brought to my attention by Veeam, VMware recently issues a support KB article about possible data corruption when sending large amounts of data of a virtual NIC. Any data send across the network can get corrupted, including file copies, database actions etc. Naturally this can also impact Exchange server operations.

This occurs only with Windows Server 2012 running inside the VM and when the VM is using the default E1000E virtual network adapter.

Two workarounds are available:

· Disable TCP Offloading in Windows Server 2012, but this may increase CPU utilization.

· Replace the E1000E NIC with an E1000 NIC or a VMXNET3 NIC. This is probably the best solution but it is labor intensive as it means reconfiguration of all your Virtual Machines. PowerCLI may be your friend in this case.

The root cause is currently under investigation. For more information (and updated information over time) please check the VMware support KB article.