Skype for Business Front-End Service stuck on Starting caused by McAfee

This is a common issue and can be resolved by running the following cmdlet in PowerShell.

Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List *&lt;/pre

<img class="wp-image-1875" src="http://www.thatlazyadmin.com/wp-content/uploads/2017/11/word-image-94.png" />

if no certificates have been resolve, then it means that we need to move on and try then next steps of troubleshooting.

To try and resolve this issue now, we need to reset the CSRegistar Pool state by running the following cmdlet.

<strong>Note: Kill the service first.</strong>

Get-Childitem cert:\LocalMachine\root -Recurse | Where-Object {$_.Issuer -ne $_.Subject} | Format-List *</pre

if no certificates have been resolve, then it means that we need to move on and try then next steps of troubleshooting.

To try and resolve this issue now, we need to reset the CSRegistar Pool state by running the following cmdlet.

<strong>Note: Kill the service first.</strong>

Get-Service –DisplayName “Skype for Business Server Front-End” |Stop-Service –Force

1	Get-Service –DisplayName “Skype for Business Server Front-End” \|Stop-Service –Force

Let’s go ahead and start the reset process.

Reset-CsPoolRegistrarState -PoolFqdn "servername" -ResetType ServiceReset

1	Reset-CsPoolRegistrarState -PoolFqdn "servername" -ResetType ServiceReset

Type Yes and Press Enter

1	Type Yes and Press Enter

After the ServiceReset the service is still stuck on Starting. So, let’s move on to try and resolve it.

To continue the troubleshotting steps, I will now use the below cmdlet with ResetType QuorumLossRecover

Reset-CsPoolRegistrarState -PoolFqdn “poolfqdn.pool.local” -ResetType QuorumLossRecover

1	Reset-CsPoolRegistrarState -PoolFqdn “poolfqdn.pool.local” -ResetType QuorumLossRecover

After waiting for the service to start, it still did not start so now I started looking at Windows update and what else could have caused the service just to fail without any sign.

After some checking I found that there was a new McAfee patch installed, so I went and removed that patch.