When I do the following, both online and offline VM's are discovered and can be added to a machine group- but VM templates DO NOT appear in list of items that can be added from a specific VMware Host.
1. From machine Group, Click Hosted Virtual Machines.
2. Click Add Server.
3. Enter FQDN Hostname.
4. Enter the admin credentials.
5. Result List of online and offline vm's appear , but NOT VM Templates.
What version of VMware host are you using?
Welcome to the communities.
Before suggesting anything hope you have went through all these steps.
It would be great if can share screen short or error message.
Thank you. We have several VM Teamplates shown in Vcenter, but when we add the host info in the Protect machine group only the VM's show up as being able to be added to the machine group. VM Templates are not shown.
Here is some information from a help article within Protect that may need to be checked:
During a scan, a template will be accessed using the VMware server credentials. Any individual credentials supplied for the template are ignored.
You should supply online credentials for any virtual machine template that will be included in a patch deployment process. During the patch deployment process the template is converted to a virtual machine and powered on -- VMware vCenter Protect will need the supplied credentials in order to access the online virtual machine.
When deploying patches to a virtual machine template, the following VMware server permissions are required in order to manage snapshots and to perform the deployment:
You might also need to ensure that VMware Tools is installed on the template so we can fully interact with it. Make sure to try hitting the "refresh server" button within the machine group as well to see if this helps bring up the templates.
1 of 1 people found this helpful
Also, are you connecting to the ESXi server or vCenter server with Protect? You would need to connect to vCenter for it to bring up templates.
Thank you. I had added the VM templates by connecting to the Vcenter Server.
Problem I have now is completing patching of the template. I am able to scan and deplloy to the template but reports patches mising or need reboot, however I am able to do a reboot then do another patch scan with deployment to confirm. Thank you
Machine,Reason,Domain,IP AddressTemplate,Error: 552 - Proxied paths failed validation.,,
Also make sure that VMware Tools is installed on the template.
I only have a record of one similar case in our ticketing system - the issue for that customer was that port requirements were not being met. The port requirements can be found at the link below - just to note: vCenter Protect used to be Shavlik NetChk.
Port Requirements for vCenter Protect:
For the above mentioned case where this error was logged previously the customer reported that TCP port 135 is actually what caused their issue. It may also be worth checking the port requirements for accessing vCenter Server/ESXi, found here: http://kb.vmware.com/kb/1012382
I hope this helps.
Thank you Adam. The first scan with patch deploment works fine using the stand vm deployment template-- so I think ports are good. Problem is the patches show up as failed/or needs reboot. Then a second scan fails with the error noted.
Can you verify that VMware Tools is installed on the template?
It might also help to provide log files from this process in Protect. The steps for obtaining logs can be found here:
If you prefer, you can PM them to me or open a support case to directly work with us on the issue.