Supported or not Supported, this is the Question

Summary of Lync Supported and Non-Supported Configurations

Teams Dude


: thanks to Lync MVP Thomas Poett, and his input, I updated the article

how many times did you stumble upon a question from a customer if a certain feature or deployment scenario is supported by Microsoft and Lync 2013 or not.

we all forget, I mean there is a new stuff happening in our world (UC) every minute and sometime we loss tracks, so I have what I call my SCS (supported Cheat sheet) where I keep all information I have through my years in Lync by something I read or researched or learned from someone else about Lync supportabilities, and I decided to share it here in a blog article about what is supported or not supported regarding Lync 2013.

feel free please to correct my information, or put a comment about something I did not mentioned and I will be add it to this article…

View original post 909 more words

One-Liner: Open Start Menu From Powershell

Working on Windows Server 2008 in a RemoteDesktoption (remote desktop inside remote desktop inside remote desktop), It’s a challenge to point the mouse curser to the exact lower left pixel to open the start menu.

Good News, Just open Powershell, and past this one-liner to simply open the start menu  without changing anything or creating any files on the server.

 $wshell = New-Object -ComObject;$wshell.SendKeys('^{ESC}')

P.S.: Of course you can also create a VBS script to do same. but in my case, this wasn’t preferable.

Simple Understanding of Lync Windows Fabric & Failover

Why you should deploy “3” Frontend Servers in Lync Server 2013 Enterprise pools.

Teams Dude


I saw a scary number of Lync 2013 deployments in the last 8 months where the Lync is deployed using an Enterprise pool with only two front end servers, even I saw a couple that have an Enterprise pool with only one front end server, yes you read that right, only one front end server.

So I decided to write another post of my “Simple Understanding” article series aimed to explain the Lync 2013 server architecture, how it utilize windows fabric for high availability and why you should not deploy a 2 nodes Enterprise Edition pool, I’ll try to use small words and simple explanations as I can.

I’m planning also to use this article as a guide to share with customers which have an existing Lync deployment or considering Lync to help them in their decisions.

View original post 1,514 more words

SQL Server 2012 automated Install ini Feature list

Good reference to interpret/create SQL installation ini file

Understanding SQL

Any DBA worth their salt will have automated the deployment of any version of SQL server using a SQL server configuration ini and a standard installation script. Through the ini, you can manage exactly what you required to be installed, where you want it installed and how you want your features to run.

With the introduction of SQL Server 2012, Microsoft introduced some new features that can be included in your network standard installation, so I figured it was time to update the list of features and their abbreviated name that needs to be included in the ini.

In your ini, you will have a line approximate to this:


For reference, here are the full names:




Server Engine




text Search


Quality Services




Services – Native


Services – SharePoint



View original post 75 more words

Disable Lync User Vs. Remove Lync User From ADSI Edit View

In this post, we will user ADSI Edit to look into a Lync Enabled user Properties, and note what changes when we temporarily disable, and remove the user from Lync.

Original Lync User properties:

2014-12-26 13_12_33-Disable Vs. Remove Lync User - Microsoft OneNote

Disable Lync User:

2014-12-26 13_13_57-Disable Vs. Remove Lync User - Microsoft OneNote

2014-12-26 13_15_02-Disable Vs. Remove Lync User - Microsoft OneNote

Remove Lync User:

2014-12-26 13_15_58-Disable Vs. Remove Lync User - Microsoft OneNote

2014-12-26 13_16_41-Disable Vs. Remove Lync User - Microsoft OneNote

2014-12-26 13_17_14-Disable Vs. Remove Lync User - Microsoft OneNote

2014-12-26 13_18_07-Disable Vs. Remove Lync User - Microsoft OneNote


Selecting “Temporarily Disable For Lync Server” for a user: Will sets the msRTCSIP-UserEnabled value to FALSE, and will maintain all the user Lync attributes

Selecting “Remove From Lync Server” for a user: Will remove all Lync attributes from the user. and the Active Directory user itself will not be deleted.

Windows 2012 R2 server With Hyper-V Shutdown Automatically by wlms.exe Process

I just installed Windows 2012 R2 server for lab testing, and installed the Hyper-V role over it, then noticed that the server shutdown automatically after a period of time.

by checking the event viewer, below event was logged prior the shutdown:

Log Name: System

Source: USER32

Event ID: 1074

The process C:\Windows\system32\wlms\wlms.exe (<Computer Name>) has initiated the shutdown of computer <Computer Name> on behalf of user NT AUTHORITY\SYSTEM for the following reason: Other (Planned)
Reason Code: 0x80000000
Shutdown Type: shutdown
Comment: The license period for this installation of Windows has expired. The operating system is shutting down.

As the event states: The license period for this installation of Windows has expired.

Activating the server will solve this problem permanently, but for meanwhile I re-armed the activation using this command:

Slmgr.vbs -rearm

[Batch] Backup Entire Folder with Current Date and Time

During my work on documentations, I usually will need to take different  snapshots of the current documentations folder at every milestone.

This batch will ask you for the folder you want to backup, then will create a new folder inside this folder named “AutoBackup” –> then will create a new folder with the current date and time inside this AutoBackup folder.

@Echo off
SET /P BackupPath=Please Enter the Folder Path to Backup:
MD "%BackupPath%\AutoBackup"
Set FolderNameFull=%BackupPath%\AutoBackup\%date:/=-%_%time::=%
Set FolderNameFinal=%FolderNameFull:~0,-5%
MD "%FolderNameFinal%"
Robocopy "%BackupPath%" "%FolderNameFinal%" /E /XD *AutoBackup

RTCP active calls must be false if bypass is enabled and refer support is disabled Error

Reblog for your favorite post…

Ibrahim Soliman Blog


In Lync Server 2010 While configuring a trunk to enable media bypass, and disable (un-enable) the refer support (as the recommended settings when creating a SIP trunk to Cisco Unified Communications Manager CUCM), you may receive the below error when you try to commit changes:





in the below example, my Trunk name is: PstnGateway:

– in the trunk prosperities, Temporarily un-enable the media bypass, and commit to save changes:


– Now, let’s open Lync Management shell and check the status of RTCP Active Calls, and RTCP Calls on hold:


We see both are True by default, Also note the EnableSessionTimer status is False.

– Now, run the below commands to set RTCPActiveCalls and RTCPCallsonHold as false:


– Now lets check the status again:



Commit to save, and it should complete successfully this time


View original post

Configure The Windows Services Recovery Options From Command Line

The command will configure the recovery options for a given service as:

  • First Failure: Restart the Service
  • Second Failure: Restart the Service
  • Subsequent failures: Take No Action (this is set to “take No Action” to avoid infinite restart attempts)
  • Restart Fail Count After: 1 Day
  • Restart Service After: 1 minute

2014-11-02 14_08_32-Remote Desktop Manager [Quick connect - EGCTRX01DR] - Trial version expire in 5

SC failure <Service Name> actions= restart/60000/restart/60000/""/60000 reset= 86400

Example for Message Queuing service:

SC failure MSMQ actions= restart/60000/restart/60000/""/60000 reset= 86400

PowerShell: Find the LDAP address from a User Account


Import-Module ActiveDirectory
$Account = Read-Host 'Enter User Account'
$DN = Get-ADuser $Account
Write-Host LDAP://$DN

Run the script from your domain controller.

The script will ask you for the user logon name, and will display the relative LDAP address in the form of: LDAP://CN=………,OU=…..,OU=………,DC=…….,DC=…..