8,330 questions
Skype Front End Server Deployment Wizard Fails to Start Services When Automated
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(185.6, 72%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EN%3C/text%3E%3C/svg%3E)
Neil676
1
Reputation point
I am automating the deployment of Skype for Business Server 2019 front end servers on a Server 2022 OS on prem. When using the commands below to run step one of the deployment wizard, the Skype services fail to start, each with an error of "Check to make the the service is not disabled. Failure to start could also be because this front end was previously failed over". There is only a single standard edition server in it's own pool and this has been replicated on different systems. Manually running step one allows the services to start successfully. Any ideas why?
& 'C:\Program Files\Skype For Business Server 2019\Deployment\bootstrapper.exe' /Bootstraplocalmgmt /SourceDirectory:"C:\OCSVolume\Setup\amd64"
$CSConfigExp = Export-csconfiguration -asbytes
Import-CsConfiguration -Byteinput $CSConfigExp -LocalStore
Enable-CsReplica
Windows for business | Windows Server | User experience | PowerShell
Microsoft 365 and Office | Skype for Business | Windows
648 questions
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 24%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJM%3C/text%3E%3C/svg%3E)
JimmyYang-MSFT 58,641 Reputation points Microsoft External Staff2024-03-22T09:06:24.3133333+00:00 Do you mean this issue only happened when using Automated PowerShell script, right?
-
Neil676 1 Reputation point
2024-03-22T10:11:44.5+00:00 Yes, it only happens when using the code instead of running step 1.
-
Neil676 1 Reputation point
2024-03-22T11:02:17.1366667+00:00 Yes, using the above code to in essence complete step one of the deployment wizard causes the issue, but can't work out why.
Sign in to comment
Sign in to answer