Thursday, February 16, 2012

Enable Event Viewer Logging on All Lync Clients

Enabling event loggin on Lync clients can be done eithr by enabling the option "Turn on Windows  Event Logging for Lync" or for all users by using Client Policies.

From Lync Management Shell run the following command:

Set-CsClientPolicy -Identity "Global" -EnableEventLogging $true
Then Sign in and out from your Lync client you should see the option set in the Lync client options:

The Lync Server Front-End service terminated with service-specific error %%-1008193021.

I had a problem where the Lync Server Front-End server could not start and found the following error in the event viewer's system log
"The Lync Server Front-End service terminated with service-specific error %%-1008193021."
It was due to that the Installation bits used were evaluation bits and it had expired, the solution was to upgrade to the RTM version.

see my other post for info. about how to upgrade from Eval to RTM.

Upgrade from Lync Evaluation edition to Lync RTM.

If you have installed Lync Server using the 180 Day  trial bits  you can upgrade to the RTM bits nsing the following easy steps:
  1. Run setup.exe on your Lync server Volume License media.
  2. Click on "Install or Update Lync server system"
  3. Click on "Setup or remove Lync server components"
  4. Open CMD and  navigate to \Setup\amd64\setup and then run msiexec.exe /fvomus server.msi EVALTOFULL=1 /qb 
  5. Open Lync Server Management Shell and then run Enable-CSComputer and then you are done !

Sunday, February 12, 2012

WSUS Console - Error: Connection Error

I faced the following problem at a cusotmer, When i opened the WSUS console i get the following message:

and the following error in the event viewer:
Log Name: Application

Source: Windows Server Update Services

Date: 2/12/2012 3:16:29 PM

Event ID: 7053

Task Category: None

Level: Error

Keywords: Classic

User: N/A


The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists,

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.

System.NullReferenceException -- Object reference not set to an instance of an object.


after investigation i found out that the Windows Internal Database service was not running, starting it fixed the problem immediately.

Thursday, February 9, 2012

Lync Phone Edition Time Synchronization

In order to get Lync Phone Edition (LPE) to Synchrnize time you need either and SRV record that points to your NTP servers (which may be your domain controllers) or allow Internet connection to your LPE devices,
as LPE synchnronizes time using one of the following methods:

  1. Lync Phone Edition searches for an NTP server in Domain Name System (DNS)  , it looks for the SRV record  _ntp._udp. pointing to NTP Server
  2. If Lync Phone Edition cannot find the NTP SRV record, it will attempt to use as an NTP server by searching for
so either create the SRV record or allow Internet access to on port 123 UDP.

fore more info. refer to

Sunday, February 5, 2012

451 4.4.0 Primary Target IP Address Responded with (501 5.5.4 Auth Command Cancelled)

I have faced a problem at a cusomter site;mails  cannot flow from an Exchange 2010 server to a specific Exchange 2003 server , while it can flow to other Exchange 2003 servers.

Exchange 2010 servers were in AD domain: and Exchange 2003 server was in ADdomain :

Domain controllers of domain only existed at the site of Exchange 2003.

The queue viewer gave the following message :
"451 4.4.0 Primary Target IP Address Responded with (501 5.5.4 Auth Command Cancelled)"
 and the application log gave the following error:

Outbound authentication failed with error -2146892976 for Send connector Intra-Organization SMTP Send Connector. The authentication mechanism is Gssapi. The target is SMTPSVC/Exchange2003ServerFQDN
i have checked the SPN , using Setspn -l Exchange2003ServerName aother posts on the Internet suggested, the SPN was not in place so i had to add it using :

setspn -a SMTPSVC/Exchange2003ServerFQDN Exchange203ServerName
But the problem still persisted, later we found out it was related to netowrk traffic being bloked, in addition to Posrt 25 for SMTP traffic , you still need Ports 389 and 88 for authentication between Exchange 2010 servers and domain controllers for AD domain.