Offline VM or Template Deployment fails with - Virtual Deployment Failed status

Version 2

    Purpose

     

    This document will provide information and a solution to a known issue that may cause offline VM or Template deployment to fail.

     

    Description

     

    You are able to scan an offline VM or Template, but the deployment attempt fails with this status:  Virtual Deployment Failed

     

    • This can be identified with the Status: Virtual Deployment Failed which can be seen in View > Deployment Track or View > Operations Monitor > Deployment Tracker tab.

     

    • This can also be identified in the logs located here: C:\ProgramData\LANDESK\Shavlik Protect\Logs on the Protect server.

     

    VirtualDeploymentStateMachine.cs:334|GettingFiles /Infrastructure/VM Templates/Windows Templates/Standard/VM-WIN2008R2: VMware.Vim.VimException: A specified parameter was not correct.
    ---> System.Web.Services.Protocols.SoapException: A specified parameter was not correct.

    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
    at VimApi_60.VimService.InitiateFileTransferFromGuest(ManagedObjectReference _this, ManagedObjectReference vm, GuestAuthentication auth, String guestFilePath)
    at VMware.Vim.GuestFileManager.InitiateFileTransferFromGuest(ManagedObjectReference vm, GuestAuthentication auth, String guestFilePath)
    --- End of inner exception stack trace ---
    at VMware.Vim.GuestFileManager.InitiateFileTransferFromGuest(ManagedObjectReference vm, GuestAuthentication auth, String guestFilePath)
    at ST.Virtual.Vim.VirtualMachine.CopyFileFromGuest(String guestPath, String destinationPath, Credential credential)
    at ST.Services.VirtualDeployment.VirtualDeploymentStateMachine.ProcessTrackerFile(VirtualMachineState virtualMachineState, VirtualMachine virtualMachine)

     

    Cause

     

    • You are specifying local administrator account credentials containing .\Username.
    • You are specifying local administrator account credentials containing WorkgroupName\Username.
    • The account you are using is locked out.

     

    Resolution

     

    • Supply the username only when providing a local administrator account.  Do not add .\ or a workgroup name\.
    • Supply domain\username when providing a domain account.
    • Verify the account you are using is not locked out.

     

    Affected Products

     

    Protect 9.2+