Skype for Business – Moving the Fileshare Error

Hello All

This blog post is to share the experience seen with issues around moving the Skype for Business fileshare from one windows server to another.

Its worth noting that this was a real life issue seen on a clients site so elements of the image are blackout to hide the clients identity.

Below is the details and scenario seen

I followed this set Microsoft procedure to move the actual file share:

  1. Create the new file share and configure the correct permissions;
  2. Stop all Skype for Business services across all FE’s in the Enterprise pool;
  3. Configure topology to include new file store and associate with the Enterprise pool before publishing changes;
  4. Run bootstrapper on all FE’s;
  5. Copy data from old file share to new one using robocopy;
  6. robocopy \\OldServerFQDN\OldShare \\NewServerFQDN\NewShare /S /R:10 /W:10 /XF Meeting.Active /MT;
  7. Start the Skype for Business Enterprise pool using Start-CsPool commandlet;

After following each of the steps about, all services started successfully however after a basic health check it appeared that there was an issue with the backup service (pool pairing), see below:Image1

Image2

So go figure….?

My next steps was to de-configure the pool pairing and re-configure it, however the error same occurred.

I then proceeded to reboot each Frontend in turn, same error occurred after rebooting all Frontend’s.

Everything looked good at this point in terms of File Store association with the Enterprise pool. The old file share was not referenced anywhere.

THE FINAL PART OF THE FIX

The fix was to move the WebServices* directory on the old file share into a temp directory, very bizarre as the old share was not referenced anywhere in Topology/PowerShell. 

After moving this directory and restarting the backup service again, all the errors cleared and the backup service returned to normal state.

 

Advertisements

Lync 2013 – Lync Phone Edition Update version 7577.4455

Yesterday evening Microsoft released an update to the Lync phone edition endpoints.

there are a number of timezone fixes included and the details can be found here.

 Product Version Download
Lync Phone Edition (for Aastra 6721ip and Aastra 6725ip) 4.0.7577.4455 3004836
Lync Phone Edition (for HP 4110 and HP 4120) 4.0.7577.4455 3004838
Lync Phone Edition (for Polycom CX500, Polycom CX600, and Polycom CX3000) 4.0.7577.4455 3004839

Lync 2013 – Lync client update April 2014

Yesterday Microsoft issued a bumper of a update for the Lync 2013 client build April 2014.

This update will soon form part of the office update suite but for now its available via the MS download page here.

http://support.microsoft.com/kb/2880474/en-gb

The update is a good one with lots of code fixing within it.

2941631 Cannot drag a distribution group to change position in your contact list in Lync 2013 

2941639 Call forwarding to the Response Group fails in Lync 2013 

2941640 Desktop sharing session stops in Lync 2013 when all screen data is updated 

2941643 Caller cannot close the window of a transferred call in Lync 2013 

2941654 Update sorts and searches contacts by Furigana in Lync 2013 

2941658 CTRL+TAB does not work when you switch between conversation windows in Lync 2013 

2941682 Instant message appears using incorrect text format when the DisableRTFIM setting is enabled in Lync 2013 

2941659 Callee’s name and detailed information is missing from the conversation history of a Lync 2013 outgoing call 

2941636 Search fails in Lync 2013 when non-Latin characters are used in a different case from the AD DS attributes 

2941635 Can’t sign in to Lync 2013 when Office 365 account UPN differs from domain account UPN 

2954951 Slow screen update in application sharing or desktop sharing session in Lync 2013 

2955577 Lync 2013 takes a long time to sign in after reconnect to the network 

2955579 Lync 2013 displays un-encoded texts in a toast notification or an instant message sent to another messaging client 

2955580 Update adds a button to show details about limited functionalities when Lync 2013 connects to a backup pool 

For me there are a couple of interest. And these are 

Fixed calls failing when forwarding into a response group.

And the reconnect time taking a long time.

 

When you putting the update on ensure you have met all the prereqs detailed within the information of the download page.

Lync For Mac – Client update April 2014 version 14.0.8

Released today is the new Lync for Mac update. Only two items detailed as fixes where one of them is quite interesting.

2952676 

Delegate doesn’t receive notification when you set delegation by using Lync for Mac 2011 

2952671 

Update enables Lync for Mac 2011 to run in Mac OS X Mavericks 

** I thought it was always supported on Mavericks?

Get the link here http://support.microsoft.com/kb/2952672/en-us 

Lync 2013 / 2010 – Public Edge Certificate missing its private key

