1 Reply Latest reply on May 2, 2016 12:00 PM by cwinning

    Deploying patches to a VM template fails - "Virtual deployment failed"

    thatch Rookie

      Hi,

       

      I'm trying to deploy patches to a VM template that hasn't been updated in about a year. The only error message in the Operations Monitor is 'Virtual deployment failed." As far as I can tell, my Browse credentials are good, since I can scan the template, mark it as a VM, and power it on and off. I also added the template to the machine group from the 'Hosted VM' tab in Proctect. The odd thing is that the number of patches found decreases every time I re-scan the template after a failed deployment. The first time I scanned it, there were 138 patches missing. The next time there were 131 missing, and the time after that there were 123 missing. This seems to indicate some kind of timeout threshold is being exceeded. Has anyone seen this behavior before?

        • 1. Re: Deploying patches to a VM template fails - "Virtual deployment failed"
          cwinning CommunityTeam

          Hello,

           

          It does look like a timeout issue, you could try increasing the timeout period. (this is a guess without looking at logs)

           

          1) Close Protect.

           

          2) Go to the Program Files install directory for Protect, default:

          C:\Program Files\LANDesk\Shavlik Protect

           

          Make a backup of this files: STServicesBindings.config

           

          3) Locate and edit the 'STServicesBindings.config' file.

           

          4) Change this: (the current timeout is 2 minutes)

           

          <binding name="VirtualDeployment"

          maxReceivedMessageSize="131072"

          sendTimeout="00:02:00" >

          <security mode="Transport" />

          </binding>

           

          To This: (new timeout is 10 minutes)

           

          <binding name="VirtualDeployment"

          maxReceivedMessageSize="131072"

          sendTimeout="00:10:00" >

          <security mode="Transport" />

          </binding>

           

          5) Save the changes to the file.

           

          6) Restart the Shavlik Protect services. (or reboot)

           

          7) Test to see if the deployment to the VM template works now. If the same timeout message occurs again, test once more with a much higher timeout value such as below to see if it really is a timeout issue.

           

          <binding name="VirtualDeployment"

          maxReceivedMessageSize="131072"

          sendTimeout="00:20:00" >

          <security mode="Transport" />

          </binding>

           

          If the issue persists, please open a case with the suppport team so we can take a look at logs.

           

          Thanks,

          Charles