Move-CsManagementServer failed

During a migration from Lync Server 2010 to Lync Server 2013 there is a point where you need to move the CMS database to a new Lync Server 2013.

In this case all Lync related data was installed on a D:\ drive as a requirement from the customer.

When installing the CMS database you need to use powershell to set the correct location to folder on the D:\ drive. 

After this step I started the Move-CsManagementServer and this failed during the bootstrapper.exe step with an error.

Error: An error occurred: "Microsoft.Rtc.Management.Deployment.DeploymentException" "Cannot find any suitable disks for database files. You must manually specify database paths."

The cause of this error was lack of free disk space on the C:\ drive. You still need 20 GB of free disk space on the system drive. After expanding the system drive lets run the Move-CsManagementServer again.....(no success)...and again with the Force switch.

PS C:\> Move-CsManagementServer -force

Confirm

This cmdlet moves Central Management Server to the pool that contains this

computer.

 Current State:

 Central Management Server Pool: "srvlync2013.contoso.com"

 Central Management File Store: "\\srvlync2013.contoso.com\LyncShare$"

 Central Management Store: "srvlync2013.contoso.com\rtc"

 Central Management Store SCP: "srvlync2010.contoso.com\rtc"

 Proposed State:

 Central Management Server Pool: "srvlync2013.contoso.com"

 Central Management File Store: "\\srvlync2013.contoso.com\LyncShare$"

 Central Management Store: "srvlync2013.contoso.com\rtc"

 Central Management Store SCP: "srvlync2013.contoso.com\rtc"

The last attempt to move the Central Management Server from

"srvlync2010.contoso.com\rtc" to "srvlync2013.contoso.com\rtc" either

failed or is in progress. Ensure that there is no other move operation in

progress and run this cmdlet with the -Force flag to retry the move to

"srvlync2013.contoso.com\rtc".

Note:

As you can read the CMS is correctly moved to the new Lync 2013 server but the SCP is still pointing to the old Lync 2010 server. When the Master Replication service and the File Transfer Agent service are starting they read out the SCP and they stop running because both services try to connect to a server with an incorrect database version.

The move is still failing with an error:

Move-CsManagementServer : Export configuration data failed. Exception Details:

Exception : System.Data.SqlClient.SqlException (0x80131904): Could not find

stored procedure 'dbo.XdsBackupAllItems'.

At this point Lync is still running without any problems. It is even possible to access the Topology Builder and download a configuration. But replication of the config to other servers is not working. To solve this error I created a backup from the XdsConfig and LisConfig database with Export-CsConfiguration and with Export-CsLisConfiguration cmdlets. 

Now again I started to move the CMS with Move-CsManagementServer -ConfigurationFileName "C:\CsConfiguration.zip" -LisConfigurationFileName "C:\CsLisConfiguration.zip" -Force

A Voila ...... a working system is the result!!!

Citrix releases Display Adapter Plug-in for Microsoft Lync 2013

With Lync™ 2013, Microsoft has introduced a new VDI Plug-in for Windows devices. This Tech Preview release enables the Microsoft® Lync™ 2013 VDI Plug-in to be used with the Citrix Receiver for Windows 3.x and XenApp 6.x. The Tech Preview consists of a new plug-in to the Citrix Receiver for Windows called the Display Adapter Plug-in. This new plug-in supports the Remote Desktop Protocol Geometry Tracking Extension used by Lync 2013 and related Windows components to insert and correctly position child windows for rendering Lync video. With this architecture, all Lync media processing is done on the user’s Windows device, maximizing XenApp server scalability and ensuring optimal audio-video quality.

Documentation for the Display Adapter Plug-in is available here

Microsoft Lync 2013 VDI Plug-in download (here you don't need a Citrx account)

This release is still a Tech Preview for more information go to www.citrix.com

Citrix HDX RealTime Connector for Microsoft Lync was unable to sign in

Finally I was able to do some testing with the Citrix Lync optimization pack and off course installing was not a problem but when logging on Lync within XenApp the following error occurred.

"Citrix HDX RealTime Connector for Microsoft Lync was unable to sign in."

After retyping my username and password the Services Sign In was still not able to sign in.
When viewing the status in of the Citrix HDX RealTime Connector for Microsoft Lync in the Lync client, this is done by clicking on Audio Video Settings the service was not registered.

In the next screen print the status is Registered but it was not before I added some registry keys.

To get the Citrix HDX RealTime Connector to registred correctly the following registry keys were added.

 

After restarting the Lync client the Citrix HDX RealTime Connector was working as expected.

If you look good to the Lync client there is a difference how to start an audio or video call.

When one of the above is selected there will be an other screen what is part of the Citrix HDX solution.

Here you can see that Citrix is actually handling the call. Also when there is an inbound call in XenApp session the Toast is slightly different form the normal Lync client.

 

 

When Video is used this is actually video from the local client which is displayed in the ICA session just like it's done with flash offloading.

 

When you tried to capture the screen it will be a screen dump without the video content.

 



This picture is taken with my phone.

I think Citrix has done some good work because with this pack it is possible to have audio and video within Citrix XenApp. Audio and video were not bad at all but I haven't tested with a lot of users and not when the system is used in a production environment.

Exchange Server 2010 SP3 Released

http://blogs.technet.com/b/exchange/archive/2013/02/12/released-exchange-server-2010-sp3.aspx

Office 365, error: Configure Legacy Exchange Support

Ever faced a problem like ERROR:Updating hybrid configuration failed with error Subtask ValidateConfiguration execution failed: Configure Legacy Exchange Support.
Today I have seen this issue and it took while before the problem was solved.

What preceded was an uninstallation of Exchange 2007 organization and before that I moved all Public Folders to Exchange 2010 Server.  After these tasks I needed to change some of the settings of the Exchange hybrid configuration and there you go.

ERROR:Updating hybrid configuration failed with error ‘Subtask ValidateConfiguration execution failed: Configure Legacy Exchange Support at Microsoft.Exchange.Management.Hybrid.Engine.ExecuteTask(TaskBase taskBase, TaskContext taskContext)

When using the verbose switch there are messages like Get-PublicFolder  -Identity '\NON_IPM_SUBTREE\SCHEDULE+ FREE BUSY' -Server 'Your Server Name' -recurse

It looks like Exchange is finding some old configuration because it's claiming legacy exchange support. The only thing what was changed was the location of Public Folders and ofdfcourse the decommissioning of Exchange 2007.

The solution was not more than running the folowing command on the Exchange Servers where the Public Folders resides. 

Run the install cmdlet . To do this user need to launch Windows Powershell (not the Exchange Management Shell) and then run the commands as below:

1. Start powershell.exe
2. add-pssnapin Microsoft.Exchange.Management.PowerShell.Setup
3. install-freebusyfolder -verbose

Now re-run the Hybrid Configuration Wizard from the On-Premise mailbox server. User should not receive the above errors now.

Original article for the solution is found here 

Response Group Monitoring Part 4

I almost forgot to share this with you. Some guys did a really good job, they have updated the response group monitoring web app. Take a look at http://lyncrd.com/2012/11/21/lync-rgs-monitor/

You can download the updated files and again you can enjoy Lync!

Thanks a lot to Ismael Batista for sharing this with us.

Skype on Windows 8

Here a preview of Skype with a metro style interface on Windows 8

 

Skype on your Windows 8 Metro Style Interface

 

 

Skype main menu

 

Click to call

 

Same look and feel with Lync 2013

 

Lync and Skype will work hand in hand