www.SysAdmins.eu

Hello Guys, Did you ever felt the need to set up Auto logon to Windows Server or Workstation? Sometimes it is needed. Especialy in Internet Coffee's, or similar places. There is an old way to setup it using Regedit. But there is also way to use PowerShell to accomplish it. Take a look on two simple functions. This function are easy to use in you scripts. I am using it for building testing environement. All You need to do, is to set up $PlainTextAccount and $PlainTextPassword variables.

Hello Guys! In Lync 2013 we have an option delete all or partial content of Persistent Chat Room! This can be easily done by powershell cmdlet Clear-CsPersistentChatRoom. Detail description of that cmdlet can be found here: http://technet.microsoft.com/en-us/library/jj204976.aspx And now some examples: his example will remove all content before 1.1.2014 from PChatRoom: Clear-CsPersistentChatRoom -Identity "contoso.com\PChatRoom" -EndDate "1/1/2014" This example will remove all content before 1/1/2014 from all Persistech Chat Rooms: Get-CsPersistentChatRoom | Clear-CsPersistentChatRoom -EndDate "1/1/2014" -Confirm: $False This example will remove content older 180 days from all Persistech Chat Rooms: Get-CsPersistentChatRoom | Clear-CsPersistentChatRoom -EndDate ( [ DateTime ]:: today . AddDays( -180 )) -Confirm: $false

Today I had to installed Persistent Chat to our existing Lync 2013 Standart environement. Plan was use dedicated server for Persistent chat and second dedicated server for SQL Server 2012. Installation was simple as expected. After successfull installation Persistent Chat service could not start. Why? I checked Event Log and found two Events: Event ID 53553: The server is not compatible with the database at Data Source=SQL1.HELL.LOCAL;Initial Catalog=mgc;Integrated Security=SSPI Event ID 53503: Microsoft Lync Server 2013, Persistent Chat could not start due to the following exception:  at Microsoft.Rtc.Internal.Chat.Server.ServerCommon.Exceptions.StopServerException: Unexpected DB version. Problem was not in SQL server version. SQL server 2012 is supported and installation was successfull. Setup process also created necessary databases. Solution was install Lync updates using LyncServerUpdateInstaller.exe utility. Update utility can be downloaded from  http:/