Lync 2013 Watcher Node Synthetic Transactions

I've set up SCOM monitoring for our Lync 2013 deployment.
Everything is looks like perfect, in the SCOM console I can see the watcher node and it looks like the monitoring is functional (marked with green as "monitored"), but in the Event Viewer of the Watcher Node server I cannot find the events 334
or 335, but as far as I know, there should be notofications in every 15 minutes, that the tests was runing and was succesfull or not.
I've tried to remove and create the watcher node configuration again, restrated the health service etc. but nothing was helpful. What is the problem? :/

Verify that enable proxy agent on lync watcher node to can monitor it.
For configure watcher node, you can refer below link
http://lyncdup.com/2013/01/how-to-setup-lync-2010-scom-management-pack-and-synthetic-transactions/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
Mai Ali | My blog: Technical | Twitter:
Mai Ali

Similar Messages

Lync 2013 watcher node and DiscoverMachine.ps1

Hello !
I have a strange issue with lync 2013 watcher node.
I completed the installation according to the instructions on the teсhnet (http://technet.microsoft.com/en-us/library/jj205152.aspx). SСOM 2012, sees Lync watcher node components and monitor node correctly. But only one script DiscoverMachine.ps1 has
an error.
Description:
DiscoverMachine.ps1 :
-Script Name: Lync Server MP Machine Topology Discovery -Run as account: nt authority\network service -Execution Policy: Bypass
Value of Source Id is {2469342F-3092-2CD4-2CE3-D45CA920984C}. Value of ManagedEntity Id is {094D7357-71C5-3848-0E33-4B8E5E23B9F3}. Value of Target Computer is LYNCWATCHER.domain.lan. Lync Server Module is added Successfully initialize discovery data. Successfully
found current machine in topology. Machine Fqdn is LYNCWATCHER.domain.lan Successfully discover deployment LS Site discovery completed for Test Site. Can not classify cluster [lyncwatcher.domain.lan]. LS Pool discovery completed for lyncwatcher.domain.lan.
Can not classify cluster [lyncwatcher.domain.lan]. LS Machine discovery completed for LYNCWATCHER.domain.lan. Found an unsupported Role 'ExternalServer'. An exception occurred during discovery script, Exception : System.Management.Automation.RuntimeException:
Cluster of current machine LYNCWATCHER.domain.lan does not have any role supported
Colleague, someone have records similar error?
Konstantin

I opened a support case last week on this, once I have resolution, I'll post it here and on my own thread of the same issue.
http://social.technet.microsoft.com/Forums/lync/en-US/92b8b0d0-c333-4b15-ab8a-6da6b4120432/lync-2013-synthetic-transaction-watcher-node-discovery-failure

Lync Synthetic Transaction from Watcher Node

Hello All,
I have a Lync 2013 Environment using Orchestrator I'm performing some activity on Lync servers and folowed by I will be executing the Synthetic transactions from Orchestrator.
I have created a watcher Node(Just Installed the Lync Core Files and Admin tools), not using SCOM here. I just use to execute the Test-cspresence, Test-CSIM, etc.. from the watcherNode and use targetFQDN as
Front end servers. But it's not working now with an below Error, rest of the commands like get-user and all working fine.
Can someone help me to fix this issue?
Error: “Exception has been thrown by the target of an invocation”

Please check you have enabled Windows Powershell for remoting.
For details, you can check
http://technet.microsoft.com/en-us/magazine/ff700227.aspx
Lisa Zheng
TechNet Community Support

Lync 2013 SCOM Watcher node requirements

Hi there,
Can i configure the watcher node (lync 2013 MP) on one of the Lync 2013 servers? else i should configure it on separate server.
Please advice
Many thanks,
David

"Depending on the size of your deployment, synthetic transactions may use a large amount of computer memory and processor time. For this
reason, we recommend that you use a dedicated computer as a watcher node. For example, you should not configure a Front End Server to act as a watcher node" - http://technet.microsoft.com/en-us/library/jj204943.aspx
Please mark posts as answers/helpful if it answers your question.
Blog
Lync Validator - Used to assist in the validation and documentation of Lync Server 2013.

Have Web App/Transaction monitoring alert only when majority of watcher nodes are in error?

We do a lot of web app/transaction monitoring and we have watcher nodes distributed globally. When we have connectivity issues at a site hosting a watcher node, the web monitors that target the watcher node in that site all alert even though all the other
watcher nodes are fine.
We'd like to reduce the noise from our web monitoring by having alerts fire only when a majority, or some other defined ratio, of watcher nodes are in an error condition. Is this possible, and if so, how?
For reference, we're running 2012 R2 and monitor hundreds of URLs. This list of URLs and watcher nodes is fairly dynamic, so we'd prefer to find a solution that doesn't require manual development (e.g. creating distributed apps), however if that's the only
path then it would also be good to know.

First, disable the alerts from the web application that you have created.
Next, create a new distributed application. Use the 'Blank (Advanced)' template. When it comes to choosing the management pack, set it to be the same as the one used for the web monitor.
Once the distributed application designer has loaded, client the 'Add Component' button.
Give it a name - Something like 'Appname web monitor component group'
Choose the 'objects of the following type(s)' radio button. Navigate the tree:
Entity -> Logical Entity -> Perspective -> Web Application Perspective -> YOURWEBMONITOR
Tick the box next to the name of your web monitor.
Now, on the left, in the Objects bar, you should see the watcher nodes for your web application. Add ALL the watcher nodes into the component group by dragging them in.
Now save your distributed application.
Click the title of the component group that you have just created, down the bottom right of the window there will be a link called 'Configure Health Rollup'. Click that.
In the override properties window, Tick the box next to the 'Rollup Algorithm' and change the Override Value to Worst state of a percentage of members in good health state' and override 'percentage' value into your expected value.
OK the changes and then save the distributed application once again.
Before you exit the designer, note the name of the component group that you created.
Finally, we have to enable alerting for that component group. To do this, exit the designer and you should be back in the Authoring pane of the console.
Go to "Management Pack Objects\Monitors" in the console. Click on the Scope toolbar button to scope the view -
if a scope was previously active, this will disable the scoped view, so click the button again. You should be presented with a "Scope Management Pack Objects Window"
Click the "Clear All" button at the bottom of that window, then type in the
name of the component group that you noted down earlier into the search box. A single line should be displayed in the search results. Tick the box and click OK.
There should now be a yellow bar saying that the view has been scoped to your web application component group. Underneath will be a tree view of the monitors in your web applicaion.
Expand the tree view until you find a monitor called "Component Group Health Roll-up for type..."
Open the properties of that item, go to the alerting tab and
enable the "generate alerts for this monitor" checkbox.
You can then fill in the alert name and description as well as other things like severity and whether or not the alert will close when the monitor is healthy.
Roger

Synthetic transactions are failing

synthetic transactions are failing with below error message
lync 2013 server
A 504 (Server time-out) response was received from the network and the operation failed
from wather node running same cmd it is working and also from the local server also working.
ksrugi

Please make sure Agent Proxy is enabled for watch node.
Add the Lync Watcher Node Computer to the RTCUniversalReadOnlyAdmins.
Check the Windows Firewall on Lync Server Front End Servers is configured to allowing incoming connectivity from Windows PowerShell application and from Microsoft SCOM process.
For details, check
http://support.microsoft.com/kb/2751720/en-us.
Lisa Zheng
TechNet Community Support

SCOM Synthetic Transactions

Wondering if anyone can help with this. Ive setup Lync with a SQL 2008 Db, SCOM and a synthetic transaction node. All seems to be working apart from the ST's. I see the following in the operation manager application event log...
UrlWatcherDiscovery.ps1 :
-Script Name:      Communication Server MP Url Watcher Discovery
-Run as account:   nt authority\network service
-Execution Policy: Bypass
Value of Source Id is {26DC881B-95B7-D85A-C9EC-B01CD4BE2E30}.
Value of ManagedEntity Id is {6598B4A8-7718-CF67-ECD8-A3C679029E00}.
Value of Target Computer is STNODE.LyncLab.Local.
Lync Server Module is added
An exception occured during discovery script, Exception : Could not connect to SQL server : [Exception=System.Data.SqlClient.SqlException: Login failed for user 'LYNCLAB\STNODE$'.
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.Rtc.Common.Data.DBCore.PerformSprocContextExecution(SprocContext sprocContext)].
There is a documented procedure in the MP helpfile which details the use of an SPN on SQL. But. Only if your SQL services are running as a domain account. Which mine aren't. They are running as Network Service.
From Help File...
If you are running SQL Server services using a domain account, you may get a failure “Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON' .
In this case the recommend solution is to configure a SPN (Service Principal Name) for SQL Instance hosting the database. For example:
setspn.exe –a MSSQLSvc/sqlserver1.contoso.com:1433 sqlserver1
where sqlserver1.contoso.com is the FQDN of the SQL Server, and 1433 is the port, and sqlserver is the hostname/accountname for the SPN, or
setspn.exe –a MSSQLSvc/sqlserver1.contoso.com:RTCINST
sqlserver1
where sqlserver1.contoso.com is the FQDN of the SQL Server, and RTCINST is the instance name, and sqlserver is the hostname/account name of the SPN.
Please refer to the SQL and setspn.exe documentation for detail on setting up an SPN.
I've found this to be very much undocumented so am assuming others must be using ST's without error... Not sure where i'm going wrong. Any help much appreciated.
Cheers
Dave

Well. They say time is a healer. And this seemed to be the case. With no changes whatsoever, just a few service restarts, everything fired into life. To anyone else experiencing this error. Ensure your synthetic transaction
watcher node is a member of the RTCUniversalReadOnlyAdmins group, that and that the node has been restarted. Then try fully restarting SCOM and the synth node. Hope this helps someone else.
PortWatcherDiscovery.ps1 :
-Script Name:      Lync Server MP Port Watcher Discovery
-Run as account:   nt authority\network service
-Execution Policy: Bypass
Value of Source Id is {EB59D368-7D0B-91B6-E14A-2CF889E6BFA9}.
Value of ManagedEntity Id is {6598B4A8-7718-CF67-ECD8-A3C679029E00}.
Value of Target Computer is STNODE.LyncLab.Local.
Lync Server Module is added
McuFactorySipPort [lyfpool01.lynclab.local:444] is discovered.
RegistrarSipPort [lyfpool01.lynclab.local:5061] is discovered.
RegistrarWebPort [lyfpool01.lynclab.local:444] is discovered.
QoeSipPort [lyfpool01.lynclab.local:5061] is discovered.
WebsitePrimaryHttpPort [lyfpool01.lynclab.local:80] is discovered.
WebsitePrimaryHttpsPort [lyfpool01.lynclab.local:443] is discovered.
WebsiteExternalHttpPort [lyfpool01.lynclab.local:80] is discovered.
WebsiteExternalHttpsPort [lyfpool01.lynclab.local:443] is discovered.
[ReachPrimaryPsomServerPort [lyfpool01.lynclab.local:8060]] is excluded from port monitoring.
[ReachExternalPsomServerPort [lyfpool01.lynclab.local:8061]] is excluded from port monitoring.
AppSharingPortStart [lyfpool01.lynclab.local:49152] is skipped. Monitoring UDP Ports is not supported.
ImSipPort [lyfpool01.lynclab.local:5062] is discovered.
ImWebPort [lyfpool01.lynclab.local:444] is discovered.
[DataPsomPort [lyfpool01.lynclab.local:8057]] is excluded from port monitoring.
[MeetingPsomPort [lyfpool01.lynclab.local:8058]] is excluded from port monitoring.
AudioVideoSipPort [lyfpool01.lynclab.local:5063] is discovered.
AppSharingSipPort [lyfpool01.lynclab.local:5065] is discovered.
DataWebPort [lyfpool01.lynclab.local:444] is discovered.
MeetingWebPort [lyfpool01.lynclab.local:444] is discovered.
AudioVideoWebPort [lyfpool01.lynclab.local:444] is discovered.
AppSharingWebPort [lyfpool01.lynclab.local:444] is discovered.
AudioPortStart [lyfpool01.lynclab.local:49152] is skipped. Monitoring UDP Ports is not supported.
VideoPortStart [lyfpool01.lynclab.local:57501] is skipped. Monitoring UDP Ports is not supported.
AppSharingPortStart [lyfpool01.lynclab.local:49152] is skipped. Monitoring UDP Ports is not supported.
[MediationServerPort [lyfpool01.lynclab.local:5070]] is excluded from port monitoring.
[MediationSipClientTlsPort [lyfpool01.lynclab.local:5067]] is excluded from port monitoring.
MediaCommunicationPort [lyfpool01.lynclab.local:49152] is skipped. Monitoring UDP Ports is not supported.
CasSipPort [lyfpool01.lynclab.local:5073] is discovered.
CaaSipPort [lyfpool01.lynclab.local:5072] is discovered.
[TestBotPort [lyfpool01.lynclab.local:5076]] is excluded from port monitoring.
CpsSipPort [lyfpool01.lynclab.local:5075] is discovered.
RgsSipPort [lyfpool01.lynclab.local:5071] is discovered.
RgsWcfMtlsPort [lyfpool01.lynclab.local:8404] is discovered.
PdpSipPort [lyfpool01.lynclab.local:5080] is discovered.
PdpTurnPort [lyfpool01.lynclab.local:448] is discovered.
AudioPortStart [lyfpool01.lynclab.local:49152] is skipped. Monitoring UDP Ports is not supported.
VideoPortStart [lyfpool01.lynclab.local:57501] is skipped. Monitoring UDP Ports is not supported.
AppSharingPortStart [lyfpool01.lynclab.local:49152] is skipped. Monitoring UDP Ports is not supported.
Found an unsupported Role 'FileStore'.
Found an unsupported Role 'ExternalServer'.

Lync 2013 Server / Roles & Components

Lync
2013 Server / Roles & Components
Front End
User authentication and registration
Presence information and contact card exchange
Address book services and distribution list expansion
IM functionality, including multiparty IM conferences
Web conferencing, PSTN Dial-in conferencing and A/V conferencing (if deployed)
Application hosting, for both applications included with Lync Server (for example, Conferencing Attendant and Response Group application), and third-party applications
Primary store for user and conference data. Information about each user is replicated among Front End Servers in the pool
Optionally, Monitoring, to collect usage information in the form of call detail records (CDRs) and call error records (CERs). This information provides metrics about the quality of the media (audio and video) traversing your network for both Enterprise
Voice calls and A/V conferences.
Web components to supported web-based tasks such as web scheduler and join launcher.
One Front End pool runs the Central Management Server DB, which manages and deploys basic configuration data to all servers running Lync
Optionally, Archiving, to archive IM communications and meeting content for compliance reasons.
Optionally, if Persistent chat is enabled, Persistent Chat Web Services for Chat Room Management and Persistent Chat Web Services for File Upload/Download.
Back End
Database server running Microsoft SQL Server
Provide the DB services for the Front End pool
Acts as backup store for the pool’s user and conference data
Primary stores for other DB’s like Response Group
High Availability for the BE DB is provided via SQL Mirroring
Optional Witness to enable automatic failover for BE
SQL Sever 2008 R2 or higher required for SQL Mirroring
Edge Server
Enable users to communicate and collaborate with users outside the organization’s firewall
Comprises four separate server roles
Access Edge – Acts as a secure proxy for all remote Lync signaling traffic
Remote Access
Federation
Public IM Connectivity (PIC)
Web Conferencing Edge – Enable remote users to participate in Web conferences with internal or remote workers
A/V Edge – Responsible for secure relay of A/V media among internal, external, and federated contacts
XMPP Gateway – Allows IM/P with XMPP federated contacts
Reverse Proxy
Simple URL Publishing – Required for users to join Lync meetings
Web Conferencing Content – Users download meeting content (PowerPoint, Whiteboard, and Poll data) via Lync Web Services when in meeting
Address Book & Distribution List Expansion – Required for users to download Lync Address Book and perform DL expansion
User Certificates – Provides client certificate authentication via Lync Web Services
Device Updates – Provides software updates to Lync IP endpoints
Mobility – Provides connectivity for mobile clients via Lync Web Services
Mediation Server
Translates signaling and media between Lync Server and PSTN, IP-PBX, or SIP Trunk
Can be co-located on Front End or separated as stand-alone Server dependent on call volume
Role facilitates dial-in conferencing
Capacity
Co-located = 150 Concurrent Calls
Standalone = 1100 Concurrent Calls
Persistent Chat
Enable users to participate in multiparty, topic-based conversations that persist over time
Pchat Front End server role runs persistent chat service
Pchat Back End server stores chat content and compliance events
Geographic DR is provided via stretched pool and SQL log shipping to replicate DB info
150k provisioned users / 80k concurrent users
Archiving
Uses SQL Server 2008 R2 or SQL Server 2012 for DB
Capable of archiving the following:
Peer-to-peer IM
Multiparty IM
Web Conferences, including uploaded content and events
A/V for peer-to-peer IM and web conferences
Web conferencing annotations and polls
Monitoring
Agent that runs on each Front End Server that collects and manages information from the Front End and Mediation Servers
Stored on SQL Server DB
Leverages SQL Server Reporting Services for creation of reports related to call quality and metrics
Office Web Apps Server
External server leveraged for rendering PowerPoint slides within the Lync client and Lync Web App
Typically leveraged within SharePoint deployments to deliver browser-based versions of Microsoft Office applications
System Center Ops Mgr
Health configuration in Lync Server 2013 is built around System Center Operations Manager and the use of Lync Server Management Packs. These Management Packs include a number of new features and enhancements, including:
Feature
Description
Synthetic Transactions
Windows PowerShell cmdlets that can be run from various locations to ensure that end user scenarios such as sign-in, presence, IM, and conferencing are readily available to end users.
Call Reliability Alerts
Database queries for Call Detail Records (CDR). These records are written by Front End Servers to reflect whether end users were able to connect to a call or why a call was terminated. These queries result in alerts that indicate when a wide range of end
users are experiencing connectivity issues for peer-to-peer calls or basic conferencing functionality.
Media Quality Alerts
Database queries that look at Quality of Experience (QoE) reports published by clients at the end of each call. These queries result in alerts that pinpoint scenarios where users are likely to be experiencing poor media quality during calls and conferences.
The data is built upon key metrics such as packet latency and loss, metrics that are known to directly contribute to call quality.
Component Health
Individual server components raise alerts by using event logs and performance counters. These alerts indicate failure conditions that can severely impact one or more end user scenarios. These alerts can also indicate a variety of other failure conditions,
including services not running, high failure rates, high message latency, or connectivity issues.
Dependency Health
Failures can occur for a variety of external reasons. The management packs now monitor and collect data for some of the critical external dependencies that might indicate severe issues, including IIS availability, CPU and memory usage of servers and processes,
and disk metrics.
Exchange UM
http://www.contactcenterarchitects.com/lync-2013-server-roles-components/

Hi,
Thank you for sharing the information. It is useful for others who not understand Lync Server Roles and Components. You time and effort are appreciated.
Best Regards,
Eason Huang
Eason Huang
TechNet Community Support

Maintenance Mode for Synthetic Transactions

Hi,
I'm looking for some guidance on how to apply Maintenance Mode to specific Synthetic Transactions correctly via Orchestrator. My setup is Orchestrator 2012 R2 (and SCOM 2012 R2)
I have an existing runbook which seems to run fine for placing a group of windows computers into maintenance mode - I 'think' it is ok, in 2012 there seems to be a single start maintenance mode activity targeting the windows computer object for this, wereas
in 2007 there were 3 objects to target - the windows computer, health service and health service watcher.
So now I'm trying to apply maintenance mode to specific Synthetic Transactions if possible - ie web application transaction monitors which run on 2 servers which are dedicated as watcher nodes for many other ST's aswell. I had thought I had the issue
solved when I created the runbook to set Maintenance Mode targeting the specific Web monitors - when I execute the runbook I can see the spanner maintenance icon appearing against all the 'Closed' alerts from these monitors in the scom console - so I assumed
I was targeting the correct objects.
I've scheduled the runbook to trigger for the time when I know these monitors create alerts (ie when the web services are restarted nightly on the particular server web server and the site will be down) however I am still seeing the alerts come in to the
console (log history shows the runbook started OK on schedule) so I am wondering if there are other objects to put into maintenance - I assume I can't put the watcher node windows computer object into Maintenance Mode as this would be suspending the monitoring
of other Stnthetic transactions running on the watcher node servers?...
Any advice much appreciated...

Sure, no worries.
The authentication types can support 4 tyes of authentication from ntlm to basic. If the site does not require authentication all the better, as the monitor will use less resourses and its easier to configure.
R2 supports something like 10000 transactions to be monitored.
Paulpaulk

Synthetic Transactions Monitoring - Query

Hi,
Couple of things I would like to clarify related to Synthetic Transactions as I'm unable to find it clearly:
1) In SCOM, are Synthetic transactions executed parallel or sequentially? I could not find anything officially written on that? Lets say if I've 10 transactions to be monitored per watcher node, will it be executed one by one until one is completed or all
10 will be executed at the same time. How to identify?
2) A transaction with multi steps, will it be counted as one transaction or every step under that is treated as separate transaction?
3) Considering the point number 2 how many transactions are supported per watcher node
3) In the pre-req guidelines it is mentioned 50 URL's monitoring supported per agent. Is it just from URL availability point of view or anything else being said here?
Thanks,

