About Me

My photo
This is a blog for John Weber. One of my joys in life is helping others get ahead in life. Content here will be focused on that from this date forward. John was a Skype for Business MVP (2015-2018) - before that, a Lync Server MVP (2010-2014). I used to write a variety of articles (https://tsoorad.blogspot.com) on technical issues with a smattering of other interests. I have a variety of certifications dating back to Novell CNE and working up through the Microsoft MCP stack to MCITP multiple times. FWIW, I am on my third career - ex-USMC, retired US Army. I have a fancy MBA. The opinions expressed on this blog are mine and mine alone.


Lync Server 2010 Backup

Published up on Microsoft Download, we now have some official word on backup and restore for Lync Server.  Quoted from DrRez:

This document describes a methodology for backing up and restoring the data that is required for full recovery of Microsoft Lync Server 2010 services. It includes the procedures for backing up data and recovering from the following levels of failure: Standard Edition Server, Central Management Server, Enterprise Edition Back End Server, a server that is a member of any Lync Server pool, a Lync Server pool, a File Store, an Archiving Server or a Monitoring Server with a collocated database, and a stand-alone Archiving database or Monitoring database.

Visit Backing Up and Restoring Lync Server 2010 to download the whitepaper.


Download Silverlight v4

My client does not allow the Lync FE servers to reach the internet directly on 80 or 443.  Therefore I needed to find a download of Silverlight for the Lync Control Panel.

Here it is.


AntiVirus and Lync

Right from the online CHM file entry on virus scanning exclusions.  I had a bit of trouble finding this, even though I knew it was there.  A colleague reminded me of this, so I thought I would throw up a quick reference so I can always find it.  I had a client ask me this question, and my response was “the entire install structure, the standard SQL exclusions, and the file share location.

Here is the link to the official material, and below is the data copied from that link so I don’t have to go hunting for it!  Note that the Lync file share is not on this list; however, I have seen some issues with meeting content when the server is actively scanning that location.  I cannot say for certain that the virus scanning on the server was causing the issue, but I do know that disabling the virus program on the server fixed the issue.  On the client side, it appears that some client virus engines get in the way of certain Lync functions unless you specifically add the Communicator.exe program to the engine’s allowed programs.

Specifying Anti-Virus Scanning Exclusions

To ensure that the antivirus scanner does not interfere with the operation of Microsoft Lync Server 2010, you must exclude specific processes and directories for each Lync Server 2010 server or server role on which you run an antivirus scanner. The following processes and directories should be excluded:

  • Lync Server 2010 processes:
    • ASMCUSvc.exe
    • AVMCUSvc.exe
    • DataMCUSvc.exe
    • DataProxy.exe
    • FileTransferAgent.exe
    • IMMCUSvc.exe
    • MasterReplicatorAgent.exe
    • MediaRelaySvc.exe
    • MediationServerSvc.exe
    • MeetingMCUSvc.exe
    • MRASSvc.exe
    • OcsAppServerHost.exe
    • QmsSvc.exe
    • ReplicaReplicatorAgent.exe
    • RTCArch.exe
    • RtcCdr.exe
    • RTCSrv.exe
    IIS processes:
    • %systemroot%\system32\inetsrv\w3wp.exe
    • %systemroot%\SysWOW64\inetsrv\w3wp.exe
  • SQL Server processes:
    • %ProgramFiles%\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Binn\SQLServr.exe
    • %ProgramFiles%\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer\Bin\ReportingServicesService.exe
    • %ProgramFiles%\Microsoft SQL Server\MSAS10.MSSQLSERVER\OLAP\Bin\MSMDSrv.exe
  • Directories:
    • %systemroot%\System32\LogFiles
    • %systemroot%\SysWow64\LogFiles


dot net v4 breaks iSCSI from NetApp v6.3sp2


edit 15 May 2011

Some feedback from NetApp is that this will work *IF* the SDW and NET3.51 are installed first before putting NET 4 into place.


In our environment, .net v4 also appeared to block installation of BES 5.0.3.  My support chain contacted NetApp engineering, who says that .net v4 is supported.

FWIW, we are using Server 2008 R2 SP1, with all updates (straight install), VMware ESX and ESXi v4, UCS hardware.  I do not know the NetApp filer model/version.

What we saw:  after install of the base O/S, we installed the NetApp v6.3sp2 LUN driver.  Everything appeared to work failry well, until we committed to the LUN and the connection process started.  All we ever got was the 120 second time out.  On the back end, the LUN looked connected at the NetApp, but on the server, there was nothing.  Attempts to reconnect at that point resulted in being told that LUN was already dedicated.

Removing .net 4 components from the server allowed full, normal, LUN connection.



test 02 Feb

this is a test it’s only a test this should be a picture