Recently i have seen the issue of your public cert missing its key on import. The situation is when you create the required .req for your public certificate on edge you send the details off to the certificate authority of choice. Once they create and return the .crt file and the necessary trusted root and intermediate certs you import them into the Lync edge server only to find that the ‘sip.<domainname>.com’ cert is missing its private key.?

Why would this be the case when you originally generated the request on the Lync edge server? At this moment the only reason i can see is if another certificate with the same name has previously been imported onto the server. Apart from them i cannot find any other logical reason for why sometimes the newly imported certificate misses the private key.

if you are in this position, the simple fix to the cert is as follows

– On the imported certificate without the private key, double click the cert to show the information associated with it. Click on the details tab and look for the field called ‘Serial’. Copy the serial key into notepad and remove the spaces below the unique code. ie

WAS 5a 12 6e 7e ee 11  AMENDED 5a126e7e11

now still on the edge server open command prompt and type the following

certutil –repairstore my <Amended unique serial number>

eg: certutil –repairstore my 5a12637e11

press enter to commit it.

you will then be presented to information and also confirmation that the update has been successful.

now if you go into the certificate store and refresh you will see the certificate will now have the private key within it.

At this point you can go back to your Lync deployment wizard and assign the public cert to your edge server.

Job Complete

Thanks

Iain S

Lync 2013 – Creating Custom Lync Reports within Monitoring

Hello All

I haven’t seen much around guides on how to create custom reports for Lync 2013 so i thought it would be good to share the mechanisms on how to do this with the native Monitoring reporting tool which can be co-located with the Lync 2013 frontend.

For this guide I’m running a Lync 2013 Frontend patched upto CU version January 2014, and SQL Server 2012r2.. All servers are running windows 2012r2 and patched unto date.

Step 1.

Ensure the current reports are working as expected

1

Next step is to go to the SQL Server you provisioned and open up internet explorer and navigate to the reports path/URL for this demo that would be 

http://lync2013sql/reports_LYNCARCHMON

Also if you are unsure you can find the path required by going into the SQL Reporting Services configuration Manager and selecting reporting Manager (as below)

2

ok now we have navigated to our browser page lets select the report builder option.

3

NOTE: Depending on your original setup up, you might have to download and install the actual report builder application. (you will be prompted for this download if you haven’t already got it installed.)

Once installed or when the new dialog appears – Now select ‘new report’ as this is what we are wanting to do.

4

Once you’ve selected the table wizard, accept the default dataset ‘create a dataset’ and click next. 

Now you will be promoted for a data source, for Lync we need to browse to the data source down the tree.

5

select it and click ok. then do a quick test connection for clarity. now select Next, and when prompted add the credentials of your ‘privileged’  user account

6

 

Once you’ve added this information, you will be presented with a dialog which is called design a query. In this you can create your own report based on the information held within the Monitoring database. (everything), NOTE: it would be worth getting hold of the Lync 2013 database schema to understand all the tables available to interrogate.

for this demo, I’m going to select a stored procedure calls GetSCOMAlertData. this store procedure in the report and information which is passed to the SCOM application for reporting. 
in this scenario you don’t need SCOM, but you can get reports on what information would have been passed. I find this useful for monitoring your Lync environment. 
Also you could if you already had a reporting tool ie: Crystal Reports data mine your own information onto a crystal report and interact with other internal system databases.

7

 

On the arrange fields page drag and drop the required fields into the rows and columns 

8

 

on the next couple of pages select your layout and style and select next/finish

once this is complete you can select the ‘Run Report’ button to see your finished result. If your not happy you can go back and redesign the report as you wish.

9

 

Once you’ve tweaked your report to suit, no select save and navigate to the lyncserverreports folder and give your report a name and select save

10

now if you go back to your browser and select the original reporting path, you will see your newly created report within to select

11

 

Thats it. 

As i say there is a whole raft of information available to report on, so before you start i would suggest you have the report requirements at had and also have a good understanding of where within the CDR database that information is stored.

 

thanks again

 

 

Lync 2013 – Masking Information from Monitoring Reports – Video Config Guide

Hello all

This is a video guide on how to change the information in the backend SQL database for Monitoring information which has been added via the Lync CDR records.

In the video scenario what we are wanting to achieve is that some caller information and the certain callee has to be removed from all records within the monitoring database. IE: Say your company has a whistle blowing program were an employee can advise a team of any internal wrong doing within the company. Well this information would be sensitive information of who actually called the whistle blowing number and this could jeopardise the callee.

