POCFabricInstaller failed because the following tasks failed: EnableCredSSP

Question

Hi,

I've been trying to get the AzureStack poc to work, without succes. I'm stuck on this error:

Start-PocFabricInstallerTasksPOCFabricInstaller failed because the following tasks failed: EnableCredSSP.

in c:\ProgramData\Microsoft\AzureStack\Logs\AzureStackDeployment-Error.txt I get this:

Start-PocFabricInstallerTasks : POCFabricInstaller failed because the following
 tasks failed: EnableCredSSP
At C:\ProgramData\Microsoft\AzureStack\Deployment\RunAzureStackDeploymentTask.p
s1:158 char:19
+ ...        $result = & "Start-$moduleName`Tasks" -StatusUpdatedCallback {
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep 
   tion
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio 
   n,Start-PocFabricInstallerTasks
 
C:\ProgramData\Microsoft\AzureStack\Deployment\RunAzureStackDeploymentTask.ps1 
: Azure Stack deployment failed in Task Group PocFabricInstaller
At C:\ProgramData\Microsoft\AzureStack\Deployment\Invoke-AzureStackDeployment.p
s1:41 char:5
+     & $PSScriptRoot\RunAzureStackDeploymentTask.ps1 -ErrorAction Stop ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep 
   tion
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio 
   n,RunAzureStackDeploymentTask.ps1

 

Any ideas on the cause of this?

Regards,

Sven.

Answer 1

Hi Sven,

Are you using a Private or Corporate domain network?

Please be advised that to Enable CredSSP make sure your network connection is either a private network or domain network. Afterward you may switch the network profile back to its original state. 

Regards,
Malar.

Answer 2

Hi Sven,

Please be advised that you would have to try to manually enable CredSSP on the host machine and re-run the deployment script.

These are the commands to run in an elevated PowerShell console:

winrm set winrm/config/client/auth ‘@{CredSSP="true"}’
Enable-WSManCredSSP -Role Client -DelegateComputer “*.azurestack.local”-Force 

Regards,
Malar.

Answer 3

Hi Malar,

Thank you for the quick response.

I've tried to perform the commands manually. This is the output:

PS D:\Microsoft Azure Stack POC> winrm set winrm/config/client/auth '@{CredSSP="true"}'
Auth
    Basic = true
    Digest = true
    Kerberos = true
    Negotiate = true
    Certificate = true
    CredSSP = true

PS D:\Microsoft Azure Stack POC> Enable-WSManCredSSP -Role Client -DelegateComputer "*.azurestack.local"-Force
Enable-WSManCredSSP : This command cannot be executed because the setting cannot be enabled.
At line:1 char:1
+ Enable-WSManCredSSP -Role Client -DelegateComputer "*.azurestack.loca ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (System.String[]:String[]) [Enable-WSManCredSSP], InvalidOperationExce
   ption
    + FullyQualifiedErrorId : WsManError,Microsoft.WSMan.Management.EnableWSManCredSSPCommand

The firewall is connected to domain and private networks, since PocFabricInstaller has run partially. It's possible that I selected a public network before I ran the powershell command.

When I disable the firewall, and try to run the commands you suggested I get the same output. I will restart and make sure I select private network before running the script.

regards,

Sven.

Answer 4

Sure Sven.
Please keep us updated with any issues or progress.

Regards,
Malar.

Answer 5

Hi Malar,

Still exactly the same error. I made a log of every step I took. For practical reasons, I'm installing Azure Stack on ESXi 6. 

This is the log:

new vm
AzurePoc
128 Gb ram, 16 cpu, 200Gb disk, vmxnet3 network
mount iso win 2016 (connected)
install Windows 2016 - Desktop Experience
logon, install vmware tools
reboot
static ip 10.1.100.100/16, dns 8.8.8.8

copy \\backup\c$\temp\Microsoft Azure Stack POC to c:\
copy c:\Microsoft Azure Stack POC\WindowsSerer2016Datacenter.vhdx to c:\MicrosoftAzureStackPOCBoot.vhdx
mount c:\MicrosoftAzureStackPOCBoot.vhdx
in cmd bcdboot e:\windows
reboot
logon, install vmware tools
reboot
static ip 10.1.100.101/16, dns 8.8.8.8
add 4 disk - 200Gb in ESX
in diskmgmt.msc bring disks online and initialize them
activate windows
disable IE enhanced security
install all windows updates
shutdown vm
remove vm from inventory
add these lines to vmx to enable vhv
hypervisor.cpuid.v0 = "FALSE"
vhv.enable= "TRUE"
add vm to inventory
boot vm

stop vm
make snapshot
start vm

start powershell and run
d:\Microsoft Azure Stack\DesployAzureStack.ps1 -verbose

The PocFabricInstaller failed:

Start-PocFabricInstallerTasks : POCFabricInstaller failed because the following
 tasks failed: EnableCredSSP
At C:\ProgramData\Microsoft\AzureStack\Deployment\RunAzureStackDeploymentTask.p
s1:158 char:19
+ ...        $result = & "Start-$moduleName`Tasks" -StatusUpdatedCallback {
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorExcep 
   tion
    + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorExceptio 
   n,Start-PocFabricInstallerTasks

If I try to ping azurestack.local, I get a reply from 192.168.100.2.

What could go wrong?

regards,

Sven.

Answer 6

Hi Sven,

Please make sure to run PowerShell in an admin context.

We see that you  are attempting nested install on ESX, please be advised this configuration is not supported.

Regards,

Pradeep

Answer 7

Hi Pradeep,

I'm aware that I'm running an unsupported configuration. The hardware specs are pretty steep for the poc. And fibre channel disks are not supported. By using ESX I can publish san disks to the vm to run AzureStackPOC.

However, I can't think of any reason why enabling CredSSP could fail, while running on ESX. 

I will try again to install the poc. This time by connecting the ESX (and thus the vm) only to the Internet. Until now the host and the vm are connected to the local lan.

I will need some time to reconfigure the setup, though.

Regards,

Sven

Answer 8

Hi,

I started from scratch again. This time the Host and the vm were connected to the internet only. Exactly the same error.

Any ideas why the this setup is failing?

Regards,

Sven.

Answer 9

Hi,

Could you confirm you are running PowerShell in an admin context?

Regards,

Pradeep

Answer 10

Hi Pradeep,

Yes I'm running powershell in an admin context.

Regards,

Sven.

Answer 11

Hi Sven,

Unfortunately the problem is probably tied to your running Azure Stack on ESX which is not supported in TP1.

Regards,

Pradeep