winrm Time out

[anoopkbaby1]

Hi Team,

     I am using vsphere-clone and while I am trying to setup getting winrm time out

==> vsphere-clone: Power on VM... ==> vsphere-clone: Waiting for IP... ==> vsphere-clone: IP address: 172.x.x.x ==> vsphere-clone: Using winrm communicator to connect: 172.x.x.x ==> vsphere-clone: Waiting for WinRM to become available... ==> vsphere-clone: Timeout waiting for WinRM. ==> vsphere-clone: Power off VM... ==> vsphere-clone: Destroying VM... Build 'vsphere-clone' errored: Timeout waiting for WinRM.

==> Some builds didn't complete successfully and had errors: --> vsphere-clone: Timeout waiting for WinRM.

==> Builds finished but no artifacts were created.

I am using the following snippet on the config :

    "communicator" : "winrm",
    "winrm_use_ntlm": "true"
    "winrm_insecure": "true",
    "winrm_use_ssl": "false",
    "winrm_username": "admin user",
    "winrm_password": "password"

Any suggestions and comments are really appreciated. If I use "communicator": "none" , its just cloning the VM successfully, but nothing from the "provisioners" section.

[LIV2]

@anoopkbaby1 Have you configured winrm to allow connections in your autounattend.xml?

A good example of how to do this is here in the FirstLogonCommands section

[anoopkbaby1]

@LIV2 Sorry I am got confused on your reply. Why we need autounattend.xml file?

[donwlewis]

@anoopkbaby1 you need that in order to enable WinRM and the firewall in order to make the connection.

That being said I am still having the same issue described here, but I am setting up WinRM in my autounattend.xml. Debug output doesn't say much, and I have verified that the client is responding on port 5985.

[donwlewis]

Forgot to mention using packer version 1.3.5 and plugin version 2.3