I hope this helps.

Regards

IainS

Lync 2013 – Move Response Groups from Lync 2010 to Lync 2013

In this blog post are the details whats needed to move you Lync 2010 response group over to Lync 2013. in truth there isn’t much to it really, just a couple of powershell commands.

to start with if you run the Get command to find information from your Lync topology about the response groups.

For Example

Get-CsRGSConfiguration then enter your pool <FQDN of your Lync 2010 Pool> this will bring details back about the Response Group application associated with Lync 2010.

Next Step is to backup the response group information just in case anything goes wrong. In order to back up your Response Groups, you need to make sure you have the Lync 2010 Resource Kit tools installed. After you have the tools installed, within your Lync Management shell, change the directory to where you installed the resource kit and then run:

Import-Module .\RgsImportExport.ps1

This will load the Powershell module so that you can interact with the Response Group service of Lync 2010. The next step is to run the export command in order to export the configuration.

Export-CsRgsConfiguration <service:poolFQDN> -Filename <path and file name for backup>

Example: Export-CsRgsConfiguration ApplicationServer:pool01.northernlync.local -Filename “C:\Lync_NLRgsConfig.zip”

Once this has exported we are now ready to migrate the response groups over from Lync 2010 to Lync 2013

In Lync powershell again we need to run the following commands

Move-CsRgsConfiguration -Source <Lync2010 Pool FQDN> -Destination <Lync2013 Pool FQDN>

eg: Move-CsRgsConfiguration -Source lyncse01.northernlync.local -Destination lync13pool.northernlync.local

Once this is complete, finally run a few commands in Lync Powershell to confirm the migration of the groups

Get-CsRgsAgentGroup  (ensure all the below is now pointing to the Lync 2013 environment 

Get-CsRgsQueue

Get-CsRgsWorkflow

thats it..

 

Lync 2013 – RTCSRV Frontend Service failing to start “showing as starting” PART 2 Certificate Store issue

Hello All

Here we are again for another blog post on a similar issue i posted about previous which was the RTCSRV service on the Lync 2013 front ends not starting.

This particular post is relating to the same RTCSRV service but this specific issue is Windows 2012 / r2 server build centric.

Ok so what was the problem.?? in both Standard and Enterprise edition builds you’ve ran through each element without issue, then you come to starting the services and bam, all of services start apart from the RTCSRV service which sits cycling on ‘starting’, so the first port of call for any issue like this is the event logs. At this point i was expecting the same damn issue with the quorum recovery due to the lync build still being RTM (not patched).

So after a quick glance at the event logs i ran in the updates to the topology. Jan 2014 updates. i then tried again with the service starting, and again it was stuck still cycling on the RTCSRV service. At this point i jumped back to the event logs as I’ve found that following the lync RTM build the information becomes a lot more ‘richer’ in content. As it happens this was the case, there was an error in the logs around certificates.? yet my installation was using an internal CA so why should i be getting these errors?

I checked the Internal CA for correct marking and trust, which all ticked out ok and then my next step was around certificates in general and the way windows 2012/r2 sees them differently. What i mean by this is the certs in the personal, intermediate and trusted root stores on windows 2008r2 server could in some cases be totally wrong and the lync services would start without issue. In Windows 2012/r2, Microsoft has done a lot of work around the certificate stores on the 2012 server build and put a lot more strict requirements within them. for example having a intermediate cert in the trusted root will throw an error in the event log. having duplicate trusts in the root trust will throw an error in the event log. etc etc

so what was the issue in my case. ? it was one i had seen before in a deployment and one which was totally unrelated to Lync and the Lync RTCSRV service. 

In the trusted root folder all certificates have to have a matching subject and issuer name or again an error would be thrown.. AND also having such an issue will stop the RTCSRV from starting for Lync.!!! crazy you might say.!

***What does Microsoft say about this.. Below

this is the event error in question

so to find this out there is a simple powershell command to run to identify this mismatched information on the trusted root certs.

Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List * | Out-File “c:\temp\certinformation.txt”

Once you have the information from your txt file, jump over to MMC and the certificate store and locate these certs in the root CA and move them to the intermediate store. Once you completed this close powershell and reopen to recycle the powershell information and rerun the command again. This time around you should have no information in your txt file.

Now if your running Standard edition simply start your fronted services.. If your running the enterprise edition, i would personally run the quorum recovery command to bring your fronted into sync, this will also start the services.

Thats it. i hope this has help other out