Can anybody share views on this please?

Synthetic Transaction Monitoring

I would like to know if System Center 2012 can support Synthetic Transaction monitoring. what i need is that the SC 2012 will have to capture the synthetic transactions being generated by the third party generator. These transactions captured by SC 2012,
will have to provide transaction breakdown time between Web, App and DB layer’s and give over all End User experience.
Can any one suggest how SC 2012 will handle such requests? how to set it up? what KPI will SC 2012 do today for synthetic transaction monitoring.
please email me the response to [email protected] or [email protected]
Michael Martin

Hi Michael,
I don't think it is a big deal. Web Application Transaction Monitoring is performed by sending HTTP requests to your application from specified Watcher Node (Management Server itself, SCOM Agent or GSM points worldwide using appropriate subscription
http://stefanroth.net/2014/01/06/scom-global-service-monitor-using-visual-studio-web-test/). Just check out that your app is available and responds well to those HTTP requests, for sure it's better to record Web Application Transaction tests on
Watcher node explicitly.
Igor Savchenko, VIAcode Consulting LLC (http://www.viacode.com/)

Lync 2013 Enterprise load balancing on the front end and edge pool

Hi,
I am setting up a Lync 2013 Enterprise deployment consisting of a Front End pool (x2 FE servers) and an Edge pool (x2 Edge servers). I'm seeing some conflicting advice regarding load balancing using hardware or DNS for the front end and the edge.
On the front end I have 2 internal DNS records 'lyncfepool1.contoso.local' each of which map to one of the IPs of the FE servers. I've used my details to populate the Detailed Design Planner excel spreadsheet and am told that I require a HLB to load
balance my front end pool. I'm aware of the need to load balance HTTPS traffic internally (which will be done by TMG) however other traffic to the front end (SIP, etc) can be balanced by DNS only, and not require a HLB?
Can someone clarify the front end requirement?
Also - looking now at the edge pool - this site again have two edge servers in a pool. We are using a total of six private IP addresses, two per edge service (2 x av.contoso.com, 2 x sip.contoso.com and 2 x webcon.contoso.com). These will be
NAT'ed by the external firewall and directed to the respective external (DMZ) IP addresses on the Edge servers on port 443. I know this isn't true roundrobin due to the intelligence of the Lync client when connecting (in that the Lync client will connect
to one of the public IPs and if it can't connect, it will know to connect to the other service IP), however I want to clarify this set up, particularly the need to direct the external public IP traffic at the DMZ Edge IP specified in the topology builder.
I've attached a basic diagram of the external/DMZ/Edge side which hopefully helps with this question
Persevere, Persevere, Per..

That is because you will always need HLB for a front-end server since it hosts the Lync webservices which use HTTP/HTTPS traffic.
The description on the calculation tool also describes this correctly:
Supports Standard and Enterprise pools (up to 12 nodes), with pure device-based load balancing or a combination of DNS load balancing and device-based load balancing (for
Lync web services)
You can use either Hardware or DNS loadbalancing for SIP traffic only, but you will always need a HLB for the webservices. Both are applicable for the Front-End so you have either
full HLB for both SIP and HTTP(S) traffic
DNS LB for SIP traffic and HLB for HTTP(S) traffic
Hope this is more clear :-)
Lync Server MVP | MCITP Lync Server 2010 | If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.

Lync 2013 updating databases after updating Front End servers

We have a front-end server pool consisting of 3 Lync 2013 servers and a back end of 2 SQL servers using SQL mirroring. All servers are Windows 2008 R2.
Following the instructions in
http://support2.microsoft.com/kb/2809243 , I verified that the servers were all ready for updates, then I ran the
Stop-CsWindowsService -Graceful cmdlet to stop the Lync services on the first FE server, then I ran LyncServerUpdateInstaller.exe to install the updates. After the updates were installed, I restarted the server, waited for Lync services
to all start, then repeated the process on the next 2 servers in turn. This was all successful.
I am now looking at step 2 in this document, applying the back-end database updates, and I have a problem and some questions. The problem is that all the databases had the principal copy on the mirrored SQL server. I ran the recommended Invoke-CsDatabaseFailover
-NewPrincipal Primary cmdlet repeatedly, using all the database types I could find, but I still have two databases (database names
xds and lis) on the mirrored server. Since the cmdlet requires a database type, what type of databases are the xds and the lis databases?
Once I get that done, I an still unsure of exactly what to run to update the databases. The KB article states to run Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose .  Do I type this in exactly
as stated, or is FEBE.FQDN a variable for our SQL server or some other entity in our environment? If I do use the actual SQL Server name in that, do I run it twice, using the name of the mirrored SQL server the second time?
Thank you very much for your help.

Hi Logan Burt,
Central Management store database files
Data file or log purpose
                Xds.ldf
Transaction log file for the Central Management store
                Xds.mdf
Maintains the configuration of the current Lync Server 2013 topology, as defined and published by Topology Builder
                Lis.mdf
Location Information service data file
                Lis.ldf
Transaction log for the Location Information service data file
And you could verify if Lync Server 2013 database updates have completed successfully.
How to Verify if Lync Server 2013 Database Updates Completed Successfully
http://blogs.technet.com/b/dodeitte/archive/2013/07/02/how-to-verify-if-lync-server-2013-database-updates-completed-successfully.aspx
Best regards,
Eric

Lync 2013 Client takes a long time to "restore" from taskbar

On many Windows 8 & 8.1 systems in our environment the Lync client will take anywhere from 2-10 seconds to pop up when clicked on in the taskbar. The application is running, logged in, and active. This is very frustrating to our userbase
as they will click on it multiple times and have it then act like a jackrabbit when it finally processes the requested actions.
The computers we have are brand new systems. Happens on freshly installed & updated versions of Lync 2013. Seems to be after the Lync client hasn't been clicked on, or utilized in a while. Other applications pop up instantly (zero delay)
and without any problems, it only affects Lync. I tried disabling UI animations such as fade, slide etc, which did nothing to help the issue.
This has me a bit stumped, and I'm wondering if this is a known issue or not? Hopefully there is a solution?

I wouldn't say it's dismissive, I was asking for more information. I wanted to know if it was potentially an overactive endpoint protection application or something similar, if it can't be reproduced on fresh build of Windows then something is interfering
and it's difficult to work out not knowing what all is installed. Most people don't experience the issue so I imagine another piece of software may likely be conflicting.
I do agree that it's not an answer, at the least not very useful answer. Occasionally items get marked as answer but they're more of a "closed" as the original poster never responds.
I'd suggest posting your issue in the Lync 2013 forums instead as people are less likely to watch this post now that it's already marked "answered". Work through it and see what can be found, hopefully you'll find some good information which will be
more helpful to others.
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications

How can I manually verify autodiscovery configuration for on premise environment from Lync 2013 desktop client?

I have very limited access to an environment (basically just user access). I am documenting the Lync 2013 cilent for this environment. I was provisioned a limited SIP enabled account for testing. Autodiscovery from the Lync 2010 client works, but not from
the 2013 client. I can connect (with some issues) from either 2010 client (autodiscovery) and 2013 client (manually configuring the server). So I want to verify if the Autodiscover is configured correctly to work with the 2013 client or not and if the reason
it fails for me is due to something wrong with my account or if this will happen with other users?
I have checked the lyncdiscoverinternal.domain.com and it resolves and is reachable. I can navigate to https :// lyncdiscoverinternal.domain.com/Autodiscover/AutodiscoverService.svc/root/domain and it returns the information I would think it should
including hrefs to Internal/Autodiscover, Internal/AuthBroker, External/Autodiscover, External/AuthBroker, Internal/Mcx & External/Mcx as well as fqdns for SipClientExternalAccess, SipClientInternalAccess, SipServerExternalAccess & SipServerInternalAccess.
The AuthBrokers urls return what I believe is the expected RemoteService Service pages. The Mcx urls return what I believe is the expected McxService2 Service pages. The SipClientInternalAccess & SipServerInternalAccess fqdns are both resolvable and
reachable. The Autodiscover urls return hrefs for Domain and User. Those Domain urls return the same information as the initial root/domain url and the user url (which I believe is the one that is actually opened by lync during the autodiscover process) returns
what I believe is an expected 401 - Unauthorized: Access is denied due to invalid credentials page.
If I explicitly configure the Lync 2013 client to use the fqdn listed for SipClientInternalAccess, the client will log me in. However on Automatic configuration, it fails to log me in.
One other note is that when I watch with Wireshark, I observed that it is getting another internal server fqdn from somewhere. We'll just say that the SipClientInternalAccess fqdn is lyncABC.domain.internal. When looking at Wireshark and the DNS requests,
I'm also seeing a lync2013ABC.domain.internal that does resolve and is reachable and can also be used as the explicitly listed server in the Lync 2013 client and it will log in. However, that fqdn is not listed in any of the root or domain url replies. So
I'm not sure where it is coming from or how to check that.
Is there any additional information anywhere that can tell me exactly what the behavior of the 2013 client is when trying to find the server to authenticate to and how I can reproduce any missing steps manually to determine what it is identifying as the
login server (if any) since it is obviously not the trying the one listed as SipClientInternalAccess?
Thanks,
Richard

Hi Richard,
To narrow down the issue, you could refer to the following steps first.
1. Delete the Lync client 2013 user profile and registry key.
User profile:
%userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\[email protected]
Registry Key:
HKCU\Software\Microsoft\Office\15.0\Lync\[email protected]
Certificate:
a. Open Windows Certificate Manager. To do this, press Windows + R, type certmgr.msc, and then click OK.
b. Expand Personal, and then expand Certificates.
c. Look for a certificate that's issued by Communications Server and delete it.
2. Upgrade Lync client to the latest update.
3. Check the DNS records(A records and SRV records) again.
Best regards,
Eric

Lync 2013 Watcher Node Synthetic Transactions

Similar Messages

Maybe you are looking for